There is a lot of change happening at the moment in my personal life, this is mainly due to the fact that Beverley's Mums health is deteriorating, which has a knock on effect on our life.
What is true in life is also true for Web-D-Zine( WDZ ). This is why the most important part of a project is the planning stage. Although I know this to be true, it can be difficult, especially as I am a bottom up designer. For me, there is nothing more enjoyable than playing about in the dirt, which for a programmer means playing around in the code. The concept of people actually paying for my work, is difficult. Yes, that was always the goal but actually implementing it, is proving hard. The main reason for this is because I am having to add tables retrospectively, which has a knock on effect on WDZ.
- Base class - Adding extra fields to the table means that you have to regenerate the base class. With WDZ this takes minutes, so is really quick to do and because the base class is separate from the user class usually has no impact on the code.
- Indexes - If you change an index type, then an affect is created. For example, if you have an unique index then fetch is used to retrieve data and the result is just one object, but if the index is a key, then fetchAll is used to retrieve the data and an array of data is returned.
- User Class - No change to the active code is produced, but you might want to update the main comment, to reflect the change in the underlying data structure
- Panels - If you add a new connection to another table, then the function editItem is changed along with additional code being added to the panel class
- Forms - New fields are added to or deleted from the forms, so these need to be dealt with.
- Lists - New fields are added to or deleted from the list displays, so these need to be dealt with.
