Hyperion Entertainment Message Boards

@ssolie

And how about "old" applications, the new installer will mantain a sort of compatibility with LISP or there will be another retro-compatible installer method for all our old apps ?

I know that we need to think forward but maintain compatibilty would be welcome too, expecially when possible

The old installer can hang around for that.

Simon

I agree with abalaban, there needs to be some documentation for the python installer if you want to encourage people to use it. Reading back on the previous page I can only deduce that I should find this install.py and copy it to my application's directory, open it and play around. I did manage to locate documentation on the 'old' installer, but it all looks rather bespoke with an odd syntax. I'd rather adopt Hyperion's vision of a standard installer and learn to use Python - after all its a cross-platform language and there is nothing stopping me using the knowledge I have learnt elsewhere.
For example in the future when I have the time I would love to learn the flickr API and perhaps others too; how is that related? Well most of them support Python.

Wel this one should be really usefull to fix:

exec.library:

(*) Alert() is broken: Alerts cannot be closed on a SAM; only on a
PS/2 interface, not a USB or Synergyc interface. Consequently,
DisplayAlert() (in intution.library) is likewise broken. (You can
use http://aminet.net/util/misc/AlPatch.lha (or similar) to work
around this.)

Everytime i have an Alert i need to turn-off my machine completely (Sam440 Flex) because the mouse doesn't seems to work at all

The Alert() thing is reported as bug 6243.
Thanks.

Do gcc bugs go into bugzilla aswell or will it be handled by a completely different person/team?
If yes, where could one get support/send bug reports?

Elwood wrote:The Alert() thing is reported as bug 6243.
Thanks.

Nice, thanks to have looked at