April 2004 - Posts
You all know and love (I hope) intellisense, and so does the Java developers. It's already became a crucial part of any respected IDE.
One of the best things in VS.NET intellisense is its rapidness. The moment you type “.”, you get the members list. This way one can type a whole line of code simply by typing “.” and TAB's. Sounds trivial, isn't it?
Well, not always. In the Java IDE's I know (WSAD and WebLogic Workshop), there is a small delay after typing “.” and before the list appears. Something like half a second. This does not sounds too much, but it's really annoying. When one is in a “coding trance”, then one does not want to wait for the IDE to help him.
IMHO, it is better to omit the intellisense than to make it in a way that delays the developer.
This is really strange.
When I look for “asp.net” in google, I get back only one (!!) result: ww.asp.net.
When I look for “vb.net” in google, I also get only one site, which has nothing to do with vb.net.
Of course, when I look for “asp net” or “vb net” I get tens of millions of results.
I think it's time someone in google will hanlde the period thingy.
I guess this issue was talked over and over, but I fell onto it from a different point of view.
I was planning our company .NET framework the other day, and I came up with an architecture that coupled a UI Page and a BL Handler via a simple interface (a bit of an MVC, but not exactly). After the base classes were ready for action, I looked for a good way of checking whether the BL were really a stand alone components as planned. The trivial solution was to create a stub class that would call the various methods in the handler, and see whether it got any unexpected exceptions. However, while thinking of it, I figured other way of doing it, and by the way adding a very nice feature to the framework. Each page now has a switch which indicates how the business logic should be performed - server side (which is the normal way of doing it) or client side. The client side option means that the logic still occurs in the server, but it's called by the web service behavior, using the very same handler. This gives a much improved user experience - a “flicker free” application, much better response time, and more.
Of course, this solution can't be implemented on all the pages, but most of them can do it.
And the best part - the web service that calls the handlers, has only 5 lines of code!