- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Nautilus questions

by Esteban Lorenzano

Hi, Some remarks: Yes: - yes, we are still working on Nautilus, and some of the things we are trying now will change (for example, I do not think we need the history dropdown there having the back/forward iconsâ¦ and in any case since they are talking about the same, they should be close) - yes, we can add other functionality, as Franck posted, thatâs why we ask for those functionality. Now if nobody answers, do not expect we can know what you want :) - yes, using abbreviated names there is bad. (Hier., Com.) we need to find a better place. - yes, âvariablesâ is not so relevant and I would like to move it to a place where does not look as is. I use it all the time, but in regular programming people should not need to use it all the time. Weâll see. Nos: - no, we are not going to put back buttons in the middle of the browser: what is a toolbar, should be where toolsbars go. I know many if you are used to the older way, but that older way was bad: the original idea was to put functionality close to the coding areaâ¦ no reason to do that this days. - actually, I do not have more ânosâ for now, but I want to keep this open, for the future ;) Some others: - the fact that you never used âScopedâ is actually the reason why we put it in such a relevant place: is one of the most powerful functionalities of Nautilus and we want you to have access to it in a direct and visible place. So you can start to use it. Using âI never used itâ as an argument does not work because in exchange I can say âthis is the function I use the most of nautilusâ. Give it a try, is particularly useful for: a) applying refactors, b) search senders/implementors inside my project and not in all image. - actually, I would like to remove also the buttons that acts on classes (most of them needs to be tabs in the right places). In my ideal browser, functionality is distributed like this: â¦ but arriving to it is not so easy. In conclusion: We are doing some right steps. It is not finished, but we are not going to go back to older way :) cheers, Esteban > On 19 Aug 2015, at 10:04, Franck Warlouzet <franck.warlouzet(a)hotmail.fr> wrote: > > There is free space for another functionnality. I asked for ideas of buttons before doing Scoped one (and it appeared that scoped is used by people). Variables is often used too, and there is no shortcut to browse all the access to the variables of a class so I think it is needed. > They seem more needed than a button with an action which can be triggered by cmd + n or m in the same context than when you are about to clic on it (selector selected). > > The toolbar may take time to be loved, but I think new users are more used to a bar with functionnalities on top of a window than a middle bar. I would put all the buttons on top but I understand the strong link of hierarchy, class and comments with the classes panel so it is ok. > > And yes, the layout handling in this case is very painful. > > Franck > > From: kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com> > Date: Tue, 18 Aug 2015 20:49:34 +0000 > To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>; pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> > Subject: Re: [Pharo-dev] Nautilus questions > > I agree with your post about the buttons. Personally I have never used scoped or really need it as feature , I dont think I would be needing variables either. Actually two buttons I miss from Squeak is implementers and senders which I found super useful. > > On Tue, Aug 18, 2015 at 11:00 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > Hi, > > maybe I'm too picky, but I have couple of questions/remarks regarding current Nautilus UI. > Now, I'm happy that new features were added/reorganized, but it does feel it is a little bit chaotic right now. > > <2015-08-18_191053.png> > I would expect the left/right history buttons being right next to the History Navigator selector. That way history-related controls are together and the purpose of the buttons is obvious > > "Hier.", "Com."... abbreviating button labels? Really? > > âAnd finally, why was part of the buttons moved up? And part stayed down? > I know that you wanted to distinguish "Scoped", because it opens a new browser, and Variables, because they have intermediate menu (and later open another menu). > But I think the fact that Variables are tied to a particular selected class would make much more sense to place the button beside hierachy/class button. > > And opening Scoped can be denoted with an appropriate icon ( https://www.google.com/search?site=&tbm=isch&source=hp&biw=&bih=&q=new+wind… <https://www.google.com/search?site=&tbm=isch&source=hp&biw=&bih=&q=new+wind…> ) > > Placing them all on a single line would also save up vertical space, which considering we've added QualityAssistant and Rubric adds another line is quite valuable. > > (And finally the width of the buttons should perhaps match more closely the actual needs of the label, because now it's bit cramped.) > > <2015-08-18_214348.png> > â > And finally, code-wise I've never really interacted with Morphic and stayed in Spec, so when I was digging through code it seems that the way Morphs are composed are through these "addMorph:fullFrame: (LayoutFrame identity rightFraction: 0.10; yourself);" constructs sprinkled haphazardly throughout the code. Is there nothing like SpecLayout? Maybe it wasn't so hard once you get used to Morphic, because I spent probably more time doing elementary changes to layout than learning half of Spec... (Also since Spec can interoperate with Morphic, maybe the layout could also be adapted? Or slowly migrate Nautilus to Spec (if there are even plans like that)?) > > Now as I've mentioned I'm not an UI/UX expert, but you don't need to be a chef to tell when food isn't great (which is of course amplified by personal tastes). > > So unless I am the only person bothered by this, I would like to raise a discussion (or send a slice, but the way I've done the layout weirds me out, so I still want to look into that regardless). > > Cheers, > Peter

Aug. 19, 2015

Re: [Pharo-dev] WhatsUp from: 2015-08-17 until: 2015-08-31

by Dimitris Chloupis

The project is called Ephestos , goal is to use Pharo to script Blender You can watch a demo here https://www.youtube.com/watch?v=XPGDQc5LUvE Documentation can be found here http://kilon.gitbooks.io/ephestos/content/introduction/introduction.pier.ht… You no longer need to install Ephestos in Pharo via Gofer, latest version can be installed through Configuration Browser/ Catalog Browser with a single click. If you want more info you can find me online at the official irc pharo channel #pharo at freenode.net I have the nick name "kilon" or "thekilon" On Wed, Aug 19, 2015 at 10:33 AM Merwan Ouddane <merwanouddane(a)gmail.com> wrote: > That's awesome :) > > On the top of which project will you write this api ? > Le 19 aoÃ»t 2015 08:05, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a > Ã©crit : > >> Yeap that one. >> >> On Wed, Aug 19, 2015 at 12:30 AM Merwan Ouddane <merwanouddane(a)gmail.com> >> wrote: >> >>> >>> >>> On 18/08/2015 23:00, Dimitris Chloupis wrote: >>> >>> 1) bringing more Python support for Pharo, now I have added support for >>> python and blender types to be automagically converted to pharo objects . >>> Used and learn SmaCC. >>> 2) Gave a deep reading on Pharo auto completion. >>> 3) Study how Playgrounds draws its GUI to improve it by making far more >>> flexible. >>> 4) Study a new programming language Nim , for making dynamic libraries >>> for pharo , replacing C/C++. Possible scenario of porting SqueakNim to >>> Pharo. >>> >>> To Do >>> >>> 1) Improve my blue theme (Nireas) >>> 2) Create an API for Blender for Pharo >>> >>> >>> Blender ? >>> >>> This one: https://www.blender.org/features/ ? >>> >>> >>> 3) Create my own custom Playground which will be more powerful >>> 4) Integrate Nim with Pharo >>> >>> On Tue, Aug 18, 2015 at 6:23 PM Sean P. DeNigris <sean(a)clipperadams.com> >>> wrote: >>> >>>> ### Here's what I've been up to since the last WhatsUp: >>>> - Ported Moose issue tracker to GitHub >>>> - GT extension for presentations semi-auto-generated from Magritte >>>> descriptions >>>> - data, label, etc pre-filled by default >>>> - Magritte actions appear as e.g. presentation list selection context >>>> menu >>>> - Magritte >>>> - extension for above >>>> - many little fixes and enhancements >>>> - [WIP]: Created Glamour browsers from presentations >>>> - Glamour/GT patches >>>> - GSoC Mentoring for sQuick Smalltalk project >>>> >>>> ### What's next, until 2015-08-31 (*): >>>> - Camp Smalltalk Portland! >>>> >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> View this message in context: >>>> http://forum.world.st/WhatsUp-from-2015-08-17-until-2015-08-31-tp4843391p48… >>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>> Nabble.com. >>>> >>>> >>>

Aug. 19, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 19, 2015

[pharo-project/pharo-core] dc13d9: 50246

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: dc13d984876b1c6233851435d08a451bc6e73d05 https://github.com/pharo-project/pharo-core/commit/dc13d984876b1c6233851435… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-08-19 (Wed, 19 Aug 2015) Changed paths: R Collections-Streams.package/TextStream.class/README.md R Collections-Streams.package/TextStream.class/definition.st R Collections-Streams.package/TextStream.class/instance/accessing/nextPutAll_.st R Collections-Streams.package/TextStream.class/instance/as yet unclassified/applyAttribute_beginningAt_.st R Collections-Streams.package/TextStream.class/instance/private/withAttribute_do_.st R Collections-Streams.package/TextStream.class/instance/private/withAttributes_do_.st R Collections-Strings.package/String.class/instance/converting/asStringOrText.st M Compiler.package/ParseNode.class/instance/private/printSingleComment_on_indent_.st M Kernel.package/ClassCategoryReader.class/instance/fileIn%2FOut/scanFrom_.st M Kernel.package/ClassCommentReader.class/instance/fileIn%2FOut/scanFrom_.st R Kernel.package/CompiledMethod.class/instance/testing/hasReportableSlip.st R Kernel.package/Object.class/instance/converting/asStringOrText.st R Monticello.package/MCAddition.class/instance/accessing/sourceString.st R Monticello.package/MCAddition.class/instance/accessing/summary.st R Monticello.package/MCPatchOperation.class/instance/accessing/sourceString.st R Monticello.package/MCPatchOperation.class/instance/accessing/summary.st R Monticello.package/MCRemoval.class/instance/accessing/sourceString.st A MonticelloGUI.package/extension/MCAddition/instance/sourceString.st A MonticelloGUI.package/extension/MCAddition/instance/summary.st A MonticelloGUI.package/extension/MCPatchOperation/instance/sourceString.st A MonticelloGUI.package/extension/MCPatchOperation/instance/summary.st A MonticelloGUI.package/extension/MCRemoval/instance/sourceString.st A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeClassVariable.st A Reflectivity.package/extension/LiteralVariable/instance/afterLinks.st A Reflectivity.package/extension/LiteralVariable/instance/beforeHooks.st A Reflectivity.package/extension/LiteralVariable/instance/beforeLinks.st A Reflectivity.package/extension/LiteralVariable/instance/hasMetalink.st A Reflectivity.package/extension/LiteralVariable/instance/hasMetalinkAfter.st A Reflectivity.package/extension/LiteralVariable/instance/hasMetalinkBefore.st A Reflectivity.package/extension/LiteralVariable/instance/hasMetalinkInstead.st A Reflectivity.package/extension/LiteralVariable/instance/insteadLinks.st A Reflectivity.package/extension/LiteralVariable/instance/isCascade.st A Reflectivity.package/extension/LiteralVariable/instance/methodNode.st A Reflectivity.package/extension/LiteralVariable/instance/preambles.st M Reflectivity.package/extension/RBProgramNode/instance/hasMetalinkBefore.st M Ring-Core-Kernel.package/ManifestRingCoreKernel.class/class/meta-data - dependency analyser/manuallyResolvedDependencies.st R Ring-Core-Kernel.package/RGCommentDefinition.class/instance/converting/asStringOrText.st R Ring-Core-Kernel.package/RGMethodDefinition.class/instance/conversion/asStringOrText.st M Ring-Tests-Kernel.package/RGCommentDefinitionTest.class/instance/testing/testingConversion.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testAsMethodDefinition2.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50245.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50246.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50245.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50246.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/DangerousClassNotifier.class/class/validation/check_.st A Slot.package/LiteralVariable.class/instance/properties/hasProperty_.st A Slot.package/Slot.class/instance/properties/hasProperty_.st R System-Changes.package/ChangeRecord.class/instance/access/text.st M System-Changes.package/ChangeRecord.class/instance/initialization/fileIn.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/checkForSlips.st A System-Changes.package/ChangeSet.class/instance/filein%2Fout/hasReportableSlip_.st R System-CommandLine.package/VTermOutputDriver.class/class/examples/printText_.st R System-Sources.package/RemoteString.class/instance/accessing/text.st M Tests.package/FileStreamTest.class/instance/testing/testCachingNextChunkPut.st M Tests.package/FileStreamTest.class/instance/testing/testNextChunkOutOfBounds.st A Text-Core.package/TextStream.class/README.md A Text-Core.package/TextStream.class/definition.st A Text-Core.package/TextStream.class/instance/accessing/nextPutAll_.st A Text-Core.package/TextStream.class/instance/as yet unclassified/applyAttribute_beginningAt_.st A Text-Core.package/TextStream.class/instance/private/withAttribute_do_.st A Text-Core.package/TextStream.class/instance/private/withAttributes_do_.st A Text-Core.package/extension/ChangeRecord/instance/text.st A Text-Core.package/extension/Object/instance/asStringOrText.st A Text-Core.package/extension/RGCommentDefinition/instance/asStringOrText.st A Text-Core.package/extension/RGMethodDefinition/instance/asStringOrText.st A Text-Core.package/extension/RemoteString/instance/text.st A Text-Core.package/extension/String/instance/asStringOrText.st A Text-Core.package/extension/VTermOutputDriver/class/printText_.st Log Message: ----------- 50246 16239 hasReportTableSlip is not packaged well and more https://pharo.fogbugz.com/f/cases/16239 16264 update ring-core-kernel dependencies https://pharo.fogbugz.com/f/cases/16264 16272 Reflectivity: start of code gen for Globals https://pharo.fogbugz.com/f/cases/16272 16192 Cut Text-Core dependencies https://pharo.fogbugz.com/f/cases/16192 http://files.pharo.org/image/50/50246.zip

Aug. 19, 2015

Re: [Pharo-dev] Nautilus questions

by Franck Warlouzet

There is free space for another functionnality. I asked for ideas of buttons before doing Scoped one (and it appeared that scoped is used by people). Variables is often used too, and there is no shortcut to browse all the access to the variables of a class so I think it is needed. They seem more needed than a button with an action which can be triggered by cmd + n or m in the same context than when you are about to clic on it (selector selected). The toolbar may take time to be loved, but I think new users are more used to a bar with functionnalities on top of a window than a middle bar. I would put all the buttons on top but I understand the strong link of hierarchy, class and comments with the classes panel so it is ok. And yes, the layout handling in this case is very painful. Franck From: kilon.alios(a)gmail.com Date: Tue, 18 Aug 2015 20:49:34 +0000 To: pharo-dev(a)lists.pharo.org; pharo-users(a)lists.pharo.org Subject: Re: [Pharo-dev] Nautilus questions I agree with your post about the buttons. Personally I have never used scoped or really need it as feature , I dont think I would be needing variables either. Actually two buttons I miss from Squeak is implementers and senders which I found super useful. On Tue, Aug 18, 2015 at 11:00 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: Hi, maybe I'm too picky, but I have couple of questions/remarks regarding current Nautilus UI.Now, I'm happy that new features were added/reorganized, but it does feel it is a little bit chaotic right now. I would expect the left/right history buttons being right next to the History Navigator selector. That way history-related controls are together and the purpose of the buttons is obvious "Hier.", "Com."... abbreviating button labels? Really? âAnd finally, why was part of the buttons moved up? And part stayed down?I know that you wanted to distinguish "Scoped", because it opens a new browser, and Variables, because they have intermediate menu (and later open another menu).But I think the fact that Variables are tied to a particular selected class would make much more sense to place the button beside hierachy/class button. And opening Scoped can be denoted with an appropriate icon ( https://www.google.com/search?site=&tbm=isch&source=hp&biw=&bih=&q=new+wind… ) Placing them all on a single line would also save up vertical space, which considering we've added QualityAssistant and Rubric adds another line is quite valuable. (And finally the width of the buttons should perhaps match more closely the actual needs of the label, because now it's bit cramped.) â And finally, code-wise I've never really interacted with Morphic and stayed in Spec, so when I was digging through code it seems that the way Morphs are composed are through these "addMorph:fullFrame: (LayoutFrame identity rightFraction: 0.10; yourself);" constructs sprinkled haphazardly throughout the code. Is there nothing like SpecLayout? Maybe it wasn't so hard once you get used to Morphic, because I spent probably more time doing elementary changes to layout than learning half of Spec... (Also since Spec can interoperate with Morphic, maybe the layout could also be adapted? Or slowly migrate Nautilus to Spec (if there are even plans like that)?) Now as I've mentioned I'm not an UI/UX expert, but you don't need to be a chef to tell when food isn't great (which is of course amplified by personal tastes). So unless I am the only person bothered by this, I would like to raise a discussion (or send a slice, but the way I've done the layout weirds me out, so I still want to look into that regardless). Cheers,Peter

Aug. 19, 2015

Re: [Pharo-dev] WhatsUp from: 2015-08-17 until: 2015-08-31

by Merwan Ouddane

That's awesome :) On the top of which project will you write this api ? Le 19 aoÃ»t 2015 08:05, "Dimitris Chloupis" <kilon.alios(a)gmail.com> a Ã©crit : > Yeap that one. > > On Wed, Aug 19, 2015 at 12:30 AM Merwan Ouddane <merwanouddane(a)gmail.com> > wrote: > >> >> >> On 18/08/2015 23:00, Dimitris Chloupis wrote: >> >> 1) bringing more Python support for Pharo, now I have added support for >> python and blender types to be automagically converted to pharo objects . >> Used and learn SmaCC. >> 2) Gave a deep reading on Pharo auto completion. >> 3) Study how Playgrounds draws its GUI to improve it by making far more >> flexible. >> 4) Study a new programming language Nim , for making dynamic libraries >> for pharo , replacing C/C++. Possible scenario of porting SqueakNim to >> Pharo. >> >> To Do >> >> 1) Improve my blue theme (Nireas) >> 2) Create an API for Blender for Pharo >> >> >> Blender ? >> >> This one: https://www.blender.org/features/ ? >> >> >> 3) Create my own custom Playground which will be more powerful >> 4) Integrate Nim with Pharo >> >> On Tue, Aug 18, 2015 at 6:23 PM Sean P. DeNigris <sean(a)clipperadams.com> >> wrote: >> >>> ### Here's what I've been up to since the last WhatsUp: >>> - Ported Moose issue tracker to GitHub >>> - GT extension for presentations semi-auto-generated from Magritte >>> descriptions >>> - data, label, etc pre-filled by default >>> - Magritte actions appear as e.g. presentation list selection context >>> menu >>> - Magritte >>> - extension for above >>> - many little fixes and enhancements >>> - [WIP]: Created Glamour browsers from presentations >>> - Glamour/GT patches >>> - GSoC Mentoring for sQuick Smalltalk project >>> >>> ### What's next, until 2015-08-31 (*): >>> - Camp Smalltalk Portland! >>> >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/WhatsUp-from-2015-08-17-until-2015-08-31-tp4843391p48… >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >>

Aug. 19, 2015

Re: [Pharo-dev] WhatsUp from: 2015-08-17 until: 2015-08-31

by Max Leske

> On 17 Aug 2015, at 07:00, seaside(a)rmod.lille.inria.fr wrote: > > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > - The build process for the Windows VM is now completely scripted, no more hand waving and magic tricks - Updated README for Windows VM to reflect the simpler build process - libgit2 and libssh2 now compile and link nicely on the Windows, Linux and Mac VMs - upgraded libgit2 to version 0.23 - Linux build for libgit2 is now green. Windows build exhibits some very strange problems with unzipping, will fix that later. - Discovered a possible bug in libssh2 on Linux which prevents libgit2 from working with ssh > > ### What's next, until 2015-08-31 (*): > - Investigate possible libssh2 bug and talk to libssh2 devs - try to fix Windows build of libgit2 > > (*) we'll be expecting results by then ;) >

Aug. 19, 2015

Re: [Pharo-dev] World Menu associated mouse click

by Dimitris Chloupis

Can't say I use it much either. On Wed, Aug 19, 2015 at 4:42 AM Ben Coman <btc(a)openinworld.com> wrote: > > On Tue, Aug 18, 2015 at 8:09 PM Ben Coman <btc(a)openinworld.com> wrote: > >> > >> Opened issue with fix - https://pharo.fogbugz.com/default.asp?16265 > >> > >> On Wed, Aug 19, 2015 at 12:13 AM, Ben Coman <btc(a)openinworld.com> > wrote: > >> >>>>> -----Message d'origine----- > >> >>>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la > part > >> >>>>> de > >> >>>>> Ben Coman > >> >>>>> A while back on reddit someone complained about the World Menu > being > >> >>>>> associated with left-mouse-click. I have come to agree. The > World > >> >>>>> Menu > >> >>>>> provides the actions available in the context of the World, i.e. > >> >>>>> the World's context-menu - but its not invoked by the usual > >> >>>>> convention > >> >>>>> for context menus, which is the right-mouse-click. > >> >>>>> > >> >>>>> By way of example, in a fresh image and open one Playground. > >> >>>>> > >> >>>>> * First right-click the Playground. Up comes the Playground's > >> >>>>> context-menu as expected per industry wide conventions. > >> >>>>> > >> >>>>> * Then right-click the background. Doh! Its not consistent, thats > >> >>>>> not > >> >>>>> the World's context-menu. "WTH is that?" says a newbie in > surprise. > >> >>>>> (Btw, who uses that list of open windows ? I *never* do and might > >> >>>>> suggest that function be moved to a meta-mouse-click.) > >> >>>>> > >> >>>>> So can we discuss changing the World Menu to be invoked by the > >> >>>>> context-click (i.e. right-click) ? > >> >>>>> > >> >>>>> cheers -ben > > On Wed, Aug 19, 2015 at 4:42 AM, Dimitris Chloupis > <kilon.alios(a)gmail.com> wrote: > > and what about the existing right click menu for selecting morphs ? > > Well I never use it ;) but I presume from your question that you do. > With no further action, this behaviour will be swapped to the > left-click. You can test this yourself in the latest build with the > preference setting mentioned previously. To me though, as a separate > issue, this is meta behaviour and should be invoked the same as > bringing up halos, leaving the left-click unassigned and available for > *something-else* application specific. > > cheers -ben > >

Aug. 19, 2015

Re: [Pharo-dev] WhatsUp from: 2015-08-17 until: 2015-08-31

by Dimitris Chloupis

Yeap that one. On Wed, Aug 19, 2015 at 12:30 AM Merwan Ouddane <merwanouddane(a)gmail.com> wrote: > > > On 18/08/2015 23:00, Dimitris Chloupis wrote: > > 1) bringing more Python support for Pharo, now I have added support for > python and blender types to be automagically converted to pharo objects . > Used and learn SmaCC. > 2) Gave a deep reading on Pharo auto completion. > 3) Study how Playgrounds draws its GUI to improve it by making far more > flexible. > 4) Study a new programming language Nim , for making dynamic libraries for > pharo , replacing C/C++. Possible scenario of porting SqueakNim to Pharo. > > To Do > > 1) Improve my blue theme (Nireas) > 2) Create an API for Blender for Pharo > > > Blender ? > > This one: https://www.blender.org/features/ ? > > > 3) Create my own custom Playground which will be more powerful > 4) Integrate Nim with Pharo > > On Tue, Aug 18, 2015 at 6:23 PM Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> ### Here's what I've been up to since the last WhatsUp: >> - Ported Moose issue tracker to GitHub >> - GT extension for presentations semi-auto-generated from Magritte >> descriptions >> - data, label, etc pre-filled by default >> - Magritte actions appear as e.g. presentation list selection context >> menu >> - Magritte >> - extension for above >> - many little fixes and enhancements >> - [WIP]: Created Glamour browsers from presentations >> - Glamour/GT patches >> - GSoC Mentoring for sQuick Smalltalk project >> >> ### What's next, until 2015-08-31 (*): >> - Camp Smalltalk Portland! >> >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/WhatsUp-from-2015-08-17-until-2015-08-31-tp4843391p48… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

