The Mock Plugin for Python Dia

Goal is to simulate dia core without dia..to avoid open/close dia each time you change your python code to see the results. This can be achieved only if we have a good understanding of dia api. Making python working under Dia is not straightforward because visibility of the documentation and code sample need a deep investigation to gather the pieces of the puzzle. I have aready generated diagram with dia python having also mocked dia-python.

Luck was Chris Daley provided with his dia-test mock project which was a complementary part I built on my side. Some parts of code I agreed, some not mainly because the api was still beta and has a lot of fake/unimplemented functions left like a bottle in the sea to find a guy that could accomplish the wow in the message bottle sent by Chris hoping someone will complete the unfinished hard work. Chris Daley explained his hard times in the article “An easier way to write Python plugins for Dia”

History

• v1.0 Original version of dia-test from Chris Daley

• v1.1 (14.10.21). Chris version dia-test was not fully python3 compatible so I fixed it at this time.

• v1.2 (03.11.21) First release with mock sample and dumpObj . Limitations: it can not create dia objects and dia.py is still monolitic

• v1.3 (15.11.21) Add documentation website for python-dia 1.0.0 and this page to integrate this as the mock plugin for python dia 2.0 (coming very soon), so I changed the origin of the repos to here and mocked dia.register_action with “About DiaMock”

• v2.0 (30.12.21) Add Core and libs support. This is the first version non monolitic trying to reproduce the C files inclusion and reusing the core files produced by the core plugin to create dia objects with their default values.

Installation

1. Grab python-dia first

 git clone https://github.com/sosie-js/python-dia

1. Create the plug-ins dir if none

cd python-dia/python-dia
mkdir plug-ins

1. Get the mock Plugin from github

 git clone https://github.com/sosie-js/python-dia-mock-plugin mock

1. Simply use my helper scripts to install

cd mock
source install_python2.sh
source install_python3.sh

they are simply calling python on setup.py to install it.

Usage

1. copy the sample test/diamock.py and test/dumpObj.py into your dia user python dir $HOME/.dia/python

2. trigger it!

either bu running dia#1 or dia#2 like described in the homepage of python-dia. and watch the result in the shell console after clicking on “About DiaMock” in the help menu

OR

use Scite to trigger diamock.py

with this is updated python.properties accessible from Menu Options > Edit Properties > Open python.properties by adding the command.name.2. entries and defaulting to python2.7

if PLAT_WIN
	command.go.*.py=pythonw -u "$(FileNameExt)"
	command.go.subsystem.*.py=1
	command.go.*.pyw=pythonw -u "$(FileNameExt)"
	command.go.subsystem.*.pyw=1
	command.build.SConscript=scons.bat --up .
	command.build.SConstruct=scons.bat .

if PLAT_GTK
	command.go.*.py=python2.7 -u "$(FileNameExt)"
	command.build.SConscript=scons --up .
	command.build.SConstruct=scons .
	command.debug.*.py=python2.7 -m pdb -u "$(FileNameExt)"
	
if PLAT_MAC
	command.go.*.py=python2.7 -u "$(FileNameExt)"
	command.build.SConscript=scons --up .
	command.build.SConstruct=scons .

command.name.1.$(file.patterns.py)=Syntax Check
command.1.$(file.patterns.py)=python -c "import py_compile; py_compile.compile(r'$(FilePath)')"
command.name.2.$(file.patterns.py)=Python3
command.2.$(file.patterns.py)=python3.9 -u  "$(FileNameExt)"

OR

run from terminal directly

cd test
python2.7 diamock.py
python3.9 diamock.py

An about dialog should pop up, have a look to the credits click close and close and watch the result in the console.

Contributing

Fork my repos and use instead the dev versions to develop

source install_python2_dev.sh
source install_python3_dev.sh

-