<div dir="ltr">Think carefully about the name as there are currently at least 4 different VM types that can be built on 4 primary architectures (and we'll probably be starting to talk about a 5th in the next few years)</div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 16, 2021 at 2:41 PM Juan Vuletich via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st">cuis-dev@lists.cuis.st</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 7/16/2021 2:29 PM, stes--- via Cuis-dev wrote: > The reason why I am thinking of making it optional, > is because I have observed over the last weeks/months, > that the version of the plugin must match the Cuis image; > you get strange results when the plugin is installed, > and when the Cuis image expects a different version of the plugin. But this problems will happen less and less as the stuff gets mature. Soon, the only changes to the plugin will be adding new primitives. And this won't happen often. > In those cases it could be useful from the user point of view, > to have a choice between installing the VM with or without the VectorEnginePlugin. > > The name for the IPS package could be squeak-VectorEnginePlugin, > and cog-spur-VectorEnginePlugin but that is a lot of typing. > > Maybe squeak-vg and cog-spur-vg where vg would stand for vector graphics. Those are much better. Maybe v3-vg and spur-vg will be even better, if there is a need to distinguish between the plugin built for v3 and for spur VMs and images. > ----- Op 16 jul 2021 om 19:20 schreef Juan Vuletich <a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>: > >> On 7/16/2021 1:54 PM, stes--- via Cuis-dev wrote: >>> I've been packaging the VectorEnginePlugin for OpenIndiana as part of the Squeak >>> VM. >>> >>> <a href="http://docs.openindiana.org/handbook/community/squeak/index.html" rel="noreferrer" target="_blank">http://docs.openindiana.org/handbook/community/squeak/index.html</a> >>> >>> Based on my observations so far, at first I thought I'd better add it to the >>> default set of plugins. >>> >>> But now I think about making the SVG (scalable Vector graphics plugin) optional. >>> >>> The plugin could be installed by : pkg install squeak-svg >>> >>> or pkg install cog-spur-svg for the spur VM. >>> >>> Is there a serious reason NOT to call the package squeak-svg ? >>> >>> I like a short name svg better than a fully spelled out VectorEnginePlugin. >>> >>> Regards, >>> David Stes >> Hi David, >> >> I think that the plugin could be included by default in VMs, The Mac VM >> gets just 2.5% larger with it. Is there any reason for making it optional? >> >> Reasons why I wouldn't call it "squeak-svg" >> - It is not squeak specific at all. Currently there's no support for it >> in Squeak. I wouldn't prefix it with "Cuis" either, as it is not Cuis >> specific, and maybe Squeak could also use it. >> - It is not about SVG. SVG is a file format. I Cuis, the file format is >> supported by the <a href="http://SVG.pck.st" rel="noreferrer" target="_blank">SVG.pck.st</a> optional package. <a href="http://SVG.pck.st" rel="noreferrer" target="_blank">SVG.pck.st</a> requires >> VectorGraphics, but Cuis can do many things with VectorGraphics without >> using SVG files at all. I wrote <a href="http://SVG.pck.st" rel="noreferrer" target="_blank">SVG.pck.st</a> to show what >> <a href="http://VectorGraphics.pck.st" rel="noreferrer" target="_blank">VectorGraphics.pck.st</a> is capable of doing. >> >> The first name I thought was VectorGraphicsEnginePlugin, as it is the >> plugin used by the VectorGraphicsEngine class hierarchy. Then I >> preferred the shorter, but hopefully still clear VectorEnginePlugin name. >> >> I hope this makes sense to you. >> >> Cheers, >> >> -- >> Juan Vuletich >> <a href="http://www.cuis-smalltalk.org" rel="noreferrer" target="_blank">www.cuis-smalltalk.org</a> >> <a href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev" rel="noreferrer" target="_blank">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a> >> <a href="https://github.com/jvuletich" rel="noreferrer" target="_blank">https://github.com/jvuletich</a> >> <a href="https://www.linkedin.com/in/juan-vuletich-75611b3" rel="noreferrer" target="_blank">https://www.linkedin.com/in/juan-vuletich-75611b3</a> >> @JuanVuletich -- Juan Vuletich <a href="http://www.cuis-smalltalk.org" rel="noreferrer" target="_blank">www.cuis-smalltalk.org</a> <a href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev" rel="noreferrer" target="_blank">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a> <a href="https://github.com/jvuletich" rel="noreferrer" target="_blank">https://github.com/jvuletich</a> <a href="https://www.linkedin.com/in/juan-vuletich-75611b3" rel="noreferrer" target="_blank">https://www.linkedin.com/in/juan-vuletich-75611b3</a> @JuanVuletich -- Cuis-dev mailing list <a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a> <a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a> </blockquote></div>