- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

by Serge Stinckwich

On Thu, Jun 16, 2016 at 11:08 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Alistair, > > On Thu, Jun 16, 2016 at 1:43 PM, Alistair Grant <akgrant0710(a)gmail.com> > wrote: >> >> On Thu, Jun 16, 2016 at 01:07:23PM -0700, Eliot Miranda wrote: >> > Hi All, >> > >> > so after fixing "git remote get-url origin" to fail over to "git remote >> > show origin | filter and munge" the culture shock of "git commit -a" >> > (git >> > commit does nothing ?!?!?) >> >> "git commit" will commit anything that has been "git add"ed to the >> index. -a is a convenience to automatically stage files that have been >> modified. > > > What I don't understand is how, or indeed why, one stages modified files. I > get that adding files requires informing git. But why doesn't "git commit" > commit modified files by default? Why do I have to use git commit -a to > include modified files? Because you can choose what files will be part of the commit (cherry-picking changes). -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

June 16, 2016

Re: [Pharo-dev] GT-Spotter dive in shortcut

by Nicolai Hess

2016-06-16 22:45 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > I think we are mixing the topics a bit. The #meta discussion is not > specific to Spotter actions. > On windows, it is. Because on windows #meta is mapped to #ctrl, and you can use ctrl+left/right for moving by "words". This works in a browser, an editor, pharos text components but *not* in spotter because spotter redefines this keystrokes for dive in /out. Currently, both ctrl+left/right and alt+left/right (and shift for selection) are working in rubric for moving by "word". But only because the (old) shortcut (cmd/shiftcmd) action dispatcher explicitly allows both. If we want to remove this and use the KMDispatcher framework only, we *need* to define only one mapping, otherwise you won't be able to use dive in/out in spotter. (Or you could modify spotter to register(overwrite) the mapping on the textfield instead of the spotter morph). > The idea was to offer a uniform support of keybindings in Pharo, in > general. exactly, and using ctrl+left/right uniformly in editor and external tools would be great. > Then Guille etal added #meta to have a predictable mapping. Yes, and to make this work, we have to remove the old keymapping implementation (cmd/shiftcmd action map) and use the KMDispatcher registration. But I can only continue with this if we have a decision what to use, (windows/linux: either ctrl+arrow or alt+arrow, mac: whatever is used on a mac for text navigation) All #cmd places were changed to #meta, and since then we should not use > explicitly #cmd anymore, except when we know we are on Mac. For a portable > modifier, we should only use #meta. > > At this point, both Rubric and Spotter use #meta. #meta maps on: > - Mac: Command > - Win: Control > - Linus: Control > > This means that #alt is now a portable modifier that will not conflict > with #meta, so we can now think of using that one in combination with #meta. > You can not use #alt modifier on windows. A shortcut definition like $g alt is never recognized. You have to define it $g command to make it work with as "alt+g"-keycombination (on windows). > For text navigation, the situation is a bit complicated. On Win/Linux, > Ctrl+Right/Left moves the cursor between words. On Mac, Cmd+Right/Left > moves the cursor at the end/beginning of line. So, using #meta for text > navigation between words is not entirely accurate. We should use #ctrl > instead. > > This would anyway mean that it would be an option to use #alt for Spotter > now. But, if we are at it, would anyone be interested in working on > revisiting the overall keybindings in Pharo? > > Cheers, > Doru > > > > > On Jun 16, 2016, at 10:22 AM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > > > > > > > > 2016-06-07 16:12 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > > We can, but I remember there were some discussions and it was decided to > use meta everywhere. > > > > Cheers, > > Andrei > > > > > > If we don't change this, I'll use cmd+left cmd+right in rubric, but this > is bad, because all other navigate/select+navigate shortcuts would use meta > as shortcut modifier. > > > > What are the arguments for using meta for dive-in/out shortcuts ? > > > > > > > > On Tue, Jun 7, 2016 at 3:49 PM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > > > > > > 2016-06-07 15:08 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > > During Pharo 5 most shortcuts from tools were changed to use "meta" > instead of cmd. > > > > Cheers, > > Andrei > > > > Can we change this for spotter ? cmd instead of meta > > > > ctrl left/right is often used for text components to move to > next/previous word. > > > > > > > > On Tue, Jun 7, 2016 at 2:18 PM, Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > > > > > > 2016-06-07 13:57 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > > Am 07.06.2016 1:56 nachm. schrieb "Henrik Nergaard" < > henrik.nergaard(a)uia.no>: > > > > > > IIRC the shortcut is not changed, it still is meta+right(+shift). Only > the tooltip was changed to display the system specific key instead of âcmdâ > so for Windows/Linux this would be âctrlâ. > > > > > > No, it changed > > > > In #40624, for example, it was cmd (alt-key on windows ) right/shift > right > > > > > > > > > > > > > > > > Best regards, > > > > > > Henrik > > > > > > > > > > > > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf > Of Nicolai Hess > > > Sent: Tuesday, June 7, 2016 12:56 PM > > > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Subject: [Pharo-dev] GT-Spotter dive in shortcut > > > > > > > > > > > > Why did the shortcut for dive-in element/category changed from > > > > > > cmd+right > > > > > > cmd+shift+right > > > > > > to > > > > > > ctrl+right > > > ctrl+shift+right > > > > > > I know there were some discussions about this and that the behavior > changed some > > > > > > time ago, but I don't know the rational behind this. > > > > > > thanks > > > > > > nicolai > > > > > > > > > > > > > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > > >

