Plan for Joshua Ritter
by Prairie Games · 01/26/2003 (10:04 am) · 0 comments
I have been back and forth and back again on the issue of content management... I am currently designing a distributed editing system with a GUI frontend. This is instead of using a web based solution(something like Zope's CMF). This stems primarily from wanting to evolve the system into a robust GAME EDITOR and not simple data entry fields on a web page. A keyword here is collaborative editing, ie. you log onto a central repository.
GUIs, GUIs, and more GUIs ... I settled on wxPython some time ago... I have been hunting thru packages looking for a decent (automated) system of generating GUIs from game classes. Generic editing of class attributes is a Very Good Thing(tm). I have evaluated quite a few packages. I was leaning towards PythonCard, but had some nagging doubt that it was best for my specific purpose(it's a GREAT package). Today I landed at wxPython's wxXmlResource ... which is a way, via XML, to describe GUI elements (at runtime if you like.
I found an excellent property class system to use (based on 2.2 properties), this week I will test out how well this system and wxXmlResource play together. I will generate GUI XML from class properties and then create the controls on the fly. This will also automatically support validation of boundries, type, editing of sub-objects, etc.
In other news, ZODB4 appears to be in a useable state... which would be great as ZODB3 has some cruft I could do without (a C extension class which is incompatible with Python 2.2 unified types for one). ZODB is a fascinating project (as is Zope3 for that matter)... one thing, theIndexedCatalog package, which supplies queries to ZODB is currently only working for v3... though, I spent 40 minutes or so on a test port to v4... I have little doubt this will be forthcoming and soon from that development team. I posted a question regarding this on their mailing list.
I spent some time considering using an Open Game system to base some test/example code off (something like d20)... though, this is probably more trouble than it is worth. We'll see... the inital release's concept of a "RPG System" may be quite minimal indeed!
-=J=-
GUIs, GUIs, and more GUIs ... I settled on wxPython some time ago... I have been hunting thru packages looking for a decent (automated) system of generating GUIs from game classes. Generic editing of class attributes is a Very Good Thing(tm). I have evaluated quite a few packages. I was leaning towards PythonCard, but had some nagging doubt that it was best for my specific purpose(it's a GREAT package). Today I landed at wxPython's wxXmlResource ... which is a way, via XML, to describe GUI elements (at runtime if you like.
I found an excellent property class system to use (based on 2.2 properties), this week I will test out how well this system and wxXmlResource play together. I will generate GUI XML from class properties and then create the controls on the fly. This will also automatically support validation of boundries, type, editing of sub-objects, etc.
In other news, ZODB4 appears to be in a useable state... which would be great as ZODB3 has some cruft I could do without (a C extension class which is incompatible with Python 2.2 unified types for one). ZODB is a fascinating project (as is Zope3 for that matter)... one thing, the
I spent some time considering using an Open Game system to base some test/example code off (something like d20)... though, this is probably more trouble than it is worth. We'll see... the inital release's concept of a "RPG System" may be quite minimal indeed!
-=J=-
