[Qgis-developer] porjectRead() and newProject() signals

2010-10-18 Thread Alexander Bruy
Hi

Some plugins stores their settings in QGIS project. And when user open
previously saved project read setting from it, when created new project -
default settings used and plugin GUI is resetted. For example in Copyright
label plugin

void QgsCopyrightLabelPlugin::initGui()
{
  ...
  //this resets this plugin up if a project is loaded
  connect( qGisInterface-mainWindow(), SIGNAL( projectRead() ), this,
SLOT( projectRead() ) );
  ...
  //initialise default values in the gui
  projectRead();
}

But projectRead() and newProject() are not documented, some info available
only in qgisapp.h. Is it possible to add this signals to the QGisInterface
and add some documentaion?

-- 
Alexander Bruy
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Release plans for QGIS 1.6

2010-10-18 Thread Giovanni Manghi
New Zealand Taumatawhakatangihangakoauauotamateaturipuk
akapikimaungahoronukupokaiwhenuakitanatahu was also not bad... ;) 

(TRANSLATION: “The brow of the hill where Tamatea, with the bony knees,
slid and climbed mountains. The great traveler sat and played on the
flute to his beloved.”) 




On Mon, 2010-10-18 at 07:44 +0200, Tim Sutton wrote:
 Hi
 
 Ok I went with Giovanni's suggestion of Capiopo for this release - see
 the new splash screen in trunk.
 
 Regards
 
 Tim
 
 On Sun, Oct 17, 2010 at 10:42 AM, Benoit de Cabissole
 ben...@exigesa.com wrote:
 
 
  On 17/10/2010 10:37, Tim Sutton wrote:
  Hi
 
  On Sun, Oct 17, 2010 at 10:16 AM, Vincent Leong loldog2...@gmail.com 
  wrote:
  How about hill names as release names?
  Hills is better than mountains because mountains is always too well
  known and probably been used by others.
  Moreover, their shape can be used to differentiate releases.
 
  One example: Bohol
 
  Any nice pics to go with your suggestion? I quite like the idea since
  philosophically each release is another hill we have climbed and put
  behind us :-)
 
  Or characteristics contour lines of the hill (we are dealing with GIS
  after all)?
 
  My 2 cents
  Benoit
 
  Lets keep the discussion on-list ok?
 
  Regards
 
  Tim
 
  On 10/17/10, Tim Sutton li...@linfiniti.com wrote:
  Hi
 
 
 
  On Sun, Oct 17, 2010 at 1:07 AM, Alex Mandel tech_...@wildintellect.com
  wrote:
  I agree that real place names is a better idea. I could see lots of
  Mythical/Fictitious names actually being claimed by people. I will also
  point out that the Mozilla Foundation uses National Parks/Reserves in
  the code naming of pre-release firefox branches and suggest that we
  could do something with a greater cause as our release names:
  Endangered Species, World Heritage Sites, Rivers, Mountain Peaks, etc..
  (suggest your idea)
 
  Sorry in retrospect my original email was probably unclear. It was my
  intention that we use *real* (hence photographable) place names, but
  obscure ones that a) have some geographical interest and b) are
  unlikely to ever have been used by someone as a trademark. Having a
  theme to the place names would be fine (making them really obscure and
  interesting was kind of my idea for a theme, but another theme would
  be fine too).
 
  Using well known places e.g. Moscow as Maxim suggests will lead to
  similar conflicts as using planetary moons.
 
  Regards
 
  Tim
 
 
  We could also de-emphasize the release name and use it amongst the
  developer group to keep track of what's being worked on, ie the trunk
  will have a name leading up to it's release and then switch names.
 
  I also agree, to just avoid the issue as it's not worth our effort to
  fight.
 
  Thanks,
  Alex
 
  On 10/16/2010 03:06 PM, Maxim Dubinin wrote:
  How about making release names geographic. QGIS 1.6 Moscow sounds
  good and easily memorizable.
 
  Maxim
 
  Вы писали 16 октября 2010 г., 14:07:10:
 
  TS Hi
 
  TS On Sat, Oct 16, 2010 at 8:09 PM, Jürgen E. j...@norbit.de wrote:
  Hi Tim,
 
  On Sat, 16. Oct 2010 at 01:42:54 +0200, Tim Sutton wrote:
  We (the PSC) recently received a threat of legal action against our
  use of the word 'Tethys' in the naming of the 1.5 release of QGIS.
  It seems that the word Tethys is trademarked by a company in one
  country.
  Although we feel their case is weak, we do not have the time, money 
  or
  inclination to engage in a legal battle over this.
  Does OSGeo have a position on this?  I thought the OSGeo umbrella was
  also
  covering legal support.
 
  Just curious - that would probably be a waste of time of resources
  anyway.
 
  TS Ok Frank covered that. And yeah we should pick our battles...
 
  This has a few implications:
  - The PSC has agreed to stop using planetary moons as the names for
  our releases, and embark on a new theme of using extremely obscure
  place names (e.g. the mythical Tweebuffelsmeteenskootgeskietfontein 
  in
  South Africa).
  Do we need codenames at all?   Any name - obscure or not - could be a
  trademark.
 
 
  TS *sniff* lose the release names? That would be no funshould we 
  let
  TS big corporations take away our fun? :-P
 
  TS But yeah theoretically we don't need them, though personally I'd 
  like
  TS to continue with them...
 
  TS Regards
 
  TS Tim
 
  Jürgen
 
  --
  Jürgen E. Fischer norBIT GmbH   Tel.
  +49-4931-918175-20
  Dipl.-Inf. (FH)   Rheinstraße 13Fax.
  +49-4931-918175-50
  Software Engineer D-26506 Norden
  http://www.norbit.de
 
  ___
  Qgis-developer mailing list
  Qgis-developer@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/qgis-developer
 
 
 
  --
  Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
  ==
  Please do not email me off-list with technical
  support questions. Using the lists will gain
  more exposure for your 

