October 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoMinimal ?

by Pavel Krivanek

2017-10-08 19:00 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi Pavel, > > Thanks a lot for the explanation. To summarise: 70-minimal is the one with > monticello and metacello in it that can load code via the config handler. > > I was confused, because that failed for me. > > Now, first doing > > $ ./pharo pharo-minimal.image eval 'ZnMimeType initialize' > > fixed my loading problem. I also did the following because some of my > project don't separate tests (I known ;-) > > $ ./pharo pharo-minimal.image eval --save 'Object subclass: #TestCase' > > With those fixes I was able to load different projects > > $ ./pharo pharo-minimal config http://mc.stfx.eu/Neo > ConfigurationOfZTimestamp --install=stable > > $ ./pharo pharo-minimal config http://mc.stfx.eu/Neo > ConfigurationOfNeoConsole --install=bleedingEdge > > The image remains equally fast in startup > > $ time ./pharo pharo-minimal.image eval ZTimestamp now > 2017-10-08T16:55:00Z > real 0m0.062s > user 0m0.025s > sys 0m0.029s > > And it works perfectly as a server, like > > $ ./pharo pharo-minimal eval --no-quit 'NeoConsoleTelnetServer new start' & > > $ telnet localhost 4999 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Neo Console Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f > (32 Bit) > > get > known metrics: > system.status - Simple system status > memory.total - Total allocated memory > memory.free - Free memory > memory.gc - Garbage collect, return free memory > system.uptime - Image uptime human readeable > system.uptimeseconds - Image uptime seconds > system.date - Current date > system.time - Current time > system.timestamp - Current timestamp > process.count - Current process count > process.list - Current list of processes > system.version - Image version info > system.mcversions - Monticello packages version info > > get process.list > Delay Scheduling Process > Low Space Watcher > Idle Process > WeakArray Finalization Process > NeoConsoleTelnetServer port 4999 > NeoConsoleTelnetServer port 4999 Connection Handler > > SessionManager default startupList collect: #handledId > > #(#SmallInteger #Delay #ProcessorScheduler #OSPlatform #FileLocator > #MCMethodDefinition #WeakArray #FileStream #MultiByteFileStream > #EndianDetector #Symbol #LanguageEnvironment #Stdio > #NonInteractiveTranscript #WeakFinalizationList #DiskStore > #BasicCommandLineHandler #SourceFileArray #ASTCache #UUIDGenerator > #InternetConfiguration #ZnLogEvent #ZnServer #Color > #UIManagerSessionHandler #ZTimestamp) > > > Bye! > Connection closed by foreign host. > Great! > > Image size remains ~11Mb. I suppose it can be smaller with the release cleanup. > > Very nice ! > > About the class initialisations. Why were they not done already ? You seem > to have a list of them, why not make sure they are executed when creating > the image ? I guess I could rewrite some of my code to do lazy > initialization class side but I should not have to do that, should I ? > > During the baselines loading some of the initializations are done manually because of the dependencies and the mentioned classes are initialized later during Morphic loading. We should check them and move them to a proper location. -- Pavel > Sven > > > On 8 Oct 2017, at 12:41, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > Hi Sven, > > > > 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi, > > > > What is the story around PharoMinimal and related images ? > > > > Is there a writeup somewhere with instructions ? > > > > Right now the minimal (Metacello) image based on Pharo 7 is used only as > intermediate step in building of the full Pharo and the only real > (successful) attempt to use it for something else is PharoLambda ( > https://gitlab.com/macta/PharoLambda) > > > > In general it can be used for building of own (server) applications. > E.g. this way you can install and run Teapot on it: > > > > ./pharo Pharo7.0-metacello-32bit-d13eed2.image config > http://smalltalkhub.com/mc/zeroflag/Teapot/main ConfigurationOfTeapot > --install=stable > > ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval --no-quit "Teapot > on GET: '/welcome' -> 'Hello World'; start." > > > > You can load baselines from the Git repositories too but we currently do > not have any command line handler for it so you need to do it using "eval" > command or *.st flile. Something like this: > > > > Metacello new > > baseline: 'Seaside3'; > > repository: 'github://SeasideSt/Seaside:master/repository'; > > load > > > > To make it more usable we probably should extend it with SUnit and Fuel. > If you want to extend it with some packages from vanilla Pharo, you should > load them using FileTree from your local Pharo repository clone. > > > > Gofer it > > url: 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; > > package: 'Multilingual-OtherLanguages'; > > package: 'Multilingual-TextConverterOtherLanguages'; > > load. > > > > It still needs some care. E.g. some classes from Zinc are not properly > initialized (I know about DigitalSignatureAlgorithm MD5NonPrimitive > RxMatcherRxParser RxsPredicate SHA1 ZnByteEncoder ZnConstants ZnMimeType > ZnNetworkingUtils ZnServer ZnSingleThreadedServer TextConstants > TextActionTextStyle). > > > > I tried to load Seaside into it today (from the example above) and it > failed (some strange error probalby related to Unicode processing). But we > will fix it. If you will tell me what exactly you need we can make it work > together as in case of PharoLambda. > > > > > > > > I see that we get **FANTASTIC** startup speed with it: > > > > $ cat /etc/issue > > Ubuntu 16.04.3 LTS > > > > $ ./pharo --version > > 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production > Spur VM] > > CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a > Aug 27 2017 > > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > > VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > $ Date: Sun Aug 27 21:55:26 2017 +0200 $ > > Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk- > vm.git $ > > Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 > 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 > i686 i686 i386 GNU/Linux > > plugin path: /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 > [default: /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] > > > > $ curl get.pharo.org/70-minimal | bash > > ... > > > > $ ./pharo Pharo.image printVersion > > [version] 'Pharo7.0' 'Pharo-7.0+alpha.build.172.sha. > d13eed2f80fe19f29fd85ede8c4809d6a6986d4f (32 Bit)' > > > > $ time ./pharo Pharo.image eval '5 factorial' > > 120 > > real 0m0.083s > > user 0m0.034s > > sys 0m0.042s > > > > That is less than 1/10 of a second on a simple server ! Wow. > > > > Loading new code in that image seem hard though. > > > > I see that in http://files.pharo.org/image/70/ there are > Pharomonticello & Pharometacello variants. > > > > Any pointers on usage/meaning ? > > > > > > Monticello is bootstrapped Pharo image with Monticello loaded. This > image then loads Metacello and the generated image is the image that we > call "minimal". It is minimal in sense minimal for common usage. > > > > During Pharo building process we generate: > > - bootstrapped image > > - image with Opal that is loaded as binary packages using Hermes > > - Monticello with only local repositories support > > - Monticello with network and remote repositories support > > - Metacello > > - full Pharo IDE (which is loaded as sequence of several standalone > baselines) > > > > Cheers, > > -- Pavel > > > > > > Thx, > > > > Sven > > >

