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

Re: [Pharo-dev] lookInGeneralPreferencesFolder

by Pharo4Stef

can you provide a reproducible case and a trace? On 31 Jan 2014, at 23:28, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi guys, > > that method is raising an exception when moving the image from one OS to other > > > > > >

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Pharo4Stef

@ Igor I guess that I know pretty well poolDictionaries I do not need an explanation. I even found bugs in the previous lookup and now we have recompilation bugs when changing pools. Now how many times gave one lectures to newcomers? Why do we have new calling initialize? Because after first lecture we HAD to explain metaclasses. Do we want to continue to stay a close club of smart asses? NOOOOOOOOOOOOOOOOOOOOOOOOO NOT ME at least @others Now people hear me well: you are ready to hear well. Lower the music WE WILL change the class definition in Pharo 4 because we want slots. So be prepared. This is not because you did not read nor type this class definition since years (because you do not even look at it) that - it will not change - students do not get overhelmed with it. I DO NOT WANT MY SONS TO PROGRAM IN PYTHON/RUBY/JS BECAUSE THIS IS âEASIERâ. Is it clear? It is BORING to have to say to kids: - do not care of classvar - do not care of pooldictionaries COME ON when can we open our eyes? So yes Iâmad at the lack of vision **you** have. But do not worry I have the vision for Pharo. If you do not like it, I cannot do much for you. Continue rambling how cool was smalltalk 30 years ago. Not me. We are INVENTING the future here. So please focus your energy on how to make pharo simpler, nicer and sexier. Stef > Guys, can you explain me, why you hating pools so much? > Because you cannot find good use of them, or because you don't know how to properly use them? Or because you don't understand what is it? > > Pool dictionary is just a namespace, which you can share among different parts of your code (on a per-class basis). > And one of most used form of it is a global one, where all public classes are. > The only difference is that access to global pool is implicit (you don't have to mention it in class definition), but it has same nature as shared pool. > > As long as you need to give names to things you using, you gonna need namespaces/pools. > > > -- > Best regards, > Igor Stasenko.

Feb. 1, 2014

Re: [Pharo-dev] Yet another week of commits

by Pharo4Stef

So it looks like a useful service :) > Websense categorizes "association.pharo.org" as "sex". > > > On Fri, Jan 31, 2014 at 10:56 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > Another week of improvements > > http://association.pharo.org/web/weekly/Commits-Jan-3 > > stef >

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Igor Stasenko

