On 19.12.2008, at 9:35, Alx wrote:

> Or should we create a sub-group to start reviewing
> design and implement some ideas in merb-admin?


My suggestion would be to use this list and lay out ideas you have  
first.
I think a whole lot of other work needs to be done first:

1. Django signals like event bus (there is no other way to loosely  
couple different plugins)
2. How to approach multiple ORMs out there
3. How to approach multiple JavaScript libraries.

2 & 3 can be solved by providing one gem that assumes one ORM and one  
JavaScript library, but I hope there is a better way

For exactly these reasons calling this sort of thing merb-admin is a  
bad idea to me: is it merb_dm_jquery_admin or would you support at  
least 2 options?

MK


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to