RichFaces in the short-term future. What is you...| JBoss.org Content Archive (Read Only)

15. Re: RichFaces in the short-term future. What is your vision?

bruno.arruda Sep 15, 2007 11:21 AM (in response to sergeysmirnov)

I also think that the examples should always have a SIMPLEST version, I mean, if you look at the examples, most of them uses facelets, managed beans, advanced attributes, i think for the begginers user it might be a little confusing and hard-working... So I think that shold be samples that shows the core functions with maximum simplicty. Like a evolution of the livedemo page.

16. Re: RichFaces in the short-term future. What is your vision?

don_psidium Sep 15, 2007 11:29 AM (in response to sergeysmirnov)

thanks for the gorgeous framework!

my wishlist:

(1) ajax upload component (possibly with progress bar)
(2) ajax upload component (without progress bar)
(3) ajax upload component

;-)

17. Re: RichFaces in the short-term future. What is your vision?

amitev Sep 15, 2007 12:27 PM (in response to sergeysmirnov)

"don_psidium" wrote:
thanks for the gorgeous framework!

my wishlist:

(1) ajax upload component (possibly with progress bar)
(2) ajax upload component (without progress bar)
(3) ajax upload component

It's not allowed to upload files with XHR due to security reasons.

18. Re: RichFaces in the short-term future. What is your vision?

amitev Sep 15, 2007 12:31 PM (in response to sergeysmirnov)

"bruno.arruda" wrote:
Hi Sergey,

4- If you say it is really easy to do "toys", I give you a suggestion, make a little specification about the Rich Toys, than make an area on the site or forum or whatelse to the users contribute their toys, you do´nt need to include them on the richfaces library, it should be the components plug and play that JSF always dreamed, but we REALLY need a specification for simplicity and avoid mess.

I agree with this. Something like richfaces sandbox will be a good idea really!

19. Re: RichFaces in the short-term future. What is your vision?

demetrio812 Sep 15, 2007 2:20 PM (in response to sergeysmirnov)

HI!
first of all thanks for the richfaces framework!

