We've added support for the first Qt types: QString and qreal.
You can now do this:

class Color : public Gpds::Serialize { public: QString name; int red; int green; int blue; virtual Gpds::Container toContainer() const override { Gpds::Container c; c.setComment("a color object"); c.addAttribute("format", "rgb"); c.addAttribute("name", name); c.addValue("red", red).addAttribute("depth", "32"); c.addValue("green", green).addAttribute("depth", "32"); c.addValue("blue", blue).addAttribute("depth", "32"); return c; } virtual void fromContainer(const Gpds::Container& c) override { // Retrieve format const QString& formatString = c.getAttribute("format").value_or("n/a"); assert( formatString == "rgb" ); name = c.getAttribute("name").value_or("n/a"); red = c.getValue<int>("red"); green = c.getValue<int>("green"); blue = c.getValue<int>("blue"); } };

Which will result in the following XML:

<color format="rgb" name="Black"> <blue depth="32">0</blue> <green depth="32">0</green> <red depth="32">0</red> </color>

There's also a Qt specific demo/example in the repo.

Isn't the world wonderful?
There's still a lot of stuff left to do tho.

If you mean outside of answering question here in forum, then no thank you. :)

I am curious then if you would like to clarify related development topics.

Do you know any higher level tools which can display structural differences between standard item models in a clear way? Have you got any experiences with “diff views” in this software area?

Adding typedef typename Container::value_type valType; to the loop helped with this issue . Thank you very much .

@Taz742 Thank you for the tip!

@TheTrueGoofy said in Read and write QBrush (QPen, QFont) as XML:

Certainly this is also quite simple to implement, but I was hoping that there is a more elegant solution.

I think the only other way is to create feature request for QtGui, or implement a Qt patch yourself - to add a QBrush::toString() method (or QTextStream overload), with a corresponding QBrush::fromString().

Another solution: Store all your data as key-value pairs in QMap<QString, QVariant> and write it to QDataStream. Next, applications will read full QMap contents from stream, then access needed values by their names.

Hi, thank you for the response!

Unfortunately, when I try to save a QList<MyStruct>, I get the following error at runtime:

QVariant::save: unable to save type 'QList<Action>' (type id: 1032). ASSERT failure in QVariant::save: "Invalid type to save", file kernel\qvariant.cpp, line 2124 Invalid parameter passed to C runtime function.

This is even though I have (after some wrestling) managed to successfully save a Action (MyStruct) using QVariant::fromValue(), having registered both Action as a metatype as well as its operators in main():

qRegisterMetaType<Action>("Action"); qRegisterMetaTypeStreamOperators<Action>("Action");

Any idea why that might be?

edit: A-ha! For future reference, it isn't needed to create custom operators for QList<MyStruct>, but it's still required to call qRegisterMetaTypeStreamOperators() on QList<MyStruct>. Solved!

@Wilk it's cool! What about JSON serialization?

I will try to use your library in my project http://forum.qt.io/topic/64999/qt-micro-rest-client-framework-beta

@mrjj Thanks)

@returnx
Ok. super. please mark as solved :)

Final note:
When you deploy,
there might be more reads for full json string.
The code you shown, will try to parse on each read. Make sure the code can
handle that it comes in blocks and not bail out if parse fails.

@SGaist Hi, However is in my plan.

Hi,

There's no ready made code to dump your model since only you know what make sense to dump. So yes you'll have to write the dumper and loader yourself. QDataStream comes to mind for that task.

Hope it helps

@SGaist
Hi SGaist,
i solved manupulating my BA manually
int bW = bitmap.value("width").toInt();
int bH = bitmap.value("height").toInt();
QString shortFileName = bitmap.value("id").toString();
QString fileName = btb::ResourceManager().getClipDir().absolutePath().append("/"+shortFileName+".png");
QByteArray ba = bitmap.value("rect").toByteArray();
QByteArray to = QByteArray();
for(int i=0; i<bWbH;i++)
{
// ARGB -> ABGR
to.append( ba[i4+3]);
to.append( ba[i4+2]);
to.append( ba[i4+1]);
to.append( ba[i4]);
}
QImage image((const unsigned char)to.data(),bW,bH,QImage::Format_RGB32);
//image.invertPixels();
image.save(fileName,"PNG");

thanks for help!

I couldn't quite believe that this could be an actual bug, so I kept testing.
And the result... oh well... I'm truly ashamed... I have included QDataStream in every file... except the one I actually tested.
So the solution is: #include <QDataStream> Facepalm
Thanks for your tips, I'm now gonna implement what you told me.