[Qgis-developer] Qgis 1.5, python 2.6 and modules error with 32 or 64 bit architecture

2010-10-18 Thread Luca Mandolesi
Hi,
under mac os x I cannot use somes plugins with qgis 1.5 because I receive
this error:

...
ImportError:
/Applications/QGIS_1.5/Qgis.app/Contents/MacOS/../Resources/python/pygraphviz/_graphviz.so:
no appropriate 64-bit architecture (see man python for running in 32-bit
mode)

ImportError:
/Applications/QGIS_1.5/Qgis.app/Contents/MacOS/../Resources/python/matplotlib/_path.so:
no appropriate 64-bit architecture (see man python for running in 32-bit
mode)

I'm under mac os x snow leopard with python 2.6.

How can I solve this problem?

Thank's a lot

luca
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


[Qgis-developer] Interlis support of OGR inside QGIS (make it default? modify make files? Windows but not only...)

2010-10-18 Thread Stefan Keller
Hi,

I'm trying to import/export INTERLIS geodata inside QGIS under Windows
(XP Professional) - but had no luck so far.

There are two QGIS plugins around, OGR Converter (C++) and
Interlis (Python) which obviously call OGR/GDAL libraries.
OGR Converter doesn't list Interlis format and Interlis plugin
reports The GDAL/OGR library you are using has beend compiled without
Interlis support.
I'm talking about INTERLIS format version 1 and 2 (read/write).

I fear that the default make files for GDAL/OGR do not include
INTERLIS libraries.
I know also that there is a problem - at least under Windows and MacOS
- of ogr/gdal accessing java jar packages (ili2.jar) unless they are
copied in the default library search path - or even in every directory
where programs and data reside.

1.Can anybody involved in delivering the (Windows) binaries and in
committing to the OGR Converter and Interlis plugins have a look
at this problem?

= To me an optimal solution would be, that Interlis support is
included by default in all QGIS deliveries.

2. Is there any workaround? Eventually I can replace the GDAL/OGR .dll
(.so) myself?

Yours, S.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Interlis support of OGR inside QGIS (make it default? modify make files? Windows but not only...)

2010-10-18 Thread Andreas Neumann
Hi Stefan,

You should use Marco Hugentoblers Interlis plugin to load files, which,
like you said uses OGR. It just makes the OGR handling easier and allows
to select only certain topics/tables.

What exactly is the problem? What error message are you getting?

I believe that Interlis should be enabled by default by QGIS 1.5 or QGIS
1.6. It works on my machine for small and medium sized itf's but fails for
big itfs. I haven't tested Interlis 2 so far.

Andreas


