[mapguide-internals] Motion: vote MapGuide RFC 67 - Common
Print Layout and Print Layout Elements
Trevor Wekel
trevor_wekel at otxsystems.com
Mon Jul 27 19:19:50 EDT 2009
+1 Trevor
I suspect there are a few more MapGuide specific details to work out with the RFC. But since the RFC is intended to "allow the concepts and ideas to be vetted and explored" then it should be ok as long as the original print layout functionality is not broken by any submissions.
Thanks,
Trevor
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Tom Fukushima
Sent: Monday, July 27, 2009 10:49 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements
Hi,
I motion for a vote on
MapGuide RFC 67 - Common Print Layout and Print Layout Elements
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc67
Summary of review:
Call to create print layout service in MapGuide should use the site connection, not a service factory.
>> RFC updated.
MapView should be an optional element on MapViewportType, and its ViewDirection and Rotation parameters should also be optional.
>> RFC updated
+1 Tom
Thanks
Tom
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
More information about the mapguide-internals
mailing list