[Tickets #2565] Re: Gecko Bookmarks extension
bugs at bugs.horde.org
bugs at bugs.horde.org
Fri Jul 27 16:54:09 UTC 2007
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=2565
-----------------------------------------------------------------------
Ticket | 2565
Updated By | joey at joeyhewitt.com
Summary | Gecko Bookmarks extension
Queue | Trean
Type | Enhancement
State | Feedback
Priority | 2. Medium
Owners |
+New Attachment | treanmarks.diff
-----------------------------------------------------------------------
joey at joeyhewitt.com (2007-07-27 09:54) wrote:
OK, here's a diff against CVS HEAD from last night.
Note that you'll have to ensure that the new
horde/framework/RPC/RPC/jsonrpc.php file ends up in your PHP include path.
Hopefully this is much easier for people to review. I'm not in a hurry to
see it committed to CVS, but if it's easier for someone to do it now, I
guess I'm alright with the new JSON-RPC stuff (small change to
horde/rpc.php, a new jsonrpc.php file mentioned above, and removal of
obsoleted trean/json.php) being committed. But trean/lib/api.php needs
some documentation, if not reworking, before I'm finished with it. If I
decide I no longer need some API methods, do we think anyone is using them
right now?
Here are some things I have in mind for more work on the extension:
o More error checking and reporting
o Finish implementation of separate TreanMarks/Bookmarks menus
o Downloading the XPI from the Horde server
o Setup wizard, a la Foxmarks, with configuration of Horde server URL
(with nice preset URL set to the server it was downloaded from, perhaps
other settings pulled from server too), import of Firefox bookmarks.
o Multiple Horde servers/users aggregated into the bookmarks
o Start investigating Firefox 3, as I have a nasty feeling its "Places"
replacement for bookmarks is a new implementation that could be drastically
different :-)
Any other suggestions?
-Joey
P.S. I haven't seen any XHR/Firebug errors with this rewrite, so I think
that's fixed!
More information about the bugs
mailing list