On Mon, Aug 2, 2010 at 9:14 AM, Case <[email protected]> wrote: > Hello Alex, > > I am also a new user to Hobo, and I'm trying to figure out more or > less the same things. > > I know that you can extend the basic tags that were created with hobo > generators using application.dryml. > In addition, you can extend or replace css code, by also placing > overriding code in application.css. > > But still, extending the default pages becomes very time-consuming if > you want to radically update the whole site template. I mean, why > extend the predefined page format (that resembles a blog) when > normally (ex. in vanilla rails) you would just define the layout of > your page? Why override the default css when you can just import the > one you want? I presume this 'extending' process is consuming server > resources, and slowing things down a bit.
To be honest, I typically *redefine* the page tag in application.dryml rather than extending it, especially when I'm working from an existing static HTML layout. Basically, you'd start with a static page then mix in all the dynamic bits. You'll probably want to refer to the standard page tag definition (in the hobo gem) to make sure you're not missing important bits. To Alex's jQuery issue: hobo_jquery makes it easy to use both, but you may run into trouble if you *totally* remove Prototype as I believe parts of Rapid still use it (most likely the part mechanism). --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.
