Since we’re in the process of breaking themes good and hard, how
attached are we to erb? I’ve been taking a cursory look at liquid[1]
and it’s got a hell of a lot going for it. And not just because of who
wrote it.
Has anyone used it? What do you think?
Or would it be safer to continue to support erb but offer the option
of liquid layouts. It shouldn’t be too hard to wrap things like the
the sidebar list and the textfilter chain in liquid plugins.
Piers C. wrote:
Not having to use Liquid is one of the main reasons I’m running Typo at
work instead of Mephisto. If you want to include support for Liquid,
that’s great, but I’d recommend doing it in a way that doesn’t lose the
ability to use ERb/rhtml templates.
–josh
On 8/22/06, Piers C. [email protected] wrote:
I’ve been wondering the same thing. I haven’t really looked at
Liquid’s performance, but I wouldn’t mind adding it as an option.
Scott
I definitely wouldn’t mind the liquid option. I’ve started using it
for a few shopify accounts and love how easy it is. Not that the
current theming method is difficult, liquid just seems all the easier.
Brandon J.
[email protected] writes:
the sidebar list and the textfilter chain in liquid plugins.
Not having to use Liquid is one of the main reasons I’m running Typo at
work instead of Mephisto.
What don’t you like about it?
If you want to include support for Liquid, that’s great, but I’d
recommend doing it in a way that doesn’t lose the ability to use
ERb/rhtml templates.
Yes, the more I think about it, the more I’m inclined to only do it if
it can be done in tandem with erb.
[email protected] a écrit :
Just thinking in term of having Typo spreading in the public, I think
erb / rhtml will be easier to understand by the public, and we need to
keep that solution if we want basic users to change their themes, don’t
we ?
More, I think we need a bit more markup in the views (mostly in the way
posts are displayed) to help web designers do their work, something like
the CSS Zengarden extra divs here and there.
I’ve been working on something like this lately, feeling stucked by the
current theming possibilities, and thinking about a “Typo CSSZengarden”
thing.
Cheers,
Frederic
–
Frédéric de Villamil
“Quand tu veux chasser une belle fille, il vaut mieux commencer par
draguer sa copine moche” – précepte de go.
http://t37.net http://fredericdevillamil.com
[email protected] tel: +33 (0)6 62 19 1337
Piers C. wrote:
[email protected] writes:
Not having to use Liquid is one of the main reasons I’m running Typo at
work instead of Mephisto.What don’t you like about it?
Mainly that it’s not ubiquitous. I don’t want to get locked in. Liquid
seems pretty nifty for supporting user-contributed layouts and
maintaining
security, but since I’m doing all the layouts myself I don’t need to
worry
about that.
–josh
On 8/22/06, Frederic de Villamil [email protected] wrote:
about that.
I’ve been working on something like this lately, feeling stucked by the
current theming possibilities, and thinking about a “Typo CSSZengarden”
thing.
I’ve resisted small HTML tweaks in the past, even if they improved the
usability of our HTML, just because it wasn’t worth forcing a zillion
themes to make minor changes.
Since we’re breaking everything for 4.1 anyway, this would be a
great time to make structural improvements. Perhaps we could even
go as far as to (gasp) standardize on a specific HTML structure, like
hAtom, so we’re able to share CSS themes with other software.
Also, one of us needs to do the (small) amount of work needed to move
Typo themes into vendor/plugins, just so we can use Rails
plugin-management tools to install themes. I can take care of this
later this week, unless Piers really wants to do it :-).
Scott
“Scott L.” [email protected] writes:
Since we’re breaking everything for 4.1 anyway, this would be a
great time to make structural improvements. Perhaps we could even
go as far as to (gasp) standardize on a specific HTML structure, like
hAtom, so we’re able to share CSS themes with other software.Also, one of us needs to do the (small) amount of work needed to move
Typo themes into vendor/plugins, just so we can use Rails
plugin-management tools to install themes. I can take care of this
later this week, unless Piers really wants to do it :-).
Nope, I’m off on holiday on Thursday. I’m taking a laptop and I’ll be
able to check mail, but if I find myself spending time monkeying with
typo themes.
While we’re about it btw, it would be neat if we could add generators
for themes and textfilters. Moving associated tests into the plugin
directory wouldn’t suck either.
I’m having bad thoughts about adding pluggability to the admin
interface as well, but that’s probably (at least) 4.2.
On 8/22/06, Piers C. [email protected] wrote:
Nope, I’m off on holiday on Thursday. I’m taking a laptop and I’ll be
able to check mail, but if I find myself spending time monkeying with
typo themes.While we’re about it btw, it would be neat if we could add generators
for themes and textfilters. Moving associated tests into the plugin
directory wouldn’t suck either.I’m having bad thoughts about adding pluggability to the admin
interface as well, but that’s probably (at least) 4.2.
Okay. I’ll see what I can do.
Scott
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs