Hello Michael
On 09-Jun-01, you wrote:
>
> hmmm...
>
> i have some commentd/questions about that:
>
> 1. it seems that the complete window is "switched" in single window
> mode, correct?
Yes. In another post you wrote:
> of course it would be nice to use both when right clicking on a link
> (popup menu "open in new window" and "open in single window mode" or
> so)
Which is not possible because of this point:
> 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 ;)
> 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.
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.
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 :)
> 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..
> 5. using complete windows when switching also has the disadvantage
> that the speedbar settings of the first window are not used. e.g. i
> have the fastlinks in minimized mode. but when a new "window" pops up,
> they are open again. could in this case the setting of the first
> window be used, please?
See point 2.
Thanks
--
Matt Sealey <[EMAIL PROTECTED]>
Website http://www.kittycat.co.uk
_____________________________________________________________________
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