From jan at intevation.de Mon Aug 4 15:37:27 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Mon, 4 Aug 2003 15:37:27 +0200 Subject: [Thuban-list] term for extensions Message-ID: <20030804133727.GA15916@intevation.de> Hi, Thuban is designed to be extensible. I am currently writing samples for this. It occured to me that so far we don't have a common term for such things. Some options that come to my mind are Extension Add-On Extra Plug-In I like Extension, but the term is already used for 3rd-party modules like proj, shapelib etc ... Any comments, suggestions? Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From Heiko.Kehlenbrink at vermes.fh-oldenburg.de Tue Aug 5 08:29:47 2003 From: Heiko.Kehlenbrink at vermes.fh-oldenburg.de (Heiko.Kehlenbrink@vermes.fh-oldenburg.de) Date: Tue, 05 Aug 2003 08:29:47 +0200 (CEST) Subject: [Thuban-list] term for extensions In-Reply-To: <20030804133727.GA15916@intevation.de> References: <20030804133727.GA15916@intevation.de> Message-ID: <1060064987.3f2f4edb6e76e@mail-ole.fh-oldenburg.de> Quoting Jan-Oliver Wagner : Hi Jan, > Hi, > > Thuban is designed to be extensible. > I am currently writing samples for this. > > It occured to me that so far we don't have a > common term for such things. > > Some options that come to my mind are > Extension > Add-On > Extra > Plug-In > > I like Extension, but the term is already used for > 3rd-party modules like proj, shapelib etc . > > Any comments, suggestions? Thinking about enhancement... regards heiko > > Jan > > -- > Jan-Oliver Wagner http://intevation.de/~jan/ > > Intevation GmbH http://intevation.de/ > FreeGIS http://freegis.org/ > > _______________________________________________ > Thuban-list mailing list > Thuban-list at intevation.de > https://intevation.de/mailman/listinfo/thuban-list > > From frank.koormann at intevation.de Wed Aug 6 15:43:35 2003 From: frank.koormann at intevation.de (Frank Koormann) Date: Wed, 6 Aug 2003 15:43:35 +0200 Subject: [Thuban-list] term for extensions In-Reply-To: <20030804133727.GA15916@intevation.de> References: <20030804133727.GA15916@intevation.de> Message-ID: <20030806134335.GA30848@intevation.de> * Jan-Oliver Wagner [030804 15:38]: > Hi, > > Thuban is designed to be extensible. > I am currently writing samples for this. > > It occured to me that so far we don't have a > common term for such things. > > Some options that come to my mind are > Extension > Add-On > Extra > Plug-In > > I like Extension, but the term is already used for > 3rd-party modules like proj, shapelib etc ... > > Any comments, suggestions? > During a local disussion the question was raised regarding the names of other stars in the Draco constellation http://www.astro.wisc.edu/~dolan/constellations/constellations/Draco.html lists them. Regards, Frank -- Frank Koormann Professional Service around Free Software (http://intevation.net/) FreeGIS Project (http://freegis.org/) From jan at intevation.de Wed Aug 6 16:00:11 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Wed, 6 Aug 2003 16:00:11 +0200 Subject: [Thuban-list] Roadmap changes Message-ID: <20030806140011.GA2378@intevation.de> Hi, I've shifted the roadmap for another 15 days. There are several reasons for this. One is that for the developers at Intevation paid Free Software projects have higher priority. Others are: * instead of just a preliminary manual, we already invested time to have a full one corresponding to the 0.8.1 release. I will make this available as pdf and html later this week (it's in the CVS of course). * the OGC SF SQL patch was against Thuban 0.2.0 and since then Thuban grew a lot making it necessary to extend the patch quite a lot. Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Fri Aug 8 12:31:11 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Fri, 8 Aug 2003 12:31:11 +0200 Subject: [Thuban-list] term for extensions In-Reply-To: <20030804133727.GA15916@intevation.de> References: <20030804133727.GA15916@intevation.de> Message-ID: <20030808103111.GA4240@intevation.de> So far, I received one pro Plug-In, and many against Plug-In. Also, Add-On was not a favorite. A new proposal was "Companion" in order to have some sort of special branding. Like "Product" for Zope. So, we might want to use the term "a Thuban Companion" analog to "Zope Product" ? Further thoughts? On Mon, Aug 04, 2003 at 03:37:27PM +0200, Jan-Oliver Wagner wrote: > Thuban is designed to be extensible. > I am currently writing samples for this. > > It occured to me that so far we don't have a > common term for such things. > > Some options that come to my mind are > Extension > Add-On > Extra > Plug-In > > I like Extension, but the term is already used for > 3rd-party modules like proj, shapelib etc ... > > Any comments, suggestions? -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Mon Aug 11 14:40:12 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Mon, 11 Aug 2003 14:40:12 +0200 Subject: [Thuban-list] User's Manual for Thuban 1.0 version 1.0pre1 Message-ID: <20030811124012.GA10032@intevation.de> Hi, I just put online the User's Manual for Thuban 1.0. It is version 1.0pre1 and there is a pdf-file as well as online html. See http://thuban.intevation.org/documentation.html Hope you like it. Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Tue Aug 12 12:35:08 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Tue, 12 Aug 2003 12:35:08 +0200 Subject: [Thuban-list] term for extensions In-Reply-To: <20030808103111.GA4240@intevation.de> References: <20030804133727.GA15916@intevation.de> <20030808103111.GA4240@intevation.de> Message-ID: <20030812103508.GA11050@intevation.de> On Fri, Aug 08, 2003 at 12:31:11PM +0200, Jan-Oliver Wagner wrote: > A new proposal was "Companion" in order to have some sort > of special branding. Like "Product" for Zope. > So, we might want to use the term "a Thuban Companion" analog > to "Zope Product" ? > Further thoughts? no further thought came in. 'Companion' had the most pro's so far (though in total not many comments arrived). So, if noone objects soon (perhaps with a better alternative :-) the Thuban extensions will be called Thuban companions. Cheers Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From bh at intevation.de Tue Aug 12 13:17:36 2003 From: bh at intevation.de (Bernhard Herzog) Date: Tue, 12 Aug 2003 13:17:36 +0200 Subject: [Thuban-list] term for extensions In-Reply-To: <20030812103508.GA11050@intevation.de> (Jan-Oliver Wagner's message of "Tue, 12 Aug 2003 12:35:08 +0200") References: <20030804133727.GA15916@intevation.de> <20030808103111.GA4240@intevation.de> <20030812103508.GA11050@intevation.de> Message-ID: <6qekzrktv3.fsf@salmakis.intevation.de> Jan-Oliver Wagner writes: > On Fri, Aug 08, 2003 at 12:31:11PM +0200, Jan-Oliver Wagner wrote: >> A new proposal was "Companion" in order to have some sort >> of special branding. Like "Product" for Zope. >> So, we might want to use the term "a Thuban Companion" analog >> to "Zope Product" ? >> Further thoughts? > > no further thought came in. > 'Companion' had the most pro's so far (though in total not many > comments arrived). > > So, if noone objects soon (perhaps with a better alternative :-) > the Thuban extensions will be called Thuban companions. Well, what do you mean precisely when you talk about a "Thuban Companion"? For instance, a Zope product is a very specific thing and there are ways to extend Zope without using products. So how does this compare to a "Thuban Companion"? I think that we have look at this from a few different angles: - What do you call an extension when you talk about the general concept of extending Thuban in a manual? - What do you call them in the user interface? - What do you call specific variants of extensions? Different kinds of extensions could be - New but perhaps simple commands in the menu - New interactive tools - Support for new file formats - Support for new database backends - What do you call the directory where you put those extensions that come with Thuban (the directory name was the main objection to using the term "extension") - What do we call an extension mechanism in the Thuban code? It seems to me that in the (introductory) documentation and user interface it's best to use terms that new users will understand more or less without further explanations. Most users have heard about extensions, plug-ins or add-ons, for instance. In the code it's a different matter. The developers of the "twisted" library for instance like to use unusual names (e.g. "jelly" for object serialization) not only because it adds some fun, but also because often the "normal" terms are already used for very similar but subtly different things by other projects. I'm not sure how well that argument would apply to Thuban, but at least terms like add-on or plug-in are quite heavily used for specific but always somewhat different ways to extend programs. I think "extension" is pretty generic for something that extends a program so I'd say we should use that as a collective noun for anything that extends Thuban. The only downside is that there's already a directory called "extension" in the Thuban sources which contains Python extension modules. On the plus-side that there's also a directory called simple_extensions in the Examples directory. "Companion" should then only be used for something more specific that is directly supported by some Thuban infrastructure. The modules in Examples/simple_extensions/ wouldn't qualify as Companions because they need some manual work by the user who has to modify his ~/.thuban/thubanstart.py module. To install a companion it should be enough to put it into a directory somewhere so that Thuban picks it up automatically on startup. Some other names some of which came up here in the office and some of which might be more appropriate as directory names or for the extension mechanism and not for the actual extensions: Booster Amplifier Corona (because Thuban is a star) Spice (because another star in the constellation Draco is Arrakis :) and because Spices let you adapt Thuban to your taste) OortCloud GravityWell Bernhard -- Intevation GmbH http://intevation.de/ Sketch http://sketch.sourceforge.net/ Thuban http://thuban.intevation.org/ From jan at intevation.de Tue Aug 12 18:16:25 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Tue, 12 Aug 2003 18:16:25 +0200 Subject: [Thuban-list] German version of Thuban available Message-ID: <20030812161625.GA11517@intevation.de> Hi, thanks to Bj?rn Broscheit there is now a german translation for Thuban available from CVS. Now Thuban is available in 6 languages! Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Mon Aug 18 11:48:14 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Mon, 18 Aug 2003 11:48:14 +0200 Subject: [Thuban-list] Thuban landed in Debian sid Message-ID: <20030818094814.GA1920@intevation.de> Hi, this is to let you know that Thuban now is an official package of Debian. It arrived in sid (unstable) last weekend. Thanks to Silke Reimer for the Debian maintainership of Thuban! Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Tue Aug 19 22:57:00 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Tue, 19 Aug 2003 22:57:00 +0200 Subject: [Thuban-list] term for extensions In-Reply-To: <6qekzrktv3.fsf@salmakis.intevation.de> References: <20030804133727.GA15916@intevation.de> <20030808103111.GA4240@intevation.de> <20030812103508.GA11050@intevation.de> <6qekzrktv3.fsf@salmakis.intevation.de> Message-ID: <20030819205700.GA18688@intevation.de> Hi, a decision on a branding term for the Thuban extensions is apparently not yet to be done. It is certainly a good idea to apply such a term for more formal way to incorporate somthing into Thuban. Namely, this also means that you could have independent install-packages. Meanwhile Extension is still the most suitable name for what is done e.g. via importing something through ~/.thuban/thubanstart.py. We'll rename the directory extensions to libraries which is more suiting anyway and create a new directory Extensions to place any sort of extensions for the time being. I've already written extensions to import GNS data and a rudimentary import of ArcView APR files :-) On Tue, Aug 12, 2003 at 01:17:36PM +0200, Bernhard Herzog wrote: > Well, what do you mean precisely when you talk about a "Thuban > Companion"? For instance, a Zope product is a very specific thing and > there are ways to extend Zope without using products. So how does this > compare to a "Thuban Companion"? > > I think that we have look at this from a few different angles: > > - What do you call an extension when you talk about the general concept > of extending Thuban in a manual? > > - What do you call them in the user interface? > > - What do you call specific variants of extensions? > > Different kinds of extensions could be > - New but perhaps simple commands in the menu > - New interactive tools > - Support for new file formats > - Support for new database backends > > - What do you call the directory where you put those extensions that > come with Thuban (the directory name was the main objection to using > the term "extension") > > - What do we call an extension mechanism in the Thuban code? > > It seems to me that in the (introductory) documentation and user > interface it's best to use terms that new users will understand more or > less without further explanations. Most users have heard about > extensions, plug-ins or add-ons, for instance. > > In the code it's a different matter. The developers of the "twisted" > library for instance like to use unusual names (e.g. "jelly" for object > serialization) not only because it adds some fun, but also because often > the "normal" terms are already used for very similar but subtly > different things by other projects. > > I'm not sure how well that argument would apply to Thuban, but at least > terms like add-on or plug-in are quite heavily used for specific but > always somewhat different ways to extend programs. > > I think "extension" is pretty generic for something that extends a > program so I'd say we should use that as a collective noun for anything > that extends Thuban. The only downside is that there's already a > directory called "extension" in the Thuban sources which contains Python > extension modules. On the plus-side that there's also a directory called > simple_extensions in the Examples directory. > > "Companion" should then only be used for something more specific that is > directly supported by some Thuban infrastructure. The modules in > Examples/simple_extensions/ wouldn't qualify as Companions because they > need some manual work by the user who has to modify his > ~/.thuban/thubanstart.py module. To install a companion it should be > enough to put it into a directory somewhere so that Thuban picks it up > automatically on startup. > > > Some other names some of which came up here in the office and some of > which might be more appropriate as directory names or for the extension > mechanism and not for the actual extensions: > > Booster > Amplifier > Corona (because Thuban is a star) > Spice (because another star in the constellation Draco is Arrakis :) and > because Spices let you adapt Thuban to your taste) > OortCloud > GravityWell -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From bernhard at intevation.de Wed Aug 20 01:31:39 2003 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 20 Aug 2003 01:31:39 +0200 Subject: [Thuban-list] Thuban landed in Debian sid In-Reply-To: <20030818094814.GA1920@intevation.de> References: <20030818094814.GA1920@intevation.de> Message-ID: <20030819233139.GA19936@intevation.de> On Mon, Aug 18, 2003 at 11:48:14AM +0200, Jan-Oliver Wagner wrote: > this is to let you know that Thuban now is > an official package of Debian. > It arrived in sid (unstable) last weekend. To get an overview about thuban's state in Debian, the following page is quite useful: http://packages.qa.debian.org/t/thuban.html That thuban is packaged now has also made the list of new or noteworthy packages in the current Debian Weekly News edition: http://www.debian.de/News/weekly/2003/33/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://www.intevation.de/pipermail/thuban-list/attachments/20030820/feb8c5ae/attachment.bin From jonathan at jpcoles.com Thu Aug 21 07:21:24 2003 From: jonathan at jpcoles.com (Jonathan Coles) Date: Thu, 21 Aug 2003 05:21:24 -0000 Subject: [Thuban-list] Re: adding layers In-Reply-To: <20030820201532.GA31487@intevation.de> References: <200308201715.h7KHFwT2004102@www38.web2010.com> <20030820201532.GA31487@intevation.de> Message-ID: <1061443150.21835.3.camel@reisen> On Wed, 2003-08-20 at 16:15, Jan-Oliver Wagner wrote: > On Wed, Aug 20, 2003 at 01:15:58PM -0400, Fidel Serrano wrote: > > i am using thuban as viewer for a proyect in a research center here in mexico, and i have a comment: > > > > when adding layers to a sesion, the open file dialog starts allways in the same folder (my documents for example), it is posible, modifing the style of the file dialog to make it remember the folder from where you got the previus layer archive... > > thanks for the feedback. > You are also welcome to send such input to the mailing list to ensure > you reach all the interested developers and users. > > Yes, I noticed this behaviour as annoying as well. > I will look into this to see whether we get it into the 0.9 release > (though it is being finalized these days). > This may be as easy as setting the wxCHANGE_DIR flag in the constructor of wxFileDialog. see here for more details: http://www.wxwindows.org/manuals/2.4.1/wx140.htm#wxfiledialogconstr --jonathan -- ========================================================================= Jonathan Coles http://www.jpcoles.com jonathan at jpcoles.com GnuPG Key: http://www.jpcoles.com/gpg_pub_key.asc ========================================================================= -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://www.intevation.de/pipermail/thuban-list/attachments/20030821/4956663b/attachment.bin From bh at intevation.de Thu Aug 21 12:24:20 2003 From: bh at intevation.de (Bernhard Herzog) Date: Thu, 21 Aug 2003 12:24:20 +0200 Subject: [Thuban-list] Re: adding layers In-Reply-To: <1061443150.21835.3.camel@reisen> (Jonathan Coles's message of "21 Aug 2003 01:19:10 -0400") References: <200308201715.h7KHFwT2004102@www38.web2010.com> <20030820201532.GA31487@intevation.de> <1061443150.21835.3.camel@reisen> Message-ID: <6q7k57wbor.fsf@salmakis.intevation.de> Jonathan Coles writes: > On Wed, 2003-08-20 at 16:15, Jan-Oliver Wagner wrote: >> On Wed, Aug 20, 2003 at 01:15:58PM -0400, Fidel Serrano wrote: >> > when adding layers to a sesion, the open file dialog starts allways >> > in the same folder (my documents for example), it is posible, >> > modifing the style of the file dialog to make it remember the >> > folder from where you got the previus layer archive... [...] >> I will look into this to see whether we get it into the 0.9 release >> (though it is being finalized these days). I for one probably won't have time. > This may be as easy as setting the wxCHANGE_DIR flag in the constructor > of wxFileDialog. IMO that's the wrong approach. An application should never change the current working directory because the interpretation of relative filenames changes which can lead to all kinds of subtle bugs. Thuban makes sure in several places that it does have absolute filenames but there may be places where it doesn't do that. A better way is to simply remember the directory of the last file opened and pass that as the default directory to the dialog. Then you could also remember different directories for different purposes, e.g. one for .thuban files, one for shapefiles, one for projection files, etc. Bernhard -- Intevation GmbH http://intevation.de/ Sketch http://sketch.sourceforge.net/ Thuban http://thuban.intevation.org/ From jan at intevation.de Thu Aug 21 12:46:11 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Thu, 21 Aug 2003 12:46:11 +0200 Subject: [Thuban-list] Re: adding layers In-Reply-To: <6q7k57wbor.fsf@salmakis.intevation.de> References: <200308201715.h7KHFwT2004102@www38.web2010.com> <20030820201532.GA31487@intevation.de> <1061443150.21835.3.camel@reisen> <6q7k57wbor.fsf@salmakis.intevation.de> Message-ID: <20030821104611.GB11522@intevation.de> On Thu, Aug 21, 2003 at 12:24:20PM +0200, Bernhard Herzog wrote: > Jonathan Coles writes: > > This may be as easy as setting the wxCHANGE_DIR flag in the constructor > > of wxFileDialog. > > IMO that's the wrong approach. An application should never change the > current working directory because the interpretation of relative > filenames changes which can lead to all kinds of subtle bugs. Thuban > makes sure in several places that it does have absolute filenames but > there may be places where it doesn't do that. > > A better way is to simply remember the directory of the last file opened > and pass that as the default directory to the dialog. Then you could > also remember different directories for different purposes, e.g. one for > .thuban files, one for shapefiles, one for projection files, etc. I agree with this approach. Furthermore, the Open File dialog to load shapefile could be changed to allow multiple selection of files (flag wxMULTIPLE). I think, this would immediately cure most of the agony cases :-) If you think, this is a good idea, I will do the changes. Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Thu Aug 21 13:58:12 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Thu, 21 Aug 2003 13:58:12 +0200 Subject: [Thuban-list] Re: adding layers In-Reply-To: <20030821104611.GB11522@intevation.de> References: <200308201715.h7KHFwT2004102@www38.web2010.com> <20030820201532.GA31487@intevation.de> <1061443150.21835.3.camel@reisen> <6q7k57wbor.fsf@salmakis.intevation.de> <20030821104611.GB11522@intevation.de> Message-ID: <20030821115812.GB11622@intevation.de> On Thu, Aug 21, 2003 at 12:46:11PM +0200, Jan-Oliver Wagner wrote: > Furthermore, the Open File dialog to load shapefile could be changed > to allow multiple selection of files (flag wxMULTIPLE). > I think, this would immediately cure most of the agony cases :-) it is in CVS now. Now you can do multi-selection for loading shapefile using the shift-key. Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From frank.koormann at intevation.de Thu Aug 28 09:08:37 2003 From: frank.koormann at intevation.de (Frank Koormann) Date: Thu, 28 Aug 2003 09:08:37 +0200 Subject: [Thuban-list] (forw) Re: [postgis-users] Re: What aplication may i buy to edit postgisdata. Message-ID: <20030828070837.GA30649@intevation.de> For the archives. Paul Ramsey comments on the thoughts of implementing live-editing on PostGIS data into JUMP. These are also relevant for Thuban: With the comming 0.9 release Thuban will have capabilities to read from PostGIS, and editing is always in mind. Frank -- Frank Koormann Professional Service around Free Software (http://intevation.net/) FreeGIS Project (http://freegis.org/) -------------- next part -------------- An embedded message was scrubbed... From: Paul Ramsey Subject: Re: [postgis-users] Re: What aplication may i buy to edit postgisdata. Date: Tue, 26 Aug 2003 18:22:40 -0700 Size: 6828 Url: http://www.intevation.de/pipermail/thuban-list/attachments/20030828/1c519299/attachment.txt