Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

9 messages Options
Embed this post
Permalink
Tom Fukushima

Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Jason Birch

RE: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
+0 Jason

Still not convinced that storing device-based items in this schema is a good idea for portability.

Jason

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Tom Fukushima
Sent: Monday, July 27, 2009 9: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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Paul Spencer-2

Re: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
+1 Paul

On 27-Jul-09, at 2:58 PM, Jason Birch wrote:

> +0 Jason
>
> Still not convinced that storing device-based items in this schema  
> is a good idea for portability.
>
> Jason
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]
> ] On Behalf Of Tom Fukushima
> Sent: Monday, July 27, 2009 9: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
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Andy Morsell

RE: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tom Fukushima
+1 Andy



-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
Sent: Monday, July 27, 2009 9: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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Trevor Wekel

RE: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tom Fukushima
+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: [hidden email] [mailto:[hidden email]] 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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Kenneth Skovhede, GEOGRAF A/S

Re: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tom Fukushima
+0 Kenneth

Regards, Kenneth Skovhede, GEOGRAF A/S



Tom Fukushima skrev:

> 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
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>  
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Robert Bray-2

Re: Motion: vote MapGuide RFC 67 - CommonPrint Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
In reply to this post by Trevor Wekel
+1 (Bob)

--------------------------------------------------
From: "Trevor Wekel" <[hidden email]>
Sent: Monday, July 27, 2009 5:19 PM
To: "MapGuide Internals Mail List" <[hidden email]>
Subject: RE: [mapguide-internals] Motion: vote MapGuide RFC 67 - CommonPrint
Layout and Print Layout Elements

> +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: [hidden email]
> [mailto:[hidden email]] 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
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals 

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Bruce Dechant

RE: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tom Fukushima
+1 Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] 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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
Tom Fukushima

RE: Motion: vote MapGuide RFC 67 - Common Print Layout and Print Layout Elements

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tom Fukushima
Hi,

RFC 67 has been approved.

Thanks
Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] 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
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals