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 . . .
Mitko Iliev wrote:
Hi Michael,
In order to perform rapid development of VSP/VSPX pages I suggest you to
use file system for development, in this way you may work even with your
favorite editor.
After development phase is complete on file system you can deploy the
application in WebDAV using Web folders or any other WebDAV capable user
agent.
The Windows WebDAV folders are not accessible via all Windows
applications, they are supported natively to my knowledge by MS Office
applications, Macromedia Dreamweaver or Adobe GoLive. Also the
development within WebDAV would require setup of two Virtual Directories
(one to edit, another to execute) as WebDAV don't have (edit/read &
execute methods, it has just retrieval via GET/POST) .
The following is a basic steps to get VSPX/VSP to work on file system,
using Conductor UI :
1) create a physical directory under HTTP ServerRoot can be seen from
the INI file, HTTPServer section ServerRoot setting.
2) put the VSPX pages in directory from p.1
3) create Virtual Directory (VD) using Conductor UI : 'WebDAV&HTTP' ,
'HTTP Hosts & Directories'
The requirement for the VD is to have 'Physical path' set to file system
location and "VSP User" set to some user which has SQL permissions to
SQL tables and objects used in the active pages in the project.
OK, that looks pretty straightforward.
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?
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)?
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?
D. Is there any documentation or architectural diagrams showing the
file relationships within ODS?
E. Any other general develop hints or guidelines?
[snip]
Thanks! I'm pleased I can develop within a standard file system
framework. (And be able to use Eclipse!) :)
Mike