doc-helmut wrote:1.) visual Basic or Delphi or Borland C++ (which I actually know better) don't generate code that calculates or writes any useful routines - they generate just a user interface with windows, buttons, canvas, menus, edit boxes. What happens "internally" if a user pushs a button must still be written in "legal handwritten C or Pascal code" - each variable, each loop, each if, is +, *, / -, ^, % or what ever.
No idea what you're saying here, but C# has excellent "code-behind" features. It's not just an interface.. And even if it wasn't, .NET allows close integration of CLI and Native codebases. I could write all of the codebehind in C++ if I knew it and wanted to.
doc-helmut wrote:2.) What you try to do is much more than this: you try to put every keyword, variable, more-dim. array, expression, macro, modifier, device, into a graphic symbol.
Not quite. Blocks will merely represent a snippet of NXC code. There will not be a single block for 'every line of code'. Some blocks will contain dozens of lines of code. Variables will be handled automatically (to some extent) in that local varaibles will not conflict with global variables, and the user will have access to the global vars
if and only if they want it.
doc-helmut wrote:3.) NXC has lots of keywords and symbols and devices and what else...
See my response to point #2.
doc-helmut wrote:4.) If you try to put all this (the programming language itself, not just the user panel and interface) into grafic symbols you will end up inevitably at a grafic language which more or less looks like or similar as NXT-G or Robolab or Labview, except the fantastic benefit that you will have an additional written code in NXC syntax.
That is the idea
And, unlike NXT-G, Robolab, or Labview I am planning on having a special block for advanced users that allows them to write the code within the block themselves.. Think of an "nxc code" block in NXT-G.
doc-helmut wrote:I really don't want to discourage you or call your challenge into any question, but given the fact that it is an almost unmanageable chunck of keywords, definitions, predefined expressions and macros (look at NXCdefs.h) which have to be processed into a graphic symbol it's worth while a big team of specialists who care about it's implementation and redeployment and it's hard to see in how many years this project will ever be finished...
The "chunk of keywords, definitions, expressions, and macros" is hardly unmanageable. V-NXC already parses all commands, constants, and keywords (2,000+ of them) to do the code highlighting. It loads this all when the "view output" window opens, and takes no noticable time at all.
doc-helmut wrote:I personally almost would have resigned since quite from the start, but I honestly hope this could be a further incentive for all for all involved people to bring this actually magnificent project to a glorious final...
That is also the idea
Have a nice day,
~Sidneys1
