David Tulloh <[EMAIL PROTECTED]> writes:
Personally I have always prefered documentation in plain text form. I feel that it should at least be provided as an alternative to html.
Confucius says: easier it is to automagically generate plaintext from HTML than the other way around. : )
So, writing them as HTML and providing a plaintext copy like you suggested would be a very real possibility.
By using a browser as your help system just slows everything down, and introduces bloat.
So you're saying using a component that's already there is bloat, but writing our own that will only be used in this sole context is not?
I think bloat was probably the wrong word. I would rather not wait for mozilla to start up and then have to connect to the internet to be told how to resize a window (for example).
Looking into it the size of the documentation comes from the images. The actual documentation is in a modified form of html already, renaming the main file and opening it in mozilla causes it to display all the images and a little bit of content.
With some hacking in gimp I managed to cut the E_backgrounds_settings.png file from 256K to 147K with no visible deterioration from the process (that wouldn't be fixed with some care).
Essentially I made the background transparent, trimmed the bottom off and cranked the compression right up. I was going to attach it but don't want to annoy all the dialup users, I will send it to any who ask.
This could probably be improved further by introducing dynamic image scaling so the image could be saved at a smaller resolution.
David
(sorry, forgot e-devel first time)
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
