SnowFlake Project

New Project: SnowFlake started to deal with the complexities to deploying multiple J2ME platforms since the games and screen savers projects will need to be developed and published to a multitude of devices.

The inspiration for the SnowFlake project's name came from the one liner in the movie Fight Club - "You are not a unique little SnowFlake!" :-)

As some build's are unique but of course need to be built in a uniform fashion at the end of the day this is achieved by the SnowFlake application and three new XML formats....
  .sf.platform.xml (manufacturer definition per file)
  .sf.mobile.xml (mobile device platform per file)
  .sf.config.xml (SnowFlake config for automated per project calling)

SnowFlake reads in the XML files and processes each manufacturer and its related mobile files performing a J2ME build per mobile turning on and off the required inline code in the java source automatically (using an already finished application's J2MEPlatformMerge (per source file) and J2MEPlatformMergeRec .

The XML / XSD Java infrastructure source code is being visually modelled by and automaticly generated from CodeSlayer.

Currently the prototype reads in all the XML files and processes them accordingly, it just needs to generate the Theena build properties and build script then call it.

--------------------------------------------
Prototype Requirements.
--------------------------------------------
- Provide a command line application to perform the multitude of builds
- Build platform framework is Theena
- Turn off / on the SnowFlake inline commented source to provide the different source code solution's across the multiple J2ME platforms such as MID 1.0 / 2.0 / 21 and CLDC 1.0 / 1.1 and any device specific idiosyncrasies.
- Provide an easy way to develop for multiple platforms from one source code base
- Easy deployment of the resulting builds to J2ME OTA or too a vendor.