<HTML dir=ltr><HEAD><TITLE>Re: [postgis-devel] Nice diagrams</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6001.18063" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText64536 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Chris,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Sounds like a good idea to not require the dependency of the documentation build. How hard is that to do?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Kevin,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>That was my thought. Although I don't think the convert script thing will be too hard unless we go nuts. My thinking is that it will be a magic 3 liner to take care of all situations. Just figuring out the magic 3 liner is the trick.</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> postgis-devel-bounces@postgis.refractions.net on behalf of Chris Hodgson<BR><B>Sent:</B> Tue 7/22/2008 12:59 PM<BR><B>To:</B> PostGIS Development Discussion<BR><B>Subject:</B> Re: [postgis-devel] Nice diagrams<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Perhaps the documentation could be built before the source packages are<BR>even built, so that people downloading the source don't need to have<BR>these dependencies, or waste time building the documentation<BR>images/documents from the sources. Only people building from an SVN<BR>checkout would need to do so, and ideally building the documentation<BR>would be separate step from building the library so that people who are<BR>helping with development don't necessarily need to have the dependencies<BR>for the documentation build either.<BR><BR>Just thinking this would be a good option to minimize the impact of the<BR>additional dependencies introduced for the documentation build.<BR><BR>Chris<BR><BR>Kevin Neufeld wrote:<BR>> Sure, sounds good to me too. I think it's important to have similar<BR>> styles throughout all the example images. This would be a good way to<BR>> accomplish that.<BR>><BR>> So, would we then have a section in the Makefile that would convert<BR>> all the svg image files to png and eps files? I can see this growing<BR>> quite large if we need to add different custom parameters to<BR>> ImageMagick's convert utility for different images or files types.<BR>><BR>> Cheers,<BR>> Kevin<BR>><BR>> Mark Cave-Ayland wrote:<BR>>> Obe, Regina wrote:<BR>>><BR>>>>> So, the proposal is to store the basic drawing in a SVG file<BR>>>>> and them use image magick to add effects and create EPS and PNG for<BR>>>> PDF<BR>>>>> and web respectively ?<BR>>>><BR>>>> That was my thought - store in some vector format so all sorts of<BR>>>> resolutions can be accommodated and not worry about shadowing and all<BR>>>> that stuff in the core output format. Use ImageMagick to do the fancy<BR>>>> fluffy stuff.<BR>>><BR>>> Sounds good to me.<BR>>><BR>>>> It may or may not be desirable to have shadowing in say PDF. SVG seems<BR>>>> like the easiest candidate to produce that core format and as you said<BR>>>> numerouse editors can output that.<BR>>>><BR>>>> As far as how we produce SVG hadn't thought much about it and not sure<BR>>>> it matters if we use InkScape or whatever. OpenJump can Save As SVG,<BR>>>> and for me personally that would be my choice since I use it a lot for<BR>>>> ad hoc queries anyway. I like that I can run my demo query, save as<BR>>>> SVG<BR>>>> and be done with it.<BR>>>><BR>>>> For certain cases the raw PostGIS output even using a template would be<BR>>>> a hassle when we need to overlay to show different colors, points etc.<BR>>>> and so forth since it would almost guarantee manual fiddling.<BR>>><BR>>> Yeah, I suspect that automatically generating the results from a<BR>>> shapefile will still require extra fiddling, although it could be a<BR>>> good starting point. My feeling is that it is more likely to be the<BR>>> styling of the images that will change rather than the contents, and<BR>>> it's probably just as easy to make the content changes using a<BR>>> program such as Inkscape.<BR>>><BR>>><BR>>> ATB,<BR>>><BR>>> Mark.<BR>>><BR>> _______________________________________________<BR>> postgis-devel mailing list<BR>> postgis-devel@postgis.refractions.net<BR>> <A href="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR><BR>_______________________________________________<BR>postgis-devel mailing list<BR>postgis-devel@postgis.refractions.net<BR><A href="http://postgis.refractions.net/mailman/listinfo/postgis-devel">http://postgis.refractions.net/mailman/listinfo/postgis-devel</A><BR></FONT></P></DIV></BODY></HTML>
<HTML><BODY><P><hr size=1></P>
<P><STRONG>
The substance of this message, including any attachments, may be confidential, legally privileged and/or exempt from disclosure pursuant to Massachusetts law. It is intended solely for the addressee. If you received this in error, please contact the sender and delete the material from any computer.
</STRONG></P></BODY></HTML>
<P><hr size=1></P>
<P><STRONG><font size="2" color="339900"> Help make the earth a greener place. If at all possible resist printing this email and join us in saving paper. </p> <p> </font></STRONG></P>