mirror of
https://github.com/qelectrotech/qelectrotech-source-mirror.git
synced 2026-10-13 16:34:14 +02:00
ispyisail
cbaf40000c
Fourth stage of the zipped project file (#1440), format 2: what an engineer would put in a list -- folio title-block fields and properties, project properties, a symbol's uuid, type, prefix, information and links, a wire's ends, number, function, colour, section, cable and bus -- moves out of the XML into project.sqlite in the .qetz, and lives only there. The folio files keep where things are drawn. On opening it goes back into the document before the usual reader runs, so nothing else in QElectroTech changes yet (the program reading the database directly is the next step of the roadmap). Each moved item keeps a key in the XML (qetz-key: its uuid where unique); each moved block leaves a marker where it was, which keeps the whitespace around it apart. A block of a shape this does not model stays in the XML. A file is untrusted: the database is read with trusted_schema off, query_only, and only from names that are plain tables. Format 2 readers still open format 1; a format 1 reader refuses format 2. Tests (tst_qetcontainer): every example back exactly, whitespace included; databaseHoldsTheData (industrial.qet: the folio files hold no information, links, wire numbers or properties; the row counts match). Outside ctest: 341 of 341 projects QET can open give the same .qet through a format 2 .qetz. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Wga9B92BNurDEtxxtCDxf
45 lines
1.7 KiB
C++
45 lines
1.7 KiB
C++
/*
|
|
Copyright 2006-2026 The QElectroTech Team
|
|
This file is part of QElectroTech.
|
|
|
|
QElectroTech is free software: you can redistribute it and/or modify
|
|
it under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation, either version 2 of the License, or
|
|
(at your option) any later version.
|
|
|
|
QElectroTech is distributed in the hope that it will be useful,
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
GNU General Public License for more details.
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
along with QElectroTech. If not, see <http://www.gnu.org/licenses/>.
|
|
*/
|
|
#ifndef QETCONTAINERDB_H
|
|
#define QETCONTAINERDB_H
|
|
|
|
#include <QByteArray>
|
|
#include <QDomElement>
|
|
|
|
/**
|
|
@brief The QetContainerDb namespace
|
|
The engineering data of a project, moved between its document and the
|
|
project.sqlite of a .qetz: what a folio's title block says, a symbol's
|
|
information, a coil's contacts, a wire's ends and number. In a .qetz
|
|
these live only in the database; the folio files keep where things are
|
|
drawn. extract() takes them out of the document into a database,
|
|
restore() puts them back, so that restore(extract(d)) is d.
|
|
|
|
Each moved item leaves its key in the document (qetz-key, qetz-folio):
|
|
its uuid where that is unique, else a made-up one. A block of a shape
|
|
this does not model -- a value holding elements, say -- stays in the
|
|
document, so nothing can be lost by moving.
|
|
*/
|
|
namespace QetContainerDb
|
|
{
|
|
QByteArray extract(QDomElement project, QString *error = nullptr);
|
|
bool restore(QDomElement project, const QByteArray &database, QString *error = nullptr);
|
|
}
|
|
|
|
#endif // QETCONTAINERDB_H
|