Hello Laurent and plc-user,

I've also taken an interest in the QET codebase recently. Forgive me intruding on your conversation, however unless I mis-read what Laurent says, what he writes is not my observation from the following tests:

If I open a couple of text editors: Brackets and Visual Studio, while in QET I change a wire number for example from "110" to "110A", I do not see that change reflected in either Brackets or Visual Studio, until I Save the project in QET.

Conversely, if I modify the .qet file in Brackets or Visual Studio (both the formula="110x" and num="110x" values for the wire I'm watching) I immediately see the change reflected in the other text editor, but not in QET until after closing and reopening the project.

Hope it helps - and I've not simply misunderstood or got the wrong end of the stick

Btw Laurent, as far as fundraising for essential annual project expenditure, I'd be very happy to contribute; and I'm sure no doubt many people would, if fundraising efforts were made more public. I know other opensource projects have similar annual fundraising campaigns and believe devs ought not to be spending their personal money on keeping a mature, widely-appreciated project online when they already contribute their free time. I think you only need decide whether to accept donations directly, or via a payment processing intermediary (searching "online donation platforms" turns up a plethora of providers) - and the money will surely follow.

Thank you both and all the devs for your ongoing work

I have a good job and earn my money for living and "a bit" more! 

Please spend the donated money for QET-Project!

If you wish, I can have Paypal send you some of the money we receive from donations from users who thank us for this project, given the excellent work you do.

It's certainly not a fortune (~ 500€)and I had to contribute out of my own pocket for the Aplle develloper notarization ~99€.

And in June I have to renew the web hosting at a cost of 160€.

I thanks all users who donate and hepling to support this project again, thanks all.

Best regards,
Laurent

In this case, the learning curve is not quite so steep for me: I "only" have to dive deeper into QT and QET programming!
I've hardly ever had anything to do with sqlite as a programmer.

As I said: For now I just want to understand how QET works "under the hood"... and maybe contribute some things.

"Still learning!" (even at my age )

As a user: If I make a change in the circuit diagram, where is this change saved internally? In the XML structure?
It is clear that this will (at some point) be transferred to a sqlite database in memory.

Or is it so that the sqlite DB in memory is used during editing the diagram and the XML structure is only adapted for saving?

To ask technically: (sqlite XOR XML)?   

Summary page and BOM use database:
https://github.com/qelectrotech/qelectr … s/dataBase

When you start QET and open an project QET read the XML of the project, draw all diagrams, etc, after it create an use a sqlite database in memory, you can export this database now, but you can't imported data yet to the project on the fly running.

Edit: Sqlite database for project was added recently also QET code can run without..

I would like to understand your comment better, therefore my questions.

How or in what is the internal structure of a folio stored at runtime of QET?
Is it the XML structure as it is in the resulting qet file, or is an sqlite database used internally?
Is there a place where this is documented?
Please don't say: "The source code is the documentation"

Of course, I would also like the connection information to become an internal QET generation for a cable plan or wiring instructions for the electrician at some point: I don't really like such things with python plugins! This can be quite a hassle on some systems... 
How this can/should be designed for the user is, in my opinion, of secondary importance for the time being: The internal structures need to be understood and extended.

Here's the new diff:

diff --git a/sources/qetgraphicsitem/conductor.cpp b/sources/qetgraphicsitem/conductor.cpp
index dc9d23595..df0e9fdc6 100644
--- a/sources/qetgraphicsitem/conductor.cpp
+++ b/sources/qetgraphicsitem/conductor.cpp
@@ -1048,6 +1048,7 @@ QDomElement Conductor::toXml(QDomDocument &dom_document,
        } else {
                dom_element.setAttribute("element1", terminal1->parentElement()->uuid().toString());
                dom_element.setAttribute("terminal1", terminal1->uuid().toString());
+               dom_element.setAttribute("terminalname1", terminal1->name());
        }
 
        if (terminal2->uuid().isNull()) {
@@ -1056,6 +1057,7 @@ QDomElement Conductor::toXml(QDomDocument &dom_document,
        } else {
                dom_element.setAttribute("element2", terminal2->parentElement()->uuid().toString());
                dom_element.setAttribute("terminal2", terminal2->uuid().toString());
+               dom_element.setAttribute("terminalname2", terminal2->name());
        }
        dom_element.setAttribute("freezeLabel", m_freeze_label? "true" : "false");
 
diff --git a/sources/qetgraphicsitem/terminal.cpp b/sources/qetgraphicsitem/terminal.cpp
index 54f9ece5f..272720382 100644
--- a/sources/qetgraphicsitem/terminal.cpp
+++ b/sources/qetgraphicsitem/terminal.cpp
@@ -744,6 +744,11 @@ QUuid Terminal::uuid() const
        return d->m_uuid;
 }
 
+QString Terminal::name() const
+{
+       return d->m_name;
+}
+
 /**
        @brief Conductor::relatedPotentialTerminal
        Return terminal at the same potential from the same
diff --git a/sources/qetgraphicsitem/terminal.h b/sources/qetgraphicsitem/terminal.h
index e014d2a1f..a8d22abc8 100644
--- a/sources/qetgraphicsitem/terminal.h
+++ b/sources/qetgraphicsitem/terminal.h
@@ -74,6 +74,7 @@ class Terminal : public QGraphicsObject
                Diagram  *diagram             () const;
                Element  *parentElement       () const;
                QUuid uuid                    () const;
+               QString   name                () const;
 
                QList<Conductor *> conductors() const;
                Qet::Orientation orientation() const;

The TerminalNames are only inserted into the connection, when the terminals have UUIDs ... only then!

In the element-collection I found "some" elements which have terminals with names but no UUID. Already working on them...

It's justa an idea, this would avoid having to write a plugin like qet_tb_generator in python, which reads the XML to generate the terminal blocks, and then it might be possible to do more with SQL and csv export?