On Oct 15, 2009, at 8:22 AM, atmorell wrote:

>
> Hello,
>
> I have a created a userdriven gallery with Ruby on Rails.The site is
> using a few plugins to create friendly links, permissions, pageless
> pagniation etc. The application controllers and views has gotton quite
> complex and I find it difficult and very time consuming to work with.
> So I thought about rebuilding the app with hobo, as it includes all
> the user and permission logics and another template system. However I
> am affraid that I will be to limited, or maybe not win anything
> becasue I will loss a lot of time hacking hobo.
>
> I am planning to add frinedships and personal messing to my website.
> Could this be to compelx for hobo? The messaging plugin I am looking
> at is ezm http://github.com/gravis/restful_ezm How would you implement
> such a feature in hobo - if possible.
>


If you actually dig around in restfule_ezm, there's not much actually  
*there* in terms of complex code. I'd recommend just trying to  
implement the same ideas in Hobo, and not worrying about using the  
plugin. If you're 100% set on the plugin, take a look at 
http://github.com/al2o3cr/restful_ezm 
  (shameless plug - my fork) I've got an instance of that running in  
production right now (not on a Hobo site) and it seems to work fine.  
At some point, it will probably turn into a Hobo plugin, along with  
the code I've got to gateway messages to/from email into the system.

But really, you're better off just rolling your own, as the views that  
EZM generates will need work to behave with Hobo anyways (they expect  
to be wrapped in a vanilla Rails layout, etc.)

--Matt Jones



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Hobo 
Users" 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/hobousers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to