Comments on: misty eyed http://archgfx.net/blog/2007/geek/blogging/misty-eyed Austin web designer - Adam Freetly Wed, 02 Nov 2011 09:47:44 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: adam http://archgfx.net/blog/2007/geek/blogging/misty-eyed/comment-page-1#comment-12605 adam Wed, 28 Feb 2007 20:11:01 +0000 http://archgfx.net/blog/2007/asides/misty-eyed#comment-12605 @ root- i think that's what matt's getting at. i like using asides, and that preference shouldn't predicate, or impinge upon, my design/aesthetic choices. @ tt- again, i think this is what matt's suggesting, despite it being contradicted by the majority of the themes installed here. the process of editting/installing/normalizing wp.com themes is supposed to bring them up to a baseline standard of functionality. most of the older themes don't meet this baseline, which is probably due to the limited number of staff focusing their efforts on new themes. @ root-
i think that’s what matt’s getting at. i like using asides, and that preference shouldn’t predicate, or impinge upon, my design/aesthetic choices.
@ tt-
again, i think this is what matt’s suggesting, despite it being contradicted by the majority of the themes installed here. the process of editting/installing/normalizing wp.com themes is supposed to bring them up to a baseline standard of functionality. most of the older themes don’t meet this baseline, which is probably due to the limited number of staff focusing their efforts on new themes.

]]> By: Root http://archgfx.net/blog/2007/geek/blogging/misty-eyed/comment-page-1#comment-12604 Root Wed, 28 Feb 2007 20:02:34 +0000 http://archgfx.net/blog/2007/asides/misty-eyed#comment-12604 I am not sure if asides are a *design* decision. More like a web construction choice. I am not sure if asides are a *design* decision. More like a web construction choice.

]]> By: timethief http://archgfx.net/blog/2007/geek/blogging/misty-eyed/comment-page-1#comment-12603 timethief Tue, 27 Feb 2007 03:58:37 +0000 http://archgfx.net/blog/2007/asides/misty-eyed#comment-12603 From my viewpoint if a theme doesn't function as I want it to then whatever its design may be - I'm not going to use it. That's why I don't understand what Matt said: <blockquote> Themes should be design decisions, not functionality decisions. </blockquote> Presumably Andy's bit of code will one day be added to all the themes and we'll have asides. I'm wondering if that event will follow or precede the event of equipping all themes with widgets. I immediately switched two of my blogs to the Misty Look theme. I now have contact pages and fonts of a readable size as well as a clean looking theme I can easily create headers for. YAY! :) From my viewpoint if a theme doesn’t function as I want it to then whatever its design may be – I’m not going to use it. That’s why I don’t understand what Matt said:

Themes should be design decisions, not functionality decisions.

Presumably Andy’s bit of code will one day be added to all the themes and we’ll have asides. I’m wondering if that event will follow or precede the event of equipping all themes with widgets.

I immediately switched two of my blogs to the Misty Look theme. I now have contact pages and fonts of a readable size as well as a clean looking theme I can easily create headers for. YAY! :)

]]> By: adam http://archgfx.net/blog/2007/geek/blogging/misty-eyed/comment-page-1#comment-12602 adam Mon, 26 Feb 2007 17:58:19 +0000 http://archgfx.net/blog/2007/asides/misty-eyed#comment-12602 there's a logistic headache i can't get my head all the way around. that means using your <code><ul></code> method for every theme then, since not all themes have styling for asides? or just adding the equivalent of andy's CSS to the code for every theme? i suppose in that light, sidebar asides would be <em>easier</em>. nonetheless, i have to agree about themes as design decisions. although i still think that the skins/mods distinction makes way more sense than including all that PHP for a design decision. there’s a logistic headache i can’t get my head all the way around. that means using your <ul> method for every theme then, since not all themes have styling for asides? or just adding the equivalent of andy’s CSS to the code for every theme?

i suppose in that light, sidebar asides would be easier.

nonetheless, i have to agree about themes as design decisions. although i still think that the skins/mods distinction makes way more sense than including all that PHP for a design decision.

]]> By: Matt http://archgfx.net/blog/2007/geek/blogging/misty-eyed/comment-page-1#comment-12601 Matt Mon, 26 Feb 2007 17:48:00 +0000 http://archgfx.net/blog/2007/asides/misty-eyed#comment-12601 Because introducing features like asides in only some of the themes is far more annoying. Themes should be design decisions, not functionality decisions. When/if we officially do asides, it'll be in all themes equally, and far easier than using a different interface for every single theme to configure it. Because introducing features like asides in only some of the themes is far more annoying. Themes should be design decisions, not functionality decisions. When/if we officially do asides, it’ll be in all themes equally, and far easier than using a different interface for every single theme to configure it.

]]>