December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] how do you use scripts?

by Norbert Hartl

> Am 12.12.2014 um 12:14 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > As input for designing new features that better support scripting in Pharo, we would benefit from a bit more input around the role scripts play in your development life. > > To this end, I would like to invite you to share your scripting experience. Here are some questions to start from, but feel free to diverge: > For me there are two kind of environments that are imported. On the one hand there is the desktop with a GUI, something that I start manually and that is being saved regularly for me to stop and continue working. On the other hand it is a server environment where everything needs to be started automatically without any GUI. This environment is never saved and always started from the same saved state. > - What kind of actions do you put in scripts? > Setup, configuration and orchestration of components. Short snippets for code I don't want to put in methods, snippets for resetting things etc. Examples are: starting zinc server, adding and configure persistence layer to a stack, resetting model state etc. > - Do you rely on script files stored on the disk at all? > On the desktop I store workspaces to files as backup and to be able to move them to a freshly build image. On the server the whole setup is done with scripts > - Where do you store your scripts (in one folder, in many folders)? > On the desktop I store them in the working directory of the image. I have separate directories for all of my projects. So the project dependent workspace files are just in that project folder. I'd like the idea of organizing scripts but then accessing/navigating to them is more effort then to type it again. I also store scripts in text documents for e.g. having quick access to Gofer snippets in order to load common modules I use. This is mainly to set up the project before writing a metacello config. And not all of those components can be accessed via configuration browser. On the server I've built a utility that accesses a directory full of snippets in a Unix SysV style manner. As an example for our mobility server: root@2d-apis:/opt# ls -1 mobility-server/launch.d/ 10_restore-ui-manager 20_rfb-vnc-server 30_logging 40_mongodb 50_start-mobility 60_scheduler 95_server-setup The prefix number organizes the order of execution of the snippets. The snippets are a mixture of shared and individual scripts. Meaning scripts like restore ui manager and rfb-vnc-server are shared among all installations because they are always the same. I just symlink them into my projects launch.d. A script like rfb-vnc-server looks like this root@2d-apis:/opt# cat mobility-server/launch.d/20_rfb-vnc-server self optionAt: 'vncport' ifPresent: [:portString| RFBServer reset. rfb := RFBServer current. self optionAt: 'vncpassword' ifPresent: [:password| rfb setFullPassword: password ]. rfb start: portString asNumber. self log: 'RFB vnc server started on port ', portString ]. This way I can switch rfb on and off using a commandline switch that is added to a project configuration. This all is part of image-launcher I want to release for several years now :) If anyone is interested please ask. > - Do you version your scripts? Workspace scripts are versioned via timemachine backup only. Server side scripts are put into git. > > - Do you store them in separate files with dedicated names, or tend to put multiple snippets in one larger file? > On the desktop it is more the latter because everything a project depends is in one or two workspaces. On the server as you could see above everything is separated into indvidual scripts > - Do you rely on the names of the scripts? > On the server for tweaking the order of execution. > - Why do you use a script file and not a class? Some of the scripts I put into classes when they grow up to be an utility function. Parts that contain contextual information I don't put into classes because I don't want to have filesystem paths, ip addresses and such inside my code and they are too static if something changes. I think putting stuff in classes is not always an option. To me scripts act as glue between the image and outer world where to image have to live in. Scripts are flexible and adhoc. In my case there is a workflow where a jenkins server builds the deployable image. If the script code (e.g. for startup) in the image needs to be tweaked you need to change the image in order to fix it and there are workflows where this would be pain (rebuilding the image and deploy it to have the change in effect). So scripts in text files have superpowers here. Norbert

Dec. 25, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by stepharo

