May 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Personal Programming onPharo

by H. Hirzel

On 5/9/18, Trygve Reenskaug <trygver(a)ifi.uio.no> wrote: > Of course not. But one of my goals is that future dynabooks will be > backwards compatible. Recent discussions have shown me that this goal is > a research project. > --Trygve Indeed [1]. And a very interesting one! Found and read your overview http://folk.uio.no/trygver/themes/Personal/PP-NIK.pdf And also the more elaborate draft of a description (50 pages) [2] http://folk.uio.no/trygver/themes/Personal/pp-index.html links to http://folk.uio.no/trygver/themes/Personal/PersonalProgramming.233.zip For my personal programming needs in Squeak so far I realized that the 'data' part is the easiest one to tackle in terms of backward compatibility. And some success in converting data to code forth and back to ease compatibility. It would be nicer of course to have a homoiconic notation [3] but still very doable. In particular as the new VMs have lifted the size constraint for the source code of in methods. --Hannes [1] An example is about the work involved to get a 17 year old 'Dynamic essay' from Squeak 3.2 to read in properly into a Squeak 6.0a trunk image http://forum.world.st/Dynamic-essay-project-MorphLayoutArticle-on-Bob-s-Sup… Quite some effort and not a full result yet... Though Squeak has some mechanisms to update classes and objects. In that thread Edgar de Cleene outlined the idea of a recursive DNU mechanism to check out earlier messages from the web http://forum.world.st/Dynamic-essay-project-MorphLayoutArticle-on-Bob-s-Sup… Needs much more elaboration ... ------------------- [2] Abstract Computer programming celebrates its platinum jubilee on the 21st of June, 2018. Exactly 70 years ago, the world's first programmer wrote the world's first program and then stored and executed it in the world's first stored program computer; affectionately known as Baby. The solitary Baby has morphed into billions of computers that are loosely connected into a single, global machine. Baby's control panel has morphed into graphical user interfaces (GUI) that empower everybody to augment their intellect. The consequences are deeply radical for individuals and society alike. A significant side effect of the GUI is that the computer has faded into the background and the user focuses on the immediate needs. We present DCI, a new programming paradigm that targets structures of communicating computers. Its goal is readable code that is so intuitive that everybody can grok it and so comprehensive that expert programmers will enjoy using it. DCI programming has been tested on real-life problems. A set of controlled experiments showed that DCI code is more readable than Java code. A new programming environment, BabyIDE, targets the single, global machine. Different GUIs support programmers having different mental models depending on their interests and proficiency. An MVC system architecture makes the program fade into the background and lets the user concentrate on satisfying his or her immediate needs. My approach is experimental. Smalltalk's universe of objects imitates the single, global machine and is my proving ground.We give two examples: one for experts and another for novices. A video1 illustrates the novice IDE. Our approach is experimental. The universe of objects found in Smalltalk's image imitates a computer network and is our proving ground. Squeak 3.10.2 is our laboratory where we experiment with various versions of BabyIDE. A great deal of work remains to make BabyIDE generally available and we are searching for a trailblazer who will take charge of it and take it out into the world. Keywords: Personal Programming, Novice Programming, Single Global Machine, IOT, Smart Home, MVC, DCI, BabyIDE, Smalltalk, Object Orientation [3] http://goran.krampe.se/2016/07/19/spry-is-a-smalltalk/ > On 09.05.2018 12:19, Marcus Denker wrote: >>> >>> >>>> I go back to Alan Kay's vision of a Dynabook: A/personal/computer >>>> for children of all ages. It should contain all its owner's >>>> /personal/data, including his or her/personal/programs, as they >>>> evolve through the years. Continuity is a must; the owner shall >>>> never loose data. >>>> >>> >> >> Do you really expect that the dynabook will be 100% backward >> compatible to Smalltalk-80? >> >> Marcus > > -- > > /The essence of object orientation is that objects collaborateto achieve > a goal. / > Trygve Reenskaug mailto: trygver(a)ifi.uio.no <mailto:%20trygver@ifi.uio.no> > Morgedalsvn. 5A http://folk.uio.no/trygver/ > N-0378 Oslo http://fullOO.info > Norway Tel: (+47) 22 49 57 27 > >

May 9, 2018

Re: [Pharo-users] #ast vs. #parseTree

by webwarrior

