So, after being impelled to read a paper closely (Oh, the horrors!) I've realized I'm doing things the wrong way.
You see, I've 'been applying the context-sensitive part of the L-systems in the wrong step. My plan was to cause minecraft to handle context. That's the display medium, after all. Because of how I'm passing minecraft the data, though, the context wouldn't operate on the l-system, it would operate on the translation of the l-system. This is not right.
Consequently, I have two choices.
I can port my L-system tools from c# to java.
...or, I can switch display mediums.
Porting the L-system tools would be a fairly dull endeavor, and tie me more heavily to minecraft.
Within the "switching display mediums" option, I have two choices: roll out a new display medium, or use my "backup display medium". I wrote the backup display medium a while ago. It has some of the same problems that minecraft does--it ties me to an array-granularity system. (meaning that the translation ends up being measured and displayed in blocks.) The other issue is that it's not a great display medium. The rendering style is both top-down and fairly abstract, meaning that while I could read the output, there's a good chance nobody else could.
Rolling my own display medium has one big problem--overhead. I'd have to drop a lot of the direct work on L-systems for a while to work up something nice. The big advantage is that by the end of the year, I'll (hopefully) have an application to show off.
Right now, I'm leaning towards creating my own display medium.
You see, I've 'been applying the context-sensitive part of the L-systems in the wrong step. My plan was to cause minecraft to handle context. That's the display medium, after all. Because of how I'm passing minecraft the data, though, the context wouldn't operate on the l-system, it would operate on the translation of the l-system. This is not right.
Consequently, I have two choices.
I can port my L-system tools from c# to java.
...or, I can switch display mediums.
Porting the L-system tools would be a fairly dull endeavor, and tie me more heavily to minecraft.
Within the "switching display mediums" option, I have two choices: roll out a new display medium, or use my "backup display medium". I wrote the backup display medium a while ago. It has some of the same problems that minecraft does--it ties me to an array-granularity system. (meaning that the translation ends up being measured and displayed in blocks.) The other issue is that it's not a great display medium. The rendering style is both top-down and fairly abstract, meaning that while I could read the output, there's a good chance nobody else could.
Rolling my own display medium has one big problem--overhead. I'd have to drop a lot of the direct work on L-systems for a while to work up something nice. The big advantage is that by the end of the year, I'll (hopefully) have an application to show off.
Right now, I'm leaning towards creating my own display medium.