> On some point, you will need to have some functional widgets. Exact and since there is no magic we will start to write them. We started to write a radio button and this led to a redesin of the core and now we should be ready to try again. If you are not afraid about strange/bad/circumvoluted code have a look at the code of PluggableButtonMorph (not talking about tableLayout intrincaties). So we will not copy Morphic! It will take time and if people want to help they will be able to improve their future. Stef > Can we start to build our own UI using Bloc? > > Cheers, > Alexandre > > >> On Dec 25, 2014, at 11:33 AM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: >> >> >>> On 25 Dec 2014, at 10:31, stepharo <stepharo(a)free.fr> wrote: >>> >>> >>> Le 25/12/14 03:04, Ben Coman a Ã©crit : >>>> Really nice to see your progress. Now do you have some sketches that show how it relates to the components of the existing Morphic? What is being disposed of, what reimplemented, what ported? >> yes, almost everything is new or rewritten and you are right, its time to write documentation. >> Now, there is one well identified issue. >> Athens is used to render everything except >> the Morphic world. >> This is cool but at the end of the rendering, the vm Form based display is used by wrappers : >> see in TBlAthensWrapper>>unprotectedFullDrawOn: >> ---- >> self surface displayOnMorphicCanvas: aCanvas at: self position >> ââ >> It slows down the rendering very much. >> what would be cool would be to have a native Athens/Cairo vm display to really >> benefit from Athens. >> >> Cheers >> Alain >> >> >>> I'm writing class comments and soon a chapter. But it takes time because I have to also do a bit of reverse engineering. >>> Now Bloc does not relate to Morphic :) Everything is rewritten from scratch and we will rewrite everything. >>> We will try to reuse Spec. >>> Now for default Morphic, rewritting all the morphs to use Athens >>> is a huge tasks considered the current logic of certain morphic elements >>> Since Bloc is fully athens-based, it may be better to only work on Bloc. >>> Now the trick is that we can use the morphic elements. >>>> This would really help to understand where contributions might be useful. >>>> >>>> >>>> btw, with Build 40419, "ConfigurationOfBloc load" warns that >>>> it depends on BlEllipseShape which must be resolved before #drawOn: and #drawOnAthensCanvas: can be resolved. >>> Yes this is normal, you should load bleedingEdge. >>>> "ConfigurationOfBlock loadDevelopment" works fine. >>>> >>>> cheer -ben >>>> >>>> Sven Van Caekenberghe wrote: >>>>> Yes, a nice X-Mas present ! >>>>> >>>>>> On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>>> >>>>>> Wow! Impressive!!! >>>>>> >>>>>> Alexandre >>>>>> >>>>>> >>>>>>> On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: >>>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> Iâve just uploaded a small demo of Bloc. >>>>>>> http://vimeo.com/115336678 >>>>>>> >>>>>>> >>>>>>> Cheers >>>>>>> Alain >>>>>>> >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>

Dec. 25, 2014

Re: [Pharo-dev] Hash questions

by stepharo

Ciao Dario Pharo 1.4 is at least 3 years old so you should really consider to migrate. You **cannot** imagine how many improvements we did since then. Stef Le 24/12/14 12:13, Dario Trussardi a Ã©crit : > Ciao, > > I wrok into Pharo Pharo1.4 Latest update: #14445 > > I have a strange behavior relative to hash and = methods into one class. > > Sometimes when i do the code aBag occurrencesOf: anItem the system answer 0 but into the bag there's the relative anItem instance. > > The problem is generated when in the anItem class definitions method, > > i do reference to a instance variable ( consumer ) setting to a Symbol. > > The hash method is: > > hash > > ^item hash > bitXor:( opzioniVoce hash > bitXor:( referenceTime hash > bitXor:( consumer hash > bitXor:( newEntry hash )))) > > > The = method is: > > = anItem > > | rslPrz | > anItem ifNil:[^false]. > > self class = anItem class ifFalse:[ ^false]. > > rslPrz:= ( item = anItem item > and:[ opzioniVoce = anItem opzioniVoce > and:[ referenceTime = anItem referenceTime > and:[ consumer = anItem consumer > and:[ newEntry = anItem newEntry ]]]]). > > ^ rslPrz > > > If i remove the consumer instance reference in the two methods all work fine. > > any ideas about it ? > > Thanks, > > Dario > > > > >

Dec. 25, 2014

Re: [Pharo-dev] Old inspector and explorer

by stepharo

