The link
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajaxcomponentscrud
has been replaced by:
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/componentscrud/persons
On 14/07/2010, at 7:01 AM, Geoff Callender wrote:
> Can't stop to consider the difference r
Thanks Thiago - I've read the follow ups to this from you and Josh,
and the "nevers" are good to know early on.
"...because of the page pooling" is a good enough reason to make it
register.
There seems to be a shortage of "never do this" cheat sheet library in
the 21st century :)
.java
On Wed, 14 Jul 2010 15:39:11 -0300, Josh Canfield
wrote:
HA! I guess I've been using joda-time for too long... I've always
treated Date as immutable, too bad Java 6 has to be backward
compatible with Java 1.1 or the setter methods could have been removed
a LONG time ago!
Agreed.
but I pre
HA! I guess I've been using joda-time for too long... I've always
treated Date as immutable, too bad Java 6 has to be backward
compatible with Java 1.1 or the setter methods could have been removed
a LONG time ago!
> but I prefer to give a
> short advice instead of a longer one informing the excep
On Wed, 14 Jul 2010 15:13:06 -0300, Josh Canfield
wrote:
@Property
private Date addedToJumpstart = new Date("2010-07-14");
Never initialize fields like you've done in the above snippet because
of the
page pooling. Use the activate or begin render event to initialize
fields.
In gener
>> @Property
>> private Date addedToJumpstart = new Date("2010-07-14");
>
> Never initialize fields like you've done in the above snippet because of the
> page pooling. Use the activate or begin render event to initialize fields.
>
In general that's sound advice, but if you look at the use case he
On Wed, 14 Jul 2010 11:13:07 -0300, Chris Mylonas
wrote:
.java
@Property
private Date addedToJumpstart = new Date("2010-07-14");
Never initialize fields like you've done in the above snippet because of
the page pooling. Use the activate or begin render event to initialize
fields.
--
T
jeez, some people are never pleased are they...
ideally, if all the tapestry devs that came before me would have just
built a drag and drop tapestry gui builder in html5, geoff wouldn't
have had to build and maintain jumpstart
/ducks
***Thanks for all that came before me on this list***
C
Ah, I should have realised that's what you meant. Yep, worth considering.
Thanks,
Geoff
On 15/07/2010, at 12:13 AM, Chris Mylonas wrote:
> Thanks for the reply Geoff,
>
> Safe to ignore my request/suggestion :)
>
> I meant moreso when the example "exercise/tutorial" was added to jumpstart.
>
Making the enough-but-not-overwhelming decision is always a tough one. What
*I* want is an example that shows only and exactly what I want to see at the
moment I'm looking. Oh, and I want it to come up first on whatever vaguely
related terms I put in a Google search.
I almost forgot; I also want t
Thanks for the reply Geoff,
Safe to ignore my request/suggestion :)
I meant moreso when the example "exercise/tutorial" was added to
jumpstart.
E.g. you've added more AJAX examples in the past couple of months, but
the onActivate/onPassivate example would be a couple of years old.
and I t
Chris,
Hmmm, I'm always tossing up between keeping the examples simple and making them
complete. Your request is pretty compelling so I'll consider it for the next
release. In the meantime, here's what I use in simple entities...
private java.sql.Timestamp createdAt;
private jav
Geoff that's a great example of some more advanced layout/theme
possibilities.
Sorry to hijack the thread somewhat,
Any chance of adding to jumpstart a "Date added" and/or "Last
modified" section to each example?
Cheers
Chris
On 14/07/2010, at 7:01 AM, Geoff Callender wrote:
Can't stop t
thanks josh, and geoff.
Josh Canfield wrote:
i have tried both of these approaches but neither cancel the event on the
... if yours works what is the fundamental difference?
when you click on the text only one click event is created and it
bubbles up through the dom. So it first is trigg
> i have tried both of these approaches but neither cancel the event on the
> ... if yours works what is the fundamental difference?
when you click on the text only one click event is created and it
bubbles up through the dom. So it first is triggered on the span and
then bubbles up to the a and
Can't stop to consider the difference right now (maybe later today) but you can
see it working in this example:
http://jumpstart.doublenegative.com.au/jumpstart/examples/ajaxcomponentscrud
HTH,
Geoff
On 13/07/2010, at 10:04 PM, Paul Stanton wrote:
> thanks geoff,
>
> your last post
thanks geoff,
your last post where you put the confirm mixin on a within the
is interesting .. wouldn't that be rendered as the equivalent of:
text
or at least the prototypesque version of this:
text
Event.observe($("spanId"), 'click', function(e){if (!confirm('?'))
e.stop();});
i have
http://tapestry-users.832.n2.nabble.com/Confirm-mixin-won-t-cancel-when-in-zone-td5048950.html#a5048950
On 13/07/2010, at 12:31 PM, Paul Stanton wrote:
> Hi all,
>
> I was hoping to be able to use a simple js confirm in order to
> (conditionally) cancel the callback from an async event link:
>
18 matches
Mail list logo
