- Pharo-users - lists.pharo.org

Re: [Pharo-users] [ANN]Windows previewer / switcher for Pharo

by Mariano Martinez Peck

Hi, Did you try it with OSX? Does not seem to work for me with cmd + tab. On Tue, Jun 28, 2016 at 12:54 PM, Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Thanks Julien. Testing it. It looks pretty cool and seems really useful > for my clutter windows usage that Pharo / Smalltalk tends towards. See: > > or full screen at: > https://offray.withknown.com/2016/windows-preview-on-pharo-by-julien-delpla… > > Cheers, > > Offray > > On 28/06/16 07:51, Julien Delplanque wrote: > > Also, here is a screenshot (I forgot to attach it to the preceding mail). > > Julien > > > On 28/06/16 11:06, Julien Delplanque wrote: > > Hello, > > This mail to announce you that I am working on a windows previewer / > switcher for > Pharo [1]. > > It is still in early stage of development but it is usable. > > To install it: > > |Metacello new repository: > 'github://JulienDelplanque/WindowsPreviewer/repository'; baseline: > 'WindowsPreviewer'; load| > > See the README for details on activation/shortcuts. > > Please, if you have some ideas or critics let me know! > > Also, a better name than "Windows Previewer" would be cool but I have > no other idea :-)... > > Regards, > > Julien > > Links: > [1]: https://github.com/juliendelplanque/WindowsPreviewer > > > > -- Mariano http://marianopeck.wordpress.com

June 28, 2016

Re: [Pharo-users] How do I convert a FileTree project to Metadataless GitFileTree project?

by Thierry Goubier

Hi Dale, Le 28/06/2016 20:49, Dale Henrichs a Ã©crit : > Thierry, > > I think I tried the obvious: > > 1. open existing repository with gitfiletree:// > 2. reload all packages from gitfiletree repo and remove old filetree:// > repo from each package > 3. edit .filetree and add `"Metadata" : "false"` > > but when I save a package I continue to get metadata created ... With that sequence, I'm sure the gitfiletree repository in memory has still kept the Metadata : true property, and so hasn't taken in account the on-disk change. Like FileTree, it only loads the repository properties on the very first access to that repository. > I even tried removing and adding the repo after editting the .filetree > file .... And that didn't work ? I suspected it would... unless the gitfiletree repository of step 1 above was not garbage collected. > I have a handful of additional random things that I will try, but I > think it is also time to find out the proper technique:) I haven't provided an API for the switch, really. And I don't know where to add that option inside the Monticello gui. What I did, in the few cases I did it, was to inspect the in-image MCFileTreeGitRepository and change the property in the inspector ;) > I want to gain experience with GitFileTree; test out the Metacello > Cypress mode; and perhaps honor the `"Metadata" : "false"` in the > GemStone version of FileTree ... > > With a short time of usage, I would really like to be able to save all > of the packages in a project (including the BaselineOf) in one commit > ... I often have multi-package units of work that really should be > committed together and of course if a method is moved across a package > boundary, the independent commits don't allow git to recognize the move > as a "rename" ... We would need a specific API for that. At the moment what would work is to save the baselineOf with all the baseline packages as dependencies. Now, I'd like to be able to query the baseline to know which packages it describes, and save all of them in one go. Another possibility would be to add an option with a no-commit flag (write but do not commit, do not try to update the package version) and add a button to the window appearing after each written package version to do the commit, store temporarily all such "staged" packages info in the repository object, and provide a warning if one tries to resave a package before a commit... > Also I'm hoping that in metadataless mode I stop scanning the entire > known repository universe for package versions that will not be found > anywhere but in the repositories that I've explicitly associated with > the the package itself:) I don't think it happens there. MCGitFileTreeVersionInfo already tracks the repository it comes from, but I'm pretty sure that MC doesn't ask the version info for the new data. Maybe add a new type of WorkingCopy object? Thierry > Thanks, > > Dale

June 28, 2016

How do I convert a FileTree project to Metadataless GitFileTree project?

by Dale Henrichs

