You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2007/07/25 15:55:31 UTC
[PASS] Dan Adams as Tapestry Committer
I've been following Dan Adams' work for a while; he's done some
impressive things with Tapestry 4 and has really been going to town on
Tapestry 5. Based on everything I've seen of his work (I've visited
him at iFactory a couple of times that I've been in Boston), I'm
convinced he would be a valuable asset to Tapestry: he's organized and
disciplined and really groks the details of Tapestry IoC and the
component model.
This is a vote to grant him committer access to the Tapestry project.
Vote to run for a week. Requirements: at least 3 +1's, no -1's.
Howard M. Lewis Ship: +1 (binding)
Daniel Gredler: +1 (binding)
Paul Ferraro: +1 (binding)
Jesse Kuhnert: +1 (binding)
Marcus Schulte: +1 (binding)
Andreas Andreou: +1 (binding)
David Solis: +1 (binding)
Ben Dotte: +1 (binding)
Non-binding votes:
Cyrille : +1
Andrea Chiumenti: +1 (non binding)
Filip S. Adamsen: +1 (non-binding)
Nick Westgate: +1 (non-binding)
Davor Hrg +1 (non-binding)
Massimo Lusetti: +1 (non-binding)
Robert Zeigler: +1 (non-binding)
Dan ... get started on that CLA: Here's some information you'll need:
http://apache.org/dev/pmc.html#newcommitter
Congrats!
Re: [PASS] Dan Adams as Tapestry Committer
Posted by #Cyrille37# <cy...@gmail.com>.
A really nice speech Dan !
T5 's future smell good ;-)
Cyrille
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Jesse Kuhnert <jk...@gmail.com>.
That's all controllable via various modes you can set on the context of the
scripts execution - so it's fairly reliable once you set that part up right.
On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
>
> hmm. interesting. actually i think the biggest problem i've seen with it
> is that it treats javascript like a real language so it's not as
> forgiving with bad javascript as a browser might be. but i'll have to
> look into that.
>
> On Thu, 2007-07-26 at 15:13 -0400, Jesse Kuhnert wrote:
> > The issues with javascript in HtmlUnit could probably be fixed by using
> some
> > of the new but as yet not announced rhino implementations floating
> around:
> >
> > ftp://ftp.mozilla.org/pub/mozilla.org/js/
> >
> > I've heard that people are able to do full dom document operations and
> stuff
> > in it now without very much work.
> >
> > I'm assuming most of the new stuff is related to compatibility with js2
> as
> > well as whatever those crazy freaks at google are doing to it.
> >
> > On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
> > >
> > > The htmlunit stuff is still pretty experimental and I've speced out
> what
> > > it might look like but haven't done any heavy development. Currently
> we
> > > have a number of integration tests that use htmlunit (which works
> great
> > > except for javascript heavy stuff). The idea is to re-implement the
> > > piece of htmlunit that does http connections so that it communicates
> > > with PageTester rather than making http requests to a server. Then
> > > rather than having to translate html text into a htmlunit dom it would
> > > convert the tapestry dom into the htmlunit dom. Events in htmlunit
> such
> > > as link.click() would actually result in calling pageTester.clickLink
> ().
> > >
> > > I've looked into it a bit and it seems pretty feasible (you basically
> > > just implement WebConnection). I'll probably do this so that we can
> > > integration test our CMS apps from within unit tests without having to
> > > separately start the environment but that won't be for a little while.
> > >
> > > On Thu, 2007-07-26 at 10:00 -0400, D&J Gredler wrote:
> > > > Hi Dan,
> > > >
> > > > Congrats! I like the @Once idea, that'll be really cool.
> > > >
> > > > Out of curiosity, can you elaborate on the HtmlUnit integration? How
> has
> > > > that gone?
> > > >
> > > > Take care,
> > > >
> > > > Daniel
> > > >
> > > >
> > > > On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
> > > > >
> > > > > Hey guys. Good to be joining the team. Here's some background on
> how
> > > > > I've been using Tapestry at my company (Interactive Factory):
> > > > >
> > > > > When I first came to our company just over 2 years ago we were
> using
> > > > > what was essentially a home-grown Struts designed such that it was
> > > > > Windows-only (despite it's being Java). After evaluating a number
> of
> > > web
> > > > > frameworks (and having worked with JSF at Sun) I promptly
> discarded
> > > our
> > > > > current code base and started afresh with T4 (and a number of
> other
> > > > > frameworks such as Hibernate and Spring). The result was, as
> expected,
> > > > > awesome. What I created for one project was then used on another,
> > > pulled
> > > > > out into a central library of components, and is now the basis for
> > > > > essentially all our projects, both CMS and custom publishing,
> ranging
> > > > > from the fairly simple to to incredibly complex.
> > > > >
> > > > > The most unique usage of Tapestry I've had is an internal CMS
> > > > > rapid-prototyping tool called ProtoCMS. It uses a simple XML CMS
> > > > > definition and an object model stored as on ASO to render entire
> > > > > interfaces of pages and components on the fly. This project is
> proof
> > > of
> > > > > Tapestry's capabilities and that component-based development
> works. In
> > > > > as little as 30 minutes you can create a functional CMS prototype
> for
> > > > > use in sales presentations or project specification. Prototypes
> are
> > > also
> > > > > easily editable through a javascript-based, ajax-enabled XML
> editor
> > > and
> > > > > can be skinned custom to each client. Since it is a prototyping
> tool,
> > > it
> > > > > allows creating new, re-usable components and functionality via a
> > > > > templating language.
> > > > >
> > > > > I'm now looking forward to the next major release of our internal
> > > > > libraries based on T5 which is driving all of the tickets and
> patches
> > > > > I've submitted as well as my becoming a committer. I am aiming
> pretty
> > > > > high with the features in this release so it's really exercising
> what
> > > T5
> > > > > can do. Some notable things I'm looking forward to or have been
> > > working
> > > > > on:
> > > > >
> > > > > - Enhancement of tapestry-hibernate to be more configurable and
> more
> > > > > usable in both small and complex systems
> > > > >
> > > > > - Inspired by T5 I've been intentionally pushing the limits of
> what
> > > you
> > > > > can do with PageTester including: integration with HtmlUnit,
> running
> > > > > Jetty in-process so your tests and application run in the same
> JVM,
> > > and
> > > > > automatic start-up of HSLQDB including creation of tables for
> > > Hibernate
> > > > > entities.
> > > > >
> > > > > - Other possibly niceties such as one-off form validation and the
> > > @Once
> > > > > annotation for caching method results optionally dependent on a
> > > binding.
> > > > >
> > > > > I'm looking forward to working with all of you and I can't wait to
> see
> > > > > just how good T5 is going to be.
> > > > >
> > > > > On Thu, 2007-07-26 at 13:37 +0900, Nick Westgate wrote:
> > > > > > Yeah, congrats Dan.
> > > > > >
> > > > > > Dan has logged a lot of JIRA issues, so hopefully we can look
> > > > > > forward to some stuff that Howard doesn't have time for. ;-)
> > > > > >
> > > > > > Cheers,
> > > > > > Nick.
> > > > > >
> > > > > >
> > > > > > Daniel Jue wrote:
> > > > > > > Congrats Dan, I can't wait to see some impressive stuff! =)
> > > > > > >
> > > > > > > Can you tell some features we can look forward to?
> > > > > > >
> > > > > > >
> > > > > > >> Dan ... get started on that CLA: Here's some information
> you'll
> > > > > need:
> > > > > > >>
> > > > > > >> http://apache.org/dev/pmc.html#newcommitter
> > > > > > >>
> > > > > > >> Congrats!
> > > > > > >>
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > > >
> > > > > --
> > > > > Dan Adams
> > > > > Senior Software Engineer
> > > > > Interactive Factory
> > > > > 617.235.5857
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > --
> > > Dan Adams
> > > Senior Software Engineer
> > > Interactive Factory
> > > 617.235.5857
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> > >
> >
> >
> --
> Dan Adams
> Senior Software Engineer
> Interactive Factory
> 617.235.5857
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Dan Adams <da...@ifactory.com>.
hmm. interesting. actually i think the biggest problem i've seen with it
is that it treats javascript like a real language so it's not as
forgiving with bad javascript as a browser might be. but i'll have to
look into that.
On Thu, 2007-07-26 at 15:13 -0400, Jesse Kuhnert wrote:
> The issues with javascript in HtmlUnit could probably be fixed by using some
> of the new but as yet not announced rhino implementations floating around:
>
> ftp://ftp.mozilla.org/pub/mozilla.org/js/
>
> I've heard that people are able to do full dom document operations and stuff
> in it now without very much work.
>
> I'm assuming most of the new stuff is related to compatibility with js2 as
> well as whatever those crazy freaks at google are doing to it.
>
> On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
> >
> > The htmlunit stuff is still pretty experimental and I've speced out what
> > it might look like but haven't done any heavy development. Currently we
> > have a number of integration tests that use htmlunit (which works great
> > except for javascript heavy stuff). The idea is to re-implement the
> > piece of htmlunit that does http connections so that it communicates
> > with PageTester rather than making http requests to a server. Then
> > rather than having to translate html text into a htmlunit dom it would
> > convert the tapestry dom into the htmlunit dom. Events in htmlunit such
> > as link.click() would actually result in calling pageTester.clickLink().
> >
> > I've looked into it a bit and it seems pretty feasible (you basically
> > just implement WebConnection). I'll probably do this so that we can
> > integration test our CMS apps from within unit tests without having to
> > separately start the environment but that won't be for a little while.
> >
> > On Thu, 2007-07-26 at 10:00 -0400, D&J Gredler wrote:
> > > Hi Dan,
> > >
> > > Congrats! I like the @Once idea, that'll be really cool.
> > >
> > > Out of curiosity, can you elaborate on the HtmlUnit integration? How has
> > > that gone?
> > >
> > > Take care,
> > >
> > > Daniel
> > >
> > >
> > > On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
> > > >
> > > > Hey guys. Good to be joining the team. Here's some background on how
> > > > I've been using Tapestry at my company (Interactive Factory):
> > > >
> > > > When I first came to our company just over 2 years ago we were using
> > > > what was essentially a home-grown Struts designed such that it was
> > > > Windows-only (despite it's being Java). After evaluating a number of
> > web
> > > > frameworks (and having worked with JSF at Sun) I promptly discarded
> > our
> > > > current code base and started afresh with T4 (and a number of other
> > > > frameworks such as Hibernate and Spring). The result was, as expected,
> > > > awesome. What I created for one project was then used on another,
> > pulled
> > > > out into a central library of components, and is now the basis for
> > > > essentially all our projects, both CMS and custom publishing, ranging
> > > > from the fairly simple to to incredibly complex.
> > > >
> > > > The most unique usage of Tapestry I've had is an internal CMS
> > > > rapid-prototyping tool called ProtoCMS. It uses a simple XML CMS
> > > > definition and an object model stored as on ASO to render entire
> > > > interfaces of pages and components on the fly. This project is proof
> > of
> > > > Tapestry's capabilities and that component-based development works. In
> > > > as little as 30 minutes you can create a functional CMS prototype for
> > > > use in sales presentations or project specification. Prototypes are
> > also
> > > > easily editable through a javascript-based, ajax-enabled XML editor
> > and
> > > > can be skinned custom to each client. Since it is a prototyping tool,
> > it
> > > > allows creating new, re-usable components and functionality via a
> > > > templating language.
> > > >
> > > > I'm now looking forward to the next major release of our internal
> > > > libraries based on T5 which is driving all of the tickets and patches
> > > > I've submitted as well as my becoming a committer. I am aiming pretty
> > > > high with the features in this release so it's really exercising what
> > T5
> > > > can do. Some notable things I'm looking forward to or have been
> > working
> > > > on:
> > > >
> > > > - Enhancement of tapestry-hibernate to be more configurable and more
> > > > usable in both small and complex systems
> > > >
> > > > - Inspired by T5 I've been intentionally pushing the limits of what
> > you
> > > > can do with PageTester including: integration with HtmlUnit, running
> > > > Jetty in-process so your tests and application run in the same JVM,
> > and
> > > > automatic start-up of HSLQDB including creation of tables for
> > Hibernate
> > > > entities.
> > > >
> > > > - Other possibly niceties such as one-off form validation and the
> > @Once
> > > > annotation for caching method results optionally dependent on a
> > binding.
> > > >
> > > > I'm looking forward to working with all of you and I can't wait to see
> > > > just how good T5 is going to be.
> > > >
> > > > On Thu, 2007-07-26 at 13:37 +0900, Nick Westgate wrote:
> > > > > Yeah, congrats Dan.
> > > > >
> > > > > Dan has logged a lot of JIRA issues, so hopefully we can look
> > > > > forward to some stuff that Howard doesn't have time for. ;-)
> > > > >
> > > > > Cheers,
> > > > > Nick.
> > > > >
> > > > >
> > > > > Daniel Jue wrote:
> > > > > > Congrats Dan, I can't wait to see some impressive stuff! =)
> > > > > >
> > > > > > Can you tell some features we can look forward to?
> > > > > >
> > > > > >
> > > > > >> Dan ... get started on that CLA: Here's some information you'll
> > > > need:
> > > > > >>
> > > > > >> http://apache.org/dev/pmc.html#newcommitter
> > > > > >>
> > > > > >> Congrats!
> > > > > >>
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > > >
> > > > > >
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > >
> > > > --
> > > > Dan Adams
> > > > Senior Software Engineer
> > > > Interactive Factory
> > > > 617.235.5857
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > >
> > > >
> > >
> > >
> > --
> > Dan Adams
> > Senior Software Engineer
> > Interactive Factory
> > 617.235.5857
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
--
Dan Adams
Senior Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Jesse Kuhnert <jk...@gmail.com>.
The issues with javascript in HtmlUnit could probably be fixed by using some
of the new but as yet not announced rhino implementations floating around:
ftp://ftp.mozilla.org/pub/mozilla.org/js/
I've heard that people are able to do full dom document operations and stuff
in it now without very much work.
I'm assuming most of the new stuff is related to compatibility with js2 as
well as whatever those crazy freaks at google are doing to it.
On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
>
> The htmlunit stuff is still pretty experimental and I've speced out what
> it might look like but haven't done any heavy development. Currently we
> have a number of integration tests that use htmlunit (which works great
> except for javascript heavy stuff). The idea is to re-implement the
> piece of htmlunit that does http connections so that it communicates
> with PageTester rather than making http requests to a server. Then
> rather than having to translate html text into a htmlunit dom it would
> convert the tapestry dom into the htmlunit dom. Events in htmlunit such
> as link.click() would actually result in calling pageTester.clickLink().
>
> I've looked into it a bit and it seems pretty feasible (you basically
> just implement WebConnection). I'll probably do this so that we can
> integration test our CMS apps from within unit tests without having to
> separately start the environment but that won't be for a little while.
>
> On Thu, 2007-07-26 at 10:00 -0400, D&J Gredler wrote:
> > Hi Dan,
> >
> > Congrats! I like the @Once idea, that'll be really cool.
> >
> > Out of curiosity, can you elaborate on the HtmlUnit integration? How has
> > that gone?
> >
> > Take care,
> >
> > Daniel
> >
> >
> > On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
> > >
> > > Hey guys. Good to be joining the team. Here's some background on how
> > > I've been using Tapestry at my company (Interactive Factory):
> > >
> > > When I first came to our company just over 2 years ago we were using
> > > what was essentially a home-grown Struts designed such that it was
> > > Windows-only (despite it's being Java). After evaluating a number of
> web
> > > frameworks (and having worked with JSF at Sun) I promptly discarded
> our
> > > current code base and started afresh with T4 (and a number of other
> > > frameworks such as Hibernate and Spring). The result was, as expected,
> > > awesome. What I created for one project was then used on another,
> pulled
> > > out into a central library of components, and is now the basis for
> > > essentially all our projects, both CMS and custom publishing, ranging
> > > from the fairly simple to to incredibly complex.
> > >
> > > The most unique usage of Tapestry I've had is an internal CMS
> > > rapid-prototyping tool called ProtoCMS. It uses a simple XML CMS
> > > definition and an object model stored as on ASO to render entire
> > > interfaces of pages and components on the fly. This project is proof
> of
> > > Tapestry's capabilities and that component-based development works. In
> > > as little as 30 minutes you can create a functional CMS prototype for
> > > use in sales presentations or project specification. Prototypes are
> also
> > > easily editable through a javascript-based, ajax-enabled XML editor
> and
> > > can be skinned custom to each client. Since it is a prototyping tool,
> it
> > > allows creating new, re-usable components and functionality via a
> > > templating language.
> > >
> > > I'm now looking forward to the next major release of our internal
> > > libraries based on T5 which is driving all of the tickets and patches
> > > I've submitted as well as my becoming a committer. I am aiming pretty
> > > high with the features in this release so it's really exercising what
> T5
> > > can do. Some notable things I'm looking forward to or have been
> working
> > > on:
> > >
> > > - Enhancement of tapestry-hibernate to be more configurable and more
> > > usable in both small and complex systems
> > >
> > > - Inspired by T5 I've been intentionally pushing the limits of what
> you
> > > can do with PageTester including: integration with HtmlUnit, running
> > > Jetty in-process so your tests and application run in the same JVM,
> and
> > > automatic start-up of HSLQDB including creation of tables for
> Hibernate
> > > entities.
> > >
> > > - Other possibly niceties such as one-off form validation and the
> @Once
> > > annotation for caching method results optionally dependent on a
> binding.
> > >
> > > I'm looking forward to working with all of you and I can't wait to see
> > > just how good T5 is going to be.
> > >
> > > On Thu, 2007-07-26 at 13:37 +0900, Nick Westgate wrote:
> > > > Yeah, congrats Dan.
> > > >
> > > > Dan has logged a lot of JIRA issues, so hopefully we can look
> > > > forward to some stuff that Howard doesn't have time for. ;-)
> > > >
> > > > Cheers,
> > > > Nick.
> > > >
> > > >
> > > > Daniel Jue wrote:
> > > > > Congrats Dan, I can't wait to see some impressive stuff! =)
> > > > >
> > > > > Can you tell some features we can look forward to?
> > > > >
> > > > >
> > > > >> Dan ... get started on that CLA: Here's some information you'll
> > > need:
> > > > >>
> > > > >> http://apache.org/dev/pmc.html#newcommitter
> > > > >>
> > > > >> Congrats!
> > > > >>
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > > >
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > >
> > > --
> > > Dan Adams
> > > Senior Software Engineer
> > > Interactive Factory
> > > 617.235.5857
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> > >
> >
> >
> --
> Dan Adams
> Senior Software Engineer
> Interactive Factory
> 617.235.5857
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Dan Adams <da...@ifactory.com>.
The htmlunit stuff is still pretty experimental and I've speced out what
it might look like but haven't done any heavy development. Currently we
have a number of integration tests that use htmlunit (which works great
except for javascript heavy stuff). The idea is to re-implement the
piece of htmlunit that does http connections so that it communicates
with PageTester rather than making http requests to a server. Then
rather than having to translate html text into a htmlunit dom it would
convert the tapestry dom into the htmlunit dom. Events in htmlunit such
as link.click() would actually result in calling pageTester.clickLink().
I've looked into it a bit and it seems pretty feasible (you basically
just implement WebConnection). I'll probably do this so that we can
integration test our CMS apps from within unit tests without having to
separately start the environment but that won't be for a little while.
On Thu, 2007-07-26 at 10:00 -0400, D&J Gredler wrote:
> Hi Dan,
>
> Congrats! I like the @Once idea, that'll be really cool.
>
> Out of curiosity, can you elaborate on the HtmlUnit integration? How has
> that gone?
>
> Take care,
>
> Daniel
>
>
> On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
> >
> > Hey guys. Good to be joining the team. Here's some background on how
> > I've been using Tapestry at my company (Interactive Factory):
> >
> > When I first came to our company just over 2 years ago we were using
> > what was essentially a home-grown Struts designed such that it was
> > Windows-only (despite it's being Java). After evaluating a number of web
> > frameworks (and having worked with JSF at Sun) I promptly discarded our
> > current code base and started afresh with T4 (and a number of other
> > frameworks such as Hibernate and Spring). The result was, as expected,
> > awesome. What I created for one project was then used on another, pulled
> > out into a central library of components, and is now the basis for
> > essentially all our projects, both CMS and custom publishing, ranging
> > from the fairly simple to to incredibly complex.
> >
> > The most unique usage of Tapestry I've had is an internal CMS
> > rapid-prototyping tool called ProtoCMS. It uses a simple XML CMS
> > definition and an object model stored as on ASO to render entire
> > interfaces of pages and components on the fly. This project is proof of
> > Tapestry's capabilities and that component-based development works. In
> > as little as 30 minutes you can create a functional CMS prototype for
> > use in sales presentations or project specification. Prototypes are also
> > easily editable through a javascript-based, ajax-enabled XML editor and
> > can be skinned custom to each client. Since it is a prototyping tool, it
> > allows creating new, re-usable components and functionality via a
> > templating language.
> >
> > I'm now looking forward to the next major release of our internal
> > libraries based on T5 which is driving all of the tickets and patches
> > I've submitted as well as my becoming a committer. I am aiming pretty
> > high with the features in this release so it's really exercising what T5
> > can do. Some notable things I'm looking forward to or have been working
> > on:
> >
> > - Enhancement of tapestry-hibernate to be more configurable and more
> > usable in both small and complex systems
> >
> > - Inspired by T5 I've been intentionally pushing the limits of what you
> > can do with PageTester including: integration with HtmlUnit, running
> > Jetty in-process so your tests and application run in the same JVM, and
> > automatic start-up of HSLQDB including creation of tables for Hibernate
> > entities.
> >
> > - Other possibly niceties such as one-off form validation and the @Once
> > annotation for caching method results optionally dependent on a binding.
> >
> > I'm looking forward to working with all of you and I can't wait to see
> > just how good T5 is going to be.
> >
> > On Thu, 2007-07-26 at 13:37 +0900, Nick Westgate wrote:
> > > Yeah, congrats Dan.
> > >
> > > Dan has logged a lot of JIRA issues, so hopefully we can look
> > > forward to some stuff that Howard doesn't have time for. ;-)
> > >
> > > Cheers,
> > > Nick.
> > >
> > >
> > > Daniel Jue wrote:
> > > > Congrats Dan, I can't wait to see some impressive stuff! =)
> > > >
> > > > Can you tell some features we can look forward to?
> > > >
> > > >
> > > >> Dan ... get started on that CLA: Here's some information you'll
> > need:
> > > >>
> > > >> http://apache.org/dev/pmc.html#newcommitter
> > > >>
> > > >> Congrats!
> > > >>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> > --
> > Dan Adams
> > Senior Software Engineer
> > Interactive Factory
> > 617.235.5857
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
>
--
Dan Adams
Senior Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [PASS] Dan Adams as Tapestry Committer
Posted by D&J Gredler <dj...@gmail.com>.
Hi Dan,
Congrats! I like the @Once idea, that'll be really cool.
Out of curiosity, can you elaborate on the HtmlUnit integration? How has
that gone?
Take care,
Daniel
On 7/26/07, Dan Adams <da...@ifactory.com> wrote:
>
> Hey guys. Good to be joining the team. Here's some background on how
> I've been using Tapestry at my company (Interactive Factory):
>
> When I first came to our company just over 2 years ago we were using
> what was essentially a home-grown Struts designed such that it was
> Windows-only (despite it's being Java). After evaluating a number of web
> frameworks (and having worked with JSF at Sun) I promptly discarded our
> current code base and started afresh with T4 (and a number of other
> frameworks such as Hibernate and Spring). The result was, as expected,
> awesome. What I created for one project was then used on another, pulled
> out into a central library of components, and is now the basis for
> essentially all our projects, both CMS and custom publishing, ranging
> from the fairly simple to to incredibly complex.
>
> The most unique usage of Tapestry I've had is an internal CMS
> rapid-prototyping tool called ProtoCMS. It uses a simple XML CMS
> definition and an object model stored as on ASO to render entire
> interfaces of pages and components on the fly. This project is proof of
> Tapestry's capabilities and that component-based development works. In
> as little as 30 minutes you can create a functional CMS prototype for
> use in sales presentations or project specification. Prototypes are also
> easily editable through a javascript-based, ajax-enabled XML editor and
> can be skinned custom to each client. Since it is a prototyping tool, it
> allows creating new, re-usable components and functionality via a
> templating language.
>
> I'm now looking forward to the next major release of our internal
> libraries based on T5 which is driving all of the tickets and patches
> I've submitted as well as my becoming a committer. I am aiming pretty
> high with the features in this release so it's really exercising what T5
> can do. Some notable things I'm looking forward to or have been working
> on:
>
> - Enhancement of tapestry-hibernate to be more configurable and more
> usable in both small and complex systems
>
> - Inspired by T5 I've been intentionally pushing the limits of what you
> can do with PageTester including: integration with HtmlUnit, running
> Jetty in-process so your tests and application run in the same JVM, and
> automatic start-up of HSLQDB including creation of tables for Hibernate
> entities.
>
> - Other possibly niceties such as one-off form validation and the @Once
> annotation for caching method results optionally dependent on a binding.
>
> I'm looking forward to working with all of you and I can't wait to see
> just how good T5 is going to be.
>
> On Thu, 2007-07-26 at 13:37 +0900, Nick Westgate wrote:
> > Yeah, congrats Dan.
> >
> > Dan has logged a lot of JIRA issues, so hopefully we can look
> > forward to some stuff that Howard doesn't have time for. ;-)
> >
> > Cheers,
> > Nick.
> >
> >
> > Daniel Jue wrote:
> > > Congrats Dan, I can't wait to see some impressive stuff! =)
> > >
> > > Can you tell some features we can look forward to?
> > >
> > >
> > >> Dan ... get started on that CLA: Here's some information you'll
> need:
> > >>
> > >> http://apache.org/dev/pmc.html#newcommitter
> > >>
> > >> Congrats!
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > > For additional commands, e-mail: dev-help@tapestry.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> --
> Dan Adams
> Senior Software Engineer
> Interactive Factory
> 617.235.5857
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Daniel Gredler
http://daniel.gredler.net/
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Dan Adams <da...@ifactory.com>.
Hey guys. Good to be joining the team. Here's some background on how
I've been using Tapestry at my company (Interactive Factory):
When I first came to our company just over 2 years ago we were using
what was essentially a home-grown Struts designed such that it was
Windows-only (despite it's being Java). After evaluating a number of web
frameworks (and having worked with JSF at Sun) I promptly discarded our
current code base and started afresh with T4 (and a number of other
frameworks such as Hibernate and Spring). The result was, as expected,
awesome. What I created for one project was then used on another, pulled
out into a central library of components, and is now the basis for
essentially all our projects, both CMS and custom publishing, ranging
from the fairly simple to to incredibly complex.
The most unique usage of Tapestry I've had is an internal CMS
rapid-prototyping tool called ProtoCMS. It uses a simple XML CMS
definition and an object model stored as on ASO to render entire
interfaces of pages and components on the fly. This project is proof of
Tapestry's capabilities and that component-based development works. In
as little as 30 minutes you can create a functional CMS prototype for
use in sales presentations or project specification. Prototypes are also
easily editable through a javascript-based, ajax-enabled XML editor and
can be skinned custom to each client. Since it is a prototyping tool, it
allows creating new, re-usable components and functionality via a
templating language.
I'm now looking forward to the next major release of our internal
libraries based on T5 which is driving all of the tickets and patches
I've submitted as well as my becoming a committer. I am aiming pretty
high with the features in this release so it's really exercising what T5
can do. Some notable things I'm looking forward to or have been working
on:
- Enhancement of tapestry-hibernate to be more configurable and more
usable in both small and complex systems
- Inspired by T5 I've been intentionally pushing the limits of what you
can do with PageTester including: integration with HtmlUnit, running
Jetty in-process so your tests and application run in the same JVM, and
automatic start-up of HSLQDB including creation of tables for Hibernate
entities.
- Other possibly niceties such as one-off form validation and the @Once
annotation for caching method results optionally dependent on a binding.
I'm looking forward to working with all of you and I can't wait to see
just how good T5 is going to be.
On Thu, 2007-07-26 at 13:37 +0900, Nick Westgate wrote:
> Yeah, congrats Dan.
>
> Dan has logged a lot of JIRA issues, so hopefully we can look
> forward to some stuff that Howard doesn't have time for. ;-)
>
> Cheers,
> Nick.
>
>
> Daniel Jue wrote:
> > Congrats Dan, I can't wait to see some impressive stuff! =)
> >
> > Can you tell some features we can look forward to?
> >
> >
> >> Dan ... get started on that CLA: Here's some information you'll need:
> >>
> >> http://apache.org/dev/pmc.html#newcommitter
> >>
> >> Congrats!
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
--
Dan Adams
Senior Software Engineer
Interactive Factory
617.235.5857
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Nick Westgate <ni...@key-planning.co.jp>.
Yeah, congrats Dan.
Dan has logged a lot of JIRA issues, so hopefully we can look
forward to some stuff that Howard doesn't have time for. ;-)
Cheers,
Nick.
Daniel Jue wrote:
> Congrats Dan, I can't wait to see some impressive stuff! =)
>
> Can you tell some features we can look forward to?
>
>
>> Dan ... get started on that CLA: Here's some information you'll need:
>>
>> http://apache.org/dev/pmc.html#newcommitter
>>
>> Congrats!
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [PASS] Dan Adams as Tapestry Committer
Posted by Daniel Jue <te...@gmail.com>.
Congrats Dan, I can't wait to see some impressive stuff! =)
Can you tell some features we can look forward to?
> Dan ... get started on that CLA: Here's some information you'll need:
>
> http://apache.org/dev/pmc.html#newcommitter
>
> Congrats!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org