Rich Widget Factory API that fulfills needs of JSF component JavaScript API
by Lukáš Fryč
Hey guys,
I have found a following issue:
we expose public JSF component API for Widget Factory based component by
allowing to reference widget reference (i.e. call methods directly on
widget instance):
#{rich:component('autocomplete')}.close();
It will make sure that e.g. following methods can be invoked:
http://www.richwidgets.io/api/classes/autocomplete.html
But those methods doesn't have to be as rich as JSF component we had in RF4.
E.g. in Autocomplete, we had methods getValue() and setValue().
Those methods doesn't do anything else than setting an appropriate value to
the input field. In order to allow unified API, we could expose those
methods for RF5 Autocomplete as well, which will be just syntactic sugar in
terms of Widget Factory -based API.
WDYT?
~ Lukas
11 years, 9 months
Recent Dependency Changes
by Lukáš Fryč
Hey guys,
recently we have upgraded and cleaned up both, NPM and Bower dependencies,
make sure to update your local builds:
$ grunt clean:bower && grunt bower
Cheers,
~ Lukas
11 years, 10 months
Head up: RichWidgets Agile Boards
by Lukáš Fryč
As we discussed recently on IRC,
we have adopted two open agile dashboards for GitHub issues, because the
amount of issues we already have has prevented to work with issues
effectively:
----
for regular contributors, there is Waffle.io:
https://waffle.io/richwidgets/richwidgets
It allows to work with issues in 3 columns:
Backlog - tracks all issues in issue tracker
Ready - current sprint issues - I would like to ask you for periodical
check whether you haven't some issues assigned here
In progress - obviously, as you work with widgets, mark them as in progress
Review - the pull requests or other kind of review is required
Done - yeaaah!
----
The only issue with Waffle is that it doesn't support filtering other than
primitive full-text search.
On the other hand this search works for all important fields:
* summary
* milestones "0.1"
* labels "autocomplete"
* assignee "jstefek"
But you can't combine filters. ;-)
-----
For this purpose we have adopted also another dashboard project, Hubboard:
it's rather for sprint management purposes, but it's available as well:
http://huboard.com/richwidgets/richwidgets/board
Thanks for setting this up, Brian!
Cheers,
~ Lukas
11 years, 10 months
Using Hub for managing Pull Requests
by Lukáš Fryč
Hey guys,
we should consolidate our efforts with Pull Requests.
Lately I use Hub [1] for merging Pull Requests successfully by using:
$ hub am -3 <pull_request_github_url>
which effectively accepts pull request commits on the top of the master
(rebase strategy).
As it is pretty straight-forward, it doesn't add too much overhead to
merging.
----
Brian recently raised an idea [2] that we could leverage Hub more broadly.
I know that it works nice even in other cases like sending pull requests.
Has someone already used Hub?
~ Lukas
[1] https://github.com/github/hub
[2] https://github.com/richwidgets/richwidgets/pull/93#issuecomment-27893868
11 years, 10 months
RW vs RF5 component event handlers
by Juraj Húska
Hello,
what approach we want to take regarding to the RW vs RF5 component handlers.
I would have these specific questions:
1. The doc for event handlers differ slightly. Do we want the same behavior in RW and RF5 ? I mean the same conditions when an event is triggered.
1.1 e.g. doc for change from RW:
{quote:modifiedtitle=true|class=jive_text_macro jive_macro_quote}
Fired when the target list of the pickList changes values.
{quote}
doc from RF5:
{quote:modifiedtitle=true|class=jive_text_macro jive_macro_quote}
Javascript code executed when the list element loses focus and its value has been modified since gaining
focus.
{quote}
1.2 IMHO we are taking over the behavior from RW, so the doc should be the same as in the event.
2. Do we plan to expose more event handlers for RW components ? For example for +pickList+ the same which are currently accessible in the RF5 ? (e.g. onclick ?).
Cheers
Juro
Posted by forums
Original post: https://community.jboss.org/message/845112#845112
11 years, 10 months
