Re: Tabs are ready? -> Let us give a definition of tabs.

[Alin Soare <as1789@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

> > There is the conception of mozilla and many text editors that changing a
> > tab means to pass to other web page or other file to edit.
>
> What does "changing a tab" mean?  Do you mean pushing some graphical
> object with the mouse or replacing one graphical object with another?


Yes. Not necessarily with the mouse. You can call a lisp function to
commute to a new tab. In firefox you can commute to the next tab using
C-PgDn .

Every time when you commute to a tab, the lisp function associated to the
'show event is called.


> > In Emacs, I propose , the behaviour of each event of a tab to be defined
> > using lisp functions, attached to the events that tab reponds to.
>
> Can I transcribe this as "reacting to a tab event means to call a
> function written in Elisp"?


Yes.

In graphical systems, like GTK, there is the concept of 'callback.

>
>
> > This does not mean necessarly only commuting to other buffer, or
> commuting
> > to other window; in order to make a tab that does such a commutation like
> > in other text editors,  particular lisp functions should be defined for
> the
> > events of that tab.
>
> Sure.  But any such function could be used in another context as well.
> As mentioned before, we could easily add menu- or toolbar items which
> stand for "saving the current window configuration" or "restoring a
> previously saved window configuration".  I can neither see why such
> actions should be exclusively tied to tabs nor why tabs are very suited
> for them.
>
>
Probably yes. But a toolbar button is not a tab. And do not forget that
toolbar does not exist in console.

In mozilla you can install lots of kind of bars. And there is no doubt that
the tabs are still useful. In mozilla the tabs are used for current-open
pages.

[-- Attachment #2: Type: text/html, Size: 2656 bytes --]