Hi Michael, Please find my responses bellow :
Michael K. Bergman wrote: > Hi Mitko, > > Excellent and thanks for the quick response! See some quick > clarification questions below. I will follow these steps and post > back soon about my success . . . > > (removed for brevity) > > A. In order to begin with ODS as the starting VSPX, should I get the > source code from the distribution on Sourceforge? Is it the latest > and current version? If you going to write a new application using the ODS framework, the SF distribution is sufficient. As for the ODS framework itself we continue to extend it, but we keep architecture compatible. > > B. Are the ODS app's individual vspx files the ones in > appsrc\ODS-xyz\www\*.vspx (with or without the \www subdirectory) (in > other words, ignore all of the VADs)? Yes, every application within ODS and Framework itself are under ~appsrc/ODS-*. As for VAD packages, they are to deploy the applications, therefore you should look at vspx&sql &xslt for reference material. > > C. Is ODS-Framework the root directory for ODS? In order to begin > modifications, how do I rename and call the new app (such as > ODSMikeVersion) and do I need to give it a port address to run? The Framework is a let say container of all ODS applications, you write a new application using the Framework interfaces (tables, implement overriding user defined types etc.) and such application can be used as part of ODS dataspaces. > > D. Is there any documentation or architectural diagrams showing the > file relationships within ODS? There are development specifications and wiki articles, but they are not published VOS wiki yet, needs some updates, cleanup etc. > > E. Any other general develop hints or guidelines? Here is a short check list of an ODS Application development : 1) create a (user defined type) UDT under DB.DBA.web_app 2) override web_app methods, can see examples from let say: appsrc/ODS-Bookmark/sql/bmk-a-wa.sql 3) register the application by inserting a row in WA_TYPES , can be see in file above 4) register valid application member types in WA_MEMBER_TYPE table (this and p.3 should be really API calls) 5) use Virtuoso users table to authenticate, or re-use the ODS login control. 6) include ODS bar in the application , something similar to <xsl:include href="http://local.virt/DAV/VAD/wa/comp/ods_bar.xsl"/> inside application vspx macro-expansion xslt style. and put at top of the page templates : <ods:ods-bar app_type='Bookmark'/>. strictly speaking p1 to p.5 are mandatory, where p.6 is to show the navigation within ODS data spaces. As for VSPX development in general, i recommend to use VSPX macro-expansion style sheets, so you can re-use some parts of work as macros (e.g. ods-bar) . Best Regards, Mitko > > [snip] > > Thanks! I'm pleased I can develop within a standard file system > framework. (And be able to use Eclipse!) :) > > Mike -- Mitko Iliev Developer Virtuoso Team OpenLink Software http://www.openlinksw.com/virtuoso Cross Platform Web Services Middleware
