[OOTB-addons] status of AAAR addon
fcorti at gmail.com
Tue Jun 2 22:27:07 BST 2015
Ops... I was mentioning Aikau framework and not Saiku (the Pentaho module).
Il 02/Giu/2015 22:42, "Francesco Corti" <fcorti at gmail.com> ha scritto:
> Hi Martin,
> Hi all,
> Following your invite, I start sharing an initial thought about the
> integration of the OOTB plugins in the Alfresco menu. Please read it as a
> personal contribution to the discussion.
> Of course I don't think to AAAR only, but I'd prefer to think to a certain
> amount of plugins that a community software should include as available (I
> think to Pentaho Suite and Liferay as good examples). I avoid to talk about
> 'the marketplace' that is an off topic, but IMHO this is one of the most
> relevant features Alfresco Community should have to make it more open to
> external contributions. :-)
> Back to the thread...
> My thought is that the item in the menu is mainly a shortcut to the
> features and, typically, it should be visible depending to the role/permits
> of the connected user. As you suggest, the menu item of the plugin could be
> in a "plugin list" under a principal "OOTB plugins" item (this is a sane
> solution because an administrator should want to install several plugins).
> In every case I imagine also a setup in the settings where the plugin item
> should be available directly in the main menu. The philosophy is: let the
> administrator choose the menu he/she wants for the users.
> Summarizing, my thought is:
> - Add the OTTB item in the main menu as unique new item.
> - The OTTB item has one sub-item for each plugin (ordered by name?).
> - The plugin sub-item should be visible depending on the role/permits of
> the connected user.
> - The plugin sub-item should admit sub-items, freely defined from the
> plugin's developers.
> - The plugin item could be requested to be in the main menu (not by
> While I was writing I was thinking on how to develop it and the Saiku is
> confirmed as a good solution because it should support all those
> features... but this is another topic. :-)
> 2015-06-01 17:55 GMT+02:00 Martin Cosgrave <martin at ocretail.com>:
>> Thanks for the reply Francesco, being late is no problem.
>> It's not really a big issue with the UI but I started thinking if we have
>> multiple plugins who all want real estate in the main layout then it could
>> get messy. Perhaps we can think of a menu just for the OOTB plugins and get
>> everyone who wants their plugin accepted into honeycomb to conform to a UI
>> However I am definitely not the UI guy which is why I included the addons
>> and distro groups in the conversation. You probably have a better idea than
>> me of how something like this could be achieved.
>> On 01/06/15 11:14, Francesco Corti wrote:
>> Hi Martin,
>> Sorry for the late reply but I was out for a couple of days.
>> It's the first time I hear about problem about the layout (the menu
>> item is very simple).
>> I'll work on it to understand and support for the solution.
>> I understand (and agree on) that the plugin should not have an impact
>> on the layout so I could suggest also different paths: why not a AAAR
>> dashlet instead of a menu item?
>> In any case I'm available for other solutions and integrations.
>> 2015-05-28 22:50 GMT+02:00 Martin Cosgrave <martin at ocretail.com>:
>>> Hi Francesco
>>> Just to let you know that Daren and I have evaluated your plugin for
>>> this release, and mostly due to the fact that it requires a separate
>>> server, and we want to get 1.0 out soon, we decided to push it to 1.1. No
>>> scheduled date for that yet. In fact we need to work out a generic way of
>>> getting services on other servers into the build, so we can support
>>> external solr as well as pentaho, but that's another story :-)
>>> Daren had a UI issue after adding AAAR, for him it is consistent between
>>> different installs, but I didn't see it myself, you can see here:
>>> One final thing, the AAAR menu is quite prominent in the top menu; if we
>>> are planning to incorporate many different 'best of breed' plugins in our
>>> honeycomb edition it will be important not to give undue screen real estate
>>> to any individual unless absolutely necessary. Would it be difficult for
>>> you to make that UI element optional?
>>> I hadn't really thought about the UI until this point but in fact we
>>> really need to tie all the honeycomb addons into a unified menu of some
>>> sort. If you have any thoughts on this let me know (basically needs to be
>>> extensible for new addons in a simple way).
>>> Just realised there are some themes here that could do with wider
>>> discussion so copying in ootb-distro@ and ootb-addons@
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OOTB-addons