[consulting] New Premium Drupal Theme - ZincOut

[George]

hi jeff, to address your points,

i shouldn't have to turn js off to escape using something that css 
effectively do. using javascript for menus should be limited to 
dreamweaver in the late 90s. yes you can get a few fancy things using 
js, but css is going to be a heck of a lot faster, both performance-wise 
and script-weight-wise at the loss of a few minor differences.

yes, the demo site looks incredibly basic, and not fit to be a demo 
site. the front page is sparse, and hardly visually appealing. how 
difficult is it to knock a default site together with some random 
content and some blocks in a few places when the theme is already dev'd? 
not very. to make a theme stand out takes a lot longer than ten minutes 
i'm not disputing that, but i still stand by my ten minutes claim.

i'm not being harsh. opinionated yes. it was constructive criticism, 
justifying my reasons. of course i'm entitled to my opinions, and i hope 
fordrupal take them on board. yes i am looking to buy themes, but i 
listed the reasons why i wouldn't want to buy from them. fordrupal can 
either go humph, or take note.

just like you said you don't think they're not earth shattering, i 
actually gave the reasons why i don't think it is.

Jeff wrote:
> Did either of you actually turn Javascript off and reload the site?  
> I'd have thought it fairly common knowledge that Superfish menus  
> degrade without JS, relying on the semantic and validating <ul>  
> foundations of the underlying menu markup to do the work when only CSS  
> is available.
>
> George, if you can put together a site like the demo in 10 minutes or  
> so, please get in touch with me asap, we can make you rich :)
>
> I'm not saying this demo site or the theme are earth shattering and I  
> have no connection with fordrupal themes whatsoever (never heard of  
> them or their founders before), nor do I have the need to ever buy a  
> theme, but honestly George, it feels like you have other reasons for  
> being harsh on this.
>
> Anyway, of more interest to me is Brian's xhtml comment — is this a  
> server config issue? How do you know it's not sending it as  
> application/xhtml+xml? I thought the browser looked at the doctype in  
> the markup?
>
> "Future validation headaches" — are you refering to html 5? Isn't it  
> realistic to think that xhtml is going to be supported until half the  
> people on this list have retired, given the ongoing infestation of  
> Internet Explorer and its associated lack of speed of improvement? In  
> other words, isn't the web moving so slowly (because of IE and the  
> w3c) that xhtml is going to be around for many years yet? Drupal.org  
> and Garland are both xhtml.
>
> Jeff
>
>
> On 09/03/2009, at 11:46 PM, Brian Vuyk wrote:
>
>   
>> That is a fairly attractive theme visually. However, George makes some
>> good points about it w.r.t the JS menus.
>>
>> Why XHTML? Your server isn't sending the site as application/xhtml 
>> +xml,
>> so the user is getting none of the benefits of XHTML with all the  
>> future
>> validation headaches.
>>
>> Brian
>>     
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>