Thierry, I think I tried the obvious: 1. open existing repository with gitfiletree:// 2. reload all packages from gitfiletree repo and remove old filetree:// repo from each package 3. edit .filetree and add `"Metadata" : "false"` but when I save a package I continue to get metadata created ... I even tried removing and adding the repo after editting the .filetree file .... I have a handful of additional random things that I will try, but I think it is also time to find out the proper technique:) I want to gain experience with GitFileTree; test out the Metacello Cypress mode; and perhaps honor the `"Metadata" : "false"` in the GemStone version of FileTree ... With a short time of usage, I would really like to be able to save all of the packages in a project (including the BaselineOf) in one commit ... I often have multi-package units of work that really should be committed together and of course if a method is moved across a package boundary, the independent commits don't allow git to recognize the move as a "rename" ... Also I'm hoping that in metadataless mode I stop scanning the entire known repository universe for package versions that will not be found anywhere but in the repositories that I've explicitly associated with the the package itself:) Thanks, Dale

June 28, 2016

Re: [Pharo-users] accepting method without creating variable and code generation

by Ben Coman

On Tue, Jun 28, 2016 at 9:31 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 28 Jun 2016, at 15:09, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Ding dong Marcus! > > > â¦ is on Holidaysâ¦ with the option #optionParseErrors you can compile code > with syntax errors: wow! quite an intelligent bot you are there. written in Smalltalk? maybe when Marcus is back you can ask him to share the source ;) cheers -ben > > method := Smalltalk compiler > class: UndefinedObject; > options: #(+ optionParseErrors); > compile: 'errorMethod ^1+'. > method valueWithReceiver: nil arguments: #() > This is really compiled to raise a syntax error at runtime. see > > OCASTTranslator>>#visitParseErrorNode: anErrorNode > methodBuilder > pushLiteralVariable: #error -> anErrorNode asSyntaxErrorNotification; > send: #signal. > > with > > RBParseErrorNode>>#asSyntaxErrorNotification > ^SyntaxErrorNotification new > setClass: self methodNode methodClass > category: nil > code: self methodNode source > doitFlag: false > errorMessage: errorMessage > location: self start > > > Marcus

June 28, 2016

Re: [Pharo-users] Pharo Launcher

by Damien Cassou

Christophe Demarey <christophe.demarey(a)inria.fr> writes: > Pharo launcher is now shipped with both vm (pre-spur and spur). The > cog-spur vm now powered PharoLauncher and should be used to run spur > images. If not, maybe you have a wrong setting for it. If you remove > settings for both VM it should work. Maybe I should remove these > settings since both VMs are now shipped with the launcher app. I do > not know if it is relevant to some of you to use another VM than the > default ones. it is at least relevant for me because I cannot use the shipped VMs: I have to use the ones of my Linux distribution. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

June 28, 2016

Re: [Pharo-users] [ANN]Windows previewer / switcher for Pharo

by Offray Vladimir Luna CÃ¡rdenas

Thanks Julien. Testing it. It looks pretty cool and seems really useful for my clutter windows usage that Pharo / Smalltalk tends towards. See: or full screen at: https://offray.withknown.com/2016/windows-preview-on-pharo-by-julien-delpla… Cheers, Offray On 28/06/16 07:51, Julien Delplanque wrote: > Also, here is a screenshot (I forgot to attach it to the preceding mail). > > Julien > > > On 28/06/16 11:06, Julien Delplanque wrote: >> Hello, >> >> This mail to announce you that I am working on a windows previewer / >> switcher for >> Pharo [1]. >> >> It is still in early stage of development but it is usable. >> >> To install it: >> >> |Metacello new repository: >> 'github://JulienDelplanque/WindowsPreviewer/repository'; baseline: >> 'WindowsPreviewer'; load| >> >> See the README for details on activation/shortcuts. >> >> Please, if you have some ideas or critics let me know! >> >> Also, a better name than "Windows Previewer" would be cool but I have >> no other idea :-)... >> >> Regards, >> >> Julien >> >> Links: >> [1]: https://github.com/juliendelplanque/WindowsPreviewer >> >

June 28, 2016

Re: [Pharo-users] accepting method without creating variable and code generation

by Marcus Denker

> On 28 Jun 2016, at 15:09, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Ding dong Marcus! > > â¦ is on Holidaysâ¦ with the option #optionParseErrors you can compile code with syntax errors: method := Smalltalk compiler class: UndefinedObject; options: #(+ optionParseErrors); compile: 'errorMethod ^1+'. method valueWithReceiver: nil arguments: #() This is really compiled to raise a syntax error at runtime. see OCASTTranslator>>#visitParseErrorNode: anErrorNode methodBuilder pushLiteralVariable: #error -> anErrorNode asSyntaxErrorNotification; send: #signal. with RBParseErrorNode>>#asSyntaxErrorNotification ^SyntaxErrorNotification new setClass: self methodNode methodClass category: nil code: self methodNode source doitFlag: false errorMessage: errorMessage location: self start Marcus

