Unfortunately, I have blogged very little in recent months. I shall follow this post with a summary of the things I've skipped blogging, but for now, I offer up the following tantalising screenshot by way of apology:
If you'd like to build the code from SVN in a few hours' time (it's not committed yet), or use my SUSE build service packages, I would certainly appreciate suggestions on how to make it more usable. However, I'll probably only focus on such tweaking when I have all the features done and stabilised.
HTML tags and attributes, based on the W3C schemas
System.Web ASP.NET controls (except special child controls), and their attributes
HTML Doctypes
This is very much a work in progress. I still need to improve the performance and error resilience of the parser and completion code, add completion cases for lots of little things such as ASP.NET directives, and finish the support for controls that aren't in System.Web.dll. I'd also like to make it possible to use the property grid, toolbox and document tree with the code view, and take a look at implementing some CSS coding features.
The designer mangles HTML badly, but is due for a rewrite in order to excise Mozilla composer (which does the mangling). Note that the designer isn't anywhere near finished, but I thought that code completion was more useful at this point, and in terms of the amount of work I put in, it gives a much better payoff :)
I'll have a look at svn when you commit.. I'm running ubuntu, do you have debs in your build service?
Do have a link to that.. I cant find it searching..
Code mangling is important maybe the most important.... nothing worse then seeing your nicely laid out HTML turn into unreadable code/markup soup.
I committed it, followed by completion for boolean, enum and colour property values :)
Sadly there are no debs; although the build service can generate them, I'd need spec files or whatever the deb equivalent is. You could try using 'alien'...
I agree that code mangling is nasty, which is one reason why I put the designer on hold. Composer returns ugly HTML4 no matter what you put in, so I decided that the best plan would be to use the WebKit HTML control as a kind of canvas that would modify the text file via editing interfaces on the ASP.NET parser. I intend to use the same interfaces for PropertyGrid-based tag editing. However, the designer is on hold while I wait for the GTK WebKit to be stabilised. Also, I feel that most other areas of MD offer much better payoff for the time that I can put into them. For these reasons, it's likely to be a while until you see the designer in a fully usable state.
Comments
Legand!!!
I have been waiting for this!!!!
Does it auto compelte attributes as well as values?
Lastly... does in mangle the html code when switching views.?
--- hoping to abandon my last ms app vs soon --
Testing
PS If you need any testing help email me
Feedback would be welcome
If you'd like to build the code from SVN in a few hours' time (it's not committed yet), or use my SUSE build service packages, I would certainly appreciate suggestions on how to make it more usable. However, I'll probably only focus on such tweaking when I have all the features done and stabilised.
It's not finished yet :)
So far it completes:
This is very much a work in progress. I still need to improve the performance and error resilience of the parser and completion code, add completion cases for lots of little things such as ASP.NET directives, and finish the support for controls that aren't in System.Web.dll. I'd also like to make it possible to use the property grid, toolbox and document tree with the code view, and take a look at implementing some CSS coding features.
The designer mangles HTML badly, but is due for a rewrite in order to excise Mozilla composer (which does the mangling). Note that the designer isn't anywhere near finished, but I thought that code completion was more useful at this point, and in terms of the amount of work I put in, it gives a much better payoff :)
Cool
I'll have a look at svn when you commit.. I'm running ubuntu, do you have debs in your build service?
Do have a link to that.. I cant find it searching..
Code mangling is important maybe the most important.... nothing worse then seeing your nicely laid out HTML turn into unreadable code/markup soup.
It's in
I committed it, followed by completion for boolean, enum and colour property values :)
Sadly there are no debs; although the build service can generate them, I'd need spec files or whatever the deb equivalent is. You could try using 'alien'...
I agree that code mangling is nasty, which is one reason why I put the designer on hold. Composer returns ugly HTML4 no matter what you put in, so I decided that the best plan would be to use the WebKit HTML control as a kind of canvas that would modify the text file via editing interfaces on the ASP.NET parser. I intend to use the same interfaces for PropertyGrid-based tag editing. However, the designer is on hold while I wait for the GTK WebKit to be stabilised. Also, I feel that most other areas of MD offer much better payoff for the time that I can put into them. For these reasons, it's likely to be a while until you see the designer in a fully usable state.