Oct. 8, 2017

Re: [Pharo-dev] PharoMinimal ?

by Thierry Goubier

Le 08/10/2017 Ã 18:55, Guillermo Polito a Ã©critÂ : > That's still not enough ;) That's close enough for me. > That will work when the loaded package has no dependencies. Otherwise, > imagine projects A and B, and A depending on B's release. every time you > release B you need to release all dependencies... Sort of. If when loading A, A has a correct reference to a stable B release, then that is ok. However, if B is released before A has the time to prepare a compatible version to the latest B, then, yes, that will break, but that also means A isn't properly synchronized with B (which is my point about external projects having to be synchronized). Then A may have in its baseline a check on the last B release known to be compatible... > And, if you use a tag or exact committish to get the Baseline you want > to install, still that baseline needs to point to the exact > tag/committish of it's dependencies. Agreed. You can still, in Metacello scripting, point to two (or more) repositories when loading the baseline (and then Metacello would pick the newest one), but: first, I don't know how to do it from inside a Baseline (dependencies), and, second, if filetree is used, then we loose the ability to tell which one is newest. (*) > Or! If you know the dependencies of your baseline you can explicitly use > a Metacello's lock. I still believe this is an overkill and I'd like to > simplify it, but that's what we have right now. As I said above, it seems possible if you create a level of indirection when fetching the baseline of a dependency. And saying that, I know how to do it. Within the BaselineOf itself. Thierry > On Sun, Oct 8, 2017 at 6:47 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Hi Guille, > > Le 08/10/2017 Ã 18:24, Guillermo Polito a Ã©critÂ : > > For a really high-level explanation, check the slides in here: > > https://www.slideshare.net/GuillePolito1/understanding-the-pharo-dev-proces… > <https://www.slideshare.net/GuillePolito1/understanding-the-pharo-dev-proces…> > > > Thanks for the pointers. I tried to do something in the Pharo4 days > (I still have probably somewhere a start of baselines and package to > add to a minimal pharo4 image, then the external project integration > changed and this approach would have failed...) > > Now, as Pavel says, minimal is an image with metacello (+ its > dependencies of course). > > This means that you could try to install packages on top of it > using baselines. > > > Cool. > > Still, lot of work to do in that front, mainly > Â Â - modularisation of the minimal-image packages, so we can > build even smaller images > Â Â - modularisation and baselines for all full-image packages, > so we can build incremental images on a per-user flavour > > > This is really interesting. > > This means of course > Â Â - cleaning/sorting initializations > Â Â - refactoring packages > Â Â - Uncovering hidden and runtime dependencies > Â Â - making some analyses on how space is taken (most is > methods, tons in kernel and collections ;)) > > What is not so clear yet from the top of my head: if we > distribute minimal images, how can we distribute the pharo > libraries that you can load on top of them easily. So far, > people using pharo minimal are aware that they are using an > alpha version. That means that if they want to load on top of > it, let's say, Morphic, they will need to do something like > > MetacelloÂ new > baseline: 'Morphic'; > repository: 'github://pharo-project/pharo:development/src'; > load > > But that means that we'll be loading the so called > 'bleeding-edge' of it all the time, and that version may not > correspond with the image they are using. > > This makes me think we have at some point to revisit the release > process so we can have releases internal of libraries such as > morphic, athens, fuel, etc, more often. > > > I think I can suggest a solution. When building an image on the > command line (as us Makefile users are keen to do), it is easy to > customize the additional packages/baselines you load based on some > internal state of > the image being built. > > So, for example, if you tag the minimal image when built with, say > v70123, then one can write on the command line: > > pharo/pharo pharo/Pharo.image --no-default-preferences eval --save > Metacello new baseline: \'Morphic\'\; repository: > \'github://pharo-project/pharo:\'\, SystemVersion current > buildNumber printString\, \'/src\'\; load > > Et hop, voilÃ : you get the right Morphic for the minimal image with > a minimum amount of distortion. > > If not, then it could be enough to have the short commit ID of the > pharo repository when the minimal image was built: it is enough to > get a github:// url to work. > > Well, if you keep naming your images like that: > > Pharo7.0-metacello-32bit-d13eed2.image > > Then we could even do it this way in the image building makefile > (and you don't have anything to do)(*). > > I'll have a try at it. > > Thierry > > (*) External projects would have to sort it out, still. But, IMHO, > it is a duty of an external project to be in sync if it wants to > stay external... > > On Sun, Oct 8, 2017 at 4:34 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com> > <mailto:thierry.goubier@gmail.com > <mailto:thierry.goubier@gmail.com>>> wrote: > > Â Â Hi Pavel, > > Â Â I'd probably see some interest in building the > Â Â GitFileTree-MergeDriver with it. It only requires Monticello. > > Â Â Thierry > > Â Â Le 08/10/2017 Ã 12:41, Pavel Krivanek a Ã©critÂ : > > Â Â Â Â Hi Sven, > > Â Â Â Â 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe > <sven(a)stfx.eu <mailto:sven@stfx.eu> > Â Â Â Â <mailto:sven@stfx.eu <mailto:sven@stfx.eu>> > <mailto:sven@stfx.eu <mailto:sven@stfx.eu> <mailto:sven@stfx.eu > <mailto:sven@stfx.eu>>>>: > > > Â Â Â Â Â Â Â Hi, > > Â Â Â Â Â Â Â What is the story around PharoMinimal and related > images ? > > Â Â Â Â Â Â Â Is there a writeup somewhere with instructions ? > > > Â Â Â Â Right now the minimal (Metacello) image based on Pharo > 7 is used > Â Â Â Â only as intermediate step in building of the full Pharo > and the > Â Â Â Â only real (successful) attempt to use it for something > else is > Â Â Â Â PharoLambda (https://gitlab.com/macta/PharoLambda > <https://gitlab.com/macta/PharoLambda> > Â Â Â Â <https://gitlab.com/macta/PharoLambda > <https://gitlab.com/macta/PharoLambda>>). > > > Â Â Â Â In general it can be used for building of own (server) > Â Â Â Â applications. E.g. this way you can install and run > Teapot on it: > > Â Â Â Â ./pharo Pharo7.0-metacello-32bit-d13eed2.image config > http://smalltalkhub.com/mc/zeroflag/Teapot/main > <http://smalltalkhub.com/mc/zeroflag/Teapot/main> > Â Â Â Â <http://smalltalkhub.com/mc/zeroflag/Teapot/main > <http://smalltalkhub.com/mc/zeroflag/Teapot/main>> > Â Â Â Â ConfigurationOfTeapot --install=stable > Â Â Â Â ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval > --no-quit > Â Â Â Â "Teapot on GET: '/welcome' -> 'Hello World'; start." > > Â Â Â Â You can load baselines from the Git repositories too but we > Â Â Â Â currently do not have any command line handler for it > so you > Â Â Â Â need to do it using "eval" command or *.st flile. > Something like > Â Â Â Â this: > > Â Â Â Â Metacello new > Â Â Â Â baseline: 'Seaside3'; > Â Â Â Â repository: 'github://SeasideSt/Seaside:master/repository'; > Â Â Â Â load > > Â Â Â Â To make it more usable we probably should extend it > with SUnit > Â Â Â Â and Fuel. If you want to extend it with some packages from > Â Â Â Â vanilla Pharo, you should load them using FileTree from > your > Â Â Â Â local Pharo repository clone. > > Â Â Â Â Gofer it > Â Â Â Â url: > 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; > Â Â Â Â package: 'Multilingual-OtherLanguages'; > Â Â Â Â package: 'Multilingual-TextConverterOtherLanguages'; > Â Â Â Â load. > > Â Â Â Â It still needs some care. E.g. some classes from Zinc > are not > Â Â Â Â properly initialized (I know about > DigitalSignatureAlgorithm > Â Â Â Â MD5NonPrimitive RxMatcher RxParser RxsPredicate SHA1 > Â Â Â Â ZnByteEncoder ZnConstants ZnMimeType ZnNetworkingUtils > ZnServer > Â Â Â Â ZnSingleThreadedServer TextConstants TextAction TextStyle). > > Â Â Â Â I tried to load Seaside into it today (from the example > above) > Â Â Â Â and it failed (some strange error probalby related to > Unicode > Â Â Â Â processing). But we will fix it. If you will tell me what > Â Â Â Â exactly you need we can make it work together as in case of > Â Â Â Â PharoLambda. > > > Â Â Â Â Â Â Â I see that we get **FANTASTIC** startup speed with it: > > Â Â Â Â Â Â Â $ cat /etc/issue > Â Â Â Â Â Â Â Ubuntu 16.04.3 LTS > > Â Â Â Â Â Â Â $ ./pharo --version > Â Â Â Â Â Â Â 5.0-201708271955Â Sun Aug 27 20:09:20 UTC 2017 gcc > 4.6.3 > Â Â Â Â [Production > Â Â Â Â Â Â Â Spur VM] > Â Â Â Â Â Â Â CoInterpreter VMMaker.oscog-eem.2265 uuid: > Â Â Â Â Â Â Â 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > Â Â Â Â Â Â Â StackToRegisterMappingCogit VMMaker.oscog-eem.2262 > uuid: > Â Â Â Â Â Â Â 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > Â Â Â Â Â Â Â VM: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > Â Â Â Â <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> > > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > Â Â Â Â <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>>> $ > Date: Sun > Â Â Â Â Â Â Â Aug 27 21:55:26 2017 +0200 $ > Â Â Â Â Â Â Â Plugins: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > Â Â Â Â <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> > > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > Â Â Â Â <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>>> $ > Â Â Â Â Â Â Â Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 > Â Â Â Â Â Â Â 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 > Â Â Â Â 16:47:06 UTC > Â Â Â Â Â Â Â 2017 i686 i686 i386 GNU/Linux > Â Â Â Â Â Â Â plugin path: > > /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 > Â Â Â Â [default: > > /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] > > Â Â Â Â Â Â Â $ curl get.pharo.org/70-minimal > <http://get.pharo.org/70-minimal> > Â Â Â Â <http://get.pharo.org/70-minimal > <http://get.pharo.org/70-minimal>> > Â Â Â Â <http://get.pharo.org/70-minimal > <http://get.pharo.org/70-minimal> > > Â Â Â Â <http://get.pharo.org/70-minimal > <http://get.pharo.org/70-minimal>>> | bash > > Â Â Â Â Â Â Â ... > > Â Â Â Â Â Â Â $ ./pharo Pharo.image printVersion > Â Â Â Â Â Â Â [version] 'Pharo7.0' > > 'Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f > Â Â Â Â Â Â Â (32 Bit)' > > Â Â Â Â Â Â Â $ time ./pharo Pharo.image eval '5 factorial' > Â Â Â Â Â Â Â 120 > Â Â Â Â Â Â Â realÂ Â 0m0.083s > Â Â Â Â Â Â Â userÂ Â 0m0.034s > Â Â Â Â Â Â Â sysÂ Â Â 0m0.042s > > Â Â Â Â Â Â Â That is less than 1/10 of a second on a simple > server ! Wow. > > Â Â Â Â Â Â Â Loading new code in that image seem hard though. > > Â Â Â Â Â Â Â I see that in http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/> > Â Â Â Â <http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/>> > Â Â Â Â Â Â Â <http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/> > Â Â Â Â <http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/>>> there are Pharomonticello & > Â Â Â Â Â Â Â Pharometacello variants. > > Â Â Â Â Â Â Â Any pointers on usage/meaning ? > > > Â Â Â Â Monticello is bootstrapped Pharo image with Monticello > loaded. > Â Â Â Â This image then loads Metacello and the generated image > is the > Â Â Â Â image that we call "minimal". It is minimal in sense > minimal for > Â Â Â Â common usage. > > Â Â Â Â During Pharo building process we generate: > Â Â Â Â - bootstrapped image > Â Â Â Â - image with Opal that is loaded as binary packages > using Hermes > Â Â Â Â - Monticello with only local repositories support > Â Â Â Â - Monticello with network and remote repositories support > Â Â Â Â - Metacello > Â Â Â Â - full Pharo IDE (which is loaded as sequence of several > Â Â Â Â standalone baselines) > > Â Â Â Â Cheers, > Â Â Â Â -- Pavel > > Â Â Â Â Â Â Â Thx, > > Â Â Â Â Â Â Â Sven > > > > > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - > _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 <tel:%2B33%2006%2052%2070%2066%2013> > > > > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

Oct. 8, 2017

Re: [Pharo-dev] PharoMinimal ?

by Sven Van Caekenberghe

Hi Pavel, Thanks a lot for the explanation. To summarise: 70-minimal is the one with monticello and metacello in it that can load code via the config handler. I was confused, because that failed for me. Now, first doing $ ./pharo pharo-minimal.image eval 'ZnMimeType initialize' fixed my loading problem. I also did the following because some of my project don't separate tests (I known ;-) $ ./pharo pharo-minimal.image eval --save 'Object subclass: #TestCase' With those fixes I was able to load different projects $ ./pharo pharo-minimal config http://mc.stfx.eu/Neo ConfigurationOfZTimestamp --install=stable $ ./pharo pharo-minimal config http://mc.stfx.eu/Neo ConfigurationOfNeoConsole --install=bleedingEdge The image remains equally fast in startup $ time ./pharo pharo-minimal.image eval ZTimestamp now 2017-10-08T16:55:00Z real 0m0.062s user 0m0.025s sys 0m0.029s And it works perfectly as a server, like $ ./pharo pharo-minimal eval --no-quit 'NeoConsoleTelnetServer new start' & $ telnet localhost 4999 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Neo Console Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f (32 Bit) > get known metrics: system.status - Simple system status memory.total - Total allocated memory memory.free - Free memory memory.gc - Garbage collect, return free memory system.uptime - Image uptime human readeable system.uptimeseconds - Image uptime seconds system.date - Current date system.time - Current time system.timestamp - Current timestamp process.count - Current process count process.list - Current list of processes system.version - Image version info system.mcversions - Monticello packages version info > get process.list Delay Scheduling Process Low Space Watcher Idle Process WeakArray Finalization Process NeoConsoleTelnetServer port 4999 NeoConsoleTelnetServer port 4999 Connection Handler > SessionManager default startupList collect: #handledId #(#SmallInteger #Delay #ProcessorScheduler #OSPlatform #FileLocator #MCMethodDefinition #WeakArray #FileStream #MultiByteFileStream #EndianDetector #Symbol #LanguageEnvironment #Stdio #NonInteractiveTranscript #WeakFinalizationList #DiskStore #BasicCommandLineHandler #SourceFileArray #ASTCache #UUIDGenerator #InternetConfiguration #ZnLogEvent #ZnServer #Color #UIManagerSessionHandler #ZTimestamp) > Bye! Connection closed by foreign host. Image size remains ~11Mb. Very nice ! About the class initialisations. Why were they not done already ? You seem to have a list of them, why not make sure they are executed when creating the image ? I guess I could rewrite some of my code to do lazy initialization class side but I should not have to do that, should I ? Sven > On 8 Oct 2017, at 12:41, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi Sven, > > 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi, > > What is the story around PharoMinimal and related images ? > > Is there a writeup somewhere with instructions ? > > Right now the minimal (Metacello) image based on Pharo 7 is used only as intermediate step in building of the full Pharo and the only real (successful) attempt to use it for something else is PharoLambda (https://gitlab.com/macta/PharoLambda) > > In general it can be used for building of own (server) applications. E.g. this way you can install and run Teapot on it: > > ./pharo Pharo7.0-metacello-32bit-d13eed2.image config http://smalltalkhub.com/mc/zeroflag/Teapot/main ConfigurationOfTeapot --install=stable > ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval --no-quit "Teapot on GET: '/welcome' -> 'Hello World'; start." > > You can load baselines from the Git repositories too but we currently do not have any command line handler for it so you need to do it using "eval" command or *.st flile. Something like this: > > Metacello new > baseline: 'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > > To make it more usable we probably should extend it with SUnit and Fuel. If you want to extend it with some packages from vanilla Pharo, you should load them using FileTree from your local Pharo repository clone. > > Gofer it > url: 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; > package: 'Multilingual-OtherLanguages'; > package: 'Multilingual-TextConverterOtherLanguages'; > load. > > It still needs some care. E.g. some classes from Zinc are not properly initialized (I know about DigitalSignatureAlgorithm MD5NonPrimitive RxMatcherRxParser RxsPredicate SHA1 ZnByteEncoder ZnConstants ZnMimeType ZnNetworkingUtils ZnServer ZnSingleThreadedServer TextConstants TextActionTextStyle). > > I tried to load Seaside into it today (from the example above) and it failed (some strange error probalby related to Unicode processing). But we will fix it. If you will tell me what exactly you need we can make it work together as in case of PharoLambda. > > > > I see that we get **FANTASTIC** startup speed with it: > > $ cat /etc/issue > Ubuntu 16.04.3 LTS > > $ ./pharo --version > 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production Spur VM] > CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ > Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 i686 i686 i386 GNU/Linux > plugin path: /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 [default: /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] > > $ curl get.pharo.org/70-minimal | bash > ... > > $ ./pharo Pharo.image printVersion > [version] 'Pharo7.0' 'Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f (32 Bit)' > > $ time ./pharo Pharo.image eval '5 factorial' > 120 > real 0m0.083s > user 0m0.034s > sys 0m0.042s > > That is less than 1/10 of a second on a simple server ! Wow. > > Loading new code in that image seem hard though. > > I see that in http://files.pharo.org/image/70/ there are Pharomonticello & Pharometacello variants. > > Any pointers on usage/meaning ? > > > Monticello is bootstrapped Pharo image with Monticello loaded. This image then loads Metacello and the generated image is the image that we call "minimal". It is minimal in sense minimal for common usage. > > During Pharo building process we generate: > - bootstrapped image > - image with Opal that is loaded as binary packages using Hermes > - Monticello with only local repositories support > - Monticello with network and remote repositories support > - Metacello > - full Pharo IDE (which is loaded as sequence of several standalone baselines) > > Cheers, > -- Pavel > > > Thx, > > Sven

Oct. 8, 2017

Non blurry Pharo 6.1 on Windows 10 and 4K display

by phil＠highoctane.be

Just wanted to say that one can have Pharo on a 4K display without blurry fonts. https://i.imgur.com/FDeLFTN.png This requires to use the settings with Large or Huge fonts. And create a shortcut to Pharo.exe with the following settings in the properties of that shortcut: https://i.imgur.com/7G1sEtz.png There are then other issues showing, namely that tools are opening with default extents that are way too small for a 4K screen. Maybe we should detect that or have a command line switch and update all tools so that the extent is multiplied by that factor. The cursor is also tiny, but maybe VistaCursors can help. So, a Hi-DPI screen on Windows 10 is definitely not an issue. My new laptop has such a screen so, I have got an itch to scratch to get legible and usable things on it. Icons are also too small and some items like Spotter "search" placeholder are not respecting the font sizes of the settings. https://i.imgur.com/lIAwdKx.png Anyway, no blur, yay! Check https://www.digitaltrends.com/computing/how-to-adjust-high-dpi-scaling-in-w… for more on those settings. Check Phil

Oct. 8, 2017

Re: [Pharo-dev] PharoMinimal ?

by Guillermo Polito

That's still not enough ;) That will work when the loaded package has no dependencies. Otherwise, imagine projects A and B, and A depending on B's release. every time you release B you need to release all dependencies... And, if you use a tag or exact committish to get the Baseline you want to install, still that baseline needs to point to the exact tag/committish of it's dependencies. Or! If you know the dependencies of your baseline you can explicitly use a Metacello's lock. I still believe this is an overkill and I'd like to simplify it, but that's what we have right now. On Sun, Oct 8, 2017 at 6:47 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Guille, > > Le 08/10/2017 Ã 18:24, Guillermo Polito a Ã©crit : > >> For a really high-level explanation, check the slides in here: >> >> https://www.slideshare.net/GuillePolito1/understanding-the- >> pharo-dev-process-79632181 >> > > Thanks for the pointers. I tried to do something in the Pharo4 days (I > still have probably somewhere a start of baselines and package to add to a > minimal pharo4 image, then the external project integration changed and > this approach would have failed...) > > Now, as Pavel says, minimal is an image with metacello (+ its dependencies >> of course). >> >> This means that you could try to install packages on top of it using >> baselines. >> > > Cool. > > Still, lot of work to do in that front, mainly >> - modularisation of the minimal-image packages, so we can build even >> smaller images >> - modularisation and baselines for all full-image packages, so we can >> build incremental images on a per-user flavour >> > > This is really interesting. > > This means of course >> - cleaning/sorting initializations >> - refactoring packages >> - Uncovering hidden and runtime dependencies >> - making some analyses on how space is taken (most is methods, tons in >> kernel and collections ;)) >> >> What is not so clear yet from the top of my head: if we distribute >> minimal images, how can we distribute the pharo libraries that you can load >> on top of them easily. So far, people using pharo minimal are aware that >> they are using an alpha version. That means that if they want to load on >> top of it, let's say, Morphic, they will need to do something like >> >> Metacello new >> baseline: 'Morphic'; >> repository: 'github://pharo-project/pharo:development/src'; >> load >> >> But that means that we'll be loading the so called 'bleeding-edge' of it >> all the time, and that version may not correspond with the image they are >> using. >> >> This makes me think we have at some point to revisit the release process >> so we can have releases internal of libraries such as morphic, athens, >> fuel, etc, more often. >> > > I think I can suggest a solution. When building an image on the command > line (as us Makefile users are keen to do), it is easy to customize the > additional packages/baselines you load based on some internal state of > the image being built. > > So, for example, if you tag the minimal image when built with, say v70123, > then one can write on the command line: > > pharo/pharo pharo/Pharo.image --no-default-preferences eval --save > Metacello new baseline: \'Morphic\'\; repository: > \'github://pharo-project/pharo:\'\, SystemVersion current buildNumber > printString\, \'/src\'\; load > > Et hop, voilÃ : you get the right Morphic for the minimal image with a > minimum amount of distortion. > > If not, then it could be enough to have the short commit ID of the pharo > repository when the minimal image was built: it is enough to get a > github:// url to work. > > Well, if you keep naming your images like that: > > Pharo7.0-metacello-32bit-d13eed2.image > > Then we could even do it this way in the image building makefile (and you > don't have anything to do)(*). > > I'll have a try at it. > > Thierry > > (*) External projects would have to sort it out, still. But, IMHO, it is a > duty of an external project to be in sync if it wants to stay external... > > On Sun, Oct 8, 2017 at 4:34 PM, Thierry Goubier <thierry.goubier(a)gmail.com >> <mailto:thierry.goubier@gmail.com>> wrote: >> >> Hi Pavel, >> >> I'd probably see some interest in building the >> GitFileTree-MergeDriver with it. It only requires Monticello. >> >> Thierry >> >> Le 08/10/2017 Ã 12:41, Pavel Krivanek a Ã©crit : >> >> Hi Sven, >> >> 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu> <mailto:sven@stfx.eu <mailto:sven@stfx.eu >> >>>: >> >> >> Hi, >> >> What is the story around PharoMinimal and related images ? >> >> Is there a writeup somewhere with instructions ? >> >> >> Right now the minimal (Metacello) image based on Pharo 7 is used >> only as intermediate step in building of the full Pharo and the >> only real (successful) attempt to use it for something else is >> PharoLambda (https://gitlab.com/macta/PharoLambda >> <https://gitlab.com/macta/PharoLambda>). >> >> >> In general it can be used for building of own (server) >> applications. E.g. this way you can install and run Teapot on it: >> >> ./pharo Pharo7.0-metacello-32bit-d13eed2.image config >> http://smalltalkhub.com/mc/zeroflag/Teapot/main >> <http://smalltalkhub.com/mc/zeroflag/Teapot/main> >> ConfigurationOfTeapot --install=stable >> ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval --no-quit >> "Teapot on GET: '/welcome' -> 'Hello World'; start." >> >> You can load baselines from the Git repositories too but we >> currently do not have any command line handler for it so you >> need to do it using "eval" command or *.st flile. Something like >> this: >> >> Metacello new >> baseline: 'Seaside3'; >> repository: 'github://SeasideSt/Seaside:master/repository'; >> load >> >> To make it more usable we probably should extend it with SUnit >> and Fuel. If you want to extend it with some packages from >> vanilla Pharo, you should load them using FileTree from your >> local Pharo repository clone. >> >> Gofer it >> url: 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; >> package: 'Multilingual-OtherLanguages'; >> package: 'Multilingual-TextConverterOtherLanguages'; >> load. >> >> It still needs some care. E.g. some classes from Zinc are not >> properly initialized (I know about DigitalSignatureAlgorithm >> MD5NonPrimitive RxMatcher RxParser RxsPredicate SHA1 >> ZnByteEncoder ZnConstants ZnMimeType ZnNetworkingUtils ZnServer >> ZnSingleThreadedServer TextConstants TextAction TextStyle). >> >> I tried to load Seaside into it today (from the example above) >> and it failed (some strange error probalby related to Unicode >> processing). But we will fix it. If you will tell me what >> exactly you need we can make it work together as in case of >> PharoLambda. >> >> >> I see that we get **FANTASTIC** startup speed with it: >> >> $ cat /etc/issue >> Ubuntu 16.04.3 LTS >> >> $ ./pharo --version >> 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 >> [Production >> Spur VM] >> CoInterpreter VMMaker.oscog-eem.2265 uuid: >> 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 >> StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: >> 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 >> VM: 201708271955 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> $ Date: >> Sun >> Aug 27 21:55:26 2017 +0200 $ >> Plugins: 201708271955 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> $ >> Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 >> 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 >> 16:47:06 UTC >> 2017 i686 i686 i386 GNU/Linux >> plugin path: >> /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 >> [default: >> /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] >> >> $ curl get.pharo.org/70-minimal >> <http://get.pharo.org/70-minimal> >> <http://get.pharo.org/70-minimal >> >> <http://get.pharo.org/70-minimal>> | bash >> >> ... >> >> $ ./pharo Pharo.image printVersion >> [version] 'Pharo7.0' >> 'Pharo-7.0+alpha.build.172.sha >> .d13eed2f80fe19f29fd85ede8c4809d6a6986d4f >> (32 Bit)' >> >> $ time ./pharo Pharo.image eval '5 factorial' >> 120 >> real 0m0.083s >> user 0m0.034s >> sys 0m0.042s >> >> That is less than 1/10 of a second on a simple server ! Wow. >> >> Loading new code in that image seem hard though. >> >> I see that in http://files.pharo.org/image/70/ >> <http://files.pharo.org/image/70/> >> <http://files.pharo.org/image/70/ >> <http://files.pharo.org/image/70/>> there are Pharomonticello & >> Pharometacello variants. >> >> Any pointers on usage/meaning ? >> >> >> Monticello is bootstrapped Pharo image with Monticello loaded. >> This image then loads Metacello and the generated image is the >> image that we call "minimal". It is minimal in sense minimal for >> common usage. >> >> During Pharo building process we generate: >> - bootstrapped image >> - image with Opal that is loaded as binary packages using Hermes >> - Monticello with only local repositories support >> - Monticello with network and remote repositories support >> - Metacello >> - full Pharo IDE (which is loaded as sequence of several >> standalone baselines) >> >> Cheers, >> -- Pavel >> >> Thx, >> >> Sven >> >> >> >> >> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - _http://www.cnrs.fr_ >> >> >> *Web:* _http://guillep.github.io_ >> >> *Phone: *+33 06 52 70 66 13 >> >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 8, 2017

Re: [Pharo-dev] PharoMinimal ?

by Thierry Goubier

Hi Guille, Le 08/10/2017 Ã 18:24, Guillermo Polito a Ã©critÂ : > For a really high-level explanation, check the slides in here: > > https://www.slideshare.net/GuillePolito1/understanding-the-pharo-dev-proces… Thanks for the pointers. I tried to do something in the Pharo4 days (I still have probably somewhere a start of baselines and package to add to a minimal pharo4 image, then the external project integration changed and this approach would have failed...) > Now, as Pavel says, minimal is an image with metacello (+ its > dependencies of course). > > This means that you could try to install packages on top of it using > baselines. Cool. > Still, lot of work to do in that front, mainly > Â - modularisation of the minimal-image packages, so we can build even > smaller images > Â - modularisation and baselines for all full-image packages, so we can > build incremental images on a per-user flavour This is really interesting. > This means of course > Â - cleaning/sorting initializations > Â - refactoring packages > Â - Uncovering hidden and runtime dependencies > Â - making some analyses on how space is taken (most is methods, tons in > kernel and collections ;)) > > What is not so clear yet from the top of my head: if we distribute > minimal images, how can we distribute the pharo libraries that you can > load on top of them easily. So far, people using pharo minimal are aware > that they are using an alpha version. That means that if they want to > load on top of it, let's say, Morphic, they will need to do something like > > MetacelloÂ new > baseline: 'Morphic'; > repository: 'github://pharo-project/pharo:development/src'; > load > > But that means that we'll be loading the so called 'bleeding-edge' of it > all the time, and that version may not correspond with the image they > are using. > > This makes me think we have at some point to revisit the release process > so we can have releases internal of libraries such as morphic, athens, > fuel, etc, more often. I think I can suggest a solution. When building an image on the command line (as us Makefile users are keen to do), it is easy to customize the additional packages/baselines you load based on some internal state of the image being built. So, for example, if you tag the minimal image when built with, say v70123, then one can write on the command line: pharo/pharo pharo/Pharo.image --no-default-preferences eval --save Metacello new baseline: \'Morphic\'\; repository: \'github://pharo-project/pharo:\'\, SystemVersion current buildNumber printString\, \'/src\'\; load Et hop, voilÃ : you get the right Morphic for the minimal image with a minimum amount of distortion. If not, then it could be enough to have the short commit ID of the pharo repository when the minimal image was built: it is enough to get a github:// url to work. Well, if you keep naming your images like that: Pharo7.0-metacello-32bit-d13eed2.image Then we could even do it this way in the image building makefile (and you don't have anything to do)(*). I'll have a try at it. Thierry (*) External projects would have to sort it out, still. But, IMHO, it is a duty of an external project to be in sync if it wants to stay external... > On Sun, Oct 8, 2017 at 4:34 PM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Hi Pavel, > > I'd probably see some interest in building the > GitFileTree-MergeDriver with it. It only requires Monticello. > > Thierry > > Le 08/10/2017 Ã 12:41, Pavel Krivanek a Ã©critÂ : > > Hi Sven, > > 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu> <mailto:sven@stfx.eu <mailto:sven@stfx.eu>>>: > > > Â Â Hi, > > Â Â What is the story around PharoMinimal and related images ? > > Â Â Is there a writeup somewhere with instructions ? > > > Right now the minimal (Metacello) image based on Pharo 7 is used > only as intermediate step in building of the full Pharo and the > only real (successful) attempt to use it for something else is > PharoLambda (https://gitlab.com/macta/PharoLambda > <https://gitlab.com/macta/PharoLambda>). > > In general it can be used for building of own (server) > applications. E.g. this way you can install and run Teapot on it: > > ./pharo Pharo7.0-metacello-32bit-d13eed2.image config > http://smalltalkhub.com/mc/zeroflag/Teapot/main > <http://smalltalkhub.com/mc/zeroflag/Teapot/main> > ConfigurationOfTeapot --install=stable > ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval --no-quit > "Teapot on GET: '/welcome' -> 'Hello World'; start." > > You can load baselines from the Git repositories too but we > currently do not have any command line handler for it so you > need to do it using "eval" command or *.st flile. Something like > this: > > Metacello new > baseline: 'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > > To make it more usable we probably should extend it with SUnit > and Fuel. If you want to extend it with some packages from > vanilla Pharo, you should load them using FileTree from your > local Pharo repository clone. > > Gofer it > url: 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; > package: 'Multilingual-OtherLanguages'; > package: 'Multilingual-TextConverterOtherLanguages'; > load. > > It still needs some care. E.g. some classes from Zinc are not > properly initialized (I know about DigitalSignatureAlgorithm > MD5NonPrimitive RxMatcher RxParser RxsPredicate SHA1 > ZnByteEncoder ZnConstants ZnMimeType ZnNetworkingUtils ZnServer > ZnSingleThreadedServer TextConstants TextAction TextStyle). > > I tried to load Seaside into it today (from the example above) > and it failed (some strange error probalby related to Unicode > processing). But we will fix it. If you will tell me what > exactly you need we can make it work together as in case of > PharoLambda. > > > Â Â I see that we get **FANTASTIC** startup speed with it: > > Â Â $ cat /etc/issue > Â Â Ubuntu 16.04.3 LTS > > Â Â $ ./pharo --version > Â Â 5.0-201708271955Â Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 > [Production > Â Â Spur VM] > Â Â CoInterpreter VMMaker.oscog-eem.2265 uuid: > Â Â 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > Â Â StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > Â Â 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > Â Â VM: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > Â Â <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> $ Date: Sun > Â Â Aug 27 21:55:26 2017 +0200 $ > Â Â Plugins: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> > Â Â <https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> $ > Â Â Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 > Â Â 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 > 16:47:06 UTC > Â Â 2017 i686 i686 i386 GNU/Linux > Â Â plugin path: > Â Â /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 > [default: > Â Â /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] > > Â Â $ curl get.pharo.org/70-minimal > <http://get.pharo.org/70-minimal> > <http://get.pharo.org/70-minimal > <http://get.pharo.org/70-minimal>> | bash > > Â Â ... > > Â Â $ ./pharo Pharo.image printVersion > Â Â [version] 'Pharo7.0' > > 'Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f > Â Â (32 Bit)' > > Â Â $ time ./pharo Pharo.image eval '5 factorial' > Â Â 120 > Â Â realÂ Â 0m0.083s > Â Â userÂ Â 0m0.034s > Â Â sysÂ Â Â 0m0.042s > > Â Â That is less than 1/10 of a second on a simple server ! Wow. > > Â Â Loading new code in that image seem hard though. > > Â Â I see that in http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/> > Â Â <http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/>> there are Pharomonticello & > Â Â Pharometacello variants. > > Â Â Any pointers on usage/meaning ? > > > Monticello is bootstrapped Pharo image with Monticello loaded. > This image then loads Metacello and the generated image is the > image that we call "minimal". It is minimal in sense minimal for > common usage. > > During Pharo building process we generate: > - bootstrapped image > - image with Opal that is loaded as binary packages using Hermes > - Monticello with only local repositories support > - Monticello with network and remote repositories support > - Metacello > - full Pharo IDE (which is loaded as sequence of several > standalone baselines) > > Cheers, > -- Pavel > > Â Â Thx, > > Â Â Sven > > > > > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

Oct. 8, 2017

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by Guillermo Polito

Yeh, the most important thing is what Jan says there. What you want to ensure is that you don't corrupt your memory (and particularly the heap). If you do so (i.e., corruption) the only way you can come back is that you remember the old uncorrupted value and, given that everything is still working, you put it back where it belongs. In any case, Hernan, I think this discussion belongs to the vm-dev list. On Sun, Oct 8, 2017 at 1:32 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > > > So I think we are talking about different things here. I don't want > > to > > save "bad memory block" errors nor dream about bullet proof VM, but > > if > > we know the bullet then let's use a nice bulletproof vest :) > > > > This can be done and has been done. > > Following code would clearly result in segmentation violation: > > bytes := ExternalBytes address: 16r10 size: 100. > bytes byteAt: 1 put: 10. > > There are smalltalk implementations out there that handle > this and open a (smalltalk) debugger (see the screenshot). > Of course, you can just abort, fix your code and > try again. > > Of course, if you happen to overwrite your object memory > or VM internal structures, you're screwed. > > As you said, you can still be shot and die, but the west can > save your life in some cases :-) > > Best, Jan > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 8, 2017

