good idea! thanks for volunteering :)
2007/9/14, Alexey Petrenko <[EMAIL PROTECTED]>: > Guys, > > we are positioning modularity as one of the key benefits for Harmony. > And it is definitely one of the key benefits. > > But there is no simple way for Harmony users to define the list of > needed classes, jars and native libraries for their applications. > > So I suggest to create a tool which will create Harmony package with > the classes and native libraries used by concrete application or work > flow. First of all this application should collect data from one or > multiple application runs and then create a Harmony bundle without > unneeded classes and native code. > > Thoughts? Volunteers to help? :) > > SY, Alexey >
