You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Twan Kogels <tw...@twansoft.com> on 2004/01/05 22:25:47 UTC

[Jelly] (Swing) Roadmap?

Hello,

Today i was looking for a framework to make it easier to develop swing 
gui's and which seperates the gui from the logic in a swing application. 
The swing application will consist of about 90 screens (dialogs and panels) 
and may be converted in a couple of years to a webapplication (that's why 
seperation of view and logic is quit important).

After scanning through Lexor (gpl), SwingML (gpl) and a couple of projects 
which did seam quit dead i bumped against jelly-swing. I read through the 
javadoc and found that only a subset of the swing library is complete.

Is there a roadmap or a planning for jelly-swing?

Thanks,
Twan Kogels



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Re: [Jelly] (Swing) Roadmap?

Posted by Paul Libbrecht <pa...@activemath.org>.
To be more precise, the documentation issue of Swing tag-libraries is a 
known issue, namely JELLY-11:
	http://jira.codehaus.org/secure/ViewIssue.jspa?key=JELLY-11
The problem is that using XDoclet for these purposes is a bit too hard 
thus far.
The other issue is a relation to the converters: when a component-tag 
encounters an attribute, it will try to find the setter method having 
at hand the possible converters (which should include data objects like 
Dimension, Color, or Font)... and you need to document this...
The current jellydoc mechanism hasn't managed this.
And I know there are other taglibs that have this problem.

Paul

>> In response to your first message, only a fraction of
>> JellySwing's tags are documented in the JavaDocs. Most
>> of the JComponent-based tags are implemented by
>> delegating to factory objects defined within the
>> SwingTagLibrary class. Look at the source for
>> org.apache.commons.jelly.tags.swing.SwingTagLibrary to
>> all of the tags.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Re: [Jelly] (Swing) Roadmap?

Posted by Twan Kogels <tw...@twansoft.com>.
Hello Serge,

That's good news, i've just retreived the last cvs package from the server 
and managed to build and run the supplied examples. Next i'm taking a 
better look at the source including your suggestion.

Greetings,
Twan

