Moose art visualizations if not more from Phratch et als can make a mark
here.
https://devart.withgoogle.com/?utm_source=emailutm_medium=gsputm_campaign=gspb
In Pharo3, there seems to be new shortcuts going on.
These do interfere with TWM ones (or the other way around).
What to do to get this to work again?
TWMKeyMappingbuildKeyMappingOn: aBuilder
keymap
See shortucts accessor to add/change a shortcut
self shortcutsActionAndKeysDo: [:action :keys|
Hi,
If you want to install GToolkit (the project that contains GTInspector,
GTPlayground and GTDebugger) in your image, you can follow one of the
options as described here:
http://www.humane-assessment.com/blog/installing-gtoolkit
If you give it a try, please let us know how it works for you.
Am 25.03.2014 um 00:33 schrieb p...@highoctane.be p...@highoctane.be:
On Tue, Mar 25, 2014 at 12:11 AM, Eliot Miranda eliot.mira...@gmail.com
wrote:
On Mon, Mar 24, 2014 at 4:02 PM, p...@highoctane.be p...@highoctane.be
wrote:
I am curious.
Maybe on the first one, substitute
I wanted to use a MethodToolbar as part of a Nautilus plugin.
Ok, I can use the widget in with an openWithSpec but how can I put this
into a widget that Nautilus will accept as a plugin?
| b |
b := MethodToolbar new.
b openWithSpec.
b method: method from plugin...
Phil
Am 24.03.2014 um 23:51 schrieb Pavel Krivanek pavel.kriva...@gmail.com:
Who can find the most useful usage of this?
thisContext instVarNamed: #receiver put: 42.
self factorial
GOTO statement in Pharo:
FileStream stdout nextPutAll: 'Hello world'; lf.
On 24 mars 2014, at 23:30, p...@highoctane.be wrote:
On a fresh 3.0, there are Trait1, Trait2 and Trait3 in Smalltalk globals
allClassesAndTraits
These 3 look like they are equivalents to Trait. What are these for?
That's just some test fixtures.
Phil
On Tue, Mar 25, 2014 at 8:17 AM, Tudor Girba tu...@tudorgirba.com wrote:
Hi,
If you want to install GToolkit (the project that contains GTInspector,
GTPlayground and GTDebugger) in your image, you can follow one of the
options as described here:
This doesn't work for building the MathodToolbar widget.
MethodToolbar defaultSpec buildWithSpec
#DNU SpecLayoutbuildWithSpec
MethodToolbar classdefaultSpec
spec
^ SpecLayout composed
newRow: [ :row |
row
add: #(model browseModel);
add: #(model sendersModel);
add: #(model implementorsModel);
On 25 Mar 2014, at 10:02, p...@highoctane.be wrote:
Question: if one has opened a Miller column too far, how can we close that
one? It was annoying to have to use to precisely use the scrollbar down there
to get back to where I was. And if the column is not out of view, it keeps on
MethodToolbar new buildWithSpec
Ben
On 25 Mar 2014, at 10:09, p...@highoctane.be wrote:
This doesn't work for building the MathodToolbar widget.
MethodToolbar defaultSpec buildWithSpec
#DNU SpecLayoutbuildWithSpec
MethodToolbar classdefaultSpec
spec
^ SpecLayout composed
On 24 March 2014 23:33, p...@highoctane.be p...@highoctane.be wrote:
On Tue, Mar 25, 2014 at 12:11 AM, Eliot Miranda eliot.mira...@gmail.com
wrote:
On Mon, Mar 24, 2014 at 4:02 PM, p...@highoctane.be p...@highoctane.be
wrote:
I am curious.
Maybe on the first one, substitute something
On Tue, Mar 25, 2014 at 12:05 PM, Frank Shearar frank.shea...@gmail.comwrote:
On 24 March 2014 23:33, p...@highoctane.be p...@highoctane.be wrote:
On Tue, Mar 25, 2014 at 12:11 AM, Eliot Miranda eliot.mira...@gmail.com
wrote:
On Mon, Mar 24, 2014 at 4:02 PM, p...@highoctane.be
Branch: refs/heads/3.0
Home: https://github.com/pharo-project/pharo-core
Commit: 906370dc243cd777ab55c0c542de1dcf7bed7fda
https://github.com/pharo-project/pharo-core/commit/906370dc243cd777ab55c0c542de1dcf7bed7fda
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Branch: refs/tags/30800
Home: https://github.com/pharo-project/pharo-core
On 22 March 2014 15:11, Pharo4Stef pharo4s...@free.fr wrote:
Just for the record, do you realise that this is between two C libraries
(easy to debug)?
I didn't tried to debug it, i can't bet it would be easy (need to build a
debug version of cairo first)
but it worth trying.
Meanwhile i will
On 24 March 2014 22:54, p...@highoctane.be p...@highoctane.be wrote:
On Mon, Mar 24, 2014 at 8:23 PM, Alexandre Bergel alexandre.ber...@me.com
wrote:
I am working on a memory model for expandable collection in Pharo.
Currently, OrderedCollection, Dictionary and other expandable collections
On Tue, Mar 25, 2014 at 1:05 PM, Igor Stasenko siguc...@gmail.com wrote:
On 24 March 2014 22:54, p...@highoctane.be p...@highoctane.be wrote:
On Mon, Mar 24, 2014 at 8:23 PM, Alexandre Bergel
alexandre.ber...@me.com wrote:
I am working on a memory model for expandable collection in
Great work..!
Hope it grows leaps and bounds like Heroku or AWS..!
Excellent!
This goes in the direction of Alfred or Quicksilver. I worked on a design
(no implementation yet) that goes in the same direction. I think we
definitely need to get more in this direction, and that we should make it
easy for people to hook their own matchers. For example, when I start
I would love to have it the other way around: that Alfred can browse a Pharo
image :)
Ben
On 25 Mar 2014, at 14:41, Tudor Girba tu...@tudorgirba.com wrote:
Excellent!
This goes in the direction of Alfred or Quicksilver. I worked on a design (no
implementation yet) that goes in the same
What about doing it that way?
Shift-enter1500*1.25Alt-i ?
Like that, you keep the same shortcut and behavior everywhere, and you
don't have to answer questions such as:
Why typing :42enter doesn't work in a workspace?
Thierry
Le 25/03/2014 14:30, Sven Van Caekenberghe a écrit :
I
I had this idea:
https://pharo.fogbugz.com/f/cases/13128/Use-Spotlight-to-quickly-evaluate-and-inspect-short-expressions
now you can do
shift-Enter:42Enter
to inspect the magic number 42
shift-Enter:1500*1.25Enter
to quickly compute your 25% raise
shift-Enter:Float piEnter
to see how many
I share with you the impression that a workspace is overkill most of the times.
I have different feelings with this.
At one side I would preserve spotlight for searching ONLY. And have a
separate REPL/cmd prompt docked to some edge (like Autocad's Text
Window one).
On the other hand I'm a vim
AWESOME! (oops, overwhelming enthusiasm effect).
Alt-O Alt-W usage is going down in flames with this one.
Now, making the spotlight larger is the next step so that we can actually
read longer expressions.
And $: is just the beginning of prefixes I guess.
Phil
On Tue, Mar 25, 2014 at 2:30
On Mar 25, 2014, at 10:30 AM, Sven Van Caekenberghe s...@stfx.eu wrote:
Opening a workspace for a single expression often is overkill. This feature
is totally keyboard driven and very clean.
Sounds okay.
Need to test it for useful feedback.
What I like about workspaces is that they have
Opening a workspace and typing in it right away is Cmd-o Cmd-w / Alt-o Alt-w
So, the Shift-Enter : thing is faster for some things.
As a TWM user, well, tiling workspaces helps when trying to find back a
given window, but I do a lot of inspect/explore in the workspace, so this
comes in handy.
Hi Igor,
On Tue, Mar 25, 2014 at 5:05 AM, Igor Stasenko siguc...@gmail.com wrote:
On 24 March 2014 22:54, p...@highoctane.be p...@highoctane.be wrote:
On Mon, Mar 24, 2014 at 8:23 PM, Alexandre Bergel
alexandre.ber...@me.com wrote:
I am working on a memory model for expandable
On Mar 25, 2014, at 12:36 PM, p...@highoctane.be wrote:
Opening a workspace and typing in it right away is Cmd-o Cmd-w / Alt-o Alt-w
So, the Shift-Enter : thing is faster for some things
cmd-O? that would be cool but is not working on my Pharo3.0 Latest update:
#30798, which one are you
Pharo 3, Win8.1
Alt-O , keeping the finger on alt and then W
Workspace!
My Mac is in its bag at the moment :-)
On 25 March 2014 17:31, Eliot Miranda eliot.mira...@gmail.com wrote:
Hi Igor,
On Tue, Mar 25, 2014 at 5:05 AM, Igor Stasenko siguc...@gmail.com wrote:
On 24 March 2014 22:54, p...@highoctane.be p...@highoctane.be wrote:
On Mon, Mar 24, 2014 at 8:23 PM, Alexandre Bergel
Hi Igor,
you have a point but I disagree. The scheduler is defined in the
implementation section of the blue book. It could be more explicit, but the
blue book scheduler is a known and simple system. In my threading work I've
made sure to preserve its semantics (cooperative within
On Tue, Mar 25, 2014 at 10:21 AM, Eliot Miranda eliot.mira...@gmail.comwrote:
Hi Igor,
you have a point but I disagree. The scheduler is defined in the
implementation section of the blue book. It could be more explicit, but
the blue book scheduler is a known and simple system. In my
Just to show what i talking about..
Credits to Queen:
| str |
str := 'Don''t stop me now.'.
[ 2 seconds asDelay wait. str := str , '(oops , i did)' ] forkAt: Processor
highestPriority.
[ 4 seconds asDelay wait. str := str, 'I''m having such a good time
I''m having a ball'] valueUnpreemptively.
On 25 March 2014 18:21, Eliot Miranda eliot.mira...@gmail.com wrote:
Hi Igor,
you have a point but I disagree. The scheduler is defined in the
implementation section of the blue book. It could be more explicit, but
the blue book scheduler is a known and simple system. In my threading
When I see all the interactions and people helping I think that this was really
worth :)
Thanks for ESUG for sponsoring your trip (like that we can reinvite with RMOD
money).
Stef
On 24 Mar 2014, at 10:06, Max Leske maxle...@gmail.com wrote:
For those who’ve been interested in what went on
On 25.03.2014, at 19:43, Pharo4Stef pharo4s...@free.fr wrote:
When I see all the interactions and people helping I think that this was
really worth :)
Yes, me too.
Thanks for ESUG for sponsoring your trip (like that we can reinvite with RMOD
money).
Cool!
Stef
On 24 Mar 2014, at
2014-03-23 8:14 GMT+01:00 Johan Brichau jo...@inceptive.be:
I reflected a bit more on your requirements. How about the following?
Put a separate reference for the project in each platform-specific
section. I combine this with a #file: declaration because otherwise your
package cache will
38 matches
Mail list logo