I will add basicInspect in Object so that we can get access to the old inspector. I like that people can choose their tools! I mentioned that 20 times but people do not care apparently. Stef Le 23/12/14 11:50, Norbert Hartl a Ã©crit : > Is there a way to get the old tools via shortcut? > > I started something new with pharo 4.0 today. I discovered a bug in Nautilus where every rename or deletion of a method raises a debugger. I tried finding the bug but struggled because to me the new inspector is really confusing. If I "just" want to unfold a few levels of references to get a glimpse of the structure the new tool prevents me from doing that. There is just to much information in this window and too much happening to me. > To me it looks like a power tool you need to get used to. So it is probably not the best tool for simple tasks and people new to this environment might be overwhelmed. At least I would like to be able to use the old tools. > > Norbert > > > >

Dec. 25, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Alexandre Bergel

On some point, you will need to have some functional widgets. Can we start to build our own UI using Bloc? Cheers, Alexandre > On Dec 25, 2014, at 11:33 AM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: > > >> On 25 Dec 2014, at 10:31, stepharo <stepharo(a)free.fr> wrote: >> >> >> Le 25/12/14 03:04, Ben Coman a Ã©crit : >>> Really nice to see your progress. Now do you have some sketches that show how it relates to the components of the existing Morphic? What is being disposed of, what reimplemented, what ported? > > yes, almost everything is new or rewritten and you are right, its time to write documentation. > Now, there is one well identified issue. > Athens is used to render everything except > the Morphic world. > This is cool but at the end of the rendering, the vm Form based display is used by wrappers : > see in TBlAthensWrapper>>unprotectedFullDrawOn: > ---- > self surface displayOnMorphicCanvas: aCanvas at: self position > ââ > It slows down the rendering very much. > what would be cool would be to have a native Athens/Cairo vm display to really > benefit from Athens. > > Cheers > Alain > > >> >> I'm writing class comments and soon a chapter. But it takes time because I have to also do a bit of reverse engineering. >> Now Bloc does not relate to Morphic :) Everything is rewritten from scratch and we will rewrite everything. >> We will try to reuse Spec. >> Now for default Morphic, rewritting all the morphs to use Athens >> is a huge tasks considered the current logic of certain morphic elements >> Since Bloc is fully athens-based, it may be better to only work on Bloc. >> Now the trick is that we can use the morphic elements. >>> This would really help to understand where contributions might be useful. >>> >>> >>> btw, with Build 40419, "ConfigurationOfBloc load" warns that >>> it depends on BlEllipseShape which must be resolved before #drawOn: and #drawOnAthensCanvas: can be resolved. >> >> Yes this is normal, you should load bleedingEdge. >>> >>> "ConfigurationOfBlock loadDevelopment" works fine. >>> >>> cheer -ben >>> >>> Sven Van Caekenberghe wrote: >>>> Yes, a nice X-Mas present ! >>>> >>>>> On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> >>>>> Wow! Impressive!!! >>>>> >>>>> Alexandre >>>>> >>>>> >>>>>> On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: >>>>>> >>>>>> Hello all, >>>>>> >>>>>> Iâve just uploaded a small demo of Bloc. >>>>>> http://vimeo.com/115336678 >>>>>> >>>>>> >>>>>> Cheers >>>>>> Alain >>>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 25, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Alain Plantec

> On 25 Dec 2014, at 10:31, stepharo <stepharo(a)free.fr> wrote: > > > Le 25/12/14 03:04, Ben Coman a Ã©crit : >> Really nice to see your progress. Now do you have some sketches that show how it relates to the components of the existing Morphic? What is being disposed of, what reimplemented, what ported? yes, almost everything is new or rewritten and you are right, its time to write documentation. Now, there is one well identified issue. Athens is used to render everything except the Morphic world. This is cool but at the end of the rendering, the vm Form based display is used by wrappers : see in TBlAthensWrapper>>unprotectedFullDrawOn: ---- self surface displayOnMorphicCanvas: aCanvas at: self position ââ It slows down the rendering very much. what would be cool would be to have a native Athens/Cairo vm display to really benefit from Athens. Cheers Alain > > I'm writing class comments and soon a chapter. But it takes time because I have to also do a bit of reverse engineering. > Now Bloc does not relate to Morphic :) Everything is rewritten from scratch and we will rewrite everything. > We will try to reuse Spec. > Now for default Morphic, rewritting all the morphs to use Athens > is a huge tasks considered the current logic of certain morphic elements > Since Bloc is fully athens-based, it may be better to only work on Bloc. > Now the trick is that we can use the morphic elements. >> This would really help to understand where contributions might be useful. >> >> >> btw, with Build 40419, "ConfigurationOfBloc load" warns that >> it depends on BlEllipseShape which must be resolved before #drawOn: and #drawOnAthensCanvas: can be resolved. > > Yes this is normal, you should load bleedingEdge. >> >> "ConfigurationOfBlock loadDevelopment" works fine. >> >> cheer -ben >> >> Sven Van Caekenberghe wrote: >>> Yes, a nice X-Mas present ! >>> >>>> On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> >>>> Wow! Impressive!!! >>>> >>>> Alexandre >>>> >>>> >>>>> On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: >>>>> >>>>> Hello all, >>>>> >>>>> Iâve just uploaded a small demo of Bloc. >>>>> http://vimeo.com/115336678 >>>>> >>>>> >>>>> Cheers >>>>> Alain >>>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> >> > >

