Re: [Studio Creator] Re: Can we use several package of jsf components together ?

[Werner Punz <we...@gmx.at>]

Hi Edwin - Craig , it sort of becomes OT,
but I have been toying around
with Creator2 and it becomes amazing.
I created 3 data aware forms in no time.

But there are some issues which struck me.

a) EJB functionality for creating that stuff seems
to be not there
(EJB3 especially slowly becomes interesting
with session beans being the source as data providers)

b) What struck me, and had stricken me before is
that there is lots of functionality in base classes.
While this makes sense in the case that some rendering phase
stuff has been simplified and you have simplified access
to the managed bean handling, it roots into the com.sun hierarchy.
While this is not bad per se, is there the sourcecode to
all this available, and if yes under which license.

(Besides that I am not too much of a fan of pushing
functionality into base classes because you loose your one and only
possibility of inheritance, but that is more a personal issue)


But besindes that an amazing tool, I am really looking
forward to use it seriously one time in the future.
It definitely is a big contender for being the best JSF ide
currently available. (Version 2 I mean, I never was happy with version 1
due to its limitations)

What I really liked first was the user interface designer and
also the idea of having visual compound componentization via partial 
forms was excellent.

I am really looking forward to see more of myfaces in this thing.
having more components can never hurt although the component set already 
is impressive.


Werner



Edwin Goei wrote:
> Martin Marinschek wrote:
> 
>> It would certainly be great to have support like this.
>>
>> Is there anything of this that can be generated? We have some
>> generating mechanism already in place, you'd need to hook up with
>> either Thomas or Manfred to find out how that works.
>>  
>>
> I've been working on getting some of the myfaces tomahawk components to
> work in Creator.  I'm an engineer on the Creator team and think it would
> great to see more third party components work in the tool.  So far I
> have the t:inputCalendar sort of working and am working to get one of
> the tree components to work but have run into problems.  For one thing,
> Creator expects that tag attributes are also component bean properties
> which is not true of t:tree2.  So some of the runtime code needs to be
> changed in cases like this.  There are other problems too though.
> 
> In any case, I am definitely interested in collaborating on work like
> this.  I've seen the anouncement on the Cherokee components which I'm
> also interested in helping on.
> 
> I haven't yet looked at the generating mechanism you mentioned.  I know
> that Creator has its own set of components that also go through a
> generation process.  I'd be interested in finding out more on this.  So
> far, I've only looked at tomahawk.jar as a black box.
> 
> -Edwin
> 
>> regards,
>>
>> Martin
>>
>> On 1/1/06, Laurie Harper <la...@holoweb.net> wrote:
>>  
>>
>>> Craig McClanahan wrote:
>>>   
>>>
>>>> On 12/31/05, Matthias Wessendorf <mw...@gmail.com> wrote:
>>>>     
>>>>
>>>>> Hi Legolas,
>>>>>
>>>>> I haven't used Studio Creator w/ MyFaces' tomahawk (or sandbox). But
>>>>> you should be able (as Alexandre pointed out) to *use* MyFaces stuff
>>>>> in Creator.
>>>>>
>>>>> Currently there is no *design time* support for Creator from our side.
>>>>> Craig mentioned by time, that one of his fellow-workers blogged (or
>>>>> just wrote a *normal* article) about howto write that Creator specific
>>>>> design time support.
>>>>>       
>>>>
>>>> On that topic, I'm interested in working on the design time support 
>>>> for the
>>>> MyFaces components, so that they run nicely in Creator, and 
>>>> contributing it
>>>> back to the MyFaces project.  We get this request (MyFaces 
>>>> components with
>>>> Creator) from time to time on the Creator forums, and I've seen it
>>>> increasingly here as well.  Would that be of interest to people here?
>>>>     
>>>
>>> It'd be interesting to me :-) I thought about doing this myself but got
>>> side tracked looking at ADF Faces, then switched to jDeveloper as it
>>> already has this design time support for ADF Faces...
>>>
>>> I'm probably going to switch back to Tomahawk instead of ADF Faces as
>>> ADF apparently can't cope with a user agent with no Javascript 
>>> support :-(
>>>
>>> If I do, I'll reevaluate jDeveloper vs. Creator and may well be willing
>>> to help out with this.
>>>
>>> L.
>>>
>>>
>>>   
>>
>>
>>
>> -- 
>>
>> http://www.irian.at
>>
>> Your JSF powerhouse -
>> JSF Consulting, Development and
>> Courses in English and German
>>
>> Professional Support for Apache MyFaces
>>
>>  
>>
> 
> 
> 
> 

Re: [Studio Creator] Re: Can we use several package of jsf components together ?

[Craig McClanahan <cr...@apache.org>]

On 1/2/06, Werner Punz <we...@gmx.at> wrote:
>
> Hi Edwin - Craig , it sort of becomes OT,
> but I have been toying around
> with Creator2 and it becomes amazing.
> I created 3 data aware forms in no time.
>
> But there are some issues which struck me.
>
> a) EJB functionality for creating that stuff seems
> to be not there


Correct ... Creator 2 is about *consuming* web services and EJBs that
already exist. I like NetBeans 5 for doing the creation part.

(EJB3 especially slowly becomes interesting
> with session beans being the source as data providers)


EJB3 (or, more generally, the Java Persistence API -- and the new web
service JSRs for that matter) is definitely something we're looking at for
the next round.  These specs are not final yet, though, so we don't really
want to make Creator 2 wait for them.

b) What struck me, and had stricken me before is
> that there is lots of functionality in base classes.
> While this makes sense in the case that some rendering phase
> stuff has been simplified and you have simplified access
> to the managed bean handling, it roots into the com.sun hierarchy.
> While this is not bad per se, is there the sourcecode to
> all this available, and if yes under which license.


The source code is available (just not in an obvious place) -- see "rave2.0
/docs/appbase-src.zip" in your Creator install.  You can attach a library
reference to this, for example, if you need to debug through these classes.
There are javadocs as well, which are accessible under the "Application
Model Reference" topic under Dynamic Help.

All of the EA release is under an "evaluation only" license.  For the
upcoming final release, you'll be able to redistribute the application model
classes (as well as Creator's component library) with your apps.

(Besides that I am not too much of a fan of pushing
> functionality into base classes because you loose your one and only
> possibility of inheritance, but that is more a personal issue)


That's one of the places we made a tradeoff for code simplicity.

But besindes that an amazing tool, I am really looking
> forward to use it seriously one time in the future.
> It definitely is a big contender for being the best JSF ide
> currently available. (Version 2 I mean, I never was happy with version 1
> due to its limitations)


We like Creator 2 a bunch as well :-).

What I really liked first was the user interface designer and
> also the idea of having visual compound componentization via partial
> forms was excellent.
>
> I am really looking forward to see more of myfaces in this thing.
> having more components can never hurt although the component set already
> is impressive.


There's no such thing as too many components :-).

Werner


Craig