Well, there are a few things that we need to get straightened out, and I think a lot of it is because we're at an impasse... *looks round nervously* Hang on, isn't that my job to sort?
Seriously, though, a lot of the decisions that need to be made need input from the programmer(s) that will work on it; I'm still learning C++ so I wouldn't be able to really input much in the way of code etc. I have also been real busy with work lately, working late and so on and I've had a major project which has come to its deadline rather quickly...
A lot of the really crucial decisions will affect the coding and since daemon has done a lot of the modifications to date, I'd really like his input before making concrete decisions.
I think I know how the decisions will turn out and I can see how/why and I'm likely to agree, but I do need his comments about them, e.g. plugin language and implementation being the main one, since he is currently the main coder.
The syntax format debate is still rumbling around in my mind, and especially with respect to exact implementation details. I'm still trying to write a structure that will cover most syntaxes without any fuss, and will be quickly parsable by a machine (human readability is nice, but high machine readability will be faster)
I'm still playing with this one at the moment.
I think the autocomplete debate is settled for the moment, though, but I know that what we do with the above syntax file will be a major factor in this, so I want to write something that promotes an autocompletion facility (not code completion, particularly, see the Syntax forums for these comments) without being a huge issue.