Hmm... Seems like autoconnect does not work for me as I expect.
I checked in setupRender() inside EditorComponent and found that
'entity' is null, while Page.setupRender() assigns new value to its
same named property.
What am I doing wrong?
On Sat, Nov 7, 2009 at 7:50 PM, Alexey Hanin wrote:
>
Carl Crowder schrieb:
Agreed: the main thing Tapestry is lacking is a book that explains not
just the basics but also concepts that it takes months of working with
Tapestry to discover. Things like shadow builders and so on. I don't
care who writes one as long as there's a definitive guide!
+1
I think both are necessary to make tapestry more popular, but i think would
be better if you work on code, tapestry is already known by a lot of people,
i’m a 24 years old Mexican and in my 3 years of experience i already have
been part of 2 tapestry 5 big projects, the first last 10 months and i’
> So the question is: do I wait and see if time opens up in Q1 to
> actually start on a T5 book ... or do I jump into 5.2 coding and leave
> books to others?
+1 for coding, as there already is a very good book available (written by
Igor). Why do it twice - what's lacking is just an english transl
+1 "Bible" Book :-)
Antonio
Carl Crowder escribió:
Agreed: the main thing Tapestry is lacking is a book that explains not
just the basics but also concepts that it takes months of working with
Tapestry to discover. Things like shadow builders and so on. I don't
care who writes one as long as
There already is one - written by Igor - but unfortunately not (yet?)
available in English.
Uli
Carl Crowder schrieb:
Agreed: the main thing Tapestry is lacking is a book that explains not
just the basics but also concepts that it takes months of working with
Tapestry to discover. Things like
Agreed: the main thing Tapestry is lacking is a book that explains not
just the basics but also concepts that it takes months of working with
Tapestry to discover. Things like shadow builders and so on. I don't
care who writes one as long as there's a definitive guide!
jose luis sanchez wrote:
Book ! Book ! Book !
El 07/11/2009, a las 19:11, Howard escribió:
I've been consciously letting Tapestry 5.1 sit and stabilize for a
while ... a time that's stretched a few months longer than I initially
intended.
This is due to a number of factors: my return to independent
consulting, my desir
I've been consciously letting Tapestry 5.1 sit and stabilize for a
while ... a time that's stretched a few months longer than I initially
intended.
This is due to a number of factors: my return to independent
consulting, my desire to write a definitive Tapestry 5 book, and
preparations for many tri
Meanwhile, in spare minutes (and during sessions at ApacheCon), I've
been continuing to work on Cascade. It's been a great learning exercise
for me, pushing my understanding of both Clojure and functional
programming in general ... and especially, some pretty advanced
meta-programming with macros.
I've been doing a lot of work for a client using the ExtJS library and
that, combined with many other things I've been looking at, has started
to shift my attitude to the correct approach to client-side JavaScript.
Not a sea change, just a minor adjustment.
Until now, I've had the approach that the
Hello,
Recently I found that autoconnect-parameters are being copied instead
of being set as reference to parent parameter.
What I want is to implement various editor-components containing
BeanEditForm accessing parent property.
class Page {
@Property
private EntityObject entity;
void onSuc
Hello,
Recently I found that autoconnect-parameters are being copied instead
of being set as reference to parent parameter.
What I want is to implement various editor-components containing
BeanEditForm accessing parent property.
class Page {
@Property
private EntityObject entity;
void on
Hey,
I'm using Tapestry 5.0.18, and trying to add a localization to my app. I
found, that, Tapestry supports Localization for only certain languages, like
the static fields, in the Locale class. It works for Japanese, German,
French, etc., But, does not support indic languages, like Hindi(hi) or T
Hey,
People, I've a problem using inbuilt, i18n support of Tapestry (I use
5.0.18). K, When i use persistentLocale and set it to Locale("hi"), hi -
Hindi, its not picking up the page, Home_hi.tml or Home_hi.properties.
Instead, it uses any page like, Home.tml or Home_en.tml
Also, the same proble
Hi Paul,
thanks a lot for your mail. Not having to rebuild the registry between
tests is indeed a major consideration. I like your idea of a special
proxy that can be 'cleaned' and refreshed from a pool.
I do not need the multi-threaded testing on our web applications right
now. I mainly need it
On Sat, Nov 7, 2009 at 11:37 AM, Ulrich Stärk wrote:
> There is a validate event fired for every individual form field (handle it
> in onValidateFromFieldid()). You might also want to have a look at the
> submitnotifier component.
I guess i (my mind) was referring to the onValidate event but gon
There is a validate event fired for every individual form field (handle it in
onValidateFromFieldid()). You might also want to have a look at the submitnotifier component.
HTH,
Uli
Am 06.11.2009 18:30 schrieb Massimo Lusetti:
Does exist an hook to get "when Tapestry5 set the field in a form
s
18 matches
Mail list logo
