[Geany-devel] Proposal: Project settings split
elextr at xxxxx
Wed Nov 2 23:03:28 UTC 2011
>> Everything else is shared via VCS, so its annoying that one thing isn't.
> As I said, you can already share settings, you just can't easily synchronize
> them *if* they change.
>> Whats the problem with doing it?
> It adds code complexity, plus backwards compatibility would make the code
> more ugly. Having all project settings stored in the same file is neater and
> easier to understand for users. It makes the manual more complex, maybe
> helping a little to obscure the important stuff.
Nick, this argument is saying that Geany should never change or
improve, if you want to stagnate just keep using 0.21 or your
favourite version ...
Storing information with different uses (personal vs project) in the
same file makes life harder for some users, all your arguments only
relate to development issues not user issues.
> I could bring up the Eclipse argument to say that worse is better. The more
> use cases Geany caters to, the more Eclipse-like it will be.
If there are going to be restrictions on what changes are made to
Geany in the future then you need to put that proposal to the Geany
community to consider how such decisions are made.
More information about the Devel