Hi CP,
On 3/25/2013 8:45, ChilliPeppers wrote:
Hi Holger,
I installed 4.2 over the weekend and have had a look at the new
SWP/SWA features. I was very pleased with the new Default Application
and the Gadgets and Events Hub looks very powerful and useful. Will
start exploring further with it this week.
Thanks for your feedback. The new gadgets framework is indeed hopefully
a nice simplification for application building. 4.2 has the first
release of this architecture, and more will follow in 4.3. We are
currently scheduled to do one major release per quarter, so 4.3 would
take us into June/July. We could certainly make pre-releases available
to interested power users.
One thing I that is quite important for me is for users of my
application to be able to input data into a form an update a knowledge
base. I noticed that form editing is still "for demo purposes only".
Can you let us know if you have any plans for more robust support of
Form Editing in in the near future?
Yes this is exactly on our roadmap for 4.3. In fact I have done the
first stage of generalizations last week. I have generalized the EVN
platform which provides not just an editing environment based on SWA
forms but also capabilities to create working copies (aka branches),
track the change history and undo capabilities. In 4.2, only EVN's
Vocabulary Editor and Tagger will be available with these capabilities,
but for 4.3 we will open this up so that people can plug in their own
editors and project types. We plan to include a pure RDFS/OWL editor as
well, and all those editors should be based on the gadgets framework.
The reason why it's still marked as work in progress is that I am not
happy with the event mechanism yet. Think about cases in which someone
edits a property on the form and the tree view needs to update to
reflect those changes. In EVN this is working through some rather ugly
JavaScript code. I want to clean this up before encouraging outside
developers to go down the same route. I guess I will provide a gadget
swa:SwitchableFormGadget that issues the correct events to the event
hub, and then have the trees and other gadgets react to change events
"correctly". Since the SWA tree is so flexible and may carry data from
any SPARQL query, it's not trivial to get this right.
I hope this clarifies things. If you have any other feedback and
criticism, feel free to post it here.
Thanks
Holger
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages 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
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
