Directory Opus 5.9 AROS 68k build

[pixie]

On dopus5allamigas we have builds for each Amiganoid OS, we have for:

- AmigaOS 3.*
- AmigaOS4
- MorphOS
- AROS x86 and even
- AROS ARM;

Wouldn't it make sense to be using an AROS 68k build instead of OS3.* one or, like the Bohemian Rhapsody says, "it doesn't really matter"?

[AMIGASYSTEM]

AROS 68k does not need Dopus5, as said there are conflicts with Wanderer, see windows themes !

Wanderer can do the same things as Dopus5, if that is not enough there is Dopus4 which can do the same things as Dopus4

I used Dopus5 on my OS3 

[OlafS3]

do not let you confuse by Amigasystem there 

3.X build works pretty well on Aros 68k as desktop replacement. How ir behaves if combined with wanderer is not known to me. I use it for my distribution. I used latest from aminet (was 5.91 I think)

[AMIGASYSTEM]

OlafS3, you should listen to my criticism is those of users about Dopus5 anomalies, graphic appearance themes and icons are very important !

[pixie]

Hi AMIGASYSTEM!  

AROS 68k does not need Dopus5, as said there are conflicts with Wanderer, see windows themes !

What I see AMIGASYSTEM is that everywhere else who has windows themes' working with Dopus but AROS, that's what I see...

Wanderer can do the same things as Dopus5, if that is not enough there is Dopus4 which can do the same things as Dopus4

You know for example what can do the same things as AROS? AmigaOS, so there's that...

I used Dopus5 on my OS3 

Does Amiga OS needs it? Does MorphOS or AmigaOS 4 for that matter? I guess they don't, they use it anyway...   You've talked about conflits, well if you have an AmigaOS binary running on AROS I guess it will be more prone to conflits, although AmigaOS4 and MorphOS both seem to handle it better, wouldn't you like such a solution for AROS? If not why not?  If there's some conflits with Wanderer,  we would assume that Wanderer could simply be shutten down? Or perhaps have you considered that those conflits might not have to do with Wanderer, but that they still might be taken care of since it's open sourced et all...

do not let you confuse by Amigasystem there 

3.X build works pretty well on Aros 68k as desktop replacement. How ir behaves if combined with wanderer is not known to me. I use it for my distribution. I used latest from aminet (was 5.91 I think)

Indeed, it was because your distro that I went searching about it, those pesky gadgets! But I have since seen that there was no problems with AmigaOS 4 and that MorphOS has somehow dealt with it

[AMIGASYSTEM]

Yes on OS3 the old version of Dopus5 the gadget problem was fixed, newer versions of Dopus5 do not have this problem on OS3, OS4 and MOS.

On AROS, theme management is different from OS4 and MOS, which is why the gadget problem is not fixable.

Dopus5 might be fine on AROS if it was native AROS by eliminating Wanderer, but in this at the moment it is not possible because sooner or later it collides with Wanderer or its prefs.

Apart from that Dopus5 like Ambient from MOS, have a way of managing preferences on a single Application which often causes confusion especially with Dopus Magellan .

I prefer Wanderer because it is native and follows the Workbench line, i.e., one App per preference, this makes it easy to find bugs and anomalies, when this is done by only one App it is a problem, Scalos being an example.

[pixie]

do not let you confuse by Amigasystem there 

3.X build works pretty well on Aros 68k as desktop replacement. How ir behaves if combined with wanderer is not known to me. I use it for my distribution. I used latest from aminet (was 5.91 I think)

From what I saw perhaps a solution similar to MorphOS might be possible, but you would have to downgrade to 5.82

[AMIGASYSTEM]

Yes but as I have always maintained, my distributions will remain native with Wanderer, those who prefer Dopus5 can use other distributions.

With Wanderer you will always have maximum compatibility with everything, see for example the tests I am doing with "RNOfer", with Wanderer I had no problem associating the various file formats, with Dopus5 it will be much more complicated.

[pixie]

Yes but as I have always maintained, my distributions will remain native with Wanderer, those who prefer Dopus5 can use other distributions.

With Wanderer you will always have maximum compatibility with everything, see for example the tests I am doing with "RNOfer", with Wanderer I had no problem associating the various file formats, with Dopus5 it will be much more complicated.

I don't know what to say... am I posting on the wrong Forum by any mistake?

[jacko]

AROS 68k does not need Dopus5, as said there are conflicts with Wanderer, see windows themes !
Wanderer can do the same things as Dopus5, if that is not enough there is Dopus4 which can do the same things as Dopus4

If you think that, you clearly never used Dopus5, I mean REALLY use not just started and clicked some icons. And no Dopus4 is not a replacement (only 2 listers, cant handle well Icons, very weak file recognition, no Workbench replacement)
If there are conflicts of the themes, that only means that Wanderer is loosing track of it's Origins and does not follow the 3.1 API which it's suppose to replicate and made some incompatible changes to show unnessecary window themes, which other platforms manage to introduce in a compatible way.
And it's not only DOpus5, MUI's extra Gradgets also show strange behaviour sometimes.

[AMIGASYSTEM]

With Dopus4 as mentioned you can do the same thing, you just have to set it up, look at the difference between default Dopus4 and Dopus4 from AROS One. Dopus4 is the best known and most used file manager in the Amiga world, Dopus5 on the other hand only a few users used it, this is already an answer.

Tell me what problems there are on Dopus4 to manage the icones, or what files Dopus4 does not recognize, for sure on Dopus4 installed on AROS One there are "particlular" file associations that on Dopus5 there are not, this thanks to Datatypes descriptors that I created and that do not exist even on OS4 and MOS, among them the various types of Archives, audio files and video files.

The strange behaviors of MUI are due to the fact that Zune is not updated enough as MUI, consequently it cannot support everything as it should.