Splitting libsyllable

• The idea is to split libsyllable in two, one 'core' part that holds the classes that don't depend on the Appserver, and one part that holds the classes that do depend on the appserver.
• The purpose of this, is to reduce the risk of generating circular dependencies (appserver uses libsyllable, which in turn relies on the appserver). This may or may not be as dangerous as it sounds, but it would at least simplify the design if it weren't like this.
• These lists aren't complete or 100% accurate yet. Feel free to correct errors.
• What name should we give the core library? libsylcore?

Classes that do not rely on the appserver

(classes that we can move to the core library.)

• DateTime
• CircularBuffer
• Handler
• Looper
• Message
• MessageFilter
• MessageQueue
• Messenger
• OptionParser
• RegExp
• Resources
• Thread
• Variant
• Rect
• Point
• Image (ie. the baseclass, NOT BitmapImage)
• Translator
• All storage classes

Classes that may rely on the appserver

• String (Localization may make this class depend on the appserver)

Classes that DO rely on the appserver

(classes that can't be used in the appserver, and should remain in libsyllable.)

• Application
• AppserverConfig
• Clipboard
• Invoker (Application class is used to get default values for constructors)
• Settings (Application class is used to get default values for constructors)
• All widgets (everything in gui, except Point, Rect, Image)

Editing is temporarily disabled!