cZen Issue No.1 - page 3

libzCiATran.so - Cincinella - Inter-process communication

cChannel cMessenger cQMessenger

libzCiAtLex.so - Cincinella - Messages handling

pHandler pInvoker cListOfMessageFilters cLooper cMessageFilter pScriptable

libzFfACore.so - Farfalla - Core elements

cApplication cListOfRects
cBitmap cListOfViews
pCanvas cListOfWindows
cContainerView cListView
cControlView uPalette
cDrawContext uPoint
cDrawView uRect
cFont sScreen
cGroupView cView
cLayoutView cWindow
cListOfPoints

libzFfAMain.so - Farfalla - Main elements

cBitmapView cMeterView
cButtonView cOffScreenView
cCheckBoxView cOnOffButtonView
cComboBoxView cPanelView
cDisjointView cProgressBarView
cDividerView cRadioButtonView
cFileListView cScrollBarView
cFloatEntryView cScrollView
cFloatingView cSeparatorView
cFrameView cSliderView
cIntegerEntryView cSlidingView
cMenuBarView cStringView
cMenuButtonView cTextEntryView
cMenuItemView cTextListView
cMenuView cTextView
cSlidingCaseView

libzFfAxTnd.so - Farfalla - Extented elements

cAlert cSlidingAlert cFilePanel

libzFfAxTra.so - Farfalla - Extra elements

cBarGroupView cCalendarView cClockView cColorCellView cColorPanelView cColorPatchView cColorWellView cIEButtonView cPulseView cToolBarView cToolButtonView

libzFfAxWeb.so - Farfalla - Web browser

cWebView

}

void cZen::WorkshopL() // Answers to developer's questions

{

Now that 0.7 is out, the big question and issue is what's the best way of migrating your code... Well, there are several ways to go about it, but here's a few tips:

Coding style

Obviously the main thing to do, is to adapt to the new coding style. This would require a lot of renaming. For instance, all the z*** classes are now named c***. The best approach is to edit the files one by one and replace all the identifiers that have changed. If you wish, you are also free to change your coding style for things such as variables names and so on ... ;-)

Header files

Now, all header files are either in Cincinella or Farfalla. As an example change, you will need to change from #include <zGUI/Window.h> to #include <Farfalla/Window.h>.

Namespaces

The SDK is now using its own namespace, zSDK. Each kit is also using its own namespace, Cincinella and Farfalla. If you are using Cincinella, you may want to add the following line to your source code files :

using namespace zSDK::Cincinella;

And if you are using Farfalla, you may want to add:

using namespace zSDK::Farfalla;

Libraries

Using the list from the previous section, you can get a clear picture of what libraries you will need for your software. Take a look at the Demos makefile to learn how to link against them.

}

void cZen::Misc() // Miscallenous stuff

{

// To be implemented

}

void cZen::FeedbackLC() // How to give some feedback on the newsletter, or ask questions

{

Feel free to contact hexaZen if you have any questions or if you wish to submit your own workshop suggestions.

}

void cZen::PrintToStream() // Display this newsletter on one page for easy printing

{

cZen - Issue No.1 newsletter is available on one page on a white background, for your printing convenience.

}


To obtain more information, please contact hexaZen at www.hexazen.com
Copyright © hexaZen 2003-2004. All rights reserved.
All content © 2004-2007, hexaZen - Vancouver BC, Canada