Re: package pages

I'll +1 that, svg sounds like it could be used effectively in the manual - possibly allowing the end-user to choose between the image based manual, and the SVG based manual would be good - since a lot of people are still on low bandwidth connections, and would rather download xml than images. Jon ----- Original Message ----- From: "Alexander Merz" <alexander.merz@t-online.de> To: "Jon Wood" <jon@jellybob.co.uk> Cc: "Bertrand Mansion" <bmansion@mamasam.com>; <smith@dybnet.de>; "'PHP PEAR Developer'" <pear-dev@lists.php.net> Sent: Sunday, October 13, 2002 12:56 PM Subject: Re: [PEAR-DEV] package pages > Jon Wood wrote: > > > I don't know if I'm being stupid here - but what would we take screenshots > > of? Most of the development for PEAR is being done on components that can be > > used to build web applications - how do you take a screenshot of the XML-RPC > > package, of a VFS package? > Replace "screenshot" with "figure". For some situations, graphics make > sense to avoid 1000 lines of text, ie. how works a SOAP request. And, > there are some apps in PEAR - PEAR installer&Co > > There are only some problems related to graphics in the manual: > - using vector graphics may be a solution, but not for all kind figure > (screenshots) > - SVG would be a good solution (XML-format), but isn't compatible for > the masses > > Proposal: allow SVG for manual and add a SVG2Image pass into peardoc-make. > >