June 16, 2016

Re: [Pharo-dev] Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

by Eliot Miranda

Hi Alistair, On Thu, Jun 16, 2016 at 1:43 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Thu, Jun 16, 2016 at 01:07:23PM -0700, Eliot Miranda wrote: > > Hi All, > > > > so after fixing "git remote get-url origin" to fail over to "git remote > > show origin | filter and munge" the culture shock of "git commit -a" (git > > commit does nothing ?!?!?) > > "git commit" will commit anything that has been "git add"ed to the > index. -a is a convenience to automatically stage files that have been > modified. > What I don't understand is how, or indeed why, one stages modified files. I get that adding files requires informing git. But why doesn't "git commit" commit modified files by default? Why do I have to use git commit -a to include modified files? > > HTH, > Alistair > > > -- _,,,^..^,,,_ best, Eliot

June 16, 2016

Re: [Pharo-dev] Implementing algorithms on polygons

by Peter Uhnak

On Thu, Jun 16, 2016 at 08:14:35PM +0100, serge.stinckwich(a)gmail.com wrote: > Hi Ralph, > > I guess you should ask your question on pharo-users instead of pharo-dev. > > Did you have a look to Voronoi diagrams implemented by Natalia ? http://natalia.tymch.uk/RTVoronyjDiagram/ The Voronoj diagram also uses Geometry package for doing some computations. Geometry was republished here https://github.com/peteruhnak/geometry and is currently automatically loaded by Roassal (I use it for some computations there). So if you install Roassal you should already see it (or follow the instructions above). I see that there's a Polygon class, but it's quite simple (so most work of the voronoj is in the voronoj repo I guess). It would be great to have a general-purpose library for doing computational geometry. Peter > > Sent from my iPhone > > > On 16 juin 2016, at 19:55, Ralph Boland <rpboland(a)gmail.com> wrote: > > > > I have some algorithms on polygons I would like to implement. > > When implemented I will release my implementations as Squeak > > or Pharo packages under an MIT licence. > > > > What does Pharo have to offer in terms of a GUI for this? > > > > It would also be helpful if the package already had an implementation > > of an algorithm for triangulating polygons. > > > > An implementation of an algorithms for constructing Voronoi diagrams > > of a point set would also be useful. > > > > Any advice appreciated. > > > > Note: earlier I made a similar post on one of the Squeak mailing lists. > > > > Are there anyone who might be interested in my algorithms? > > I won't go into details here but I am likely to implement my own > > triangulation algorithm among others and it would be nice if this > > implementation in particular was used by someone or some package. > > > > Ralph Boland > > >

June 16, 2016

Re: [Pharo-dev] GT-Spotter dive in shortcut

by Tudor Girba

