Roslyn Parsing now Formatting Code

-

I almost took another break on Roslyn’s SyntaxTree, to tackle dialogue. But I spent Thursday resolving it to completion. 😊 For the initial test, I wanted parsing, as it is *somewhat* easy to apply formatting based on the syntax kind (of which there are around 500 see: https://github.com/dotnet/roslyn/blob/master/src/Compilers/CSharp/Portable/Syntax/SyntaxKind.cs ).  I set it up to pick a color at random for each new kind it comes across in code. (rather than resolve them all right now)



What is not so visible, is the fact that I now have access to the types called out in the code. I can tell what classes and namespaces are in use. After researching several paths, including looking up black lists of C#, such as CAS, I ultimately will be going with a white list. 

If a type or method is not in the white list, the code will not be executed, and the unsafe code will be highlighted as under risk.  I will also generate a black list myself.  Basically code will go into one of 3 categories; Safe, Unevaluated, Unsafe. 

If all types are considered safe, it will compile.  If any type is unevaluated or unsafe, it will prevent the compiling of the code, and highlight the member(s) in question. If the class/member is marked unsafe, then it will give the reason through a tool tip or another system, as to why you cannot use it.  I.e. the specific security concerns. Finally, if it is unevaluated, then it will explain that we simply haven’t considered the safety risks for using the given code. It will also give the option to flag the code for evaluation in a later release. 

I don’t have the lists built up for this at all, but I will be starting that soon. Before the first playable demos are released to the public. I do plan on hitting the dialog system next, from UI and editor as well. I’m specifically looking at using Unity Graphview for managing the dialogue. But that will be a later post.

Comments

Post a Comment

Popular posts from this blog

C# Parser and Code View

-
Image
I don't have any Proof of Concept in place yet on this, but I've finally started designing how the code editor UI will work, then designed some of the basic architecture needed to support how the UI would work, and finally, this lead to how I need to protect the user from dangerous code (you can write C# to format your machine, or try to steal memory from other apps like passwords), while also improving the debugging and teaching abilities. Alright, so I'm planning on having Classes exposed, as an item, then under the class view, is a list of items, like fields, properties, methods, etc. When selecting one of the members, you get details like notes, title, version history; for beginner coders I felt giving them a really easy ability to step back a version or two to something that last worked. Then show the code.  To be able to provide physical system responses, we need to detect all sort of things, like an infinite loop. In the case of an infinite loop, we don't ...
Read more

Setting up Roslyn Parser In Unity

-
Image
So, I did manage to get the Roslyn C# Parser partially running, on the last commits of the Proof development. Now I'm putting Roslyn back in.  As I'm finding the same hurdles I thought I would call them out more clearly for others to tread. Generated on WordClouds.com , from sample C# parsed by Roslyn SyntaxTree First off, it wasn't a straight forward install, of just add this package and go. The first step was to install NuGet for Unity, as found here: ( https://github.com/GlitchEnzo/NuGetForUnity ). Instructions and download are there. Keep in mind: NuGet Packages are typically designed for Visual Studio solutions, but this is Unity. Many packages will not work out of the box. Roslyn is no exception. So now, with NuGet running, we need to pull in Roslyn. Search for "Microsoft.CodeAnalysis.CSharp" and pull it in. Once done, there will be a handful of errors, relating to references being missing or incompatible.  So now we need to fix those errors. Now, ...
Read more

A Momentary Lapse of Passion

-
Image
There have been so many projects that I have lost passion for while developing, that a few years ago, I challenged myself to start paying close attention to this. To start researching the psychology of what drives me to and from a goal. In that time, I found that Game Design is actually a key value in life's success. And Codavore will survive because of this. :D I'll tell you a short story of why I lost my passion for Codavore and then how I revived it. In hopes that when you hit this runners wall, you might be able to get past it as well. source:  https://pixabay.com/photos/light-bulb-idea-creativity-socket-3104355/ 2 weeks ago, I wanted to start working on the dialogue system, as that would be a common need in this game. I had seen the start of an instructional video on how another person had created this really nice looking Dialogue Graph, and kept looking for opportunities to apply it (or similar) in my code. So my first steps into the dialogue pushed me into worki...
Read more