[robertgary1]

I'm curious if the roadmap includes re-introducing some of the coolest features of extendedDataTable from 3.X that were available on the top menu including...

1) Abily for user to make columns visible/invidible

2) Grouping

-Robert

[lfryc]

Hi Robert,

not all features has been re-introduced from 3.x and we are tracking interest in their re-introduction in issue tracker.

However you still have possibility to adopt current components to your needs by either wrapping them as JSF composite component or modify their source.

We would welcome your story in the forums!

1) this could be simply implemented with current EDT and custom header. (You could open new topic on RichFaces Users space if you need any help)

2) I haven't found any request to migrate this feature to 4.x, could you please open feature request so we can track it?

[robertgary1]

I agree that most of the featuers in the 3.3.3 version of extendedDataTables can be recreated by the user. However, the ability to dynamically assign a column to be a subtable group was really powerful. Would it be useful to offer this feature in a future release?

I've created enhancement https://issues.jboss.org/browse/RF-11914 to track this.

-Robert

[sunkaram]

when would be the approximate release date for 4.3. I am looking for Richfaces ADA Compliant components..

[kwutzke]

Feature requests for page layouting and gmap components are here:

https://issues.jboss.org/browse/RF-11956

https://issues.jboss.org/browse/RF-11957

Please vote if you're interested as well.

Karsten

[bleathem]

A lot has changed since we started this thread - with a 4.2 release out addressing many of the issues raised in this thread.  Originally slated to be a 4.1.1 release, we renamed it to 4.2, since the added components, push configuration changers, and resource loading optimisation improvements really warranted a rev in the minor revision number.

We’ll fall back into our regular release cycle and start planning the milestone releases for RichFaces 3.  Overall, Richfaces 3 will focus on

• new features/fixes for existing components
  • "Big topics include"
    • Support for lazy-laoding of ajax rendered components
    • Improved MyFaces compatibility (some known issues went unadressed in the 4.1 dev cycle)
  • As for other indiviudal comopnent fixes and improvements, I'll put out a call for votes on short-listed jira issues shortly
• Improved testing infrastructure
  • Discussion underway in a parallel thread: https://community.jboss.org/thread/177821?tstart=0
• A new component set initative
  • focusing on a rapid turnaround of on new comoponents
  • Discussion underway in a parallel thread: https://community.jboss.org/thread/177406
• CDK improvements
  • We'll start a dev forum discussion on this topic shortly, but in short this will help us with our new rapid-component-turnaround initiative

Thanks everyone for your feedback, and keep the ideas coming in.

[feuyeux]

I wanna know if the a4j:ajax's features have been finished?

I don't think its event and listener attributes can work, at any time.

What I used from 4.0 to 4.2.

[lfryc]

Hi Lu Han, have you reported any JIRA issues or opened a forum thread?

It is possible that you have just misused these attributes?

Btw I don't really think that such a question belongs to the Roadmap/Planning-kind of thread.

If you want us to fix the issue, send a patch, vote on the issue or come to our regular meeting to say us that there is something wrong.

If you have doubts about feature working well, open the forum thread.

[feuyeux]

Hi Lukáš Fryč,

Firstly, thanks for your reply. I had talked about this issue. Please see https://community.jboss.org/message/716702#716702

I think so that a component's issue is not belong to the global roadmap, however, as a user, I'm always thinking when could this component could be release without bug and when could that component back to the library since rf4. I hope you great developers could show the more detail in the roadmap, for instance, date and feature list. I like the rf4.2 doc from you and Brian, please go on!

I wish a4j:ajax could do everything f:ajax does and provide more powerful features.

BTW, I just studied rich:push from your article, that's very good for me. Thanks!

BR,

Lu Han

[lfryc]

Hey Lu Han, you can simply look for fixVersion in the JIRA to determine which issues are going to be fixed in upcoming releases.

If you want to see a list of issues, you can use search for issues with fixVersion in upcoming releases.

But at first, issue needs to be reported properly, with solid example provided.

[gonzalad]

Hello,

What do you think about an option to lazy load popupPanel contents (i.e. https://issues.jboss.org/browse/RF-8210) ?

modalPanel content would be retrieved by ajax on first show().

This would help reduce HTML Markup.

[bleathem]

I've added the lazy-loaded tag, and we will consider this issue when we consider the rest of the lazy-loading optimizations.

[ruser]

Please implement macrosubstitutions feature in contextMenu https://issues.jboss.org/browse/RF-11842.

We use it heavily with tables and it prevents RF 3-4 migration.

[healeyb]

I was just wondering if you presently have any kind of idea how long it will be after the release of JSF 2.2 that a Richfaces release

will be available that supports that version. It's clearly the "biggest" release since JSF 2 hit the streets, and there was an interval

of over a year (IIRC) before RF4 was released.

Regards,

Brendan.

[paul.dijou]

IMO, it will be really quick. So far, I haven't seen any real break between JSF 2.1 and 2.2. This new versions is more about correcting bugs and adding awesome new features, not breaking everything to build new stuff (like it nearly was bewteen JSF 1.2 and 2.0). It mights even be possible that most of current RichFaces components works in JSF 2.2 as they are (I think so).