[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [jwt-dev] Now that JWT 0.6 is released...
|
Hi Mickael,
thanks for this wiki-page. This is really helpful for all developers (me,
too! ;-).
The only part that I didn't understand was the following. What is this with
this activity if I make a contribution to the UI? Does this mean that I need
to change the org.eclipse.jwt plugin each time I create a new plugin that
contributes to the UI? How do I need to adapt it? The sample that you've
written there seems to be the same each time!?
Thanks for your answer!
Florian
---
JWT defines an activity in its "branding" org.eclipse.jwt plugin, that can
be found on CVS at org.eclipse.jwt/releng/jwt-branding-plugin. For the
moment, this plugin should be the only one to bind extensions with binding.
If your plugin adds a contribution to Eclipse UI (ie a contribution to
org.eclipse.ui.*) and is part of the JWT feature, then the branding plugin
should define a binding from these contributions to the JWT activity.
Simply add into the org.eclipse.jwt plugin
<activityPatternBinding
activityId="org.eclipse.jwt.Activity"
pattern="org\.eclipse\.jwt\.plugin/.*">
</activityPatternBinding>
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 26 June 2009 10:18
An: Java Workflow Toolbox
Betreff: [jwt-dev] Now that JWT 0.6 is released...
Hi all,
It is time to leverage everything we could learn during this release train.
Here are some thing we should now care about to keep on improving JWT
conforming to Eclipse quality standard:
* Internationalization, String externalization, NLS and Babel
* APIs (will soon become very very important): Now that we have our first
release conforming to API tooling convention, we can make use of PDE API
Tools to handle API versioning automatically
* Unit testing: Now that we have automated tests, let's use it to avoid
regressions.
* Separate UI and non-UI plugin: When one develop a UI, he also develops
some logic code for what this UI is used. Those 2 parts must be separated.
* And a lot of other things...
You can find some documentation at
http://wiki.eclipse.org/JWT_Modifications. I did not test the API Tooling
yet, and I'm not sure the step described to get it working are enough (I
imagine it also requires sources from baseline...).
I'll refine it as soon as possible, and feel free to add you advices and
comments for next JWT development on that page.
Regards,
Mickael
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
