well I agree that it pushed it too far of course, but basically that was determined not by me but by Peter who wanted there to be bindings for basically everything in the Danish localization.
As well as repeating of lines. The killing thing was on the line, where it was actually decided to try to ease up on the forms by allowing there to be only two allowance charges on any line, but each charge needed something like 7 bindings for that charge. So that, with the bindings already on the line was something like 20+ bindings per line. Now lets say you say you want 15 lines. Then on top of that start adding in the various parties, the payment requirements and stuff. yes it was definitely pushing it further than it should. But mine not to reason why, mine but to bind and cry. Remember no repeat, no dynamic creation of elements and bindings in form, so that if you need to have some elements in some of your forms they must basically be present in all, and bound, whether or not the actual form user wants them (although I did produce some code to show how you could build templates for producing the forms, and then get rid of the form parts you didn't want.) I also had some hacks using the extensible content (which required bindings) to get over some problems with updating parts of the form dependent on values in other parts, For example choosing currency values and such. Because by putting values into the extensible content I could output a value that wouldn't create a problem. So these bindings were related to other limitations of the OO xforms implementation, aside from the lack of repeat. Cheers, Bryan Rasmussen On 10/4/07, Stephen Green <[EMAIL PROTECTED]> wrote: > Hi Bryan > > How does that compare with my ODF XForm Ken hosted at > http://www.cranesoftwrights.com/resources/index.htm#odf-xslt ? > > Also, my XForms for Firefox for most key UBL documents > http://www.systml.co.uk/content/view/43/54/ only use a few > bindings and seem to work OK. > > I think you may be pushing the ODF XForms a lot too far > - they are a simple provision for simple solutions IMO. So > far at least. > > The filters seem to be more suited to complex requirements. > You could even provide a standard mapping of the UBL into > a table and export a UBL spreadsheet as HTML then transform > it to UBL perhaps. ODF is itself a standard (ISO of course) > so you could maybe just combine the UBL with the ODF, > specifying a standard mapping of items in the ODF map to UBL, > then send the ODF itself as if it were the UBL Order or Invoice. > http://lists.oasis-open.org/archives/ubl/200709/msg00037.html > It's all standard XML anyway. The same would apply, I guess, > to any XML. Just send it as ODF and specify the mapping ?? :-) > > Regards > > Steve > > On 04/10/2007, bryan rasmussen <[EMAIL PROTECTED]> wrote: > > I would think that 1000 bindings is too much, by too much I mean that > > there would most probably be a noticeable lag between typing text on > > the keyboard and its appearance in the input field on the form. IIRC > > an order form with ten lines in UBL produced (after all unnecessary > > bindings had been dropped) somewhere in the neighborhood of 2000 > > bindings and keys entered had a lag time of some seconds per key. So > > that with my typing speed entering my name in a field meant I was done > > typing and sitting around for what must have been ten seconds while > > the field finished getting filled in (I timed it and wrote it down > > somewhere but don't want to go look now).This could have been > > optimized perhaps, but probably not that much. > > > > 300 though I think would be reasonable. > > > > Cheers, > > Bryan Rasmussen > > > > On 10/4/07, Zhang Weiwu <[EMAIL PROTECTED]> wrote: > > > Zhang Weiwu wrote: > > > > bryan rasmussen wrote: > > > > > > > >> As far as repeat, no. I have some examples generating UBL documents > > > >> (Invoices) outside of OO with the user determining at generation time > > > >> how many lines are required. This however ran into another problem > > > >> with the OO implementation which cannot handle the large number of > > > >> bindings such a format as UBL requires for the editing of a large > > > >> document. > > > As of number of binding limitation, how is it? As for the project I am > > > working on, we commonly have XForm that have 300 values in it (would > > > reflect 300 bindings). > > > I would think as an extreme case a form we have may reach 1000 bindings > > > in the future. How is your experience in regarding to binding limitation? > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Stephen Green > > Partner > SystML, http://www.systml.co.uk > Tel: +44 (0) 117 9541606 > > http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
