Print

[BenJeremy]

Very strange indeed, however, I did clean up a few more things in the code involved with ActionDraw lists, so hopefully the next WIP will clean things up.

[BenJeremy]

WIP 1205 is now up.

Nothing much new, outwardly. See if this cleans up the issues you've been having, though.

I've started integrating the XSM/RSM/ZSM plug-n-play stuff. The current routine is having a brainfart over RSM (rar) modules, but picks up XSM and ZSM modules so far. It reads the XSM (unzipping to a temporary directory, for ZSM and RSM) and gets the important information out of it. If it unarchived anything, it removes the temporary directory from Z:

This version will also automatically "install" any XAS files in the MXM directory.



In the future, users will dump modules into a plug-n-play directory, and when MXM reboots, it will "install" all new modules, and prompt for the dispensation of any existing modules that have already been installed (an upgraded module, for example). The Plugins directory will then be ceaned of any "installed" modules, which will be moved into a PnP Repository. They each get their own directory, based on their GUID, with all files from the module unzipped into their repository home directory.

Users will then be able to select if they wish a particular plugin to be "active" by selecting in a dialog (they can also delete the module out of the system, too).

The XSM file is an XML format file, containing information about the module, scripts required, and even data nodes for dialogs and other stuff. It will also tell MXM what files may be used from the archive (required or optional). RSM and ZSM modules are Rar'd or Zipped archives. The base name of the module is expected to be the base name of the XSM archived in that file.



Once I have it in place, skins modules will work in a similar fashion.

[koldfuzion]

wow, its going to take me a little bit to digest all that,  cool as hell, but i think like a 8086.

[koldfuzion]

1205

WIP Message Bug seems fixed,  I let mine close itself, and also pressed a button to escape it and it never locked.  This is without any autoexec running too.

[koldfuzion]

1205

internal HTTP test script (using an invalid url) returns 404 error fine, but locks the box.

just a FYI for testing,  im not sure if its the bad url, or the result code that might be messing it up.  Im not using any result vars, but rather checking for existance and downloaded filesize in the Content Download script,  so it might be the use of the result var.

[flattspott]

Do this mean I should re-read the Script whitepaper so I can brush up on the XSM stuff?

[flattspott]

Edit: forgot we had a new WIP Bug specific forum.

[flattspott]

[flattspott]

1205:

Something got broke. The Benchmark.xas will lock up your Xbox. Using the Concept.B skin or MXM Tivo skin since they both have semi-transparent system and message box colors, you can see the "Please wait" messagebox behind the results MsgBox. Then when you press a button to close the results box the please wait one stay and locks up the Xbox

[flattspott]

1205:

Something's going on with the Context stuff now.
When you try to go to About for a game or what-have-you it'll lock up the Xbox.

[BenJeremy]

QUOTE (flattspott @ May 13 2004, 12:21 AM)

Do this mean I should re-read the Script whitepaper so I can brush up on the XSM stuff?

It's a start.... I haven't finalized it, and I have asked for further input from you guys.

I will also look into the Benchmark.xas issue not working.

[flattspott]

QUOTE

I will also look into the Benchmark.xas issue not working

I just found out that it's not just the Benchmark.xas. The TestScript.xas does the same thing too, and now my demo script freezes at the end as well.

[flattspott]

The XSM stuff doesn't seem to work at all. I put the XSMTest.XSM file in both $ActualPath$XSMTest.XSM and $ActualPath$\Scripts\XSMTest.XSM

[BenJeremy]

Well, the XSM stuff isn't finished....  some of the stuff to intsall it is present in the latest release, while more is present in the version I'm working on.


Sometimes it's all baby steps. I have to make sure the installation is done right. XSM's are a collection of script(s) and data (and files). The script that gets executed will be named by the XSM's attributes. I haven't worked out all the fine details yet, but they are rapidly forming, as I creep through each step (for example, working out the way the archived files get unzipped and placed, as well as how the "repository" works.)

Once I have the installation nailed, I'll worry about running them.

[BenJeremy]

OK, WIP 1207 is up, seems to run fairly stable.

LightOut (at least the version I'm running) complains about reusing Overlay on the second round. Not sure what that's all about, and I didn't have time to look at the script.

At any rate, I ran it in Release mode with Tetris, Demo, LightsOut, Concentration, Benchmark, and ColorSelector.

I modified the way I deleted the handles at the end of the script.


More done towards "installing" XSM files to the repository. If it finds files in <MXMPath>\Plugins it will attempt to create a repository directory in U:\XSM\

For some reason, it isn't saving the repository index XML file yet.  Tomorrow I expect to have time to figure out the last of the XSM/ZSM/RSM install problems and will have a functional install procedure in place, then the fun stuff begins - working out the actual execution of XSM scripts!