This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Preparing for Pollock
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
One of the things I get asked about a lot is how VisualWorks developers should proceed with GUI plans - Pollock is coming (usable beta next year, full support in 2006) - see the roadmap. I realize that full production on this is a ways out, and that our user community has real work to do in the meantime. Here are a few tips on how to proceed:
Read Sames' blog. Sames is posting on Pollock development regularly - it's your best way to get information on what's happening - and your best way to provide early feedback
Join vw-dev. This will give you early access to developing code, as well as access to our developer forum
Use the current GUI tools - but prepare for the future:
Separate your UI code from your domain logic
Use trigger events instead of dependency. This is covered in the documentation
If you customize the Cincom UI frameworks, make sure that you keep that code in a separate package that is easily identifiable
When Pollock ships in full production, we'll have migration tools available - and the more closely you've hewn to the UI steps outlined above, the easier it will be to migrate.