#Halomd cli server full#
#Halomd cli server code#
#Halomd cli server Pc#

The Xilium.CefGlue project provides full Chrome embedding for Windows, and I will look into Mac options. I could host a local webserver using Python, then connect with an embedded WebKit view. Since the XML plugins will be defining how Python can edit metadata, I think I will use XML plugins solely for defining what edits can be made, and allow editor customization through HTML instead. Lastly, I have been thoroughly impressed by the d3.js library and would love some way to create HTML5-based design of editor controls. With that library it is possible to create Mac GUIs with only Python. The Mac GUI is in territory that's more uncharted for me, but nil from MGM has informed me about the PyObjC library which allows seamless Python-ObjC interop. I will also investigate embedding a Python REPL. With a combination of Cython and C++/CLI I will expose Python datatypes to C# and create a GUI which allows some manner of editing tags. I have more experience with WPF, and I like the concept of 'data-binding' that it so readily supports. Once the Python scripting API is in a workable state, I will investigate creating a GUI. I will be looking into exposing some sort of usable REPL, maybe using IPython.

My goal here is to recreate the functionality of traditional meta editors and reference swappers, but to expose it through a scripting interface.ДЄt this point, LeafLock will be no more than a cross-platform Python script. These classes will allow interpretation of raw metadata as the tags we are used to: weap, bipd, effe, etc. I intend to use Python's lxml library to read and interpret Entity plugins and define Python classes based on them. The next step is to allow Entity-style plugin support. These objects rely on a 'ByteAccess' interface which can be reimplemented to allow editing on-disk as well as in Halo's memory, just as with Quickbeam. Cython objects (half C, half Python) use these structs to expose Halo datatypes to the Python environment.

#Halomd cli server code#

Here is where development currently stands: Using the Cython C-extensions for Python, I have created code which reads in raw data and interprets it as C-structs. Moving forward, the project will be primarily authored in Python and will be given the name LeafLock, the common tongue translation of the Finglas the ent's name. I'm actually surprised it survived so long. I gave the project that name because it was intended to read Entity-style plugins (.ent) and was originally a hastily thrown-together experiment. He got his name when Treebeard declared him 'hasty' for answering a question before another ent had finished asking it. Quickbeam was named after the common tongue translation of the name of Bregalad the ent. It will be in the vein of Quickbeam, but designed to be cross-platform compatible with Mac computers. In light of all this cross-pollination between communities (as well as the need to make breaking changes in my Quickbeam project) I am beginning a new project.

#Halomd cli server Pc#

HaloMD is compatible with regular Halo for the PC (so long as everyone uses the same maps), so we over at have been playing games with MGM members for a few weeks now.

HaloMD also comes with an alternate list of servers which host HaloMD-compatible maps and mods. Because the original Halo Demo for Macs was for PPC processors only, HaloMD was created to run on the Intel Macs. The folks over at have developed a Halo Demo replacement called HaloMD or Halo 'Mini Demo'. (And I want to talk about my new project ) Hey everyone! I know you guys are basically H2+ devs, but I thought you might like to be kept in the loop about recent H1 community happenings.