Kim; It is the case that Composer-ME can serve a localhost environment. But the current situation w.r.t. client-side libraries is changing in 3.0, as there has been a fundamental architectural change from 2.x versions of Ensemble (as shown in the Calendar brief).
TopBraid Ensemble 2.0 is an example application running on TopBraid Live, to serve as a demonstration of out-of-the-box Flex user interface components that Flex application developers could reuse for custom applications. For example, to build the Calendar App described in the white paper. Ensemble 2.0 is available on a request basis with the above caveats. In release 3.0, TBE has been re-architected as a full fledged semantic web application assembly toolkit; the Flex components became configurable. This means that in 3.0 users (who are not necessarily Flex developers) can select and deselect components, change their layout, couple component events with actions, modify the way components interact with each other and save the result as a custom application such as the Calendar App - all without programming in ActionScript. Additionally, 3.0 release includes an SDK for developing custom components and provides much cleaner APIs than those available in 2.0. Configurability is the key functionality of TBE 3.0 and is available in beta 1. Having said this, TBE port to the new architecture is still work in progress. For beta 1, not all of the TBE UI components have been ported. Specifically, trees, grids, forms and map have been ported, but not the graph component or the calendar component. Additional components are likely to be available for beta 2 in February. Beta 2 will also include integration of SPARQLMotion with TBE making it possible to create even greater degree of customizable actions and features. Finally, in beta 1 our focus has been the new architecture with most of the performance optimizations left for the later releases. For the reasons above, beta 1 of TBE 3.0 is by invitation only. As the broader beta becomes available next month, we will include you in the list. -- Scott/Irene On Jan 13, 8:56 pm, KimT <[email protected]> wrote: > Hi, > > I have recently developed a feature catalogue ontology using Composer > ME and want to build a web-based application to access/manage the > instance data contained in the model. I have been examining the > Calender management application, described on the TopBraid Live site, > to try and see how to use Composer ME and FlexBuilder to create a > small demo (or pilot) using the Composer tool. The notes on the site > imply that the tools required to build the calender app are Composer, > Flex Builder and TopBraid Live but that Composer ME can be used in > stand-alone mode because it has a built-in application server. I > haven't purchased TopBraid Live. > > I can't find any of the client-side libraries or scripts mentioned in > the calender app documentation. Is this because I only have Composer > ME and these libraries and scripts come packaged with TopBraid Live ? > Is it possible to obtain the necessary component libraries and scripts > to see how these apps can be built and deployed or will this make no > sense if I do not have the full TopBraid Live environment in which to > deploy them ? > > I have looked on this site for similar questions and hope that I'm not > repeating the question by Jody posted on the 9th, which is probably > the most similar issue I could see being discussed. > > Regards, KimT --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
