Re: [cdt-dev] Module dependency

[Alexander Fedorov <alexander.fedorov@xxxxxxxxxx>]

Hi Martin,

Yes, technically you can express it all with global constants and global 
functions. Unfortunately it is all allowed in Java while they say it is 
OOP language [1]
Unfortunately, because "static" in general and "constant" in particular 
are counter-OOP practices [2]

As for OSGi magic. In CDT we are based on Eclipse Equinox (OSGi 
implementation) that gives us modularity and a lot of other good things.
For example we can declare a service contract in one bundle and then 
start using it from another bundle omitting implementation details. 
Without platform support it will be an ugly design like global singleton 
instance or evil "setter" methods, that will make things more coupled. 
So, why not to start using OSGi instead of competing with it?

Regards,
AF

[1] https://docs.oracle.com/javase/tutorial/java/concepts/index.html
[2] https://www.yegor256.com/2015/07/06/public-static-literals.html


13.03.2020 22:20, 15 knots пишет:
> Hi Alexander,
>
> Am Fr., 13. März 2020 um 18:49 Uhr schrieb Alexander Fedorov
> <alexander.fedorov@xxxxxxxxxx>:
> > Hi Martin,
> >
> > I used to assume the code is clear enough, but it seems I was wrong.
> > Thanks for pointing to this fact! :)
> >
> > 1) "org.eclipse.cdt.core.options" package provides generic API
> > 2) "org.eclipse.cdt.doxygen.core" package provides domain-specific API
> > for doxygen - you will need to define your own, but very similar.
> > 3) org.eclipse.cdt.doxygen.internal.core.DoxygenPreferenceAccess is
> > implementation for DoxygenConfiguration and DoxygenPreferences interfaces
> > === warning! magic starts from here
> > 4) and, org.eclipse.cdt.doxygen.internal.core.DoxygenPreferenceAccess is
> > an OSGi component (see annotation and manifest in OSGI-INF/)
> This is is the magic I did not catch.
>
> > 5) CEditorPreferencePage gets the DoxygenPreferences service via E4
> > context:  EclipseContextFactory
> > .getServiceContext(FrameworkUtil.getBundle(getClass()).getBundleContext())
> >                   .get(DoxygenPreferences.class)
> >
> > This is how it works. Hope it will help.
> >
> > And I also have a question for you: where do you expect to find this
> > info initially? It is important question, because it may help us to
> Somewhere in the javadocs in the o.e.c.c.options package. Maybe a
> simple example in the javadocs.
>
> I one looks at the docs in o.e.c.c.options, he/she will have no clue
> how to use OptionMetadata to get the actual data (that is: there is no
> indication that someone will have to implement steps 2-5 you outlined
> above).
>
> BTW, I just need three String keys to access preferences for 2
> Booleans and a String from jface.preferences. What was not on my
> radar, is that I was expected to create at least 3 classes and
> configure an OSGI-service to accomplish the task.
> I expected to just move the String keys from *.ui bundle to *.core bundle.
>
> Regards, Martin
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev