Forgot to mention Nikhil's book: Developing Microsoft ASP.NET Server Controls and Components. For those of you that don't know Nikhil wrote the ASP.NET data controls, was one of the principle dev leads for all of the ASP.NET controls, and is just a super star all around developer.

10:41:53 PM    comment []

I'm pretty much the most impatient person that I know. Some of my friends tell me that I'm the most impatient person that they know. The fact that I have to wait another 63 days to move into the new house is killing me.

I got the title and CC&Rs for the property. Nothing too scary.

I sent the sellers my list of requests from the inspection... however I haven't got a response yet. Actually I have until tomorrow for them to "receive" them... then they have 3 days to respond.

My agent went on vacation this week. He brought his laptop and cell phone with him. He also located the Windermere office at this vacation site so that he can keep up with the deal. Not sure I'd like to be in his family, but I like having him as an agent! :)

10:19:53 PM    comment []

John points out:

"That said, the challenges involved in building a "scalable API" are considerably greater than "let's not do MVC". One of the things that I hated about the way classic Windows controls operated was the fact that they held a copy of the data that they owned, rather than delegating ownership of that data to some (and almost always more appropriate) application data structure."

I agree - it's all about the balance... while you want to support cases where the developer keeps an optimized data store (like for a ListView, etc.), you want to continue to support the simple case where the dev pushes the data into the control (like text into a TextBox).

An example of this is the difference between the ListBox and DataGrid in WinForms. Even in the case of data binding we still ended up copying the string data into the ListBox because of the underlying control implementations, while the DataGrid never copies the data, just reads it from the bound source when render is required.

RichTextBox brings up an interesting question. Given the rich editing expierence for the RichTextBox, how could you provide a virtualized store? Perhaps a "ITextProvider" interface that could allow reading RTF from some user store? To make this even trickier, lets imagine the virtual store model for an HTML editor... Trident (sorry, codename for MSHTML which is the system component that does all the HTML rendering, parsing, etc, in Internet Explorer) handles the data and display - using the HTML elements as the model. This is needed for a rich editing experience. How could Trident provide the rich editing expierence with a virtualized store?  - unless you virtualize just on the HTML text (with that same "ITextProvider" model)...

... sorry, i'm rambling...

10:14:54 PM    comment []