tapestry-tassel-development

[Tassel-Dev] tapestrycomponents.org

[James T. <ja...@da...>]

So I have gone ahead and registered tapestrycomponents.org and 
tapestrycomponents.com for our use.  Robert - I am glad that you like 
the tabs idea (whereby we can provide links to other tapestry component 
repositories from the top of the tapestrycomponents.org main page).  I 
too think it provides an excellent tradeoff between convergence and 
independence.

Obviously I second your sentiments about moving our discussions to the 
list.  :-)

James

[Tassel-Dev] solving the "coders don't write docs problem"

[James T. <ja...@da...>]

For what it is worth, I would like to float my ideas about the features
that I am thinking about adding to Tassel.

I agree with those who say that Tassel should have low barriers to entry
- documentation and examples are nice but should not be required.  In
many successful open source projects there is a division of labour
between those who code and those who write the docs - and wikis seem to
do a good job of facilitating this division of labour.

So I am thinking about adding 2 "wiki-ized" sections to Tassel, one
structured and one essentially unstructured.  I intend to give the owner
the ability to turn off the "public may edit" properties on the two
sections if he wishes to control the documentation himself - but the
default would be "open to those with a Tassel account".

The two sections would be the traditional "parameters" and "example" 
sections we are used to seeing in Tapestry component documentation.  For 
example: 
http://jakarta.apache.org/tapestry/tapestry/ComponentReference/TextField.html

James

Re: [Tassel-Dev] solving the "coders don't write docs problem"

[Robert Z. <ro...@sc...>]

Sounds great.
On another project, I incorporated the radeox wiki rendering engine into
a tapestry app... I was pretty pleased with the result.  I've been
contemplating doing the work necessary to "componentize" the stuff, if
that would help.  In any event... I think it would be a great addition.

Robert

James Treleaven wrote:
> For what it is worth, I would like to float my ideas about the features
> that I am thinking about adding to Tassel.
> 
> I agree with those who say that Tassel should have low barriers to entry
> - documentation and examples are nice but should not be required.  In
> many successful open source projects there is a division of labour
> between those who code and those who write the docs - and wikis seem to
> do a good job of facilitating this division of labour.
> 
> So I am thinking about adding 2 "wiki-ized" sections to Tassel, one
> structured and one essentially unstructured.  I intend to give the owner
> the ability to turn off the "public may edit" properties on the two
> sections if he wishes to control the documentation himself - but the
> default would be "open to those with a Tassel account".
> 
> The two sections would be the traditional "parameters" and "example"
> sections we are used to seeing in Tapestry component documentation.  For
> example:
> http://jakarta.apache.org/tapestry/tapestry/ComponentReference/TextField.html
> 
> 
> James
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Tapestry-tassel-development mailing list
> Tap...@li...
> https://lists.sourceforge.net/lists/listinfo/tapestry-tassel-development

Re: [Tassel-Dev] tapestrycomponents.org

[Robert Z. <ro...@sc...>]

I thought I had sent this along earlier, but, apparently it got lost in
my drafts folder, sorry. :)

Robert

Sweet. Thanks for doing that.
I've added a few odds and ends to the RFE list,and noted one bug that
I know of. I've made the initial commit to CVS of the tassel source.
Needs cleaning/refactoring/etc. All in good time, I suppose. :)
I'll get back in touch with the eq ppl to work out the virtual hosting
details.

Robert

James Treleaven wrote:
> So I have gone ahead and registered tapestrycomponents.org and
> tapestrycomponents.com for our use.  Robert - I am glad that you like
> the tabs idea (whereby we can provide links to other tapestry component
> repositories from the top of the tapestrycomponents.org main page).  I
> too think it provides an excellent tradeoff between convergence and
> independence.
> 
> Obviously I second your sentiments about moving our discussions to the
> list.  :-)
> 
> James
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Tapestry-tassel-development mailing list
> Tap...@li...
> https://lists.sourceforge.net/lists/listinfo/tapestry-tassel-development