COmanage Developers List

[Benn Oshrin <>]

I don't think the license is compatible with Apache 2.

And actually, anything external code we use needs to have an Apache 2 or 
compatible license.

On 2/2/12 6:45 PM, Marie Huynh wrote:
> I found this old menu plugin:
> http://www.udm4.com/
>
> It can be tabbed through.  See the demo below:
> http://www.udm4.com/demos/style-original.php
>
> It also has instructions for cakephp and looks like it's still
> maintained.  Should we switch the menus to this?
>
> Marie
>
> On Tue, Jan 3, 2012 at 9:57 PM, Marie Huynh 
> <
> <mailto:>>
>  wrote:
>
>     I found this fork of jqueryui that has a select menu not included in
>     the standard one:
>
>     https://github.com/fnagel/jquery-ui
>
>     Demo:
>
>     http://jquery-ui.googlecode.com/svn/branches/labs/selectmenu/index.html
>
>     Any problems with adding a few files for this?  The menu currently
>     looks like this:
>
>     https://skitch.com/mariehuynh/gi57c/comanage-registry-groups
>
>     I took the liberty of overriding some existing CSS, adding rollovers
>     (my mouse was over the white "As Known To LIGO" text during the
>     screenshot) and rearranging things a bit.  On the far left are the
>     personal things that everyone will see for managing their own data.
>       Those who have privileges to manage groups, orgs, and the platform
>     will see those.  The dropdown carat and envelope for notifications I
>     took from standard jqueryui.
>
>     The links are as functional as the old menu page; notifications have
>     not been implemented yet and the logout button works as well as it
>     did before, which is to say that it doesn't really.  The unthemed
>     select was supposed to be for choosing a CO; we will need to discuss
>     how that should be implemented so it doesn't need to be chosen again
>     so often.  The old menu already iterated through the list of COs and
>     I've pushed those into the 3rd level in the first menu so the 2nd
>     level wouldn't be so cluttered.  This seems better than redirecting
>     to the selector on its own page and I'd rather not have the selector
>     floating around unless a page needs it.  Thoughts?
>
>     Marie