At 22:21 06-1-2004, you wrote:
>Twan,
>In response to your first message, only a fraction of
>JellySwing's tags are documented in the JavaDocs. Most
>of the JComponent-based tags are implemented by
>delegating to factory objects defined within the
>SwingTagLibrary class. Look at the source for
>org.apache.commons.jelly.tags.swing.SwingTagLibrary to
>all of the tags.
>
>I believe you'll find most of what you could need.
>Serge Schremmer
>
>--- Twan Kogels <tw...@twansoft.com> wrote:
> > Hello John,
> >
> > Thanks for the reply, i would be more than happy the
> > get view at your
> > framework! It would be nice if you could post a
> > message when you upload it
> > to sourceforge, maybe you could also post a message
> > on javalobby's product
> > announcements, that's a nice place to get a global
> > look of java related
> > releases (most small, but sometimes quite
> > interesting).
> >
> > Greetings,
> > Twan
> >
> > At 04:28 06-1-2004, you wrote:
> > >Hi Twan,
> > >
> > >I am currently working on a GUI project called TS
> > Client which I will post
> > >on Source Forge within a week or 2.
> > >This GUI project is not based on Jelly, but has
> > some features that may
> > >save some hours coding.
> > >
> > >The system is has a MVC pattern with the following
> > features:
> > >- 100% Java using Swing and McKoi as database
> > server
> > >- System can run in server mode and in embedded
> > mode, like for example MS
> > >Access.
> > >- Generic controller handles 90% of all database
> > queries
> > >- Specific controller for join queries
> > >- GenericTableModel is used for all tables
> > >         This saves a lot of manual coding as it
> > can be re-used for all
> > > tables.
> > >         Has complete separation of colums shown
> > and data stored in table.
> > >- Forms have Search > Table > Form structure
> > consistently throughout the
> > >system.
> > >         Creating new forms takes a few hours
> > including testing.
> > >- Jakarta DBCP for connection pooling
> > >- Jakarta Db Utils for returning resultset as a
> > collection, like Map or List.
> > >         This keeps clode clean as SQL code is
> > encapsulated in DB Utils.
> > >
> > >With this framework in place creating new forms is
> > fast and easy.
> > >In virtaully all cases you do not need to write SQL
> > statements as this can
> > >be handled by the generic controller.
> > >Even the specific controller can be turned into
> > generic code using meta data.
> > >However in this case I prefered speed over
> > abstraction.
> > >The project does not use XML to generate the view.
> > >However in how many cases do you want to re-use
> > your GUI view for a web page.
> > >This looks very unlikely to me as web pages simply
> > have other requirements
> > >than GUI forms.
> > >Just let me know if you are interested and I will
> > post a message when the
> > >project is life at Source Forge.
> > >
> > >--
> > >John Zoetebier
> > >Web site: http://www.transparent.co.nz
> > >
> > >On Mon, 05 Jan 2004 22:25:47 +0100, Twan Kogels
> > <tw...@twansoft.com> wrote:
> > >
> > >>Hello,
> > >>
> > >>Today i was looking for a framework to make it
> > easier to develop swing
> > >>gui's and which seperates the gui from the logic
> > in a swing application.
> > >>The swing application will consist of about 90
> > screens (dialogs and
> > >>panels) and may be converted in a couple of years
> > to a webapplication
> > >>(that's why seperation of view and logic is quit
> > important).
> > >>
> > >>After scanning through Lexor (gpl), SwingML (gpl)
> > and a couple of
> > >>projects which did seam quit dead i bumped against
> > jelly-swing. I read
> > >>through the javadoc and found that only a subset
> > of the swing library is
> > >>complete.
> > >>
> > >>Is there a roadmap or a planning for jelly-swing?
> > >
> > >
> > >
> > >
> > >
> > >
> > >>
> > >>Thanks,
> > >>Twan Kogels
> > >>
> > >>
> > >>
> >
> >>---------------------------------------------------------------------
> > >>To unsubscribe, e-mail:
> > commons-user-unsubscribe@jakarta.apache.org
> > >>For additional commands, e-mail:
> > commons-user-help@jakarta.apache.org
> > >
> > >
> > >
> >
> >---------------------------------------------------------------------
> > >To unsubscribe, e-mail:
> > commons-user-unsubscribe@jakarta.apache.org
> > >For additional commands, e-mail:
> > commons-user-help@jakarta.apache.org
> > >
> > >
> >
> >
> >
> >
>---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > commons-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> > commons-user-help@jakarta.apache.org
> >
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
>http://hotjobs.sweepstakes.yahoo.com/signingbonus
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Re: [Jelly] (Swing) Roadmap?

Posted by S Schrem <ss...@yahoo.com>.
Twan,
In response to your first message, only a fraction of
JellySwing's tags are documented in the JavaDocs. Most
of the JComponent-based tags are implemented by
delegating to factory objects defined within the
SwingTagLibrary class. Look at the source for
org.apache.commons.jelly.tags.swing.SwingTagLibrary to
all of the tags.

I believe you'll find most of what you could need.
Serge Schremmer

