[Cuis] A formal presentation to the list

[Ignacio Matías Sniechowski]

Thank you, all of you for your warm welcome.
I totally agree with you. Simplicity is nothing but one side of the coin,
being the other code quality. It's impossible to achieve a certain degree
of simplicity and elegance without good code quality.
Once thing I'm curious is about the evolution of Cuis, how was developed.
In squeak.org says that it's a fork of Squeak. But closely inspecting Cuis,
it dawn on me that may be it was build from scratch. It seems that
unloading, correcting, fixing and shrinking Cuis is much more time
consuming than -using Squeak as a guide- build from zero.
I've taken a look at Squeak 1.3 or 1.2 and it was much simpler than let's
say 3.8 or 4.4 which is impossible to follow. Pharo has lots of classes
too, but everything is very good organized and once you know what is the
purpose of package X, it's easy to concentrate on those that matter for the
project being developed. Though IMHO I really prefer "extreme modularity"
just the kernel. If you need something more, then just loaded, only those
things needed for a project.
Is there some guide or tutorial on morphic on Cuis?
Thanks in advance
Nacho



*Lic. Ignacio Sniechowski, MBA*






On Wed, Dec 11, 2013 at 8:00 AM, Casey Ransberger
<casey.obrien.r at gmail.com>wrote:

> Good to meet you! I'm in Seattle, Washington in the USA. Not terribly far
> from Ken as it happens.
>
> I did the main work around visual themes in Cuis, the original taskbar
> (which has since been replaced with something much nicer) and an odd little
> thing for moving assets in and out of the image called ContentPack. I also
> did some work to update our icons.
>
> In the future I look forward to contributing to the Morphic 3 effort, and
> to help continue Juan's earlier work with mobile devices.
>
> I was the second committer to Cuis (after Juan) and I must say that it's
> been a real joy to watch the community grow.
>
> It's a wonderful system. I think probably the strongest evidence that
> Juan's approach has been successful is that we were able to actually add
> features at the same time as removing classes and methods. Having a
> smaller, more manageable core opens up possibilities like this.
>
> Another part of this which is important to me is the idea that "the code
> is the curriculum," that the best way to make a complex system easy to
> understand and learn is to include only the highest quality code we can
> imagine, and avoid unnecessary complexity (or "complication") wherever
> possible.
>
> Glad to have you on the list, Ignacio!
>
> --Casey
>
> > On Dec 7, 2013, at 5:53 AM, nacho <0800nacho at gmail.com> wrote:
> >
> > My name is Ignacio (aka "nacho"). I'm a smalltalker apprentice, I live in
> > Buenos Aires, Argentina.
> > I came to Cuis from Squeak's homepage.
> > Instantly get identified with Juan's observations, thoughts and
> reflections.
> > It was like reading what I expect from a simple, powerful and personal
> > development system.
> > Cuis is amazing. Maybe it does not have Seaside, Roassal, Athens, etc.
> But
> > that simplicity of only one person knowing all the aspects of the system
> is
> > invaluable.
> > I work in a company and most of the software I need it's developed by
> me, so
> > knowing the system deep it's something very important for me. And build
> from
> > there.
> > Thanks Juan for developing such a wonderful Smalltalk environment.
> > Best regards
> > Nacho
> >
> >
> >
> >
> >
> > -----
> > Nacho
> > Smalltalker apprentice.
> > Buenos Aires, Argentina.
> > --
> > View this message in context:
> http://forum.world.st/A-formal-presentation-to-the-list-tp4728293.html
> > Sent from the Cuis Smalltalk mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > Cuis mailing list
> > Cuis at jvuletich.org
> > http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>
> _______________________________________________
> Cuis mailing list
> Cuis at jvuletich.org
> http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jvuletich.org/pipermail/cuis_jvuletich.org/attachments/20131211/a5829974/attachment-0004.html>