N.B. The CSS in the current version of Insoshi doesn't use Blueprint anymore. The architectural principles are similar, though, so Blueprint is still worth studying.
Michael On Fri, Apr 25, 2008 at 12:35 PM, Ziad Hussain <[EMAIL PROTECTED]> wrote: > > Nikos, > > I can help you a bit understanding the way the design is set up with > insoshi. I think you'll actually find it pretty graceful. > > Its important to understand blueprint when working with insoshi. Its > actually a css framework, not just 3 arbitrary css files. > > Before you do anything with design in insoshi spend 15 minutes here > learning about blueprint. > http://code.google.com/p/blueprintcss/ > > > > > On Apr 25, 2008, at 1:30 PM, Michael Hartl wrote: > > > > > I hate templating languages, too, and will do my utmost to keep them > > out of Insoshi. (Mephisto lost me by using Liquid templates. Remind > > me again why I just spent two years becoming an ERb expert?) But if > > we're talking vanilla CSS, that's a better possibility. > > > > In any case, thanks for the feedback. These are the early days at > > Insoshi, and we'd like to get this stuff right from the start. > > > > Michael > > > > > > On Fri, Apr 25, 2008 at 11:22 AM, Timothy Johnson > > <[EMAIL PROTECTED]> wrote: > >> > >> Please don't clutter up the current code by adding what has come > >> to be > >> known as "skinning" by many other CMSes and OS apps. Anyone with > >> minor > >> Rails experience can get into the code and muck around with CSS and > >> layouts and views to their hearts content. It so bothers me to > >> see an > >> otherwise approachable project derailed (sigh) by adding in some > >> templating language or other such abstraction. ERB is very > >> approachable to even non-Ruby programmers. > >> > >> > >> > >> On Apr 25, 1:55 pm, "Michael Hartl" <[EMAIL PROTECTED]> wrote: > >>> We don't have concrete plans for skinning yet, but it has always > >>> been > >>> on the cards. Now that the HTML structure has stabilized a bit, > >>> we'd > >>> be happy to hear your ideas. > >>> > >>> We would like to keep the CSS partitioning scheme. I'm not sure if > >>> it's better to make skins using drop-in replacements or using an > >>> 'overrides' file, but both are worth investigating. > >>> > >>> Michael > >>> > >> > >> > >>> On Fri, Apr 25, 2008 at 5:39 AM, Ehlo <[EMAIL PROTECTED]> wrote: > >>> > >>>> Hi Nikos, > >>>> To be honest I think that the 3 file (actually 2 + 1 for the > >>>> reset) is > >>>> quiet smartly done. > >>>> It's basically split the typo stuff from the rest. > >>>> However this is only my humble opinion. > >>> > >>>> Michael, what do think about this ? Is already something planed > >>>> for > >>>> the future about themes/skins ? > >>> > >>>> Cheers, > >>> > >>>> E > >>> > >> > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Insoshi" 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/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
