[Qgis-user] mapserverexportplugin: use current loaded project only

[matej at matnet.net]

Hi,

I think that exporting without pointing to qgis project file is logical, so just export the current (saved) project.

My five cents.

BR, Matej Serc

Sent via BlackBerry from Vodafone

-----Original Message-----
From: Richard Duivenvoorde <rdmailings at duif.net>
Date: Sun, 08 Nov 2009 00:36:36 
To: <qgis-user at lists.osgeo.org>
Subject: [Qgis-user] mapserverexportplugin: use current loaded project only

Hi List,
we are busy with the python mapserverexport plugin...

current version asks you to point to a qgs-project-file which will then be
used to make the map file.
Often this project-file is actually the project currently loaded in qgis.
Which made people add functionality to check if the current project is
actually changed after loading...

BUT: isn't it more intuitive to NOT let the user point to a qgs-project
file, but always use the current project for exporting? In this way we can
force people to save current project if not saved yet (because the mapfile
is actually build by using data from a (saved) project file).
Another option would be that the user would not be forced to save the
file, and silently save the file to some temporary place just to build the
mapfile...

I prefer the first option.

Do people see any objections in removing the 'browse to
qgs-file'-functionality in the plugin?

Please comment.

Regards

Richard Duivenvoorde


_______________________________________________
Qgis-user mailing list
Qgis-user at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user