I am going to stray off topic here because I think every post in this thread already has. First, I find it almost offensive that anyone feels each post has to end with some compliment to the Core Team. I don't think any one of us feel like that at all, I can say we are not big fans of getting 'slammed' though so as long as the post doesn't indirectly say F the Core Team I think we are all good without requiring praise (and indirectly saying F the Core Team isn't abolished with praise either!).

I will admit I am personally tired of anyone assuming what myself or any of the other Core Teamers are thinking. I understand you cannot help how you feel about whomever, but "Well I got the feeling that sometimes people on the core team are happy with the way things are, and are not looking into making these changes." is completely off base. What you need to do as a member of this community is understand there are many more things going on besides what you consider the top priority.

For once instead of everyone debating why the Core Team does or does not do something why don't we proceed in a manner more consistant with other open source projects: Someone work out a complete solution and submit this to someone who can do something with it. I want to emphasize that feedback is important from the community. I am saying this to trond.rud with no disrespect intended: You have questioned many things here and presented a valid area which needs improvement but so far you have offered nothing of substance to resolve the issue.

A final note, I am not saying it is not important to be XHTML compliant. I believe people should be able to use tabless or tabled designs, I personally have no preference for one or the other and have worked with both. I do think in terms of priorities, this is something I would consider to be lower on my list of must haves for the DotNetNuke framework.

---

Chris Paterra

Get direct answers to your questions in the Community Exchange.

Great turning of this. Lets lay it all down
Well my point was to get a debate on how to get a valid output code.
And now we are talking. Good.

As I stated on the asp.net site, I have read posts that dates more then two years back about people rquesting valid xhtml output. And little have changed before OBrien. I never get tired of mentioning him. Well to be serious, I have asked people to make a team that will try to work with changing this. The respons was low, except from dear nina. So I put that thought to rest for now.

I will be the first one saying assumption is the mother of all fxxk ups. Of course I do not know how the core team thinks, and that was out of line. Sry. Do remember that I do not have english as my first laguage, so if my words sounds strange, just ask for me to clear it for you, and I will. Surely I have not intended any disrespect to anyone, and not the coreteam in particular. This could be that when I am writing here, I actually translate from my mother tongue in my head into english as I type.

But this does not change the fact that the xhtml issue have been raised for more the two years ago, and we are still not there. Sure, I am new, but I have spend hours and hours reading on the asp.net forum trying to learn the most about the framework. And I will be waiting in line to join a team that will get some work done on this erea. Surely it is doable. I have yet to take the code as a whole into pieces, so I do not know where all the cjanges need to go, but that was why I tried to get people to join forces in the first place.

Well I am off skiing and drinking beers. Easter for me.

Cu all in  week, or sooner if I find wireless where we are going.

Good news on the 2GB, my portal is currently 'broken' none of the drop down boxes work for selecting / uploading files with the admin settings / modules etc. - I will look forward to that.

Education is the key here, mainly for module developers.

If you take a look at Tims tutorial I mentioned earlier it will give you an outline of what is involved, but to talk you through it:

1st is getting DotNetNuke to produce valid code within the default.aspx file - this is not hard, just closing tags, lowercase etc.
There is one core code change that needs to be made so that the <link> tag in the default.aspx file is produced in lowercase & that is it - no breaking changes.

The next step is to create a skin that is completely XHTML compliant, this is easy, again just lowercase tags and close all tags.- This is possible whether your skin is tables or CSS.

The final step is adding a module to the page and then seeing what it has added codewise to the page. - Usually this again just involves changing uppercase to lowercase and closing tags. - You may also need to change any <span> tags to <div> tags.(This is the only change you have to make to the Text/HTML module to make it compliant)

There is a further tweak that I discovered that isn't mentioned in Tims tutorial and that's the code that is added when you select 'Do Not Display Container' when this is selected DNN places <span> tags, these need to be replaced with <div> tags through an edit in the core code. - These changes should not break peoples installations.

If the module creates any html code through a .dll and it's not XHTML compliant - such as the dotnetnuke.dll creates the <link> tags in the default.aspx file, then you will need to edit the core code of the module, but in most cases it's just a matter of editing the .ascx files and no asp.net code needs to be touched.

Another element to consider for the modules is to remove the styling of the table from the table and put it in a module css file as certain module stylings will get pulled up as invalid code, again this shouldn't be too hard a task.

I am not talking about changing table based modules to CSS based modules, we are just talking about getting the modules using XHTML compliant code.

So, there is no problem with the skinning engine, it just requires a tiny tweak in the dnn core code and then its a tweak for each of the modules. Generally it's not that hard, it's just time consuming and there shouldn't be any breaking changes. - If you know of any let me know.

Does this make it clearer as to what is generally involved?

Thanks,

---

Lee Sykes - DNN Creative Magazine - 600+ Video Tutorials, Articles, Interviews - July Issue 58 out now!


Twitter: www.twitter.com/DNNCreative