There is something distinctly refreshing about re-visiting a past tool that you've used; much like finding an old install of Diablo 1 and losing 5 hours as you remember exactly how much fun it is to play. I dare say I'll experince the same with StarCraft2 and Diablo 3 at some point.
Though for now it's the rekindled fun of programming with Java (no no not for vBulletin, don't fret), the Sun Microsystems variety.
It's been near 6-7 years now, so getting back up to speed
And the end of a year nears close.
ImpEx is 116 systems now, and tier one has averaged a 24 hour turn around (allowing for weekends) for updates.
Progress on ImpEx2 has slowed a fair bit as I'm now working more on core features for vBulletin with other members of the team.
Though for ImpEx2 ; ease of interface use, performance, smaller footprint & fuller automation are the four main areas I'm looking at.
An evolution opposed to a revolution
Well some Quad core ImpEx development action is leading to some much needed benchmarking now with the help of Zend Studio for Eclipse.
Finding the bottle necks on the bigger imports is leading to order of magnitude of speed increases.
The ImpEx2 plans to compliment vB4 go well ....
Well ImpEx gets it's first new product to support, which puts us well over the hundred systems supported ..... no to some (on going) refactoring and evolution to stay on top of the growing system and customers requirements
Hello all
All is well in the world of ImpEx at the moment, new development on forum systems is on hold while the blog core is added to ImpEx and the separate systems developed, which is the current development task.
As for the core the next thing after the blog systems is the database logging and front end display of the failed data items for Tier 1. A update in the language from failed to not valid also to differentiate between the two diffrent states that can result
