Questions about RF "bootstrap components" .

[jadtn]

Hi,

All is in the subject : "In which RF release bootstrap components will be available?"

I didn't found the keyword bootstrap in any release  note on jira  for RF5 M1 or RF 5 Tracking.

Thanks

Adrien

[jadtn]

First I want to congratulate the team for richfaces bootstrap, I think now , the richfaces will lose it s princicipal default : skins, beautiful components. Seeing the demo richfacesbootstrap I no longer look than primefaces saying: mashed their interface is prettier! richfaces will be the best;) and more and more developpers will choice it.

I have some anothers questions about Richfaces / bootstrap.

.

.

A)If I understand Richfaces is now 'splitted' in 2 parts' :

•   -current components and skins (from RF4)
•   -new components richfacesbootstrap

These 2 'bundles' are not complementary but 'concurrents', they  have the 'same' components.

So in the future one of these two 'bundle' will disappear? Only richfaces bootstrap will remain?

.

.

B)When richfaces bootstrap will be release, does the old components already exists in the same release?

If yes:. For my case my application is divided in two part (in one .war) :

• 1 part for administror
• 1 part 'public' for the users

Does it will be  possible to have :

• 1 part (public in my case) wich used richfaces bootstrap
• 1 part (admin in my case) wich continue to use old component from RF4

What about the skins?It will be possible to have in the same application:

• Some pages fully 'bootstrap
• Some pages fully old skins?

(I consider to migrate in 2 times)

.

.

C) About the testability

Actually all my ui are tested with jsfunit.

• will richfaces bootstrap continue to be tested with jsfunit?
• will jsfunit upgrade to test richfaces bootstrap components?

For a migration what about the existing tests? It will be a big change?

.

.

D) Navigator compatibility

Does it mean the compatibility with differents navigator/version of richfaces bootstrap will be the same of bootstrap (if i well understanding, richfaces use a 'bridge' in front of bootstrap)?

.

.

E)About components in richfaces bootstrap:

I don't see any file upload in demo: does bootstrap will have this component in it s first release?

.

.

F)Actually, I m on the point to finish the migration  of my application from RF3.3 to RF4.3 (ouf...), and put it on production. But I think it will be more interesting (for me) to start to migrate to richfaces bootstrap if it s release date is soon (when..?). It s not interessting to me to put in production a release wich will a a short live of some months....

.

.

Thanks for your responses and sorry for my english...(thanks google translate )

Adrien

[ppitonak]

Hi,

please have a look on our RichFaces 5 roadmap [1]. Hopefully it will answer your questions.

[1] https://community.jboss.org/thread/213160

Regards,

Palo

[bleathem]

Adrien Adrien wrote:

First I want to congratulate the team for richfaces bootstrap, I think now , the richfaces will lose it s princicipal default : skins, beautiful components. Seeing the demo richfacesbootstrap I no longer look than primefaces saying: mashed their interface is prettier! richfaces will be the best;) and more and more developpers will choice it.

I have some anothers questions about Richfaces / bootstrap.

.

.

A)If I understand Richfaces is now 'splitted' in 2 parts' :

•   -current components and skins (from RF4)
•   -new components richfacesbootstrap

These 2 'bundles' are not complementary but 'concurrents', they  have the 'same' components.

So in the future one of these two 'bundle' will disappear? Only richfaces bootstrap will remain?

.

The RichFaces bootstrap components are currently a sandbox initiative.  As the components mature, we will "graduate" them out of the sandbox and into the RichFaces framework.  Where their is duplication between the new and old components, the new component will replace the old component, with the aim of being backwards compatible.

To make this overlap and gradual replacement possible, the goal is to ship with RichFaces 5 a LESS skin that makes the current components compatible (in terms of L&F) with the newer bootstrap components.

.

B)When richfaces bootstrap will be release, does the old components already exists in the same release?

If yes:. For my case my application is divided in two part (in one .war) :

• 1 part for administror
• 1 part 'public' for the users

Does it will be  possible to have :

• 1 part (public in my case) wich used richfaces bootstrap
• 1 part (admin in my case) wich continue to use old component from RF4

What about the skins?It will be possible to have in the same application:

• Some pages fully 'bootstrap
• Some pages fully old skins?

(I consider to migrate in 2 times)

.

.

I would not recommend using sandbox components in a production application.  While incubating in the sandbox, component APIs are subject to change, and they have not undergone the extensive QA as have our current components.  That being said, I do encourage you to play with the Bootstrap components and ask that you provide feedback about what you like, and what you don't.

C) About the testability

Actually all my ui are tested with jsfunit.

• will richfaces bootstrap continue to be tested with jsfunit?
• will jsfunit upgrade to test richfaces bootstrap components?

For a migration what about the existing tests? It will be a big change?

.

.

JSFUnit is being deprecated in favor of the Arquillian extensions Warp and Graphene.  One of the neat things about Graphene is the page fragments that encapsulate the DOM behind a stable API against which you will write your tests.  We are looking at shipping Graphene Page fragments as part of our framework to better enable RichFaces application developers to write stable tests.  Look for blogs on this subject in the coming months as we continue to develop these Arquillian extensions.

D) Navigator compatibility

Does it mean the compatibility with differents navigator/version of richfaces bootstrap will be the same of bootstrap (if i well understanding, richfaces use a 'bridge' in front of bootstrap)?

.

.

The javascript event bridge is used to loosely couple our new javascript "widgets" into the RichFaces framework.  By pursuing this loosely coupled architecture we are able to offer our widgets as standalone javascript libraries that can be used with any language or web framework.  Again, stay tuned for more blogs as we work out how best to deliver these standalone widgets.

E)About components in richfaces bootstrap:

I don't see any file upload in demo: does bootstrap will have this component in it s first release?

.

.

All current RichFaces visual components are targeted to be re-developed in the above mentioned architecture, including the file upload component.  However no fileupload has as yet begun.

F)Actually, I m on the point to finish the migration  of my application from RF3.3 to RF4.3 (ouf...), and put it on production. But I think it will be more interesting (for me) to start to migrate to richfaces bootstrap if it s release date is soon (when..?). It s not interesting to me to put in production a release wich will a a short live of some months....

.

.

Thanks for your responses and sorry for my english...(thanks google translate )

Adrien

RichFaces 5 will continue to build on what was started in RichFaces 4, the migration should be comparatively painless from 4 to 5.  Also, I expect the new skins developed to be optional, the components should continue to work with the old skins.  It's hard to know for certain until the LESS skin implementation is complete, but that is very much a design goal.

So don't wait for our "next generation" components, we'll be rolling them out into the frameowrk as they are ready.  Rather stay current with the RichFaces releases, and take advantage of the latest and greatest as it's ready to be consumed.

Brian Leathem