--- Twan Kogels <tw...@twansoft.com> wrote:
> Hello John,
> 
> Thanks for the reply, i would be more than happy the
> get view at your 
> framework! It would be nice if you could post a
> message when you upload it 
> to sourceforge, maybe you could also post a message
> on javalobby's product 
> announcements, that's a nice place to get a global
> look of java related 
> releases (most small, but sometimes quite
> interesting).
> 
> Greetings,
> Twan
> 
> At 04:28 06-1-2004, you wrote:
> >Hi Twan,
> >
> >I am currently working on a GUI project called TS
> Client which I will post 
> >on Source Forge within a week or 2.
> >This GUI project is not based on Jelly, but has
> some features that may 
> >save some hours coding.
> >
> >The system is has a MVC pattern with the following
> features:
> >- 100% Java using Swing and McKoi as database
> server
> >- System can run in server mode and in embedded
> mode, like for example MS 
> >Access.
> >- Generic controller handles 90% of all database
> queries
> >- Specific controller for join queries
> >- GenericTableModel is used for all tables
> >         This saves a lot of manual coding as it
> can be re-used for all 
> > tables.
> >         Has complete separation of colums shown
> and data stored in table.
> >- Forms have Search > Table > Form structure
> consistently throughout the 
> >system.
> >         Creating new forms takes a few hours
> including testing.
> >- Jakarta DBCP for connection pooling
> >- Jakarta Db Utils for returning resultset as a
> collection, like Map or List.
> >         This keeps clode clean as SQL code is
> encapsulated in DB Utils.
> >
> >With this framework in place creating new forms is
> fast and easy.
> >In virtaully all cases you do not need to write SQL
> statements as this can 
> >be handled by the generic controller.
> >Even the specific controller can be turned into
> generic code using meta data.
> >However in this case I prefered speed over
> abstraction.
> >The project does not use XML to generate the view.
> >However in how many cases do you want to re-use
> your GUI view for a web page.
> >This looks very unlikely to me as web pages simply
> have other requirements 
> >than GUI forms.
> >Just let me know if you are interested and I will
> post a message when the 
> >project is life at Source Forge.
> >
> >--
> >John Zoetebier
> >Web site: http://www.transparent.co.nz
> >
> >On Mon, 05 Jan 2004 22:25:47 +0100, Twan Kogels
> <tw...@twansoft.com> wrote:
> >
> >>Hello,
> >>
> >>Today i was looking for a framework to make it
> easier to develop swing 
> >>gui's and which seperates the gui from the logic
> in a swing application. 
> >>The swing application will consist of about 90
> screens (dialogs and 
> >>panels) and may be converted in a couple of years
> to a webapplication 
> >>(that's why seperation of view and logic is quit
> important).
> >>
> >>After scanning through Lexor (gpl), SwingML (gpl)
> and a couple of 
> >>projects which did seam quit dead i bumped against
> jelly-swing. I read 
> >>through the javadoc and found that only a subset
> of the swing library is 
> >>complete.
> >>
> >>Is there a roadmap or a planning for jelly-swing?
> >
> >
> >
> >
> >
> >
> >>
> >>Thanks,
> >>Twan Kogels
> >>
> >>
> >>
>
>>---------------------------------------------------------------------
> >>To unsubscribe, e-mail:
> commons-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail:
> commons-user-help@jakarta.apache.org
> >
> >
> >
>
>---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> commons-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail:
> commons-user-help@jakarta.apache.org
> >
> >
> 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> commons-user-help@jakarta.apache.org
> 



__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Re: [Jelly] (Swing) Roadmap?

Posted by Twan Kogels <tw...@twansoft.com>.
Hello John,

Thanks for the reply, i would be more than happy the get view at your 
framework! It would be nice if you could post a message when you upload it 
to sourceforge, maybe you could also post a message on javalobby's product 
announcements, that's a nice place to get a global look of java related 
releases (most small, but sometimes quite interesting).

Greetings,
Twan

At 04:28 06-1-2004, you wrote:
>Hi Twan,
>
>I am currently working on a GUI project called TS Client which I will post 
>on Source Forge within a week or 2.
>This GUI project is not based on Jelly, but has some features that may 
>save some hours coding.
>
>The system is has a MVC pattern with the following features:
>- 100% Java using Swing and McKoi as database server
>- System can run in server mode and in embedded mode, like for example MS 
>Access.
>- Generic controller handles 90% of all database queries
>- Specific controller for join queries
>- GenericTableModel is used for all tables
>         This saves a lot of manual coding as it can be re-used for all 
> tables.
>         Has complete separation of colums shown and data stored in table.
>- Forms have Search > Table > Form structure consistently throughout the 
>system.
>         Creating new forms takes a few hours including testing.
>- Jakarta DBCP for connection pooling
>- Jakarta Db Utils for returning resultset as a collection, like Map or List.
>         This keeps clode clean as SQL code is encapsulated in DB Utils.
>
>With this framework in place creating new forms is fast and easy.
>In virtaully all cases you do not need to write SQL statements as this can 
>be handled by the generic controller.
>Even the specific controller can be turned into generic code using meta data.
>However in this case I prefered speed over abstraction.
>The project does not use XML to generate the view.
>However in how many cases do you want to re-use your GUI view for a web page.
>This looks very unlikely to me as web pages simply have other requirements 
>than GUI forms.
>Just let me know if you are interested and I will post a message when the 
>project is life at Source Forge.
>
>--
>John Zoetebier
>Web site: http://www.transparent.co.nz
>
>On Mon, 05 Jan 2004 22:25:47 +0100, Twan Kogels <tw...@twansoft.com> wrote:
>
>>Hello,
>>
>>Today i was looking for a framework to make it easier to develop swing 
>>gui's and which seperates the gui from the logic in a swing application. 
>>The swing application will consist of about 90 screens (dialogs and 
>>panels) and may be converted in a couple of years to a webapplication 
>>(that's why seperation of view and logic is quit important).
>>
>>After scanning through Lexor (gpl), SwingML (gpl) and a couple of 
>>projects which did seam quit dead i bumped against jelly-swing. I read 
>>through the javadoc and found that only a subset of the swing library is 
>>complete.
>>
>>Is there a roadmap or a planning for jelly-swing?
>
>
>
>
>
>
>>
>>Thanks,
>>Twan Kogels
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org


Re: [Jelly] (Swing) Roadmap?

Posted by John Zoetebier <jo...@transparent.co.nz>.
Hi Twan,

I am currently working on a GUI project called TS Client which I will post 
on Source Forge within a week or 2.
This GUI project is not based on Jelly, but has some features that may 
save some hours coding.

The system is has a MVC pattern with the following features:
- 100% Java using Swing and McKoi as database server
- System can run in server mode and in embedded mode, like for example MS 
Access.
- Generic controller handles 90% of all database queries
- Specific controller for join queries
- GenericTableModel is used for all tables
	This saves a lot of manual coding as it can be re-used for all tables.
	Has complete separation of colums shown and data stored in table.
- Forms have Search > Table > Form structure consistently throughout the 
system.
	Creating new forms takes a few hours including testing.
- Jakarta DBCP for connection pooling
- Jakarta Db Utils for returning resultset as a collection, like Map or 
List.
	This keeps clode clean as SQL code is encapsulated in DB Utils.

With this framework in place creating new forms is fast and easy.
In virtaully all cases you do not need to write SQL statements as this can 
be handled by the generic controller.
Even the specific controller can be turned into generic code using meta 
data.
However in this case I prefered speed over abstraction.
The project does not use XML to generate the view.
However in how many cases do you want to re-use your GUI view for a web 
page.
This looks very unlikely to me as web pages simply have other requirements 
than GUI forms.
Just let me know if you are interested and I will post a message when the 
project is life at Source Forge.

-- 
John Zoetebier
Web site: http://www.transparent.co.nz

On Mon, 05 Jan 2004 22:25:47 +0100, Twan Kogels <tw...@twansoft.com> wrote:

> Hello,
>
> Today i was looking for a framework to make it easier to develop swing 
> gui's and which seperates the gui from the logic in a swing application. 
> The swing application will consist of about 90 screens (dialogs and 
> panels) and may be converted in a couple of years to a webapplication 
> (that's why seperation of view and logic is quit important).
>
> After scanning through Lexor (gpl), SwingML (gpl) and a couple of 
> projects which did seam quit dead i bumped against jelly-swing. I read 
> through the javadoc and found that only a subset of the swing library is 
> complete.
>
> Is there a roadmap or a planning for jelly-swing?






>
> Thanks,
> Twan Kogels
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org