qjson-devel Mailing List for QJson
Brought to you by:
flavio_castelli
You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(10) |
Aug
|
Sep
(4) |
Oct
(2) |
Nov
(7) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(4) |
May
(3) |
Jun
|
Jul
(4) |
Aug
(3) |
Sep
(5) |
Oct
(4) |
Nov
(5) |
Dec
(5) |
2011 |
Jan
(3) |
Feb
(11) |
Mar
(1) |
Apr
(8) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(17) |
Sep
(7) |
Oct
(4) |
Nov
(2) |
Dec
(5) |
2012 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
(1) |
May
(3) |
Jun
(4) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
(26) |
Dec
|
2013 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2017 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jonathan W. <jf...@tp...> - 2017-02-26 19:58:32
|
I found http://qjson.sourceforge.net/docs/index.html which explains some of how to use QJson but what I cant find is documentation on what header files I need to include in my code and what I need to add to the build system (DEFINES, CFLAGS, CXXFLAGS, INCPATH, LFLAGS and LIBS) to add QJson to the project, can anyone help me out? The code I am working with is already linking to QT 4.7 so that's taken care of. |
From: Nithin C. <ni...@em...> - 2015-12-15 06:14:50
|
Hi All, I am new to QT. I am working on project which uses qt-extended-4.4.3. In this project i want get from rest api which gives data in JSON format and put into databse. Is there anyway i can use qjson in my project i.e. i don't want to install qjson but i want use it as a part of my code. Is it possible. And if possible, i want to decode data from json file which is in array format rather than object. Please anyone help me ASAP! Thanks & Regards, *M. Nithin Chakravrthi* Software Engineer *EmbDes Technologies Pvt Ltd* #124,2nd Floor,Hosur Main Road, Madiwala,| Bangalore-68 | Karnataka, India Tel: 080-25537562 | Mob: +91-8050597236 *Website <http://www.embdestech.co.in> | Email <ni...@em...> | Map <https://www.google.com/maps?f=q&source=embed&hl=en&geocode&q=EmbDes+Technologies+Bangalore&aq&sll=37.0625,-95.677068&sspn=30.185946,66.533203&ie=UTF8&hq=EmbDes+Technologies&hnear=Bengaluru,+Karnataka,+India&ll=12.915675,77.623311&spn=0.123032,0.063246&t=m>* |
From: Nithin C. <ni...@em...> - 2015-12-14 12:33:52
|
Hi All, I am new to QT. I am working on project which uses qt-extended-4.4.3. In this project i want get from rest api which gives data in JSON format and put into databse. Is there anyway i can use qjson in my project i.e. i don't want to install qjson but i want use it as a part of my code. Is it possible. And if possible, i want to decode data from json file which is in array format rather than object. Please anyone help me ASAP! Thanks & Regards, *M. Nithin Chakravrthi* Software Engineer *EmbDes Technologies Pvt Ltd* #124,2nd Floor,Hosur Main Road, Madiwala,| Bangalore-68 | Karnataka, India Tel: 080-25537562 | Mob: +91-8050597236 *Website <http://www.embdestech.co.in> | Email <ni...@em...> | Map <https://www.google.com/maps?f=q&source=embed&hl=en&geocode&q=EmbDes+Technologies+Bangalore&aq&sll=37.0625,-95.677068&sspn=30.185946,66.533203&ie=UTF8&hq=EmbDes+Technologies&hnear=Bengaluru,+Karnataka,+India&ll=12.915675,77.623311&spn=0.123032,0.063246&t=m>* |
From: Senthamizh C. <con...@gm...> - 2015-08-18 13:44:29
|
Hi, I am currently working on an x86 debian machine (Wheezy version). My application uses the qjson library for parsing JSON strings and so on. Currently the qjson version installed is 0.7.1. Can the qjson version be upgraded to 0.8 version under the same environment i.e Wheezy debian version? Thanks.. regards, Sen |
From: Navani K. S. <NAVANI.Srivastava@LntTechservices.com> - 2014-09-02 06:20:19
|
Hi, I want to know if qjson recipe (.bb file) is available for Yocto integration? Any information related to yocto integration will be helpful.. Thanks Navani Srivastava L&T Technology Services Ltd www.LntTechservices.com<http://www.lnttechservices.com/> This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. |
From: Serguey K. <s.x...@gm...> - 2014-08-28 08:40:55
|
Some text editors like to insert BOM character at the begining of document. It is legal and useful, invisible by most editors/viewers, it quite difficult to remove it from file but parser stops on it. It seems to be a bug not a feature. My configuration: Fedora 20, library is installed frome rpm package Name : qjson Arch : x86_64 Version : 0.8.1 Release : 3.fc20 |
From: ChannareddyAdaragunchi <Channareddy.Adaragunchi@LntTechservices.com> - 2014-07-31 06:44:52
|
Hi, I am using qjson 0.8.1 library with qt-4.8.1 in our project. I need to form a qjson data format which has nested array elements as shown below using QVariantList and QVariantMap using serilize function provided by qjson 0.8.1 library. { "Mode": "Initialising", "Type": "Init", "Warnings": [ { "AlertId": "XXXX", "Text": "", "Alert": "" }, { "AlertId": "XXXX", "Text": "", "Alert": "" } ], "Cautions": [ { "AlertId": "XXXX", "Text": "", "Alert": "" }, { "AlertId": "XXXX", "Text": "", "Alert": "" } ], }. I am able to form simple json data like below: [ { "Mode": "Initialising", "Type": "Init" } ] Please do the needful ASAP. Thanks in advance!!! Thanks & Regards, Channareddy A L&T Technology Services Ltd www.LntTechservices.com<http://www.lnttechservices.com/> This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. |
From: Casey D. <ca...@qn...> - 2014-05-12 15:36:41
|
Hello, I am trying to install Qjson on my terminal, and I get an error at the make stage that does not allow me to proceed QNXWS9011:build cadoyle$ make CMake Warning at /opt/local/share/cmake-2.8/Modules/Platform/Darwin.cmake:179 (message): Ignoring CMAKE_OSX_SYSROOT value: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk because the directory does not exist. Call Stack (most recent call first): /opt/local/share/cmake-2.8/Modules/CMakeSystemSpecificInformation.cmake:36 (include) CMakeLists.txt:1 (PROJECT) Qt5 not found, searching for Qt4 -- Configuring done -- Generating done -- Build files have been written to: /Users/cadoyle/qjson-master/build [ 9%] Building CXX object src/CMakeFiles/qjson.dir/parser.cpp.o In file included from /Users/cadoyle/qjson-master/src/parser.cpp:21: In file included from /Users/cadoyle/qjson-master/src/./parser.h:24: In file included from /Users/cadoyle/qjson-master/src/./qjson_export.h:23: /opt/local/include/QtCore/qglobal.h:68:10: fatal error: 'algorithm' file not found #include <algorithm> ^ 1 error generated. make[2]: *** [src/CMakeFiles/qjson.dir/parser.cpp.o] Error 1 make[1]: *** [src/CMakeFiles/qjson.dir/all] Error 2 make: *** [all] Error 2 Any idea on how to fix this? Thanks. |
From: Flavio C. <fl...@ca...> - 2013-05-15 09:46:10
|
On 05/14/2013 07:34 PM, Adrián Chaves Fernández wrote: >> 0.8.1, which seems to be the latest¹. Version 0.8.1 is still affected by this bug. Checkout master if you want to get rid of it. Cheers Flavio |
From: Adrián C. F. <adr...@gm...> - 2013-05-14 17:34:48
|
O Martes, 14 de Maio de 2013 19:33:30 Adrián Chaves Fernández escribiu: > O Martes, 14 de Maio de 2013 17:35:24 Flavio Castelli escribiu: > > On 05/04/2013 07:43 PM, Adrián Chaves Fernández wrote: > > > I’m working on a library to interact with MediaWiki sites. Through the library, you perform a request to a MediaWiki server, which (usually) answers with JSON data. But I want to be able to let the library user know when that is not the case. > > > > > > So, I’m writing a unit test where the server answers with a non-empty string that is clearly *not* JSON. I was expecting that the parser would turn the “ok” variable to “false” in this case, however that is not what happens. Instead, the parser keeps “ok” to “true”, but a call to qCritical() is made. This is the code: > > > > Which version of qjson are you using? This problem has been fixed on master. > > 0.8.1, which seems to be the latest¹. > > — > ¹ https://github.com/flavio/qjson/tags BTW, the non-JSON code was “<?xml ?>”. |
From: Adrián C. F. <adr...@gm...> - 2013-05-14 17:33:41
|
O Martes, 14 de Maio de 2013 17:35:24 Flavio Castelli escribiu: > On 05/04/2013 07:43 PM, Adrián Chaves Fernández wrote: > > I’m working on a library to interact with MediaWiki sites. Through the library, you perform a request to a MediaWiki server, which (usually) answers with JSON data. But I want to be able to let the library user know when that is not the case. > > > > So, I’m writing a unit test where the server answers with a non-empty string that is clearly *not* JSON. I was expecting that the parser would turn the “ok” variable to “false” in this case, however that is not what happens. Instead, the parser keeps “ok” to “true”, but a call to qCritical() is made. This is the code: > > Which version of qjson are you using? This problem has been fixed on master. 0.8.1, which seems to be the latest¹. — ¹ https://github.com/flavio/qjson/tags |
From: Flavio C. <fl...@ca...> - 2013-05-14 15:36:16
|
On 05/04/2013 07:43 PM, Adrián Chaves Fernández wrote: > I’m working on a library to interact with MediaWiki sites. Through the library, you perform a request to a MediaWiki server, which (usually) answers with JSON data. But I want to be able to let the library user know when that is not the case. > > So, I’m writing a unit test where the server answers with a non-empty string that is clearly *not* JSON. I was expecting that the parser would turn the “ok” variable to “false” in this case, however that is not what happens. Instead, the parser keeps “ok” to “true”, but a call to qCritical() is made. This is the code: Which version of qjson are you using? This problem has been fixed on master. Cheers Flavio |
From: Adrián C. F. <adr...@gm...> - 2013-05-04 17:44:02
|
Hi, I’m working on a library to interact with MediaWiki sites. Through the library, you perform a request to a MediaWiki server, which (usually) answers with JSON data. But I want to be able to let the library user know when that is not the case. So, I’m writing a unit test where the server answers with a non-empty string that is clearly *not* JSON. I was expecting that the parser would turn the “ok” variable to “false” in this case, however that is not what happens. Instead, the parser keeps “ok” to “true”, but a call to qCritical() is made. This is the code: bool ok = false; data = parser.parse(QString("<?xml ?>").toUtf8(), &ok).toMap(); if (!ok) { // I was expecting the code to get here. } else { // Instead, here we are. } An the output goes: QSYSTEM: ReplyTest::incorrectJSON() JSonScanner::yylex - unknown char, returning -1 So, is there any other way that I can check whether or not the string is valid JSON? Or do I have to somehow catch that call to qCritical()? Many thanks, Adrian |
From: <luk...@em...> - 2013-03-15 12:44:10
|
Hey there, I really like this library and it's really easy to use. Sadly somehow something doesn't want to work and I don't understand why. I have a class called 'Message', Message contains two private QVariantMaps, one called Header, the other Data. I exported both QVariantMaps as a Q_PROPERTY. If I serialize the class, I get a valid JSon string: { "Data" : { "Code" : 0, "Message" : "Hello, OK" }, "Header" : { "SubType" : "Error", "Type" : "Message" }, "ID" : "" } When I try to parse it back I get the following error: Number is out of range: 0 json_parser - syntax error found, forcing abort, Line 1 Column 1 I don't understand what's wrong here. Code itself is typed as int. But when I type it as an enum I get the same error. So I guess the Json parser has problems with integers itself, because enums get serialized as integers too. I serialize/parse the class like so: inline static Message * ConvertFromString(QString JSon, bool * parsed = 0) { QJson::Parser parser; QVariant Data = parser.parse(JSon.toUtf8(), parsed); if(*parsed) // I know this can lead to an error { Message * pRequest = new Message(); QJson::QObjectHelper::qvariant2qobject( Data.toMap(), pRequest ); return pRequest; } return new pimote::Message::Message(); } QString ConvertToString() { QJson::Serializer serializer; serializer.setDoublePrecision(2); serializer.setIndentMode( QJson::IndentFull ); QVariantMap Data = QJson::QObjectHelper::qobject2qvariant(this); QString Converted = serializer.serialize(Data); qDebug() << serializer.errorMessage(); return Converted; } I see no mistake here. If I replace the int with a QString it works. But well .. I want it typed correctly. Thanks in advance, have a great weekend! Greetings from Germany Lukas Möller |
From: 蔡火胜 <cai...@gm...> - 2013-03-01 04:00:49
|
Hi, I'm compiling qjson0.8.1 on a centos 5.6 i386 server. It has qt4.2.1 installed. And g++ 4.1.2. I'm doing an out-of-source build in a directory /root/temp/qjsonbil. And I get this error: [ 9%] Generating moc_serializerrunnable.cxx [ 18%] Generating moc_parserrunnable.cxx Scanning dependencies of target qjson [ 27%] Building CXX object src/CMakeFiles/qjson.dir/parser.cpp.o /root/temp/qjson-0.8.1/src/qjson_debug.h: In function ‘QNoDebug qjsonDebug()’: /root/temp/qjson-0.8.1/src/qjson_debug.h:30: error: return type ‘struct QNoDebug’ is incomplete /root/temp/qjson-0.8.1/src/qjson_debug.h:30: error: invalid use of undefined type ‘struct QNoDebug’ /usr/lib/qt4/include/QtCore/qglobal.h:1240: error: forward declaration of ‘struct QNoDebug’ make[2]: *** [src/CMakeFiles/qjson.dir/parser.cpp.o] Error 1 make[1]: *** [src/CMakeFiles/qjson.dir/all] Error 2 make: *** [all] Error 2 How to solve this? -- - no title specified 蔡火胜 手机:13267053475 邮件:cai...@gm... <mailto:cai...@gm...> 祝你身体健康、万事如意! |
From: Flavio C. <fl...@ca...> - 2013-02-10 17:00:40
|
On 02/03/2013 05:23 PM, Mostafa Razavi wrote: > I was wondering if QJson can be made to accept "undefined" as a valid > json value. I know "undefined" is not valid json but you do occasionally > encounter it in the wild, and sometimes you need to be flexible. This is not supported by QJson. I think it would make sense to implement it (like we did with some other values which are not part of json's spec but are seen in the wild). Feel free to file a bug on github or, even better, make a pull request ;) In the latter case please wait for this [1] pull request to be merged in master (or just work inside of this branch). Cheers Flavio [1] https://github.com/flavio/qjson/pull/12 |
From: Mostafa R. <hom...@gm...> - 2013-02-03 16:49:37
|
I was wondering if QJson can be made to accept "undefined" as a valid json value. I know "undefined" is not valid json but you do occasionally encounter it in the wild, and sometimes you need to be flexible. I remember that the json decoder bundled with Python standard library used to let you add "undefined" as one of the possible json built-in constants (a newer version, rewritten in C, has removed this feature), so I thought maybe the same feature lurks somewhere in QJson too. If it does, I'd appreciate it if someone can point me to the right direction. If this is not possible, it doesn't sound like a terribly difficult job to add it, perhaps as an optional feature. I think I can take on the job myself. I'm not super familiar with lex/yacc though, but I took a cursory look at the source code and I thought I could make "undefined" to act as a "null" value the same way the current source handles "null". Do you think this can find its way to the official repository? Any other thoughts or suggestions? Cheers, Mostafa |
From: Flavio C. <fl...@ca...> - 2012-11-28 08:53:39
|
On 06/14/2012 02:01 PM, Jean NAVAILLES wrote: > My property is an enum and to convert a string to that enum, I made > some changes (in red ) in qvariant2qobject. > > I don’t know if this is interesting for you? Sorry for the long delay. This change is going to be part of QJson 1.0.0. Cheers Flavio |
From: Flavio C. <fl...@ca...> - 2012-11-28 08:51:41
|
Yesterday I released qjson 0.8.1. This release ensures API and ABI compatibility with version 0.7.1 (ABI has been broken by 0.8.0 without me changing the SOVERSION). Version 1.0.0 is almost there, you can find it inside of the 1_0_0 branch. Please take a look at the changes I made to the API, I would like to hear your feedback. Cheers Flavio |
From: Lisandro D. N. P. M. <per...@gm...> - 2012-11-24 19:13:55
|
On Fri 23 Nov 2012 09:46:52 Lisandro Damián Nicanor Pérez Meyer escribió: > Note: please CC me, I'm not subscribed to the list (I've tried but I > couldn't). > > Hi everyone! While packaging 0.8.0 I've found that the API has changed in > an incompatible way, so either the SONAME should be bumped (libqjson1) or > the API fixed. > > The problem is that the symbol QJson::Serializer::serialize(QVariant > const&) has dissapeared. > > If this API entry really needs to dissapear, then SONAME should be bumped. > Else, this method should come back. > > Please feel free to ask me in case of any doubts. Hi! Looking at [0] it seems all it takes to fix the issue is to add (pseudocode): serializer.h: Serializer::serialize(foo); and define it as: serializer.cpp: serialize(foo) { serialize(foo, 0); } [0] <https://projects.kde.org/projects/kde/kdepimlibs/repository/revisions/87837df7533445d5165e35423e7a636084c1627b/diff> With that it may even keep binary compatibility. You can also mark it as deprecated and drop it in 1.0, if you want (or just keep it, I guess). Thanks! -- If you realize that you are in a hole... stop digging. Anonimous, thanks to ScottK. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ |
From: Lisandro D. N. P. M. <per...@gm...> - 2012-11-23 12:47:13
|
Note: please CC me, I'm not subscribed to the list (I've tried but I couldn't). Hi everyone! While packaging 0.8.0 I've found that the API has changed in an incompatible way, so either the SONAME should be bumped (libqjson1) or the API fixed. The problem is that the symbol QJson::Serializer::serialize(QVariant const&) has dissapeared. If this API entry really needs to dissapear, then SONAME should be bumped. Else, this method should come back. Please feel free to ask me in case of any doubts. Kinds regards, Lisandro. -- Mi experiencia me dice que lo que la gente quiere y necesita -en Indonesia, en Turquía, en Italia, en los Estados Unidos, en Brasil, en la Argentina o donde sea- es básicamente lo mismo. La gente quiere comida en la mesa, una vivienda básica, un gobierno que funcione, que en las fuerzas de seguridad haya personas confiables, a las que no tengan que tenerles miedo, educación y salud. ¡La gente de todo el mundo quiere lo mismo! Padre Thomas Michel, jesuita, especialista en diálogo interreligioso, en una entrevista de Elisabetta Piqué para La Nación, 27/09/2006. http://www.lanacion.com.ar/844069 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ |
From: Flavio C. <fl...@ca...> - 2012-11-22 10:27:50
|
On 11/22/2012 01:00 AM, Piotr Miedzik wrote: > Could someone add .pro files to master repository? I'm sorry but I decided to remove them because I didn't want to maintain two build systems. You can still grab them from git history, they have been removed with commit 66d10c44dd3b21d693933f320c32b3c9a175a693. Cheers Flavio |
From: Flavio C. <fl...@ca...> - 2012-11-22 10:20:33
|
I'm glad to announce QJson 0.8.0 has been released. For more details checkout [1] and [2]. Cheers Flavio [1] http://flavio.castelli.name/2012/11/21/qjson-0-dot-8-0-released/ [2] http://qjson.sourceforge.net/ |
From: Piotr M. <qe...@se...> - 2012-11-22 00:24:50
|
Hi. Could someone add .pro files to master repository? -- Piotr Miedzik |
From: Ralf J. <po...@ra...> - 2012-11-08 09:14:36
|
Hi, >> All we need is a guarantee that the next major release will do the cmake >> stuff the same way master does it currently - then we can go ahead and >> update our Debian-specific patches to do the same. > > I guarantee next release of qjson will ship with the cmake config files > that are currently on master. Great, thanks a lot! Kind regards, Ralf |