[Feedback Request] XML-Based Script Manifest Format

Discussion in 'Executive Blogs' started by Cloud, Jul 14, 2014.

  1. I'm looking for feedback in regards to the xml-based script bot manifests that we will soon be using instead of annotation-based script bot manifests.

    I am not looking for feedback in regards to whether or not we should implement it (although you are still free to express your opinions).

    Does the following format seem acceptable to you and are there any changes/options that you would like to see within it?
    Code (Text):
    2. <?xml version="1.0" ?>
    3. <manifest>
    4.     <name>XML Manifest Editor</name>
    5.     <description>A tool for making and editing xml manifests</description>
    6.     <version>1.0.0</version>
    7.     <compatibility>
    8.         <game-type>OSRS</game-type>
    9.         <game-type>RS3</game-type>
    10.     </compatibility>
    11.     <categories>
    12.         <category>Developer Tools</category>
    13.     </categories>
    14. </manifest>
    Additional elements that are not shown are:
    • tags (optional)
    • open-source (optional)
    • production (optional)
    • store-id (optional)
    • main-class (optional)
  2. I think it is nice :)
  3. Reminds me of rsbot v2...

    Look into it op, you probably want to standardize gui's if you're having these types of idea.
  4. The main reason for this change is because xml provides more flexibility and our script bot pusher could do a lot more with this data if we had it pre-compilation.

    I know about RSBot 2, but trust me we're not heading backwards.
  5. I meant with this type of idea you could do all gui's internally from runemate's options menu and save scripters the hassle creating their own.
  6. Not sure if you're serious or sarcastic... regardless we want our developers to use javafx to create a "style" for their scripts bots, we want them to be able to show their own unique flare in their scripts bots.
  7. I remind you that paint api idea you liked.
  8. I've been looking into it :) I'm debating between adding a full api for it and adding a minimalist api to support things like boxes, dragging, and buttons.

Share This Page