Richard O'Keefe wrote > First, my message was *defending* most of the short names > that someone else was attacking. For the record, I am > *far* more worried about the fragility of typical Smalltalk > code than I am about method names, which are generally > pretty good. > > ... If by "someone else" you mean me, I was obviously sarcastic. If you are OK with GCD, LCM, ULP and other abbreviations, why get rid of AST? It's well-known and unambigous term in respective area, that is also usually used as identifier in other programming languages and libraries (e.g. ast module in Python, Microsoft.FSharp.Compiler.Ast module in F#). -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 9, 2018

Re: [Pharo-users] Tonel, Pharo 6.1 and file per class?

by Herbert VojÄÃk

Esteban Lorenzano wrote: > the problem is that tonel relies in a .properties file to know a repository format. > and for backward compatibility, if this .properties file is not present, iceberg assumes the repository is a plain old âfiletreeâ repository. > > so, until we figure out how to provide both things (a nice tonel switch and backwar compatibility), the workaround is to commit a .properties file into you root repository, with this form: > > { > #format : #tonel > } > > and of course, thatâs before doing anything image-side. Yeah, that was maybe what I actually did, somehow. I faintly remember only doing something with .properties first... maybe I achieved it by getting to the newly created repo instance by some allInstances filtering and setting it to tonel format by some message send then committing it empty so .properties got there... anyway thanks for clarifying it for the next time. > cheers, > Esteban > > >> On 9 May 2018, at 12:21, herby(a)mailbox.sk wrote: >> >> Yes, it is insanely hard to write project in tonel format. Needs lot of hacking here and there, setting the setting itself is not helpful. I managed to, somehow, but I forgot the algorithm already. I am dreadful as to when I will need to do it again. Takes lots of time and nerves. >> >> Herby >> >> On May 9, 2018 11:54:56 AM GMT+02:00, Tim Mackinnon <tim(a)testit.works> wrote: >>> Hi guys - With all the talk about iceberg changes, Iâve stayed away >>> from it for a bit (6 months) - but downloaded a new 6.1 image a few >>> weeks ago and went to version some stuff yesterday into a new project. >>> >>> Iceberg seems a bit more stable - but it still seems to write out >>> individual methods as files which I thought had been changed? Am I >>> doing something wrong - or do i need to set something? >>> >>> Tim >>> >>> Sent from my iPhone >> > >

May 9, 2018

Re: [Pharo-users] Personal Programming onPharo

by Trygve Reenskaug

Of course not. But one of my goals is that future dynabooks will be backwards compatible. Recent discussions have shown me that this goal is a research project. --Trygve On 09.05.2018 12:19, Marcus Denker wrote: >> >> >>> I go back to Alan Kay's vision of a Dynabook: A/personal/computer >>> for children of all ages. It should contain all its owner's >>> /personal/data, includingÂ his or her/personal/programs, as they >>> evolve through the years.Â Continuity is a must; the owner shall >>> never loose data. >>> >> > > Do you really expect that the dynabook will be 100% backward > compatible to Smalltalk-80? > > Marcus -- /The essence of object orientation is that objects collaborateto achieve a goal. / Trygve Reenskaug mailto: trygver(a)ifi.uio.no <mailto:%20trygver@ifi.uio.no> Morgedalsvn. 5A http://folk.uio.no/trygver/ N-0378 Oslo http://fullOO.info NorwayÂ Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Tel: (+47) 22 49 57 27

May 9, 2018

Re: [Pharo-users] Tonel, Pharo 6.1 and file per class?

by Esteban Lorenzano

the problem is that tonel relies in a .properties file to know a repository format. and for backward compatibility, if this .properties file is not present, iceberg assumes the repository is a plain old âfiletreeâ repository. so, until we figure out how to provide both things (a nice tonel switch and backwar compatibility), the workaround is to commit a .properties file into you root repository, with this form: { #format : #tonel } and of course, thatâs before doing anything image-side. cheers, Esteban > On 9 May 2018, at 12:21, herby(a)mailbox.sk wrote: > > Yes, it is insanely hard to write project in tonel format. Needs lot of hacking here and there, setting the setting itself is not helpful. I managed to, somehow, but I forgot the algorithm already. I am dreadful as to when I will need to do it again. Takes lots of time and nerves. > > Herby > > On May 9, 2018 11:54:56 AM GMT+02:00, Tim Mackinnon <tim(a)testit.works> wrote: >> Hi guys - With all the talk about iceberg changes, Iâve stayed away >> from it for a bit (6 months) - but downloaded a new 6.1 image a few >> weeks ago and went to version some stuff yesterday into a new project. >> >> Iceberg seems a bit more stable - but it still seems to write out >> individual methods as files which I thought had been changed? Am I >> doing something wrong - or do i need to set something? >> >> Tim >> >> Sent from my iPhone >

May 9, 2018

Re: [Pharo-users] Tonel, Pharo 6.1 and file per class?

by herby＠mailbox.sk

Yes, it is insanely hard to write project in tonel format. Needs lot of hacking here and there, setting the setting itself is not helpful. I managed to, somehow, but I forgot the algorithm already. I am dreadful as to when I will need to do it again. Takes lots of time and nerves. Herby On May 9, 2018 11:54:56 AM GMT+02:00, Tim Mackinnon <tim(a)testit.works> wrote: >Hi guys - With all the talk about iceberg changes, Iâve stayed away >from it for a bit (6 months) - but downloaded a new 6.1 image a few >weeks ago and went to version some stuff yesterday into a new project. > >Iceberg seems a bit more stable - but it still seems to write out >individual methods as files which I thought had been changed? Am I >doing something wrong - or do i need to set something? > >Tim > >Sent from my iPhone

May 9, 2018

Re: [Pharo-users] Personal Programming onPharo

by Marcus Denker

> > >> I go back to Alan Kay's vision of a Dynabook: A personal computer for children of all ages. It should contain all its owner's personaldata, including his or her personal programs, as they evolve through the years. Continuity is a must; the owner shall never loose data. >> > Do you really expect that the dynabook will be 100% backward compatible to Smalltalk-80? Marcus

May 9, 2018

Re: [Pharo-users] Tonel, Pharo 6.1 and file per class?

by Sven Van Caekenberghe

Can't really speak for 6.1 but on 7 things are definitively Tonel based (unless you use existing/older repos). Tracking Iceberg is best done in 7 (if you can live with an actively developed system). > On 9 May 2018, at 11:54, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi guys - With all the talk about iceberg changes, Iâve stayed away from it for a bit (6 months) - but downloaded a new 6.1 image a few weeks ago and went to version some stuff yesterday into a new project. > > Iceberg seems a bit more stable - but it still seems to write out individual methods as files which I thought had been changed? Am I doing something wrong - or do i need to set something? > > Tim > > Sent from my iPhone >

May 9, 2018

Tonel, Pharo 6.1 and file per class?

by Tim Mackinnon

Hi guys - With all the talk about iceberg changes, Iâve stayed away from it for a bit (6 months) - but downloaded a new 6.1 image a few weeks ago and went to version some stuff yesterday into a new project. Iceberg seems a bit more stable - but it still seems to write out individual methods as files which I thought had been changed? Am I doing something wrong - or do i need to set something? Tim Sent from my iPhone

May 9, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Esteban Lorenzano

to talk seriously, I agree #onDNU:do: would be better called with its long name. now, well known acronyms have their place in pharo as complete, self explaining method names too. is about matter of common sense to opt for one or the other (for example, âln" is more known in maths that its âlong name" neperian logarithm). Rules and conventions are not written in stone and smart people can have an agreement on when to break them. Acronyms is this case: while *in general* using them is bad, well known acronyms as HTTP, AST, etc. are fine and even sometimes better. cheers! Esteban > On 9 May 2018, at 02:03, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > First, my message was *defending* most of the short names > that someone else was attacking. For the record, I am > *far* more worried about the fragility of typical Smalltalk > code than I am about method names, which are generally > pretty good. > > Second, the criterion was implicit but fairly clear: > if an abbreviation of any kind is sufficiently common > that someone who wants the semantics will recognise the > identifier, use it. "ulp" is MORE familiar to people > who need it than "unitOfLeastPrecision" (spit), so it is > a better name. In the same way, HTTP is a *better* name > than HyperTextWhatever (amongst other things because the > word is Hypertext, so HyperText violates a Smalltalk style > rule that says internal capitals at *word* boundaries) > because it is familiar and takes less effort to recognise > than the fully spelled out thing. > > Third, the rule as always is "intention-revealing names". > (Another Smalltalk style rule that I did not invent.) > #onDNU:do: is a confusing name because when I saw it I > expected the first argument to be a signalled exception, > not a selector. There is nothing wrong with the DNU bit; > if you know you want to catch a DNU you are probably > familiar with "DNU" (and don't want to fuss with whether > it means Does Not Understand or Did Not Understand). > As a particular example from the list, #log or > #logarithm are both ambiguous, while #ln is NOT > ambiguous (in the context of numbers), making it a > better name, > > Finally, the significant point was not where I live > (about 1/1600 of the world's population live here) > but when I went to primary school, which was somewhat > more than 50 years ago. Twenty years before that, > children learned how to calculate square roots by hand. > (Cue Four Yorkshiremen. :-)) > > > > On 8 May 2018 at 20:00, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 08.05.2018 um 05:15 schrieb Richard O'Keefe <raoknz(a)gmail.com>: >> >> #gcd: >> #lcm: >> >> These come from elementary (primary school in my day) mathematics. They are the standard names. > > You mean where you live? That excludes 90% and more of the world. So when is a abbreviation ok again? > > Norbert > >

May 9, 2018