+1 for this
feature!!!
I think that
this will add a lot of value
to MTJ users.
J
gep
Hi Gustavo,
A suggestion on how
to improve the user
experience of sharing MTJ projects between users is
to get a
configuration selection dialog
while importing an MTJ project, so the user can choose which
configuration to use
with the project.
Since the device often will differ between users, at least some paths
in the device, this
would be an
improvement from the current: import project, see that there is a
problem
with the device,
change the device.
We are thinking
about implementing this
at Sony Ericsson, do you think this would be interesting for MTJ?
Best regards,
Tomas Westling
Eclipse team, Sony
Ericsson
Hi ingemar,
Actually the
information that is presented
on .mtj and device.xml files are different. The information on
device.xml is a
workspace information that describe all devices that are imported on
mtj. On
the other hand, the .mtj file keep symbol set data that is associated
to the
different runtime configurations that a mtj project can have. The
symbol sets
are used on the java code preprocessing feature.
The user is
able to edit / add / delete
new fields when he adds a new configuration to the project. That why
just
having a reference to the device / group on .mtj file would not be
enough. We
usually refer to the data on the .mtj file as project level symbolset.
We presented
a talk during last eclipsecon
that describe the muti-configuration support on mtj. All of those
concepts were
described on the talk. Slides are available here. If you
have
some questions about it, feel free to send to the list. Suggestions
about how
to improve the feature or make them more clear are also welcome
(specially with
a patch that implements it J).
J
gep
Hi!
Regarding this:
Q: Why is so much device information saved in
the .mtj
file? Isn't most of that information workspace specific?
A:
The information you see on the .mtj file is the runtime configuration
information required for each device configuration you have o your
project.
These information is project specific since the project configuration
must kept
across workspaces.
Yes, but the
workspace have to have the
same device that is connected to the project in its devices.xml file
that is
located in “.metadata/.plugins/org.eclipse.mtj.core”. All
information regarding the device is already in that file. To me it
seems like
redundant information. Since you have to import that device to any
workspace
where you want to import your mtj-project anyway…
Wouldn’t just device
name and
group be enough?
BR
Ingemar
Hi Olsén,
Olsén wrote:
Hi!
I have a question regarding the import
mechanism of
MTJ projects. When working in a multiuser environment people may want
to import
a colleagues project into their workspace. This is troublesome if the
device
that is associated with the project is not located in the exact same
path as
the one that created the project, since the .mtj file is containing
device
specific information. Has this problem been discussed?
I tried to import an mtj-project that had
been created
on another computer. I got some errors so I change the device in the
Java ME
properties to a device that is available on my computer. Some of the
errors
disappeared it still produces an error saying "No device definition is
associated to this project". I cannot find a way around this, apart
from
creating a new project instead.
Can you please
open a bug on MTJ (see link bellow) and describe a step by step process
of
reproducing the issue so we can fix it.
Link: https://bugs.eclipse.org/bugs/enter_bug.cgi?assigned_to=dsdp.mtj-inbox%40eclipse.org&
amp;blocked=&
;bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=Overview%3A%20(More%20detailed%20restatement%20of%20summary)%0D%0A%0D%0ASteps%20to%20Reproduce%3A%20(Minimized%2C%20easy-to-follow%20steps%20that%20will%20trigger%20the%20bug)%0D%0A%0D%0A%20%20%20%201)%0D%0A%20%20%20%202)%0D%0A%0D%0AActual%20Results%3A%20(What%20MTJ%20did%20after%20performing%20the%20above%20steps)%0D%0A%0D%0A%0D%0A%0D%0AExpected%20Results%3A%20(What%20MTJ%20should%20have%20done%2C%20were%20the%20bug%20not%20present)%0D%0A%0D%0A%0D%0A%0D%0ABuild%20Date%20%26%20Platform%3A%20(update%20with%20the%20correct%20values%20from%20your%20workspace)%0D%0A%20%0D%0A%20Installation%20%3A%20eclipse-SDK-3.4.0%20(I20080617-2000)%20%0D%0A%20MTJ%20install%20%20%3A%20Runtime%20|%20SDK%20|%20Examples%0D%0A%20java.runtime%20%3A%20Java(TM)%20SE%20Runtime%20Environment%20(build%201.6.0_07-b06)%0D%0A%20os.name%3A%20%20%20%20%20%3A%20Windows%20XP%20Professional%2C%20Service%20Pack%203%0D%0A%0D%0AAd
ditional%20Builds%20and%20Platforms%3A%20(Whether%20or%20not%20it%20occurs%20on%20other%20platforms)%0D%0A%0D%0A%0D%0A%0D%0AAdditional%20Information%3A%20(Any%20other%20useful%20information)%0D%0A%0D%0A%0D%0A&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=""
Why is so much device information saved in
the .mtj
file? Isn't most of that information workspace specific?
The
information you see on the .mtj file is the runtime configuration
information
required for each device configuration you have o your project. These
information is project specific since the project configuration must
kept
across workspaces.
A nice way to handle it would be to have the
importer
ask the user which device he wants to associate with the project when
he
imports it.
Best regards
Ingemar Olsén
Eclipse team, SonyEricsson
_______________________________________________
dsdp-mtj-dev mailing list
dsdp-mtj-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
Best Regards,
David Marques