On Fri, 06 May 2011 09:27:51 -0300, Adam Zimowski
wrote:
I'm sorry about confusion. That's right, a much better way of
generalizing what is a component is to check the package. For Tapestry
component, if it lives in org.apache.tapestry5.corelib.components,
then it is a component.
This is th
I'm sorry about confusion. That's right, a much better way of
generalizing what is a component is to check the package. For Tapestry
component, if it lives in org.apache.tapestry5.corelib.components,
then it is a component.
Adam
On Fri, May 6, 2011 at 7:12 AM, Thiago H. de Paula Figueiredo
wrote
On Fri, 06 May 2011 09:00:04 -0300, Adam Zimowski
wrote:
http://tapestry.apache.org/component-reference.html
At the bottom, there is a list of base classes which make a component
class a component. If a class does not derive from one of them, it
technically IS NOT a component.
This is n
On Fri, 06 May 2011 08:52:54 -0300, Josh Kamau
wrote:
Thanks Thiago,
:)
I actually thought blocks are components. I didnt know there are pages,
components and blocks .[?]
I'd say there are pages, components and mixins. Block is something you can
declare inside a page or component temp
It is somewhat confusing. Blocks seem like components because they are
defined in the template. But Thiago is right, they're just "Blocks".
Here is a good reference you can use as a rule of thumb for what is (and is
not) a component:
http://tapestry.apache.org/component-reference.html
At the bot
Thanks Thiago,
I actually thought blocks are components. I didnt know there are pages,
components and blocks .[?]
regards.
Josh.
On Fri, 06 May 2011 05:36:06 -0300, Josh Kamau
wrote:
Hi Team,
Hi!
I am still learning t5 So i may ask very many questions. So here is a
question on injections.
I have so far learnt the following regarding injection:
When injecting Services , Use @Inject
When injecting pages, user @Inj
