[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Module dependency
|
Hi Martin,
You are right, .core should never require .ui
One of the reasons it to keep the most part of functionality easily
testable in pipeline. And ideally, UI layer should be as thin as
databinding between SWT widget and "data storage".
The solution is simple: we focus or preference reading/writing in
.core bundle and deal with visualization in .ui bundle.
We already have this in CDT, you can start from here
https://github.com/eclipse-cdt/cdt/tree/master/core/org.eclipse.cdt.core/options/org/eclipse/cdt/core/options
Regards,
AF
12.03.2020 0:22, Jonah Graham пишет:
Marco has pointed you in the right direction. I
hope Alexander F can point you in the best direction
going forward to go with his commit.
CDT has some bad examples (anti-patterns) in the current
code base.
Jonah
Hi
all,
I am implementing a UI bundle which provides a preferences
page and
exports the preference constant keys.
My core bundle needs to read the preferences by the keys. This
causes
a dependency of the core bundle to the UI bundle which somehow
seems
to be wrong to me.
How does CDT usually handle this case?
TIA, Martin
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
