Generating C# Code from node tree form is getting there!
Showing a project with one class, "ClassyClass", one method "Mannie Method", and one declared "String" with default value, "StringyString".
Showing a source file with one class, "ClassyClass", one method "Mannie Method", and one declared "String" with default value, "StringyString".
Compilation is in it's early stages, but it's still cool to see this coming together! Code generation uses the CSharpCodeProvider class to generate code for things like classes, class members, etc. During the generation process, each node has its data saved to the project file, ensuring that the data found in the project save file is the same as the data that is getting code generated for it. Additionally, this process gets the information to generate directly from the save file rather than from nodes loaded into memory, because the latter would require that the nodes to compile had all been opened at least once. That really isn't an option with larger files as one might imagine.
Node Information section has some new fields:
The people reading these who have a keen eye might have noticed the section "Node Information" has a new field: "Comments". Comments has a text box that when you press enter will save the comments for the class/method/node currently opened. This can be seen working above where the comment for ClassyClass was saved using Node Information. Expect more in the soon, because there will be more!
New Property Create Dialog:
The previous dialog (right) did not match the style at all and from a functionality standpoint, barely worked as it was made so early in development that I hadn't thought much about these would be applied in the future. This fresh new design was made knowing how I wanted to apply properties in Intensive.
Node Companion:
Note that the situation I'm about to describe 1) Does not take formal parameters into consideration and 2) Is concept only and is not functional yet!
When you click a node that can perform a task, in this case a node that represents the Glide.GrowGlide class (briefly mentioned in the previous post). The companion allows you to edit the way the node does its job, as you might have expected. For example, if you click "Declare New Instance", the node then knows to declare a new instance of GrowGlide and then to call the selected method above: BeginEffect(); Additionally, when we press select variable, we can make a new variable to assign a value, the new instance is one of the valid return values! So lets say we made a new variable, and selected the value to set it as is the new instance of Glide.GrowGlide.
In case you didn't get all that, here's the code we should expect this to generate:
Glide.GrowGlide <variable name> = new Glide.GrowGlide();
<variable name>.BeginEffect();
Likewise, if you didn't specify a variable to set the new instance as, we should get this code:
new Glide.GrowGlide().BeginEffect();
That wraps things up for this post. Thank you so much for visiting my project's thread, and I really appreciate you taking the time to read my little spiel
.
A list of commands that Lookup can do with descriptions.