Dec. 25, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by stepharo

Le 25/12/14 03:04, Ben Coman a Ã©crit : > Really nice to see your progress. Now do you have some sketches that > show how it relates to the components of the existing Morphic? What is > being disposed of, what reimplemented, what ported? I'm writing class comments and soon a chapter. But it takes time because I have to also do a bit of reverse engineering. Now Bloc does not relate to Morphic :) Everything is rewritten from scratch and we will rewrite everything. We will try to reuse Spec. Now for default Morphic, rewritting all the morphs to use Athens is a huge tasks considered the current logic of certain morphic elements Since Bloc is fully athens-based, it may be better to only work on Bloc. Now the trick is that we can use the morphic elements. > This would really help to understand where contributions might be useful. > > > btw, with Build 40419, "ConfigurationOfBloc load" warns that > it depends on BlEllipseShape which must be resolved before #drawOn: > and #drawOnAthensCanvas: can be resolved. Yes this is normal, you should load bleedingEdge. > > "ConfigurationOfBlock loadDevelopment" works fine. > > cheer -ben > > Sven Van Caekenberghe wrote: >> Yes, a nice X-Mas present ! >> >>> On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> >>> wrote: >>> >>> Wow! Impressive!!! >>> >>> Alexandre >>> >>> >>>> On Dec 24, 2014, at 3:19 PM, Alain Plantec >>>> <alain.plantec(a)yahoo.com> wrote: >>>> >>>> Hello all, >>>> >>>> Iâve just uploaded a small demo of Bloc. >>>> http://vimeo.com/115336678 >>>> >>>> >>>> Cheers >>>> Alain >>>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> >> > > > > >

Dec. 25, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Ben Coman

Really nice to see your progress. Now do you have some sketches that show how it relates to the components of the existing Morphic? What is being disposed of, what reimplemented, what ported? This would really help to understand where contributions might be useful. btw, with Build 40419, "ConfigurationOfBloc load" warns that it depends on BlEllipseShape which must be resolved before #drawOn: and #drawOnAthensCanvas: can be resolved. "ConfigurationOfBlock loadDevelopment" works fine. cheer -ben Sven Van Caekenberghe wrote: > Yes, a nice X-Mas present ! > >> On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> Wow! Impressive!!! >> >> Alexandre >> >> >>> On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: >>> >>> Hello all, >>> >>> Iâve just uploaded a small demo of Bloc. >>> http://vimeo.com/115336678 >>> >>> >>> Cheers >>> Alain >>> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > >

Dec. 25, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Sven Van Caekenberghe

Yes, a nice X-Mas present ! > On 24 Dec 2014, at 15:41, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Wow! Impressive!!! > > Alexandre > > >> On Dec 24, 2014, at 3:19 PM, Alain Plantec <alain.plantec(a)yahoo.com> wrote: >> >> Hello all, >> >> Iâve just uploaded a small demo of Bloc. >> http://vimeo.com/115336678 >> >> >> Cheers >> Alain >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Dec. 24, 2014

Re: [Pharo-dev] [Ann] a short Bloc demo

by Hilaire

Wonderful! Thanks Le 24/12/2014 15:19, Alain Plantec a Ã©crit : > Hello all, > > Iâve just uploaded a small demo of Bloc. > http://vimeo.com/115336678 > > > Cheers > Alain > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Dec. 24, 2014