Scalos discussion

[Amiwell]

deadwood will make scalos functional you know it needs fixing at the moment

[OlafS3]

@Amigasystem

I do not want to have a discussion about that with you again

I disagree

That is your opinion... I will supply Deadwood with test versions so he can decide himself based on facts and is not dependent on "opinions" (be it my opinion or yours)

[Amiwell]

then we will wait for the opinions of deadwood who however expressed favorably that he wanted to work on scalos

hi

[AMIGASYSTEM]

@deadwood

I copied "Menu13.prefs" and "Scalos.pre" from AROS 68k to AROS x86, "Menu Scalos" and "Menu Wander" work but the Scalos Apps Prefs Scalos freeze, see video.

In the video you can also see that the "Menu of Scalos" fails to place icons, while the "Menu of Wanderer" can automatically place icons, in the video you can also see the artifacts on the DualPNG icons.
Also note the slow opening of windows (no the system one, but the internal folders)

https://drive.google.com/file/d/19etrPIuQipBQltz9Fj_HspaRjibC9wso/view?usp=sharing


@OlafS3

I am not against Scalos, in fact I like it very much, the problem is that before putting it on AROS x86/68k it has to work well, You cannot distribute a Distro with all these problems !!!

[OlafS3]

@Amigasystem

As I wrote you are free to have your opinion as I have mine. I will supply Deadwood with test environments and he can decide himself.  I really want to stop it here please. I only asked Deadwood to look at the problem with the two preference dialogs that not open on X86 and not this discussion again.

[AMIGASYSTEM]

Ok, I will not do any more tests for Scalos !

[OlafS3]

Ok, I will not do any more tests for Scalos !

You can report problems like the artifacts but not always repeat your conclusions. That is opinion, not fact.

The advantage and disadvantage (at the same time) is Scalos is much more complex than Wanderer. There are many options that change behavior and it is more complicated to install. That makes it look like bugs whereas that is often not the case. Deadwood is able to draw his own conclusions from what he sees when using it. I will supply Scalos installations so he can look at it. You are free to do the same.

[OlafS3]

Yes, as you can see from the screenshot, on AROS 68k it works auto disposition, but from the Wanderer menu, the native Scalos Menu is not present on AROS 68k.

On AROS 68 Gadgets don't work, also tried other Gadget paths

The gadgets work on Aros 68k... I could make a screenshot but I am not at home. I will show it this evening. As I wrote solution is copying images from scalos to individual themes on aros. Then it is ok.

[deadwood]

https://drive.google.com/file/d/19etrPIuQipBQltz9Fj_HspaRjibC9wso/view?usp=sharing

Thanks for the video. It made clear what you were describing.

[deadwood]

Here is list of issues I noted down from the discussion so far. I understand that some of them have workarounds (like THEME: assign) but they are not addressed in the default  build.

Code: [Select]

1) (x86 & 68k) Menu13.prefs file is missing in AROS build
2) (x86) DualPNG icon is rendered wrongly. Half of the icon only or text is missing.
    Using "Scalos -> Update" does not fix it.
    Using "Window -> Clean up by -> Name" fixes the current view, but when scrolled down newly shown icons are wrong agin
3) (x86) After copyign Menu13.prefs and Scalos.prefs from 68k, Scalos Preferences application freezes at startup
4) (x86 & 68k) There is conflict in THEME: assign between AROS and Scalos. Both use it for their own theme settings
5) (x86 & 68k) If THEME: is set as default on AROS, button images are not visible in Scalos Preferences application
6) (x86 & 68k) If THEME: is set as default on AROS, top nagivation toolbar is not visible in drawer windows
7) (x86 & 68k) Refresh of drawer windows is considerably slower than on Wanderer
8) (x86) Prefs/Locale is not working when started from Scalos and causes other preferences to fail.
9) (x86) Prefs/Input is not working when started from Scalos and causes other preferences to fail.

Let me know if I documented them correctly.

@AMIGASYSTEM, @OlafS3. I see value of both your input and I would like to work with both of you on getting Scalos more "in shape" once I'm done with ABIv0 refresh if you can acknowledge that you have difference in opinions and put them asides, at least for this work. Otherwise it will be pretty irritable experience for all of us and that's not something I'm interested in.

[OlafS3]

