Feature freeze?

[bluesturbo]

Is Primefaces on a feature freeze iteration?

Perhaps, another two weeks of strictly stabilization snapshots towards a stable release. PrimeFaces is still way ahead of the rest, anxious to get into PrimeFaces 2.01 target.

Thank you, Cagatay, for your incredible work, also, want to thank your wife for "supporting" PrimeFaces!

Cheers!

[cagatay.civici]

Thanks.

We need to fix a couple of issues in datatable, test PrimeFaces 2.0 entirely (will take 1-2 days) and then update user's guide(3-4 days). Then it'll be ready for a release.

We so much want to add new features and components but as you said stable release is the priority now, so there won't be any new features and non major bug fixes other than datatable until the release. Target date is first week of february.

[Oleg]

Hello,

I agree. We don't need really new components at the moment, there are enough . We need a stable release and bigfixing / improvments of existing stuff.

Cagatay, may be you could try to apply my patches to this release? http://code.google.com/p/primefaces/iss ... %20Summary

I would be deeply grateful. I know you are very busy at the moment. That is if you have a little time. I don't believe that my patch would have some side effects.

Thanks a lot for your efforts!
Oleg.

[cagatay.civici]

Sure Oleg, once the other issues are fixed, I'll try to look into this.

Let's release the beast

[cagatay.civici]

Also jquery 1.4 update and side effects took 1 week to stabilize but now we're back on track.

[Oleg]

Sure Oleg, once the other issues are fixed, I'll try to look into this.

Let's release the beast

Cagatay, if you are happy with my beast I could contribute additional two non UI components at that. I'm writing them just now. Short description

Code: Select all

<p:focusManager for="componentId">
......
</p:focusManager>

If for-attribute is present set focus on the component with given ID if it's editable and visible and placed inside of p:focusManager. Without for-attribute set focus into the first editable and visible field below. This component can be used for EditableValueHolder components.

Code: Select all

<p:errorColorizer errorStyle="..." errorClass="...">
......
</p:errorColorizer>

Highlight all invalid fields (not passed validation) by using style / class attributes. Applied for fields inside of p:errorColorizer. The goal is to point invalid field out (e.g. with red borders). This component can be used for EditableValueHolder components. This tag can by used together with focusManager and this is the most interesting variant for fill out a form in your wizard for instance

Code: Select all

// highlight all invalid fields and set focus into the first focusable invalid field
<p:focusManager>
	<p:errorColorizer>
	......
	<p:errorColorizer/>
</p:focusManager>

These are simple, but useful components. I wonder about their missing in component libraries. Another quite useful function (especially for custom JavaScript calls) would be a function to find out the clientId of any component on the page like rich:component from RichFaces.

Regards. Oleg.