I'm now using zxaf for a project, it's tried and testing code just repackaged slightly so it makes a lot of sense. What doesn't make sense though is the directory structure that the current version has. The reason being because it really doesn't lend itself to being part of a larger system, or more importantly part of a composite system.

This has now been resolved with the new views that arrived in r11; however I'm keeping the page because it is a good indicated of middle aged code spread

Currently we have the view-main module; however we have developed into a situation where there are two different methods for presenting form and or table view (for display and/or edit).

On a page where there are lots of views but all from the same entity there is an interesting challenge when an individual item is updated within a view. Normally this is catered for during a full postback simply because the entire page is recreated dynamically, so it is enough that the post is processed during the construct phase.

However this isn't true when we are using an ajax update to modify an item.

Exploring the difficulties of taking over an entire system, usually undocumented (see footnote) and understanding it.

A matter of opinion...

A tranquil haven away from the hustle and bustle of pressured modern life, development is performed in a small stone room in the corner. The only fortifications are the firewalls, and the stone walls, just enough to think creatively. Here I ponder the intracacies of coding, sometimes complex distributed systems, othertimes the more mundane, and in my spare time the personal coding and pet projects. The site isn't not meant to be definitive, but hopefully it is informative, however if you don't find it useful I will understand the mouse pointer veering towards the back button.It's that simple.

About Me

About me
I've been developing software (or programming as we used to call it) since 1982, in the rough order: Basic -> 6502 assembler -> APL -> Pascal -> C -> C++ , and ending up with Java, C# and PHP. The last three are my preferred languages, the choice depends on the requirements of any given task. Add in database design and the ability to write efficient SQL.

Site Mission Statement

Apparently, according to management consultants, its important to have a Mission Statement, so here it is.

This site is primarily my place to keep track of ideas and concepts, the journal is there for the same reason, it tracks my thoughts and rather like a diary or one of those reassuringly navy blue Engineering Notebooks that we were given at certain companies to fill in with all our thoughts and then leave behind as an eternal record for whoever followed.

Disclaimer

I'm probably not as clever as I'd like to think I am, so so don't expect everything to work
the trouble with developers is that it's always in a state of development

Rules of thumb

1. "any given completed project will take no less than three months full time (500hrs)".
2. Don't change anything without a compelling reason "If it isn't broken it doesn't need fixing"
3. "HTML for content, CSS for layout".
4. "You don't need to write a framework"
5. "You do need version control from day one"
6. "You haven't just found a bug in the compiler"