Here is list of issues I noted down from the discussion so far. I understand that some of them have workarounds (like THEME: assign) but they are not addressed in the default  build.

Code: [Select]

1) (x86 & 68k) Menu13.prefs file is missing in AROS build
2) (x86) DualPNG icon is rendered wrongly. Half of the icon only or text is missing.
    Using "Scalos -> Update" does not fix it.
    Using "Window -> Clean up by -> Name" fixes the current view, but when scrolled down newly shown icons are wrong agin
3) (x86) After copyign Menu13.prefs and Scalos.prefs from 68k, Scalos Preferences application freezes at startup
4) (x86 & 68k) There is conflict in THEME: assign between AROS and Scalos. Both use it for their own theme settings
5) (x86 & 68k) If THEME: is set as default on AROS, button images are not visible in Scalos Preferences application
6) (x86 & 68k) If THEME: is set as default on AROS, top nagivation toolbar is not visible in drawer windows
7) (x86 & 68k) Refresh of drawer windows is considerably slower than on Wanderer
8) (x86) Prefs/Locale is not working when started from Scalos and causes other preferences to fail.
9) (x86) Prefs/Input is not working when started from Scalos and causes other preferences to fail.

Let me know if I documented them correctly.

@AMIGASYSTEM, @OlafS3. I see value of both your input and I would like to work with both of you on getting Scalos more "in shape" once I'm done with ABIv0 refresh if you can acknowledge that you have difference in opinions and put them asides, at least for this work. Otherwise it will be pretty irritable experience for all of us and that's not something I'm interested in.

I will try that and hopefully Amigasystem too

I do not think that the list is correct... 

1) yes I copied it from 3.X version and then changed it with scalos preferences
2) icons are shown correctly including label. It depends on a option in configuration. Sometimes icons overlap so one icon hides the label of another icon. So it is not a bug in my view.
3) is not correct either. He propably used my configuration but if I f.e. use certain images for windows that are not present on another installation pref file might fail. I f.e. use same images on both X86 and 68k and exchange preference files without any freezes or crash
4) 5) and (I assume) 6) can be solved by copying images to theme:. I copied scalos images in every theme directory and it worked. At least on context menu and in preference dialog
7) yes it is slower. On the other hand you have tons of options how to display icons in a window that are not in wanderer. Everything has a prize. Of course making it faster is never bad.
8. and 9) yes

[deadwood]

@OlafS3

4,5,6 - I understand there is a workaround. I want this to work "by default", without a need for a workaround.
3 - that is what I see on the video. I'll add a note that this is possibly due to images being stored in copied configuration that are not present on disk
2 - that is not what I see on the video that AMIGASYSTEM shared. There the icons are damaged with default display. Can you let me know (best with a screen shot) what option where needs to be changed as a workaround?

[AMIGASYSTEM]

@OlafS3

In your systems you have disabled Wander Themes, try enabling them and when you change Theme to Appearance you will no longer see the Gadgets.

When you use Appearance the Path "Theme" data "changes" because it moves to the chosen Theme folder!!!
In  OS you can't copy settings to all themes, it doesn't seem like a thing to do this

You see my video, use DualPNG icons, try to do the same thing and show us your video

Scalos is no more Complex has one program unique that handles all preferences like Dopus5 and Ambient, this does not mean it works better than Wanderer which has many Amiga-style preference apps makes it lighter and more intuitive.

Example Wanderer fixes the Icons Automatically "Forever," you don't bio need to ask every time

[deadwood]

Scalos is no more Complex has one program unique that handles all preferences like Dopus5 and Ambient, this does not mean it works better than Wanderer which has many Amiga-style preference apps makes it lighter and more intuitive.

Example Wanderer fixes the Icons Automatically "Forever," you don't bio need to ask every time

I've taken a note of that problem in Scalos, please see my list above. If I worded it wrongly, let me know. Any other reason to bring up this topic?

[AMIGASYSTEM]

There are only two things that are not correct:

3) Regarding the crash, this happens if it is present in Env-Archive/Scalos, the file Menu13.prefs, the crash happens with any version of "Menu13.prefs", whether taken from OS3 or from "AROS-20180423-1-any-i386-contrib"

4) On AROS x86, there are no conflicts, as you can see from the archive "AROS-20180423-1-any-i386-contrib", Scalos on AROS X86, looks for its data files in the path:
Scalos:Themes\Default_Theme