cnjinhao / kunlun Goto Github PK

Forked issue off of #1 to put stuff about the build process here.

Here be examples!
I trust you can do all the option stuff much better than i can, just want to show what i meant in forms.
All of the below can also be done with wizards and good defaults! But sometimes, as I need to, building in msys2_32bit and msys2_64bit while having VC++ and C++ Builder installed, stuffing **** into my environment variables make this necessary.

My Env. Var Window:

(Sorry if I could've used nanas capabilities better here ;))

My tooling options, to name the executables that can be found in PATH used for building:

My GDB Settings

And last but not least my project-target options. (A target = a combination of tooling and environment)
(I can also imagine a much better UI design here, but it served the purpose so i could get on and build my projects etc)

I didn't formulate a pull request for the specs, because I would love to hear other peoples opinions on this.

• Code highlighting is a very non trivial thing since its tightly coupled to the language. They way its implemented should be a simple but powerful interface where the individual language highlighting implementations are attached to, so that contributing highlighters is easier. This way highlighting support may grow over time (eg. multiple languages, swapping the highlighter implementation for individual file extensions)
  • Potential "Highlightables": keywords, literals, string literals, comments, macros, user defined identifiers (like user macros).
• Highlighting for searches.

I suggest to pass the code parsing to an interface (maybe the same as the highlighting) too to provide tokens (maybe more) which can then be used for editor features like highlighting.

To suggest more concrete ideas, I would need to try and implement everything myself to see where issues and complications with these ideas arrise.

Less necessary features:

• Indentation Guides?
• Multi Carret Editing?
• Code folding?