Yeah, that would be great. Better than that, we could have a alpha release of
Jelly Swing with some fixes until a beta or final release is available. How
does that sound ?
Dario
-----Original Message-----
From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
Sent: Tue 11/8/2005 8:14 AM
To: Jakarta Commons Users List
Cc:
Subject: Re: [jelly] swing example
Hans,
why not produce a snapshot ??
Something like maven jar:deploy-snapshot, I think... need to have
ssh-key-based access to cvs.apapache.org.
paul
Le 8 nov. 05, à 03:48, Hans Gilde a écrit :
> Uh, oh, sorry. I was using the trunk. Yeah... version 1.0 Action is
> completely and totally broken. Can't possibly work right. Paul fixed
> this in
> the trunk.
>
> If you can get it through SVN, trunk/HEAD seems to be working well.
> Otherwise you'll have to wait for a 1.1, which will also include
> CardLayout.
> :)
>
> I'm committing the test to prevent something like this in the future.
>
> This would definitely be something to go in the 1.1 release notes...
> Action
> tag works now.
>
> -----Original Message-----
> From: Dário Luís Coneglian Oliveros [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 07, 2005 8:19 AM
> To: Jakarta Commons Users List
> Subject: RE: [jelly] swing example
>
> Hi Hans,
>
> I was able to reproduce the problem with the information provided by
> you.
> After I executed 'maven test', I got a failure in the TestActionTag.
> If I
> comment out the test tag from actionTagTest.jelly, then the test
> passes.
> FYI, I got the Jelly Swing code from subversion
> (http://svn.apache.org/repos/asf/jakarta/commons/proper/jelly/tags/
> COMMONS-J
> ELLY-SWING-1_0)
> Any clues ?
>
> Thanks,
> Dario
>
> -----Original Message-----
> From: Hans Gilde [mailto:[EMAIL PROTECTED]
> Sent: Sun 11/6/2005 8:32 PM
> To: 'Jakarta Commons Users List'
> Cc:
> Subject: RE: [jelly] swing example
>
>
>
> Hmm, this is interesting... it doesn't work this way for me.
Also,
> looking
> at the code, I don't see how it could fail.
>
> Could you set up a test in the Swing tag directory that
demonstrates
> the
> issue?
>
> All you have to do is add a test case called TestXYZ in the
Jelly
> test
> directory, that extends BaseJellyTest and uses some Jelly
script in
> that
> same package. Then, you execute it from "maven test" in the
root of
> the
> Swing tag directory.
>
> I used this test tag:
>
> /*
> * Created on Nov 6, 2005
> *
> */
> package org.apache.commons.jelly.swing;
>
> import org.apache.commons.jelly.XMLOutput;
> import org.apache.commons.jelly.core.BaseJellyTest;
>
> public class TestActionTag extends BaseJellyTest {
>
> public TestActionTag(String name) {
> super(name);
> }
>
> public void testActionTagExecution() throws Exception {
> setUpScript("actionTagTest.jelly");
> getJelly().compileScript().run(getJellyContext(),
> XMLOutput.createXMLOutput(System.out));
> }
>
> }
>
> actionTagTest.jelly -----------------------------
> <?xml version="1.0"?>
> <j:jelly xmlns:j="jelly:core" xmlns:sw="jelly:swing"
> xmlns:log="jelly:log"
> xmlns:test="jelly:junit">
> <sw:action var="exitAction" name="Exit">
> <test:fail>Action tag was executed
immediately.</test:fail>
> </sw:action>
> <sw:frame title="Jelly Swing" var="frame" location="100,100"
> size="450,300">
> </sw:frame>
> ${frame.show()}
> </j:jelly>
>
> -----Original Message-----
> From: Dário Luís Coneglian Oliveros [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 06, 2005 4:44 PM
> To: Jakarta Commons Users List
> Subject: RE: [jelly] swing example
>
> Hi Hans,
>
> I was able to reproduce the problem in a very simple Jelly
script.
> See it
> below:
>
> <?xml version="1.0"?>
> <j:jelly xmlns:j="jelly:core" xmlns:sw="jelly:swing"
> xmlns:log="jelly:log">
> <sw:action var="exitAction" name="Exit">
> <log:info>EXIT action!</log:info>
> </sw:action>
> <sw:frame title="Jelly Swing" var="frame" location="100,100"
> size="450,300">
> </sw:frame>
> ${frame.show()}
> </j:jelly>
>
> Whenever I run this script, the action is always executed in the
> first
> place.
> Any help will be appreciated.
> Thanks,
> Dario
>
> -----Original Message-----
> From: Hans Gilde [mailto:[EMAIL PROTECTED]
> Sent: Sun 11/6/2005 4:26 AM
> To: 'Jakarta Commons Users List'
> Cc:
> Subject: RE: [jelly] swing example
>
>
>
> I cannot reproduce this behavior of having action tags
> executed
> immediately.
> I've checked in a test for this behavior as well (which
> passes).
>
> My guess is that you're defining the action tag
incorrectly,
> could
> you
> attach a Jelly snippet that reproduces the problem?
>
> -----Original Message-----
> From: Dário Luís Coneglian Oliveros
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 03, 2005 3:36 PM
> To: Jakarta Commons Users List
> Subject: RE: [jelly] swing example
>
> Hi Paul,
>
> Thanks for the tips.
> However I am still having problem getting the swing to
work.
> :-(
> I tried to use the code snippet about the System.exit,
but
> it didn´t
> work.
> Regarding the CardLayout, I couldn´t find its tag in the
> jelly swing
> documentation. Do you happen to have an example about
how to
> use it
> ?
>
> One thing I´ve noticed when using Jelly Swing is that
any
> action you
> define
> in the jelly script is always executed as of the script
> startup,
> even though
> an event is not triggered yet. Do you know if this is an
> expected
> behaviour
> ? I thought any action would be executed only if an
event
> associated
> to it
> was activated.
>
> Regarding your reloadable strategy, I think it would be
> great to
> have
> something like that. We can discuss it later if you
wish.
>
> Thanks a bunch.
> Dario
>
> -----Original Message-----
> From: Paul Libbrecht [mailto:[EMAIL PROTECTED]
> Sent: quinta-feira, 3 de novembro de 2005 10:15
> To: Jakarta Commons Users List
> Subject: Re: [jelly] swing example
>
>
>
>
>
> Le 3 nov. 05, à 11:46, Dário Luís Coneglian Oliveros a
écrit
> :
> > I was wondering if anyone could help me get some of my
> Jelly Swing
> > questions answered.
> >
> > 1) Considering my swing appl has two menu items and
one
> main
> panel, is
> > it possible to change the panel content according to
the
> menu item
> > selected ?
>
> You might give a try with a CardLayout, or ?
>
> > 3) Is there any command to quit a Jelly Swing
application
> ?
> Couldn´t
> > find any sample on the web that does that.
>
>
> Would the following work ?
> <j:invokeStatic className="java.lang.System"
method="exit">
> <arg>0</arg>
> </j:invokeStatic>
> There is also a quit in the swing-demo.
>
> > 2) Let´s say a panel has a text field and a button.
When
> pressing
> the
> > button, a request is sent with the text field value.
How
> can I
> show
> > the response in the panel ?
>
> This is not easy, I feel. I've been working on
reloadable
> swing
> components for a while where a script would be run
again in
> order to
> populate the pane but I didn't come with a final
solution.
> I know that you can get a similar effect by doing a bit
more
> method
> invocations and variable assignments.
> ${pane.remove(xx)}
>
> My intent for reloadable component is, indeed, to have
each
> component
> behave as a browser frame and request to re-run a
> population-script
> along a target.
>
> Just thinking out loud, I seem to encounter that the
> following might
> be
> enough:
>
> <sw:frame>
> blabla
> <sw:panel var="myList"/>
> </sw:frame>
>
> and somewhere else (e.g. as a child of action:
>
> <sw:target name="panel">
> <sw:label>casdasa</sw:label>
> ....
> </sw:target>
>
> That is, we would introduce a "target" element that
would
> allow an
> component to be cleared than repopulated by its
content...
> This seems suddenly pretty easy to implement compared
to the
> "reloadable" kind of things I expected. Would it fit
your
> task ?
>
> paul
>
>
>
> ---------------------------------------------------------------------
> 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]
>
>
>
>
> ---------------------------------------------------------------------
> 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]
>
>
>
>
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
