in

dotnet.org.za

South African .NET Developer Portal

Adam Heunis tech talk

Software mostly, but other techie stuff as well. I primarily use Notepad, Visual Studio, the Command Prompt, XmlSpy, SQL Server, MySQL and Photoshop. I speak
C# (incl. OO), XML, XSL, ASP.NET, VB.NET, VB6, SQL, UML and XForms.

June 2005 - Posts

  • SharpDevelop: the open source solution for C# coders

    Anyone who reads this blog will know that I am a supporter of open source & open standards etc. In this light I'd like to mention SharpDevelop from the guys at ic#code. Once again my learned friend, Phil Armitage, first introduced me to SharpDevelop a couple of years ago.

    This is a very useful open-source IDE that you can use to code C# to your heart's content. It is very easy to use (has a similar feel to VS.NET) and does most things that VS.NET can do. In fact, I think Microsoft "lent" some of their ideas (XML Schema integration) for VS.NET '05 from SharpDevelop. It also integrates very well with nUnit, nAnt (and therefore CI in general). Obviously any code you write with SharpDevelop can be consumed by any .NET application.

    SharpDevelop's one big con is that it doesn't ccurrently support Web applications yet. Definitely worth a look. They also have some insightful videos on their wiki.

  • XForms: an "interface" for user input

    If you've read my blog, you might've noticed that I list XForms as one of my skills. A lot of visitors to this blog have enquired as to what XForms are. With this in mind, here is a brief explanation.

    In essence, XForms are XML driven forms. I know it sounds too simple, but this really is what all the fuss is about. To understand the benefits that XForms have over standard web forms you have to look at it in deeper detail though.

    Forms are an important part of many web applications today. Most of these forms are HTML based and until now they have been doing a good job. The XForms guys are trying to tell us that standard HTML is starting to struggle with complex transactions. I don't know that I agree fully with them on this, but I do say is that all web based (and indeed other) data gathering/user input systems share a lot of commonality.

    XForms is a well thought out (by the W3C with extensive consultation), extensible standard that can define the implementation of a data gathering/user input system. The system will still have to be implemented by the device that you are using but XForms define how it should be implemented in a standard way.

    I guess in C# terms you could almost say that it works in the same way that an interface would. In the same way that implementation is not part of an interface, implemantion is not part XForms. The implemantion is for the class/device. This means that any XForms compliant device can handle user input whether this is a web browser, a windows form, a telephone system, a mobile application, server-side, client-side or even HTML itself. Again note the similarity with OO interfaces.

    I got involved with XForms, through an indirect predecessor called ISML and I have built my own XForms renderer, but some big guns (Adobe, Mozilla, IBM etc) have now commited their massive weight behind their own renderers. Microsoft, rather predictably, are sofar touting their own Infopath as something similar, but there is a rumour that they have started taking XForms more seriously.

    To be brutally honest, I don't think XForms will be anything more than a good standard if Bill & His Boys don't come to the party. I also think that it is a good enough standard and has enough use for them to want to come to the party.

    My final thought: If your organisation requires a lot of user input and you have the standard maintainability issues, then watch this space. The support isn't quite there yet, but when it reaches critical mass I think this could become a very useful standard.

    See more at the W3C Xforms site.

Powered by Community Server (Commercial Edition), by Telligent Systems