Printable View
thinked to write to "feature request" part but reslly, it for developers only...
so, what about implement API for INTERNAL JSON parser?
Many internet resources uses it, so, what is the reason to use their own implementation in every plugins who need it?
XML was made, what about JSON now?
really, i was glad to see zlib interface too but... at least, JSON. please!
zlib interface was part of Miranda forever... Not sure what else are you looking for.
If somebody want's to code JSON parser you are welcome.
And BTW, XML API was poorly made, nobody except Jabber protocol actually using it... All other protocols/plugin still have built-in parser.
firstly, don't say "all" if you don't knows it.
secondary, WHERE is zlib support in API? you mean m_freeimage / m_imgsrvc.h ? isn't it not proper place for common functions?
i don't says what implemented XML is good but it doing what needs. JSON can be usable too. right now and maybe in future too.
[QUOTE=Awkward;213206]firstly, don't say "all" if you don't knows it.
secondary, WHERE is zlib support in API? you mean m_freeimage / m_imgsrvc.h ? isn't it not proper place for common functions?[/QUOTE]The header files are in plugins\zlib. I know it's not the proper place to store them... But it they are there.
[QUOTE=Awkward;213206]i don't says what implemented XML is good but it doing what needs.[/QUOTE]No it does not. Over complex, too slow, does not support pure UTF8 parsing with no TCHARs, even Jabber has issues with it. The code to work around them is very ugly and not full proof. ghazan promised to fix it 2 years ago never did.
[QUOTE=Awkward;213206]JSON can be usable too. right now and maybe in future too.[/QUOTE]Somebody get to volunteer to create JSON plugin.
about zlib: then i am uderstands ^_^ but maybe better to move header to more proper place?
XML is ugly, i know, i said about it long time ago. but even in form as is it still useful - "someting" better than "nothing"
not too hard to create plugin for it. world have many ready libraries. but i said about future implementation in core, like XML. before that, all right, i will ask people to implement it as plugin...
Try finding a good C library or C++ with no STL. The choice is very limited....
Actually you may try the libJSON library with my modification to fix UTF-8 characters.
Source code is available in:
[url]http://code.google.com/p/studiokuma/source/browse/#svn%2Ftrunk%2Flibjson[/url]
The checked out project is ready to build a DLL file, or you may incorporate it into your project directly.
I have already used it in 2 of my protocol projects.
starkwong, interesting ....
Awkward,
it doesn't matter if your plugin is written in Pascal or C, you can always use exported C functions from DLL.
You can download the precompiled DLL at following address:
[url]http://studiokuma.googlecode.com/files/libjson.zip[/url]
Documentation is available in previous link.
You may need to write definitions for the functions, however the JSON handle that it use is just a opaque pointer (i.e. void* in C), so it should be easy.
it ok, i will try it.
i just hoped what it will be implement as "native" miranda plugin or core module ^_^