Wordpress Coders: Widget-ready?

The words "Smoking" and "Crack" come to mind. But that's not surprising from someone who suggest compromising code quality to accommodate.

Anyway, you've never coded a serious wordpress site if you think widgets will work anywhere.

I will further Blue Ires suspicions of 'Smoking' 'crack', as you cannot seem to spell widgets. They are completely different to widgits.

Originally Posted by Blue Ire The words "Smoking" and "Crack" come to mind. But that's not surprising from someone who suggest compromising code quality to accommodate. Anyway, you've never coded a serious wordpress site if you think widgets will work anywhere.

Immersion?

You missed the point. The guy I was replying to spelled widget wrong, that's what Immersion was talking about.

Originally Posted by Immersion I will further Blue Ires suspicions of 'Smoking' 'crack', as you cannot seem to spell widgets. They are completely different to widgits.

Was that last misspelling done on purpose?

Neither of those are misspellings! It is spelled WIDGET. Geez, people, pay attention!

I'm fairly new to WordPress coding and I can't say I've ever used "nested lists". I don't really see the need in them, but then, that's probably because I'm missing something?

What purpose do they serve?

Originally Posted by Blue Ire The words "Smoking" and "Crack" come to mind. But that's not surprising from someone who suggest compromising code quality to accommodate. Anyway, you've never coded a serious wordpress site if you think widgets will work anywhere.

Code quality? Where did you get the idea that I would sacrifice code quality. When I met compromising, I met compromising the design slightly in order to have a layout that is easier to change by the end user. Please do not get my wrong, I'm all for standards. Also, sorry for my misspelling of widget (I think).

Also, I never said widgets would work anywhere. However, you can use a combination of widgets and static dynamic content (When I refer to static, I'm refering to non-customizable dynamicly generated code....hopefully someone will get what I mean :S). The whole point of wordpress, in my opinion, and all other dynamic software is to keep things dynamic and modifiable by the user, without having programing knowledge. Also, you speak of "serious wordpress" themes. Frankly, if you are to the point where you can't use wigets at all, you should probably be looking into different software. Applications such as Drupal or CMS Made Simple would be much better choices than wordpress for more complex sites. I think it's silly to be using wordpress as a full-fledged CMS.

Finally, we really don't need people ranting over misspellings of a made up word :S

EDIT: .....I applogise. Wiget is a word, wigit is not. Because of a certain someone's post (sorry, really I just forgot your name), I thought I was spelling wiget wrong, and I thought it was suppose to be wigit.



EDIT3: Concerning Lists.
If, by code quality, you were referring to having your side bars be lists instead of lots of nice divs....I have to tell you that the person using divs instead of lists for the sidebar is technically the one who is sacrificing code quality. Using divs for the sidebar like some people do is not very good code. Also, you can change the way the sidebars are generated quite easily within your template (so if you did want to use divs instead of lists, you could....but you really shouldn't.).

Steven Fergus: The main reason behind using lists is because it keeps your code semantic. Screen readers will understand it better and you'll have that warm fuzy feeling in your heart because you wrote semantic and helped further "the cause". It can also help your markup make more sense.

If you still believe the words "smoking" and "crack" still pertain to me, please elaborate. Wordpress is not the ideal solution for all projects. ;-) Also, i'd appreciate some projects where you couldn't use wigets in any way to help the theme be more customizable. Special side bar items are no excuse with PHP wigets and the ability to simply make your own wigets. Also, multiple sidebars are no excuse, with the ability to have as many sidebars as you want, within reason. Also, projects that would be better suited for software such as Drupal, don't count either.

First off, until recently, Widgets (You still aren't spelling it correctly) were only recently introduced as more than aplugin to wordpress, therefore your argument that 'if you can't use widgets you should change CMS' is moot.

Beyond that, you pretty much have no idea what you are talking about. I can make this point no better than by showing a bit of the code from your main page...

Are you kidding me? The first six lines of your code contain 6 divs... ouch. And then after that you have a nav that isn't even a list, just a bunch of links in a div... speaking of accessibility.

Hah, take that!