[Tickets #2565] Re: Firefox 3 bookmarks extension

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/2565
------------------------------------------------------------------------------
  Ticket             | 2565
  Updated By         | joachim at jnissen.de
  Summary            | Firefox 3 bookmarks extension
  Queue              | Trean
  Type               | Enhancement
  State              | Accepted
  Priority           | 2. Medium
  Milestone          | 2.0
  Patch              |
  Owners             |
------------------------------------------------------------------------------


joachim at jnissen.de (2010-05-13 06:28) wrote:

> Here's the first (beta-ish) release of my solution to this bounty.   
> I've oh-so-creatively named it TreanMarks (better suggestions  
> welcomed.)  It comes in two pieces: a patch to server-side Trean,  
> mostly to add RPC calls, and a Firefox extension implemented in  
> javascript.
>
>
>
> Features
>
> =================
>
> o 100% JS means it should be cross-platform! (or, as much so as  
> XmlHttpRequest is)
>
> o A TreanMarks menu next to the Bookmarks menu
>
> o Support for bookmark/folder deletion, adding bookmarks (by  
> delegating to Trean itself in a popped-up browser window), and  
> bookmark/folder properties (also delegated to Trean)
>
> o Locally caching the bookmarks and then "synchronizing" via RPC, to  
> cut down on time spent down-/up-loading
>
>
>
> TODOs
>
> =================
>
> o Look into 'compressing' server response XML (for RPC), by not  
> indenting prettily. I don't think this is even offered through the  
> PHP extension :( But I think it may cut down on wait times  
> considerably.
>
> o Pre-fetching bookmarks on browser load
>
> o Caching bookmarks to disk, for "offline" access (if that makes any  
> sense) or just quicker pre-fetches on browser load
>
>
>
> Bugs
>
> =================
>
> o Each browser window keeps its cache separately, so that means your  
> Trean bookmarks have to be loaded "into" each window.  I'd imagine  
> this might be simple to fix, I just haven't got around to it yet.
>
>
>
> Request for Comments
>
> =================
>
> I've actually been wondering if there's a different, much better way  
> to go about this.  Are there already (preferably HTTP-based)  
> protocols to do stuff like this?  Perhaps Atom?  Anyways, I'll get  
> this code out there since I've already invested a bunch of time into  
> it. ;)
>
>
>
> Files
>
> =================
>
> o treanmarks.diff is a "cvs diff -Nur HEAD" of all my Horde-side changes.
>
> o treanmarks.xpi is a Mozilla extension installer package.  It's a  
> renamed ZIP file, so you can get at all my extension source in  
> there. (By the way, anyone have a 32x32 Trean "heart" icon?)