[mapguide-users] mapguide-react-layout 0.7 released

[Jackie Ng]

Hi All,

I've put out a new release of mapguide-react-layout.

Download:
https://github.com/jumpinjackie/mapguide-react-layout/releases/tag/v0.7

This release contains lots of new features which I've blogged about here

http://themapguyde.blogspot.com.au/2017/01/announcing-mapguide-react-layout-07.html

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[GordonL]

Happy New Year Jackie. Fantastic job!
I cannot believe how responsive and fast the new view is!

gordon




--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5301785.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

Good to hear about the speed. Have you been trying this with really "heavy"
maps with 100 or more layers?

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5301909.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[dan.nilsson]

Hi!

I have tested it with "heavy" maps, with many layers.
The layers is connected to PostGIS, SQLite, SHP files and WMS.
It is very good speed!

I have found out that if I have more than two levels in layergroups, the
layer legend doesn't work.
Is this a known issue?

And I have more than one layer with flyouts (maptip), only the first layer
with flyout works.
For example, I have a polygon layer that have a flyout. If I then have a
point layer over that polygon layer, the flyout for the point doesn't show
up. Or is it only in my installation?

I am using MapGuide OpenSource v3.1.0.9064 on a Windows 10 x64.
The browser I use is Microsoft Edge, IE11, Firefox 50.1.0, Google Chrome
Version 55.0.2883.87 m.



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5301916.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

Re: nested layergroups

Most likely a bug, probably because I forget that a layergroup itself can
have child layergroups

Re: maptip

I'm sure this is normal behaviour that the tooltip query stops at the first
feature of a matching tooltip-enabled layer and returns tooltip data for
that feature.


Good to hear another data point about the good performance. I suspect the
legend was the bottleneck for older viewers on heavy maps due to the large
amount of DOM nodes (to represent layers/groups/rules) needed to be manually
created/shuffled around.

React and its highly-performant virtual DOM makes this a non-issue, which is
why the legend in mapguide-react-layout is much more snappy.

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5302056.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[dan.nilsson]

Have tested with other layers now that have tooltip.
Found out that I can't get any tooltip on point layers and line layers, only
on area layers.
It works fine if I have two area layers and when I move my pointer over the
different area layers.
So the problem is the point layer and line layer, I think.

Have tested it on ipad also, and the tooltip show up there also when I hold
my finger for some second on the object, very nice!

- Dan



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5302079.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

Re: ipad

That's ... surprisingly great!

Since tablets have no notion of mouse events, something must've translated
the long press to an idle mouse pointer that triggers the tooltip request

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5302210.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Kajar]

When using sidebar.html template and web layouts then in viewer(chrome,
firefox) I got only a slice of map not full map as it was defined in
Maestro.
Visible map area is about 46km x 395km so map height is reduced.
Full map size must be about 250x395km.
Is there are any restrictions about map window size?
Using aqua, slate or other templates and applicationdefinitions then map
size is correctly in viewer.

Kajar



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5302304.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

That sounds strange. Sidebar template doesn't do anything special, it's a
"full screen" map with a responsive sidebar draped over on the left hand
side.

If you look at the map image rendering requests made in your browser dev
tools, do the width and height parameters match your browser viewport size?

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5302316.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Kajar]

Now same problem occurs using slate, aqua or other templates also, something
completely broken when trying to use react.
But Sheboygan webloyout working normally so something must be wrong with my
own map or layout.
Background Openstreetmap is fully visible but all other layers is visible
only in the center of the map screen.
Does somebody else having similar issues. For me react layout is not working
also in my second mapguide server I set it up. Can it be some coordinate
system problem?




--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5302397.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Kajar]

This is so annyoing. I have same problem in three different servers I
have(win 7 and win 10 and MG 3.1).
Strange is when using Sheboygan sample then react layouts working as it
should.
But when I use my own made maps then react not working. Maybe this is some
some CS problem.
I use EPSG:3301 and 3857. Sheboygan uses 4326 but also 3857 and both
working.
Somebody have any idea, whats can be wrong?

Kajar



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5306561.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Kajar]

I found the source of problem and this was Infrastructure Studio(latest one).
I tried to create layout using Maestro and then react is working.

Kajar




--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5306572.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

I'd be interested in having a copy of the layout that Infr. Studio produced,
just to see what in it causes the viewer to break.

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5306707.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Kajar]

I have made lot of research related this issue I'm experiencing and found
that Studio is not breaking layout for react but issue is related to map
definition. When creating map with Studio and set map extent using "use
current map zoom to set these coordinates" and then use this map and react
layout then layer is not fully visible. Even if layer in Studio map
preview seems fully visible is not correctly visible using react layout.
When you use same map which was previously created by Studio and use
Maestro to create new extent for map and save the map, then layer is
correctly visible using react layout.
So Studio map view extent generation causing some error for react layout.
I added also package I made for better understand the problem.
Some explanation using package:
Studio_map_false: this is map created with Studio and added extents for map.
Studio_map_true: this is fixed map( new extent for map) by Maestro.
Studio_flex_true: layout created with Studio using map
definition(Studio_map_true) which works with react.
Studio_flex_false: layout created with Studio using map
definition(Studio_map_false) which is causing faulty layer visibility with
react.
Studio_react_issue.mgp
<http://osgeo-org.1560.x6.nabble.com/file/n5306817/Studio_react_issue.mgp>


Kajar



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5306817.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

Issue logged:
https://github.com/jumpinjackie/mapguide-react-layout/issues/118

Thanks for the package, this will help.

- Jackie





--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5306934.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Kajar]

I'm a big Mapguide fan so if I can help to get it better then I'll help as
much as I can.

Kajar



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/mapguide-react-layout-0-7-released-tp5301769p5307028.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

[Jackie Ng]

An update for this bug.

I had been artificially capping the OL image layers to the extents declared
in the Map Definition. Why did I do this? I honestly don't remember :)

But that capping of extents is what was causing the strange "cropped out"
effect you were experiencing for the problem map.

This is fixed for the next release (0.11)

- Jackie



--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html