A few messages on the FaceSpan 5 Alpha mailing list have described the difficulties FaceSpan 3 users face when trying to get up and running with FaceSpan 5.<\/p>\n\n
I’m going to use this blog post to collect a summary of the differences between FaceSpan 5 and FaceSpan 3. This list will no doubt grow over time as we learn more about how best to program FaceSpan 5.<\/p>\n\n
So here we go:<\/p>\n\n
The names of many properties have changed. When the FaceSpan 5 dictionary settles down, I’ll prepare a table that maps the old FaceSpan 3 names to the new FaceSpan 5 names. Until then, you’ll have to use the FaceSpanKit dictionary to find the new names.<\/p><\/li>\n
You can safely ignore FaceSpan 5’s delegates when starting out with FaceSpan 5. FaceSpan 3 message dispatching is identical to FaceSpan 5’s default way of dispatching events (i.e. upwards the containment hierarchy: view -> window -> application).<\/p><\/li>\n
FaceSpan 3 allowed you to reference any view from any other view. This allowed you to say things like text view “myViewName”<\/em> in any other view’s script and FaceSpan would search the window for you.<\/p>\n\n In FaceSpan 5, you have to explicitly reference the window using my window<\/em>‘s text view “myViewName” (or more directly: my window’s myViewName).<\/p><\/li>\n There are no storage items. However, you can simulate storage items using Bag<\/em> objects. Just create Bag<\/em> instances at the application level in the IDE. You can then use the Bag<\/em>‘s persistent data<\/em> property to store information that should be retained between application runs.<\/p><\/li>\n<\/ol>\n\n …more later<\/p>\n","protected":false},"excerpt":{"rendered":" A few messages on the FaceSpan 5 Alpha mailing list have described the difficulties FaceSpan 3 users face when trying to get up and running…