<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
<div><span style="font-size: 13.3333px">Hi Dave.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Pardon me for not providing the appropriate argumentation. :-) Yes, we should keep on watching out for image bloat, but not by keeping essential packages/projects out of the trunk. Instead, we should minimize dependencies and make sure that projects can be unloaded on-the-fly if somebody needs to shrink the .image file.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Supporting web requests and their common content/mime types feels like supporting various character encodings when reading a text file. Among the common mime types, there are:</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">text/plain</span></div><div><span style="font-size: 13.3333px">text/html</span></div><div><span style="font-size: 13.3333px">text/csv --- external project, cross-smalltalk compatible</span></div><div><span style="font-size: 13.3333px">text/xml</span></div><div><span style="font-size: 13.3333px">application/xml</span></div><div><span style="font-size: 13.3333px">application/json --- external project, effectively Squeak only?</span></div><div><span style="font-size: 13.3333px">application/zip</span></div><div><span style="font-size: 13.3333px">application/gzip</span></div><div><span style="font-size: 13.3333px">image/gif</span></div><div><span style="font-size: 13.3333px">image/jpeg</span></div><div><span style="font-size: 13.3333px">image/png</span></div><div><span style="font-size: 13.3333px">image/svg+xml --- external project, cross-smalltalk compatible (?)</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">There is already support for plain text, html, xml, (g)zip, gif, jpeg, png in Trunk. There is also support for json in Trunk because of WebClient/WebUtils.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">My impression is that both external JSON implementations are used by Squeak projects only:</span></div><div><span style="font-size: 13.3333px">(1) http://www.squeaksource.com/JSON</span></div><div><span style="font-size: 13.3333px">(2) http://squeaksource.com/PostgresV3/JSON-ul.56.mcz</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">So, it makes sense to unify those. Not having support for JSON in Trunk by default makes no sense considering that we do support XML by default. It would be more consistent to also keep JSON in Trunk. Just make it better.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">In case that either (1) oder (2) support also other Smalltalk systems, I would rather not want to migrate those projects into Trunk. Levente? Tony? You might know more about this. </span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Best,</span></div><div><span style="font-size: 13.3333px">Marcel</span></div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 07.07.2021 01:34:07 schrieb David T. Lewis <lewis@mail.msen.com>:</p><div style='font-family:Arial,Helvetica,sans-serif'>If it is already stable, high quality, and useful, then why does it<br>need to be in trunk? This seems like exactly the kind of package that<br>we want to be easily found and installed through something like SqueakMap.<br><br>Or maybe it would be better to handle it like the git tooling by making<br>JSON an installation option in the Preference Wizard.<br><br>I am perfectly happy if JSON is added to trunk, but I do want to point<br>out that we are not very consistent in these matters. One day we are<br>complaining about image bloat and lack of modularity, and the next day<br>we're all trying to add our favorite packages into trunk. We can't<br>have it both ways.<br><br>Dave<br><br><br>On Tue, Jul 06, 2021 at 03:06:29PM +0200, Marcel Taeumel wrote:<br>> Hi all!<br>> <br>> I think it would be nice to have JSON as part of Squeak Trunk. This would make parsing the content of web requests easier. Recently, I got lucky to find the last-modified date in the HTTP header for the public TravisCI badge. But usually, one would have to query the official endpoint/API to then get XML or JSON content.<br>> <br>> http://www.squeaksource.com/JSON<br>> <br>> <br>> What do you think? The project is<br>> + Self-contained<br>> + Stable since 2016<br>> + Not that big<br>> o Adding the extension #jsonWriteOn: to the system<br>> <br>> Latest maintainers seem to be:<br>> Hannes Hirzel (hjh, 2010)<br>> Levente??Uzonyi (ul, 2010)<br>> Tony Garnock-Jones (tonyg, 2016)<br>> Fabio Niephaus (FabN, 2016)<br>> <br>> Best,<br>> Marcel<br>> <br><br><br></div></blockquote>
</div></body>