<[EMAIL PROTECTED]> wrote at Sat, 09 Jun 2001 17:54:59 +0000
about <[voyager] Re: comment on single window mode>:
[...]
> > 2. wouldn't it be better (and of course faster!) just to switch the
> > content of the real html frame instead of the complete window?
>
> The way V switches windows is to use a MUI feature which basically
> allows many windows to coexist at once: clicking the button simply
> changes the window that is displayed (or something to that effect).
>
> This way has it's problems in that it's an undocumented MUI feature
> (although Olli was the one who coded it into MUI, so :) and that
> you cannot really simply have this hack enabled for V and also have
> entire new windows popping up. It also plays havoc when you drag
> tearoff bars outside and drag them back in to a DIFFERENT window
> tab.
>
> It also has a HUGE advantage: that V can properly respect Javascript
> window and toolbar attributes for each window. So you have a borderless
> JS popup, and V can respect those attributes. And no silly hacks
> required to support this ;)
well... this windows-switching *is* sort of a hack, you mentioned ;-)
> > 3. why didn't you use the mui tabs but "simple" buttons instead? is
> > this a technical problem?
>
> It could be done with MUI "tabs", but they're a little clunky IMO.
well, but this would be a better way, imho.
> There *is* a technical problem in that I think V's HTML display relies
> on being able to be in it's own window (setting window titles etc.): the
> hack solves this. It could be abstracted so that window stuff was done
> through a wrapper, but that requires work.
sure - no question. new features require some work. but i'm sure olli
has this already on his list. especially if you think for v3 as sort
of a pluginable html browser. i mean, have a look at microdot2. these
days it is very common to send emails in html format or to exchange
documents in that format. now one day md2 hould be able to display
such mails and this could be done by using the rendering engine of
v3... but only if this is available as sort of a plugin, .mcc, or
whatever.
> Essentially there ARE much better ways of doing it, but they entail
> coding lots of new stuff, which could induce new problems, require
> more testing... you can look at AmIRC for ONE way of doing these
> tabs without that hack. But is that a suitable method? Someone needs
> to look at these things, and I think you'll agree that the time may well
> be better spent working on Javascript, or HTML lists :)
definately. currently stability, js and the not yet
implemented/working html tags have the highest priority. and vapor so
far always proved than they can do it.
> > 4. please allow those buttons (or later tabs) to be on the *bottom* of
> > the window (user definable). i'd prefer that as it is a standard on
> > other browsers.
>
> Hmm..
shouldn't be to hard.
thanks and
byebye...
--
Michael Merkel (MiMe@IRC)
[EMAIL PROTECTED]
http://home.t-online.de/home/Merkel.Michael/
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
