Hi Mitko,
I would like to suggest that the best way to conclude this thread is to
volunteer more details and instructions. We are getting there (and I am
documenting complete steps as they are verified! :) ), but we seem to be
progressing only millimeters at a time. :)
Please see below:
M
Hi Michael,
I meant to say that instructions for editing ODS-Framework applies only
to it, therefore only it have to be copied.
The ODS applications like Bookmark, Briefcase etc. except Blog must have
filesystem VAD packages, so if you install let say
ods_bookmark_filesystem.vad, you can edit the
Hi Mitko,
I don't understand.
Are you saying that if I put the source files for ODS-Wiki,
ODS-Bookmark, ODS-Briefcase, etc., etc., under 'wa' and then invoke
init.sql that I will then be able to edit their source code under the
physical file system?
Or, when you say, "As for other applicati
Hi Michael,
You need only appsrc/ODS-Framework copied as wa under web root.
As for other applications they provide filesystem based VAD packages,
except ODS-Blog which is WebDAV only oriented because of templates. I
will check if ODS-Blog can be run for development from file system and
let you
Hi Mitko,
OK, I think this is the last important question for now:
In my CVS or \appsrc directories where ODS-Framework is located, there
are also many other sibling ODS-OtherApp directories.
1. Do these need to get copied over to the new 'wa' directory under the
vsp root?
2. If so, do t
Hi Michael,
I forgot to clarify that points mentioned in previous mail are on basis
of having a local source distribution or CVS checkout at very least
'appsrc' and 'binsrc/oat' .
Please find the rest of responses bellow:
Michael K. Bergman wrote:
Hi Mitko,
Could you expand on the initial s
Hi Mitko,
Could you expand on the initial set up for this? I'm still confused
about how to set up the beginning file/directory structure.
Also, please see the other questions below.
I know I'm a newbie about this stuff, but I'm trying to get over the
hump and actually do some productive dev
Hi Michael,
The directory structure for file system development to be used with
init.sql is :
/appsrc/ODS-Framework -> /wa/
/binsrc/oat/toolkit/ -> /wa/oat/
/binsrc/oat/images/ -> /wa/images/oat/
As for a script to do that, you are right, we should have such a script
placed in cvs. I'll try t
Hi Mitko,
I can get the script to run without error so long as I run it in the
same directory where the files wa_search_procs.sql and wa_template.sql
reside.
But I'm still not sure what the starting file structure should be. I
continue to get this error when I http://localhost:8890/ods/:
Hi Mitko,
Unfortunately, I have more questions:
Mitko Iliev wrote:
Hi Michael,
The ODS framework has no file system VAD package as it's user home
temples mechanism is WebDAV oriented.
However it's possible to setup the ODS to run in file system.
To do that i.e. to make appropriate virtual dire
Hi Mitko:
Mitko Iliev wrote:
Hi Michael,
The ODS framework has no file system VAD package as it's user home
temples mechanism is WebDAV oriented.
My question arose from the quote on
http://virtuoso.openlinksw.com/wiki/main/Main/OdsConfig:
"Alternately, you can install the ods_filesystem.va
Hi Michael,
The ODS framework has no file system VAD package as it's user home
temples mechanism is WebDAV oriented.
However it's possible to setup the ODS to run in file system.
To do that i.e. to make appropriate virtual directories etc. you may do
the following:
* suppose ODS Framework director
Hi All,
I am renewing an older thread entitled, "VSPX, WebDAV, UI and Windows
Issues" that last had Mitko providing response on 4/24-4/25. That
earlier information has proven helpful, but not yet fully sufficient.
I anticipate there may be a number of these new posts as I again try to
work
Hi All,
I am renewing an older thread entitled, "VSPX, WebDAV, UI and Windows
Issues" that last had Mitko providing response on 4/24-4/25. That
earlier information has proven helpful, but not yet fully sufficient.
I anticipate there may be a number of these new posts as I again try to
work
14 matches
Mail list logo