Thread
System 6 Browser Development Opinions
Any chance we can get an early build?Yes, still working on it when I find the time.
It's not pretty to look at, lot's of debug tracing etc. It's built from the bottom up, so not useable as a browser, but just rendering stage to do. It's going to sound awful, but I'll try and make a Christmas present of something to see.Any chance we can get an early build?Yes, still working on it when I find the time.
Do you have a name for it yet? I have a suggestion: 6Browse.
Very close!!!Do you have a name for it yet? I have a suggestion: 6Browse.
I'm calling it "Browser6" at the moment.
maybe even 68rowse :b&w: 1337Very close!!!Do you have a name for it yet? I have a suggestion: 6Browse.
I'm calling it "Browser6" at the moment.![]()
Oh, I thought it should bemaybe even 68rowse :b&w: 1337
68000-AAAA030000000800-06-0050
Which is CPU, IP SNAP, TCP packet type, then port 80.
*sneeze* pardon me. is that sleigh bells i hear? ;-D
Will it be able to open local .html files? I recall one browser that wouldn't let you do that.
What is the creator/type associated with HTML files?Will it be able to open local .html files? I recall one browser that wouldn't let you do that.
I didn't think html files had resource forks... When I get back on my PowerBook 3400 I'll take a look.What is the creator/type associated with HTML files?Will it be able to open local .html files? I recall one browser that wouldn't let you do that.
Okay, I'm on the slow 3400c. Netscape saves html files with type TEXT and creator MOSS.
I don't know what the point of this is.
I don't know what the point of this is.
It'sI don't know what the point of this is.
(a) how the finder opens files by determing which application to use
( B) how the application decides what type of file it is
So, say a browser is told to open a file of type 'TEXT', what is it expected to do? A reasonable thing is to show all the raw HTML as just text, because that is what open a TEXT file means.
In order to keep this thing simple, I don't want it to have to delve into a file to try and determine what type of data it contains.
why not have it trust the file type (extension)?
You don't want a Macintosh application then? The Macintosh approach is that file extensions are for Neanderthals. The file type is held within the finder info, not the name of the file.why not have it trust the file type (extension)?
Browsers themselves shouldn't give too hoots about file extensions as they go by the Content-Type HTTP header field.
porter, is browsersix supporting inline images, or calling an externat da/app?
I'm only supporting GIFs at the moment. I'll look at the possibility of PNG once the rendering is done.porter, is browsersix supporting inline images, or calling an externat da/app?
If you had to go one format only, I'd say let it be PNG. GIF is a dinosaur. Does anybody really make new images in GIF format?I'm only supporting GIFs at the moment. I'll look at the possibility of PNG once the rendering is done.
Unfortunately yes. Doubly so if you have to support IE6 visitors, which is still a large portion of web users.
Many website banners are GIFs.If you had to go one format only, I'd say let it be PNG. GIF is a dinosaur. Does anybody really make new images in GIF format?
Like this one ...
... and this
Every graphical browser ever made supports giff... same can't be said for png.
so porter, to support jpeg, would you call an external da?
Bah! Forget those losers!Unfortunately yes. Doubly so if you have to support IE6 visitors, which is still a large portion of web users.
Sometimes you have to make a clean break from the past. }Every graphical browser ever made supports giff... same can't be said for png.
That may be difficult in a System 6 browserSometimes you have to make a clean break from the past. }![]()
Doesn't the server tell the browser what to do with a file (since most non-HTML files don't have a Content-type header)? I'm basing this off my *limited* experience with MacHTTP, but I know that until I add a MIME type entry to the server's config any oddball files try to come through as plain text. Of course the server uses the file extension to determine what it is, so whether or not the browser cares about extensions should be a moot point.Browsers themselves shouldn't give too hoots about file extensions as they go by the Content-Type HTTP header field.
I'm basing all my decisions on the Content-Type, that will tell you if it's plain text, html, GIF, etc. I'm not going to do anything with MIME.
If the server doesn't provide the Content-Type I'll have to assume something. That assumption may be wrong in some cases.
Currently I'm not intending doing anything with JPEG. You may have the opporunity to download the file, but that would be it, I don't intend to support Quinn's IC.
If the server doesn't provide the Content-Type I'll have to assume something. That assumption may be wrong in some cases.
Currently I'm not intending doing anything with JPEG. You may have the opporunity to download the file, but that would be it, I don't intend to support Quinn's IC.
Seems reasonable. Are you planning to have a text-only mode available?
Yes. It will "just happen". If it's text it gets shown as text, if it's text/html it gets parsed and rendered, if it's anything else, we'll see.Seems reasonable. Are you planning to have a text-only mode available?
Are we gonna be seeing a Browser6 - Xmas Edition?
So how do I publish what I have done so far?Are we gonna be seeing a Browser6 - Xmas Edition?
Avoid sarcasm at all costs.