Ask somebody in the building industry to visually communicate the architecture
of a building and you'll be presented with site plans, floor plans, elevation
views, cross-section views and detail drawings. In contrast, ask a software
developer to communicate the softwar…
This example shows how GitUML can visualise
* association with one to many
* modules containing classes
The one to many is had to detect. GitUML scans Python source code for
".append" operations and deduces its a one to many.
I use this source code as a torture test example for implementing java-nested
I (the author of GitUML) also recently added optimisations so that nest
packages with no classes would collapse into **a.b.c** etc. syntax rather than
showing one nest…
Most of the commands in Pynsource are wrapped in command objects, which have
an **execute** , undo and redo method.
This is a classic use of the Command design pattern.
This is the architecture referred to in my forthcoming article. Here is a
### Building traditional GUIs with the Entity Component System
#### Is the Entity Component System any good for building traditional GUIs?
Continuation of my Gui Showdown -- ECS vs Pl…
From my forthcoming article - here is a sample:
The Model View Controller (MVC) design pattern is…
The main app class **MainApp** is different to the App class in Pynsource \-
containing the main GUI handlers.
It points to a `umlcanvas` which is where all the fancy drawing is done, using
the wxPython GUI toolkit.
Here are some screenshots of what's possible to dra…
The App class owns an instance of Controller. The App class also has a Boot()
method, as well as a Shutdown() method.
The Controller is defined thus:
def __init__(self, app):
self.app = app
self.cmd_mgr = CommandManager(100)