[Project_owners] Persistant attribute in a <toolbar>
mike at nachbaur.com
Fri Oct 7 10:53:37 EDT 2005
Ah, well in that case the problem is simpler. My suggestion is to
simply set a property in the user prefs for your extension that
indicates the visibility state of the toolbar. When you add the
toolbar you can check that preference, and set the hidden attribute
accordingly. If you put the toolbar in the browser using a XUL
overlay, then my recommendation would be to have the toolbar be
hidden by default, and check the preference at window load time,
possibly un-hiding it at that time.
On Oct 7, 2005, at 9:43 AM, Didier Ernotte wrote:
> In fact, I only use a toolbar in order to have a "area" at the top of
> the screen for which the user can hide it or show it easily. The
> content is a simple hbox with my RSS scrolling ticker. The standard
> location for that ticker is in the status bar, but the user can
> move it
> at the bottom or at the top of the screen. When it's located at the
> top, I create a toolbar as the parent of my hbox. But some user
> want to
> keep the attribute hidden/collapsed ? of the toolbar from one session
> to another.
> --- Michael Nachbaur <mike at nachbaur.com> wrote:
>> On Oct 7, 2005, at 1:49 AM, Neil wrote:
>> If you are building your toolbar dynamically, you can just track what
>> changes are made to the toolbar and store those in the user prefs or
>> in rdf:local-store.
>> How do you build your toolbar, by the way? How do you decide which
>> buttons, labels, etc to create? If you store the definitions for the
>> toolbar in RDF, then it could be possible to store the definitions
>> for persistance in there as well, and can build your toolbar using
>> XUL templates.
>> I do something very similar (not with a toolbar, but with a side-
>> panel of buttons).
>> Project_owners mailing list
>> Project_owners at mozdev.org
> Project_owners mailing list
> Project_owners at mozdev.org
More information about the Project_owners