Log in to follow, share, and participate in this community.
Thread RenderkitUtils and decodeBehaviors
RenderkitUtils and decodeBehaviorsHey guys, Working on RF-10862 [1], I've found that the behaviorSource check in RenderKitUtils is too restrictive. Specifically the check that the behaviorSource matches the clientId of the component....
RichFaces 4 Component Development ProcessIntroduction
Migrating Components From RichFaces 3.3.X
Getting Started
Before You Begin
Play with the CDK
Creating Your Sandbox Component
Considerations during development
Introduction So y...
Sandbox issue trackingHi team, the Sandbox is coming to stage where it is necessary to describe the existing issues/tasks so we could effectively solve them. There are three options what issue tracker to use: JBoss...
Requirements for a new component setAs discussed in the ongoing RichFaces 4.Next discussion, we are looking to start work on a new component set to address providing components with a faster turnaround. (I'd like to remind everyone that developmen...
Docs migration to GitDocumentation was migrated from SVN to Git, SVN repository for docs module is now locked, and further documentation efforts should be focused in Git.
Bean Validation, @Pattern, and CSVThis discussion relates to the JIRa issue RF-11531. If you have a backing bean, annotated with @Pattern(regexp = "[a-z].*"), then the validation on the server and client disagree. The server side seems t...
Thread What to do about the columnVar/var attributes of the pickList?
What to do about the columnVar/var attributes of the pickList?See issue: https://issues.jboss.org/browse/RF-11208 Summarized here: If we want the pickList to be able to define it's own select items, the way the orderingLIst does, then the syntax looks like: <r:pickLi...
PickList eventsThe picklist currently has three types of events: source, taget, and global events. Global is perhaps a bad choice of words, but I mean events that apply to the picklist as a whole. I'm wondering to waht degre...
3rd party dependency managementAs discussed in this weeks team meeting the requirements for managing 3rd party dependencies are: Regardless of the state of the upstream project source remains accessible. Process should be transparent for use...
Problem creating SelectItemsFor the orderingList, I prototyped the functionality using a nested f:selectItems component, as in: [example 1]:
<rich-input:orderingList id="order...
RenderKit.renderPassThroughAttributesOptimizedWhat does RenderKit.renderPassThroughAttributesOptimized(...) do? As in select.template.xml. If you put it in a template.xml by itself, it has no effect. On has to explicitly include the cdk:passThroughW...
Thread Adding original SelectItem to ClientSelectItem
Adding original SelectItem to ClientSelectItemThe ClientSlectItem would be more useful to me if I added a reference to the SelectItem used to generate to it. I'm concerned that this might place a Serialization requirement on the SelectItem values provided b...
Making sense of events in the CDKI've been spending a lot of time with the CDK this week. I've been able to figure out how it all fits together with the bits of existing documentation, and looking over some examples of other RichFaces component...
Thread Multiple inheritance with RichFaces javascript objects
Multiple inheritance with RichFaces javascript objectsIn the RichFaces components "input" project, I want to take the rf.ui.PopupList javascript object, and split some of the funtionality out for code re-use. Specifically, I want to re-use the list part, and refact...
Quick turnaround for component developmentHi guys, I have identified process of component very time-consuming, especially when used CDK, but this process may very shortened when used right tools. Current process: 1) change sources 2) compil...
Thread No-fast-forward merges of feature branches into develop
No-fast-forward merges of feature branches into developOne more issue regarding to new flow which has been discussed on meeting [1] was using no-fast-forward feature merges with develop (discussed in section Incorporating a finished feature on develop in [2]). This goes w...
Default branch: develop, release branch: masterAs we have discussed on last team meeting, cleanup of unnecessary branches and tags was needed [1] and we have also aligned branch setup with new workflow, so develop branch is currently acting the role of pre...