*** tech1_ has joined #gnuenterprise *** shmooz has quit IRC *** dcmwai has joined #gnuenterprise *** reinhard has joined #gnuenterprise *** johannesV has joined #gnuenterprise *** sjc has joined #gnuenterprise *** kilo has joined #gnuenterprise good morning reinhard: finished translations, green lamp for release ok thanks johannesV: are german translations also up to date? reinhard, yes i've updated them yesterday (only needed in common though) ok thanks sorry, but i've seen this typo just this moment ... kilo: have you been successfull with ? *** btami has joined #gnuenterprise johannesV: no ok iirc there was some namespacing problem seems so yes anyway it's kind of a philosophical question wether to integrate trigger-code into forms or not for *large* trigger it could be helpful for reading the gfd, but one would have to provide two files to the client then oth one could ask if *large* triggers are a *right* solution to a given problem ... (like doing things in appserver instead on the client side) in my case it should serve code reuse. if you look at the invoice forms, nearly all contain the same code in the startup trigger right maybe i can fix something ... not vital at all hmm, importing dialogs does not work too ... that's really bad hmm same error? yes, the error appears to happen in GParser.py line 451 (GImportItem.primaryInit) actually the parent of type None (which is a GFForm instance) has an attribute _app which is None too so it cannot provide a property called '_parameters' i see *** dcmwai has quit IRC ok, i've fixed it but it's not very usefull though ... now the dialog (which is a form with style=dialog) get's loaded by GFParser.loadFile () but this leads to all phased inits which ends up in an activateForm (__main__) so the dialog superseeds the *real* main form and i get a clash ... i think we let ja* fix that importing stuff i agree the quick-fix was to either use findParentOfType (None)._instance in common.GParser did it fix import-trigger too? or to add a '_app': instance to forms.GFParser haven't tried yet ... just a sec no, it's not useable at all because the import-trigger leads to a loadFile () and loadFile expects a *complete* form-definition (gfd) including form-tag, logic, layout, ... but i can try it with that stuff all there ... ok importing works ... yes, importing triggers definitly works so i haave to define a foo form that contains them triggers right i'll try to replace that dialog-import thingy using a runForm () with params ... hmmm, it's kind a ... hmmm... interesting like when a woman is neither beautiful, nor nice, nor clever, then you say, she is 'interesting'... :) does runForm () work for you ? oho ... shit i've got it it's the name-tag !! if you set a
you !!!! cannot !!! open it using gnue-forms :) cause it's missing the key __main__ in the formsDictionary ok, so, if i *remove* the name-attribute from my dialog-form everything is ok we can circumvent that import-dialog problem by using an external form with style="dialog" which get's called using runForm ('dialog.gfd', parameters) this has the same effect as a call to activateDialog () wrt to trigger-import i think we really wait for jamest or jcater to ask what's all about that _app/_instance thing ok, as i've said eariler, it is not vital at all *** btami has quit IRC hmm, we cannot set 'navigable' attribute on GFButtons ? if it is a child of GFTabstop, it should be navigable but i want a button which does *not* get the focus so usually we do this by setting navigable="False" but navigable is no valid xml-attribute of