so, is the component solely a way of communicating data to other systems in a read-only way?
In other words, this means: should I make the component constructor private?
and any facilitators to āupdateā components fields should also be private? to no allow logic that can update them ouside the system?
and, whatever I would use exclusively inside of the system, should never be stored on a component? like toggables and limits options, where many are user accessible ones.
and not necessarily, the components are intended to be on a savegame? this means, I shouldnt bloat it with savable data either, just because they are to be saved?
[details=I dont mean to be repetitive]I am just bringing it all toguether to try to have an overview of the best basic practices.
I think some of these statements, if they are correct, should be frontpage somewhere.
sometimes restrictions are good to increase our code clarity and prevent troubles later on, mostly for newcomers (like me :)).[/details]
.
[details=About constructors again]4 or 5 fields would annoy me enough I guessā¦ some bad things (on my developer side) IMHO:
- having to maintain one constructor per specific usage situation, that truly annoys me from a long long dateā¦
- having to pass many nulls in case of a big-all-fields constructor, for ignorable fields or with defaults.
An workaround (not for components) is an empty constructor and to use many setters after, but that may leave some loose conditions, like things that should be setted together, or before another, would only be detected dynamically, not being a good option.
And I think that will happen to the component with bean I created, and to counter that I would have to create setters with 2+ params with these few being usually not null, what would put me almost like again in the same place I was with many constructorsā fieldsā combinations. But at least would put me away from constructorsā maintenance, have to experiment how that will be
[/details]
I watched its video and it was on eclipse IDE! so most probably it will work great I guess;
I wonder if lombok could provide a combinatory bloating-auto-creation of constructors too? that would be quite useful I guess
intellij </3 blabering
I am unable to use intellij with the same nimbleness I do at eclipse luna. Also their non opensource license bothered me a bit concerning our privacy, despite I believe it would be only related to commercial relations, I didnt like it much. Considering the slowness and my disgust I gaveup on it
Lol itās raining a lot with thunders and I need to stop thinking right now dammit! xD