Hi Alex, El 25/08/13 06:29, Alex Z escribió: > Dear Hobo Users, > > I've been looking at Hobo for a little while now and I really like what > I see, so far. I think it has a lot of potential, but certain parts of > it seem quite inflexible/brittle to me. I would really appreciate some > feedback on a few questions I presently have: > > 1. In general, are the Hobo enhancements to Rails more advantageous for > developing numerous sites, a single large site, or both? (Please explain > your reasoning)
I think they are more advantageous when developing numerous sites. If you have one designer, one frontend developer, two programmers and a year to develop one application you are probably going to customise everything that you are not going to feel so much difference with a Rails vanilla app. Having said this, I've worked in big projects with and without Hobo. And I usually miss Hobo when it's not available, specially Dryml and all the prebuilt widgets. > > 2. Can you list/explain all of the major advantages and disadvantages of > using DRYML over, say, haml on: > > a) numerous similar projects Reuse lots of tags very easily. > > b) a single large ongoing projec. Make use of the prebuild UI widgets while being able to customise them. The Ajax partial system is a lot of fun too. And remember, if it gets in the way you can always use "tradicional" Rails xhr requests. > > 3. The Hobo documentation states that themes are easily developed, but > to me it looks quite tedious to get, say, bootstrap 3, or foundation 4, > working properly with Hobo and Rapid. Is my assumption incorrect? If so, > can you explain why? Hobo themes are designed to cope with the all the possible widgets in Hobo. This is why cloning hobo bootstrap (https://github.com/Hobo/hobo_bootstrap) to create your own theme looks hard. I think the docs should say more clearly that you don't need to create a theme from scratch to style your app. Just edit the application.css and js files and add the files you need. You'll probably need to tweak some classes in the Dryml but that should be really fast. I think a good example of what I just described would be very welcome in the docs :). > > 4. Is it possible to modify the default auto-generation capabilities of > Hobo to auto-generate user specified types of views in response to new > models and controllers? I don't know an easy way of doing this without forking Hobo. What I usually do is rewriting the default show-page/edit-page/etc in the app/views/taglibs directory. For example: https://github.com/Hobo/hobo_bootstrap/blob/master/taglibs/edit_page.dryml > > 5. Are there any other important Hobo limitations and advantages any > experienced Hobo developers can bring to light? (excluding those > addressed in the online documentation) I can't think of anything else. > > I apologise if my questions seem very noobish - I've dabbled in various > languages and frameworks, but I'm, unfortunately, very far from an > expert! :) > > Thanks in advance for any help or guidance you can provide. You are welcome ;) > > Kindest regards, > > Alex Z > > -- > You received this message because you are subscribed to the Google > Groups "Hobo Users" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/hobousers. > For more options, visit https://groups.google.com/groups/opt_out. -- Ignacio Huerta Arteche http://www.ihuerta.net Teléfono: 0034 645 70 77 35 Email realizado con software libre -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/hobousers. For more options, visit https://groups.google.com/groups/opt_out.