On Mon, October 18, 2010 12:14 pm, Stefan Keller wrote:
 Hi,

 I'm trying to import/export INTERLIS geodata inside QGIS under Windows
 (XP Professional) - but had no luck so far.

 There are two QGIS plugins around, OGR Converter (C++) and
 Interlis (Python) which obviously call OGR/GDAL libraries.
 OGR Converter doesn't list Interlis format and Interlis plugin
 reports The GDAL/OGR library you are using has beend compiled without
 Interlis support.
 I'm talking about INTERLIS format version 1 and 2 (read/write).

 I fear that the default make files for GDAL/OGR do not include
 INTERLIS libraries.
 I know also that there is a problem - at least under Windows and MacOS
 - of ogr/gdal accessing java jar packages (ili2.jar) unless they are
 copied in the default library search path - or even in every directory
 where programs and data reside.

 1.Can anybody involved in delivering the (Windows) binaries and in
 committing to the OGR Converter and Interlis plugins have a look
 at this problem?

 = To me an optimal solution would be, that Interlis support is
 included by default in all QGIS deliveries.

 2. Is there any workaround? Eventually I can replace the GDAL/OGR .dll
 (.so) myself?

 Yours, S.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



-- 
Andreas Neumann
http://www.carto.net/neumann/
http://www.svgopen.org/

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Qgis 1.5, python 2.6 and modules error with 32 or 64 bit architecture

2010-10-18 Thread Luca Mandolesi
On Mon, Oct 18, 2010 at 3:31 PM, William Kyngesburye
wokl...@kyngchaos.comwrote:

 On Oct 18, 2010, at 3:27 AM, Luca Mandolesi wrote:

  Hi,
  under mac os x I cannot use somes plugins with qgis 1.5 because I receive
 this error:
 
  ...
  ImportError:
 /Applications/QGIS_1.5/Qgis.app/Contents/MacOS/../Resources/python/pygraphviz/_graphviz.so:
 no appropriate 64-bit architecture (see man python for running in 32-bit
 mode)
  
  ImportError:
 /Applications/QGIS_1.5/Qgis.app/Contents/MacOS/../Resources/python/matplotlib/_path.so:
 no appropriate 64-bit architecture (see man python for running in 32-bit
 mode)
 
  I'm under mac os x snow leopard with python 2.6.
 
  How can I solve this problem?

 How did you install pygraphviz and matplotlib?  Source? binary?  from
 binary, I'm guessing that only 32bit builds are available.


Hi William, and thanks.
I've installed pygraphviz from source (I found also Qgis don't allow
pygraphviz to find graphviz, and I must to add a simple hack to make to work
inside qgis) and matplotlib from easy_install.


 You could force all of Qgis to run 32bit: Get Info on the application and
 check the box Open in 32bit mode.


I don't understand where find Open in 32bit mode.

Under /Applications/Qgis/ Show Contents - I found Info.plist
I opened it and I add a string:

Executable architectures
and add Intel-64 bit

but nothing change.

I think I need to allow Qgis to allow the 64bit python modules
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Qgis 1.5, python 2.6 and modules error with 32 or 64 bit architecture

2010-10-18 Thread Luca Mandolesi
Sorry William, I'm stupid! I didn't understand I need only to open the file
info of Qgis app!
Now I don't receive the error about 32-bit mode.

Thanks a lot!!!

Luca

On Mon, Oct 18, 2010 at 4:02 PM, Luca Mandolesi mandol...@gmail.com wrote:



 On Mon, Oct 18, 2010 at 3:31 PM, William Kyngesburye 
 wokl...@kyngchaos.com wrote:

 On Oct 18, 2010, at 3:27 AM, Luca Mandolesi wrote:

  Hi,
  under mac os x I cannot use somes plugins with qgis 1.5 because I
 receive this error:
 
  ...
  ImportError:
 /Applications/QGIS_1.5/Qgis.app/Contents/MacOS/../Resources/python/pygraphviz/_graphviz.so:
 no appropriate 64-bit architecture (see man python for running in 32-bit
 mode)
  
  ImportError:
 /Applications/QGIS_1.5/Qgis.app/Contents/MacOS/../Resources/python/matplotlib/_path.so:
 no appropriate 64-bit architecture (see man python for running in 32-bit
 mode)
 
  I'm under mac os x snow leopard with python 2.6.
 
  How can I solve this problem?

 How did you install pygraphviz and matplotlib?  Source? binary?  from
 binary, I'm guessing that only 32bit builds are available.


 Hi William, and thanks.
 I've installed pygraphviz from source (I found also Qgis don't allow
 pygraphviz to find graphviz, and I must to add a simple hack to make to work
 inside qgis) and matplotlib from easy_install.


 You could force all of Qgis to run 32bit: Get Info on the application and
 check the box Open in 32bit mode.


 I don't understand where find Open in 32bit mode.

 Under /Applications/Qgis/ Show Contents - I found Info.plist
 I opened it and I add a string:

 Executable architectures
 and add Intel-64 bit

 but nothing change.

 I think I need to allow Qgis to allow the 64bit python modules






