Hi Thiago,
I just thought of another idea and would like to bounce it off you. Instead
of subclassing AbstractTextField to create NumericField, I can just use
TextField as is, but define a new binding prefix for the translate parameter
which will allow the format pattern to be specified as the bin
On 23.12.2009 22:37, Thiago H. de Paula Figueiredo wrote:
> Better documentation and examples are a very good idea. :)
> Demo projects would really help. Something like the Guice introduction
> would be nice.
I hope we (our team) will soon agree with the licencing issues of our
own project and open
Thanks Thiago, that helped me a lot.
Unfortunately it seems that it does not help against these error-bubbles.
Piero
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h.
> Agreed. Don't forget to check the third-party packages in the Tapestry home
> page.
Talking about these..
It would be great to tag them defining what they are about:
* projects using tapestry (like InterLDAP)
* projects providing extensions
* showcase / tutorial projects
Outdated:
* Godcode Co
Em Wed, 23 Dec 2009 19:19:17 -0200, Alfonso Quiroga
escreveu:
Hi! very interesting thread. I use T5 since 1 year aprox, and it's
true that T-IOC was the first "wall" I had, now I understand it and I
like it a lot (my system does NOT use spring, all with t-ioc). I don't
know which is the solut
Hi! very interesting thread. I use T5 since 1 year aprox, and it's
true that T-IOC was the first "wall" I had, now I understand it and I
like it a lot (my system does NOT use spring, all with t-ioc). I don't
know which is the solution, because there is documentation about
t-ioc, but maybe more docu
A few thoughts from this discussion:
Tapestry site needs:
1. immediately visible search field over all valuable resources, like wiki.
We were discussing custom google search that makes it.
2. A few more diagrams, like
http://tapestry.apache.org/tapestry5.1/images/component-render-states.png
> Wicket itself doesn't. Nor does JSF. (all this as far as I know and I google
> it)
JSF does not qualify as framework IMHO. Seam brings security.
Agreed on chenillekit.
By the way, it would be nice to have something like wicketstuff.org :-)
> Regarding JDO, its implementations need for class en
Em Wed, 23 Dec 2009 17:37:24 -0200, Piero Sartini
escreveu:
For me, authentication is an important part of a web framework and
should provide some standard way to do so.
Wicket itself doesn't. Nor does JSF. (all this as far as I know and I
google it)
There is a third-party package for W
Hi!
I'd never tried to override the default ValidationDecorator.
It adds the "invalid-field" CSS class to fields that have validation
errors and to their labels. For each required field, it adds an asterisk
after its label. In addition, it writes the error message after the field
inside a
> More freedom, more control, more complex. Quite hard to avoid that.
Agreed. The challange is to define what parts need to be customized
often, and should be easy to change. For me, these bubbles should be
easy to change.. but as always, others may have a different oppinion.
> I cannot speak fo
Em Wed, 23 Dec 2009 16:22:49 -0200, Piero Sartini
escreveu:
I wrote that because of the @PersistenceContext. That's the only thing,
AFAIK, that would be different from tapestry-hibernate.
From a users perspective, its a matter of injecting EntityManager
instead of hibernate's Session.
In th
> I wrote that because of the @PersistenceContext. That's the only thing,
> AFAIK, that would be different from tapestry-hibernate.
>From a users perspective, its a matter of injecting EntityManager
instead of hibernate's Session.
In the module itself there are more changes.
> You can do this in
Em Wed, 23 Dec 2009 15:42:20 -0200, Piero Sartini
escreveu:
I know... but your CRUD package is not tapestry.
It's a Tapestry extension that I plan to contribute to Tapestry itself
when is good enough (a.k.a. it has unit tests).
That's your oppinion... my feeling is the opposite. On its
> Select models out of beans could be improved. My Tapestry CRUD package has a
> solution for that.
I know... but your CRUD package is not tapestry.
> You're talking about a snapshot. This behaviour was changed and now
> everything in the context is allowed.
Hey.. this was no complain, you asked
Em Wed, 23 Dec 2009 14:01:03 -0200, Benny Law
escreveu:
Hi Thiago,
Hi!
should be displayed. Where I got lost is figuring out how to provide the
custom translator from within NumericField.
In this case, I think it would be easier to not use a translator and do
the conversion yourself.
While it's true that other frameworks (Grails, Wicket, Rails) have
large numbers of integrations, if you talk to real developers you find
out that the majority of those integrations are not actually usable
for production work. All too often, they are orphaned, unsupported,
incomplete, naive or code
Hi Thiago,
I finally got some time to revisit this. I spent some time last night trying
to subclass AbstractTextField as you suggested, but got lost. I would
appreciate it if you or anybody else could give me some pointers. What I am
trying to do is to create a NumericField by extending AbstractTe
Noe, I've been down this path before, regrettably. The ONLY thing to
do it to ignore the trolls.
On Tue, Dec 22, 2009 at 11:29 PM, Newham, Cameron wrote:
> I don't agree with the OP that the ServerSide discussion shows Tapestry "has
> lost the battle" - two posters state they don't want to see
Em Wed, 23 Dec 2009 12:07:21 -0200, Alessandro Bottoni
escreveu:
Hence, the relatively scarce fame of Tapestry can be considered a
problem in itself. If few people know Tapestry and few people write few
code and support it, then the whole framework became less palatable.
Maybe, we should do s
Il 23/12/2009 13:45, Thiago H. de Paula Figueiredo ha scritto:
> I think you're looking for the cause in the wrong places. I guess these
> integratiosn weren't written just because, unfortunately, Tapestry is
> not very well-known, so few people use it and write extensions and
> integrations.
Hen
Em Wed, 23 Dec 2009 11:20:41 -0200, Piero Sartini
escreveu:
What concepts exactly?
Starting in the frontend, there are concepts like the static
structure, dynamic behaviour, the Environment and the Assets which are
hard to get. Thats what I remind of fighting with some months ago.
Also the
> There's also JavaConfig and use of annotations instead of XML, but
> Tapestry-IoC still looks better to me. And Spring doesn't have distributed
> configuration.
At the time I had a look at Spring it didn't have this ;-)
> What I meant is that it is hard to find your
>> way around the IoC concep
Em Wed, 23 Dec 2009 10:14:53 -0200, Alessandro Bottoni
escreveu:
As a newbie, I have to say that learning Tapestry (5) is actually a
little bit more complicated than what you could expect after having read
the available "marketing" documentation.
This is a known issue.
Maybe this (apparen
Em Wed, 23 Dec 2009 10:13:59 -0200, escreveu:
Please give us some examples of hard-to-build modules.
Distributed configuration is great for something simple, but to use it
for something more involved can be tricky, for example Tapestry IoC
provides the platform for developing IoC services,
Il 23/12/2009 11:28, Piero Sartini ha scritto:
>> I have an idea, may be a controversial one. I've seen much about Tapestry
>> and think it's a nice Framework. But what I still don't understand is why
>> it's not widely in use. It existed before Wicket but Wicket is far more
>> popular. I don't thi
> Please give us some examples of hard-to-build modules.
Distributed configuration is great for something simple, but to use it for
something more involved can be tricky, for example Tapestry IoC provides the
platform for developing IoC services, but doesn't follow through with web
services inte
Em Wed, 23 Dec 2009 09:20:05 -0200, Piero Sartini
escreveu:
I never liked Spring because of its XML configuration.
There's also JavaConfig and use of annotations instead of XML, but
Tapestry-IoC still looks better to me. And Spring doesn't have distributed
configuration.
I like guice
>> I've also thought about this, and my only conclusion is that Tapestry is
>> too difficult to master. Especially when it comes to tapestry-ioc and
>> getting productive with it.
>
> What exactly is difficult to master? I think Tapestry-IoC is easier to learn
> than Spring.
> Maybe there's a sensa
Em Wed, 23 Dec 2009 08:28:35 -0200, Piero Sartini
escreveu:
I am not sure if it is possible or not to integrate CDI without
breaking backwards
compatibility... but it is something we should find out.
Agreed. :)
I've also thought about this, and my only conclusion is that Tapestry is
too
--
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Please visit http://www.albourne.com/email.html for important
additional terms relating to this e-mail.
> I've also thought
Hi list,
I just ran into a problem while trying to use the TriggerFragment Mixin
inside a Loop-component...
The loop should iterate over some list of elements and for each element
there should be a radio button, which should make one formFragment
visible. In the end there is one single radio
> Having seen some discussions in the past about the history of Tapestry, I'm
> wondering what the status of Tapestry with CDI support will be. In other
> words, is it again going to result a new major release incompatible with
> previous versions? I think CDI in it's current form, if should be sup
Em Wed, 23 Dec 2009 08:21:23 -0200, Peter Stavrinides
escreveu:
There's a recent discussion about that in the dev mailing list. Everyone
is invited. :)
Thiago could you provide a link perhaps?
Yes! :)
http://old.nabble.com/JSR-229%2C-JSR-330-and-other-integrations-to26857781.html
--
Th
Em Wed, 23 Dec 2009 07:59:47 -0200, Gerald Bauer
escreveu:
Lutz,
Hi!
Having seen some discussions in the past about the history of Tapestry,
I'm wondering what the status of Tapestry with CDI support will be. In
other
words, is it again going to result a new major release incompatibl
> There's a recent discussion about that in the dev mailing list. Everyone
> is invited. :)
Thiago could you provide a link perhaps?
--
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistri
Use Event.observe for the form and use the validation with custom JS of
urs...
HTH
- Ashwanth Kumar
On Wed, Dec 23, 2009 at 3:48 PM, Kenneth CH, LEE wrote:
> There is a submit button within the form. I could not attach the code
> in onclick handler because I want it to run only if the form is
There is a submit button within the form. I could not attach the code
in onclick handler because I want it to run only if the form is valid.
2009/12/22 Ashwanth Kumar :
> On Tue, Dec 22, 2009 at 6:14 PM, Kenneth CH, LEE wrote:
>
>> Hi there,
>>
>
> Hello,
>
>
>>
>> Is there any existing facilitie
Lutz,
Having seen some discussions in the past about the history of Tapestry, I'm
wondering what the status of Tapestry with CDI support will be. In other
words, is it again going to result a new major release incompatible with
previous versions? I think CDI in it's current form, if should be supp
Em Wed, 23 Dec 2009 06:25:14 -0200, Lutz Hühnken
escreveu:
Hi everybody,
Hi!
So the interesting (to me, at least) questions are:
- How does CDI relate to Tapesty and Tapestry IOC?
- Should / could Tapestry incorporate / conform to CDI somehow?
- Should we try to add Tapestry support to We
Hi everybody,
I think the discussion on TheServerSide actually is somewhat
interesting, but not because of the unfortunate Tapestry vs. Wicket
flame war. Let's have a look at the topic leading to that...
- One part of Java EE 6 is "CDI" (JSR 299) -
http://jcp.org/en/jsr/detail?id=299 - originall
41 matches
Mail list logo
