Guido Casper wrote:
Upayavira wrote:
Upayavira wrote:
Guido Casper wrote:
Upayavira wrote:
Marc Portier wrote:
now, in this case backendX is cocoon (modifiable) sources, so I
would guess some saveToSource/loadFromSource can be made quite
generic and might very well be candidates
Marc Portier wrote:
also having the saveDocument and loadDocument you propose here
_outside_ the woody specific flowscript seems to make them more
widely re-useable in different areas!
with those in place I think my previous idea to 'extend' the Form
object from woody2.js is a nice (almost
Upayavira wrote:
Guido Casper wrote:
Upayavira wrote:
Marc Portier wrote:
now, in this case backendX is cocoon (modifiable) sources, so I would
guess some saveToSource/loadFromSource can be made quite generic and
might very well be candidates for natural extension of the woody2.js
Upayavira wrote:
Upayavira wrote:
Guido Casper wrote:
Upayavira wrote:
Marc Portier wrote:
now, in this case backendX is cocoon (modifiable) sources, so I
would guess some saveToSource/loadFromSource can be made quite
generic and might very well be candidates for natural extension
Upayavira wrote:
Marc Portier wrote:
now, in this case backendX is cocoon (modifiable) sources, so I would
guess some saveToSource/loadFromSource can be made quite generic and
might very well be candidates for natural extension of the woody2.js
Yup. You've confirmed what I suspected. What I
Guido Casper wrote:
Upayavira wrote:
Marc Portier wrote:
now, in this case backendX is cocoon (modifiable) sources, so I would
guess some saveToSource/loadFromSource can be made quite generic and
might very well be candidates for natural extension of the woody2.js
Yup. You've
Upayavira wrote:
snip/
Hmmm. Actually, Tony, I think you might have helped me with one of my
own sites. If I can use Woody binding to bind to a modifiable
XMLDBSource, I don't need to write any of my own Java, which would be
cool. I think I'll have a go at making XMLDBSource modifiable. (For
Upayavira wrote:
Tony Collen wrote:
Has anyone given thought to binding a Woody form to a Xindice document?
I'm starting to develop an app, and I'd like to explore various
binding methods. Xindice seems like it would be useful for this sort
of thing.
I can only agree. And Vadim has been
Upayavira wrote:
Upayavira wrote:
Tony Collen wrote:
Has anyone given thought to binding a Woody form to a Xindice document?
I'm starting to develop an app, and I'd like to explore various
binding methods. Xindice seems like it would be useful for this sort
of thing.
I can only agree. And
From: Marc Portier [mailto:[EMAIL PROTECTED]
snip/
It depends on what you call 'binding'
strictly speaking (technically) the woody-binding is about copying
values between the form-instance and some object-model coming
from some
backend
these object-models are pretty much
Marc Portier wrote:
Upayavira wrote:
Upayavira wrote:
Tony Collen wrote:
Has anyone given thought to binding a Woody form to a Xindice
document?
I'm starting to develop an app, and I'd like to explore various
binding methods. Xindice seems like it would be useful for this
sort of thing.
Has anyone given thought to binding a Woody form to a Xindice document?
I'm starting to develop an app, and I'd like to explore various binding methods. Xindice seems like
it would be useful for this sort of thing.
Regards,
Tony
Tony Collen wrote:
Has anyone given thought to binding a Woody form to a Xindice document?
I'm starting to develop an app, and I'd like to explore various
binding methods. Xindice seems like it would be useful for this sort
of thing.
I can only agree. And Vadim has been very active on XIndice
13 matches
Mail list logo
