Page 1 of 1

What might an 'Asset Toolkit' look like?

Posted: Tue Oct 30, 2012 3:44 pm
by JohnWordsworth
I've got a day off work today and I've just finished X-Com. I didn't fancy diving straight in to more numbers with the GMT, so I mocked up a sample interface of what a 'Grimrock Asset Toolkit' might look like. I would envision the right hand side changing depending on the type of asset you have selected top left.
SpoilerShow
Image
I just want to be clear, I'll not likely to have time to program something like this for a long while. I aim to put all of my efforts into the GMT and making my own mod, but if the GMT becomes 'complete' at some point, then I might start work on this.

If there are any C++/C#/Java developers out there that would like to start a project like this - that would be awesome! I can share any code that's useful - such as my .lua parsing methods from the GMT and the controls I made for this mock-up (it switches the form on the right depending on which item you select).

Re: What might an 'Asset Toolkit' look like?

Posted: Tue Oct 30, 2012 9:48 pm
by LordYig
This is a great start John ! :D

The interface layout seems good, efficient and very simple at the same time.
I hope someone with programming skills will answer your call and start this kind of project !

Notepad++ is sufficiant for my own needs of LUA editing right know, but there is no doubt that this kind of tool should come handy for anyone starting modding with the Grimrock Editor.

Re: What might an 'Asset Toolkit' look like?

Posted: Tue Oct 30, 2012 11:05 pm
by Neikun
Ahaha. I like the reference to me. Cracks me up.
This looks like an excellent start to making it easy for more beginner level modders, and those who dislike writing code and those who make silly typos and end up bug tracking for hours only to find out it was a missing underscore or bracket.

Things I like a good whole lot:
  • Icon referred to what it is rather than by number. (This helps cut down on memorization)
    Option for clone object.
    I like the segregation of properties and scripts.
    being able to browse for model eliminates some of the most common typos.
I think you've just about nailed how a program like this should look.
It should contain everything you'd see in the scripting format, but more click-friendly.

Biggest plus about this format, no more accidentally deleting commas and quotation marks lol