Re: [jelly] XMLOutput.data(Object)

Le 8 oct. 04, à 02:08, Dion Gillard a écrit : On Thu, 7 Oct 2004 11:40:27 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: More precisely, it's passing objects around. I see no other mechanism for a tag to pass an object to a tag that called it... (which is not always a parent tag). In keeping with

Re: [jelly] XMLOutput.data(Object)

Le 7 oct. 04, à 02:23, Dion Gillard a écrit : On Wed, 6 Oct 2004 15:18:50 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: Gee... I was really thinking this was obvious... hence the relatively undetailed descriptions. Obviously it isn't for me. It seems to me that you want to use XMLOutput to pass

Re: [jelly] XMLOutput.data(Object)

More precisely, it's passing objects around. I see no other mechanism for a tag to pass an object to a tag that called it... (which is not always a parent tag). paul Le 7 oct. 04, à 08:54, Paul Libbrecht a écrit : That's not really reading or writing, it's just catching!

Re: [jelly] XMLOutput.data(Object)

Now that's making some sense. On Thu, 7 Oct 2004 11:40:27 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: More precisely, it's passing objects around. I see no other mechanism for a tag to pass an object to a tag that called it... (which is not always a parent tag). In keeping with the

Re: [jelly] XMLOutput.data(Object)

Maybe one little quick example: - currently, jelly-swing's ComponentTag calls, somewhere down in its doTag() findAncestorWithClass(ContainerTag.class) to which they call addComponent... At least one major drawback: putting such in a defined tag does not work unless you go till the top-level

Re: [jelly] XMLOutput.data(Object)

How does this differ from writing to XMLOutput. It seems XMLOutput is being confused with the context...? On Wed, 6 Oct 2004 09:54:11 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: Maybe one little quick example: - currently, jelly-swing's ComponentTag calls, somewhere down in its doTag()

Re: [jelly] XMLOutput.data(Object)

It does differ only by the fact that you write an Object and not XML-nodes! Only, this tiny change to be able to invoke the sacred functional word. paul Le 6 oct. 04, à 10:12, Dion Gillard a écrit : How does this differ from writing to XMLOutput. It seems XMLOutput is being confused with the

Re: [jelly] XMLOutput.data(Object)

So what's the advantage over this versus the context. XMLOutput is for producing output, not storing data. The context is for storing data. Paul, I must be missing something obvious here. On Wed, 6 Oct 2004 10:37:21 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: It does differ only by the fact

Re: [jelly] XMLOutput.data(Object)

Gee... I was really thinking this was obvious... hence the relatively undetailed descriptions. - XMLoutput objects are exchanged as part of the doTag nested calls. Therefore it is easy for something aimed at receiving data to create an XMLOutput object that does something just for the

Re: [jelly] XMLOutput.data(Object)

On Wed, 6 Oct 2004 15:18:50 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: Gee... I was really thinking this was obvious... hence the relatively undetailed descriptions. Obviously it isn't for me. It seems to me that you want to use XMLOutput to pass data around, even though it's currently a

[jelly] XMLOutput.data(Object)

Dear Jellyers, I'd like to propose an addition to the XMLOutput class, used throughout Jelly: a method called data() (or object) accepting any object. By default... take the toString and call characters... Actually, this is the way it is done with the return value of a Jexl expression as part

Re: [jelly] XMLOutput.data(Object)

I'm not sure I understand what the use of this method is for Tags and TagLibraries, since it's on XML output. Can you give us an idea? On Tue, 5 Oct 2004 21:31:08 +0200, Paul Libbrecht [EMAIL PROTECTED] wrote: Dear Jellyers, I'd like to propose an addition to the XMLOutput class, used