W3C home > Mailing lists > Public > www-forms@w3.org > April 2006

RE: Additions to section 7?

From: T. V. Raman <raman@users.sf.net>
Date: Tue, 4 Apr 2006 06:12:21 -0700
Message-ID: <17458.28853.406874.48702@localhost.localdomain>
To: mark.birbeck@x-port.net
Cc: www-forms@w3.org


This is a great discussion, and it is even better to see it
happening on www-forms.

Next, since these changes are concrete, I'd strongly urge the WG
to turn it into spec-ready text and publish a public Working
Draft. 

One thing we did well during the 1.0 timeframe and later started
slipping up on is to publish regular Working Drafts --- as the
XForms community grows out beyond the WG, it is important to
retain momentum by ppublishing early and often.



>>>>> "Mark" == Mark Birbeck <mark.birbeck@x-port.net> writes:
    Mark> Hi Allan,
    Mark> 
    Mark> All good suggestions:
    Mark> 
    >> 1) Get the default |instance| element when no parameter is
    >> given to getInstanceDocument()
    Mark> 
    Mark> Yes...good idea.
    Mark> 
    Mark> 
    >> 2) Make it possible to iterate over all instance documents
    Mark> 
    Mark> Good idea. And if your next suggestion is added (number
    Mark> 3) then you could also iterate the instance elements
    Mark> themselves to get all the documents.
    Mark> 
    Mark> 
    >> 3) Add "shortcut" for getting the instance document
    >> directly from the |instance| element.
    Mark> 
    Mark> Just pondering how this might be done. One thought is
    Mark> to go the way that the SVG group have gone, and just
    Mark> have a 'get' function (they have getSVGDocument()).
    Mark> 
    Mark> Another possibility is a bit more 'abstract', and that
    Mark> is to link this to the more general notion of 'shadow
    Mark> trees'. I don't know if you have such a function at the
    Mark> moment for your XBL, but there may be some crossover
    Mark> here; some general function that applies to other
    Mark> elements too, could be used to 'get the hidden data
    Mark> associated with this element'.
    Mark> 
    Mark> 
    >> 4) Make it possible to get from an instance data node to
    >> the |instance| element in the form.
    Mark> 
    Mark> That's an interesting one. Wouldn't the interface for
    Mark> DOM nodes have to be modified? That could get a little
    Mark> tricky.
    Mark> 
    Mark> Out of interest, what sort of use cases are you
    Mark> thinking of for this? Is it so that you can find out
    Mark> the model? Or do you want to get to other nodes in the
    Mark> same instance as a node you already have?
    Mark> 
    Mark> One last thing, do you have a way to obtain the
    Mark> instance node that is bound to a particular control?
    Mark> I'm sure you do, but that might be a useful method to
    Mark> standardise on. It could even be the same method as
    Mark> used for 'get the hidden data associated with this
    Mark> element' in number 3, above.
    Mark> 
    Mark> Regards,
    Mark> 
    Mark> Mark
    Mark> 
    Mark> 
    Mark> Mark Birbeck CEO x-port.net Ltd.
    Mark> 
    Mark> e: Mark.Birbeck@x-port.net t: +44 (0) 20 7689 9232 b:
    Mark> http://internet-apps.blogspot.com/ w:
    Mark> http://www.formsPlayer.com/
    Mark> 
    Mark> Download our XForms processor from
    Mark> http://www.formsPlayer.com/
    Mark> 
    Mark> 

-- 
Best Regards,
--raman

      
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs
Received on Tuesday, 4 April 2006 13:12:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:03 GMT