June 28, 2016

Re: [Pharo-users] accepting method without creating variable and code generation

by Thierry Goubier

Le 28/06/2016 15:03, Nicolas Passerini a Ã©crit : > Still, I think it would be nice to be able to save a method even when it > does not compile. I believe it would be better to be able to manipulate, inspect and edit properly virtual methods (MCMethodDefinition, RB-created methods) given that saving a method even if it does not compile is already possible, even if not made available in the GUI. Thierry > On Tue, Jun 28, 2016 at 2:52 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > > Yeah I guess that's not such a bad idea, to have a TemplateClass > that would contain just the template methods, so I don't need to > worry about conflicting instance variables. > > Peter > > On Tue, Jun 28, 2016 at 2:08 PM, Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > On Tue, Jun 28, 2016 at 5:55 PM, Peter Uhnak <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > > Hi, > > > > is it possible to accept a method without creating instance > variable? > > > > E.g. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Object subclass: #MyObject > > slots: { } > > classVariables: { } > > category: 'Category' > > ~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~ > > MyObject>>addValue: aValue > > container add: aValue > > ~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > Now normally when I would try to compile the method I would > get the "Unknown variable 'container'" warning that will force > me to either create temporary or instance variable; I would like > to somehow ignore that, because the method will actually never > get called. > > > > My objective is use this method as a template for code > generation, so I would then take this method, apply some code > transformation and compile it into different object. > > > > Of course I could do > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > MyObject>>addValueTemplate > > ^ 'MyObject>>addValue: aValue > > container add: aValue' > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > But then I would lose code highlighting, which is quite > error-prone for more complex snippets. > > > > If you have a better approach, I am all ears. :) > > > > Thanks, > > Peter > > If you are only templating the method and not the whole class, > why not > add it as an instance variable MyObject? > Or if MyObject is a real domain object with a few template methods, > maybe put the templates on the class side and add a dummy > class-instance-variable there. > > cheers -ben > > >

June 28, 2016

Re: [Pharo-users] accepting method without creating variable and code generation

by Guillermo Polito

Ding dong Marcus! Le 28 juin 2016 15:04, "Nicolas Passerini" <npasserini(a)gmail.com> a Ã©crit : > Still, I think it would be nice to be able to save a method even when it > does not compile. > > On Tue, Jun 28, 2016 at 2:52 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > >> Yeah I guess that's not such a bad idea, to have a TemplateClass that >> would contain just the template methods, so I don't need to worry about >> conflicting instance variables. >> >> Peter >> >> On Tue, Jun 28, 2016 at 2:08 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> On Tue, Jun 28, 2016 at 5:55 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> > Hi, >>> > >>> > is it possible to accept a method without creating instance variable? >>> > >>> > E.g. >>> > >>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> > Object subclass: #MyObject >>> > slots: { } >>> > classVariables: { } >>> > category: 'Category' >>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> > >>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> > MyObject>>addValue: aValue >>> > container add: aValue >>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> > >>> > Now normally when I would try to compile the method I would get the >>> "Unknown variable 'container'" warning that will force me to either create >>> temporary or instance variable; I would like to somehow ignore that, >>> because the method will actually never get called. >>> > >>> > My objective is use this method as a template for code generation, so >>> I would then take this method, apply some code transformation and compile >>> it into different object. >>> > >>> > Of course I could do >>> > >>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> > MyObject>>addValueTemplate >>> > ^ 'MyObject>>addValue: aValue >>> > container add: aValue' >>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> > >>> > But then I would lose code highlighting, which is quite error-prone >>> for more complex snippets. >>> > >>> > If you have a better approach, I am all ears. :) >>> > >>> > Thanks, >>> > Peter >>> >>> If you are only templating the method and not the whole class, why not >>> add it as an instance variable MyObject? >>> Or if MyObject is a real domain object with a few template methods, >>> maybe put the templates on the class side and add a dummy >>> class-instance-variable there. >>> >>> cheers -ben >>> >>> >> >

June 28, 2016

Re: [Pharo-users] accepting method without creating variable and code generation

by Cyril Ferlicot Delbecque

On 28/06/2016 15:03, Nicolas Passerini wrote: > Still, I think it would be nice to be able to save a method even when it > does not compile. > I think Marcus added the possibility to do that in Pharo 6 as a Setting. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

June 28, 2016