hey Beej, you're going to regret ever starting this thread :) > + What's your biggest problem with V? That I have reported bugs, know they are fixed, but have no access to the latest version :) > + What has been the best improvement or addition in the last year? Flash! AAAaaa.. saviour of the universe! :) > + If you decide to use IBrowse instead of V, why is that? The configurable per-site options are nice. ~ The new font doobry which allows you to do *real* FONT FACE support is okay, but I hate the way it's done. I would like to see in Voyager: Support for FONT FACE tag by simply looking for the named font in the font list. So if you have ttf.library installed and a copy of the Tahoma font, and a site asks for it, then you get it. There would be a list of default sizes for the font to use, as per the standard font options. If the font can't be found, or if the user wishes to set some options like alternate sizes (which could be done via wildcards: set all fonts matching "Arial#?" to use sizes 11,12,14.. instead of the defaults or something) then they can, a la IBrowse. This would pave the way for easy font support via CSS: by simply implementing the styles serif, sans-serif, cursive, fantasy, monospace, etc. and redirecting them to fonts (a la IE5 on the Mac). ~ I'd also like to see proper Unicode support: all the truetype fonts I have have full unicode tables, including Euro symbols. When someone asks for a symbol like © or ™ or whatever, it should ask the font for the unicode glyph that goes with it, rather than using the Amiga's duff font mapping (you could ask the ttf.library author about this I think) ~ Other stuff I'd like to see in Voyager? Hmm.. A proper download manager! Support for something like Charon would be great (now THERE'S an option for a new Vapor product, a Go!Zilla style download manager). Even something that looks anything like the one IE5 for the Mac has! (i.e. simple, progress bars, etc.) An option to have a progress window like IE for Windows: a seperate little download window with stats and things for each download task? ~ Support for mFTP-II so that you can redirect FTP site links to it! Right click menus etc.. ~ Hover-underlining for links! ~ Full PNG transparency support, like proper alpha channels, if it isn't in there already. ~ "Multithreading" of Voyager windows: if I have two windows open and one is chugging through Freshmeat.net, the other locks up while the other lays everything out. I can't enter URLs or click on links! A seperate task for each Voyager window, that share the network and image decoder tasks, maybe? ~ A proper Error Window, like YAM has. So that if I get a network error, I don't have a requester-per-connection pop up and say "couldn't access something, connection refused 61". And the same for Javascript errors. ~ Decent docs for the ARexx port! The ability, like AWeb, to execute ARexx scripts from the URL bar or links, but only executable from the local machine because running stuff off a network server would be a security risk. (let Amigactive Magazine use a DECENT browser!) ~ Support for saving the history list, and cache stats, to disk WHILE V3 IS RUNNING. So that I can close down the MooBunny window, and surf on in another safe in the knowledge that if my Amiga crashes, or if V locks up, or whatever, that the links will stay visited and my cache won't overflow. ~ The ability to use an external editor like GoldED *by default* for editing HTML source code - instead of loading up the texteditor class and clicking on the tiny button.. And activation of the Save button on the source editor for local file://! ~ Friendly HTML error messages, like Internet Explorer does. ~ The ability to use Datatypes fallbacks for images - especially since OS3.5's datatypes system allows you to keep the image in memory and decode it in-situe, rather than saving it to disk. And does Voyager support XBM files? ~ Support for some kind of ColorSync type thing, or gamma correction for images? ~ Dithering of colours for table backgrounds (BGCOLOR) as long as it doesn't make a complete mess.. ~ When a javascript opens a new Window, it should use a smaller, cut-down, less-toolbars-and-gubbins version rather than an ENTIRE Voyager window: i.e. don't do what IBrowse does, do what Netscape does! ~ Configurable spoofing string. ~ NUMBERED Ordered Lists ~ A guaranteed release within the next week or two :) ~ Ummm... that's it for now :) I'll be back with more as and when I think of them :) > The point is to be constructive, so don't get carried away :) :) -- Matt Sealey [EMAIL PROTECTED] Distributed Systems Support Computer Centre University of Leicester ____________________________________________________________ Voyager Mailing List - Info & Archive: http://www.vapor.com/ For Listserver Help: <[EMAIL PROTECTED]>, "HELP" To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
