Re: [udig-devel] Move KML Import/Export Capabilities into a separate bun

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle

From: Jody Garnett <jody.garnett@xxxxxxxxx>
Date: Sat, 14 Apr 2012 16:08:56 +1000
Delivered-to: udig-devel@xxxxxxxxxxxxxxxxxxxxxx
List-archive: <http://lists.refractions.net/pipermail/udig-devel>
List-help: <mailto:udig-devel-request@lists.refractions.net?subject=help>
List-subscribe: <http://lists.refractions.net/mailman/listinfo/udig-devel>, <mailto:udig-devel-request@lists.refractions.net?subject=subscribe>
List-unsubscribe: <http://lists.refractions.net/mailman/options/udig-devel>, <mailto:udig-devel-request@lists.refractions.net?subject=unsubscribe>

The general question is : how to structure the bundle names in the
future, properly a simple "addon" would be better than tools, because
if I read tools I expect to do something with it. Right now these are
just wizards ...

eu.udig.addon.kml or better prepared for the future : eu.udig.catalog.kml ?

I would go with eu.udig.catalog.kml - as "import" and "export" wizards are used to take data into and out of the catalog.

Jody

Follow-Ups:
- Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
  - From: andrea antonello

References:
- [udig-devel] Move KML Import/Export Capabilities into a separate bundle
  - From: Frank Gasdorf
- Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
  - From: andrea antonello
- Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
  - From: Frank Gasdorf

Prev by Date: Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
Next by Date: [udig-devel] pom-libs dependency:tree trick
Previous by thread: Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
Next by thread: Re: [udig-devel] Move KML Import/Export Capabilities into a separate bundle
Index(es):
- Date
- Thread

Breadcrumbs