xapier14/cerulean

A cross-platform UI framework for C#.

👋 Hello!

I'm Lance, a computer science graduate currently working as a Frontend Developer!

I do a variety of projects, but they are mostly written in C#.

I'm looking to learn and explore other languages and tech such as Ruby and Containers.

Languages and Skills

My Projects

Some Stats

cerulean's Issues

Use ISourceGenerator in auto-generation of XML parsed code

Current solution uses a simple string builder and writes the source into a designated folder to be discovered by the compiler.
A better solution is to use ISourceGenerator for native functionality.

Move Builder implementation back to CLI project

Move the Builder and BuilderContext back to the CLI project.
Make an interface to allow extensions to Element Handlers.

Update and write new tests

Update and write tests for new CLI features.

CLI builder generates invalid nested component line.

Sample XML:

<Panel>
  <InputContext SubmitButton='Btn_Submit'>
    <Button Name='Btn_Submit'/>
  </InputContext>
</Panel>

Generates C# snippet:

...
GetChild("<anon_panel>").GetChild<InputContext>("<anon_ic>").SubmitButton = (Button)GetChild("<anon_panel>")GetChild("<anon_ic>").GetChild("Btn_Submit");
...

Expected snippet:

...
GetChild("<anon_panel>").GetChild<InputContext>("<anon_ic>").SubmitButton = (Button)GetChild("<anon_panel>").GetChild("<anon_ic>").GetChild("Btn_Submit");
...

Use ISourceGenerator in auto-generation of IComponentRefs for external component support

Cerulean.CLI currently uses special IComponentRef classes that have information on how to handle component properties when generating from XML files. These are, for now, created manually but can be too tedious to create for each component. A solution is to have a source generator generate it for us.

This can be done alongside #44.

The current progress of this solution is to have a project called Cerulean.Analyzer that contains the source generator.
For now, the focus would be on a source generator for IComponentRef.