>I will see if I can build amphetadesk with my latest version >of standalone builder and report here.
Awesome. Make sure you use the latest CVS sources. Of special importance is that the lib/ directory SHOULD NOT NOT NOT be included in the runtime. The lib/ directory is intended to be shipped with AmphetaDesk, so that people can tweak the Perl code within, and the wrapper runtime would interpret the new changes. This allows me to do streaming updates of 200k tarbulls, not forcing a 2 or 3 meg download of the runtime for each update. >I fear the lot of questions users might have because of dynamic >module loading like 'require $module'. Those situations cannot be solved. Agreed. In AmphetaDesk, the only time I use "require" is *because* of it's at-runtime "drawback". Basically, AmphetaDesk determines what OS it's running under, and then 'require's a certain OS library to cope. >Let's see how things go with your project and decide the >principal questions later. Awesome. Please let me know how it goes. At the moment, my planned date for the next version of AmphetaDesk is June 15th. The code has been frozen (save bugfixes), the Windows .exe is finalized, I've got a guy working on an OS X pretty GUI wrapper, and the Classic Mac version is the last one left. If I can get it in 5.6.1 by then, awesome, if not, I'll be shipping the 5.004 version... -- Morbus Iff ( i'm the droid you're looking for ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ Tech: http://www.oreillynet.com/pub/au/779 - articles and weblog icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