Re: [Pharo-dev] PharoMinimal ?

by Guillermo Polito

For a really high-level explanation, check the slides in here: https://www.slideshare.net/GuillePolito1/understanding-the-pharo-dev-proces… Now, as Pavel says, minimal is an image with metacello (+ its dependencies of course). This means that you could try to install packages on top of it using baselines. Still, lot of work to do in that front, mainly - modularisation of the minimal-image packages, so we can build even smaller images - modularisation and baselines for all full-image packages, so we can build incremental images on a per-user flavour This means of course - cleaning/sorting initializations - refactoring packages - Uncovering hidden and runtime dependencies - making some analyses on how space is taken (most is methods, tons in kernel and collections ;)) What is not so clear yet from the top of my head: if we distribute minimal images, how can we distribute the pharo libraries that you can load on top of them easily. So far, people using pharo minimal are aware that they are using an alpha version. That means that if they want to load on top of it, let's say, Morphic, they will need to do something like Metacello new baseline: 'Morphic'; repository: 'github://pharo-project/pharo:development/src'; load But that means that we'll be loading the so called 'bleeding-edge' of it all the time, and that version may not correspond with the image they are using. This makes me think we have at some point to revisit the release process so we can have releases internal of libraries such as morphic, athens, fuel, etc, more often. On Sun, Oct 8, 2017 at 4:34 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Pavel, > > I'd probably see some interest in building the GitFileTree-MergeDriver > with it. It only requires Monticello. > > Thierry > > Le 08/10/2017 Ã 12:41, Pavel Krivanek a Ã©crit : > >> Hi Sven, >> >> 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu <mailto: >> sven(a)stfx.eu>>: >> >> >> Hi, >> >> What is the story around PharoMinimal and related images ? >> >> Is there a writeup somewhere with instructions ? >> >> >> Right now the minimal (Metacello) image based on Pharo 7 is used only as >> intermediate step in building of the full Pharo and the only real >> (successful) attempt to use it for something else is PharoLambda ( >> https://gitlab.com/macta/PharoLambda) >> >> In general it can be used for building of own (server) applications. E.g. >> this way you can install and run Teapot on it: >> >> ./pharo Pharo7.0-metacello-32bit-d13eed2.image config >> http://smalltalkhub.com/mc/zeroflag/Teapot/main ConfigurationOfTeapot >> --install=stable >> ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval --no-quit "Teapot on >> GET: '/welcome' -> 'Hello World'; start." >> >> You can load baselines from the Git repositories too but we currently do >> not have any command line handler for it so you need to do it using "eval" >> command or *.st flile. Something like this: >> >> Metacello new >> baseline: 'Seaside3'; >> repository: 'github://SeasideSt/Seaside:master/repository'; >> load >> >> To make it more usable we probably should extend it with SUnit and Fuel. >> If you want to extend it with some packages from vanilla Pharo, you should >> load them using FileTree from your local Pharo repository clone. >> >> Gofer it >> url: 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; >> package: 'Multilingual-OtherLanguages'; >> package: 'Multilingual-TextConverterOtherLanguages'; >> load. >> >> It still needs some care. E.g. some classes from Zinc are not properly >> initialized (I know about DigitalSignatureAlgorithm MD5NonPrimitive >> RxMatcher RxParser RxsPredicate SHA1 ZnByteEncoder ZnConstants ZnMimeType >> ZnNetworkingUtils ZnServer ZnSingleThreadedServer TextConstants TextAction >> TextStyle). >> >> I tried to load Seaside into it today (from the example above) and it >> failed (some strange error probalby related to Unicode processing). But we >> will fix it. If you will tell me what exactly you need we can make it work >> together as in case of PharoLambda. >> >> >> I see that we get **FANTASTIC** startup speed with it: >> >> $ cat /etc/issue >> Ubuntu 16.04.3 LTS >> >> $ ./pharo --version >> 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production >> Spur VM] >> CoInterpreter VMMaker.oscog-eem.2265 uuid: >> 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 >> StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: >> 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 >> VM: 201708271955 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ Date: Sun >> Aug 27 21:55:26 2017 +0200 $ >> Plugins: 201708271955 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ >> Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 >> 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC >> 2017 i686 i686 i386 GNU/Linux >> plugin path: >> /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 [default: >> /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] >> >> $ curl get.pharo.org/70-minimal <http://get.pharo.org/70-minimal> | >> bash >> >> ... >> >> $ ./pharo Pharo.image printVersion >> [version] 'Pharo7.0' >> 'Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c480 >> 9d6a6986d4f >> (32 Bit)' >> >> $ time ./pharo Pharo.image eval '5 factorial' >> 120 >> real 0m0.083s >> user 0m0.034s >> sys 0m0.042s >> >> That is less than 1/10 of a second on a simple server ! Wow. >> >> Loading new code in that image seem hard though. >> >> I see that in http://files.pharo.org/image/70/ >> <http://files.pharo.org/image/70/> there are Pharomonticello & >> Pharometacello variants. >> >> Any pointers on usage/meaning ? >> >> >> Monticello is bootstrapped Pharo image with Monticello loaded. This image >> then loads Metacello and the generated image is the image that we call >> "minimal". It is minimal in sense minimal for common usage. >> >> During Pharo building process we generate: >> - bootstrapped image >> - image with Opal that is loaded as binary packages using Hermes >> - Monticello with only local repositories support >> - Monticello with network and remote repositories support >> - Metacello >> - full Pharo IDE (which is loaded as sequence of several standalone >> baselines) >> >> Cheers, >> -- Pavel >> >> Thx, >> >> Sven >> >> >> > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 8, 2017

