[mapguide-internals] RFC Review - RFC 96: QuickPlot solution for both Ajax and Fusion viewers

[Ivan Miličević]

Hello,

I'm just wondering, is it possible to add "save-as-DWG" method in QuickPlot solution?

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Mars Wu
Sent: Friday, June 18, 2010 9:40 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC Review - RFC 96: QuickPlot solution for both Ajax and Fusion viewers

Hi Jason,

Maybe the new QuickPlot can co-exist with the "save-as-dwf" widget?
My idea is that QuickPlot provides this kind of workflow: select region -> preview -> print. While the "save-as-dwf" widget provides a quick way to save current screen as a file (picture or DWF) and maybe send it via email to share with others.  So the workflow is like: select region -> save -> share.

Thanks,
Mars 

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Sunday, June 13, 2010 2:47 PM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] RFC Review - RFC 96: QuickPlot solution for both Ajax and Fusion viewers

If you change to advanced mode on my map
(http://maps.nanaimo.ca/nanaimomap/) you can see the way DMSG implemented the save-as-dwf fusion widget.  I wonder if giving options html/png/jpg/dwf would be cramming too much into one widget/task.

On 2010-06-12, Mars Wu <mars.wu at autodesk.com> wrote:
> Hi Jason,
>
> Really thanks for your comments!
>
>>> - what is the output format for quickplot? I understand that the 
>>> preview window will show layout; is the output the same html+png as 
>>> the current print widget, but with higher dpi image?
>
> It's basically right. The output format is still HTML +png. And the 
> picture has higher dpi
>
>>>- sounds like there may be a dependency between fusion and the ajax 
>>>viewer  for this function. If so, please work to avoid this. These 
>>>viewers should  be able to be individually removed from a production 
>>>install to limit  attack surface area.
>
> There will be no dependency between fusion and Ajax viewer. The "share"
> between Ajax and Fusion will be based on "idea" level. Maybe the code 
> will be copied from Fusion to Ajax and has a small change to work in Ajax viewer.
> And also the "main UI" which is in the taskpane will "look" the same 
> in Ajax and Fusion. (but the code is separated)
>
>>>- I wonder if there is a way to shape this enhancement so that it 
>>>replaces  the current print function instead of adding a new one?
>>>Maybe have it  open the task pane first, with optional area-select 
>>>button, title, dpi,  and print button at bottom? Ideally, would allow 
>>>selecting sheet size,  portrait/landscape, and format as well, but I 
>>>know that's stretching it a  bit...
>
> "Replacing" the existing widget could be a good idea, it will remove 
> confusion for the user, I like it... (I will update the RFC on this) 
> About the "sheet size", it's also in the plan (I will update the RFC 
> on
> this)
> About the "portrait/landscape", the "capture box" could be rotated. 
> Then by default it's Landscape, if the user rotates it by 90, then it 
> will be Portrait.
> About the format (I guess you are talking about PDF), it's not planned
> :)
>
> Thanks,
> Mars
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason 
> Birch
> Sent: Sunday, June 13, 2010 1:39 PM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] RFC Review - RFC 96: QuickPlot 
> solution for both Ajax and Fusion viewers
>
> You forgot the part about PDF support! :)
>
> Seriously, I have a few questions:
>
> - what is the output format for quickplot? I understand that the 
> preview window will show layout; is the output the same html+png as 
> the current print widget, but with higher dpi image?
>
> - sounds like there may be a dependency between fusion and the ajax 
> viewer for this function. If so, please work to avoid this. These 
> viewers should be able to be individually removed from a production 
> install to limit attack surface area.
>
> - I wonder if there is a way to shape this enhancement so that it 
> replaces the current print function instead of adding a new one? Maybe 
> have it open the task pane first, with optional area-select button, 
> title, dpi, and print button at bottom? Ideally, would allow selecting 
> sheet size, portrait/landscape, and format as well, but I know that's 
> stretching it a bit...
>
> Jason
>
> On 2010-06-12, Mars Wu <mars.wu at autodesk.com> wrote:
>> Hi all,
>>
>> Could you help to review the new RFC here?
>> https://trac.osgeo.org/mapguide/wiki/MapGuideRfc96
>> Any comments are appreciated!
>>
>> Thanks,
>> Mars
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals