You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Jesse Kuhnert <jk...@gmail.com> on 2006/01/16 17:30:08 UTC
Demo application
I think I'm ready to start doing actual development work and was wondering
what the best way to go about developing an example app would be? Should I
just start enhancing the workbench or create a brand new example? If brand
new, did anyone have any ideas on what it should do ? ;)
It would also be nice to be able to reference running demo's in the
component documentation the way that tacos is doing, but I'm not sure if
javaforge will be able to handle that kind of load, I guess we'll find out ?
Does this sound like a bad idea?
jesse
Re: Demo application
Posted by Howard Lewis Ship <hl...@gmail.com>.
I've found that Tapestry has improved the most when I've worked on a
real project and hit bugs and annoyances. I'd say, go do a realistic
application, one with some database access in it ... but a lot of Ajax
(that is your focus, no?). Try and keep a diary of your pain points so
that we can address those for 4.1.
On 1/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> I should say that this demo application is intended to be completely third
> party independant, not an example of showing hibernate or anything else.
> Just something for me to test and assert how easy the changes I'm making are
> to implement in an actual application.
>
>
> On 1/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> >
> > So, definitely a bad idea or definitely a good idea? ;)
> >
> > On 1/16/06, Massimo Lusetti <ml...@gmail.com> wrote:
> > >
> > > On 1/16/06, Jesse Kuhnert <jkuhnert@gmail.com > wrote:
> > >
> > > > Does this sound like a bad idea?
> > >
> > > Definetly. I also read from Howard's blog
> > > http://howardlewisship.com/blog/2006/01/maven-and-missing-java-transaction-api.html
> > >
> > > he is doing some work on the same topic so i guess it's worthwhile to
> > > join the effort, don't you?
> > >
> > > Besides I've started the same thing to help the tapestry spreading
> > > inside my organization, doing that i've started from hivetranse for
> > > the hibernate interface layer.
> > >
> > > --
> > > Massimo
> > > http://meridio.blogspot.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> > >
> > >
> >
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Demo application
Posted by Jesse Kuhnert <jk...@gmail.com>.
I should say that this demo application is intended to be completely third
party independant, not an example of showing hibernate or anything else.
Just something for me to test and assert how easy the changes I'm making are
to implement in an actual application.
On 1/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> So, definitely a bad idea or definitely a good idea? ;)
>
> On 1/16/06, Massimo Lusetti <ml...@gmail.com> wrote:
> >
> > On 1/16/06, Jesse Kuhnert <jkuhnert@gmail.com > wrote:
> >
> > > Does this sound like a bad idea?
> >
> > Definetly. I also read from Howard's blog
> > http://howardlewisship.com/blog/2006/01/maven-and-missing-java-transaction-api.html
> >
> > he is doing some work on the same topic so i guess it's worthwhile to
> > join the effort, don't you?
> >
> > Besides I've started the same thing to help the tapestry spreading
> > inside my organization, doing that i've started from hivetranse for
> > the hibernate interface layer.
> >
> > --
> > Massimo
> > http://meridio.blogspot.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
> >
> >
>
Re: Demo application
Posted by Massimo Lusetti <ml...@gmail.com>.
On 1/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> So, definitely a bad idea or definitely a good idea? ;)
I mean :) ... a good idea... but better would be to have your effort
together with Howard's ones. Don't you think so?
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Demo application
Posted by Jesse Kuhnert <jk...@gmail.com>.
So, definitely a bad idea or definitely a good idea? ;)
On 1/16/06, Massimo Lusetti <ml...@gmail.com> wrote:
>
> On 1/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
>
> > Does this sound like a bad idea?
>
> Definetly. I also read from Howard's blog
>
> http://howardlewisship.com/blog/2006/01/maven-and-missing-java-transaction-api.html
> he is doing some work on the same topic so i guess it's worthwhile to
> join the effort, don't you?
>
> Besides I've started the same thing to help the tapestry spreading
> inside my organization, doing that i've started from hivetranse for
> the hibernate interface layer.
>
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
Re: Demo application
Posted by Massimo Lusetti <ml...@gmail.com>.
On 1/16/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> Does this sound like a bad idea?
Definetly. I also read from Howard's blog
http://howardlewisship.com/blog/2006/01/maven-and-missing-java-transaction-api.html
he is doing some work on the same topic so i guess it's worthwhile to
join the effort, don't you?
Besides I've started the same thing to help the tapestry spreading
inside my organization, doing that i've started from hivetranse for
the hibernate interface layer.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Demo application
Posted by Leonardo Quijano Vincenzi <le...@dtqsoftware.com>.
Jesse Kuhnert wrote:
> I think I'm ready to start doing actual development work and was wondering
> what the best way to go about developing an example app would be? Should I
> just start enhancing the workbench or create a brand new example? If brand
> new, did anyone have any ideas on what it should do ? ;)
>
> It would also be nice to be able to reference running demo's in the
> component documentation the way that tacos is doing, but I'm not sure if
> javaforge will be able to handle that kind of load, I guess we'll find out ?
> Does this sound like a bad idea?
>
> jesse
>
>
Jesse, IMO it'd be better to continue work in documentation (in the form
of user guides, developer guides, etc) than to do
yet-another-example-application - as much fun those could be.
Besides, there's one thing that I'm actually looking forward to in
Tapestry 4.1, and that's component contributions. As my Tacos lists's
comment was saying, I'm trying to implement a mask edit solution using
Dojo's event connect and render contributions (as in the AjaxEventSubmit
component). But that Tacos-specific render contribution could go as a
standard way of "decorating" base components.
Some things I think should be done using decorators (I know, some of
them already are, but the mechanism is not very clear to me - there's no
developer's documentation):
- Validation (Tacos's is more dynamic but a bit more stiff, Tapestry's
doesn't use standard Javascript libraries, that bugs me)
- Formatting (There's a pluggable implementation already, right?)
- Ajax Events (Already implemented in Tacos)
- DHTML Events (With this I'm talking about pure client-side events,
such as disabling a field when another one is selected, etc).
- Masks: That's DHTML but it's a specific concern of mine so I put that
separately :P.
etc....
So, this is a suggestion of where I think effort could be better spent.
I know I'll actually be implementing the mask solution ASAP.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org