Re: [Galeon-devel] Re: [Usability]Galeon feature implementation

[Jeff Waugh <jdub perkypants org>]

<quote who="Yanko Kaneti"/>

> > So, the idea: Galeon already has cool Smart Bookmarks (now
> > "AutoBookmarks").  It's dynamic, clever, and will floss your teeth if
> > you ask it nicely. 
> 
> Confusion abound. galeon1 has AutoBookmarks (automatically generated
> bookmarks folder representing the sites that are visited most often,
> statistically). And there are the SmartBookmarks (bookmarks with
> parameters) which are completely outside the scope of this issue.

Thanks.

> Do you claim that autosaving of session information will remove the need
> for any UI for arbitrary saving a named session? I fail to see how.

Not at all, but once the session information is related in the user's mind
with bookmarks, the UI fits nicely into the bookmarks menu.

> I want a session named "cisco VOIP" at this specific moment. Dont see how
> autowhatever fits in this pattern.  _If_ the code for session handing is
> moved to the bookmarks I will still need a "bookmark this session" action
> somewhere in the UI.

Definitely, and I'd suggest that "Save Bookmark Collection" or something to
that effect was used.

> > (Yanko also notes that extra session information cannot be saved with
> > bookmarks. Given that you're using XBEL, I say "Bollocks to that!" Throw
> > in an extra namespace for Galeon session information, and you're done.)
> 
> With this approach I sense complexity that outweights the potential
> benefit (the mentioning of the poor animal was my gut reaction). Ricardo
> as the bookmarks code author would have a better idea I guess.

It's not very complicated. You've already got tags for the bookmarks
themselves, you just need to add namespaced attributes and/or some other
tags to save the session state. To Galeon, it's XBEL++, to other software
it's XBEL and some other namespace it can happily ignore.

- Jeff

-- 
            ...                           *bounce*bounce*bounce*