Howard may be forgiven :)
Howard is stuck in London due to Volcano. Never thought that'd be my status.
Howard is also jet-lagged, exhausted and sick.
On Fri, Apr 16, 2010 at 11:24 AM, Markus Feindler
wrote:
So?? Howard?
So a community-driven documentation effort is out of the questi
Howard is stuck in London due to Volcano. Never thought that'd be my status.
Howard is also jet-lagged, exhausted and sick.
On Fri, Apr 16, 2010 at 11:24 AM, Markus Feindler
wrote:
> So?? Howard?
>>>
>>> So a community-driven documentation effort is out of the question unless
>>> we
>>> come up
So?? Howard?
So a community-driven documentation effort is out of the question unless we
come up with a system or procedure that complies with ASF rules.
We could just require to sign a CLA for people that want to help out
with documentation. This would mean to give rights to modifiy/creat
> So a community-driven documentation effort is out of the question unless we
> come up with a system or procedure that complies with ASF rules.
We could just require to sign a CLA for people that want to help out
with documentation. This would mean to give rights to modifiy/create
only to people
What about developing such a system in Tapestry, document the code and use
it as a guide? Two birds with one stone.
>
> Original-Nachricht
> Datum: Wed, 24 Mar 2010 08:46:30 +0100
> Von: "Ulrich Stärk"
> An: Tapestry users
> Betref
Unfortunately, ASF procedures require every contribution to be made porpuseful and record of this
purpose has to be kept. In practice that means that every contribution to the project, even
documentation, has to be made by someone who either signed a contributor license agreement (CLA) or
(in ca
to this e-mail.
>
> - Original Message -
> From: "Geoff Callender"
> To: "Tapestry users"
> Sent: Wednesday, 24 March, 2010 05:13:22 GMT +02:00 Athens, Beirut,
> Bucharest, Istanbul
> Subject: Re: Documentation Request/Suggestion
>
> I agree
ender"
To: "Tapestry users"
Sent: Wednesday, 24 March, 2010 05:13:22 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Documentation Request/Suggestion
I agree too. Users of anything usually need both a Guide and a Reference. To
me, the Tapestry documentation is much more
I agree too. Users of anything usually need both a Guide and a Reference. To
me, the Tapestry documentation is much more of a Reference than a Guide, and
that makes it a source of immense frustration to newbies and the experienced
alike.
Here's what I mean: A User Reference is usually organised
I'll second Michael's statement, the documentation may exist but you
don't even know it's there unless you already know it's there. Tribal
knowledge and all that. Sometimes Google even gets me there.
But the T5 website is NOT my first choice exactly because of its
organization, and it *should* be
Most new users don't know where in the JavaDoc to begin looking. I
wasn't suggesting there was no JavaDoc, but I don't consider it to be
the main starting point for a new user (needle in a haystack). It is
something for more advanced users.
As for: http://tapestry.apache.org/tapestry5.1/tapestry
You're right about the information being technically available, but to
newbies it isn't.
I absolutely love the idea of a page that presents a "best of" list of
services, with hands-on examples and simple explanations. For me, T5 is all
about common patterns. I always use RenderSupport for doing ex
I guess we can kill two birds with one stone here. There is the lack of an annotation telling the
user which services are there just for consumption and which are to be overriden with a
user-supplied implementation. Having such an annotation (or two) would make it easy to just scan the
packages
Why is the javadoc insufficient? All the services are located in few
packages depending on the module they were created. Some of them are:
http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/ioc/services/package-frame.html
http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/t
Created: https://issues.apache.org/jira/browse/TAP5-1070
I'm not sure if what I meant by Injectables makes sense, but basically
I meant all things supplied by T5 that you can @Inject (such as
ComponentResources). I had been using T5 for 2-3 months and had no
idea ComponentResources even existed a
+1
On 23/03/2010, at 7:11 AM, Thiago H. de Paula Figueiredo wrote:
> On Mon, 22 Mar 2010 16:48:31 -0300, Michael Gentry
> wrote:
>
>> Hello everyone,
>
> Hi!
>
> For annotations,
>
>> All I'm imagining here is a table for each that lists all of the
>> annotations and injectables that ship w
On Mon, 22 Mar 2010 16:48:31 -0300, Michael Gentry
wrote:
Hello everyone,
Hi!
For annotations,
All I'm imagining here is a table for each that lists all of the
annotations and injectables that ship with Tapestry, a short
description as to what they do, and perhaps links to examples/detai
Hello everyone,
I've been working with some developers who were new to Tapestry 5 (and
I had only worked with it a few months before them). One thing that
has come out of that process is I think it would be nice for new and
even experienced users to have a couple more reference pages in the
docum
18 matches
Mail list logo
