|
All the options The new Framework preference code and interface is done bringing us one step closer to the next development phase. The preference code now provides a centralized structure for handling the reading and writing of preference data. We also simplified things in the code by storing all the data exclusively in the Mac OS X based .plist file and doing away with the Mac OS 9 legacy "Prefs" file still found in our current line of applications. Up-to-date We should really take vacations more often. Talk about a productivity boost. The complete software update feature of Framework, including downloading and automatic installation, is now done and tested... and it's only Wednesday (beating our original "end of this week" estimate). The .dmg format we were originally using has been dropped due to an issue with Apple's newer Mac OS X releases that prevented our automatic installation code from working. Our thanks go out to all the users who reported the issue to us after running the download & install in our current applications. The next generation of YENCO.COM apps will be distributed in the .zip format which works much better for our purposes. We're back This is a quick note to let everyone know that we have returned from a very relaxing vacation and are back to work on Framework. The new software update check routines are now in place and seem to be functioning properly in our tests. We were very nearly finished this before we left, but we didn't want to rush through things and introduce sloppy code or new bugs. Over the next few days we'll be experimenting with a new download & install feature and can hopefully wrap up the entire automatic software update feature by the end of this week. Facilitating feedback As previously mentioned, in the event that any of our next generation of applications unexpectedly quit or need to be forced to quit, the new framework will display a crash report window complete with the previous usage log the next time you launch. Of course, the first step to fixing any problem is knowing that there is a problem, and so the crash report has a "Send to YENCO.COM..." button. The hope is that, once the feedback is sent in, we will be able to follow the same steps in the usage log to duplicate the issue, because the second step to fixing the problem is to be able to see it in action so we can figure out what is going on and then work out how to solve it. But what if the issue you run into doesn't result in an unexpected quit or require a force quit? What if you want to send some other type of feedback? Perhaps a feature suggestion? Perhaps a comment? Perhaps a question? Lets get it started There is still a lot of work ahead, but today YENCO.COM made the first application build of the framework code to test out the new startup process which is now mostly feature complete. This is a very important milestone in our framework development efforts and a very big deal as this is the first process that every user running our next generation of applications will see. So far the initial test results have been outstanding. What can you expect to see? |
August 2005: |
|||
 |
|
|
|
|
