neooffice 2 upgrade suggestion

[fabriziovenerandi]

I installed neooffice 2.0 on my powerbook, ok, but I do not install it on office's mac mini where I work, 'cause the oo 2.0 Base section is still full of bugs (it is not a neooffice problem, but a Oo one).

When I'll move from neooffice 1.2 to neooffice 2.1 (hoping in a more stable Oo 2.1) anyway I'll have to move my database from neooffice 1.2 to neooffice 2.x. I have no problem for table, cause I'm using mysql, but I'll have to built a macro to export all the queries (or make a long copy-past from one program to another) and re-create queries in neooffice 2, and after I have to rebuilt all the forms (importing neooffice 1.x forms in neooffice 2 is like building a house with sand and water).

The choice to give neooffice 2 as upgrade to neooffice 1 is a problem, cause to move query and forms, I need to have all the programs working, to copy sql from one to another, test new forms, inspect older forms gerarchy, et ceterae.

Also I can try to test something here in office sometimes, but I can not 'cause the neooffice 2 installation will 'delete' the neooffice 1.2 i need to work.

So, I understand the problem that a neooffice 1.2 and neooffice 2 could have living together, but I suggest you to find/give a way to keep all the programs on same machine, 'cause for some kind of work (like databases) the moving from neooffice 1.2 to neooffice 2.0 is quite hard, and become real real hard if you can not use all the programs together for a short time.


f.

[sardisson]

There are 2 real issues with that:

One, Mac OS X does not play nice with 2 different versions or copies of the same program. You never really know which one a double-click on a document will launch.

Two, the OOo code has a tendancy to write hard paths all over the prefs that cause problems when the app is moved or renamed.

The second one can be worked around, either at install-time (install to different volumes) or via some careful manual editing of prefs files and Patrick's "fix paths" code.

So move or rename NeoOffice 1.2.2 before installing 2.0 and you can keep both, provided the path-fixing-code catches everything in the 1.2 prefs.

Smokey

[OPENSTEP]

While OS X will get confused, generally I've found that if you've already got an application running that can handle a specific document type, OS X will pass along the open request from the finder to that application first instead of launching what it thinks is the "preferred" one. Granted, this is without using the "Open With" to map types to apps.

The bundle renaming should work for two Neo versions, but make sure to use a name that contains *neither* spaces *nor* slashes. The preferences may still compete on launch (e.g. 2.0 may still try to import 1.x prefs), but I'm not 100% sure that's the case.

Also, to keep Spotlight from losing its tack, you may want to dive into one of the bundles and remove the duplicate neolight.mdimporter. Although spotlight may be confused, it shouldn't matter as the importer is identical between Neo 1.x and 2.0 Alpha PPC.

ed

[OPENSTEP]

Additionallly, if Base seems to be just a load of buggy ***p, I've got no problems with actively considering removing it wholesale from Neo and trying to shim in the 1.x support. Not sure if that'd be possible on that large a scale, but I have done it with other things in the past (e.g. floating palette implementation changes in 1.1 for which I replaced 1.0's implementation in /C)

ed

[jakeOSX]

i would suspect that base would be buggy. if memory serves, access had three versions before it was stable.

i'd say leave it in though. better spend that time doing other things. you know. like drinking beer. with ninjas. in an igloo.

[OPENSTEP]

[jakeOSX]

geishas are ninjas with fans.