@wawa
Its zune/mui differences again :(

> Binaries with SSL linked are massively bloated.

massively bloated ! too much for additional 0.5 mb, nope ?:)

> It is plain stupid to go backwards from a shared library that can be easily upgraded separately from the things using it, to having them all statically linked to it.

What is more stupid, its being forced to wait years for amissl being updated, instead of just grab when you want latest openssl, and rebuild your apps.

> a lot of code expects to use the AmiSSL API to access the SSL code and would need modified to work with openssl directly

What code ? Ibrowse only ?:)

My point is : that all fancy good to have amissl, but if one want to make anything with ssl, it is better to attach another 0.5 mb but be sure that once new verson of openssl out, you can rebuild your projects without that "amiga waiting of years for simple things". And calling that "stupid" and "massively bloated" sounds like only amiga, sorry :)

Can anyone explain needs of that native amigassl port ? I mean, what wrong with staticaly linked openssl libs, which have no needs to be wrapped by amiga-native-library-only-for-make-it-look-more-amiga. Or i miss something and amissl doing something and give us something which pure openssl port (./configure;make) can't ?

@hal9000

Quote:

Probably nope, as every thing i touch when it come to MUI/ZUNE always shows that Zune still different and react somehow different. There need someone who know ZUNE quirks and co and can adapt mui based parts.

If it will be any of help for AROS version, there is latest VPDF source code with amigaos4 ifdefs/makefiles/etc ready to build:

https://github.com/kas1e/mui_ports_to_os4/tree/master/VPDF

I read on morphzone that mazzie works on it as well some time ago, and even have it partially working , dunno why it wasn't finihed. I can help with if need it.

@slicer
Automatic conversions from asm to c , or from c to asm, never will produce decent enough result. Its all need to rewrite manually step by step, and only then.

Imho easyer way will be just clone whole gui/graphics, but write everything in the core from scratch, on C.

Of course nothing should be broken. Dopus5 porting done without loosing anything from previous version, and arexx parts should works too, of cours. At least, on os3 and os4 dopus5 arexx port works.

Can't say how it on aros, probably Paolo can answer on. But if you believe somethig is broken, plz make a bugreport on SF and we can check it more deeply.

@nikolaos
Probably before it was just corrupted download, or, what is more possible, you download arm-version by some ancident, that can explain thing like "double click on icon and nothing happens" , on all amiga oses when used "wrong" binary, by default clicking on icon do nothing.

Btw, versions on aros-archive.org , are the same as on dopus5.org of course. You also can always grab latest nighly from dopus5.org (currently its 5.92), and help us betatest it same as you do with aros nightlys :)

If you find bugs, plz report them on our sourceforge's bugtracker.

Thanks for using it :)

@nikolaos
I myself didn't test aros version and probably you need to ask BSZili (as he works on aros port) or author of Icaros (as he integrate it to icaros, so should have clue as well).

In meatime you can play with snoopy (or analog), to see what happens when you click on icon, run it from shell, recheck that it i386 version and not arm downloaded by ancident, etc.

You may also try 5.90 version, will it react different, or the same. If the same, problem can be on our side, if 5.90 not works too, then probabaly something with latest-nightly-build of aros.