<div dir="ltr"><div>Hi Juan!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 5, 2022 at 6:34 PM Juan Vuletich <<a href="mailto:JuanVuletich@zoho.com">JuanVuletich@zoho.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div bgcolor="#ffffff">
Hi Nico,<br>
<br>
On 1/5/2022 5:12 PM, Nicolás Papagna Maldonado via Cuis-dev wrote:
<blockquote type="cite">
<div dir="ltr">I second Mariano's request!
<div><br>
</div>
<div>I don't really know what should I do to fix my packages.</div>
</div>
</blockquote>
<br>
See my response to Mariano's email. The Cuis update mechanism was
designed to make it easy to follow changes. Compare, for instance,
with .mcz non human readable files...<br></div></blockquote><div><br></div><div>Thanks for the clarification. That helped a lot to understand how these kinds of changes are merged/released.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#ffffff">
<br>
<blockquote type="cite">
<div dir="ltr">
<div>Related to that, please check an email I sent a couple of
days ago ("[Proposal] Keep a changelog").</div>
<div>I believe that would make the life of all of us who want to
improve Cuis a little easier when this kind of change happens.</div>
</div>
</blockquote>
<br>
Agreed. Anyone can volunteer to do that by following the GitHub
commits and this email list.<br>
<br>
Please keep in mind this is a volunteer community. Nobody pays for
anything, and therefore nobody is a customer. Nobody charges for
anything, and therefore nobody provides customer service. And this
is a project aimed at Smalltalk developers and serious students.
People is expected to be willing to study the system. If in doubt,
give a read to README.md in the main repo, and
CodeManagementInCuis.md in the Documentation folder.<br>
<br></div></blockquote><div><br></div><div>My apologies if what I wrote sounded like a demand (it was a proposal), that was not my intention.</div><div>Yup, I was aware of that and agree 100%. </div><div><br></div><div>Sadly, in the case of keeping a changelog, volunteering won't work IMHO. </div><div>The whole point of it is to have a single, reliable source of truth to check for breaking changes and have a summary of what changed since the last release.</div><div><br></div><div>I'd expect that people submitting changes to contribute to the changelog as well (at least that's how I see the volunteer part).</div><div>Having someone else do that doesn't sound right to me (lack of context, doubling the effort required, etc).</div><div><br></div><div>Anyways, if this is not an issue (or maybe for a few), then there is nothing to be fixed :)</div><div><br></div><div>Cheers!</div><div>Nico PM</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#ffffff">
Thanks,<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>Best,</div>
<div>Nico PM</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jan 5, 2022 at 5:09 PM
Mariano Montone via Cuis-dev <<a href="mailto:cuis-dev@lists.cuis.st" target="_blank">cuis-dev@lists.cuis.st</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
several packages of mine have stopped working on Cuis6 because
of the<br>
Morphic changes.<br>
<br>
I cannot find the email with the final changes. Is there a
list with the<br>
final changes somewhere?<br>
<br>
And can I apply the renames blindly, or almost blindly? Like
say,<br>
replace all mentions of WidgetMorph in my files with
BoxedMorph, etc, etc.<br>
<br>
Thanks!<br>
<br>
Mariano<br>
<br>
El 21/12/21 a las 16:02, Juan Vuletich via Cuis-dev escribió:<br>
> Hi Folks,<br>
> <br>
> It has become apparent that some class names I chose some
time ago are<br>
> not meaningful enough. The most confusing is the meaning
I assumed for<br>
> "Widget". Decades ago, Widget meant "UI element in some
library". Today<br>
> it means "Anything the user can interact with". So, I
want to do the<br>
> following renames:<br>
> <br>
> MovableMorph -> MorphicWidget<br>
> WidgetMorph -> GUIControlMorph<br>
> KernelMorph -> SpecialMorph<br>
> WorldMorph -> MorphicWorld<br>
> PasteUpMorph -> PlaygroundMorph<br>
> <br>
> I hope these convey meaning more effectively.<br>
> <br>
> There will be impact on some packages. I have changesets
ready to be<br>
> applied for all packages in repos in the Cuis-Smalltalk
organization.<br>
> <br>
> Before applying all this:<br>
> Do you like the new names? Do you know better ones to
suggest?<br>
> Any other thoughts?<br>
> <br>
> Thanks,<br>
> <br>
<br>
-- <br>
Cuis-dev mailing list<br>
<a href="mailto:Cuis-dev@lists.cuis.st" target="_blank">Cuis-dev@lists.cuis.st</a><br>
<a href="https://lists.cuis.st/mailman/listinfo/cuis-dev" rel="noreferrer" target="_blank">https://lists.cuis.st/mailman/listinfo/cuis-dev</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr"><br>
Nicolás Papagna</div>
</blockquote>
<br>
<br>
<pre cols="72">--
Juan Vuletich
<a href="http://www.cuis-smalltalk.org" target="_blank">www.cuis-smalltalk.org</a>
<a href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev" target="_blank">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
<a href="https://github.com/jvuletich" target="_blank">https://github.com/jvuletich</a>
<a href="https://www.researchgate.net/profile/Juan-Vuletich" target="_blank">https://www.researchgate.net/profile/Juan-Vuletich</a>
<a href="https://www.linkedin.com/in/juan-vuletich-75611b3" target="_blank">https://www.linkedin.com/in/juan-vuletich-75611b3</a>
<a href="https://independent.academia.edu/JuanVuletich" target="_blank">https://independent.academia.edu/JuanVuletich</a>
@JuanVuletich</pre>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><br>Nicolás Papagna</div></div>