Making FlexWiki XHTML-compliant is a pretty big task and one that I've
thought about doing for quite some time, but shied away from because I
didn't want to do half a job and not have time to finish it. On second
thoughts, though, even if we only get half way there, it's still a very good
start.
I had actually made some personal notes about future possibilities for the
Web application that included XHTML compliance, but hadn't got round to
posting them yet :o) To avoid muddying the waters, I'll come back to these
ideas when John's implementation is complete :o)
>From what I recall, one of the biggest barriers to becoming XHTML compliant
was the rendered output that the Formatter class produces. Have you
addressed that side of things, too?
The changes that you have discussed so far all seem to be very sensible and,
if nothing else, will give us a neater Web application that performs a
little better, too :o)
I haven't had chance to look at any great depth at the markup that you've
used to generate your XHTML-compliant pages, but the Thierry Koblentz [1]
and Alessandro Fulciniti [2] (among others) have done some amazing work to
create incredibly flexible markup that supports a wide range of styled
layout options. Full height columns can easily be achieved in XHTML layouts
by using "faux columns" (links to relevant articles are provided in [1] and
[2]).
The "tricky" part remains in providing a layout that is flexible enough to
cope with the configurable borders solution that FlexWiki provides, but I'm
sure you're looking at that, too ;o)
As for testing ... I'm no expert in this field so I can't really comment.
The "Browser Verification Tests" engine that David built did provide some
mileage for a while, but I'm not even sure if that works or not any
more. We're not doing much to test the Web application at the moment (I
believe), so as longs as the formatting tests pass, then we're still
providing the same level of testing at least. Obviously, I'd like to see
more testing being applied to the browser output, but we need someone with
more experience, or the time to try out solutions, before we can make much
headway there I think.
I'm keen to see these changes implemented as soon as possible, so if you
need any help, just let me know.
Derek
[1] http://tjkdesign.com/articles/one_html_markup_many_css_layouts.asp
[2] http://blog.html.it/layoutgala/
On 8/4/07, John Davidson <[EMAIL PROTECTED]> wrote:
>
> I have got the default.aspx page written so that it now uses XHTML 1.0
> transitional. In doing this I have some proposed changes to the way
> Flexwiki layout is managed. I have started a page at FlexWiki for
> discussion of what this layout is and does.
>
> http://www.flexwiki.com/default.aspx/FlexWiki/XhtmlLayout.html
>
> I would really like to get Derek's input, but all others are more than
> welcome to comment as this may break something I have not considered.
> I do hope it will enable more flexibility especially with the
> ContainerPresentation by Derek.
>
> Samples of the layout (without a top or bottom border can be viewed at
> the links below):
>
> http://ods.dyndns.org/FlexWiki/default.aspx/OdsWiki/OdsLinks.html
>
>
> http://ods.dyndns.org/FlexWiki/default.aspx/OdsWiki/FormattingRulesContinuous1.html
>
> I have changed the default.aspx.cs so that it uses StringBuilder and a
> single Response.Write, rather than hundreds of Response.Write
> statements. Also the supporting javascript files have been extracted
> into 3 now js files. This leaves just 3 small js functions that are
> created inside the default.aspx.cs code. In doing so the default.aspx
> page became a single line of code holding just the Page directive
> code.
>
> I took the menu js out of formatter.cs, but have not touched the rest
> of formatter.cs yet. It looks like it could also benefit from
> StingBuilder.
>
> Generally the improvement in throughput on my server averages about
> 25% with 1000ms savings on each page.
>
> None of the remaining pages will require a great deal of effort to
> convert.
>
> The problem of testing these changes remains. Has anyone had any
> ASP.NET 2.0 experience with NUnitASP 2.0? I was using it until it
> broke when VS 2005 was released, but now they claim it will work
> correctly, at least for the aspx.cs code functions.
>
> John Davidson
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Flexwiki-users mailing list
> Flexwiki-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
