hello Flavio,
Flavio Costa wrote:
thanks for reporting this - haven't noticed this issue yet. we're
running Chiba on windows too, so this is not the problem - i think we've
to file a bug-report for this.
How should I proceed when I find something I believe to be a bug?
First post it to this list or it's best to follow any specific
procedure?
we're not that elaborated about this yet - simply report it to the list
and of course it always helps to have a detailed description - in some
cases (if directly related to a specific form) its nice to have the
related xforms document attached.
sure, i think nobodys used to input dates in schema format ;) and so
your requirement is a quite common one. as an open source project we're
lacking financial support and so i can't make promises when we'll have
addressed this issue. its planned to refactor the schema datatypes part
in Chiba and we'll take your issue into account then.
Incidentally this date format is often used in Japan, but evidently
Schema's time and datetime formats are more akward. Unfortunatelly I
don't know enough of Chiba's inner workings, therefore I cannot
volunteer to help on it yet.
we'll definitely think about this issue and where to integrate it into
Chiba. i already have a rough idea - whenever a refresh() is executed
Chiba updates its UI objects to reflect the status of the instance-data.
cause the data values are copied to the controls the update() method of
XFormsElement might be the right place.
the other direction might work quite the same. - have to look into it ...
but you raised a definitely very important issue that also touched i18n
and localization of datatype representations
We have been also trying to use custom actions but from the comments
in the conf file it seems that this feature not currently implemented.
Making minor changes in two classes (adding a constant to
XFormConstants and another "if" to
XFormsElement.createXFormsElement()) we could make Chiba call an
action made by us. Perhaps it's not so difficult to finally add
support for any custom actions.
this feature already worked very well up to chiba 0.9 but was disabled
during refactoring. it was planned to reactivate this feature. we've to
merge the old implementation back into cvs head.
you're actually the first demanding custom actions that why it wasn't in
focus for a while. i'll see if we can quickly put them back in.
By the way, a trivial optimization could be done to
XFormsElement.createXFormsElement() method. There we have an
unchanging "localName" variable being tested over several "if". As it
cannot enter two "ifs" in the same call (unless the value of some of
these constants is the same), every "if" should be changed to "else
if", so once there is a match the other conditions aren't tested. Of
course, if this method is changed to support custom actions then
another approach would be required.
i'll have a look when re-integrating
thanks
Joern
Best regards,
Flávio Costa
-------------------------------------------------------
This SF.net email is sponsored by OSDN's Audience Survey.
Help shape OSDN's sites and tell us what you think. Take this
five minute survey and you could win a $250 Gift Certificate.
http://www.wrgsurveys.com/2003/osdntech03.php?site=8
| 
