Em Wed, 15 Oct 2008 08:51:33 -0300, Lubor Gajda [EMAIL PROTECTED]
escreveu:
Hi Thiago/Geoff,
Hi!
However, when you are using page based approach your flow definition is
scattered across whole application
and you have to edit and analyze all those hundreds of pages to gather
all
What implementations? Any Tapestry-related one?
For instance in Geoff's JumpStart are some examples how to implement
conversations in Tapestry.
On Wed, Oct 15, 2008 at 2:24 PM, Thiago H. de Paula Figueiredo
[EMAIL PROTECTED] wrote:
Em Wed, 15 Oct 2008 10:21:39 -0300, Lubor Gajda [EMAIL
Get yourself a copy of Tapestry in Action (Manning Publications) written by Howard. It is explicitly
written for Tapestry 3.
Uli
StevenF schrieb:
Thanks!
Is it true that the First Edition is for Tapestry 3 and the Second Edition
is for Tapestry 4?
Andy Huhn-3 wrote:
Hi Steven,
Woah! Indeed, this doesn't work anymore. Evil. How are we supposed to do this
now?
Uli
Geoff Callender schrieb:
No response, so I guess that means we can't add a Delete column to a
Grid any more.
On 14/10/2008, at 8:36 PM, Geoff Callender wrote:
Can anyone tell me if Penyihir's technique
You might want to try using the method naming convention instead of annotation.
@OnEvent(value = reset)
public Object reset(){
tableParsed = false;
saveSucceed = false;
return null;
}
change to:
public Object onActionFromReset(){
tableParsed = false;
Please ignore my stupidity. I misinterpreted the error message I was getting that had nothing to do
with this.
You can still add a delete column to your model with model.add(delete, null) and add a
deleteCell parameter to your template in order to have a delete column. Works like a charm.
Thanks for the reply.
I tried several types of namings, including your proposal. The method is
only started when I change it for example to onAction().
Jecki wrote:
You might want to try using the method naming convention instead of
annotation.
@OnEvent(value = reset)
public
THANKS!! That was it!
I knew it must be something trivial.
Thiago H. de Paula Figueiredo wrote:
Em Wed, 15 Oct 2008 12:16:13 -0300, moritzgilsdorf
[EMAIL PROTECTED] escreveu:
Thanks for the reply.
I tried several types of namings, including your proposal. The method is
only
Em Wed, 15 Oct 2008 12:31:15 -0300, moritzgilsdorf
[EMAIL PROTECTED] escreveu:
THANKS!! That was it!
You're welcome! :)
I knew it must be something trivial.
That should maybe be a Tapestry #1 rule: You must use t:id to give an id
to a component, not id (without the t: prefix). By the
OMG, 2 days of efforts (or even more) for this trivial thing. shame on
us :( and the credit goes to Thiago.
On Wed, Oct 15, 2008 at 11:31 PM, moritzgilsdorf
[EMAIL PROTECTED] wrote:
THANKS!! That was it!
I knew it must be something trivial.
Em Wed, 15 Oct 2008 12:48:13 -0300, Jecki [EMAIL PROTECTED] escreveu:
OMG, 2 days of efforts (or even more) for this trivial thing. shame on
us :( and the credit goes to Thiago.
That's why mailing list and forums exist: you help a little, you get
helped a little. :)
--
Thiago H. de Paula
On Wed, Oct 15, 2008 at 9:21 AM, Lubor Gajda [EMAIL PROTECTED] wrote:
Don't forget you can add new object scopes to Tapestry.
The main problem here is not definition of conversation scope, but
specification of conversation boundaries (when the conversation should
start
and when it should
I got some answers here supporting what Thiago and Geoff ranted about.
http://tapestry.apache.org/tapestry5/tapestry-ioc/
Quote :
*The core concept of Tapestry IoC is that the Java language itself is the
easiest and most succinct way to describe object creation and method
invocation. Any
Em Wed, 15 Oct 2008 10:21:39 -0300, Lubor Gajda [EMAIL PROTECTED]
escreveu:
The main problem here is not definition of conversation scope, but
specification of conversation boundaries (when the conversation should
start and when it should end and release all objects associated with
Just to bring this up. I tried several things to solve the Problem but to no
avail. I still have no clue on what is going wrong here.
I've put everything from the component into a page, nothing changed. I
testet it on several other computers, nothing. I tried it using tomcat,
nothing.
I have
No response, so I guess that means we can't add a Delete column to a
Grid any more.
On 14/10/2008, at 8:36 PM, Geoff Callender wrote:
Can anyone tell me if Penyihir's technique for adding a Delete
column to Grid still works?
Please note this is not the same as editing a flag in the
Good rant. I completely agree.
On 15/10/2008, at 12:31 PM, Thiago H. de Paula Figueiredo wrote:
Em Tue, 14 Oct 2008 20:51:10 -0300, John Jimmy Dondapati [EMAIL PROTECTED]
escreveu:
I am sorry if this has already been asked but is there anyway to
integrate Spring Web Flow 2.x with
Em Wed, 15 Oct 2008 13:03:07 -0300, John Jimmy Dondapati
[EMAIL PROTECTED] escreveu:
Looks like the fundamental idea of Tapestry is moving away from xml and
putting the IOC into code. I guess, same goes for navigation.
So, I guess there will not be a Spring Web Flow integration from Tapestry
I don't follow you ... the t: tags are components or directives in
templates, they don't get echoed out to the client browser. They are
converted into active components that render (X)HTML. Perhaps you
should expand on what is happening, and what you think should be
happening. Give examples.
On
Hi,
I've joined a project that uses Tapestry 3. (yes old version) and I have
read good things about the book 'Enjoying Web Development with Tapestry'. If
I understand correctly, the first edition is for Version 3 and the second
edition is for Version 4.
So I need the First Edition, but I can't
Sorry for the long post, but here goes.
I have a zone that contains two components in its body that i'd like to
update on a given event.
Because i can't return more than one component to update from the event
listener method i created a block inside the zone and outside the two
components and
No, actually, Keith Donald and I have discussed this repeatedly, and I
think it would be a good thing to add in 5.1. We also have ideas
about how to make Spring/Tapestry IoC integration better and more
symmetric.
We're stumbling one one thing, Keith doesn't know much Tapestry and
sees it as a
Em Wed, 15 Oct 2008 14:22:10 -0300, Hugo Palma [EMAIL PROTECTED]
escreveu:
I use the delegate to because i want the block content to be visible
when the whole page is rendered and not just after the update event.
Nice approach! But I would really like to have multiple
I would prefer multiple whatever updates too, but as long as this block
approach works i guess it's an ok workaround.
Regarding ur solution, if that was the cause shouldn't the render fail
when i add elements using the tapestry namespace to the block and not
when i add non tapestry namespace
Hi Thiago/Geoff,
In my opinion centralized flow definition can be quite useful in some
circumstances, especially in complex applications. Imagine for instance that
you have to analyze/understand application that consists of hundreds of
pages and you are not familiar with the code because it was
Uli,
I'm seeing isDelete() called as it renders the display but I'm not
seeing setDelete(boolean delete) being called on submit. Can you
please play spot the obvious error? Here's the code:
html xmlns:t=http://tapestry.apache.org/schema/tapestry_5_0_0.xsd;
body
form t:type=form
Yes, it's true.
On 15/10/2008, at 10:47 PM, StevenF wrote:
Thanks!
Is it true that the First Edition is for Tapestry 3 and the Second
Edition
is for Tapestry 4?
Andy Huhn-3 wrote:
Hi Steven,
http://www.agileskills2.org/EWDT/ has a link to the first edition.
Thanks,
Andy
On Wed,
Folks,
I cannot help thinking that somehow the rendering of components and their
positions are skewed someway... under the hood.
I am unable to calculate the position of my component on the page.
Does anyone have a reliable method for calculating x,y ?
My code lives in a *.script file
28 matches
Mail list logo
