Great Warpzilla Screenshots

Wednesday June 9th, 1999

Paulo Dias has great news and screenshots on their OS/2 port of Mozilla.

"...some news from John Fairhurst of the warpzilla project (OS/2 mozzila port): 'Warpzilla is currently floating around the m6 level (that is, on parity with the main platforms) with a few minor & one major exception (see below). I've stuck a couple of screenshots of the browser here -- the editor & various other minor applications seem to work; messenger brings up a 3-pane window but I haven't quite figured out how to point it at a mail- or newsserver.

The major exception is a strange kind of PM resource leak -- after quitting the program, random bits of windows stop painting properly,almost as though the stock of micro cached presentation spaces had been used up. This started happening back in January, but subsequently fixed itself; it's back.'

The screenshots are awesome.. check them out..."

#1 Re:Great Warpzilla Screenshots

by asa <>

Wednesday June 9th, 1999 8:24 PM

Reply to this message

You guys rock!

#2 Re:Great Warpzilla Screenshots

by sspitzer <>

Wednesday June 9th, 1999 10:49 PM

Reply to this message

look at <> on how to set up your prefs to use mail / news.

#3 mailnews prefs etc.

by johnf <>

Thursday June 10th, 1999 3:42 AM

Reply to this message

Yeah, thanks -- I was suffering from (a) not previously having used comm4.x for mail/news and (b) an amusing hard-coded path involving C:\TEMP or something -- a drive which happens not to be accessable on my system.

imap works; send message hangs (100% cpu); guess I'm going to have to poke comm 4 into producing some kind of .newsrc to see if news works.

#4 Re:Great Warpzilla Screenshots

by Anon

Thursday June 10th, 1999 7:35 AM

Reply to this message

I guess the only complaint I have about the screenshots (and this goes for all platforms, not just OS/2) is that the left pane witht he 3 windows stacked on top of each other is really innefficient. Each window by themselves does not have enough display space to display their own informmation without looking crowded (SIX scrollbars on the screen all stuffed together makes the UI look very very busy. May I suggest using tabbed paines?


#5 Re:Great Warpzilla Screenshots

by mozineAdmin

Thursday June 10th, 1999 8:03 AM

Reply to this message

The latest build allows for each of those panels to collapse to just its header.

#6 Re:Great Warpzilla Screenshots

by SomeSmartAss

Thursday June 10th, 1999 8:24 AM

Reply to this message

"May I suggest using tabbed paines? "

according to the tab widget requirements <…abwidgetrequirements.html>

The authors at this time specifically do not intend to implement these arguably desirable features

* vertical tabs

* multiple rows of tabs

* scrolling tabs

* inline editing of the tab text (hey, we're trying to be complete!)

either of the top three would probably be needed to properly implement tabs in what will usually be a very skinny window. besides, tabs would only allow one open at a time, colapsability would be much more flexible (IMHO at least)

#7 Re:Great Warpzilla Screenshots

by arielb

Friday June 11th, 1999 2:00 AM

Reply to this message

I'm still thinking about the best way to do the sidebar but the current way just isn't good at all.

#8 Re:Great Warpzilla Screenshots

by arielb

Friday June 11th, 1999 3:55 AM

Reply to this message

btw John Fairhurst will leave the project an the end of the month

#9 Re:Great Warpzilla Screenshots

by SomeSmartAss

Friday June 11th, 1999 7:22 AM

Reply to this message

The horizontal scroll bars definately must go. If you want to read the entire title (or extra info) than you can open it wider). Also, the ability to "undock" it, so it floats above (or behind, as long as there was any easy, and obvious, way to bring it to the front) would be nice too. If it is undocked, any links should be sent to the last browser window used, and give that window focus.

#10 Re:Great Warpzilla Screenshots

by arielb

Saturday June 12th, 1999 9:22 PM

Reply to this message

I think chris had horizontal tabs in mind. Anyway I definitely think this bar should be separate from the browser-just like the bookmark app or history