destiny team mailing list archive

[Zach Elko <zachelko@xxxxxxxxx>]

...and for those interested, the code is located here:

trunk/src/Sleuths/Tools/SceneToolWidget.h/cpp

And is built andn run as such:

   1. qmake Tools.pro
   2. qmake
   3. make
   4. ./Tools

Zach J. Elko
Ball State University Unified Technology Support
Certified Hardware & Software Technician


On Sun, Mar 21, 2010 at 1:02 AM, Zach Elko <zachelko@xxxxxxxxx> wrote:

> Since I like Ian so much, I created a tool for him to assist in creating
> the Scene.xml files for all of his Sleuth's scenarios.
>
> The tool is very straightforward and is designed with ease of use and fast
> iteration in mind.
>
> The typical workflow is as follows:
>
>
>    1. Launch the application
>    2. Enter data in all of the text fields
>    3. Hit "Add Object"
>    4. Repeat Step 3 until you've added all objects for the scene. Note:
>    The field for the Scene's background image persists through each click of
>    "Add Object" because it only appears once in the XML. The app expects that
>    you set this field on the initial 'Add Object', but if you choose to change
>    that field later prior to saving, it will use the most recent value for that
>    field, so that's fine.
>    5. Once you've added all of your objects, hit "Save"
>    6. Save your file as Scene.xml in the appropriate directory for this
>    scenario
>    7. From here, you are returned to the original screen. You can begin
>    adding objects again. The next time you hit save, you'll be saving an
>    entirely different Scene.xml.
>    8. Pressing "Quit' and closing the app via the "X" do the same thing:
>    Exit without saving.
>
> This design allows you to essentially run the application once, and create
> all of your files, and be done with it. You can obviously run it as many
> times as you want, but the application gives you the ability to do
> everything at once.
>
> I've already done a good bit of testing on it, but I'm sure I've missed
> something. Let me know if you run into any issues.
>
> A few notes:
>
>    - The x and y fields must be convertible to integers. The program does
>    check for this and will display a dialog informing you of such, but just a
>    heads up.
>    - The x and y fields expect the values from Adobe. It converts the y
>    value to the proper QT value internally and writes that to file. Just enter
>    it from Adobe and forget about it.
>    - All fields must be filled in before you can Add or Save. If you hit
>    either button prior to this, nothing will happen.
>
> Zach J. Elko
> Ball State University Unified Technology Support
> Certified Hardware & Software Technician
>