D5 – D2009 porting project update

The project has been put on hold for now. We got stuck early in January when we couldn’t get past a deeply entrenched component from a third party vendor that had gone belly up. With no access to source code (and we did try to find a way of getting it) – there was no option but looking at replacing the component. Unfortunately, the effort required to migrate to a new component have been estimated to be so comprehensive that a complete refactoring may turn out to be a better alternative.

It just goes to show the importance of ALWAYS, and I do mean ALWAYS getting ALL components with source code. Another repeat observation is the importance of decoupling your GUI from your datamodel and business logic. Keep your GUI stupid.

I’ll post some generic observations about code changes at a later point in time – but right now I am sunk in other tasks.

2 thoughts on “D5 – D2009 porting project update

  1. Agreed. Even then, it’s no golden guarantee, you still may have to change the component to get it to compile (and it might require considerable work), but you’re improving your odds considerably this way. Sometimes you get lucky and others have gone through the modifications already and you can find the changes on the Internet.Two other factors I take into account are: How likely is it that the components will be around in a few years’ time, and can I design the code around it or encapsulate the interface to the component so that it will be easier to switch the component for another.


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.