Thus spake "Tim Byrne":
> First, big thanks to Tim McCaron for opening my eyes up to the automation
> that can be accomplished by chaining a slew of triggers and GKCs together.
> 
> I'd like to request a more manageable format for the buildFile,
> specifically for traits assigned to pieces.  I find it relatively easy to
> create a piece with the editor, and then duplicate many similar pieces
> with small tweaks by some alternative method (text editor, or program
> generated).  However, if I need to create a single piece (or more likely a
> prototype) with MANY similar traits this be comes quite difficult for me.
> 
> An example would be creating a prototype with 100 SendToLocation traits. 
> There's no way I will spend the time to create that within the editor. 
> When I look at the buildFile, its very difficult for me to determine what
> in the prototype definition delineates the traits.  And even if I could,
> the other problem I have is the "keys" used are not human readable.  So if
> I have one SendToLocation that is activated by ALT-CTRL-SHIFT-1, I don't
> know how to edit it to change it to ALT-CTRL-SHIFT-2.
> 
> So, I'd like to see a full XML format for the buildFile.  However, I know
> that might be a big undertaking, so I have some suggestions for some
> intermediate solutions.
> 
> 1. Use a simple delimiter for traits.  Something where a developer can
> look at a definition line, and split up all of the traits.  With that, one
> could at least copy and paste traits for an object, and then tweak them in
> the editor.
> 
> 2. Use human readable key commands, making it possible for a developer to
> change the keys for triggers, GKC, etc. with a text editor.
> 
> These two suggestions could be a stop-gap solution to a full XML format.
> 
> Would it help if I said, "pretty please"?
> 
> Cheers
> 
> Tim

I'm interested in implementing such a thing, but saying "n-pretty please"
for finite n isn't going to get me to it any sooner than I was already
planning. :)

(There are four or five small- to moderately-sized projects ahead of
that on my List of Things To Do right now.)

-- 
J.


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/vassalengine/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/vassalengine/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to