Hi, I think we are mixing the topics a bit. The #meta discussion is not specific to Spotter actions. The idea was to offer a uniform support of keybindings in Pharo, in general. Then Guille etal added #meta to have a predictable mapping. All #cmd places were changed to #meta, and since then we should not use explicitly #cmd anymore, except when we know we are on Mac. For a portable modifier, we should only use #meta. At this point, both Rubric and Spotter use #meta. #meta maps on: - Mac: Command - Win: Control - Linus: Control This means that #alt is now a portable modifier that will not conflict with #meta, so we can now think of using that one in combination with #meta. For text navigation, the situation is a bit complicated. On Win/Linux, Ctrl+Right/Left moves the cursor between words. On Mac, Cmd+Right/Left moves the cursor at the end/beginning of line. So, using #meta for text navigation between words is not entirely accurate. We should use #ctrl instead. This would anyway mean that it would be an option to use #alt for Spotter now. But, if we are at it, would anyone be interested in working on revisiting the overall keybindings in Pharo? Cheers, Doru > On Jun 16, 2016, at 10:22 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-06-07 16:12 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > We can, but I remember there were some discussions and it was decided to use meta everywhere. > > Cheers, > Andrei > > > If we don't change this, I'll use cmd+left cmd+right in rubric, but this is bad, because all other navigate/select+navigate shortcuts would use meta as shortcut modifier. > > What are the arguments for using meta for dive-in/out shortcuts ? > > > > On Tue, Jun 7, 2016 at 3:49 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-06-07 15:08 GMT+02:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > During Pharo 5 most shortcuts from tools were changed to use "meta" instead of cmd. > > Cheers, > Andrei > > Can we change this for spotter ? cmd instead of meta > > ctrl left/right is often used for text components to move to next/previous word. > > > > On Tue, Jun 7, 2016 at 2:18 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-06-07 13:57 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > Am 07.06.2016 1:56 nachm. schrieb "Henrik Nergaard" <henrik.nergaard(a)uia.no>: > > > > IIRC the shortcut is not changed, it still is meta+right(+shift). Only the tooltip was changed to display the system specific key instead of âcmdâ so for Windows/Linux this would be âctrlâ. > > > No, it changed > > In #40624, for example, it was cmd (alt-key on windows ) right/shift right > > > > > > > > > > Best regards, > > > > Henrik > > > > > > > > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Nicolai Hess > > Sent: Tuesday, June 7, 2016 12:56 PM > > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > Subject: [Pharo-dev] GT-Spotter dive in shortcut > > > > > > > > Why did the shortcut for dive-in element/category changed from > > > > cmd+right > > > > cmd+shift+right > > > > to > > > > ctrl+right > > ctrl+shift+right > > > > I know there were some discussions about this and that the behavior changed some > > > > time ago, but I don't know the rational behind this. > > > > thanks > > > > nicolai > > > > > > > > > > -- www.tudorgirba.com www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

June 16, 2016

Re: [Pharo-dev] Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

by Alistair Grant

On Thu, Jun 16, 2016 at 01:07:23PM -0700, Eliot Miranda wrote: > Hi All, > > so after fixing "git remote get-url origin" to fail over to "git remote > show origin | filter and munge" the culture shock of "git commit -a" (git > commit does nothing ?!?!?) "git commit" will commit anything that has been "git add"ed to the index. -a is a convenience to automatically stage files that have been modified. HTH, Alistair

June 16, 2016

Re: [Pharo-dev] [Moose-dev] What is GTInspector using to print UUID?

by Tudor Girba

