-
|
I am experimenting with Fore and like what I see, but I can't get controls to display when they are bound to elements that don't (yet) exist in the xml document to which the default instance is bound. I have done as follows:
I then have explicitly created controls bound to all elements and attributes in the default instance. After the page has loaded, all these are duly displayed, without text content, just as expected. When I click the button, the default instance is replaced by the xml doc found at the url in point 6 above and the text content of the non-empty elements and attributes is shown in the controls bound to these, but all the controls bound to elements or attributes not existing in this xml doc disappear from view, become nonrelevant. I am editing the html page in eXide, which even with an hml page having the extension ".html" (corresponding to the chosen file type) and headed by " Any help would be much appreciated. Henrik Thiil Nielsen |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hello Henry, seems you've done right as far as i can tell from your description. However it would be more helpful to share a complete page or at least the fx-fore element block along with the data you're loading. You're editing in eXide which MAY be part of the issue. Unfortuneltely eXide does not properly serialize html sometimes auto-closing elements when it shouldn't. Example: serializes to which is fine for XML but not HTML. All html element must have an explicit closing tag with very few eceptions like meta, link, input, img... This results in a different DOM when parsed again in a browser and eventually completely break the page. I would recommend to edit in another editor and synchronize via eXide or just copy/paste to eXide and save. This resolves the serialization issue. Search your page for '/>' and correct those if any. This MAY the problem but there might be others which i can't tell without seeing the markup in complete. I hope the issue in eXide can one day finally be addressed cause it hurts eXistdb users for quite some time. (Note: as an alternative to eXide you can also use Visual Studio with existdb plugin to edit pages. With the plugin your edits will automatically be synchronized to eXistdb. This is nowadays the preferred method of most devs and avoids the abovementioned issues.) |
Beta Was this translation helpful? Give feedback.
-
|
Hello Joern, Thanks. I will avoid eXide and stick with Oxygen but also give VS Code a try for this purpose. I have got a minimal test case working wihout problems and will build on that. |
Beta Was this translation helpful? Give feedback.
Hello Henry,
seems you've done right as far as i can tell from your description. However it would be more helpful to share a complete page or at least the fx-fore element block along with the data you're loading.
You're editing in eXide which MAY be part of the issue. Unfortuneltely eXide does not properly serialize html sometimes auto-closing elements when it shouldn't.
Example:
when saving in eXide it may something like this:
serializes to
which is fine for XML but not HTML. All html element must have an explicit closing tag with very few eceptions like meta, link, input, img...
This results in a different DOM whe…