Ticket #450 (closed task: fixed)

Opened 5 months ago

Last modified 6 days ago

Make ExportWizard a gxp component

Reported by: ahocevar Owned by: ahocevar
Priority: major Milestone: 1.0 Beta
Component: JavaScript Components Version:
Keywords: gxp Cc:
Total Hours: 5.5 Blocked By:
Sensitive: no Estimated Hours: 2
Blocking:

Description


Change History

Changed 5 months ago by sbenthall

  • milestone set to 0.1.5 GeoNode

Changed 3 weeks ago by sbenthall

  • owner changed from dwinslow to ahocevar
  • status changed from new to assigned

Changed 7 days ago by sbenthall

  • milestone changed from 1.0 Release to 1.0 Beta

Changed 6 days ago by ahocevar

  • owner changed from ahocevar to sbenthall

Seb, are you sure this is still valid? The OpenGeo Suite's GeoExplorer does not have an ExportWizard any more. Instead, it has a GeoExplorer.Composer, which extends GeoExplorer, adding functionality like saving and exporting a map.

So instead of making ExportWizard a gxp component, I would propose to restructure our GeoExplorer to have the same class hierarchy as the OpenGeo Suite's one. This will make it easier in the future to move GeoExplorer to gxp, enlarging the common code base of GeoNode and the OpenGeo suite.

Please let me know how to proceed, and if the milestone for this is still 1.0 Beta.

Changed 6 days ago by ahocevar

  • owner changed from sbenthall to ahocevar
  • status changed from assigned to accepted

Seb, nevermind. I see now that the Composer and making the ExportWizard an Ext component are no contradiction. On it.

Changed 6 days ago by ahocevar

s/Ext/gxp/

Changed 6 days ago by ahocevar

  • status changed from accepted to closed
  • resolution set to fixed

http://bit.ly/a7tS4e, 4 hours

Changed 6 days ago by ahocevar

http://bit.ly/bC6d2X, 0.5 hours

Note: See TracTickets for help on using tickets.