Sounds wonderful Chris. With the current place bookmarks is I think you can probably do the development in the trunk. If we need to fix something in 1.0.7 we can just branch back there and fix it. My first thought as to how to approach the changes would be in an incremental fashion so things still work after each change. That may not be possible for all changes but it is a noble goal :)

Also would you be interested in being listed as the project lead for bookmarks? All that means is you get to cut releases (or delegate that responsibility) and manage the Jira project.

Thanks for the interest in moving bookmarks forward.
-Eric

Chris Doyle wrote:
I just wanted to give everyone a quick heads-up regarding some work I am
interested in tackling (pending the groups' blessings, of course).  Last
year I began working on (yet another) Bookmarks Portlet here at JHU,
which was prior to my awareness of Eric's.  At the developer's meeting
in April, I shared my progress with Eric and we agreed it might be
beneficial to try and merge some of the more useful features of mine in
with his.  Most notably, I have implemented features that address the
following open issues:

        PBOOK-7    Drag and drop folder and bookmark moving
        PBOOK-24   Seeding the bookmarks portlet
        PBOOK-25   Multiply publishable
        PBOOK-26   Multiply subscribable (*partially begun work on
subscription mechanism)
        PBOOK-27   Read-only, administrator updatable mode
        PBOOK-29   CBookmarks upgrade path
        PBOOK-42   Provide a user option for default folder state

To begin this work, I'd like to create a new working development branch
in SVN:

        
https://www.ja-sig.org/svn/portlets/BookmarksPortlet/branches/JHU

I don't anticipate being able to complete the merge in time for the
upcoming conference, but would like to aim for a release later this
summer.  How does this all sound to everyone?

Just a little background on my current version...

        - It's already Maven-ized (using Maven2)
        - I use the Spring Portlet MVC (the project is very Spring-y in
general)
        - I use the concept of "groupings" or sets of bookmarks:
                - Conceptually, one XBEL document = one grouping
                - Groupings can be "pushed" to specific uPortal
users/groups
                - Administration of groupings can be delegated to
specific users/groups
                - Groupings can be set to read-only
        - There are some nice portlet parameters for configuration
        - I have written some web services around it using Axis2
                - I developed and use both a Java client, as well as a
JS client via AJAX
                - due to AJAX web service calls, there are very few
actual page reloads
        - I wrote a conversion utility used to upgrade from CBookmarks
        - Caching using ehcache
        - The UI is pretty nice (floating DIVs for input, dropdown
menus, etc.)
        - Drag and Drop!  :)

All that being said, there are also some major deficiencies,
limitations, and definitely some portability obstacles to be addressed.
(Everything is a constant work in progress, right?)  But I think I might
be ambitious (or crazy) enough to give this merge a try.

Thoughts?  Blessings?  Curses?

Thanks,

--Chris

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to