myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Punz <>
Subject Re: [Trinidad] "Best" Javascript package to use in a new render kit
Date Fri, 11 Mar 2011 23:22:05 GMT
Hi, we are very interested, btw. we probably have to read our own parts 
for the inheritance stuff, because we use inheritance, delegation
and singletons as structural core patterns ourselves in the core.
So if the tool needs meta information in this regard we will have to 
readd our own implementation stuff here.

Oh well I guess this is the krux of using a dynamic lanugage which does
not have inheritance and namespaces baked into the core itself.

I guess for every framework used all this information on how to deal 
with it must be added and hence tools like jsdoc simply fail on more 
complicated cases or frameworks which do not belong to the more popular 


Am 11.03.11 18:43, schrieb Scott O'Bryan:
> So I did do some checking on this and we have something we are using
> in-house here at Oracle. It uses a more robust javascript parser to
> generate the Javadocs and even allows the code to be annotated to
> produce much cleaner documentation. The only bad thing about it is that
> we have some parsing for inheritance that is probably specific to our
> richclient.
> I talked with the guy who wrote and and he'd be willing to donate it if
> people are interested. He said ripping out the proprietary stuff for
> inheritance should be pretty easy and then the MyFaces community could
> enhance to to allow the docs to work on our own stuff. Are people
> interested?
> If so, I can open up a discussion on the dev list with the specifics.
> Scott
> On 03/10/2011 10:59 AM, Scott O'Bryan wrote:
>> Very good points Leonardo, and your right about Trinidad's parser. I
>> do know that I've seen some stuff in-house which generates
>> javascriptDoc and even does auditing. Let me check to see if it's
>> something we can donate or if it's too specific to our legacy code..
>> On Mar 10, 2011, at 10:35 AM, Leonardo Uribe<> wrote:
>>> Hi
>>> I think one of the problems right now it is necessary to overcome is
>>> create
>>> a javascript documentation maven plugin for trinidad, myfaces core
>>> 2.0.x,
>>> and probably tobago.
>>> If you take a look at the sites of those projects, you'll see there is
>>> generated javadoc, tlddoc, facelets-tlddoc and other documentation
>>> reports
>>> available on the site. But there is not anything for javascript.
>>> The reason is there is not a maven plugin written in java that do the
>>> job.
>>> In theory it is possible to use jsdoc toolkit, but unfortunately
>>> there is
>>> some code on myfaces core that by its structure can't be documented
>>> properly
>>> with that tool (I already tried it, it just don't), and mozilla rhino
>>> causes
>>> some problems when the goal is executed, because it loads the javascript
>>> file too.
>>> This is a good idea for a Google Summer Of Code, because in practice
>>> half of
>>> the solution is done. Trinidad javascript plugin contains a code that is
>>> capable of parse javascript files (look the obfuscator), so what we
>>> need is
>>> use this code and create some code that scan for doclets (annotations
>>> on the
>>> comments), get the information and build a model and finally generate
>>> the
>>> documentation using a template tool like velocity. Again we have already
>>> some code on myfaces builder plugin that could be useful.
>>> Trinidad code is very robust. With JSF 2.0, we have a common ajax
>>> framework,
>>> so in theory it is possible to create custom ajaxified components and
>>> make
>>> them work together with trinidad. But I think what users wants is to
>>> know
>>> the details behind it and how they can extend or override trinidad
>>> stuff.
>>> regards,
>>> Leonardo Uribe
>>> 2011/3/10 Scott O'Bryan<>
>>>> Walter,
>>>> Yeah, while creating a new renderkit isn't trivial, the Trinidad
>>>> internals and API really lend themselves to allowing extensions to the
>>>> framework.
>>>> 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.
>>>> I really would like to see a project like this get some traction
>>>> personally. ;)
>>>> Scott
>>>> On Mar 6, 2011, at 5:39 AM, Walter Mourão<>
>>>> wrote:
>>>>> Thank you Dominik.
>>>>> Just to be clear: the aim is not simply compete...
>>>>> I think Trinidad has:
>>>>> - rock solid back-end;
>>>>> - support to non-javascript browser (I have applications running in
>>>>> old
>>>> data
>>>>> collectors - windows mobile)
>>>>> ...
>>>>> and I would like to keep most of the java code untouched when
>>>>> migrating
>>>> my
>>>>> applications to an "up to date UI".
>>>>> I am personally highly involved in another open source project and I
>>>> don't
>>>>> have much experience with JSF/Trinidad internals. I am not sure I can
>>>> help
>>>>> much in such a task (create the new render kit), but I'm
>>>>> experimenting to
>>>>> see if I should go ahead with Trinidad or just migrate to another
>>>> library.
>>>>> Best regards,
>>>>> Walter Mourão
>>>>> 2011/3/6 Dominik Dorn<>
>>>>>> If you're really want to compete with PrettyFaces, IceFaces,
>>>>>> RichFaces
>>>>>> etc.,
>>>>>> I suggest to take a look at
>>>>>> and rebuilt those for JSF.
>>>>>> Sproutcore is currently quite hyped in twitter and gains a lot of
>>>>>> interest, especially
>>>>>> in the rails community.
>>>>>> 2011/3/6 Walter Mourão<>:
>>>>>>> Hi folks,
>>>>>>> following the thread "Concerns about the future of Trinidad"
I would
>>>> like
>>>>>> to
>>>>>>> know the opinions about the "best' Javascript package to use
as a
>>>>>>> base
>>>> to
>>>>>> a
>>>>>>> new Trinidad render kit.
>>>>>>> JQuery<>
>>>>>>> Dojo Toolkit<>
>>>>>>> (another options ?)
>>>>>>> What do you think ? what about the licensing ?
>>>>>>> Thanks,
>>>>>>> Walter Mourão
>>>>>> --
>>>>>> Dominik Dorn
>>>>>> Tausche Deine Lernunterlagen auf !

View raw message