Guys, can you explain me, why you hating pools so much? Because you cannot find good use of them, or because you don't know how to properly use them? Or because you don't understand what is it? Pool dictionary is just a namespace, which you can share among different parts of your code (on a per-class basis). And one of most used form of it is a global one, where all public classes are. The only difference is that access to global pool is implicit (you don't have to mention it in class definition), but it has same nature as shared pool. As long as you need to give names to things you using, you gonna need namespaces/pools. -- Best regards, Igor Stasenko.

Feb. 1, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Igor Stasenko

On 31 January 2014 18:03, Andreas Wacknitz <a.wacknitz(a)gmx.de> wrote: > > Am 31.01.2014 um 14:40 schrieb Johan Fabry <jfabry(a)dcc.uchile.cl>: > > > Hi Torsten, > > > > I think it is a design decision / tradeoff, and therefore there is no > fundamentally "right way" to do it. For me, it is the same case as the > uses: message for Traits. It's not in the template by default because it is > used very infrequently. So for language simplicity it should not be there. > For me, simplicity is one of the core points of Smalltalk so this is why I > feel strongly about it. > > I donât see how this change make Smalltalk (the language) simpler. For me > this change looks more like an obfuscation than a simplification. > > +1 > > > > > When I say "very infrequently", this is of course a fuzzy metric, I > know. And I understand that you do not agree with this design decision. > > > > But on the other hand, I don't think that it is too hard to remember > where to add the pooldictionaries: line if you need it, and the old message > with this line still works, so all old examples still work. > > How should newcomers know how to enter pool dictionaries? I rarely use > pool dictionaries and if I will need it I surely have forgotten about > this change and expect irritation and frustration. > > So, a -1 for this change from my side. > > +1 > Regards > Andreas > > > > -- Best regards, Igor Stasenko.

Feb. 1, 2014

[launcher] Windows Installer UAC Virtualization problems

by btc＠openinworld.com

Damien Cassou wrote in "[Pharo-dev] [FEEDBACK] Install Pharo on Windows": > Hi, > > I've just made an executable file for installing Pharo on Windows (in > program files, with a shortcut in the Start menu...). Please try > it and report problems: > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Win-Package/lastSu… > > Best, > > Just reporting a very strange experience. A while ago I installed Pharo Launcher using the Windows Installer and its been working great. In the meantime I have dropped into development mode and opened a few other windows. Calling that one Image-A, today I wanted to throw away my changes, so from folder "C:\Program Files (x86)\Pharo\" I deleted files pharo.{image,changes} and dropped in files pharolauncher.{image,changes}. now with a single image in the oflder I expected it to just start up, but strangely I get presented with a file-choice-dialog on folder "C:\Program Files (x86)\Pharo\" showing pharo.image and pharolauncher.image to choose between, even though Windows Explorer shows pharo.image does not exist. So I renamed pharolauncher.image to pharo.image, and the file-choice-dialog stops coming up, but it the old pharo.image that is still opening. Now the REALLY weird thing to keep in mind as I describe below a few things I've tried, is that the native window title bar _always_ shows "Pharo! (C:\Program Files (x86)\Pharo\Pharo.image" I have tried: * a. Re-rerunning the PharoLauncher installer * b. Running the PharoLauncher un-install, then re-running the installer. * c. Starting from the Windows Start menu * d. Double-clicking file "pharo.exe" in folder "C:\Program Files (x86)\Pharo\" * e. Dragging file "pharo.image" on top of file "pharo.exe" * f. Deleting file "pharo.image" from folder "C:\Program Files (x86)\Pharo\" - but double-clicking "pharo.exe" still starts * g. Manually deleting whole folder "C:\Program Files (x86)\Pharo\" then re-running the installer. * h. When saving the image, the date on "C:\Program Files (x86)\Pharo\pharo.image" is not being updated. * i. Evaluating FileSystem workingDirectory --> "FileSystem workingDirectory" * j. After the folder "C:\Program Files (x86)\Pharo\" to "C:\temp\Pharo\" then double-slicking on Pharo.exe opens the fresh pharo.image as expected. * k. Re-running the installer but using a different folder "C:\Program Files (x86)\Pharo3\" works. Its been a frustratingly surreal experience to investigate, for a while not even believing what I was seeing. Now I operate under a non-admin account (as should anyone with the smallest belief in security [1]) and rely on UAC to elevate privileges during an install. So the problem turned out to be with Microsoft's SILENT file virtualization. I found an echo of the install in folder "C:\Users\Ben\AppData\Local\VirtualStore\Program Files (x86)\Pharo\". Deleting that folder resolved the shallow-problem, such the fresh install was now running as expected. However the deeper-problem is that this is likely to frustrate others in the future - particularly in a corporate setting trying to update PharoLauncher fighting multiple user's virtualized copies. So far it seems the options are: 1. Add a manifest to the installer such that UAC virtualization is turned off (per Task #5 [3]). Saving the image will now fail but avoid submarine problems later on. Can the VM be told the image is read-only and Save is disabled. Or if a save fails, could is fall back to the Save As defaulting to the folder where PharoLauncher is managing its other images. There might be other issues to deal with the files Pharo.ini, stderr & stdout being prevented from being written to in the normal course of operation. 2. Install "User Only" per [4]. This is probably easiest to do this close to Pharo 3 release. [1] http://blogs.msdn.com/b/aaron_margosis/archive/2004/06/17/157962.aspx [2] https://blogs.windows.com/windows/archive/b/developers/archive/2009/08/04/u… [3] http://www.klopfenstein.net/lorenz.aspx/simple-nsis-installer-with-user-exe… [4] http://www.klopfenstein.net/lorenz.aspx/simple-nsis-installer-with-user-exe… cheer -ben

Feb. 1, 2014