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/C
I would love to be part of any such project.
taha
On Thu, Jun 23, 2011 at 8:59 AM, Robert Zeigler 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 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,
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 wrote:
> I agree that the main need is for a
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 databas
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." 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
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-Tape
That is very ambitions but it would be awesome!My (and my coworker's)
problem so far is having either too many componentsthat do the same thing, or
not a single one.For example, Security, JPA integration, datepicker, and
grid.The most important part of all of this for me is to have it googleable
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 compone
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
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 a
11 matches
Mail list logo
