Hi Alex,
I believe I have discovered the source of the error, after much debugging. In the newer builds, has the autocomplete function changed? I am using autocomplete in two cases, and the result is "[No error message provided.]". The code is as follows: <fr:autocomplete ref="." dynamic-itemset="false" style="float: left;"> <xforms:label>Language</xforms:label> <xforms:itemset nodeset="instance('languageselect-template')//language"> <xforms:label ref="name"/> <xforms:value ref="name"/> </xforms:itemset> </fr:autocomplete> This works in 3.7.1, but not in the nightly build. Ethan On Wed, Jan 6, 2010 at 7:09 PM, Alessandro Vernet <[hidden email]> wrote:
-- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
Ethan,
Yes, there were some improvements made to the fr:autocomplete recently, but I can't say if that could be the reason for the issues you are seeing. Would you be able to create a simple reproducible test case we can run in the XForms sandbox for this? Alex On Thu, Jan 7, 2010 at 8:20 AM, Ethan Gruber <[hidden email]> wrote: > > Hi Alex, > > I believe I have discovered the source of the error, after much debugging. In the newer builds, has the autocomplete function changed? I am using autocomplete in two cases, and the result is "[No error message provided.]". > > The code is as follows: > > <fr:autocomplete ref="." dynamic-itemset="false" > style="float: left;"> > <xforms:label>Language</xforms:label> > <xforms:itemset nodeset="instance('languageselect-template')//language"> > <xforms:label ref="name"/> > <xforms:value ref="name"/> > </xforms:itemset> > </fr:autocomplete> > > This works in 3.7.1, but not in the nightly build. > > Ethan > > > On Wed, Jan 6, 2010 at 7:09 PM, Alessandro Vernet <[hidden email]> wrote: >> >> Ethan, >> It would be good to figure out why. The nightly builds are quite stable now, and we're getting very close to cutting a release from a nightly build (yes, yes, I know you heard that before!). I'd be interested to know more about the problem, if you get a chance to investigate this further. >> Alex >> >> >> On Jan 6, 2010, at 3:47 PM, Ethan Gruber <[hidden email]> wrote: >> >> I've tried the nightly build, but my application doesn't work at all in the nightly build. I don't even get a descriptive error. >> >> On Wed, Jan 6, 2010 at 6:28 PM, Alessandro Vernet <[hidden email]> wrote: >>> >>> Ethan, >>> rteConfig is there in the latest code (nightly builds). >>> Alex >>> >>> >>> On Jan 6, 2010, at 1:39 PM, Ethan Gruber <[hidden email]> wrote: >>> >>> Thanks for the replies. To clarify, this is the xforms.js in Orbeon 3.7.1? I followed the directions for extracting the ops folder from the jar into WEB-INF/resources, but the string "rteConfig" is not in the file anywhere. I do find where the toolbar is defined in xforms.js, but I'm not quite sure where the button functions are defined. The function that defines what the "Bold" button does is not in this file, it seems. I'd like to get the hang of the yuiRTE by first changing bold and italic from <b> and <i> to the syntax that I require--<emph render="bold"> and <emph render="italic">. After adapting the current buttons to the new syntax, then I will understand how to add new ones. >>> >>> Thanks, >>> Ethan >>> >>> On Tue, Jan 5, 2010 at 9:31 PM, Dave McIntyre <[hidden email]> wrote: >>>> >>>> I made a change along these lines a while ago. In xforms.js, replace the declaration of yuiRTE with something like >>>> >>>> // Create RTE object, using a default config unless YUI_RTE_CUSTOM_CONFIG is defined >>>> var config = { >>>> // Don't set width/height (done in CSS) >>>> }; >>>> var yui_config_type_check = typeof YUI_RTE_CUSTOM_CONFIG; >>>> if (yui_config_type_check != 'undefined') { >>>> config = YUI_RTE_CUSTOM_CONFIG; >>>> } >>>> >>>> var yuiRTE = new YAHOO.widget.Editor(control, config); >>>> >>>> and then include some suitable javascript declaration of the variable YUI_RTE_CUSTOM_CONFIG. However, I seem to recall that this involved some other tweaks to arrange that xforms.js gets loaded with defer="defer" so that the variable is available to be checked. >>>> >>>> >>>> Alessandro Vernet wrote: >>>> >>>> Ethan, >>>> >>>> For this, you will only need to change the code in xforms.js. Like you >>>> said, that file is in a jar file, so you'll want to extract it, and >>>> put the extracted file, which you will modify, in your resources, >>>> under the same path, so it overrides the one in the jar file. You'll >>>> find more on JavaScript development for Orbeon Forms here: >>>> >>>> http://wiki.orbeon.com/forms/doc/contributor-guide/javascript-development >>>> >>>> Then in xforms.js search for rteConfig, and you'll find the place >>>> where the RTE toolbar is initialized. As you'll see, this has not been >>>> designed for extensibility ;), so let us know if you have suggestions >>>> on how to make the RTE more easily configurable. >>>> >>>> Alex >>>> >>>> On Monday, January 4, 2010, Ethan Gruber <[hidden email]> wrote: >>>> >>>> >>>> Hello, >>>> >>>> I'd like to modify the YUI RTE code to add plugins for a new set of buttons, which should be possible according to here: http://developer.yahoo.com/yui/editor/#toolbar . Has anyone sucessfully done this before? Where do I get started? I assume the js is contained in a jar file. >>>> >>>> Thanks, >>>> Ethan >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> ________________________________ >>>> >>>> Dave McIntyre Development Team Lead >>>> [hidden email] >>>> P: +64 9 638 0600 >>>> M: +64 21 212 8087 >>>> F: +64 9 638 0699 >>>> S: dave.mcintyre >>>> www.orionhealth.com >>>> >>>> This e-mail and any attachments are intended only for the person to whom it is addressed and may contain privileged, proprietary, or other data protected from disclosure under applicable law. If you are not the addressee or the person responsible for delivering this to the addressee you are hereby notified that reading, copying or distributing this transmission is prohibited. If you have received this e-mail in error, please telephone us immediately and remove all copies of it from your system. Thank you for your co-operation. >>>> >>>> __________ Information from ESET NOD32 Antivirus, version of virus signature database 4746 (20100105) __________ >>>> >>>> The message was checked by ESET NOD32 Antivirus. >>>> >>>> http://www.eset.com >>> >>> >>> -- >>> You receive this message as a subscriber of the [hidden email] mailing list. >>> To unsubscribe: mailto:[hidden email] >>> For general help: mailto:[hidden email]?subject=help >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >>> -- >>> You receive this message as a subscriber of the [hidden email] mailing list. >>> To unsubscribe: mailto:[hidden email] >>> For general help: mailto:[hidden email]?subject=help >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >> >> >> -- >> You receive this message as a subscriber of the [hidden email] mailing list. >> To unsubscribe: mailto:[hidden email] >> For general help: mailto:[hidden email]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws >> >> >> -- >> You receive this message as a subscriber of the [hidden email] mailing list. >> To unsubscribe: mailto:[hidden email] >> For general help: mailto:[hidden email]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws >> > > > > -- > You receive this message as a subscriber of the [hidden email] mailing list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > -- Orbeon Forms - Web forms, open-source, for the Enterprise Orbeon's Blog: http://www.orbeon.com/blog/ My Twitter: http://twitter.com/avernet -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hey Alex,
I've been working on trying to produce a reproducible test case today, but to no avail. Are there any issues with Orbeon handling 2 or more layers of xi:include? The data model I am working on is fairly complex, with a number of repeatable elements that can occur within a variety of contexts. In my attempt to modularize the project as much as possible, I have used xi:include in many places. My test case involved moving the code: <xforms:repeat nodeset="language"> <div style="margin-bottom:10px"> <fr:autocomplete ref="." dynamic-itemset="false" style="float: left;"> <xforms:label>Language</xforms:label> <xforms:itemset nodeset="instance('languageselect-template')//language"> <xforms:label ref="name"/> <xforms:value ref="name"/> </xforms:itemset> </fr:autocomplete> <!--<xforms:input ref="."> <xforms:label>Language</xforms:label> </xforms:input>--> <xforms:trigger appearance="minimal"> <xforms:delete ev:event="DOMActivate" nodeset="."/> <xforms:label> <img src="/apps/ead/images/remove.gif"/> </xforms:label> </xforms:trigger> </div> </xforms:repeat> from an xml file that was included into the xhtml view into the xhtml file itself, and it worked. But the nightly build doesn't seem to handle fr:autocomplete in included xml files properly. 3.7.1 did. It doesn't seem to be a universal problem with xi:include, because every other input works correctly. Let me know if you need more info from me. Ethan On Wed, Jan 27, 2010 at 2:33 PM, Alessandro Vernet <[hidden email]> wrote: Ethan, -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Hi Alex,
I have found the real culprit here, finally. It's not really an xi:include issue. It is an issue where the fr:autocomplete does not work if it is nested inside of an xforms:repeat that is also nested inside of an xforms:repeat. It worked fine in 3.7.1, but something must be a bit different in the newer builds. I have attached a zip with two views you can load into the sandbox, one labeled "pass", the other "fail" so you can get a look at what's going on. This is the last hurdle preventing me from using the the nightly/3.7.2 like builds. Ethan On Tue, Feb 9, 2010 at 2:14 PM, Ethan Gruber <[hidden email]> wrote: Hey Alex, -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws autocomplete-repeat.zip (3K) Download Attachment |
Administrator
|
Ethan,
How can I reproduce this? I am running test-fail, and without doing anything else, the autocomplete seems to be working as far I can tell. Alex On Fri, Feb 19, 2010 at 8:07 AM, Ethan Gruber <[hidden email]> wrote: > Hi Alex, > > I have found the real culprit here, finally. It's not really an xi:include > issue. It is an issue where the fr:autocomplete does not work if it is > nested inside of an xforms:repeat that is also nested inside of an > xforms:repeat. It worked fine in 3.7.1, but something must be a bit > different in the newer builds. > > I have attached a zip with two views you can load into the sandbox, one > labeled "pass", the other "fail" so you can get a look at what's going on. > This is the last hurdle preventing me from using the the nightly/3.7.2 like > builds. > > Ethan > > On Tue, Feb 9, 2010 at 2:14 PM, Ethan Gruber <[hidden email]> wrote: >> >> Hey Alex, >> >> I've been working on trying to produce a reproducible test case today, but >> to no avail. Are there any issues with Orbeon handling 2 or more layers of >> xi:include? >> >> The data model I am working on is fairly complex, with a number of >> repeatable elements that can occur within a variety of contexts. In my >> attempt to modularize the project as much as possible, I have used >> xi:include in many places. My test case involved moving the code: >> >> <xforms:repeat nodeset="language"> >> <div style="margin-bottom:10px"> >> <fr:autocomplete ref="." dynamic-itemset="false" >> style="float: left;"> >> <xforms:label>Language</xforms:label> >> <xforms:itemset >> nodeset="instance('languageselect-template')//language"> >> <xforms:label ref="name"/> >> <xforms:value ref="name"/> >> </xforms:itemset> >> </fr:autocomplete> >> <!--<xforms:input ref="."> >> <xforms:label>Language</xforms:label> >> </xforms:input>--> >> <xforms:trigger appearance="minimal"> >> <xforms:delete ev:event="DOMActivate" >> nodeset="."/> >> <xforms:label> >> <img src="/apps/ead/images/remove.gif"/> >> </xforms:label> >> </xforms:trigger> >> </div> >> </xforms:repeat> >> >> from an xml file that was included into the xhtml view into the xhtml file >> itself, and it worked. But the nightly build doesn't seem to handle >> fr:autocomplete in included xml files properly. 3.7.1 did. It doesn't seem >> to be a universal problem with xi:include, because every other input works >> correctly. >> >> Let me know if you need more info from me. >> >> Ethan >> On Wed, Jan 27, 2010 at 2:33 PM, Alessandro Vernet <[hidden email]> >> wrote: >>> >>> Ethan, >>> >>> Yes, there were some improvements made to the fr:autocomplete >>> recently, but I can't say if that could be the reason for the issues >>> you are seeing. Would you be able to create a simple reproducible test >>> case we can run in the XForms sandbox for this? >>> >>> Alex >>> >>> On Thu, Jan 7, 2010 at 8:20 AM, Ethan Gruber <[hidden email]> wrote: >>> > >>> > Hi Alex, >>> > >>> > I believe I have discovered the source of the error, after much >>> > debugging. In the newer builds, has the autocomplete function changed? I >>> > am using autocomplete in two cases, and the result is "[No error message >>> > provided.]". >>> > >>> > The code is as follows: >>> > >>> > <fr:autocomplete ref="." dynamic-itemset="false" >>> > style="float: left;"> >>> > <xforms:label>Language</xforms:label> >>> > <xforms:itemset >>> > nodeset="instance('languageselect-template')//language"> >>> > <xforms:label ref="name"/> >>> > <xforms:value ref="name"/> >>> > </xforms:itemset> >>> > </fr:autocomplete> >>> > >>> > This works in 3.7.1, but not in the nightly build. >>> > >>> > Ethan >>> > >>> > >>> > On Wed, Jan 6, 2010 at 7:09 PM, Alessandro Vernet <[hidden email]> >>> > wrote: >>> >> >>> >> Ethan, >>> >> It would be good to figure out why. The nightly builds are quite >>> >> stable now, and we're getting very close to cutting a release from a nightly >>> >> build (yes, yes, I know you heard that before!). I'd be interested to know >>> >> more about the problem, if you get a chance to investigate this further. >>> >> Alex >>> >> >>> >> >>> >> On Jan 6, 2010, at 3:47 PM, Ethan Gruber <[hidden email]> wrote: >>> >> >>> >> I've tried the nightly build, but my application doesn't work at all >>> >> in the nightly build. I don't even get a descriptive error. >>> >> >>> >> On Wed, Jan 6, 2010 at 6:28 PM, Alessandro Vernet <[hidden email]> >>> >> wrote: >>> >>> >>> >>> Ethan, >>> >>> rteConfig is there in the latest code (nightly builds). >>> >>> Alex >>> >>> >>> >>> >>> >>> On Jan 6, 2010, at 1:39 PM, Ethan Gruber <[hidden email]> wrote: >>> >>> >>> >>> Thanks for the replies. To clarify, this is the xforms.js in Orbeon >>> >>> 3.7.1? I followed the directions for extracting the ops folder from the jar >>> >>> into WEB-INF/resources, but the string "rteConfig" is not in the file >>> >>> anywhere. I do find where the toolbar is defined in xforms.js, but I'm not >>> >>> quite sure where the button functions are defined. The function that >>> >>> defines what the "Bold" button does is not in this file, it seems. I'd like >>> >>> to get the hang of the yuiRTE by first changing bold and italic from <b> and >>> >>> <i> to the syntax that I require--<emph render="bold"> and <emph >>> >>> render="italic">. After adapting the current buttons to the new syntax, >>> >>> then I will understand how to add new ones. >>> >>> >>> >>> Thanks, >>> >>> Ethan >>> >>> >>> >>> On Tue, Jan 5, 2010 at 9:31 PM, Dave McIntyre >>> >>> <[hidden email]> wrote: >>> >>>> >>> >>>> I made a change along these lines a while ago. In xforms.js, >>> >>>> replace the declaration of yuiRTE with something like >>> >>>> >>> >>>> // Create RTE object, using a default config unless >>> >>>> YUI_RTE_CUSTOM_CONFIG is defined >>> >>>> var config = { >>> >>>> // Don't set width/height (done in CSS) >>> >>>> }; >>> >>>> var yui_config_type_check = typeof >>> >>>> YUI_RTE_CUSTOM_CONFIG; >>> >>>> if (yui_config_type_check != 'undefined') { >>> >>>> config = YUI_RTE_CUSTOM_CONFIG; >>> >>>> } >>> >>>> >>> >>>> var yuiRTE = new YAHOO.widget.Editor(control, config); >>> >>>> >>> >>>> and then include some suitable javascript declaration of the >>> >>>> variable YUI_RTE_CUSTOM_CONFIG. However, I seem to recall that this >>> >>>> involved some other tweaks to arrange that xforms.js gets loaded with >>> >>>> defer="defer" so that the variable is available to be checked. >>> >>>> >>> >>>> >>> >>>> Alessandro Vernet wrote: >>> >>>> >>> >>>> Ethan, >>> >>>> >>> >>>> For this, you will only need to change the code in xforms.js. Like >>> >>>> you >>> >>>> said, that file is in a jar file, so you'll want to extract it, and >>> >>>> put the extracted file, which you will modify, in your resources, >>> >>>> under the same path, so it overrides the one in the jar file. You'll >>> >>>> find more on JavaScript development for Orbeon Forms here: >>> >>>> >>> >>>> >>> >>>> http://wiki.orbeon.com/forms/doc/contributor-guide/javascript-development >>> >>>> >>> >>>> Then in xforms.js search for rteConfig, and you'll find the place >>> >>>> where the RTE toolbar is initialized. As you'll see, this has not >>> >>>> been >>> >>>> designed for extensibility ;), so let us know if you have >>> >>>> suggestions >>> >>>> on how to make the RTE more easily configurable. >>> >>>> >>> >>>> Alex >>> >>>> >>> >>>> On Monday, January 4, 2010, Ethan Gruber <[hidden email]> wrote: >>> >>>> >>> >>>> >>> >>>> Hello, >>> >>>> >>> >>>> I'd like to modify the YUI RTE code to add plugins for a new set of >>> >>>> buttons, which should be possible according to here: >>> >>>> http://developer.yahoo.com/yui/editor/#toolbar . Has anyone sucessfully >>> >>>> done this before? Where do I get started? I assume the js is contained in >>> >>>> a jar file. >>> >>>> >>> >>>> Thanks, >>> >>>> Ethan >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>>> -- >>> >>>> ________________________________ >>> >>>> >>> >>>> Dave McIntyre Development Team Lead >>> >>>> [hidden email] >>> >>>> P: +64 9 638 0600 >>> >>>> M: +64 21 212 8087 >>> >>>> F: +64 9 638 0699 >>> >>>> S: dave.mcintyre >>> >>>> www.orionhealth.com >>> >>>> >>> >>>> This e-mail and any attachments are intended only for the person to >>> >>>> whom it is addressed and may contain privileged, proprietary, or other data >>> >>>> protected from disclosure under applicable law. If you are not the addressee >>> >>>> or the person responsible for delivering this to the addressee you are >>> >>>> hereby notified that reading, copying or distributing this transmission is >>> >>>> prohibited. If you have received this e-mail in error, please telephone us >>> >>>> immediately and remove all copies of it from your system. Thank you for your >>> >>>> co-operation. >>> >>>> >>> >>>> __________ Information from ESET NOD32 Antivirus, version of virus >>> >>>> signature database 4746 (20100105) __________ >>> >>>> >>> >>>> The message was checked by ESET NOD32 Antivirus. >>> >>>> >>> >>>> http://www.eset.com >>> >>> >>> >>> >>> >>> -- >>> >>> You receive this message as a subscriber of the [hidden email] >>> >>> mailing list. >>> >>> To unsubscribe: mailto:[hidden email] >>> >>> For general help: mailto:[hidden email]?subject=help >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >>> >>> >>> >>> -- >>> >>> You receive this message as a subscriber of the [hidden email] >>> >>> mailing list. >>> >>> To unsubscribe: mailto:[hidden email] >>> >>> For general help: mailto:[hidden email]?subject=help >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >>> >> >>> >> >>> >> -- >>> >> You receive this message as a subscriber of the [hidden email] >>> >> mailing list. >>> >> To unsubscribe: mailto:[hidden email] >>> >> For general help: mailto:[hidden email]?subject=help >>> >> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >> >>> >> >>> >> -- >>> >> You receive this message as a subscriber of the [hidden email] >>> >> mailing list. >>> >> To unsubscribe: mailto:[hidden email] >>> >> For general help: mailto:[hidden email]?subject=help >>> >> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >> >>> > >>> > >>> > >>> > -- >>> > You receive this message as a subscriber of the [hidden email] >>> > mailing list. >>> > To unsubscribe: mailto:[hidden email] >>> > For general help: mailto:[hidden email]?subject=help >>> > OW2 mailing lists service home page: http://www.ow2.org/wws >>> > >>> >>> >>> >>> -- >>> Orbeon Forms - Web forms, open-source, for the Enterprise >>> Orbeon's Blog: http://www.orbeon.com/blog/ >>> My Twitter: http://twitter.com/avernet >>> >>> >>> -- >>> You receive this message as a subscriber of the [hidden email] mailing >>> list. >>> To unsubscribe: mailto:[hidden email] >>> For general help: mailto:[hidden email]?subject=help >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >> > > > > -- > You receive this message as a subscriber of the [hidden email] mailing > list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- Orbeon Forms - Web forms, open-source, for the Enterprise - http://www.orbeon.com/ My Twitter: http://twitter.com/avernet -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Um, let me retry that on the most recent nightly build. I think I was testing it on one from last week.
On Fri, Feb 19, 2010 at 6:26 PM, Alessandro Vernet <[hidden email]> wrote: Ethan, -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Okay, Alex, I grabbed the most recently nightly build and it looks like the error I noted with fr:autocomplete within nested xforms:repeat is solved, but it appears that there is a new issue. If you save a document after entering one or more values into the fr:autocomplete field, when you load the document, the text node of that element doesn't load. There is are inputs representing the number of values there should be, but the inputs are blank. If you double check the XML in exist, it's fine. The instance inspector also shows the text node of the element. You can use one of the test views I sent you in the earlier email. The forms save and load to/from db/test/test.xml.
Attached is an image that I hope will illustrate what I'm explaining. Sorry if it's confusing. Ethan On Fri, Feb 19, 2010 at 7:29 PM, Ethan Gruber <[hidden email]> wrote: Um, let me retry that on the most recent nightly build. I think I was testing it on one from last week. -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws autocomplete_error.png (58K) Download Attachment |
Administrator
|
Hi Ethan,
Your example is clear, and I was able to reproduce this. The issue is that the autocomplete doesn't initialize itself with the value from the instance. The code to do that is simply not there in the XBL component. We've never hit this case before because we always used the autocomplete in pages where is was used as a way to search for things, and so the initial value was always empty. I created a bug for this below, but unfortunately, unless we get a request to fix this from one of our clients, I am afraid we won't have the time to implement this in the near future. http://forge.ow2.org/tracker/index.php?func=detail&aid=314755&group_id=168&atid=350207 Alex On Sat, Feb 20, 2010 at 10:43 AM, Ethan Gruber <[hidden email]> wrote: > Okay, Alex, I grabbed the most recently nightly build and it looks like the > error I noted with fr:autocomplete within nested xforms:repeat is solved, > but it appears that there is a new issue. If you save a document after > entering one or more values into the fr:autocomplete field, when you load > the document, the text node of that element doesn't load. There is are > inputs representing the number of values there should be, but the inputs are > blank. If you double check the XML in exist, it's fine. The instance > inspector also shows the text node of the element. You can use one of the > test views I sent you in the earlier email. The forms save and load to/from > db/test/test.xml. > > Attached is an image that I hope will illustrate what I'm explaining. Sorry > if it's confusing. > > Ethan > > On Fri, Feb 19, 2010 at 7:29 PM, Ethan Gruber <[hidden email]> wrote: >> >> Um, let me retry that on the most recent nightly build. I think I was >> testing it on one from last week. >> >> On Fri, Feb 19, 2010 at 6:26 PM, Alessandro Vernet <[hidden email]> >> wrote: >>> >>> Ethan, >>> >>> How can I reproduce this? I am running test-fail, and without doing >>> anything else, the autocomplete seems to be working as far I can tell. >>> >>> Alex >>> >>> On Fri, Feb 19, 2010 at 8:07 AM, Ethan Gruber <[hidden email]> wrote: >>> > Hi Alex, >>> > >>> > I have found the real culprit here, finally. It's not really an >>> > xi:include >>> > issue. It is an issue where the fr:autocomplete does not work if it is >>> > nested inside of an xforms:repeat that is also nested inside of an >>> > xforms:repeat. It worked fine in 3.7.1, but something must be a bit >>> > different in the newer builds. >>> > >>> > I have attached a zip with two views you can load into the sandbox, one >>> > labeled "pass", the other "fail" so you can get a look at what's going >>> > on. >>> > This is the last hurdle preventing me from using the the nightly/3.7.2 >>> > like >>> > builds. >>> > >>> > Ethan >>> > >>> > On Tue, Feb 9, 2010 at 2:14 PM, Ethan Gruber <[hidden email]> >>> > wrote: >>> >> >>> >> Hey Alex, >>> >> >>> >> I've been working on trying to produce a reproducible test case today, >>> >> but >>> >> to no avail. Are there any issues with Orbeon handling 2 or more >>> >> layers of >>> >> xi:include? >>> >> >>> >> The data model I am working on is fairly complex, with a number of >>> >> repeatable elements that can occur within a variety of contexts. In >>> >> my >>> >> attempt to modularize the project as much as possible, I have used >>> >> xi:include in many places. My test case involved moving the code: >>> >> >>> >> <xforms:repeat nodeset="language"> >>> >> <div style="margin-bottom:10px"> >>> >> <fr:autocomplete ref="." dynamic-itemset="false" >>> >> style="float: left;"> >>> >> <xforms:label>Language</xforms:label> >>> >> <xforms:itemset >>> >> nodeset="instance('languageselect-template')//language"> >>> >> <xforms:label ref="name"/> >>> >> <xforms:value ref="name"/> >>> >> </xforms:itemset> >>> >> </fr:autocomplete> >>> >> <!--<xforms:input ref="."> >>> >> <xforms:label>Language</xforms:label> >>> >> </xforms:input>--> >>> >> <xforms:trigger appearance="minimal"> >>> >> <xforms:delete ev:event="DOMActivate" >>> >> nodeset="."/> >>> >> <xforms:label> >>> >> <img src="/apps/ead/images/remove.gif"/> >>> >> </xforms:label> >>> >> </xforms:trigger> >>> >> </div> >>> >> </xforms:repeat> >>> >> >>> >> from an xml file that was included into the xhtml view into the xhtml >>> >> file >>> >> itself, and it worked. But the nightly build doesn't seem to handle >>> >> fr:autocomplete in included xml files properly. 3.7.1 did. It >>> >> doesn't seem >>> >> to be a universal problem with xi:include, because every other input >>> >> works >>> >> correctly. >>> >> >>> >> Let me know if you need more info from me. >>> >> >>> >> Ethan >>> >> On Wed, Jan 27, 2010 at 2:33 PM, Alessandro Vernet >>> >> <[hidden email]> >>> >> wrote: >>> >>> >>> >>> Ethan, >>> >>> >>> >>> Yes, there were some improvements made to the fr:autocomplete >>> >>> recently, but I can't say if that could be the reason for the issues >>> >>> you are seeing. Would you be able to create a simple reproducible >>> >>> test >>> >>> case we can run in the XForms sandbox for this? >>> >>> >>> >>> Alex >>> >>> >>> >>> On Thu, Jan 7, 2010 at 8:20 AM, Ethan Gruber <[hidden email]> >>> >>> wrote: >>> >>> > >>> >>> > Hi Alex, >>> >>> > >>> >>> > I believe I have discovered the source of the error, after much >>> >>> > debugging. In the newer builds, has the autocomplete function >>> >>> > changed? I >>> >>> > am using autocomplete in two cases, and the result is "[No error >>> >>> > message >>> >>> > provided.]". >>> >>> > >>> >>> > The code is as follows: >>> >>> > >>> >>> > <fr:autocomplete ref="." dynamic-itemset="false" >>> >>> > style="float: left;"> >>> >>> > <xforms:label>Language</xforms:label> >>> >>> > <xforms:itemset >>> >>> > nodeset="instance('languageselect-template')//language"> >>> >>> > <xforms:label ref="name"/> >>> >>> > <xforms:value ref="name"/> >>> >>> > </xforms:itemset> >>> >>> > </fr:autocomplete> >>> >>> > >>> >>> > This works in 3.7.1, but not in the nightly build. >>> >>> > >>> >>> > Ethan >>> >>> > >>> >>> > >>> >>> > On Wed, Jan 6, 2010 at 7:09 PM, Alessandro Vernet >>> >>> > <[hidden email]> >>> >>> > wrote: >>> >>> >> >>> >>> >> Ethan, >>> >>> >> It would be good to figure out why. The nightly builds are quite >>> >>> >> stable now, and we're getting very close to cutting a release from >>> >>> >> a nightly >>> >>> >> build (yes, yes, I know you heard that before!). I'd be interested >>> >>> >> to know >>> >>> >> more about the problem, if you get a chance to investigate this >>> >>> >> further. >>> >>> >> Alex >>> >>> >> >>> >>> >> >>> >>> >> On Jan 6, 2010, at 3:47 PM, Ethan Gruber <[hidden email]> >>> >>> >> wrote: >>> >>> >> >>> >>> >> I've tried the nightly build, but my application doesn't work at >>> >>> >> all >>> >>> >> in the nightly build. I don't even get a descriptive error. >>> >>> >> >>> >>> >> On Wed, Jan 6, 2010 at 6:28 PM, Alessandro Vernet >>> >>> >> <[hidden email]> >>> >>> >> wrote: >>> >>> >>> >>> >>> >>> Ethan, >>> >>> >>> rteConfig is there in the latest code (nightly builds). >>> >>> >>> Alex >>> >>> >>> >>> >>> >>> >>> >>> >>> On Jan 6, 2010, at 1:39 PM, Ethan Gruber <[hidden email]> >>> >>> >>> wrote: >>> >>> >>> >>> >>> >>> Thanks for the replies. To clarify, this is the xforms.js in >>> >>> >>> Orbeon >>> >>> >>> 3.7.1? I followed the directions for extracting the ops folder >>> >>> >>> from the jar >>> >>> >>> into WEB-INF/resources, but the string "rteConfig" is not in the >>> >>> >>> file >>> >>> >>> anywhere. I do find where the toolbar is defined in xforms.js, >>> >>> >>> but I'm not >>> >>> >>> quite sure where the button functions are defined. The function >>> >>> >>> that >>> >>> >>> defines what the "Bold" button does is not in this file, it >>> >>> >>> seems. I'd like >>> >>> >>> to get the hang of the yuiRTE by first changing bold and italic >>> >>> >>> from <b> and >>> >>> >>> <i> to the syntax that I require--<emph render="bold"> and <emph >>> >>> >>> render="italic">. After adapting the current buttons to the new >>> >>> >>> syntax, >>> >>> >>> then I will understand how to add new ones. >>> >>> >>> >>> >>> >>> Thanks, >>> >>> >>> Ethan >>> >>> >>> >>> >>> >>> On Tue, Jan 5, 2010 at 9:31 PM, Dave McIntyre >>> >>> >>> <[hidden email]> wrote: >>> >>> >>>> >>> >>> >>>> I made a change along these lines a while ago. In xforms.js, >>> >>> >>>> replace the declaration of yuiRTE with something like >>> >>> >>>> >>> >>> >>>> // Create RTE object, using a default config unless >>> >>> >>>> YUI_RTE_CUSTOM_CONFIG is defined >>> >>> >>>> var config = { >>> >>> >>>> // Don't set width/height (done in CSS) >>> >>> >>>> }; >>> >>> >>>> var yui_config_type_check = typeof >>> >>> >>>> YUI_RTE_CUSTOM_CONFIG; >>> >>> >>>> if (yui_config_type_check != 'undefined') { >>> >>> >>>> config = YUI_RTE_CUSTOM_CONFIG; >>> >>> >>>> } >>> >>> >>>> >>> >>> >>>> var yuiRTE = new YAHOO.widget.Editor(control, >>> >>> >>>> config); >>> >>> >>>> >>> >>> >>>> and then include some suitable javascript declaration of the >>> >>> >>>> variable YUI_RTE_CUSTOM_CONFIG. However, I seem to recall that >>> >>> >>>> this >>> >>> >>>> involved some other tweaks to arrange that xforms.js gets loaded >>> >>> >>>> with >>> >>> >>>> defer="defer" so that the variable is available to be checked. >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> Alessandro Vernet wrote: >>> >>> >>>> >>> >>> >>>> Ethan, >>> >>> >>>> >>> >>> >>>> For this, you will only need to change the code in xforms.js. >>> >>> >>>> Like >>> >>> >>>> you >>> >>> >>>> said, that file is in a jar file, so you'll want to extract it, >>> >>> >>>> and >>> >>> >>>> put the extracted file, which you will modify, in your >>> >>> >>>> resources, >>> >>> >>>> under the same path, so it overrides the one in the jar file. >>> >>> >>>> You'll >>> >>> >>>> find more on JavaScript development for Orbeon Forms here: >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> http://wiki.orbeon.com/forms/doc/contributor-guide/javascript-development >>> >>> >>>> >>> >>> >>>> Then in xforms.js search for rteConfig, and you'll find the >>> >>> >>>> place >>> >>> >>>> where the RTE toolbar is initialized. As you'll see, this has >>> >>> >>>> not >>> >>> >>>> been >>> >>> >>>> designed for extensibility ;), so let us know if you have >>> >>> >>>> suggestions >>> >>> >>>> on how to make the RTE more easily configurable. >>> >>> >>>> >>> >>> >>>> Alex >>> >>> >>>> >>> >>> >>>> On Monday, January 4, 2010, Ethan Gruber <[hidden email]> >>> >>> >>>> wrote: >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> Hello, >>> >>> >>>> >>> >>> >>>> I'd like to modify the YUI RTE code to add plugins for a new set >>> >>> >>>> of >>> >>> >>>> buttons, which should be possible according to here: >>> >>> >>>> http://developer.yahoo.com/yui/editor/#toolbar . Has anyone >>> >>> >>>> sucessfully >>> >>> >>>> done this before? Where do I get started? I assume the js is >>> >>> >>>> contained in >>> >>> >>>> a jar file. >>> >>> >>>> >>> >>> >>>> Thanks, >>> >>> >>>> Ethan >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> >>> >>> >>>> -- >>> >>> >>>> ________________________________ >>> >>> >>>> >>> >>> >>>> Dave McIntyre Development Team Lead >>> >>> >>>> [hidden email] >>> >>> >>>> P: +64 9 638 0600 >>> >>> >>>> M: +64 21 212 8087 >>> >>> >>>> F: +64 9 638 0699 >>> >>> >>>> S: dave.mcintyre >>> >>> >>>> www.orionhealth.com >>> >>> >>>> >>> >>> >>>> This e-mail and any attachments are intended only for the person >>> >>> >>>> to >>> >>> >>>> whom it is addressed and may contain privileged, proprietary, or >>> >>> >>>> other data >>> >>> >>>> protected from disclosure under applicable law. If you are not >>> >>> >>>> the addressee >>> >>> >>>> or the person responsible for delivering this to the addressee >>> >>> >>>> you are >>> >>> >>>> hereby notified that reading, copying or distributing this >>> >>> >>>> transmission is >>> >>> >>>> prohibited. If you have received this e-mail in error, please >>> >>> >>>> telephone us >>> >>> >>>> immediately and remove all copies of it from your system. Thank >>> >>> >>>> you for your >>> >>> >>>> co-operation. >>> >>> >>>> >>> >>> >>>> __________ Information from ESET NOD32 Antivirus, version of >>> >>> >>>> virus >>> >>> >>>> signature database 4746 (20100105) __________ >>> >>> >>>> >>> >>> >>>> The message was checked by ESET NOD32 Antivirus. >>> >>> >>>> >>> >>> >>>> http://www.eset.com >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> You receive this message as a subscriber of the [hidden email] >>> >>> >>> mailing list. >>> >>> >>> To unsubscribe: mailto:[hidden email] >>> >>> >>> For general help: mailto:[hidden email]?subject=help >>> >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> You receive this message as a subscriber of the [hidden email] >>> >>> >>> mailing list. >>> >>> >>> To unsubscribe: mailto:[hidden email] >>> >>> >>> For general help: mailto:[hidden email]?subject=help >>> >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >>> >>> >>> >> >>> >>> >> >>> >>> >> -- >>> >>> >> You receive this message as a subscriber of the [hidden email] >>> >>> >> mailing list. >>> >>> >> To unsubscribe: mailto:[hidden email] >>> >>> >> For general help: mailto:[hidden email]?subject=help >>> >>> >> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >> >>> >>> >> >>> >>> >> -- >>> >>> >> You receive this message as a subscriber of the [hidden email] >>> >>> >> mailing list. >>> >>> >> To unsubscribe: mailto:[hidden email] >>> >>> >> For general help: mailto:[hidden email]?subject=help >>> >>> >> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >> >>> >>> > >>> >>> > >>> >>> > >>> >>> > -- >>> >>> > You receive this message as a subscriber of the [hidden email] >>> >>> > mailing list. >>> >>> > To unsubscribe: mailto:[hidden email] >>> >>> > For general help: mailto:[hidden email]?subject=help >>> >>> > OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> > >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Orbeon Forms - Web forms, open-source, for the Enterprise >>> >>> Orbeon's Blog: http://www.orbeon.com/blog/ >>> >>> My Twitter: http://twitter.com/avernet >>> >>> >>> >>> >>> >>> -- >>> >>> You receive this message as a subscriber of the [hidden email] >>> >>> mailing >>> >>> list. >>> >>> To unsubscribe: mailto:[hidden email] >>> >>> For general help: mailto:[hidden email]?subject=help >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >>> >>> >> >>> > >>> > >>> > >>> > -- >>> > You receive this message as a subscriber of the [hidden email] >>> > mailing >>> > list. >>> > To unsubscribe: mailto:[hidden email] >>> > For general help: mailto:[hidden email]?subject=help >>> > OW2 mailing lists service home page: http://www.ow2.org/wws >>> > >>> > >>> >>> >>> >>> -- >>> Orbeon Forms - Web forms, open-source, for the Enterprise - >>> http://www.orbeon.com/ >>> My Twitter: http://twitter.com/avernet >>> >>> >>> -- >>> You receive this message as a subscriber of the [hidden email] mailing >>> list. >>> To unsubscribe: mailto:[hidden email] >>> For general help: mailto:[hidden email]?subject=help >>> OW2 mailing lists service home page: http://www.ow2.org/wws >>> >> > > > > -- > You receive this message as a subscriber of the [hidden email] mailing > list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- Orbeon Forms - Web forms, open-source, for the Enterprise - http://www.orbeon.com/ My Twitter: http://twitter.com/avernet -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex,
Thanks for looking into this. I'm surprised it doesn't work in the currently nightly. It did in 3.7.1. Ethan On Tue, Feb 23, 2010 at 7:24 PM, Alessandro Vernet <[hidden email]> wrote: Hi Ethan, -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Administrator
|
Hi Ethan,
The autocomplete has been fully rewritten since 3.7.1. It is better in many way, but not at all when it comes to updating itself using a value that comes from an instance (as it is unable to do that!). And don't get me wrong: I'd like to implement this, but I just don't think that we'll be able to find the time for this in the very near future. If you feel like giving this a shot, I think we need: * In autocomplete.xbl to handle the xforms-value-changed and xforms-enabled event on external-value, pass the value. * When there is a value change, lookup the corresponding label in the itemset (I don't think we can do this in XForms right now without http://forge.ow2.org/tracker/index.php?func=detail&aid=314627&group_id=168&atid=350207 so either those functions need to be implemented, or this should be done in JavaScript). * If the value is found, populate the search field with the corresponding label. * Add a unit test for this to http://localhost:8080/orbeon/xforms-sandbox/sample/xbl/orbeon/autocomplete/autocomplete-unittest Alex On Tue, Feb 23, 2010 at 4:36 PM, Ethan Gruber <[hidden email]> wrote: > Hi Alex, > > Thanks for looking into this. I'm surprised it doesn't work in the > currently nightly. It did in 3.7.1. > > Ethan > > On Tue, Feb 23, 2010 at 7:24 PM, Alessandro Vernet <[hidden email]> > wrote: >> >> Hi Ethan, >> >> Your example is clear, and I was able to reproduce this. The issue is >> that the autocomplete doesn't initialize itself with the value from >> the instance. The code to do that is simply not there in the XBL >> component. We've never hit this case before because we always used the >> autocomplete in pages where is was used as a way to search for things, >> and so the initial value was always empty. >> >> I created a bug for this below, but unfortunately, unless we get a >> request to fix this from one of our clients, I am afraid we won't have >> the time to implement this in the near future. >> >> >> http://forge.ow2.org/tracker/index.php?func=detail&aid=314755&group_id=168&atid=350207 >> >> Alex >> >> On Sat, Feb 20, 2010 at 10:43 AM, Ethan Gruber <[hidden email]> wrote: >> > Okay, Alex, I grabbed the most recently nightly build and it looks like >> > the >> > error I noted with fr:autocomplete within nested xforms:repeat is >> > solved, >> > but it appears that there is a new issue. If you save a document after >> > entering one or more values into the fr:autocomplete field, when you >> > load >> > the document, the text node of that element doesn't load. There is are >> > inputs representing the number of values there should be, but the inputs >> > are >> > blank. If you double check the XML in exist, it's fine. The instance >> > inspector also shows the text node of the element. You can use one of >> > the >> > test views I sent you in the earlier email. The forms save and load >> > to/from >> > db/test/test.xml. >> > >> > Attached is an image that I hope will illustrate what I'm explaining. >> > Sorry >> > if it's confusing. >> > >> > Ethan >> > >> > On Fri, Feb 19, 2010 at 7:29 PM, Ethan Gruber <[hidden email]> >> > wrote: >> >> >> >> Um, let me retry that on the most recent nightly build. I think I was >> >> testing it on one from last week. >> >> >> >> On Fri, Feb 19, 2010 at 6:26 PM, Alessandro Vernet <[hidden email]> >> >> wrote: >> >>> >> >>> Ethan, >> >>> >> >>> How can I reproduce this? I am running test-fail, and without doing >> >>> anything else, the autocomplete seems to be working as far I can tell. >> >>> >> >>> Alex >> >>> >> >>> On Fri, Feb 19, 2010 at 8:07 AM, Ethan Gruber <[hidden email]> >> >>> wrote: >> >>> > Hi Alex, >> >>> > >> >>> > I have found the real culprit here, finally. It's not really an >> >>> > xi:include >> >>> > issue. It is an issue where the fr:autocomplete does not work if it >> >>> > is >> >>> > nested inside of an xforms:repeat that is also nested inside of an >> >>> > xforms:repeat. It worked fine in 3.7.1, but something must be a bit >> >>> > different in the newer builds. >> >>> > >> >>> > I have attached a zip with two views you can load into the sandbox, >> >>> > one >> >>> > labeled "pass", the other "fail" so you can get a look at what's >> >>> > going >> >>> > on. >> >>> > This is the last hurdle preventing me from using the the >> >>> > nightly/3.7.2 >> >>> > like >> >>> > builds. >> >>> > >> >>> > Ethan >> >>> > >> >>> > On Tue, Feb 9, 2010 at 2:14 PM, Ethan Gruber <[hidden email]> >> >>> > wrote: >> >>> >> >> >>> >> Hey Alex, >> >>> >> >> >>> >> I've been working on trying to produce a reproducible test case >> >>> >> today, >> >>> >> but >> >>> >> to no avail. Are there any issues with Orbeon handling 2 or more >> >>> >> layers of >> >>> >> xi:include? >> >>> >> >> >>> >> The data model I am working on is fairly complex, with a number of >> >>> >> repeatable elements that can occur within a variety of contexts. >> >>> >> In >> >>> >> my >> >>> >> attempt to modularize the project as much as possible, I have used >> >>> >> xi:include in many places. My test case involved moving the code: >> >>> >> >> >>> >> <xforms:repeat nodeset="language"> >> >>> >> <div style="margin-bottom:10px"> >> >>> >> <fr:autocomplete ref="." >> >>> >> dynamic-itemset="false" >> >>> >> style="float: left;"> >> >>> >> <xforms:label>Language</xforms:label> >> >>> >> <xforms:itemset >> >>> >> nodeset="instance('languageselect-template')//language"> >> >>> >> <xforms:label ref="name"/> >> >>> >> <xforms:value ref="name"/> >> >>> >> </xforms:itemset> >> >>> >> </fr:autocomplete> >> >>> >> <!--<xforms:input ref="."> >> >>> >> <xforms:label>Language</xforms:label> >> >>> >> </xforms:input>--> >> >>> >> <xforms:trigger appearance="minimal"> >> >>> >> <xforms:delete ev:event="DOMActivate" >> >>> >> nodeset="."/> >> >>> >> <xforms:label> >> >>> >> <img >> >>> >> src="/apps/ead/images/remove.gif"/> >> >>> >> </xforms:label> >> >>> >> </xforms:trigger> >> >>> >> </div> >> >>> >> </xforms:repeat> >> >>> >> >> >>> >> from an xml file that was included into the xhtml view into the >> >>> >> xhtml >> >>> >> file >> >>> >> itself, and it worked. But the nightly build doesn't seem to >> >>> >> handle >> >>> >> fr:autocomplete in included xml files properly. 3.7.1 did. It >> >>> >> doesn't seem >> >>> >> to be a universal problem with xi:include, because every other >> >>> >> input >> >>> >> works >> >>> >> correctly. >> >>> >> >> >>> >> Let me know if you need more info from me. >> >>> >> >> >>> >> Ethan >> >>> >> On Wed, Jan 27, 2010 at 2:33 PM, Alessandro Vernet >> >>> >> <[hidden email]> >> >>> >> wrote: >> >>> >>> >> >>> >>> Ethan, >> >>> >>> >> >>> >>> Yes, there were some improvements made to the fr:autocomplete >> >>> >>> recently, but I can't say if that could be the reason for the >> >>> >>> issues >> >>> >>> you are seeing. Would you be able to create a simple reproducible >> >>> >>> test >> >>> >>> case we can run in the XForms sandbox for this? >> >>> >>> >> >>> >>> Alex >> >>> >>> >> >>> >>> On Thu, Jan 7, 2010 at 8:20 AM, Ethan Gruber <[hidden email]> >> >>> >>> wrote: >> >>> >>> > >> >>> >>> > Hi Alex, >> >>> >>> > >> >>> >>> > I believe I have discovered the source of the error, after much >> >>> >>> > debugging. In the newer builds, has the autocomplete function >> >>> >>> > changed? I >> >>> >>> > am using autocomplete in two cases, and the result is "[No error >> >>> >>> > message >> >>> >>> > provided.]". >> >>> >>> > >> >>> >>> > The code is as follows: >> >>> >>> > >> >>> >>> > <fr:autocomplete ref="." dynamic-itemset="false" >> >>> >>> > style="float: left;"> >> >>> >>> > <xforms:label>Language</xforms:label> >> >>> >>> > <xforms:itemset >> >>> >>> > nodeset="instance('languageselect-template')//language"> >> >>> >>> > <xforms:label ref="name"/> >> >>> >>> > <xforms:value ref="name"/> >> >>> >>> > </xforms:itemset> >> >>> >>> > </fr:autocomplete> >> >>> >>> > >> >>> >>> > This works in 3.7.1, but not in the nightly build. >> >>> >>> > >> >>> >>> > Ethan >> >>> >>> > >> >>> >>> > >> >>> >>> > On Wed, Jan 6, 2010 at 7:09 PM, Alessandro Vernet >> >>> >>> > <[hidden email]> >> >>> >>> > wrote: >> >>> >>> >> >> >>> >>> >> Ethan, >> >>> >>> >> It would be good to figure out why. The nightly builds are >> >>> >>> >> quite >> >>> >>> >> stable now, and we're getting very close to cutting a release >> >>> >>> >> from >> >>> >>> >> a nightly >> >>> >>> >> build (yes, yes, I know you heard that before!). I'd be >> >>> >>> >> interested >> >>> >>> >> to know >> >>> >>> >> more about the problem, if you get a chance to investigate this >> >>> >>> >> further. >> >>> >>> >> Alex >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> On Jan 6, 2010, at 3:47 PM, Ethan Gruber <[hidden email]> >> >>> >>> >> wrote: >> >>> >>> >> >> >>> >>> >> I've tried the nightly build, but my application doesn't work >> >>> >>> >> at >> >>> >>> >> all >> >>> >>> >> in the nightly build. I don't even get a descriptive error. >> >>> >>> >> >> >>> >>> >> On Wed, Jan 6, 2010 at 6:28 PM, Alessandro Vernet >> >>> >>> >> <[hidden email]> >> >>> >>> >> wrote: >> >>> >>> >>> >> >>> >>> >>> Ethan, >> >>> >>> >>> rteConfig is there in the latest code (nightly builds). >> >>> >>> >>> Alex >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> On Jan 6, 2010, at 1:39 PM, Ethan Gruber <[hidden email]> >> >>> >>> >>> wrote: >> >>> >>> >>> >> >>> >>> >>> Thanks for the replies. To clarify, this is the xforms.js in >> >>> >>> >>> Orbeon >> >>> >>> >>> 3.7.1? I followed the directions for extracting the ops >> >>> >>> >>> folder >> >>> >>> >>> from the jar >> >>> >>> >>> into WEB-INF/resources, but the string "rteConfig" is not in >> >>> >>> >>> the >> >>> >>> >>> file >> >>> >>> >>> anywhere. I do find where the toolbar is defined in >> >>> >>> >>> xforms.js, >> >>> >>> >>> but I'm not >> >>> >>> >>> quite sure where the button functions are defined. The >> >>> >>> >>> function >> >>> >>> >>> that >> >>> >>> >>> defines what the "Bold" button does is not in this file, it >> >>> >>> >>> seems. I'd like >> >>> >>> >>> to get the hang of the yuiRTE by first changing bold and >> >>> >>> >>> italic >> >>> >>> >>> from <b> and >> >>> >>> >>> <i> to the syntax that I require--<emph render="bold"> and >> >>> >>> >>> <emph >> >>> >>> >>> render="italic">. After adapting the current buttons to the >> >>> >>> >>> new >> >>> >>> >>> syntax, >> >>> >>> >>> then I will understand how to add new ones. >> >>> >>> >>> >> >>> >>> >>> Thanks, >> >>> >>> >>> Ethan >> >>> >>> >>> >> >>> >>> >>> On Tue, Jan 5, 2010 at 9:31 PM, Dave McIntyre >> >>> >>> >>> <[hidden email]> wrote: >> >>> >>> >>>> >> >>> >>> >>>> I made a change along these lines a while ago. In xforms.js, >> >>> >>> >>>> replace the declaration of yuiRTE with something like >> >>> >>> >>>> >> >>> >>> >>>> // Create RTE object, using a default config >> >>> >>> >>>> unless >> >>> >>> >>>> YUI_RTE_CUSTOM_CONFIG is defined >> >>> >>> >>>> var config = { >> >>> >>> >>>> // Don't set width/height (done in CSS) >> >>> >>> >>>> }; >> >>> >>> >>>> var yui_config_type_check = typeof >> >>> >>> >>>> YUI_RTE_CUSTOM_CONFIG; >> >>> >>> >>>> if (yui_config_type_check != 'undefined') { >> >>> >>> >>>> config = YUI_RTE_CUSTOM_CONFIG; >> >>> >>> >>>> } >> >>> >>> >>>> >> >>> >>> >>>> var yuiRTE = new YAHOO.widget.Editor(control, >> >>> >>> >>>> config); >> >>> >>> >>>> >> >>> >>> >>>> and then include some suitable javascript declaration of the >> >>> >>> >>>> variable YUI_RTE_CUSTOM_CONFIG. However, I seem to recall >> >>> >>> >>>> that >> >>> >>> >>>> this >> >>> >>> >>>> involved some other tweaks to arrange that xforms.js gets >> >>> >>> >>>> loaded >> >>> >>> >>>> with >> >>> >>> >>>> defer="defer" so that the variable is available to be >> >>> >>> >>>> checked. >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> Alessandro Vernet wrote: >> >>> >>> >>>> >> >>> >>> >>>> Ethan, >> >>> >>> >>>> >> >>> >>> >>>> For this, you will only need to change the code in xforms.js. >> >>> >>> >>>> Like >> >>> >>> >>>> you >> >>> >>> >>>> said, that file is in a jar file, so you'll want to extract >> >>> >>> >>>> it, >> >>> >>> >>>> and >> >>> >>> >>>> put the extracted file, which you will modify, in your >> >>> >>> >>>> resources, >> >>> >>> >>>> under the same path, so it overrides the one in the jar file. >> >>> >>> >>>> You'll >> >>> >>> >>>> find more on JavaScript development for Orbeon Forms here: >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> http://wiki.orbeon.com/forms/doc/contributor-guide/javascript-development >> >>> >>> >>>> >> >>> >>> >>>> Then in xforms.js search for rteConfig, and you'll find the >> >>> >>> >>>> place >> >>> >>> >>>> where the RTE toolbar is initialized. As you'll see, this has >> >>> >>> >>>> not >> >>> >>> >>>> been >> >>> >>> >>>> designed for extensibility ;), so let us know if you have >> >>> >>> >>>> suggestions >> >>> >>> >>>> on how to make the RTE more easily configurable. >> >>> >>> >>>> >> >>> >>> >>>> Alex >> >>> >>> >>>> >> >>> >>> >>>> On Monday, January 4, 2010, Ethan Gruber <[hidden email]> >> >>> >>> >>>> wrote: >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> Hello, >> >>> >>> >>>> >> >>> >>> >>>> I'd like to modify the YUI RTE code to add plugins for a new >> >>> >>> >>>> set >> >>> >>> >>>> of >> >>> >>> >>>> buttons, which should be possible according to here: >> >>> >>> >>>> http://developer.yahoo.com/yui/editor/#toolbar . Has anyone >> >>> >>> >>>> sucessfully >> >>> >>> >>>> done this before? Where do I get started? I assume the js >> >>> >>> >>>> is >> >>> >>> >>>> contained in >> >>> >>> >>>> a jar file. >> >>> >>> >>>> >> >>> >>> >>>> Thanks, >> >>> >>> >>>> Ethan >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> >> >>> >>> >>>> -- >> >>> >>> >>>> ________________________________ >> >>> >>> >>>> >> >>> >>> >>>> Dave McIntyre Development Team Lead >> >>> >>> >>>> [hidden email] >> >>> >>> >>>> P: +64 9 638 0600 >> >>> >>> >>>> M: +64 21 212 8087 >> >>> >>> >>>> F: +64 9 638 0699 >> >>> >>> >>>> S: dave.mcintyre >> >>> >>> >>>> www.orionhealth.com >> >>> >>> >>>> >> >>> >>> >>>> This e-mail and any attachments are intended only for the >> >>> >>> >>>> person >> >>> >>> >>>> to >> >>> >>> >>>> whom it is addressed and may contain privileged, proprietary, >> >>> >>> >>>> or >> >>> >>> >>>> other data >> >>> >>> >>>> protected from disclosure under applicable law. If you are >> >>> >>> >>>> not >> >>> >>> >>>> the addressee >> >>> >>> >>>> or the person responsible for delivering this to the >> >>> >>> >>>> addressee >> >>> >>> >>>> you are >> >>> >>> >>>> hereby notified that reading, copying or distributing this >> >>> >>> >>>> transmission is >> >>> >>> >>>> prohibited. If you have received this e-mail in error, please >> >>> >>> >>>> telephone us >> >>> >>> >>>> immediately and remove all copies of it from your system. >> >>> >>> >>>> Thank >> >>> >>> >>>> you for your >> >>> >>> >>>> co-operation. >> >>> >>> >>>> >> >>> >>> >>>> __________ Information from ESET NOD32 Antivirus, version of >> >>> >>> >>>> virus >> >>> >>> >>>> signature database 4746 (20100105) __________ >> >>> >>> >>>> >> >>> >>> >>>> The message was checked by ESET NOD32 Antivirus. >> >>> >>> >>>> >> >>> >>> >>>> http://www.eset.com >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> -- >> >>> >>> >>> You receive this message as a subscriber of the >> >>> >>> >>> [hidden email] >> >>> >>> >>> mailing list. >> >>> >>> >>> To unsubscribe: mailto:[hidden email] >> >>> >>> >>> For general help: mailto:[hidden email]?subject=help >> >>> >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> -- >> >>> >>> >>> You receive this message as a subscriber of the >> >>> >>> >>> [hidden email] >> >>> >>> >>> mailing list. >> >>> >>> >>> To unsubscribe: mailto:[hidden email] >> >>> >>> >>> For general help: mailto:[hidden email]?subject=help >> >>> >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >>> >>> >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> -- >> >>> >>> >> You receive this message as a subscriber of the >> >>> >>> >> [hidden email] >> >>> >>> >> mailing list. >> >>> >>> >> To unsubscribe: mailto:[hidden email] >> >>> >>> >> For general help: mailto:[hidden email]?subject=help >> >>> >>> >> OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> -- >> >>> >>> >> You receive this message as a subscriber of the >> >>> >>> >> [hidden email] >> >>> >>> >> mailing list. >> >>> >>> >> To unsubscribe: mailto:[hidden email] >> >>> >>> >> For general help: mailto:[hidden email]?subject=help >> >>> >>> >> OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >>> >> >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > -- >> >>> >>> > You receive this message as a subscriber of the >> >>> >>> > [hidden email] >> >>> >>> > mailing list. >> >>> >>> > To unsubscribe: mailto:[hidden email] >> >>> >>> > For general help: mailto:[hidden email]?subject=help >> >>> >>> > OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >>> > >> >>> >>> >> >>> >>> >> >>> >>> >> >>> >>> -- >> >>> >>> Orbeon Forms - Web forms, open-source, for the Enterprise >> >>> >>> Orbeon's Blog: http://www.orbeon.com/blog/ >> >>> >>> My Twitter: http://twitter.com/avernet >> >>> >>> >> >>> >>> >> >>> >>> -- >> >>> >>> You receive this message as a subscriber of the [hidden email] >> >>> >>> mailing >> >>> >>> list. >> >>> >>> To unsubscribe: mailto:[hidden email] >> >>> >>> For general help: mailto:[hidden email]?subject=help >> >>> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >>> >> >>> >> >> >>> > >> >>> > >> >>> > >> >>> > -- >> >>> > You receive this message as a subscriber of the [hidden email] >> >>> > mailing >> >>> > list. >> >>> > To unsubscribe: mailto:[hidden email] >> >>> > For general help: mailto:[hidden email]?subject=help >> >>> > OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> > >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> Orbeon Forms - Web forms, open-source, for the Enterprise - >> >>> http://www.orbeon.com/ >> >>> My Twitter: http://twitter.com/avernet >> >>> >> >>> >> >>> -- >> >>> You receive this message as a subscriber of the [hidden email] >> >>> mailing >> >>> list. >> >>> To unsubscribe: mailto:[hidden email] >> >>> For general help: mailto:[hidden email]?subject=help >> >>> OW2 mailing lists service home page: http://www.ow2.org/wws >> >>> >> >> >> > >> > >> > >> > -- >> > You receive this message as a subscriber of the [hidden email] >> > mailing >> > list. >> > To unsubscribe: mailto:[hidden email] >> > For general help: mailto:[hidden email]?subject=help >> > OW2 mailing lists service home page: http://www.ow2.org/wws >> > >> > >> >> >> >> -- >> Orbeon Forms - Web forms, open-source, for the Enterprise - >> http://www.orbeon.com/ >> My Twitter: http://twitter.com/avernet >> >> >> -- >> You receive this message as a subscriber of the [hidden email] mailing >> list. >> To unsubscribe: mailto:[hidden email] >> For general help: mailto:[hidden email]?subject=help >> OW2 mailing lists service home page: http://www.ow2.org/wws >> > > > > -- > You receive this message as a subscriber of the [hidden email] mailing > list. > To unsubscribe: mailto:[hidden email] > For general help: mailto:[hidden email]?subject=help > OW2 mailing lists service home page: http://www.ow2.org/wws > > -- Orbeon Forms - Web forms, open-source, for the Enterprise - http://www.orbeon.com/ My Twitter: http://twitter.com/avernet -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Thanks for helping me get started. I'll get back to the list if I figure it out.
Ethan On Tue, Feb 23, 2010 at 7:49 PM, Alessandro Vernet <[hidden email]> wrote: Hi Ethan, -- You receive this message as a subscriber of the [hidden email] mailing list. To unsubscribe: mailto:[hidden email] For general help: mailto:[hidden email]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws |
Free forum by Nabble | Edit this page |