I've got a funny feeling I'm doing too much for the assignment. I haven't even started on the actual assignment yet, I've just written a generic MVC framework to speed up client-side development. The thing is, the framework is now getting to the point where it's a project in itself (and it'll probably come in useful at some future point, so that's not a bad thing).
How much effort have other people put into their frameworks for their assignment?
Steve Chaloner<br />-----------<br />SCJP 1.4<br />SCWCD 1.4
Zip. My experience has taught me to put very little time upfront in building a framework for a custom application. The most successful projects I've worked on have developed the framework side-by-side the application at the same time, for reasons of requiring less coding. Most importantly not to think about reusing the framework in the future for some as yet unspecified requirements. Deviating from these guidelines almost always resulted in either wasted time and/or a framework that was more of a hiderance then help, with a redesign difficult.
the framework is now getting to the point where it's a project in itself
I would not think about making a framework for the client GUI. In general, I would stick with a minimal implementation and not over-engineer it. This is a one-time application, there is no appreciation for a framework. Rather, you may lose points if the code is considered to be too complicated, hard to understand and maintain, under-documented, etc.
SCJD 1.4<br />SCWCD
Joined: Jan 07, 2005
The framework itself is a fairly simple MVC job that uses attributes. It's not so hard to understand, and for the actual client implementation it results in views such as:
instead of the usual gui-intensive code.
(the formatting is not mine )
[ January 23, 2005: Message edited by: Steve Chaloner ]
[Andrew: Put code inside UBB code blocks] [ January 23, 2005: Message edited by: Andrew Monkhouse ]