Am Sonntag, den 04.11.2007, 22:09 +0100 schrieb Frank Schönheit - Sun Microsystems Germany: > Hi Ariel, > > > This would be a great idea!!! (though what about backwards > > compatibility? will it be too much code to implement - not to destroy > > the users old data?) > > meditated a little about this the last few days. The more I think about > it, the more I like it. > > We could, for compatibility, leave everything as-is with old documents. > That is, opening them would yield a warning "This document contains > forms and/or reports with embedded macros. This is not recommended > anymore. Please migrate the macros to the database document itself. Bla > Bla Bla." Something like this, with more sugar added, of course. (One > could even think about a automatic migration, though this would > inevitably lead to conflicts in case we have equal-named > functions/modules/libraries in different sub documents.)
Although I do have some macros in forms (for interaction and things strongly relating to the form, more generally useful things are in libraries) I could accept this solution inside .odb documents very well. Base is young enough, so not too much will be broken by the change. But the compatibility makes me think. How would one deal with older solutions from OO.o 1.x, where standalone forms were the only database document type? Will the difference persist and the change in hierarchy only apply to .odb-forms? E.g. I have some forms from 1.1 doing funny things like having two listboxes side by side, one showing the underlying table and the other one showing the users selcetion. Much like in the import wizard when selcting fields to import, with button for moving from one list to the other. The code therein is really very specialized on this single form in building a filter on a second logical form in parallel to the main one using the same table, I never had an occasion for reuse. So, there are cases when having code in the form itself makes sense, but inside a .odb there is not much lost in having these form related code in a library "My Macros -> Form Interaction xyz". But for single writer doc forms this is an issue. Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
