You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Lenny Primak <lp...@hope.nyc.ny.us> on 2011/06/22 18:30:30 UTC
Contributed modules to Tapestry
I agree with Taha here.
I think Tapestry needs THE one place to put contributing modules.
'Put it on GitHub' isn't good enough.
One of the guys who works for me came from microsoft world,
and he constantly complains that everything is very hard to find.
I am teaching him the 'right' unix way of doing things but I am starting
to feel his pain when it comes to finding tapestry contributing components.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by Taha Hafeez <ta...@gmail.com>.
Hi Bob
If I have to create such an application for components, I will just use
database driven tapestry application with each component contributing
1. A component block to show the usage
2. A help block to show the usage etc
The application will keep track of its level, ratings etc in a database.
Search, filtering etc can be then be added..
regards
Taha
On Thu, Jun 23, 2011 at 5:57 AM, Bob Harner <bo...@gmail.com> wrote:
> I agree that the main need is for a registry, rather than a
> repository. Coincidentally over the last several days I have been
> thinking about how a "component registry" app could work to solve
> these sorts of code locator issues. It could include modules as well,
> but my focus here has been on components.
>
> There are currently at least 150 (!) Tapestry components and mixins
> available out there (Tapestry-core components, collections like
> ChenilleKit, Equanda, Ioko, Lombok and TapX, blog posts like those on
> tinybits.blogspot.com and several MoinMoin wiki pages), but there is
> no master list of the components and mixins available across all the
> modules. The http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry
> and http://tapestry.apache.org/third-party-modules.html pages do
> provide simple lists of modules, but there is no "component finder"
> tool anywhere.
>
> This is what I'm considering. Tell me what you think:
>
> * A database-driven web app using Tapestry and Apache Cayenne,
> Tapestry-security, Apache Shiro (hey, all Apache products)
>
> * A light, carefully-designed, AJAX-based, highly componentized UI.
> Definitely NOT something slapped together and half-baked, but really
> serious and complete.
>
> * Copy the CSS of the new Tapestry documentation site.
>
> * Would have, for each component, the name, brief description,
> license, Tapestry version compatibility, links to similar components
> (e.g. JumpStart's Textbox Hint mixin is similar to Lombok's Watermark
> mixin), maybe a small screenshot, a link to the component's
> documentation, and a link to the component's demo page, if any.
>
> * Searching, sorting and filtering. For example, be able to search for
> "editor" and find ChenelleKit's Editor and InPlaceEditor, as well as
> Kenai's CKEditor and FCKEditor components. Or choose a specific module
> and list all of its components. Or list only mixins. Or only
> components with Apache 2.0 licenses.
>
> * Some sort of rating system reflecting the component's code quality,
> design, and freshness.
>
> * Anybody could submit a new component for consideration, but only
> certain designated people (committers?) could approve the listing.
>
> * Use Tapestry-security to manage authentication/authorization. Can we
> tie this to Apache's LDAP so that committers can use their existing
> accounts?
>
> The goal would be to complement JumpStart and other resources, rather
> than competing with them. For example, for Tapestry's Palette
> component, the demo link would go to
>
> http://jumpstart.doublenegative.com.au/jumpstart/examples/component/coreinputcomponents
> .
>
> * Hosted somewhere at apache.com, perhaps in the Apache Jail like
> Hotel Booking (not sure of the implications there).
>
> * Source code in apache SVN.
>
> As a Tapestry app, it should be a very high quality public showcase
> for the best that Tapestry can do.
>
> Anyway, that's my goal. I'm starting on it today. Any ideas?
>
>
> On Wed, Jun 22, 2011 at 1:47 PM, Lenny Primak <lp...@hope.nyc.ny.us>
> wrote:
> > Yes, this is the old question of keeping the ecosystem as pure as
> possible.
> > I don't think it matters as much where it is hosted (apache etc)
> > it could very well be hosted on github,
> > but there should be only one place, one list, perhaps with subsections,
> > and the voting idea is also a good one to get on that list,
> > but it should be number one result in google :)
> >
> > On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote:
> >
> >> I would prefer two real centers. For licensing reasons, much code can
> >> not be hosted at Apache. In addition, my big concern is "dump-and-run"
> >> code (which we've even seen with Tapestry committers in the past). We
> >> don't want to be responsible for more code than we can support.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Contributed modules to Tapestry
Posted by Taha Hafeez <ta...@gmail.com>.
I would love to be part of any such project.
taha
On Thu, Jun 23, 2011 at 8:59 AM, Robert Zeigler <robert.zeigler@roxanemy.com
> wrote:
> I started something like this a long time ago; it had a lot of what you're
> talking about here, although I wouldn't call the interface "polished" by any
> stretch of the imagination. :)
> I started porting it to T5 awhile ago, but other projects took precedence.
> I can send the code along if you want, but, honestly, probably better to
> start from scratch.
>
> I'm wondering if it's worth having, eg, a "tapesty-contrib" maven
> repository so that if people are interested in using the components it's a
> simple matter to add the dependencies to the project?
>
> It's possible that I can arrange hosting for such a repository (the maven),
> if there's enough interest.
>
> Robert
>
> On Jun 22, 2011, at 6/227:27 PM , Bob Harner wrote:
>
> > I agree that the main need is for a registry, rather than a
> > repository. Coincidentally over the last several days I have been
> > thinking about how a "component registry" app could work to solve
> > these sorts of code locator issues. It could include modules as well,
> > but my focus here has been on components.
> >
> > There are currently at least 150 (!) Tapestry components and mixins
> > available out there (Tapestry-core components, collections like
> > ChenilleKit, Equanda, Ioko, Lombok and TapX, blog posts like those on
> > tinybits.blogspot.com and several MoinMoin wiki pages), but there is
> > no master list of the components and mixins available across all the
> > modules. The http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry
> > and http://tapestry.apache.org/third-party-modules.html pages do
> > provide simple lists of modules, but there is no "component finder"
> > tool anywhere.
> >
> > This is what I'm considering. Tell me what you think:
> >
> > * A database-driven web app using Tapestry and Apache Cayenne,
> > Tapestry-security, Apache Shiro (hey, all Apache products)
> >
> > * A light, carefully-designed, AJAX-based, highly componentized UI.
> > Definitely NOT something slapped together and half-baked, but really
> > serious and complete.
> >
> > * Copy the CSS of the new Tapestry documentation site.
> >
> > * Would have, for each component, the name, brief description,
> > license, Tapestry version compatibility, links to similar components
> > (e.g. JumpStart's Textbox Hint mixin is similar to Lombok's Watermark
> > mixin), maybe a small screenshot, a link to the component's
> > documentation, and a link to the component's demo page, if any.
> >
> > * Searching, sorting and filtering. For example, be able to search for
> > "editor" and find ChenelleKit's Editor and InPlaceEditor, as well as
> > Kenai's CKEditor and FCKEditor components. Or choose a specific module
> > and list all of its components. Or list only mixins. Or only
> > components with Apache 2.0 licenses.
> >
> > * Some sort of rating system reflecting the component's code quality,
> > design, and freshness.
> >
> > * Anybody could submit a new component for consideration, but only
> > certain designated people (committers?) could approve the listing.
> >
> > * Use Tapestry-security to manage authentication/authorization. Can we
> > tie this to Apache's LDAP so that committers can use their existing
> > accounts?
> >
> > The goal would be to complement JumpStart and other resources, rather
> > than competing with them. For example, for Tapestry's Palette
> > component, the demo link would go to
> >
> http://jumpstart.doublenegative.com.au/jumpstart/examples/component/coreinputcomponents
> .
> >
> > * Hosted somewhere at apache.com, perhaps in the Apache Jail like
> > Hotel Booking (not sure of the implications there).
> >
> > * Source code in apache SVN.
> >
> > As a Tapestry app, it should be a very high quality public showcase
> > for the best that Tapestry can do.
> >
> > Anyway, that's my goal. I'm starting on it today. Any ideas?
> >
> >
> > On Wed, Jun 22, 2011 at 1:47 PM, Lenny Primak <lp...@hope.nyc.ny.us>
> wrote:
> >> Yes, this is the old question of keeping the ecosystem as pure as
> possible.
> >> I don't think it matters as much where it is hosted (apache etc)
> >> it could very well be hosted on github,
> >> but there should be only one place, one list, perhaps with subsections,
> >> and the voting idea is also a good one to get on that list,
> >> but it should be number one result in google :)
> >>
> >> On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote:
> >>
> >>> I would prefer two real centers. For licensing reasons, much code can
> >>> not be hosted at Apache. In addition, my big concern is "dump-and-run"
> >>> code (which we've even seen with Tapestry committers in the past). We
> >>> don't want to be responsible for more code than we can support.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Contributed modules to Tapestry
Posted by Robert Zeigler <ro...@roxanemy.com>.
I started something like this a long time ago; it had a lot of what you're talking about here, although I wouldn't call the interface "polished" by any stretch of the imagination. :)
I started porting it to T5 awhile ago, but other projects took precedence. I can send the code along if you want, but, honestly, probably better to start from scratch.
I'm wondering if it's worth having, eg, a "tapesty-contrib" maven repository so that if people are interested in using the components it's a simple matter to add the dependencies to the project?
It's possible that I can arrange hosting for such a repository (the maven), if there's enough interest.
Robert
On Jun 22, 2011, at 6/227:27 PM , Bob Harner wrote:
> I agree that the main need is for a registry, rather than a
> repository. Coincidentally over the last several days I have been
> thinking about how a "component registry" app could work to solve
> these sorts of code locator issues. It could include modules as well,
> but my focus here has been on components.
>
> There are currently at least 150 (!) Tapestry components and mixins
> available out there (Tapestry-core components, collections like
> ChenilleKit, Equanda, Ioko, Lombok and TapX, blog posts like those on
> tinybits.blogspot.com and several MoinMoin wiki pages), but there is
> no master list of the components and mixins available across all the
> modules. The http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry
> and http://tapestry.apache.org/third-party-modules.html pages do
> provide simple lists of modules, but there is no "component finder"
> tool anywhere.
>
> This is what I'm considering. Tell me what you think:
>
> * A database-driven web app using Tapestry and Apache Cayenne,
> Tapestry-security, Apache Shiro (hey, all Apache products)
>
> * A light, carefully-designed, AJAX-based, highly componentized UI.
> Definitely NOT something slapped together and half-baked, but really
> serious and complete.
>
> * Copy the CSS of the new Tapestry documentation site.
>
> * Would have, for each component, the name, brief description,
> license, Tapestry version compatibility, links to similar components
> (e.g. JumpStart's Textbox Hint mixin is similar to Lombok's Watermark
> mixin), maybe a small screenshot, a link to the component's
> documentation, and a link to the component's demo page, if any.
>
> * Searching, sorting and filtering. For example, be able to search for
> "editor" and find ChenelleKit's Editor and InPlaceEditor, as well as
> Kenai's CKEditor and FCKEditor components. Or choose a specific module
> and list all of its components. Or list only mixins. Or only
> components with Apache 2.0 licenses.
>
> * Some sort of rating system reflecting the component's code quality,
> design, and freshness.
>
> * Anybody could submit a new component for consideration, but only
> certain designated people (committers?) could approve the listing.
>
> * Use Tapestry-security to manage authentication/authorization. Can we
> tie this to Apache's LDAP so that committers can use their existing
> accounts?
>
> The goal would be to complement JumpStart and other resources, rather
> than competing with them. For example, for Tapestry's Palette
> component, the demo link would go to
> http://jumpstart.doublenegative.com.au/jumpstart/examples/component/coreinputcomponents.
>
> * Hosted somewhere at apache.com, perhaps in the Apache Jail like
> Hotel Booking (not sure of the implications there).
>
> * Source code in apache SVN.
>
> As a Tapestry app, it should be a very high quality public showcase
> for the best that Tapestry can do.
>
> Anyway, that's my goal. I'm starting on it today. Any ideas?
>
>
> On Wed, Jun 22, 2011 at 1:47 PM, Lenny Primak <lp...@hope.nyc.ny.us> wrote:
>> Yes, this is the old question of keeping the ecosystem as pure as possible.
>> I don't think it matters as much where it is hosted (apache etc)
>> it could very well be hosted on github,
>> but there should be only one place, one list, perhaps with subsections,
>> and the voting idea is also a good one to get on that list,
>> but it should be number one result in google :)
>>
>> On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote:
>>
>>> I would prefer two real centers. For licensing reasons, much code can
>>> not be hosted at Apache. In addition, my big concern is "dump-and-run"
>>> code (which we've even seen with Tapestry committers in the past). We
>>> don't want to be responsible for more code than we can support.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by David Woods <dw...@gmail.com>.
Sounds like a great idea. I'd also suggest a region where people can
suggest new components, and these can be discussed and voted on, so that
those who want to can choose a project that will have the greatest impact.
On 23 June 2011 10:27, Bob Harner <bo...@gmail.com> wrote:
> I agree that the main need is for a registry, rather than a
> repository. Coincidentally over the last several days I have been
> thinking about how a "component registry" app could work to solve
> these sorts of code locator issues. It could include modules as well,
> but my focus here has been on components.
>
> There are currently at least 150 (!) Tapestry components and mixins
> available out there (Tapestry-core components, collections like
> ChenilleKit, Equanda, Ioko, Lombok and TapX, blog posts like those on
> tinybits.blogspot.com and several MoinMoin wiki pages), but there is
> no master list of the components and mixins available across all the
> modules. The http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry
> and http://tapestry.apache.org/third-party-modules.html pages do
> provide simple lists of modules, but there is no "component finder"
> tool anywhere.
>
> This is what I'm considering. Tell me what you think:
>
> * A database-driven web app using Tapestry and Apache Cayenne,
> Tapestry-security, Apache Shiro (hey, all Apache products)
>
> * A light, carefully-designed, AJAX-based, highly componentized UI.
> Definitely NOT something slapped together and half-baked, but really
> serious and complete.
>
> * Copy the CSS of the new Tapestry documentation site.
>
> * Would have, for each component, the name, brief description,
> license, Tapestry version compatibility, links to similar components
> (e.g. JumpStart's Textbox Hint mixin is similar to Lombok's Watermark
> mixin), maybe a small screenshot, a link to the component's
> documentation, and a link to the component's demo page, if any.
>
> * Searching, sorting and filtering. For example, be able to search for
> "editor" and find ChenelleKit's Editor and InPlaceEditor, as well as
> Kenai's CKEditor and FCKEditor components. Or choose a specific module
> and list all of its components. Or list only mixins. Or only
> components with Apache 2.0 licenses.
>
> * Some sort of rating system reflecting the component's code quality,
> design, and freshness.
>
> * Anybody could submit a new component for consideration, but only
> certain designated people (committers?) could approve the listing.
>
> * Use Tapestry-security to manage authentication/authorization. Can we
> tie this to Apache's LDAP so that committers can use their existing
> accounts?
>
> The goal would be to complement JumpStart and other resources, rather
> than competing with them. For example, for Tapestry's Palette
> component, the demo link would go to
>
> http://jumpstart.doublenegative.com.au/jumpstart/examples/component/coreinputcomponents
> .
>
> * Hosted somewhere at apache.com, perhaps in the Apache Jail like
> Hotel Booking (not sure of the implications there).
>
> * Source code in apache SVN.
>
> As a Tapestry app, it should be a very high quality public showcase
> for the best that Tapestry can do.
>
> Anyway, that's my goal. I'm starting on it today. Any ideas?
>
>
> On Wed, Jun 22, 2011 at 1:47 PM, Lenny Primak <lp...@hope.nyc.ny.us>
> wrote:
> > Yes, this is the old question of keeping the ecosystem as pure as
> possible.
> > I don't think it matters as much where it is hosted (apache etc)
> > it could very well be hosted on github,
> > but there should be only one place, one list, perhaps with subsections,
> > and the voting idea is also a good one to get on that list,
> > but it should be number one result in google :)
> >
> > On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote:
> >
> >> I would prefer two real centers. For licensing reasons, much code can
> >> not be hosted at Apache. In addition, my big concern is "dump-and-run"
> >> code (which we've even seen with Tapestry committers in the past). We
> >> don't want to be responsible for more code than we can support.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Contributed modules to Tapestry
Posted by Bob Harner <bo...@gmail.com>.
I agree that the main need is for a registry, rather than a
repository. Coincidentally over the last several days I have been
thinking about how a "component registry" app could work to solve
these sorts of code locator issues. It could include modules as well,
but my focus here has been on components.
There are currently at least 150 (!) Tapestry components and mixins
available out there (Tapestry-core components, collections like
ChenilleKit, Equanda, Ioko, Lombok and TapX, blog posts like those on
tinybits.blogspot.com and several MoinMoin wiki pages), but there is
no master list of the components and mixins available across all the
modules. The http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry
and http://tapestry.apache.org/third-party-modules.html pages do
provide simple lists of modules, but there is no "component finder"
tool anywhere.
This is what I'm considering. Tell me what you think:
* A database-driven web app using Tapestry and Apache Cayenne,
Tapestry-security, Apache Shiro (hey, all Apache products)
* A light, carefully-designed, AJAX-based, highly componentized UI.
Definitely NOT something slapped together and half-baked, but really
serious and complete.
* Copy the CSS of the new Tapestry documentation site.
* Would have, for each component, the name, brief description,
license, Tapestry version compatibility, links to similar components
(e.g. JumpStart's Textbox Hint mixin is similar to Lombok's Watermark
mixin), maybe a small screenshot, a link to the component's
documentation, and a link to the component's demo page, if any.
* Searching, sorting and filtering. For example, be able to search for
"editor" and find ChenelleKit's Editor and InPlaceEditor, as well as
Kenai's CKEditor and FCKEditor components. Or choose a specific module
and list all of its components. Or list only mixins. Or only
components with Apache 2.0 licenses.
* Some sort of rating system reflecting the component's code quality,
design, and freshness.
* Anybody could submit a new component for consideration, but only
certain designated people (committers?) could approve the listing.
* Use Tapestry-security to manage authentication/authorization. Can we
tie this to Apache's LDAP so that committers can use their existing
accounts?
The goal would be to complement JumpStart and other resources, rather
than competing with them. For example, for Tapestry's Palette
component, the demo link would go to
http://jumpstart.doublenegative.com.au/jumpstart/examples/component/coreinputcomponents.
* Hosted somewhere at apache.com, perhaps in the Apache Jail like
Hotel Booking (not sure of the implications there).
* Source code in apache SVN.
As a Tapestry app, it should be a very high quality public showcase
for the best that Tapestry can do.
Anyway, that's my goal. I'm starting on it today. Any ideas?
On Wed, Jun 22, 2011 at 1:47 PM, Lenny Primak <lp...@hope.nyc.ny.us> wrote:
> Yes, this is the old question of keeping the ecosystem as pure as possible.
> I don't think it matters as much where it is hosted (apache etc)
> it could very well be hosted on github,
> but there should be only one place, one list, perhaps with subsections,
> and the voting idea is also a good one to get on that list,
> but it should be number one result in google :)
>
> On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote:
>
>> I would prefer two real centers. For licensing reasons, much code can
>> not be hosted at Apache. In addition, my big concern is "dump-and-run"
>> code (which we've even seen with Tapestry committers in the past). We
>> don't want to be responsible for more code than we can support.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Yes, this is the old question of keeping the ecosystem as pure as possible.
I don't think it matters as much where it is hosted (apache etc)
it could very well be hosted on github,
but there should be only one place, one list, perhaps with subsections,
and the voting idea is also a good one to get on that list,
but it should be number one result in google :)
On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote:
> I would prefer two real centers. For licensing reasons, much code can
> not be hosted at Apache. In addition, my big concern is "dump-and-run"
> code (which we've even seen with Tapestry committers in the past). We
> don't want to be responsible for more code than we can support.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by Howard Lewis Ship <hl...@gmail.com>.
I would prefer two real centers. For licensing reasons, much code can
not be hosted at Apache. In addition, my big concern is "dump-and-run"
code (which we've even seen with Tapestry committers in the past). We
don't want to be responsible for more code than we can support.
On Wed, Jun 22, 2011 at 9:30 AM, Lenny Primak <lp...@hope.nyc.ny.us> wrote:
> I agree with Taha here.
>
> I think Tapestry needs THE one place to put contributing modules.
> 'Put it on GitHub' isn't good enough.
>
> One of the guys who works for me came from microsoft world,
> and he constantly complains that everything is very hard to find.
> I am teaching him the 'right' unix way of doing things but I am starting
> to feel his pain when it comes to finding tapestry contributing components.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by "Angelo C." <an...@gmail.com>.
whatever as long as we can find it:) issue this time is, Taha has a nice
module, I came across his posting before and book marked it as I know, I'd
use it sometimes, but when the time comes to use, it is not there any more.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Contributed-modules-to-Tapestry-tp4514606p4516392.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by Lenny Primak <lp...@hope.nyc.ny.us>.
Forcing anything is a bad idea IMHO. Not everyone uses git as a source control system for one.
On Jun 22, 2011, at 10:48 PM, "Angelo C." <an...@gmail.com> wrote:
> putting it in github works, probably just a section in the
> tapestry.apache.org : contributed modules hosted in github with the last
> update date, forcing it to be in github will make locating easier.
>
> --
> View this message in context: http://tapestry.1045711.n5.nabble.com/Contributed-modules-to-Tapestry-tp4514606p4516169.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Contributed modules to Tapestry
Posted by "Angelo C." <an...@gmail.com>.
putting it in github works, probably just a section in the
tapestry.apache.org : contributed modules hosted in github with the last
update date, forcing it to be in github will make locating easier.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Contributed-modules-to-Tapestry-tp4514606p4516169.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org