{5} Assigned, Active Tickets by Owner (Full Description) (11 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

aaronr (8 matches)

Ticket Summary Component Milestone Type Created
Description
#237 Add checks in creating new XML elements for "Required" fields AZ-SMART AZ-SMART Phase 2+ enhancement 06/08/08

In both the creation of database configurations and new script configs into the XML via the GUI we need to add logic to check that users have entered in all required fields into the forms. Both of these cases employ a template definition for parameters with a choices="Required|Optional" attribute that is currently not checked. We need to only allow the adding of the new XML if the values of required fields are present.

#84 design 'plug-in' or 'add-on' framework for gui AZ-SMART task 10/23/07

This idea stems from a discussion Paul and I had regarding QGIS being currently embedded in the GUI. I suggested a switch somewhere for running the GUI with or without QGIS support to help aleviate problems with QGIS builds and versions. Paul suggested that this idea is applicable to any add-on functionality that we or users may want to add in the future. Is there a way to create a plug-in type framework to add in new GUI functionality, possibly including new treeviews, tabs, menus and context menus?

#103 Add the ability to edit scripts in the data_manager via QScintilla Opus/UrbanSim GUI task 12/28/07

Need to add the ability to edit python scripts indicated in the data_manager tab via a right click menu option that loads the base script into the QScintilla editor.

#154 Hide command window and redirect stdout to log tab AZ-SMART AZ-SMART Phase 2+ task 02/06/08

When AZ-SMART is started, hide the command window but still show stdout information in the log tab.

#185 Add mainwindow/tabs/toolbox manager classes Opus/UrbanSim GUI GUI enhancements task 03/31/08

We need generic classes to interact with the main parts of the GUI. Right now it is difficult to navigate around and get references to the different GUI objects. For instance, we should just be able to get to the mainwindow from anywhere in the GUI code. We should also be able to do things like add a tab easily by calling an addTab method on a TabManager? class, and so on. This should eliminate most of the self.parent.parent.parent widget reference stuff that is hanging around at the moment.

#227 Generalize dynamic form creation AZ-SMART AZ-SMART Phase 2+ task 06/05/08

The tree structure display should be converted to dynamically generated pop up forms following the example in Database Server Connections area.

To do this, we will add a display_type attribute to nodes to indicate whether to display as a tree, form, or tab within a form. For nodes identified to be displayed as a form, children of this node will be either a node to organize the display under a tab, or items to be displayed directly on the form (as in the Add Database Server Connection form).

For initial development and testing, create a mockup XML branch in a project.

#241 add ability to run a tool_file without configuring it AZ-SMART AZ-SMART Phase 2+ task 06/12/08
  • Add right-click option to tools in the tool library for 'Execute Tool'
  • This should give the user a popup dialog populated with the parameters they need to fill out to run the tool
  • it should have 'go' or 'execute' and 'cancel' buttons
  • it would be nice to somehow give a status as the tool runs

As a further enhancement to the Opus Data section and related to this ticket:

  • right-click year folder and get 'Export Database >' with at least two options now: SQL and ESRI
  • the user receives a pop up dialog with the tool parameters partially filled out based on what they just clicked
  • repeat this for dataset folders with 'Export Dataset >' as the option
#243 create XML expression library AZ-SMART AZ-SMART Phase 2+ task 06/16/08

Create an editable table containing the following fields: 'name', 'definition' (attribute name, expression, or python module), 'dataset', 'use' (model variable, indicator, or both), 'source' (primary attribute, expression, or python class).

Should be stored in the <general> section of the XML project.

jlivni (1 match)

Ticket Summary Component Milestone Type Created
Description
#59 Generate view with Python in PostGIS Opus/UrbanSim GUI task 08/27/07

DB connnection (sqlalchemy) geometry table name table to join to view column(s) for joins name of view to create column for geometry where argument (optional) (create index on geom column)

travis (2 matches)

Ticket Summary Component Milestone Type Created
Description
#67 replace localhost dependency in unit tests Opus/UrbanSim (general) task 09/20/07

Many of the unit tests that involve database operations are hardcoded to access a db server on localhost. This should be replaced by looking first at the HOSTNAMEFORTESTS env variable before defaulting to localhost.

#83 get rid of jdbc url in parent database specification in scenario db chain package opus_core task 10/19/07

The jdbc url that is used to link databases together in the chain is unnecessary and nonsensical, and currently hardcoded to look for a mysql url. We really just need to have a database name. First step would be to support both a url or a simple db name.

Note: See TracReports for help on using and creating reports.