On Jul 30, 2010, at 6:14 PM, John Perdoni wrote:
> Thank you Holger for the steer in the right direction, I managed to
> get it to work by escaping the # with %23.
I am glad I could help.
> On another note would it be possibe for you to give a quick outline of
> what is changing for 3.4,
Lots of improvements in general. I am using it myself right now to develop a
next generation tool for TopQuadrant. This is a complete web application,
including Ajax callbacks and stand-alone web pages, all component-based and
ontology-driven. This exercise leads to improvements to UISPIN along the way.
Here is a list of a few improvements that I wrote down, but there are others
- Feature: UISPIN now part of TopBraid Live stand-alone
- Feature: Added ui:else and ui:setContext control elements to UISPIN
- Feature: Added ui:parse for inserting arbitrary XML from parsing a text
- Feature: Added html:encodeBRs for converting raw line breaks into <br />
- Feature: Added ui:addNamespace to dynamically add xmlns declarations to a
document
- Feature: Support for &nsbp; entity in UISPIN
- Feature: UISPIN can now be used to generate (almost) arbitrary XML - unknown
elements
will be mapped to their qnames, and corresponding xmlns declarations
added.
- Feature: Default TUI widgets now generate RDFa automatically
- Feature: Added ui:priority to make overloading the default (TUI) views easier
- Feature: Added ui:name and ui:defaultBaseURI to conveniently access "global"
app pages
- Feature: Added ui:insertionPoint and ui:insert control elements
- Feature: Added ui:update control element
- Feature: Added ui:createLink control element
- Feature: Added ui:throw control element
- Feature: Added ui:errorPrototype
- Change: ui:let has been deprecated and replaced with ui:group
- Bug fix: Global .ui. graphs (including .tui.) were not regognized after first
launch
- Bug fix: TUI.css stylesheet no longer contains global definitions
- Bug fix: UISPIN now generates relative CSS file paths (and copies them into
/tbl/css on demand)
> the prospective release date
End of September, with 3.4.0
> and whether or
> not the mapping of uispin elements will include Flex Components.
It won't include Flex components, but a library of interactive JavaScript
components (like a Tree) based on ExtJS, at least as a first version and to
demonstrate how arbitrary components can be developed.
Regards,
Holger
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
