little progress, lots of probs
the good news first. the parser can extract the comment text from the html source file. the HTMLSite class is able to determine, if the html contains editable comments. this is important for later implementation of the edit function. with this i can quickly decide if an edit button es required or not.
ok, after that i would start with the forms and then the problems came :-(
the actual problems:
- the links in the html source point to the wrong destination. but this can i fix. it has two possibilities to do that. first, i correct all the links with the parser. second, i intercept the every http request and rewrite the url if needed. but, how can i intercept the request? do i need a http module or a http handler for that? do you have any experiences with these? is that a good idea?
- the request interception do i need specially for the links which are defined in the generated documentation. because i can't define any events on these.
- i can show the html documentation in the browser. but it has some drawbacks with the masterpage. the documentation will be placed above all masterpage definition even if i define the control which shows the html text below the masterpage definition. do you have any hints or solutions?

1 Comments:
Why are the links pointing to the wrong location? Can you explain?
In any case I think it's better practice to replace them when you parse and create the web page.
Interception could be done using the Server.Transfer method. This will redirect the request to a page without going back to the client.
I don't know about the Masterpage problem. Remy is the master on this.
Post a Comment
<< Home