[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [xtext-dev] Migrated to Google Guice
|
Some additional changes I've not mentioned, but don't want to put into
the documentation:
Previously there was an extension point, which activated all Xtext
plugins (they have implemented the extension point) when loaded.
This is no longer the case. Instead the configuration is done in a
generated Activator class (startUp).
The whole plugin gets active when code is loaded. For now there is an
empty Editor class (also generated), which activates the whole bundle.
So a bundle is only activated when it's needed.
We have to think about situations where the bundle needs to get
initiated without having the editor opening a file.
This might for instance be the case, some other component want to load
a resource using the ResourceFactory.
Is not hard to solve, but it is not solved yet.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263046
Sven
On Jan 30, 2009, at 3:38 PM, Sven Efftinge wrote:
Hi,
I've just checked in the migration to google guice.
In case you don't know, Guice is a dependency injection framework,
which now replaces our homegrown DI framework.
The main changes are:
- some projects are superfluous (I removed everything and put a
DELETE.ME file in, in addition they are no longer in the team
project set files)
- two new projects (I've renamed the *.ui.common.xtend project to
just *.xtend, because it's planned to have Xtend-based runtime API,
as well. I've added a corresponding *.xtend.tests project)
- the configuration classes used to do the DI setup are replaced by
module implementations (module is a guice concept).
I'll write down the details in the wiki.
You should also read http://google-guice.googlecode.com/files/Guice%201.0%20User%27s%20Guide.pdf
.
Cheers,
Sven
_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/xtext-dev
