Hi Greg, thanks for the infos ... > OK, I think I understand. Yes, you can write a Pivot app that will > dynamically load WTKX files. This would not be terribly difficult to do. For > example, if you had a URL instance, you could write: > > WTKXSerializer wtkxSerializer = new WTKXSerializer(); > Component component = (Component)wtkxSerializer.readObject(url.openStream()); Ok, but this can works also if inside the wtkx file/s i define many elements, like forms, fields, tables, etc all together (so in this case I should got a reference to the container that holds them, like the current page in Web Browsers) ? I imagine something like tabContents = wtkxSerializer.readObject(urlForStartPage);
And after this, if i have to load another wtkx files/s (or reload the same), am i able to destroy all the content created before (keeping my fixed content, but defined outside), and substitute with the new content (form new wtkx file/s) ? So i can do another time tabContents = wtkxSerializer.readObject(urlForStartPage); where now urlForStartPage could have point to another URL ... > You would probably want to do this in a Task so it doesn't bog down the UI > thread while loading the content. You could then add the component to a > TabPane or wherever it made sense in your UI. Ok. > The WTKX files could even by dynamically generated on the server, if that > made sense for your application. Great. Thanks, Sandro
