August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5

by Sean P. DeNigris

Torsten Bergmann wrote > sorry for "hijacking" the topic Yes, when you pre-announce something exciting, you have to move quickly or Torsten may finish it for you ha ha ;) Torsten Bergmann wrote > allowing me to put my recommended puzzle pieces together myself I wonder how it compares to the solution in TWM, which has been very buggy since Pharo 4.0â¦ ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Multiple-Desktop-support-for-Pharo-5-tp4846189p48… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 28, 2015

Re: [Pharo-dev] OSX code signing

by Stephan Eggermont

On 28-08-15 11:00, Marcus Denker wrote: >> 3. For a "portable" app (e.g. on USB stick) push the app down one >> folder, so rather than putting the Win/Lin executables inside the OSX >> app, the top level folder contains folders Windows, Linux, Common, and >> the app. > > No, I would retire that concept. (I know some people love it, but I think it does > not fit into days world where the OS installs Apps). I strongly disagree. It is very useful to be able to carry a complete environment with me that is useable wherever I am. We will run into a lot less problems with it once we move to 64 bit. Stephan

Aug. 28, 2015

Re: [Pharo-dev] QANautilusPluggin Logic Question

by Marcus Denker

Maybe related.. there is test failing on the CI server : ReleaseTests.ReleaseTest.testMethodsWithUnboundGlobals (from ReleaseTests) Found methods with unbound globals: an OrderedCollection(QANautilusPluginMorph>>#buildConfirmationCheckbox:) > On 28 Aug 2015, at 11:34, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> QANautilusPluggin

Aug. 28, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50285 Home: https://github.com/pharo-project/pharo-core

Aug. 28, 2015

[pharo-project/pharo-core] 3fc93c: 50285

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 3fc93c5c30e986c03f235b030da076576aa30847 https://github.com/pharo-project/pharo-core/commit/3fc93c5c30e986c03f235b03… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-28 (Fri, 28 Aug 2015) Changed paths: R MonticelloGUI.package/MCConfigurationBrowser.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCConfigurationBrowser.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCRepositoryInspector.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCRepositoryInspector.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCSaveVersionDialog.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCSaveVersionDialog.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCSnapshotBrowser.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCSnapshotBrowser.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCTool.class/instance/morphic ui/defaultExtent.st M MonticelloGUI.package/MCTool.class/instance/morphic ui/initialExtent.st M MonticelloGUI.package/MCTool.class/instance/opening/show.st M MonticelloGUI.package/MCTool.class/instance/opening/showLabelled_.st R MonticelloGUI.package/MCVersionHistoryBrowser.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCVersionHistoryBrowser.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCVersionInspector.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCVersionInspector.class/instance/morphic ui/initialExtent.st R MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/defaultExtent.st A MonticelloGUI.package/MCWorkingCopyBrowser.class/instance/morphic ui/initialExtent.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50284.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50285.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50284.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50285.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/ComposableModel.class/instance/accessing/announcer.st M Spec-Core.package/ComposableModel.class/instance/initialization/initialize.st Log Message: ----------- 50285 16347 ComposableModel announcer should not be a valueHolder https://pharo.fogbugz.com/f/cases/16347 16401 opening monticello window does not respect world size https://pharo.fogbugz.com/f/cases/16401 http://files.pharo.org/image/50/50285.zip

Aug. 28, 2015

Re: [Pharo-dev] QANautilusPluggin Logic Question

by Yuriy Tymchuk

Wow, this is weird. Yes, GLMAsyncTask spawns a process. I use it not to block the ui in nautilus while critics are retrieved. So when you switch to a new method it changes pluginâs critic list to âloading progress morphâ and runs the task with a lower priority. If in ui you go through methods, it simply reschedules the task to check different critics. When you stop working with UI it calculates the critics and shows them to you. For me its weird that you get DNU for symbol while `morph` should be a QANautilusPluginMorph. Did I do something very evil not knowing about all the concurrent/morphic black magic? Uko > On 28 Aug 2015, at 10:50, stepharo <stepharo(a)free.fr> wrote: > > When I add an iv to Model I get a ByteSymbol>>entity: > > QANautilusPluggin>>initialize > > changeHandler := GLMAsyncTask new > priority: Processor activePriority - 1; > doInBackground: [ morph entity: self currentEntity ]; > yourself > > And in the debugger morph is a a Morph exactly a QANautilusPluginMorph(493092864) > > Yuriy do you use thread? > > Stef > > >

Aug. 28, 2015

Re: [Pharo-dev] [ANN] Multiple Desktop support for Pharo 5

by Torsten Bergmann

Aug. 28, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50284 Home: https://github.com/pharo-project/pharo-core

Aug. 28, 2015

[pharo-project/pharo-core] 5c5432: 50284

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 5c5432b11932806e8a57cc398685c4c0a9beffda https://github.com/pharo-project/pharo-core/commit/5c5432b11932806e8a57cc39… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-28 (Fri, 28 Aug 2015) Changed paths: M Fuel.package/extension/TClassDescription/instance/instanceVariableNamesDo_.st M Kernel.package/InstructionStream.class/class/compiling/instVarNamesAndOffsetsDo_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/display/class_andInstVariable_.st M OpalTools.package/extension/OCAbstractScope/instance/sourceInterval.st A OpalTools.package/extension/OCClassScope/instance/gtInspectorSourceCodeIn_.st A OpalTools.package/extension/OCInstanceScope/instance/gtInspectorSourceCodeIn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50283.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50284.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50283.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50284.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/AbstractLayout.class/instance/accessing/instVarNames.st R Slot.package/AbstractLayout.class/instance/accessing/instanceVariables.st A Slot.package/PointerLayout.class/instance/accessing/instVarNames.st R Slot.package/PointerLayout.class/instance/accessing/instanceVariables.st M Slot.package/extension/ClassDescription/instance/superclass_layout_.st M Traits.package/TClassDescription.class/instance/compiling/instVarNamesAndOffsetsDo_.st M Traits.package/TClassDescription.class/instance/instance variables/instVarIndexFor_ifAbsent_.st M Traits.package/TClassDescription.class/instance/instance variables/instVarNameForIndex_.st Log Message: ----------- 50284 16409 MNU: receiver of sourceInterval is nil https://pharo.fogbugz.com/f/cases/16409 16249 change all senders of #instanceVariables to use #instVarNames https://pharo.fogbugz.com/f/cases/16249 http://files.pharo.org/image/50/50284.zip

Aug. 28, 2015

Re: [Pharo-dev] OSX code signing

by Esteban Lorenzano

> On 28 Aug 2015, at 11:00, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 26 Aug 2015, at 18:39, Ben Coman <btc(a)openinworld.com> wrote: >> >> What are the future plans for dealing with OSX code signing? >> > We need to do it. We should have done it ages ago, nobody had the time. yes, it is in my infinite todo since a couple of years now :( maybe I will find the time when doing the spur transitionâ¦ Esteban >> > >> So if we can no longer store a writable Image under the Resources >> folder, what are the alternatives? >> >> 1. Deliver app with read-only Image under the Resources folder. The >> INI file can define the location of the writeable Image under >> ../{user}/Library/. When the VM starts, if the writable Image file >> does not exist, the VM transparently copies the read-only Image from >> resources to the writable location. >> > > I want to ship the an app called âPharo5â that contains the VM, sources > and a read-only image template. > > This just lives in /Applications. > > -> start it, it starts the template > -> save template, it saves a one file pharo image > -> klick on a pharo image, it starts the correct VM contained in Pharo<Version> package > >> 2. Use a launcher application like PharoLauncher. > > I would like to have the launcher concept be integrated with what i described. But I am not > sure I want just a launcher to start when clicking on âPharoâ. And it needs to play well with > people that manage images themselves. We want PharoLauncher as the default download from some time now. Againâ¦ no time to polish the detailsâ¦ :( > >> >> 3. For a "portable" app (e.g. on USB stick) push the app down one >> folder, so rather than putting the Win/Lin executables inside the OSX >> app, the top level folder contains folders Windows, Linux, Common, and >> the app. > > No, I would retire that concept. (I know some people love it, but I think it does > not fit into days world where the OS installs Apps). +42 Esteban > > Marcus > >

Aug. 28, 2015