I am planning to do a Spring Framework (.net, java)seminar at the new Finetix office. The general gist is that I would like to cover the .net and java implmentations and I would like this to be open to the public. I already spoke to the Spring.net folks and they will make a post when I have a date sorted out. I imagine I can get the original java based Spring folks to post as well. Anyhow – I was asked to put together a general overview – this post will cover my initial thoughts. I hope that I can comple one of the folks in the Finetix office (perhaps a particular collegue that spent the past serveral years @ sun) to do the Java portion of the chat – while I will do the .Net portion. Below are the .net relevant thoughts I have so far. If one of the other guys will not do the Java chat – I surely will do it.

1. Intro to Inversion of Control
1. compare and contrast vs service locator
2. The importance of seperating interface from implementation
3. Eliminating the need to pass references through classes that should not need to depend on them
2. Defering singleton-ness decisions from implementation – when you can – INTERFACE BASED SINGLETONS
3. How IoC relates to testability
1. Unit test framework (NUnit)
2. Mock framework (Rhino Mocks)
4. Spring general components overview
1. Core Container
1. object factory
2. initialization method
3. getting properties off of objects in spring
4. prototype vs singleton
2. AOP – basic intro
5. Setter vs Construction Injection
6. A demo of Spring for implementing a large strategy pattern implementation (.net based)
7. The need for service locator in UI applications, Windows Forms, Swing UIs
8. Touch on Copeland Ruby example IoC container, PicoContainer, MicroKernel/ Windsor, etc.

That is about it – anyone with thoughts – put em out there.

-Chris

You can leave a response, or trackback from your own site.

Aah – I spend so much time trying to make the Presentation Layer of my applications as ‘thin’ as possible – one might think that I believe it to be unimportant. Alas- I believe the opposite is true. While I think of myself as sort of an enterprise software guy – I think that end users CARE about the usability of their software. 9 times out of 10 – there are non-technical end users for my software. These people have some goals. They try to meet these goals by doing some tasks. The ability for the users to understand how to accomplish these tasks to meet their goals is what matters.
Since I tend to believe that the UI is actually very important for software applications – I tend to think about it a lot. I have spent lots of the time on the server – building web services. I have spent lots of time on the server building servlet like services. I have spent lots of time in databases. I have spent lots of time building web UIs. I have spent lots of time building Windows Desktop App UIs. I have had to build service daemons, agent like thingys, and all things in between. All of that said – end users care about their ability to get their goals met and about not being made to feel dumb.

I DO think that prototyping UIs is a good plan. I do think that making the UI as SIMPLE and CLEAR as possible is very important. I DO NOT think that putting zillions of rarely used features into UI applications is useful. I DO NOT think that this is at all ‘hard’ I just think it needs to be considered. Anyhow – here are a few decent links to read some tidbits about designing for usability. Much of this is ‘web geared’ but do not be thrown by that – it is all relevant in any UI environment.
Sites
welie.com
designinginterfaces.com
Yahoo! Patterns
asktog

Books
the design of everyday things
the inmates are running the asylum
user interface design for programmers

Enjoy!

Chris

You can leave a response, or trackback from your own site.