Event "Facebook like"

["Aurélio A. Heckert"]

Wait... no_design_blocks may be a good idea sometimes, but must not be 
by default. Event as a content needs to interact and respect the defined 
aside content.

On 27-04-2014 13:59, Bráulio Bhavamitra wrote:
> Thinking on the user, as I think you are doing, I would remove the
> sideblocks to make an UI focused on the event. Use the
> no_design_blocks directive for that. Or you may hide some blocks from
> the profile and put a
> special block on this event page.
>
> To make it a plugin, run a migration like this:
> def self.up
>    environments = Set.new
>    Event.for_each do |event|
>      EventsPlugin::Event.create! event.attributes
>
>      environments << event.environment
>    end
>
>    system 'script/noosfero-plugins enable events' if Event.count > 0
>    environments.each{ |e| e.enabled_plugins << 'EventsPlugin'; e.send
> :update_without_callbacks }
>
>    Event.destroy_all
> end
>
> On Sun, Apr 27, 2014 at 10:28 AM, Matheus Sousa Faria
> <matheus.sousa.faria em gmail.com> wrote:
>> So, the idea is to inherite from folder, but keep the interface like a
>> community? Or do you have any other ideas for the interface?
>>
>> Soon my team and I are going to start working in this new plugin, during
>> this I'll bring the news and we can discuss if is going to turn to be a core
>> feature or not.
>>
>>
>> 2014-04-25 20:15 GMT-03:00 "Aurélio A. Heckert" <aurelio em colivre.coop.br>:
>>> Hi Matheus,
>>>
>>> To improve the events feature is a nice idea, but build a new profile to
>>> this thing looks odd...
>>>
>>> The event is something done by some organization, so, the organization
>>> must to be the profile container of a event.
>>>
>>> Well... that is the logic, and i believe we must to enforce it, but we
>>> have the fisl using a whole profile for an event. The debate is open, but a
>>> "event profile" will promote the creation of (non-)profiles with validation
>>> term, in place of content (its real nature).
>>>
>>> Braulio proposal is good. Make a event inheriting from folder will allow
>>> you to organize the event specific content. I and Valéssio also planed to
>>> allow sub-events to detail a big event, like fisl, for instance:
>>>
>>> Event "FISL15"
>>>
>>> Sub-event "Day 1"
>>>
>>> Sub-event "Encontro Comunitário do Noosfero"
>>> Sub-event "Ruby on Rails 5,6,...,999"
>>>
>>> Sub-event "Day 2"
>>>
>>> Sub-event ...
>>>
>>> This usage will allow us to build a event grid, as fisl does today with
>>> another tool.
>>> Obviously sub-events must to respect the parent event period.
>>>
>>> So, you propose some fields:
>>>
>>> Name
>>> Start Date
>>> End Date
>>> Address
>>> Description
>>> Participants (list of users)
>>>
>>> The only new field is the "Participants". Ok! That may come from "I'll
>>> Go!" button, and that may be filled by any guest with an e-mail (open as the
>>> comments) (if allowed by the author). What you think?
>>>
>>>
>>> And we thought that the event could have an apperance like a Community,
>>> where the "Join"  button would be something like "I'll Go!", and "Leave" be
>>> "Nah, maybe next time."
>>>
>>> Not exactly like a Community... inside it! :-)
>>> I LOVE this button labels! |-D
>>>
>>>
>>> Other ideas that appeared in our brainstorm:
>>>
>>> New button of "Manage my Events" in Control Panel
>>> List of Inviteds
>>> Events Block
>>>
>>> Yeah, Yeah, YEAH!!!
>>>
>>> May you want to review proposals not done on this AI:
>>> http://noosfero.org/Development/ActionItem2587
>>> And this list:
>>> http://noosfero.org/Development/Agenda
>>>
>>> Hasta!
>>>   Aurium
>>>
>>> _______________________________________________
>>> Noosfero-dev mailing list
>>> Noosfero-dev em listas.softwarelivre.org
>>> http://listas.softwarelivre.org/cgi-bin/mailman/listinfo/noosfero-dev
>>>
>>
>>
>> --
>> Matheus de Sousa Faria
>>
>> _______________________________________________
>> Noosfero-dev mailing list
>> Noosfero-dev em listas.softwarelivre.org
>> http://listas.softwarelivre.org/cgi-bin/mailman/listinfo/noosfero-dev
>>
>
>