Aug. 19, 2015

Re: [Pharo-dev] World Menu associated mouse click

by Ben Coman

> On Tue, Aug 18, 2015 at 8:09 PM Ben Coman <btc(a)openinworld.com> wrote: >> >> Opened issue with fix - https://pharo.fogbugz.com/default.asp?16265 >> >> On Wed, Aug 19, 2015 at 12:13 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >>>>> -----Message d'origine----- >> >>>>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part >> >>>>> de >> >>>>> Ben Coman >> >>>>> A while back on reddit someone complained about the World Menu being >> >>>>> associated with left-mouse-click. I have come to agree. The World >> >>>>> Menu >> >>>>> provides the actions available in the context of the World, i.e. >> >>>>> the World's context-menu - but its not invoked by the usual >> >>>>> convention >> >>>>> for context menus, which is the right-mouse-click. >> >>>>> >> >>>>> By way of example, in a fresh image and open one Playground. >> >>>>> >> >>>>> * First right-click the Playground. Up comes the Playground's >> >>>>> context-menu as expected per industry wide conventions. >> >>>>> >> >>>>> * Then right-click the background. Doh! Its not consistent, thats >> >>>>> not >> >>>>> the World's context-menu. "WTH is that?" says a newbie in surprise. >> >>>>> (Btw, who uses that list of open windows ? I *never* do and might >> >>>>> suggest that function be moved to a meta-mouse-click.) >> >>>>> >> >>>>> So can we discuss changing the World Menu to be invoked by the >> >>>>> context-click (i.e. right-click) ? >> >>>>> >> >>>>> cheers -ben On Wed, Aug 19, 2015 at 4:42 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > and what about the existing right click menu for selecting morphs ? Well I never use it ;) but I presume from your question that you do. With no further action, this behaviour will be swapped to the left-click. You can test this yourself in the latest build with the preference setting mentioned previously. To me though, as a separate issue, this is meta behaviour and should be invoked the same as bringing up halos, leaving the left-click unassigned and available for *something-else* application specific. cheers -ben

Aug. 19, 2015