On 11/28/05, Legolas Woodland <[EMAIL PROTECTED]> wrote:
Hi
Thank you for your replys.
My question is from Mr McClanahan , does Studio creator
2 support :
1-adding new components to pallete ?
Yes. You can package a set of components (including optional
source for debugging, optional javadoc for popping up in the tool, and
optional design time code to provide a rich user experience for your
components) into a "component import library" that can be imported into
Creator.
A good starting point for information about this is an article
maintained by Edwin Goei, one of the Creator engineers:
http://wiki.java.net/bin/view/Javatools/CustomComponentLibraries
for example how i can add myface components to its
component set ?
It will take some work to set up the metadata to describe these
components to Creator, plus it would be good to put some time into
creating the design time behavior for them. I'd be happy to
assist in these efforts.
2-there is a table component which could be bind to a
data table
now :
I presume you are speaking of the Table component that is included in
Creator 2 EA?
1-does it support inline editing ? i mean it shows an
editable GUI to user based on field type ,use checkbox for boolean ,
text box for text..,
When you choose columns for your table, you also get to choose what
component goes inside the columns. They can be output or input
fields, depending on your needs (just like the standard JSF
<h:dataTable> component allows).
2-does it support saving that inline changed data ?
JSF does all that for you ... the table component itself doesn't need
to worry about it.
for example user uncheck some of check boxes , change
some
of text fields... , now how it can save them all back to database ?
On 11/28/05, Craig McClanahan <[EMAIL PROTECTED]>
wrote:
On 11/27/05, Werner Punz <[EMAIL PROTECTED]
> wrote:
If you use Studio Creator2 you will have to use the RI,
the code this tool generates is very good but roots into the com.sun
hierarchy left and right, which is not TCK, hence you will have
to use the RI and additional creator runtimes for the new
components.
As for ajax, use ajax anywhere, I have not used it yet, but it looks
very good.
Werner,
This is not quite right. The "com.sun" classes you are referring to
are *not* dependent on the JSF RI ... they are
a runtime layer on top of any standard JSF
implementation (essentially at the same place that Shale would go).
The RI is definitely used inside the tool, but you're free to replace
it in the deployed runtime application.
Craig
