Hi Leonardo,
I'm not sure I've got the idea... do you think the javascript documentation
is THE big problem ? I really don't have an opinion because I didn't go
deeper in Trinidad javascript code.
In your opinion the best solution is just continue improving the current
Trinidad client code ? As
Hi Scott,
I know Oracle, for instance, has a very large renderkit extension
which is based on Trinidad Internals. Now it's mostly geared toward
support of web business applications, but it really shows what can be
done with the framework.
Do you mean ADF Rich Faces ?
Why do you say it's
Ok, now I understand...
I think it is one of the problems. Instead thinking about what it is
wrong, I'm trying to thing on which steps should we take to enhance
trinidad.
If the objective is rewrite trinidad components using a theorical
javascript library, it is necessary to take these steps
Yes, ADF Faces. The two share a similar API but ADFFces is much more rich.
It has animations, push technologies, and some other things. The
client-side JavaScript has been re-engineered as well and while it uses
Trinidad as the foundation, there is a lot more on the client side.
Suffice to
+1
On Mar 12, 2011, at 12:35 PM, Walter Mourão walter.mou...@gmail.com wrote:
Ok, now I understand...
I think it is one of the problems. Instead thinking about what it is
wrong, I'm trying to thing on which steps should we take to enhance
trinidad.
If the objective is rewrite trinidad
5 matches
Mail list logo