| RES: [dsdp-mtj-dev] MTJ extension points |
|
Hi craig, I did some tests with
diego and MTJ worked the same with or without it (we tested the import of both an
UEI sdks and microemu). I’m not sure if we are missing something on the
code. And when we looked at
this extension in a perspective of a public MTJ API, we could not identify a clear
use case that it implements. So following that approach to simplify mtj api, we
suggest to remove it. again, this is just a suggestion that is open to
discussions. Do you see some scenario where
it will be used by someone? What are your thoughts on that? J gep De:
dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] Em nome de Craig Setera So, the API extension point is now completely gone? I thought
that one was staying, but being renamed to something else? On Feb 9, 2009, at 11:30 AM, Paula Gustavo-WGP010 wrote:
Hi, We are working now on the extension points for tomorrow’s
build. Initially we plan to have
the following extension
points defined on MTJ: Core plugin: - org.eclipse.mtj.core.deviceimporter
UI Plugin - org.eclipse.mtj.ui.vendorattributes
Probably it is possible to merge both jad editor extensions, but the
impact now is quite high now. We are still evaluation how to do it. J gep _______________________________________________ |