Richard,
actually more worried about the osx and windows versions of the
standalones keeping up. i have been solving this by working in the
2.61 IDE and making the classic standalone from that then opening the
stack up in the latest rev for then creating the mac and osx versions.
rub with this is always worrying something might be funky with the
2.61 stack in the newer rev sometime and then fun tracking it back and
fixes might need to then bifurcate the development effort that would
be a mess.
would be nicest to start working in the 3.0 ide then build everything
from there as long as i dont end up doing something that does not
transport back to classic builds...
from the problem with classic builds in the current rev 3.0 that
François reported, it looks like i will need to continue in 2.6.1 ide
for now then move the stack to 3.0 to do the osx and windoz builds.
cheers,
jeff
On Sep 18, 2008, at 5:45 PM, [EMAIL PROTECTED]
wrote:
The nice thing about supporting Classic is that it's frozen in time,
just like the Rev engine for it appears to be. Apple isn't likely
to do
anything more for Classic, so the Rev 2.6.1 is expected to run as long
as your hardware holds out.
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
