Hi,
I've attached a setupdb script for OpenGuides created for 2 reasons
1) it seems silly to have to remember the arguments for cgi-wiki-setupdb when you've already input them into a perfectly good wiki.conf file 2) it can input some standard nodes (like Text Formatting Tips, sample licensing etc.) for an OpenGuides distribution.
Hopefully should be pretty clear from script and basic POD. Any suggestions?
(Tested on Win32 with Mysql and SQLite) -- osfameron
Osfameron said:
(Tested on Win32 with Mysql and SQLite)
Oh yes, and on Debian with SQLite. Works fine, though I had to do 'perl openguides-setupdb': I thought it was supposed to parse the #!perl shebang? Do I need to package it in some way (Like pl2bat on Win32)?
On Thu 24 Jun 2004, Hakim hakim@cassimally.net wrote:
Oh yes, and on Debian with SQLite. Works fine, though I had to do 'perl openguides-setupdb': I thought it was supposed to parse the #!perl shebang? Do I need to package it in some way (Like pl2bat on Win32)?
This kind of script is best packaged in the distribution, like cgi-wiki-setupdb is packaged in the CGI::Wiki distribution.
Now, it is a good idea and it's certainly a helpful thing, but what I have in mind for the install procedure is to entirely get rid of all the questions in Build.PL and have a separate install script - openguides-setup - that you run in your openguides directory and it looks at your wiki.conf and writes out wiki.cgi (or whatever you want to call the file) and the templates, and also sets up the database tables. So what yours does but more.
So I'm not really wanting to include your script just yet given that I'm planning a similar thing with more functionality. I'm willing to be talked around though.
The things that are holding up openguides-setup:
- Too much stuff in wiki.cgi, need to move it to OpenGuides.pm I am working on this.
- The endless templates problem - what do we do about custom templates.
I've attached the rough skeleton that I just knocked up - don't blindly run it and overwrite your scripts and complain at me please :) It doesn't do what it's meant to yet; you'll probably be able to spot the gaps. I'm not going to do any more with it until I finish gutting wiki.cgi.
Kake
On Thu, Jun 24, 2004 at 06:32:17PM +0100, Kate L Pugh wrote:
...snippage...
The things that are holding up openguides-setup:
Too much stuff in wiki.cgi, need to move it to OpenGuides.pm I am working on this.
The endless templates problem - what do we do about custom templates.
Out of interest, where is getting Openguides to work on other grids/ellipes on the large Things To Do list?
I only ask because it always seemed to me that the principal selling point of Openguides was the ability to relate pages in real space, that's what sets it apart from other wikis in my mind anyway.
Stephen
On Thu 24 Jun 2004, Stephen Stewart beowulf@carisenda.com wrote:
Out of interest, where is getting Openguides to work on other grids/ellipes on the large Things To Do list?
I took it off my Things To Do list when Ivor said he was going to work on it. If he's not going to have time to do anything about it then I can put it back on mine, but I do need to know if this is the case.
Kake
----- Original Message ----- From: "Kate L Pugh" kake@earth.li To: "OpenGuides software developers" openguides-dev@openguides.org Sent: 25 June 2004 00:29 Subject: Re: [OpenGuides-Dev] openguides-setupdb script
On Thu 24 Jun 2004, Stephen Stewart beowulf@carisenda.com wrote:
Out of interest, where is getting Openguides to work on other grids/ellipes on the large Things To Do list?
I took it off my Things To Do list when Ivor said he was going to work on it. If he's not going to have time to do anything about it then I can put it back on mine, but I do need to know if this is the case.
The state of this is that I released a plugin in the form of CGI::Wiki::Plugin::Locator::UTM
This contains its own distance finder, and the necessary code to translate between lat/long and zone/easting/northing. To do this, the module requires an additional piece of data by way of the ellipsoid. This needs to be prompted for in the setup, and held in the config file.
In terms of metadata, the module needs (and relies on) latitude and longitude. The pythagorean distance finder needs zone, easting and northing. The plugin will provide these via the location method. The distance finder needs zone, easting and northing to be stored in the database.
By the way, I have a Postgres problem with type conversion. How do I force it to use a float (or rather a double)? This is a problem with the distance finder on Postgres.
When it comes to integrating this with OpenGuldes, I started this many releases ago. I will probably need to start again with my changes. Kake: I'm happy for you to take this over if you have the time to do so. Or, let me know if you want me to continue.
Let me know of any issues with C::W::P::L::U.
Ivor.
On Sun 27 Jun 2004, IvorW ivorw-openguides@xemaps.com wrote:
The state of this is that I released a plugin in the form of CGI::Wiki::Plugin::Locator::UTM
How does this mesh with zool's work? Are your plugins complementary or should we pick one or the other?
Kake
On Mon, Jun 28, 2004 at 12:03:37AM +0100, Kate L Pugh wrote:
The state of this is that I released a plugin in the form of CGI::Wiki::Plugin::Locator::UTM
How does this mesh with zool's work? Are your plugins complementary or should we pick one or the other?
an additional piece of data by way of the ellipsoid. This needs to be prompted for in the setup, and held in the config file.
i kind of assume it will always be wgs84 - 23 for Geo::Coordinates::UTM - or nad83 which is centimetres of difference. this is what gps, the big mapping sites, etc use - this could be a default config option without a prompt?
In terms of metadata, the module needs (and relies on) latitude and longitude. The pythagorean distance finder needs zone, easting and northing. The plugin will provide these via the location method. The distance finder needs zone, easting and northing to be stored in the database.
i never needed to use the zone, but things will blow up if a guide spans more than one and gets different spatial references? as 'easting' and 'northing' rather than os_x / os_y?
then i think the 2 plugins should be totally compatible, and i just change mine to use base CGI::Wiki::Plugin::Locator::UTM, and add the geocoding method. nice one ivor.
a further thought! Schuyler objects that distances in metres and kilometres meant little to people not used to seeing them / converting between them and yards/miles, e.g. pesky merkins. i could do metre/mile conversion and change the distances - or keep it like it is - but it's definitely a question.
zx
openguides-dev@lists.openguides.org
-
Hakim -
IvorW -
Jo Walsh -
Kate L Pugh -
Osfameron
-
Stephen Stewart