In my idea it would be a nice-to-have feature that it runs on all 2.x releases but the main focus should be on the current stable release.
Maintaining versions to be compatible with all OO-Versions is in my idea a night mare and adding code to distinguish between these version only makes the whole thing less understandable for a beginner. But that's only my way of thinking maybe others have another opinion. You may demonstrate the concept of recognizing the version in an external document. Tom Andrew Jensen schrieb: > Andrew Jensen schrieb: >> The question is , what would be a good example. Which I suppose comes >> first to the question, as always, of 'the target audience' for Base. >> > How about a target Base release. Should it be that the example runs > completely in the most current release, but not necessarily in older > releases? > > An example - the form eventAttendees3 in the eventKeeper database looks > different between 2.0.3 and 2.0.2. Under 2.0.2 the status line is about > 1/2 inch from the bottom of the window frame, and the top level menu is > gone. Under 2.0.3 neither of these are true. I see three possiblilities: > > 1. Ignor the problem. > 2. Don't make use of chaning the layout manager. > 3. Add code to the library to recognize the different versions. > > > What do people think? > > Drew
signature.asc
Description: OpenPGP digital signature
