Re: [fpc-pascal] Challenge accepted
Hi all, I've put some code, documentation and examples online for the serialization-library. Very rough, but I think it shows my ideas. You can find it here: https://wiki.freepascal.org/cnocstream The name, classnames etc may change. Everyone with good ideas, they are welcome. There is no support for the serialization of object-lists or collections (only arrays). Adding this might lead some large refactorings. (I'm also not sure if I'm content with the property and items classes) But please have a look. I'm off for vacation now, so I'll respond only next week. Regards, Joost. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Challenge accepted
On 15/08/2019 00:14, Joost van der Sluis wrote: Op 11-08-19 om 12:28 schreef Michael Van Canneyt: [snip] Another thing, can you help me setting up some kind of git-repository on the FPC-infrastructure? Or don't you have any plans in that direction? Regards, Joost. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal You could do that by yourself by using local svn mirror of FPC (so you don't stress orginal source if the git mirror creation goes awry) repository and subgit (https://subgit.com/> needs java (!!!) [use 64-bit one] and decent amount memory, 16GB+ is suffcient and some swap space, too). subgit saves whole SVN history beatifully and have some speed improvements and other optimizations over standard git-svn command. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Challenge accepted
Op 11-08-19 om 12:28 schreef Michael Van Canneyt: What additions are you talking about ? Can we incorporate it ? Improvements are always welcome. Maybe the ability to handle read- or write-only properties. And a flag to allow that properties which are not available in the JSON, are simply skipped. (Not by using the allow-errors flag) Note that the SQLDB rest bridge has dataset result streaming in various formats. It's somewhat similar to your goal, but is limited to datasets. Does remind me. It should also be able to stream datasets to something else. And offcourse to stream objects to a dataset. Another thing, can you help me setting up some kind of git-repository on the FPC-infrastructure? Or don't you have any plans in that direction? Regards, Joost. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Challenge accepted
On Sun, 11 Aug 2019, Joost van der Sluis wrote: Op 10-08-19 om 18:37 schreef Michael Van Canneyt: On Sat, 10 Aug 2019, Marco van de Voort wrote: Op 2019-08-10 om 17:30 schreef Joost van der Sluis: And who else wanna help? Why not simply port superobject? 2 reasons: 1. Interface based. Really bad idea. There can be a really good use for interfaces regarding streaming. Like you saw earlier in the fppkg-repository code. I think the only case when interfaces are truly needed is in IPC/RPC. For the rest it just complicates otherwise simple things. I will use them when useful, which I think is far less than commonly assumed. As such I'm violently opposed to the 'you must always program an interface' attitude. 2. JSON only. 3. I didn't really know it. You don't miss out on that. It's better than the mess Embarcadero produced, but still needlessly complicated IMHO. And if you need more reasons: the jsonrtti has just this. I still need to add some functionality to it from the restbase unit (dynamic arrays) but other than that I've been using it since ages. I use jsonrtti now, and with some additions it works like I want. But the goal is somewhat more generic, yes. I understood that, I just compared it to superobject, not to your eventual goal. What additions are you talking about ? Can we incorporate it ? Improvements are always welcome. Note that the SQLDB rest bridge has dataset result streaming in various formats. It's somewhat similar to your goal, but is limited to datasets. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Challenge accepted
Op 10-08-19 om 18:37 schreef Michael Van Canneyt: On Sat, 10 Aug 2019, Marco van de Voort wrote: Op 2019-08-10 om 17:30 schreef Joost van der Sluis: And who else wanna help? Why not simply port superobject? 2 reasons: 1. Interface based. Really bad idea. There can be a really good use for interfaces regarding streaming. Like you saw earlier in the fppkg-repository code. 2. JSON only. 3. I didn't really know it. And if you need more reasons: the jsonrtti has just this. I still need to add some functionality to it from the restbase unit (dynamic arrays) but other than that I've been using it since ages. I use jsonrtti now, and with some additions it works like I want. But the goal is somewhat more generic, yes. Regards, Joost. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Challenge accepted
On Sat, 10 Aug 2019, Marco van de Voort wrote: Op 2019-08-10 om 17:30 schreef Joost van der Sluis: And who else wanna help? Why not simply port superobject? 2 reasons: 1. Interface based. Really bad idea. 2. JSON only. And if you need more reasons: the jsonrtti has just this. I still need to add some functionality to it from the restbase unit (dynamic arrays) but other than that I've been using it since ages. Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Challenge accepted
Op 2019-08-10 om 17:30 schreef Joost van der Sluis: And who else wanna help? Why not simply port superobject? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