the first thing I would like is to find more documentation on CDK coz I also want to make a lot of "toys" but with more documentation I can make better components (to upload in a sandbox, it's a good idea for me too)...

The second very important thing for me it's to give more functionalities to rich:dataTable like sorting and filtering:

http://www.teamdev.com/quipukit/demo/datatable/DataTable_sortingAndSelection.jsf
http://www.teamdev.com/quipukit/demo/datatable/DataTable_filteringAndPaging.jsf

Also I would like to have more layout components (now I have to use panelGrid, panelGroup and html), expecially for making user forms (using skin).

Also I would like to use seam components in an ajax way and it would be cool, very cool, if the framework could change the browser URL from an ajax call (to maintain the page bookmarkable) (I saw it in the new version of backbase).

Also I think that it it very important to make a floating version of messages like with an animation and they come from the top, stay for a while, and then go away because if I have the page scrolled and there is, for example, a validation error after an ajax call I can see the error (I have to scroll up to see what is happening)...I think this would be great...

About new components here it is the list in order of importance:

1. file uploading (with or without progress bar): by now I have to use a workaround with a lot of problems and bad design.

2. javascript skinnable listbox (http://www.teamdev.com/quipukit/demo/dropdown/dropDownDefault.jsf) coz I can't skin in firefox the standard listbox

3. inline input text editor (like flickr): actually I do it with togglePanel but it would be very usefull to have one

4. dialogs framework (to ask questions and get response) (http://www.teamdev.com/quipukit/demo/confirmation/ConfirmationDefault.jsf): actually I use javascript

5. contextual menu

6. selectMany boxes (http://www.teamdev.com/quipukit/demo/twolistselection/TwoListSelection.jsf)

7. more position for tabs (left vertical, right vertical, bottom) and tabset (tabs without container)

8. hint label (http://www.teamdev.com/quipukit/demo/hintlabel/HintLabel.jsf)

9. xHTML editor

10. predefined effects inside components with an on/off switch

Sorry for the long list :)

Keep in mind the cdk doc and sandbox idea coz I would be glad to help with (simple) components...

Demetrio Filocamo

20. Re: RichFaces in the short-term future. What is your vision?

don_psidium Sep 16, 2007 6:02 PM (in response to sergeysmirnov)

"amitev" wrote:
"don_psidium" wrote:
thanks for the gorgeous framework!

my wishlist:

(1) ajax upload component (possibly with progress bar)
(2) ajax upload component (without progress bar)
(3) ajax upload component

It's not allowed to upload files with XHR due to security reasons.

come on amitev, you know what i mean.
ajax-like upload.. over iframe/swf/whatever

21. Re: RichFaces in the short-term future. What is your vision?

dastei Sep 17, 2007 1:42 AM (in response to sergeysmirnov)

The independents of mouse interaction with useable keyboard interaction.

My company works for government institutes, because that my wish is more support the make RichFaces applications accessible to paradigm of W3C ARIA, WCAG or other guidelines like that.

22. Re: RichFaces in the short-term future. What is your vision?

sergeysmirnov Sep 17, 2007 3:32 PM (in response to sergeysmirnov)

"baz" wrote:

There are some questions that bothered me:
Is it possible to integrate richfaces with other component librarys?
Why do we have to implement each component in each library?
I do not know the answers to this question. But i will be happier if i know them:-)

If you look at the JSF Matrix ( http://www.jsfmatrix.net/ ), you can see that a "Combinable" row is almost empty except two libraries that says their are OK with RichFaces (Ajax4jsf). So, we are not in the bad position in general. Our strategy from the very beginning was a keeping the compatibility with others. However, we have no power to force "partners" to think about compatibility as a first priority task.
It seems for me that only QuipuKit (DevTeam) thinks about this topic seriously.

Now, about why (a quote from the past):

AFAIK, mostly, available advanced JSF component libraries are incompatible with each others. The hundreds components is on the marketplace in total. However, end developer has to select the particular library from a particular component provider instead of selecting what she needs from the all available on the component marker. Once the library is selected, developer starts to complain that the selected library has no desirable components that other libraries have.
This screaming forces component providers to create the same set of components instead of concentrating on creating the unique ones. Components provider who create such components (like chart or industrial components) face the same problem of incompatibility with other component sets.

The huge portion of code in the modern component libraries is not components themselves, but the frameworks that serve the components. Those are adding Ajax capability, resource (assets) management, skinning (if any), state management etc. Exactly those frameworks are primary culprits in libraries incompatibility.

The components support stuff is a subject to be standardized at least on API level, but it will be better that JSF implementation include the
implementation.

23. Re: RichFaces in the short-term future. What is your vision?

sergeysmirnov Sep 17, 2007 6:45 PM (in response to sergeysmirnov)

"AlexanderBelov" wrote:

It would be very usefull to give opportunity developers to send their own components to richfaces team. This way we shall have a change to exchange components. Later the best of them could be added to main richfaces library. I mean the need a community to make components faster. I have sent you client validation library, but have founded and fixed several bugs for today. I really can help by my component, but they cannot be tested good while they are not in Richfaces library. And it is a problem.

The list of contributors is not closed. Actually, we already has contributed outside of Exadel and JBoss dev team.

Some key requirements:
1. You have to be agree with LGPL license terms
2. The code should be integrated into RichFaces Component Factory (based on CDK)
3. Be open for additional requirements and possible refactoring

24. Re: RichFaces in the short-term future. What is your vision?

sergeysmirnov Sep 17, 2007 6:53 PM (in response to sergeysmirnov)

"demetrio812" wrote:

8. hint label (http://www.teamdev.com/quipukit/demo/hintlabel/HintLabel.jsf)

What is the difference between this "hint label" and rich:toolTip ?
See http://livedemo.exadel.com/richfaces-demo/richfaces/toolTip.jsf , "Use ToolTip with DataTable" tab

25. Re: RichFaces in the short-term future. What is your vision?

baz Sep 18, 2007 1:44 AM (in response to sergeysmirnov)

Sergey, thanks for the jsfmatrix.net link. It proved out very valuable
Ciao,
Carsten

26. Re: RichFaces in the short-term future. What is your vision?

baz Sep 18, 2007 2:12 AM (in response to sergeysmirnov)

Another 2 cent from me:-)

Documentation
On the weekend i have read the documentation for 3.1.0 from page 1 to page 397.
IMHO, the documentation has to be improved in a very short term.
It should be much shorter and simultaneous grow in content.
What i mean by this:
the attribute tables lists each and every attribute with a short explanation. It would be nice if attributes could be grouped. Each group is explained in detail only once. And the attribute tables will only list the groups and those attributes which are unique for the component described.

I have not understand the usage of rowKeyVar, ajaxKeys, eventsQueue, data. and some others. The concepts behind this need much more documentation.

New components
dynamic columns
Some people demand dynamic columns in data table. We are happy with ui:repeat,c:foreach or a4j:repeat
But there is one exception: matrix representation.What we really need is a component for displaying matrices with column and row headers.
The row headers should be configurable display on left,right or both sides.

For clarification: a matrix is a thing where each cell displays the same type. the number of rows are not known
Whereas a data table displays a finite number of columns with different meanings.
We ae in favour of an matrix component.

file upload
Many people are wanting a file upload component. I, personally, am happy with the component from seam. Since this component is written with the CDK it,imho, could not be so hard to create a component which does not depend on seam. But for my case, i will use the seam dependent one.

multiple selection
This is quite usefull in shot term perspective.
I imagine 2 components.
One, which is called in trinidad selectManyShuttle (and the ordered variant)
The other should look like table row selection from icefaces demo (http://component-showcase.icefaces.org/component-showcase/) Possible with drag and drop of rows.

Ciao,
Carsten

27. Re: RichFaces in the short-term future. What is your vision?

sergeysmirnov Sep 18, 2007 6:17 PM (in response to sergeysmirnov)

I have create a wiki article with overview on this thread:
http://labs.jboss.com/wiki/RichFacesFuture

28. Re: RichFaces in the short-term future. What is your vision?

baz Sep 19, 2007 1:14 AM (in response to sergeysmirnov)

Thanks for the wiki entry. Great job.
One question:
How does my matrix fit in?

a matrix is a thing where each cell displays the same type. the number of rows are not known
Whereas a data table displays a finite number of columns with different meanings.

And a matrix should have row and column headers.
Ciao,
Carsten

29. Re: RichFaces in the short-term future. What is your vision?

demetrio812 Sep 19, 2007 3:13 AM (in response to sergeysmirnov)

"SergeySmirnov" wrote:
"demetrio812" wrote:

8. hint label (http://www.teamdev.com/quipukit/demo/hintlabel/HintLabel.jsf)

What is the difference between this "hint label" and rich:toolTip ?
See http://livedemo.exadel.com/richfaces-demo/richfaces/toolTip.jsf , "Use ToolTip with DataTable" tab

I know the tooltip with dataTable...but I think it is different from hintLabel (both usefull for me)...

the use of hint label explain the difference:

<q:hintLabel style="width: 100px;" value="#{ForumMessages.topic}"/>

in this case, only the text that fits in 100 pixels is displayed. If the user moves the mouse pointer over the HintLabel component, the full text will appear in the tooltip.

(if can find the full description of the component here: http://www.teamdev.com/quipukit/documentation/developersGuide/hintlabel.html)

so It is used just to put a lot of text in a table without modifying the size of cells: the comp will cut the text and you see the whole string going over with mouse.

I think it's more simple and limited of tooltip but more simple to use too...

did I explained well? (sorry for bad english)

demetrio