while working on dynamic geoservers, i noticed (well, already noticed it
a while ago in http://trac.osgeo.org/geonetwork/ticket/983) that we have
two concurrent implems of GeoPublisherPanel :
web/src/main/webapp/scripts/editor/app.GeoPublisherPanel.js
web-client/src/main/resources/apps/js/GeoNetwork/lib/GeoNetwork/widgets/editor/GeoPublisherPanel.js
The first one seems unused... or maybe only with the legacy UI ?
Is that intended ? this is confusing...
The one used in develop branch is web-client/src/main/resources/apps/js/GeoNetwork/lib/GeoNetwork/widgets/editor/GeoPublisherPanel.js
However, your proposal will certainly be integrated in GN 3.0 and this version won’t probably use extjs ui anymore.
I would suggest you to wait a bit to see if the new editor UI is merged into develop, and start your work on this new UI.
You can find it in refactor_editorui branch from now.
while working on dynamic geoservers, i noticed (well, already noticed it
a while ago in http://trac.osgeo.org/geonetwork/ticket/983) that we have
two concurrent implems of GeoPublisherPanel :
web/src/main/webapp/scripts/editor/app.GeoPublisherPanel.js
web-client/src/main/resources/apps/js/GeoNetwork/lib/GeoNetwork/widgets/editor/GeoPublisherPanel.js
The first one seems unused… or maybe only with the legacy UI ?
Is that intended ? this is confusing…
while working on dynamic geoservers, i noticed (well, already noticed it
a while ago in http://trac.osgeo.org/geonetwork/ticket/983) that we have
two concurrent implems of GeoPublisherPanel :
web/src/main/webapp/scripts/editor/app.GeoPublisherPanel.js
web-client/src/main/resources/apps/js/GeoNetwork/lib/GeoNetwork/widgets/editor/GeoPublisherPanel.js
The first one seems unused… or maybe only with the legacy UI ?
Is that intended ? this is confusing…
I don't think you need to up-date the implementation in web module if
you are doing the work on develop branch.
After re-reading that code, i remembered that the extjs code gets the
XML from geoserver-nodes.xml via geoserver.publisher?action=LIST (pruned
from the admin/pwd login stuff), so i might not even need to change
those UI parts in the end.
Maybe i should just keep the XML structure, and only do the geoserver
interaction in the java parts.IE:
- if the current user has a special tag/authority for geoserver access
- fetch the list of workspaces from REST
- create the required workspaces if they're missing
- munge the returned XML to only contain the workspaces the user is
supposed to write to.
Just an idea, as i'm digging into the code..
On Thu, Feb 13, 2014 at 3:27 PM, Landry Breuil <breuil@anonymised.com
<mailto:breuil@anonymised.com>> wrote:
Hi,
while working on dynamic geoservers, i noticed (well, already noticed it
a while ago in http://trac.osgeo.org/geonetwork/ticket/983) that we have
two concurrent implems of GeoPublisherPanel :
web/src/main/webapp/scripts/editor/app.GeoPublisherPanel.js
web-client/src/main/resources/apps/js/GeoNetwork/lib/GeoNetwork/widgets/editor/GeoPublisherPanel.js
The first one seems unused... or maybe only with the legacy UI ?
Is that intended ? this is confusing...
one was used by Classic gui and the other one by ExtJS and they should be relatively similar (which were using different Ext and OL version at some point).
while working on dynamic geoservers, i noticed (well, already noticed it
a while ago in http://trac.osgeo.org/geonetwork/ticket/983) that we have
two concurrent implems of GeoPublisherPanel :
web/src/main/webapp/scripts/editor/app.GeoPublisherPanel.js
web-client/src/main/resources/apps/js/GeoNetwork/lib/GeoNetwork/widgets/editor/GeoPublisherPanel.js
The first one seems unused… or maybe only with the legacy UI ?
Is that intended ? this is confusing…