Re: [Pharo-dev] Call for Ruby, Python, Java, Javascript Guide to Pharo

by Dimitris Chloupis

Yes I know thats what I am saying , that I dont think its a good idea to learn like this a language. In any case I am adding the Python code snippets and leave the teaching to you. It will take some time but will get it done, no big deal. On Sun, Oct 8, 2017 at 5:20 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Comparing languages in a discussion about Pharo vs the rest is vastly >> different, at least to me , from teaching Pharo. >> > > The pdf that Stef posted I wrote for my students (which know Java and C), > just so it is easier for them to compare/grasp the new syntax based on what > they already know. It wasn't/isn't meant as a language comparison in the > sense that one is better than the other. > > Peter >

Oct. 8, 2017

Re: [Pharo-dev] PharoMinimal ?

by Thierry Goubier

Hi Pavel, I'd probably see some interest in building the GitFileTree-MergeDriver with it. It only requires Monticello. Thierry Le 08/10/2017 Ã 12:41, Pavel Krivanek a Ã©critÂ : > Hi Sven, > > 2017-10-07 16:18 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu > <mailto:sven@stfx.eu>>: > > Hi, > > What is the story around PharoMinimal and related images ? > > Is there a writeup somewhere with instructions ? > > > Right now the minimal (Metacello) image based on Pharo 7 is used only as > intermediate step in building of the full Pharo and the only real > (successful) attempt to use it for something else is PharoLambda > (https://gitlab.com/macta/PharoLambda) > > In general it can be used for building of own (server) applications. > E.g. this way you can install and run Teapot on it: > > ./pharo Pharo7.0-metacello-32bit-d13eed2.image config > http://smalltalkhub.com/mc/zeroflag/Teapot/main ConfigurationOfTeapot > --install=stable > ./pharo Pharo7.0-metacello-32bit-d13eed2.image eval --no-quit "Teapot on > GET: '/welcome' -> 'Hello World'; start." > > You can load baselines from the Git repositories too but we currently do > not have any command line handler for it so you need to do it using > "eval" command or *.st flile. Something like this: > > Metacello new > baseline: 'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > > To make it more usable we probably should extend it with SUnit and Fuel. > If you want to extend it with some packages from vanilla Pharo, you > should load them using FileTree from your local Pharo repository clone. > > Gofer it > url: 'filetree:///path-to-my-pharo-repository-clone/pharo/src'; > package: 'Multilingual-OtherLanguages'; > package: 'Multilingual-TextConverterOtherLanguages'; > load. > > It still needs some care. E.g. some classes from Zinc are not properly > initialized (I know about DigitalSignatureAlgorithm MD5NonPrimitive > RxMatcher RxParser RxsPredicate SHA1 ZnByteEncoder ZnConstants > ZnMimeType ZnNetworkingUtils ZnServer ZnSingleThreadedServer > TextConstants TextAction TextStyle). > > I tried to load Seaside into it today (from the example above) and it > failed (some strange error probalby related to Unicode processing). But > we will fix it. If you will tell me what exactly you need we can make it > work together as in case of PharoLambda. > > > I see that we get **FANTASTIC** startup speed with it: > > $ cat /etc/issue > Ubuntu 16.04.3 LTS > > $ ./pharo --version > 5.0-201708271955Â Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production > Spur VM] > CoInterpreter VMMaker.oscog-eem.2265 uuid: > 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 > StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: > 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 > VM: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ Date: Sun > Aug 27 21:55:26 2017 +0200 $ > Plugins: 201708271955 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ > Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 > 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC > 2017 i686 i686 i386 GNU/Linux > plugin path: > /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 [default: > /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] > > $ curl get.pharo.org/70-minimal <http://get.pharo.org/70-minimal> | bash > ... > > $ ./pharo Pharo.image printVersion > [version] 'Pharo7.0' > 'Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f > (32 Bit)' > > $ time ./pharo Pharo.image eval '5 factorial' > 120 > realÂ Â 0m0.083s > userÂ Â 0m0.034s > sysÂ Â Â 0m0.042s > > That is less than 1/10 of a second on a simple server ! Wow. > > Loading new code in that image seem hard though. > > I see that in http://files.pharo.org/image/70/ > <http://files.pharo.org/image/70/> there are Pharomonticello & > Pharometacello variants. > > Any pointers on usage/meaning ? > > > Monticello is bootstrapped Pharo image with Monticello loaded. This > image then loads Metacello and the generated image is the image that we > call "minimal". It is minimal in sense minimal for common usage. > > During Pharo building process we generate: > - bootstrapped image > - image with Opal that is loaded as binary packages using Hermes > - Monticello with only local repositories support > - Monticello with network and remote repositories support > - Metacello > - full Pharo IDE (which is loaded as sequence of several standalone > baselines) > > Cheers, > -- Pavel > > Thx, > > Sven > >

Oct. 8, 2017