[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [dsdp-mtj-dev] Current MTJ code
|
Title: Current MTJ code
Hey Paula,
Below are some of the major changes done to the 0.7
codebase.
-
support for multiple SDK
(adding Device Platform, removing Device Platform and its consequences
with regards to Runtime Platform, duplicate Runtime Platform,
etc.)
-
implementation of import of a
MIDlet project from Netbeans, EclipseME, CarbideJ
( new project creation
from import and import into existing MTJ
application)
-
MIDP2.1 support (though not well
tested)
Addition to above, there was a lot of small bug fixes
done.
The
things that we have not taken any further, relates to the Device fragmentation
area.
Yes,
there are several plugins, which are rather small. About the MTJ
plugin model, I did attach (a bit outdated, but quite relevant) Excel sheet
about the plugin structure. I have used Lattix dependency tool to analyze the
plugin structure and overall situation is nice (thus there are few cases
that would be needed to fix).
To
gain overall to the plugin structure, please look at the few documents at the
cvs (mtj-home/docs/*)
The
current project resourcing is problematic, cause there are not so
many active committers in this project.
-Arto
Hi,
I started to study the current MTJ
code. One initial aspect that i note is that there is big different between
the 0.7 release code and what it currently in the cvs. In the cvs there almost
50 plugins.
Is there any list of the
differences between what is on 0.7 release and what is on the cvs?
Is there any email or document
that describe all of those plugins?
I'm trying to setup everything in
my desktop and see if i can use it. Once i have some news i will send back to
the list
thanks,
:)
gep
Attachment:
MTJ_dependency_model.xls
Description: MTJ_dependency_model.xls
