From: "Jirka Tomasek" <jtomasek(a)redhat.com>
To: aeolus-devel(a)lists.fedorahosted.org
Sent: Friday, October 19, 2012 4:35:23 AM
Subject: Re: RFC: Portlets for Conductor
On 10/19/2012 10:18 AM, Jiří Stránský wrote:
> On 15.10.2012 16:33, Tzu-Mainn Chen wrote:
>>
https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Portlets
>>
>> Please send any feedback you may have!
>>
>> Thanks,
>> Tzu-Mainn Chen
>>
>
> Hi guys,
>
> I'd recommend looking at Cells [1] and thinking if we can use it to
> implement the portlets. It's a components/portlets implementation
> for
> Rails, has more than 1200 stars on GitHub [2], so I guess it's the
> Rails "standard" for doing these things (although I admit I never
> used
> component based approach for views in Rails). It might prevent us
> from
> reinventing the wheel and also keep the project community-friendly,
> as
> I think it's always better to go with "standard implementations",
> so
> that community contributors are not forced to learn Aeolus-specific
> solutions to standard problems.
>
> That said, I didn't look into this in detail, so I'm not sure
> whether
> Cells would fit for our use case. Just want to bring it up to your
> attention.
>
> Have a nice day
>
> J.
>
> [1]
http://cells.rubyforge.org/
> [2]
https://github.com/apotonick/cells
This looks like exactly what we need. Anyway we might still consider
whether a dashboard's controller (UsersController) can hold the
amount
of logic for portlets. It depends on the amount of portlets we want
to
use and logic necessary to generate data for them. If the amount is
overkill for UsersController, I see the Cells as great solution. Only
disadvantage I see is that it brings another gem dependency.
Jirka
Cells does look great, thanks for pointing it out! From what I understand, a cell could
represent a portlet or (in my grand vision) a portlet type; it's pretty arbitrary in
that sense.
Mainn