Hi Fernand, On Tue, 2009-10-06 at 12:04 +0200, Fernand Vanrie wrote: > Noel , > > Any change your code can been used in Basic ? well, it depends what you mean by my code, iirc ( and it's been quite a while since I looked at this ) the code I have in the ooo-build filter substitues the form control model when building the imported dialog ( this is sure to be done by the existing uno api and hence should be achievable by basic ) I am not sure if doing this out of the box will work in the vanilla build, but, I see no reason why it shouldn't. Also you would need to do all of this programatically, e.g. create the Dialog and add the required controls/models[1], position them, set the appropriate attributes etc. all manually. In theory it *should* work. Anyway it's worth a try I guess ( I will look back my code when I get a chance )
hth Noel [1] e.g for a data-aware listbox call insertByName on the dialog model and insert a control created from "com.sun.star.form.component.ListBox" specifier instead of "com.sun.star.awt.UnoControlListBoxModel" > > Greetz > Fernand > > Hi Frank, > > On Tue, 2009-10-06 at 09:45 +0200, Frank Schoenheit, Sun Microsystems > > Germany wrote: > > > >> Hi Fernand, > >> > >> > >>> For months i am looking for the best solutions to manipulating data in > >>> Dialogs instead of forms. > >>> > >> Just this morning, sitting in the subway and having no newspaper to read > >> :), I wondered whether it would make sense to implement the runtime code > >> for all the database controls in dialogs. Adding a full-blown dedicated > >> UI for creating "database dialogs" would be an additional effort, but > >> perhaps it would be valueable having only the "runtime", i.e. the > >> ability to programmatically create and execute such dialogs. As a first > >> step, at least. > >> > > This sounds a little familiar to something we discussed on this list in > > the past ( it wasn't exactly the same thing, but if you remember we > > talked about using form control models ( especially data aware ones ) > > with the toolkit controls in dialogs ) as such, I think supporting > > database controls is a great idea :-) > > Btw I use currently use the form control models with the toolkit > > controls ( and it seems to work well ) in ooo-build, the (self imposed) > > limitation is that this is only available 'transiently' when importing > > MSO 'Userform' controls. Not sure if any of the work I have done is that > > useful in this case but I'd happily attach it/upload [*] etc. somewhere > > should you want it or think it's useful. In anycase I am interested in > > upstreaming this code anyway but I was thinking about doing that in the > > context of a future vba support CWS. > > However, as I said at the moment it really isn't suitable to be used > > with Openoffice directly ( lack of ui/persistence support for one ) and > > I haven't had the time to concentrate on that part of it :-/ It sounds > > though that any work in this area would be relevant to ( and affect ) a > > 'proper' solution for what I would like to do, so I am very interested > > > > Noel > > > > [*] currently I don't recall exactly what I have in terms of changes but > > iirc it's just a cheap and nasty solution to use the appropriate (form) > > models when the dialog is in vba mode > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org > > For additional commands, e-mail: dev-h...@dba.openoffice.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org > For additional commands, e-mail: dev-h...@dba.openoffice.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
