Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
John Abreau wrote: > An extension would actually get pretty complicated; Seems pretty simple to me... > I'm not sure how it would determine whether to load index.html, > index.htm, index.php, index.jsp, default.htm... You'd simply declare a list of files to try and the order: index.html index.htm default.htm default.html ... whatever. It could be an option you set in your prefs.js. > Also, the plugin would then have to somehow access the private > resources on the server necessary to properly render its php and jsp > pages. Anything that requires server-side processing would be out of the question. This is perfectly acceptable if you understand the use case: the purpose of such a plug-in would be to provide a friendlier way to browse a local file system. The automated behavior would only apply to file:// URLs. Think local documentation, mirrored web sites, stuff stored on CDROMs, etc. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |