From jonathan at intevation.de Mon Feb 10 16:28:56 2003 From: jonathan at intevation.de (Jonathan Coles) Date: 10 Feb 2003 16:28:56 +0100 Subject: [Thuban-list] cvs putback Message-ID: <1044890936.32131.1.camel@reisen> Just putback the latest classification changes. Updates to the dialog box, load and save routines, and internal data representation. See the ChangeLog for more details. --jonathan -- Jonathan Coles Intevation GmbH http://www.intevation.net From jan at intevation.de Mon Feb 10 16:45:39 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Mon, 10 Feb 2003 16:45:39 +0100 Subject: [Thuban-list] cvs putback In-Reply-To: <1044890936.32131.1.camel@reisen> References: <1044890936.32131.1.camel@reisen> Message-ID: <20030210154539.GA23705@intevation.de> On Mon, Feb 10, 2003 at 04:28:56PM +0100, Jonathan Coles wrote: > Just putback the latest classification changes. Updates to the dialog > box, load and save routines, and internal data representation. See the > ChangeLog for more details. I get an exception when trying to load the iceland sample for classification: | Warning: .SESSION_CHANGED: | () | Traceback (most recent call last): | File "./Thuban/Lib/connector.py", line 89, in Issue | apply(func, args + fargs) | File "/powerhome/jan/project/thuban/Thuban/UI/tree.py", line 162, in | session_changed | self.update_tree() | File "/powerhome/jan/project/thuban/Thuban/UI/tree.py", line 93, in | update_tree | self.add_items(root, info[1]) | File "/powerhome/jan/project/thuban/Thuban/UI/tree.py", line 119, in | add_items self.add_items(treeitem, info[1]) | File "/powerhome/jan/project/thuban/Thuban/UI/tree.py", line 119, in | add_items self.add_items(treeitem, info[1]) | File "/powerhome/jan/project/thuban/Thuban/UI/tree.py", line 116, in | add_items info = item.TreeInfo() | File "/powerhome/jan/project/thuban/Thuban/Model/classification.py", | line 185, in TreeInfo | items.append((_("'DEFAULT'"), build_item(self.DefaultData))) | File "/powerhome/jan/project/thuban/Thuban/Model/classification.py", | line 178, in build_item | i.append((_("Stroke: %s") % color_string(v), v)) | NameError: global name 'color_string' is not defined -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jonathan at intevation.de Wed Feb 19 17:55:42 2003 From: jonathan at intevation.de (Jonathan Coles) Date: 19 Feb 2003 17:55:42 +0100 Subject: [Thuban-list] cvs update Message-ID: <1045673742.1133.2309.camel@reisen> Just updated the cvs repository. Changes are to the classification dialog. You should now be able to view the classifications and change some parts of them: double-click on the sample visual and type numbers/ranges for the value. --jonathan -- Jonathan Coles Intevation GmbH http://www.intevation.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://www.intevation.de/pipermail/thuban-list/attachments/20030219/fef731d1/attachment.bin From jonathan at intevation.de Wed Feb 26 18:37:45 2003 From: jonathan at intevation.de (Jonathan Coles) Date: 26 Feb 2003 18:37:45 +0100 Subject: [Thuban-list] TODO List Message-ID: <1046281065.29697.142.camel@reisen> Current functionality: ====================== The user can add/view classification groups and modify the visual properties (stroke color, width, fill color) for single values and ranges as well as change the values and ranges. There is no way to generate these properties automatically. This information can be saved and loaded from a file. The following things concerning classification are needed before the next release of Thuban: ==================================================================== Dialog Clean Up --------------- The classification dialog doesn't look very nice. It was put together to test some of the classes and some things are a bit rough. Generating Ranges ----------------- The user can add classification groups one at a time, but we need to be able to automatically generate groups based on the kind of data that a table field represents. If it is a series of floats then groups of ranges are appropriate, but with strings singleton values are needed. Generating the visual properties over many groups needs to be discussed. I was thinking there could be predefined types such as False-Color which could range from red to green, or the user could select a start and end color. The code would also have to analyse the field values to determine how many different values exist. In the case of strings this means building a list of unique entries. In the case of floats it could mean determining min and max values and then subdividing that range into equal (perhaps) parts. The user should be allowed to specify this. All this functionality will exist only in the classification dialog. Once the classification groups are built Thuban uses the classification class to render the map as normal. If things go to plan (ha!) I should be spending most of next week working on this part of things. Tests ----- Many of the classes have changed recently due to design modifications and the tests don't reflect these changes. In some cases the tests don't even exist. General Code Inspection ----------------------- I need to review some parts of the code and clean them up a bit. A few places here and there could be written better (no specifics, just general house keeping). --jonathan -- Jonathan Coles Intevation GmbH http://www.intevation.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://www.intevation.de/pipermail/thuban-list/attachments/20030226/2316dff8/attachment.bin From jan at intevation.de Wed Feb 26 20:05:54 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Wed, 26 Feb 2003 20:05:54 +0100 Subject: [Thuban-list] Python 2.2 and wxWindows 2.4 Message-ID: <20030226190554.GA25985@intevation.de> Hi, this week we (Bernhard Herzog, Bernhard Reiter, Jonathan Coles, Frank Koormann and myself) had a discussion on the further development we want to perform until June. One important decision, however, is which version of Python and wxWindows Thuban should be compatible for mid-term future (say about 2-3 years). We came to the conclusion that this should be Python 2.2 and wxWindows(wxPython) 2.4. Though both are not yet the standard on many GNU/Linux distribution, we expect them to be within about a year. The forthcoming release 0.2.0 will already depend on this (at least it is only tested against Python 2.2 and wxWindows 2.4 from now on). All the best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Wed Feb 26 20:09:05 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Wed, 26 Feb 2003 20:09:05 +0100 Subject: [Thuban-list] PostGIS interface for Thuban? Message-ID: <20030226190905.GB25985@intevation.de> Hi, we are know planning a PostGIS interface for Thuban (work to be started mid of March). If anyone already is working on this or has concret plans to do so, please let us know. Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jan at intevation.de Thu Feb 27 11:32:34 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Thu, 27 Feb 2003 11:32:34 +0100 Subject: [Thuban-list] issue tracker Message-ID: <20030227103234.GA691@intevation.de> Hi, I just added jonathan as a manipulator for the Thuban request tracker. So, now you can asign bugs directly to him ;-) Also, I configured the thuban bug tracker to be a bit more verbose. Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ From jonathan at intevation.de Thu Feb 27 17:07:07 2003 From: jonathan at intevation.de (Jonathan Coles) Date: 27 Feb 2003 17:07:07 +0100 Subject: [Thuban-list] cvs update Message-ID: <1046362027.4827.6.camel@reisen> updated the repository with code to edit the classification data. --jonathan -- Jonathan Coles Intevation GmbH http://www.intevation.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://www.intevation.de/pipermail/thuban-list/attachments/20030227/a3f9ce97/attachment.bin From jan at intevation.de Thu Feb 27 23:30:55 2003 From: jan at intevation.de (Jan-Oliver Wagner) Date: Thu, 27 Feb 2003 23:30:55 +0100 Subject: [Thuban-list] Roadmap towards release 0.2.0. Was: TODO List In-Reply-To: <1046281065.29697.142.camel@reisen> References: <1046281065.29697.142.camel@reisen> Message-ID: <20030227223055.GB11225@intevation.de> Hi, this sbasically discusses tge roadmap for release 0.2.0. On Wed, Feb 26, 2003 at 06:37:45PM +0100, Jonathan Coles wrote: > The following things concerning classification are needed before the > next release of Thuban: > ==================================================================== > > Dialog Clean Up > --------------- > The classification dialog doesn't look very nice. It was put together to > test some of the classes and some things are a bit rough. Some items that just came to my mind: - replace term 'visual' by 'symbol'. - add a 'Remove' button to get rid one or many marked classes - Make the frame a dialog window. - add hot-keys to the buttons - make the widgets resize with the window size > Generating Ranges > ----------------- > The user can add classification groups one at a time, but we need to be > able to automatically generate groups based on the kind of data that a > table field represents. If it is a series of floats then groups of > ranges are appropriate, but with strings singleton values are needed. > > Generating the visual properties over many groups needs to be discussed. > I was thinking there could be predefined types such as False-Color which > could range from red to green, or the user could select a start and end > color. > > The code would also have to analyse the field values to determine how > many different values exist. In the case of strings this means building > a list of unique entries. In the case of floats it could mean > determining min and max values and then subdividing that range into > equal (perhaps) parts. The user should be allowed to specify this. > > All this functionality will exist only in the classification dialog. > Once the classification groups are built Thuban uses the classification > class to render the map as normal. > > If things go to plan (ha!) I should be spending most of next week > working on this part of things. I propose to skip the range generation for release 0.2.0. You can make the button ivisible for the release and afterwards start implementation of this quite sophisticated feature. > Tests > ----- > Many of the classes have changed recently due to design modifications > and the tests don't reflect these changes. In some cases the tests don't > even exist. yeah, those need to be fixed and some missing to be added for 0.2.0. > General Code Inspection > ----------------------- > I need to review some parts of the code and clean them up a bit. A few > places here and there could be written better (no specifics, just > general house keeping). good idea for 0.2.0. Finally, we should remove the critical bugs listed in the thuban bug tracker - of course :-) -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/