search

simoncaliss / cropplanning

Automatically exported from code.google.com/p/cropplanning
0 stars 0 forks source link

Planting Groups #18

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Plantings should belong to "planting groups" which could be collapsed in
the plan.  Example: a plan might have numerous entries for "tomatoes", each
a different variety or something, but they would all be treated as a single
planting in effect.

Original issue reported on code.google.com by cropplan...@gmail.com on 17 Jan 2008 at 2:58

GoogleCodeExporter commented 8 years ago 
The mechanism to use to implement this is the JXTreeTable from the swingx 
package at
SwingLabs.  We would have to create a new table model: a TreeTableModel to 
handle
some of the TreeTable specific stuff, but it seems like it might not be 
difficult.

Additionally, this might allow us to group plantings arbitrarily.  Eg, in 
addition to
"group by group", we could group by crop, by succession, by week, by location, 
etc. 
It's all just a matter of having the TreeTableModel so come checking of the 
records
to see if what "group" each row belongs to.

Original comment by cropplan...@gmail.com on 4 Mar 2008 at 1:54

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 18 Oct 2008 at 11:44

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 18 Oct 2008 at 11:52

GoogleCodeExporter commented 8 years ago

Original comment by cropplan...@gmail.com on 19 Dec 2008 at 2:29

GoogleCodeExporter commented 8 years ago 
Closing issue.  Feature added for planting lists in post-v0.6 development 
builds.  Not sure how it would/should work for the general table views.  It 
should be fine just for the planting lists.

Original comment by cropplan...@gmail.com on 13 Mar 2013 at 2:33