___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Interlis support of OGR inside QGIS (make it default? modify make files? Windows but not only...)

2010-10-18 Thread Stefan Keller
I'm trying to use OGR in whatever plugin under QGIS and Windows XP.

The error reported in a QGIS window is The GDAL/OGR library you are
using has been compiled without Interlis support.

I think you (and Horst too) are using Linux, so it seems to me I'm the
first user of the Interlis plugin :-?

The plugin Interlis (Python) mentioned before is the one from Marco
(via http://karlinapp.ethz.ch/python_plugins/python_plugins.xml)
= Or do you mean another one?

Looking inside settings\.qgis\python\plugins\interlis\interlisplugin.py
there is an obious test:
Interlis support.
def run(self):
fileFilters = QgsProviderRegistry.instance().fileVectorFilters()
if not fileFilters.contains(Interlis,  Qt.CaseInsensitive):
QMessageBox.critical(None, 
 QCoreApplication.translate(InterlisPlugin,No Interlis support available),
 
 QCoreApplication.translate(InterlisPlugin,The GDAL/OGR library you are 
 using has been compiled
   
without Interlis support))

Replacing C:\Programs\OSGeo4W\bin\ogr2ogr.exe did'nt help neither
which is weird, because calling the same ogr2ogr.exe out of a Windows
shell reports
 -f Interlis 1
 -f Interlis 2
as possible values.

Yours, S.


2010/10/18 Andreas Neumann a.neum...@carto.net:
 Hi Stefan,

 You should use Marco Hugentoblers Interlis plugin to load files, which,
 like you said uses OGR. It just makes the OGR handling easier and allows
 to select only certain topics/tables.

 What exactly is the problem? What error message are you getting?

 I believe that Interlis should be enabled by default by QGIS 1.5 or QGIS
 1.6. It works on my machine for small and medium sized itf's but fails for
 big itfs. I haven't tested Interlis 2 so far.

 Andreas


 On Mon, October 18, 2010 12:14 pm, Stefan Keller wrote:
 Hi,

 I'm trying to import/export INTERLIS geodata inside QGIS under Windows
 (XP Professional) - but had no luck so far.

 There are two QGIS plugins around, OGR Converter (C++) and
 Interlis (Python) which obviously call OGR/GDAL libraries.
 OGR Converter doesn't list Interlis format and Interlis plugin
 reports The GDAL/OGR library you are using has beend compiled without
 Interlis support.
 I'm talking about INTERLIS format version 1 and 2 (read/write).

 I fear that the default make files for GDAL/OGR do not include
 INTERLIS libraries.
 I know also that there is a problem - at least under Windows and MacOS
 - of ogr/gdal accessing java jar packages (ili2.jar) unless they are
 copied in the default library search path - or even in every directory
 where programs and data reside.

 1.Can anybody involved in delivering the (Windows) binaries and in
 committing to the OGR Converter and Interlis plugins have a look
 at this problem?

 = To me an optimal solution would be, that Interlis support is
 included by default in all QGIS deliveries.

 2. Is there any workaround? Eventually I can replace the GDAL/OGR .dll
 (.so) myself?

 Yours, S.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



 --
 Andreas Neumann
 http://www.carto.net/neumann/
 http://www.svgopen.org/


___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Interlis support of OGR inside QGIS (make it default? modify make files? Windows but not only...)

2010-10-18 Thread Andreas Neumann
Hi Stefan,

I use the plugin on Windows (OSGeo4W) and Linux.

Are you using the OSGeo4W installer or the Windows standalone installer? I
have only experience with the OSGeo4W installer, which I believe comes
with Interlis support out of the box. At least it works on several of our
windows machines. It may be that you manually have to copy the ili2c.jar
fileinto a path reachable by osgeo. You can copy ili2c.jar to
\OSGeo4Wroot\bin (on my machines it is C:\Programme\OSGeo4W\bin). Since
ili2c.jar is based on Java, you also need Java.

Also, with OSGeo4W you have to use at least QGIS 1.5 or trunk (qgis-dev).

I have no experience with the Windows standalone installation. It may be
that the OGR included with that version does not support Interlis.

Hope this helps. The goal should be have Interlis support enabled by
default - I agree.

Andreas


On Mon, October 18, 2010 4:25 pm, Stefan Keller wrote:
 I'm trying to use OGR in whatever plugin under QGIS and Windows XP.

 The error reported in a QGIS window is The GDAL/OGR library you are
 using has been compiled without Interlis support.

 I think you (and Horst too) are using Linux, so it seems to me I'm the
 first user of the Interlis plugin :-?

 The plugin Interlis (Python) mentioned before is the one from Marco
 (via http://karlinapp.ethz.ch/python_plugins/python_plugins.xml)
 = Or do you mean another one?

 Looking inside settings\.qgis\python\plugins\interlis\interlisplugin.py
 there is an obious test:
 Interlis support.
def run(self):
fileFilters = QgsProviderRegistry.instance().fileVectorFilters()
if not fileFilters.contains(Interlis,  Qt.CaseInsensitive):
QMessageBox.critical(None,
 QCoreApplication.translate(InterlisPlugin,No Interlis
 support available),
 
 QCoreApplication.translate(InterlisPlugin,The
 GDAL/OGR library you are
 using has been compiled
  
 without
 Interlis
 support))

 Replacing C:\Programs\OSGeo4W\bin\ogr2ogr.exe did'nt help neither
 which is weird, because calling the same ogr2ogr.exe out of a Windows
 shell reports
  -f Interlis 1
  -f Interlis 2
 as possible values.

 Yours, S.


 2010/10/18 Andreas Neumann a.neum...@carto.net:
 Hi Stefan,

 You should use Marco Hugentoblers Interlis plugin to load files, which,
 like you said uses OGR. It just makes the OGR handling easier and allows
 to select only certain topics/tables.

 What exactly is the problem? What error message are you getting?

 I believe that Interlis should be enabled by default by QGIS 1.5 or QGIS
 1.6. It works on my machine for small and medium sized itf's but fails
 for
 big itfs. I haven't tested Interlis 2 so far.

 Andreas


 On Mon, October 18, 2010 12:14 pm, Stefan Keller wrote:
 Hi,

 I'm trying to import/export INTERLIS geodata inside QGIS under Windows
 (XP Professional) - but had no luck so far.

 There are two QGIS plugins around, OGR Converter (C++) and
 Interlis (Python) which obviously call OGR/GDAL libraries.
 OGR Converter doesn't list Interlis format and Interlis plugin
 reports The GDAL/OGR library you are using has beend compiled without
 Interlis support.
 I'm talking about INTERLIS format version 1 and 2 (read/write).

 I fear that the default make files for GDAL/OGR do not include
 INTERLIS libraries.
 I know also that there is a problem - at least under Windows and MacOS
 - of ogr/gdal accessing java jar packages (ili2.jar) unless they are
 copied in the default library search path - or even in every directory
 where programs and data reside.

 1.Can anybody involved in delivering the (Windows) binaries and in
 committing to the OGR Converter and Interlis plugins have a look
 at this problem?

 = To me an optimal solution would be, that Interlis support is
 included by default in all QGIS deliveries.

 2. Is there any workaround? Eventually I can replace the GDAL/OGR .dll
 (.so) myself?

 Yours, S.
 ___
 Qgis-developer mailing list
 Qgis-developer@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/qgis-developer



 --
 Andreas Neumann
 http://www.carto.net/neumann/
 http://www.svgopen.org/





-- 
Andreas Neumann
http://www.carto.net/neumann/
http://www.svgopen.org/

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Raster algebra C++

2010-10-18 Thread Martin Dobias
Hi Marco

On Thu, Oct 14, 2010 at 5:40 PM, Marco Hugentobler
marco.hugentob...@sourcepole.ch wrote:
 Hi devs,

 A very cool and handy tool is Alexander Bruys raster algebra plugin. It's so
 usefull in environmental modelling that Tim and I thought it would be good to
 have it in our analysis library (where it can be used by 3rd party
 applications too and without the dependency of the numpy library).
 So here is my initial patch that implements a calculator tool as part of the
 analysis library by extending the search string mechanism.

 [...]

 You can try the functionality by applying the following patch:
 http://karlinapp.ethz.ch/101014_qgis_rastercalculator.diff
 The menu to open the calculator is located under 'Layer-Raster calculator'.

Thanks a lot for the patch. I have taken a brief look on it and I have
one suggestion: IMHO it would be better to keep the parser (and
interpreter) for raster algebra and search strings separate. I
understand that it is easier to reuse some of the code from search
strings with raster algebra, but the semantics is very different. And
there are various functions and operators that work only for one of
them, so mixing them together complicates the inner working of the
search string interpreter. Extending the languages (e.g. usage of
raster neighborhood, further string operations) will make the code
even more cluttered.

My vision is that search strings should continue to evolve to support
a reasonable subset of SQL language, while raster algebra language can
evolve to support further raster/matrix operations. Keeping these
different languages separately may bring brighter future for both :-)

Regards
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer