On Jan 16, 2007, at 4:50 PM, Andy Dent wrote:
On 17/01/2007, at 1:38 AM, Tim Jones wrote:
After you've converted your app to use the new REALDatabase
format, your users would only need to run the conversion once.
Therefore, you wouldn't need to provide the converter into
perpetuity.
You're assuming customers themselves migrate entirely to Intel.
That is a highly unlikely scenario for schools and some small
businesses. Thus, the issue remains of people generating "old"
documents.
Not at all. You create the updated version of your app that uses the
new version of the database. Add the conversion routine into your
new app and check the datatable the next time it's run. This is
regardless of the type of platform they are on (of course, back to 9.x).
I guess the bottom line is having to tell customers if they want to
keep using Classic, they can choose to either:
1) run the main app under Rosetta, or
Just update them - provide a PEF build for 9, and then Mach-O for 10
PPC and UB for PPC or Intel - customer's choice. It's just a build
step from your perspective.
2) manually convert the file as a secondary step.
Not required if you have the conversion built into your new version...
or
hmmmm
Could I ship a command-line conversion utility that runs under
Rosetta, that could be invoked transparently from the Intel UB as a
shell task?
Absolutely. Build a console app that JUST converts the old format
into the new format.
Tim
--
Tim Jones
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
