This is part 1 of the series of posts which will come in the near future describing DAssistA & its representation as User Experience.
First of all I should explain something for the in-deep workings within DAssistA. It is nekovm based haxe runtime compiled solution where there are two (at the moment) possible entry points: command prompt & web service interface. Every peace of DAssistA as itself is a MultiModule implementation, more on that in the future. But the important thingy is that every single module in DAssistA can be at runtime modified-re-compiled-re-executed. As such module implementations are the ActionPdml module which is responsible of parsing pdml files all around the repository to their proper analogue class->method invokes.
That was in-the-box into. Now on the front:
– on left you can see the repository or so called project swarm where everything involved in project development as material resides.
- on right , opened pdml file editor-like, but with drag & drop funcs for faster & better construction of pdmls.
- on bottom empty space there will be presented all possible modules supported within DAssistA & ActionPDML parser.