Spring RTS Engine

CarRepairer wrote:It means I copy files with important sounding names from CA until Chili finally works.

Good approach.

I prefer to copy over everything that sounds like it may be vaguely relevant and delete non-important sounding files until it doesn't work. When it doesn't work I add the thing that made it not work and delete something else. This way I am sure I only have the important files.

Sounds good. And yes, evo doesn't so much block local widgets from being used as much as VFS isn't even aware that the users local widgets directory even exists. So yes it is a custom widget handler (if you can call it that), so if that changes I need to know, but otherwise, lets do eet!

I put chili in evo and said I would document what I did, but I have no idea what I did. I just kept adding files from CA and removing files from evo until the errors stopped screaming at me.

Yeah, I noticed that my widget handler is now been replaced by the one from CA. No big deal really, I can fix that fairly easily once I get the time to screw with it, but priority of changing the vfs stuff is pretty low. I cannot thank you enough for getting in in there. I have already done TONS of stuff with it, and I'm planning quite a bit more. Chilli really is a quite excellent framework.

And for you good sir, a cookie mountain:

CarRepairer wrote:I put chili in evo and said I would document what I did, but I have no idea what I did. I just kept adding files from CA and removing files from evo until the errors stopped screaming at me.

Aw.. No tutorial is on the way.

I was pretty shocked at chilli being so hard to integrate, given that a lot of it is well written. So I tried implemented it myself, here are the steps:

Step 1) Copy in LuaUI\Widgets\api_chili.lua and LuaUI\Widgets\chilli folder.
Step 2) Add 'newproxy = newproxy,' to the 'System' table in LuaUI\system.lua

Done. At least the simple chilli_selections widget works with chilli-style window/bars/etc showing up perfectly.