Hi Matthew, some random thoughts.
I'm not sure I agree with doing lots of changes on a separate branch basically without any review. While you will be able to commit things fast to the branch, the most probable outcome will be the branch will get never merged because either nobody will be able to review the changes during merge or there will be some disagreement about something that could have been caught early. And then it's just lost effort. The individual points here https://github.com/geany/geany/issues/1195 look like they should be able to do one by one. The most useful seems to be the code completion so this might be the one to start with. In parallel it would be good to develop a plugin that uses the new API and get it to a really usable state - you won't be able to tell what exactly you need for the plugin unless you have some working code. In parallel you can get some feedback from users and they will have something useful rather than lots of half-finished prototype features that aren't really usable. My other question is who wants to work on this? The issue mentions only those providing patches should be involved but is there anyone except you who will contribute patches? I confess this isn't very interesting for me - I'm not so terribly tied to Geany and if I wanted e.g. a dedicated C++ editor, I'd grab something else - you always get better language support if the editor is made specifically for your needs. I use Geany as a general purpose editor but otherwise use also Android Studio and XCode when writing for Android or iOS. So no patches from me I'm afraid :-(. Apart from that this is a huge amount of work and I'm just lazy, sorry ;-) Cheers, Jiri
_______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
