-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
What browser
- Thread starter macguy
- Start date
That's because it's based on Mozilla.
No, dang it! It's MINE. ALL MINE. I WROTE IT. ALL ME.
Just ignore me surfing Bugzilla, because that has NOTHING to do with Classilla. At all.
Thank you for that wonderful mental image..... (The guys next to me at work have been having potty-humor all day, so I'm sure you can imagine what "plop out" entered my mind as plopping out of....)
No, that was lunch. Sorry about the mess.
As you can see, Jeff, I just don't know when to quit.
Looking like March for Classilla 9.1. I've got most of the major bugs shaken out of the new compositor. It's slower, but the scrolling and screen updates/repaints are way less glitchy than they were in 9.0.4. I'm trying to tune it up a little more, though.
Has "the bug" been fixed? It affects several forums I visit, where I have to turn off style sheets in order to read longer messages rather than get repeated portions near the bottom.
If you mean the infamous issue 65 that bedeviled me for months, yes. Well, more accurately, it's been kludged around. The problem seems to be that the double buffering code for OS 9 just doesn't work (and the solution for OS X was ... drum roll please ... turn off double buffering and let the OS sort it out, which is why 1.3.1 on OS X doesn't have the issue).
The workaround, if you're interested in the guts of it, came when I discovered that off-screen rects just crap out, so I turn off double buffering for rects that extend off screen and the scroll isn't glass smooth but is now correct.
Issue 28 is the one I think I have beaten into a state of submission today. This is an omnibus bug for a whole bunch of compositor glitches which individually have been hell to stamp out. The solution has been to make it overpaint to smooth these out, but overpainting is expensive, so I've been trying to figure out strategies for smarter overpainting in nsWindow and I think I have it to a useable point. It's still slower, so don't be surprised when scrolling doesn't act the same in 9.1, but visually now most things come out right.
Today I'm doing worst case testing on my tireless PB 1400. If scrolling is acceptable on that, then it should be acceptable most other places. Have to upgrade the hard disk first, tho, poor girl is running out of space!
I am sure you are sick and tired of hearing this, but the fact that you are re-working such a key piece of software for the (real) Macintosh platform is hugely appreciated. Classic really did have class.
Asked in 2004 what Apple should do next, Jef Raskin replied, "Turn out a good interface." Amen, I say. After nearly ten years of using the damn thing daily, I still can't find my way around OSX. The GUI on top is sugar-coating on the gawd-awful mess in the DNA, in the billions of lines of code that have grown merely by accretion, of the UNIX underneath. As Raskin put it, there really isn't any real difference anymore between Apple's OS and that of its competitors. Yes, I am sure that it is all ever-so powerful, and as OSes go, it is seemingly the pick of the litter, but it is Byzantine in its complexity, and only the insider who has lurked for years in its countless inversions and curlicues knows how to navigate it.
This has been recently brought home to me by my trying to work with BibDesk, a relatively simple bibliographic program which no doubt can be modified somehow to do exactly what you want it to do — except that I can't even find the files stashed away in umpteen different Libraries and such that, according to its Spartan wiki, require modification. Hours and hours I have spent on it, and given up. Remember the priesthood of the "computer scientist" of the 1960s and 70s, white-coated and pure so as to handle the "secret code" that the uninitiated must never touch? Well, we still have it today.
And so when I want to enjoy what I am doing on a computer, I go back to the old Macintosh system that was designed around the needs of a non-specialist user. The simpler, the better, and like it, I generally can only do one thing properly at a time when I am there.
I do, however, wish I knew how to program, if for no other reason than that I might then be able to tell the backside from the elbow of BibDesk. Unfortunately, I am old enough to have used early 68k machines in working life when they were brand spanking new, and therefore to have missed all opportunity for education in programming skills as a schoolchild; thus I fear it. I also did not pick programming up later at University, which I began when hole-punched cards were still in vogue, and I am presently too preoccupied with mortgages and such to learn. Filemaker scripts are about as far as I get.
I'd happily buy you a beer, though, let me tell you. Point yourself out in a crowd sometime and we'll find a good pub.
Asked in 2004 what Apple should do next, Jef Raskin replied, "Turn out a good interface." Amen, I say. After nearly ten years of using the damn thing daily, I still can't find my way around OSX. The GUI on top is sugar-coating on the gawd-awful mess in the DNA, in the billions of lines of code that have grown merely by accretion, of the UNIX underneath. As Raskin put it, there really isn't any real difference anymore between Apple's OS and that of its competitors. Yes, I am sure that it is all ever-so powerful, and as OSes go, it is seemingly the pick of the litter, but it is Byzantine in its complexity, and only the insider who has lurked for years in its countless inversions and curlicues knows how to navigate it.
This has been recently brought home to me by my trying to work with BibDesk, a relatively simple bibliographic program which no doubt can be modified somehow to do exactly what you want it to do — except that I can't even find the files stashed away in umpteen different Libraries and such that, according to its Spartan wiki, require modification. Hours and hours I have spent on it, and given up. Remember the priesthood of the "computer scientist" of the 1960s and 70s, white-coated and pure so as to handle the "secret code" that the uninitiated must never touch? Well, we still have it today.
And so when I want to enjoy what I am doing on a computer, I go back to the old Macintosh system that was designed around the needs of a non-specialist user. The simpler, the better, and like it, I generally can only do one thing properly at a time when I am there.
I do, however, wish I knew how to program, if for no other reason than that I might then be able to tell the backside from the elbow of BibDesk. Unfortunately, I am old enough to have used early 68k machines in working life when they were brand spanking new, and therefore to have missed all opportunity for education in programming skills as a schoolchild; thus I fear it. I also did not pick programming up later at University, which I began when hole-punched cards were still in vogue, and I am presently too preoccupied with mortgages and such to learn. Filemaker scripts are about as far as I get.
I'd happily buy you a beer, though, let me tell you. Point yourself out in a crowd sometime and we'll find a good pub.
I get the idea some people here only use Classilla occasionally, when they're using their older Macs. I just wanted to mention that I use my old Mac (8500 upgraded with 400 MHz Sonnet G3, 384 MB RAM) for about 8 hours each day (programming), and use Classilla full-time. I'd use my newer iMac G4 flat panel with OS X 10.3.9, except that I hate everything about it, starting with the 1024x768 display with no option for anything larger, even if plugged in externally. Classilla has been a godsend. Before, I used Internet Explorer 5.x, which has countless problems, and most importantly, lacks tabs. Having tabs has made an enormous improvement to my web experience.
Hay, you're a talking about me.
Albeit these days i use my "legacy" macs more then my iMac: perhaps it's because the latest OS ( snowyleopard ) is flash and dash BUT BUT BUT far more stable then OS 9, 8, 7.6 for the midi/audio programmes i need to run although i have learned ( most of the time ) not to do this or that which will inevitably crash those 7.6 thru 9 programs.
If your iMac G4 happens to be the 1 GHz model, you can use Screen Spanning Doctor to enable extended desktop. Then you can use an external display at higher resolution. (Unfortunately, the only 15" model that has a compatible graphics chip is the 1 GHz, none of the earlier 15" models can do it.)
Similar threads
