First of all, I’m not sure if this is the correct category to post in (maybe Add-ons, even if it’s a general Q and not tied to any specific add-on?).
Now the real question:
I have just completed a component/add-on (OT: we should definitely stick with ONE name here…) that is 95% developed in the
Now today, to my surprise, I realised that Studio will stop adding the
gui module to new projects, and one should add it if required.
To my understanding the
gui module is, more or less, there to support projects that target (or wish to) both
desktop environments. So, in the end, is pretty much useless for those willing to target only
web (the 99% of CUBA users?)
Now the dilemma of a component developer:
Should I stop putting generic code in the
gui module, and use only the
web one, because:
- this is your first step towards the deprecation of the
desktopuser’s base is so tiny that I shouldn’t bother giving them my components
I continue as before putting as much code as I can in the
gui module (that is, when I see something that can be generalised, I usually put it in the less specific module, the
gui one), and force the consumers to add the module if missing in their project, only to be able to use my component(s)?
Thanks (and move this to another category if you see fit)