Hi, More specifically, you can find this specific extension here: SequenceableCollection>>gtInspectorItemsIn: composite ^ composite table title: 'Items'; display: [ :aCollection | [(1 to: self size) collect: [ :index | index -> (self at: index) ]] on:Error do:[#()]]; beMultiple; searchOn: [:text :each | Smalltalk compiler evaluate: ' | entity each | each := self. entity := each.', text for: each value logged: false]; column: 'Index' evaluated: [ :assoc | assoc key asString ] width: 50; column: 'Item' evaluated: [ :assoc | GTObjectPrinter new asTruncatedTextFrom: assoc value ]; send: [ :result | result isNil ifTrue: [ nil ] ifFalse: [ result value size = 1 ifTrue: [result anyOne value] ifFalse: [self species withAll: (result collect: [:each | each value])]]]; showOnly: 50; helpMessage: 'Quick selection field. Given your INPUT, it executes: self select: [:each | INPUT ]'. And then: GTObjectPrinter>>asTruncatedTextFrom: anObject ^ [ Text fromString: (anObject gtDisplayString replaceAll: String cr with: String space) ] on: Error do: [ Text string: 'error printing' attribute: TextColor red ] So, in the end, you want to override gtDisplayOn: in your class. Cheers, Doru > On Jun 16, 2016, at 2:19 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Peter, > > It's done as a GT extension: see #gtInspectorItemsIn: in class SequencableCollection > and (as nothing is carved in stone in Pharo) for sure this can be changed (or overwritten) ;) > > HTH > T. > > Gesendet: Donnerstag, 16. Juni 2016 um 14:10 Uhr > Von: "Peter UhnÃ¡k" <i.uhnak(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org>, "Moose-related development" <moose-dev(a)list.inf.unibe.ch> > Betreff: [Pharo-dev] What is GTInspector using to print UUID? > Hi, > > how inspector decides what to print in the table/headings/etc? > Because for UUID it prints the bytes (I guess because it's child of ByteArray?), however that's rarely useful for UUID, as normally you want to see the #asString representation. > > > <Mail Attachment.png> > â > Can this be changed? > > Thanks, > Peter > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

June 16, 2016

Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

by Eliot Miranda

Hi All, so after fixing "git remote get-url origin" to fail over to "git remote show origin | filter and munge" the culture shock of "git commit -a" (git commit does nothing ?!?!?) I have a VM that outputs a reasonable version info: /Users/eliot/oscogvm/build.macos32x86/squeak.cog.spur/CocoaFast.app/Contents/MacOS/Squeak 5.0 5.0.201606161953 Mac OS X built on Jun 16 2016 12:56:52 PDT Compiler: 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57) [Production Spur VM] CoInterpreter VMMaker.oscog-eem.1886 uuid: d413db9f-37cc-4c5d-bfc6-87b11203ee96 Jun 16 2016 StackToRegisterMappingCogit VMMaker.oscog-eem.1886 uuid: d413db9f-37cc-4c5d-bfc6-87b11203ee96 Jun 16 2016 VM: r201606161953 http://github.com/OpenSmalltalk/vm $ Date: Thu Jun 16 12:53:33 2016 -0700 $ Plugins: r201606161953 http://github.com/OpenSmalltalk/vm $ Which begs the question how do I differentiate this from something built officially via Travis? Arguably the URL is wrong, and should only say " http://github.com/OpenSmalltalk/vm" for travis builds, and perhaps should just include my local hostname and current directory when I make any kind of local modification. So the above would read ... VM: r201606161953 McStalker:?users/eliot/oscogvm $ Date: Thu Jun 16 12:53:33 2016 -0700 $ Plugins: r201606161953 McStalker:?users/eliot/oscogvm $ Alternatively we could add another field, or modify one of the existing fields to say "I'm official" however one would do that. I don't know how, I just know we need this. I shouldn't be able to pollute the VM pool by putting some VM on some site somewhere that i just happened to build after several sherries and some cannabis brownies that looks to all intents and purposes just like a VM built by our official Travis slaves. Hic. Chillin' _,,,^..^,,,_ best, Eliot

June 16, 2016

Re: [Pharo-dev] Implementing algorithms on polygons

by Damien Pollet

Le jeudi 16 juin 2016, Ralph Boland <rpboland(a)gmail.com> a Ã©crit : > I have some algorithms on polygons I would like to implement. > When implemented I will release my implementations as Squeak > or Pharo packages under an MIT licence. > > What does Pharo have to offer in terms of a GUI for this? Depends what you envision as GUI. I'd point you to Athens (2D vector graphics), Bloc (Pharo's next GUI framework), Roassal (visualization DSL)â¦ It would also be helpful if the package already had an implementation > of an algorithm for triangulating polygons. > > An implementation of an algorithms for constructing Voronoi diagrams > of a point set would also be useful. Check http://natalia.tymch.uk/RTVoronyjDiagram/ > Any advice appreciated. > > Note: earlier I made a similar post on one of the Squeak mailing lists. > > Are there anyone who might be interested in my algorithms? > I won't go into details here but I am likely to implement my own > triangulation algorithm among others and it would be nice if this > implementation in particular was used by someone or some package. > Computational geometry is something I would explore for fun, but I don't have a professional use-case for it :) -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

June 16, 2016

Re: [Pharo-dev] Implementing algorithms on polygons

by serge.stinckwich＠gmail.com

Hi Ralph, I guess you should ask your question on pharo-users instead of pharo-dev. Did you have a look to Voronoi diagrams implemented by Natalia ? http://natalia.tymch.uk/RTVoronyjDiagram/ Sent from my iPhone > On 16 juin 2016, at 19:55, Ralph Boland <rpboland(a)gmail.com> wrote: > > I have some algorithms on polygons I would like to implement. > When implemented I will release my implementations as Squeak > or Pharo packages under an MIT licence. > > What does Pharo have to offer in terms of a GUI for this? > > It would also be helpful if the package already had an implementation > of an algorithm for triangulating polygons. > > An implementation of an algorithms for constructing Voronoi diagrams > of a point set would also be useful. > > Any advice appreciated. > > Note: earlier I made a similar post on one of the Squeak mailing lists. > > Are there anyone who might be interested in my algorithms? > I won't go into details here but I am likely to implement my own > triangulation algorithm among others and it would be nice if this > implementation in particular was used by someone or some package. > > Ralph Boland >

June 16, 2016