ditto.
-1 forum
-Original Message-
From: Christian Edward Gruber
Reply-To: Tapestry users
To: Tapestry users
Subject: Re: Solving the T5 Documentation Dilemma
Date: Wed, 13 May 2009 09:29:10 -0400
-1 on forum for the same reasons.
On 13-May-09, at 07:36 , Alfie Kirkpatrick wrote
will simply act to fragment discussions which are an invaluable
information source.
Best regards, Alfie.
-Original Message-
From: liigo [mailto:com.li...@gmail.com]
Sent: 13 May 2009 03:02
To: Tapestry users
Subject: Re: Solving the T5 Documentation Dilemma
+1 for Official docs and User
regards, Alfie.
-Original Message-
From: liigo [mailto:com.li...@gmail.com]
Sent: 13 May 2009 03:02
To: Tapestry users
Subject: Re: Solving the T5 Documentation Dilemma
+1 for Official docs and User docs, and +1 for tapestry forum
+1 for Official docs and User docs, and +1 for tapestry forum
2009/5/1 Otho
> I would suggest splitting the documentation.
>
> There should be the reference documentation by the creators/commiters of
> the
> project, whis is organized like a book covering all the different aspects
> of
> tapestr
I'll look into all that.
On Tue, May 12, 2009 at 12:06 AM, Ben Gidley wrote:
> I think the wiki is a great idea
> I was just thinking of adding some notes to it but I can't figure out where
> to add them at http://tapestry.formos.com/wiki/dashboard.action.
>
> It could do with a home page helping
I think the wiki is a great idea
I was just thinking of adding some notes to it but I can't figure out where
to add them at http://tapestry.formos.com/wiki/dashboard.action.
It could do with a home page helping people find which space to use etc.
Would it also be possible to update the Apache wik
-1 for forums
+1 for wiki
Wiki is much better to create "persistent" knowledge, imho.
We can try it open for guests thus it would be easier to start for
occasional users.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apa
> Is someone still using own mail to receive these :)
Yes... that means normally there should be a lists@ alias for sending mails to
the lists - need to check whats wrong with my smtp setup.
> I've used nabble for a while, and it really rocks. Try it out
>
> http://www.nabble.com/Tapestry-f302.h
Is someone still using own mail to receive these :)
I've used nabble for a while, and it really rocks. Try it out
http://www.nabble.com/Tapestry-f302.html
- Ville
Piero Sartini-4 wrote:
>
> On Freitag, 1. Mai 2009 19:04:53 Otho wrote:
>> The perfect solution and topping cream would be a for
On Freitag, 1. Mai 2009 19:04:53 Otho wrote:
> The perfect solution and topping cream would be a forum/community system
> written in Tapestry of course, as a showcase and demonstration of its
> capabilities as well as a solid starting point for Tapestry apps. But I am
> aware of the effort and time
On Freitag, 1. Mai 2009 20:09:07 Ulrich Stärk wrote:
> As I understand, CLAs only have to be signed by documentation contributors
> if the exported wiki documentation is bundled with the release. If its
> purely online, I don't think that this is necessary.
Thanks for pointing this out. My assumpt
As I understand, CLAs only have to be signed by documentation contributors if the exported wiki
documentation is bundled with the release. If its purely online, I don't think that this is
necessary. On the other hand, CLAs also give the users an assurance that the generated content will
be freel
yes, I know nabble, and I think it is great. I also think usenet is
generally great, but at some point of support it does not scale.
At mailinglists you don't have topic categories + sticky notes which I
think are quite important for navigation. Further more it lacks and a
notification system
2009/5/1 Alex Kotchnev
> -1 on the forum. nabble, markmail and others do an excellent job at
> providing a forum interface to a mailing list.
I would really contend the "excellent". It is crude and not really useably
imo. The main point for a forum would be exactly your second point:
> The co
Re: Solving the T5 Documentation Dilemma
From: Andy Pahne
Date: 05/01/2009 11:45
except when they are down, just like the hibernate forums recently. I
always preferred mailing lists...
just my 2 cents
manuel aldana schrieb:
> Otho schrieb:
>> And lastly I would suggest sett
f tying it into Maven. I for one don't use Maven, and the
perceived additional complexity may put others off experimenting & using
Tap.
-Original Message-
From: Otho
Reply-To: Tapestry users
To: Tapestry users
Subject: Re: Solving the T5 Documentation Dilemma
Date: Fri, 1 Ma
On Wed, Apr 29, 2009 at 7:29 PM, Howard Lewis Ship wrote:
> It might be possible for a wiki to operate in the same way ... we
> could have a Tapestry 5.1 space and, at the start of 5.2, we could
> copy it to form the Tapestry 5.2 space. In this way,
> the documentation for prior releases would be
I must also say I prefer mailing lists - it is easier to follow it. If you
want a forum why not use the nabble or markmail interfaces to the mailing
lists?
e.g. http://tapestry.markmail.org/ or
http://www.nabble.com/Tapestry---User-f340.html
Ben Gidley
www.gidley.co.uk
b...@gidley.co.uk
On Fri,
except when they are down, just like the hibernate forums recently. I
always preferred mailing lists...
just my 2 cents
manuel aldana schrieb:
Otho schrieb:
And lastly I would suggest setting up a forum. Information is more
easily
organized there and searching is more convenient than wíth
Otho schrieb:
And lastly I would suggest setting up a forum. Information is more easily
organized there and searching is more convenient than wíth a mailing list
alone. I would think that the barrier of contributing to a forum is lower
than that of contributing to / asking on a mailinglist. Well,
I would suggest splitting the documentation.
There should be the reference documentation by the creators/commiters of the
project, whis is organized like a book covering all the different aspects of
tapestry 5 in a reference manner eg like spring or hibernate docs. These are
tied to the release ve
> I don't think Tapestry's wiki, http://wiki.apache.org/tapestry, is up
> to the task.
Confluence is available with apache as well. There is already a space
available at http://cwiki.apache.org/TAPESTRY/ ... maybe its just a matter of
adding content to it?
Anyway.. on Tapestry360 someone would
On Apr 29, 2009, at 7:29 PM, Howard Lewis Ship wrote:
On Wed, Apr 29, 2009 at 4:11 PM, Christian Edward Gruber
wrote:
...
project which could be versioned (or at least released) on a
different
cycle. This could keep (for any branch such as 5.0, 5.1) the docs
as fresh
as you wanted to r
LOL. You got me, Howard. Sorry. I have even visited them, but in my
caffeine starved brain I forgot entirely.
Christian.
On Apr 29, 2009, at 7:29 PM, Howard Lewis Ship wrote:
A second, orthogonal pattern is to generate site-documentation on a
nightly
build and put it up at a standard l
On Wed, Apr 29, 2009 at 4:11 PM, Christian Edward Gruber
wrote:
> I think a wiki is a decent option, but another option would be to make a
>
> /trunk/tapestry-ioc/
> ...
> /trunk/tapestry-site/
> ...
>
> project which could be versioned (or at least released) on a different
> cycle. This could ke
I'd also like to suggest that we add small usage examples into
the .xdocs for the components themselves.
This was what made NeXTSTEP documentation so nice. You'd have some
decent usage documents right in the component reference, so I can go
to the loop component reference and see six ways
I think a wiki is a decent option, but another option would be to make a
/trunk/tapestry-ioc/
...
/trunk/tapestry-site/
...
project which could be versioned (or at least released) on a different
cycle. This could keep (for any branch such as 5.0, 5.1) the docs as
fresh as you wanted to rele
27 matches
Mail list logo
