Matt,
I notice that our examples page references the ol-integration trunk from:
http://communitymapbuilder.org/display/MAP/Examples
This is good.Would it be possible to also reference the last few
releases too?
--
Cameron Shorter
Systems Architect, http://lisasoft.com.au
Tel: +61 (0)2 8570 5050
Anthony Manfredi,
Andrea tells me that you are a Google Summer of Code student who will be
writing a SLD Editor?
This is a very needed piece of functionality by a number of
applications. Of note:
Olivier Terral and others at Geomatys have written a SLD editor in
http://communitymapbuilder.org w
Hi,
On 6/1/07, olivier.terral <[EMAIL PROTECTED]> wrote:
> > - When Mapbuilder loads, there is occasionaly an error: dstdefn has no
> > properties (cscs.js, line 355). I observed that also in an application
> > using EPSG:31295.
> I've seen the same bug in ZoomToAoi tool so maybe it comes from he
Andreas Hocevar a écrit :
>
> - When Mapbuilder loads, there is occasionaly an error: dstdefn has no
> properties (cscs.js, line 355). I observed that also in an application
> using EPSG:31295.
I've seen the same bug in ZoomToAoi tool so maybe it comes from here.
No time to fixed today; I've a loo
Bug already fixed Andres read previous mail
Andreas Hocevar a écrit :
> Hi,
>
> On 6/1/07, Christopher Schmidt <[EMAIL PROTECTED]> wrote:
>> > - The map scalebar works for me in an application with EPSG:31295. So
>> > maybe the wrong scale is only calculated in EPSG:4326? Because the
>> > wrong i
Hi,
On 6/1/07, Christopher Schmidt <[EMAIL PROTECTED]> wrote:
> > - The map scalebar works for me in an application with EPSG:31295. So
> > maybe the wrong scale is only calculated in EPSG:4326? Because the
> > wrong information comes from OpenLayers functions, I suspect that this
> > has to do wi
On Fri, Jun 01, 2007 at 06:05:19PM +0200, Andreas Hocevar wrote:
> Hi,
>
> two observations:
>
> - The map scalebar works for me in an application with EPSG:31295. So
> maybe the wrong scale is only calculated in EPSG:4326? Because the
> wrong information comes from OpenLayers functions, I suspec
Hi,
two observations:
- The map scalebar works for me in an application with EPSG:31295. So
maybe the wrong scale is only calculated in EPSG:4326? Because the
wrong information comes from OpenLayers functions, I suspect that this
has to do with incorrect settings of maxExtent, maxResolutions and
Bug find Gertjan, thanks for debugging.
Units paramter of proj hardcoded in meters
Don't worry for internationalization, it's in progress.
Gertjan van Oosten a écrit :
> As quoted from Gertjan van Oosten <[EMAIL PROTECTED]>:
>
>>> But say me what scale I must find for mapViewer demo?
>>>
hey all
No hardcoding styles in .js unless absolutely necessary please!
The whole point of css is to make it easy to change styles, it's better
to use stylesheets to define certain styles.
On a related note: the whole border thing is a known issue between IE
and FF, one adds the border with to
As quoted from Gertjan van Oosten <[EMAIL PROTECTED]>:
> > But say me what scale I must find for mapViewer demo?
>
> The mapViewer demo:
> http://localhost:8080/mapbuilder/demo/mapViewer/
> actually uses MapScaleBar, but that also shows the wrong scale (it shows
> "2 m" when you just open the UR
I've just added some tests for the Basic demo (Interactive Map Viewer).
Of these tests, the ones for drag_map and zoom_map currently fail under
Microsoft Internet Explorer 6.
The reason for this is that the offset of the map image(s) within the
mainMapPane div is different under IE than under Fire
I suggest we drop the sarissa.js because with IE6 there is a bug when
sarissa is named with 's'.
Gertjan van Oosten a écrit :
> Oliviers commit[*] triggered this: we have two copies of Sarissa in
> lib/util/sarissa/:
> sarissa.js
> Sarissa.js
>
> The only difference is: one has an upper-cas
Oliviers commit[*] triggered this: we have two copies of Sarissa in
lib/util/sarissa/:
sarissa.js
Sarissa.js
The only difference is: one has an upper-case 'S' in the file name and
uses DOS line endings, the other one is lower case and uses UNIX line
endings[+]. I propose we drop one. Since t
Hi Olivier,
As quoted from "olivier.terral" <[EMAIL PROTECTED]>:
> MapScaleText never use cscs so I don't think it's a cscs problem.
Hmm, interesting.
> But say me what scale I must find for mapViewer demo?
The mapViewer demo:
http://localhost:8080/mapbuilder/demo/mapViewer/
actually uses Map
Hi Gertjan,
MapScaleText never use cscs so I don't think it's a cscs problem.
But say me what scale I must find for mapViewer demo?
Gertjan van Oosten a écrit :
> Hi Olivier,
>
> I just noticed (in the mapViewer demo) that the MapScaleText is no
> longer correct. It was correct just before
Hi Olivier,
I just noticed (in the mapViewer demo) that the MapScaleText is no
longer correct. It was correct just before the CSCS commit, and is now
incorrect after updating CSCS. Could you please have a look at it?
Kind regards,
--
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.
Hi,
I just added the Austrian projections again.
Regards,
Andreas.
On 6/1/07, Gertjan van Oosten <[EMAIL PROTECTED]> wrote:
> Olivier,
>
> I have changed (in r2862) some of the hard-coded messages in the CSCS
> code to use the mbgetMessage() method. What surprises me is that many
> of these wer
Olivier,
I have changed (in r2862) some of the hard-coded messages in the CSCS
code to use the mbgetMessage() method. What surprises me is that many
of these were messages that were already translated in Proj.js; it is
almost as if you were working from an old version of it. In which case
I worr
Hi,
I am trying what you have said to me. I've created a new button called
MovePoint.js. In this file, I've changed doAction() method to get the
feature of the old point, but I failed. I do not know what I have to
do to recover the feature of the point.
I attach you the file. I wish you can help
20 matches
Mail list logo
