Re: [Pharo-dev] Cmd+click in Rubric

Thanks! Doru On Wed, Nov 12, 2014 at 4:47 PM, Andrei Chis wrote: > cmd+click and cmd+shitf+click now work in Rubric for methods, classes and > methods parameters. > > > Cheers, > Andrei > > On Wed, Nov 12, 2014 at 12:44 PM, Tudor Girba > wrote: > >> Great n

Re: [Pharo-dev] Spotlight2 for Pharo40

he new hotness is > developed? > > > > > > Tudor Girba-2 wrote > > Hi Mariano, > > > > We want to build a moldable search interface that allows one to find > > objects. It will likely be a combination between a spotlight an an > > inspector.

Re: [Pharo-dev] ValueHolder analysis

I agree as well. Doru On Fri, Nov 14, 2014 at 4:58 PM, Igor Stasenko wrote: > > > On 14 November 2014 16:25, Henrik Johansen > wrote: > >> >> > On 14 Nov 2014, at 12:01 , stepharo wrote: >> > >> > I checked a bit deeper >> > >> > >> > Nautilus is not implemented in Spec. But senders and imple

Re: [Pharo-dev] [ANN] NetGen - OSM Roassal Demo

Nice! Doru On Wed, Nov 19, 2014 at 10:40 PM, Onil Goubier wrote: > > Hi all, > > We are pleased to announce a wireless sensor network animation demo in > Pharo, Roassal and OpenStreetMap. > > https://github.com/OnilGoubier/Cirela > > The release contains 2 packages: > 1. Cirela-OSM Package cons

Re: [Pharo-dev] Link between PetitParser and Roassal and Glamour

It's not strange. You only get this dependency if you load the gui of petit parser. If you do not need the gui, you can load the core group. Doru -- www.tudorgirba.com "Every thing has its own flow" > On 20 Nov 2014, at 15:57, Noury Bouraqadi wrote: > > Load PetitParser (dev version) => Roas

Re: [Pharo-dev] About the Playground cache

Hi Nicolai, On Thu, Nov 20, 2014 at 10:04 PM, Nicolai Hess wrote: > > I thought the Playground cache holds all evaluated/used expressions. > It used to only remember the expressions after you pressed Go. But, then we noticed that this is not enough as sometimes you just do it. So, rather than d

Re: [Pharo-dev] Link between PetitParser and Roassal and Glamour

No problem :) Cheers, Doru On Thu, Nov 20, 2014 at 10:10 PM, Noury Bouraqadi wrote: > I see. thanks :-) > On 20 Nov 2014, at 16:15, Tudor Girba wrote: > > > It's not strange. You only get this dependency if you load the gui of > petit parser. If you do not need the gui

Re: [Pharo-dev] About the Playground cache

Hi, On Thu, Nov 20, 2014 at 11:56 PM, Nicolai Hess wrote: > 2014-11-20 22:14 GMT+01:00 Tudor Girba : > >> Hi Nicolai, >> >> On Thu, Nov 20, 2014 at 10:04 PM, Nicolai Hess >> wrote: >> >>> >>> I thought the Playground cache holds all eva

Re: [Pharo-dev] About the Playground cache

Thanks. Doru On Fri, Nov 21, 2014 at 10:54 AM, Nicolai Hess wrote: > 14513 > GTPlayground cache does not truncate the current cache file > > 14512 > GTPlayground duplicate the number of cache files on im

Re: [Pharo-dev] ConfigurationOfGlamour not connected to repository

Hi Stephan, Indeed, these are not needed. Those groups are not maintainable and make tool building a nightmare. We will remove them from all Moose configurations eventually :). Doru On Fri, Nov 21, 2014 at 1:41 PM, Stephan Eggermont wrote: > Hmm, there are also other configurations still loade

Re: [Pharo-dev] [ANN] SciSmalltalk v0.16

+1 Doru On Sat, Nov 22, 2014 at 3:57 PM, Alexandre Bergel wrote: > Yes! This is important! > > > > > > > Le 21-11-2014 à 8:51, stepharo a écrit : > > > > Super keep pushing! > > > > Stef > > Le 18/11/14 14:14, Serge Stinckwich a écrit : > >> Dear all, > >> > >> we are to happy to announce SciS

Re: [Pharo-dev] [ANN] OnScreenKeyboard

Nice job! Doru On Sat, Nov 22, 2014 at 8:55 PM, Pavel Krivanek wrote: > Hi, > > I created the first version of a virtual keyboard morph for Pharo. To > try it, evaluate: > > Gofer it > url: ' > http://www.smalltalkhub.com/mc/PavelKrivanek/OnScreenKeyboard/main'; > package: 'OnScreenKe

Re: [Pharo-dev] About RBCompiler

Indeed, this is really exciting work :). Keep it up. Cheers, Doru On Sun, Nov 23, 2014 at 11:49 PM, Jan Vrany wrote: > On Sun, 2014-11-23 at 10:13 +0100, Marcus Denker wrote: > > > On 22 Nov 2014, at 18:17, Serge Stinckwich > wrote: > > > > > > I'm trying to port QuasiQuote package from Lukas

Re: [Pharo-dev] editing the default window size of glamour inspector

Hi, Sorry for not replying earlier. Thanks Nicolai for picking this one up. I missed the initial mail. The initialExtent does not make sense for presentation, and anyway, you would not want to change an inspector when you are inside a flow. If I understand correctly, Clement would want that when

Re: [Pharo-dev] Listening for shift key pressed

Exciting :) Doru On Mon, Nov 24, 2014 at 2:19 PM, Ben Coman wrote: > Aliaksei Syrel wrote: > >> Hi Ben, >> >> Thanks :) >> >> Here I opened issue > cases/14521/Pressing-shift-ctrl-command-options-capslock- >> doesn-t-trigger-corresponding-Event-on-Mac> >> >> I did

Re: [Pharo-dev] changing MC repository url display

It will certainly help. Ideally, we should have this string displaying method in the MCRepository hierarchy. Cheers, Doru On Mon, Nov 24, 2014 at 3:12 PM, Esteban Lorenzano wrote: > yes you are right, but also you are digressing :) > my question is simple: do you think this small change can he

Re: [Pharo-dev] What is the limit

I think this discussion answers the wrong question. The question should not be if something is large or small compared with the size of the disc. The question should be: is it larger than it has to be for what it does? It is precisely this question that will keep Pharo slim. Nowadays, the greates

Re: [Pharo-dev] editing the default window size of glamour inspector

Hi, Ok. Can you open a ticket about finding a solution for custom Inspector window size? Doru On Mon, Nov 24, 2014 at 3:54 PM, Clément Bera wrote: > > > 2014-11-24 13:11 GMT+01:00 Tudor Girba : > >> Hi, >> >> Sorry for not replying earlier. Thanks Nicolai for pi

[Pharo-dev] class variable slots?

Hi, As far as I see, the class variables are not slots. Is that correct? If not, how do I get the slots? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Re: [Pharo-dev] class variable slots?

, Doru On Wed, Nov 26, 2014 at 9:10 PM, Marcus Denker wrote: > > On 26 Nov 2014, at 19:36, Eliot Miranda wrote: > > Hi Tudor, > > On Wed, Nov 26, 2014 at 6:02 AM, Tudor Girba wrote: > >> Hi, >> >> As far as I see, the class variables are not slots. Is that

Re: [Pharo-dev] class variable slots?

Hi Eliot, Thanks. I know what class variables are, I was just asking if there is a Slot-like meta-object in the implementation :). Cheers, Doru On Wed, Nov 26, 2014 at 7:36 PM, Eliot Miranda wrote: > Hi Tudor, > > On Wed, Nov 26, 2014 at 6:02 AM, Tudor Girba wrote: > >> H

Re: [Pharo-dev] editing the default window size of glamour inspector

Thanks. Doru On Fri, Nov 28, 2014 at 9:59 AM, Clément Bera wrote: > > > 2014-11-25 8:35 GMT+01:00 Tudor Girba : > >> Hi, >> >> Ok. Can you open a ticket about finding a solution for custom Inspector >> window size? >> > > Done: > > > ht

Re: [Pharo-dev] New Cog VMs available

+1 Doru On Sun, Nov 30, 2014 at 8:57 PM, stepharo wrote: > No problem! Thanks for creating this great asset! > > Stef > > > > On Fri, Nov 21, 2014 at 4:08 PM, Eliot Miranda > wrote: > >> ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3144. >> >> Apologies; the 3143 VMs were broken. >> >

Re: [Pharo-dev] SmalltalkHub bugs & hangs :-(

+1 Doru On Mon, Dec 1, 2014 at 11:19 AM, Hilaire wrote: > Hello, > > From my experience point of view with SmalltlakHub, I found this tool > remarkably stable, useful, feature complete and quite well integrated > with Monticello. > I want to say thank you guys for the energy you spend to keep i

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

On Mon, Dec 1, 2014 at 7:00 AM, 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 bee

Re: [Pharo-dev] [Moose-dev] Woden-GT integration

There is a GT-InspectorExtensions-Woden package in the GT repository. Doru On Mon, Dec 1, 2014 at 3:39 PM, Ronie Salgado wrote: > And I have to fix a bug that chrashes it. (opening a view twice) > > 2014-12-01 11:35 GMT-03:00 Alexandre Bergel : > > If I remember correctly, Doru told me he worke

Re: [Pharo-dev] Woden processor occupation and text highlight

I think it is fine to keep the discussions either on the Pharo or on the Moose mailing list :). Doru On Mon, Dec 1, 2014 at 3:39 PM, Yuriy Tymchuk wrote: > Hi, > > first of all let me know where I can write questions about Woden (because > I have not seen a lot of activity around it in any chat

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

On Mon, Dec 1, 2014 at 5:51 PM, Ben Coman wrote: > seas...@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 di

Re: [Pharo-dev] [To be merged] GT-InspectorExtensions-Core-SvenVanCaekenberghe.77

Where do I find this one? Doru On Mon, Dec 1, 2014 at 10:04 PM, Sven Van Caekenberghe wrote: > In Moose/GToolkit: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.77 > Author: SvenVanCaekenberghe > Time: 1 December 2014, 9:56:58.104994 pm > UUID: 3da8544f-909e-49c6-88a5-f944a5f13

Re: [Pharo-dev] [To be merged] GT-InspectorExtensions-Core-SvenVanCaekenberghe.77

Ugh. Sorry, I missed it. It's merged now. Cheers, Doru On Mon, Dec 1, 2014 at 11:28 PM, Sven Van Caekenberghe wrote: > http://www.smalltalkhub.com/#!/~Moose/GToolkit > > > On 01 Dec 2014, at 23:18, Tudor Girba wrote: > > > > Where do I find this one? > > &

Re: [Pharo-dev] default fonts changed in Pharo 4.0

Great! Doru p.s. Finally :) On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano wrote: > Hi, > > We changed the default fonts in Pharo for the ones that are used normally > in Moose. > They are: Source Sans Pro and Source Code Pro. > We needed to do it for several reasons: > > 1) TxText (the ne

Re: [Pharo-dev] default fonts changed in Pharo 4.0

former in my 3.0 image, and I like it a bit more, it seems > a bit wider. > > > On 02 Dec 2014, at 11:27, Tudor Girba wrote: > > > > Great! > > > > Doru > > > > p.s. Finally :) > > > > > > On Tue, Dec 2, 2014 at 9:48 AM, Esteban Loren

Re: [Pharo-dev] default fonts changed in Pharo 4.0

2014, at 12:47, Sven Van Caekenberghe wrote: > > > On 02 Dec 2014, at 12:12, Esteban Lorenzano wrote: > > > On 02 Dec 2014, at 12:02, Sven Van Caekenberghe wrote: > > > On 02 Dec 2014, at 11:46, Tudor Girba wrote: > > There is no Source Code Sans :). There is on

Re: [Pharo-dev] class variable slots?

Exactly! This is what I was looking for :) Thanks, Doru On Wed, Dec 3, 2014 at 9:35 AM, Marcus Denker wrote: > > > One we did for Pharo4 is to use the Associations of Globals to model these > variables as meta-objects (in the same spirit as the Slot objects). > > Thos means that > -> there is a

Re: [Pharo-dev] class variable slots?

What do you mean? Doru On Wed, Dec 3, 2014 at 2:33 PM, Ben Coman wrote: > Marcus Denker wrote: > >> >> >> On Wed, Dec 3, 2014 at 1:32 PM, Tudor Girba > <mailto:tu...@tudorgirba.com>> wrote: >> >> Exactly! This is what I was looking for :)

Re: [Pharo-dev] GTPlayground cache

Why not? Was there a change in the Pharo image? (I do not have access to the code right now) Doru On Thu, Dec 4, 2014 at 8:57 AM, Nicolai Hess wrote: > Since 40393 the play-cache is not read when you open the first > GTPlayground in a fresh image. > > > -- www.tudorgirba.com "Every thing ha

Re: [Pharo-dev] How to tell Pharo 3.0 from 4.0

Go to the World menu / System / About Cheers, Doru On Thu, Dec 4, 2014 at 10:22 AM, Jan Vrany wrote: > Hi, > > how do I tell from within a running image whether > I'm running on Pharo 3.0 or 4.0 image? Thanks! > > Jan > > > -- www.tudorgirba.com "Every thing has its own flow"

Re: [Pharo-dev] GTInspector and huge arrays issue

Hi Kilon, We started to explore a new list implementation that is more scalable and whose goal is to support smooth scrolling, but it will take a while. Until then, you can still increase the paging size (the 50 is editable). Cheers, Doru On Thu, Dec 4, 2014 at 12:15 PM, kilon alios wrote: >

Re: [Pharo-dev] GTInspector and huge arrays issue

Hi, I think Kilon refers to the search in the Items presentation of a collection. If so, that search field accepts a Pharo expression of the form: each isMatchingSomething In that case, this will translate in self select: [:each | each isMatchingSomething] If you hover with the mouse over

Re: [Pharo-dev] GTInspector and huge arrays issue

In that presentation, yes. Doru On Thu, Dec 4, 2014 at 1:09 PM, kilon alios wrote: > "In that case, this will translate in >self select: [:each | each isMatchingSomething]" > > ah ok, I see, so it does not search based on a string but based on > expression. > -- www.tudorgirba.com "Eve

Re: [Pharo-dev] GTInspector and huge arrays issue

Hi, We are working on the edit values. Could you open a ticket in the meantime to not forget about it? As for auto refresh, we will probably have to wait until we get the ability to listen to an individual object. Doru On Thu, Dec 4, 2014 at 11:56 AM, Sven Van Caekenberghe wrote: > > > On 04

Re: [Pharo-dev] GTPlayground cache

ot the > contents written into play-cache from the prior used images. > > nicolai > > 2014-12-04 9:45 GMT+01:00 Tudor Girba : > >> Why not? Was there a change in the Pharo image? (I do not have access to >> the code right now) >> >> Doru >> >> On T

Re: [Pharo-dev] Pharo+Git cons?

Hi, I think that most browsers produced in Samlltalk look remarkably similar to the original one which was developed 30 years ago [1], even though it clearly isn't the best possible solution. I would like to get to one that does not necessarily resemble the current one, and in the process uncover

Re: [Pharo-dev] [ANN] Transition of Ubuntu PPA maintenance

Thanks, Markus. This is great to hear. Cheers, Doru On Thu, Dec 4, 2014 at 9:46 PM, Markus Fritsche wrote: > Hello, > > The maintenance of the Ubuntu Pharo VM and .source Packages is being > transferred from Damien Cassou to myself, Markus Fritsche. By trade, I > am a Business Intelligence con

Re: [Pharo-dev] GTPlayground cache

Done. It will be available in the next GT release. Doru On Thu, Dec 4, 2014 at 4:02 PM, Marcus Denker wrote: > > On 04 Dec 2014, at 15:46, Marcus Denker wrote: > > > On 04 Dec 2014, at 15:42, Tudor Girba wrote: > > Aha. So, that's a bug, right? > > > I th

Re: [Pharo-dev] [Pharo-users] Twittering Smalltalk

+1. Doru On Fri, Dec 5, 2014 at 4:00 PM, Thushar G R wrote: > Thank you. > > Made my day. > thushar > > On Fri, Dec 5, 2014 at 1:57 AM, Mariano Martinez Peck < > marianop...@gmail.com> wrote: > >> Very nice indeed to read that. >> >> On Thu, Dec 4, 2014 at 5:15 PM, Sven Van Caekenberghe >> wro

Re: [Pharo-dev] Glamour-core maybe missing from Pharo40/main

I agree. Doru On Sat, Dec 6, 2014 at 12:34 PM, Marcus Denker wrote: > > On 06 Dec 2014, at 12:21, Marcus Denker wrote: > > > On 06 Dec 2014, at 12:10, Yuriy Tymchuk wrote: > > > On 05 Dec 2014, at 15:30, stepharo wrote: > > > Le 3/12/14 10:08, Marcus Denker a écrit : > > Yes, seemingly we lo

Re: [Pharo-dev] [Esug-list] [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects

rrowUp/ArrowDown = Next/Prev category, Cmd+RightArrow = Dive > into, Cmd+Shift+RightArrow = ??? > > > On Dec 7, 2014, at 10:14, Tudor Girba wrote: > > > > Hi, > > > > Alex Syrel, Andrei Chis and I are happy to announce a new addition to > the Glamorous Toolkit: >

Re: [Pharo-dev] [Esug-list] [ann] gtspotter: a moldable interface for spotting objects

ly inside the > implementor of y. > and of course I wanted to refactored them. And the default message browser > is not parametrized via an environment :_ > Exactly. This problem exists in any IDE I know. Doru > Stef > > On 07 Dec 2014, at 05:14, Tudor Girba wrote: > &

Re: [Pharo-dev] [Esug-list] [ann] gtspotter: a moldable interface for spotting objects

:05 PM, stephane ducasse wrote: > > On 07 Dec 2014, at 06:56, Tudor Girba wrote: > > Thanks, Stef. > > On Sun, Dec 7, 2014 at 2:35 PM, stephane ducasse < > stephane.duca...@gmail.com> wrote: > >> Truly excellent! >> I have to try :) >> I rea

Re: [Pharo-dev] [Esug-list] [ann] gtspotter: a moldable interface for spotting objects

:) I know how this feels. On the other hand, with this one we target 15 minutes (= the coffee break) :) Doru On Sun, Dec 7, 2014 at 4:20 PM, stephane ducasse wrote: > > Hi, > > This is indeed a significant challenge. Until that point we need a couple > of more features, of which the most impor

Re: [Pharo-dev] [Moose-dev] [ann] gtspotter: a moldable interface for spotting objects

Caekenberghe wrote: > > > On 07 Dec 2014, at 14:14, Tudor Girba wrote: > > > > Alex Syrel, Andrei Chis and I are happy to announce a new addition to > the Glamorous Toolkit: > > GTSpotter, a novel interface for spotting objects. > > Excellent work, all around

Re: [Pharo-dev] [Moose-dev] [ann] gtspotter: a moldable interface for spotting objects

#x27;some string' ? > Globals like the Transcript ? > Singletons accessible by class side accessors, like announcers ? > An evaluation functionality, just type an expression ? > Examples ? > The clipboard (contents), open windows, processes, ... > > Anyway, I am sure you get the

[Pharo-dev] playground vs workspace

Hi, As you might see, the GTPlayground is called playground not workspace. The main reason for this is that workspace implies the place where work is done, and work is typically associated with creating code. This is not the intention of the workspace. Workspace also comes with a history that is

Re: [Pharo-dev] playground vs workspace

e typical commands for >> you to use". >> >> Removing this ability and having a large thing popping at the right is >> really disturbing for these use cases. >> >> Phil >> >> >> >> On Mon, Dec 8, 2014 at 7:18 AM, Tudor Girba wrote: &

Re: [Pharo-dev] [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects

I think this is out of the direct realm of GTSpotter. But, it would be an interesting area nevertheless. We would likely be able to benefit from combining somehow RB rules with spotter. Cheers, Doru > Christophe. > > Le 7 déc. 2014 à 14:14, Tudor Girba a écrit : > > Hi, >

Re: [Pharo-dev] playground vs workspace

Hi Kilon, Please, let's get positive :). I really do not see how your remarks apply to the current situation. We put quite some effort in documenting GT tools through posts on the humane assessment blog (in the meantime, the page should be more reliable - I hope) and through examples in the image

Re: [Pharo-dev] playground vs workspace

Hi, This was a long mail :). I tried to address your points below. On Mon, Dec 8, 2014 at 10:55 AM, Torsten Bergmann wrote: > I would go the opposite direction and rename the "Playground" window to > "Workspace". > > Several reasons: > >1. "Playground" reminds me too much on toyish things

Re: [Pharo-dev] playground vs workspace

Exactly! This is precisely the way we should look at tools: we should identify why we need that tool, but not necessarily stick with the tool. For example, people said a while ago that the Workspace is better than the Playground for searching for things like implementors. While that might have be

Re: [Pharo-dev] playground vs workspace

you are using GTPlayground very extensively: > Do YOU use the Workspace at all ? > Do YOU miss something in GTPlayground, where you would say: "Yes, only a > workspace should do this". > > > Nicolai > > > 2014-12-08 7:18 GMT+01:00 Tudor Girba : > >> Hi, >

Re: [Pharo-dev] playground vs workspace

Hi Sven, Thanks for the kind words. Doru On Mon, Dec 8, 2014 at 2:33 PM, Sven Van Caekenberghe wrote: > More documentation is always better, but you can hardly accuse Doru from > trying, he is making an excellent effort in explaining what he does and > why, this is a lot of work, and I appreci

Re: [Pharo-dev] [Esug-list] [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects

rote: > Sorry, but no :-( > > I am always confused when people say ‘category’ because the word has so > many overloaded meanings. The same happens in the blog post, it is not > clear to me what category means here, and what does it have to do with the > collection object? > >

Re: [Pharo-dev] Applying GTSpotter to domain objects, an experiment

Great! Thanks a lot for doing this. At this moment, you cannot add more than one action. It's hardcoded, but we want to extend that part as well. We just did not get to do it yet. Cheers, Doru On Mon, Dec 8, 2014 at 5:19 PM, Stephan Eggermont wrote: > GTSpotter looks like a nice way to buil

Re: [Pharo-dev] playground vs workspace

Hi, On Mon, Dec 8, 2014 at 4:51 PM, Torsten Bergmann wrote: > >And Playground would match so well the marketing term of "playing with > live objects". > > Sorry - but to me it looks like you were catched too much into: now we > have to be more modern > or rival with all this "lively" stuff (Ligh

Re: [Pharo-dev] playground vs workspace

uld keep > it innovative and breaking with its legacy. Playground for all! No more > workspaces! And yeah, we will have to write new book about that. We are > already working on this! > > Cheers, > Alexandre > > > > On Dec 8, 2014, at 3:18 AM, Tudor Girba wrote: > >

Re: [Pharo-dev] playground vs workspace

he history of Smalltalk. It cares about how we can solve their problem. That's all. Cheers, Doru On Mon, Dec 8, 2014 at 8:21 PM, Andreas Wacknitz wrote: > > > Am 08.12.2014 um 07:18 schrieb Tudor Girba : > > > > Hi, > > > > As you might see, the GTPlaygroun

Re: [Pharo-dev] playground vs workspace

Hi, We do not yet have an IDE (where I stands for integrated). We have a set of tools and some of them are quite strong. But, we do not have an overall experience yet. Yes, the underlying language model does offer a beautiful experience, but the experience of the tools is far from that. We need t

Re: [Pharo-dev] playground vs workspace

splay a sub-menu with both > implementations. And community gains a place to display/register more > implementations discriminated by its type. > > Hernán > > > > > > > 2014-12-08 3:18 GMT-03:00 Tudor Girba : > > Hi, >> >> As you might see, th

Re: [Pharo-dev] [Esug-list] [Pharo-users] [ann] gtspotter: a moldable interface for spotting objects

results list > would be: > Cmd+Shift+ArrowUp/ArrowDown = Next/Prev category, Cmd+RightArrow = Dive > into Result, Cmd+Shift+RightArrow = Dive into Category > > > On Dec 8, 2014, at 12:48, Tudor Girba wrote: > > > > Hi, > > > > Ok. Let's take it step by st

Re: [Pharo-dev] [pharo-project/pharo-core] 673fff: 40409

Interesting :) Doru On Wed, Dec 10, 2014 at 11:12 AM, GitHub wrote: > Branch: refs/heads/4.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 673fff3f082913ebffedc2b6491a0dde6e731f3f > > https://github.com/pharo-project/pharo-core/commit/673fff3f082913ebffedc2b6491a0dde6e73

Re: [Pharo-dev] Find message name /implementors in Spotter

Yes. I was too lazy. It's committed now. Thanks, Doru On Wed, Dec 10, 2014 at 4:39 PM, Nicolai Hess wrote: > Currently, spotter finds only messages with the exact name. > for example: > addStep > finds no implementors althought the method > addStep: > > exists. > > > > suggestion for spotterImp

Re: [Pharo-dev] Is GTSpotter theme-aware ?

It is. Read my mail :). Doru On Wed, Dec 10, 2014 at 4:59 PM, Esteban Lorenzano wrote: > it doesn’t need to be made for every theme around, just “theme aware”, > which means do not use hardcoded values but the ones defined in the themes. > > Esteban > > On 10 Dec 2014, at 16:47, Aliaksei Syrel

Re: [Pharo-dev] About launching tools with Spotter

Hi, Actually, the thing is that I would search for 'o b' as a shortcut :). For the system browser I search for 'm b'. But, indeed, it seems that people prefer to have the applications on top and the rest of the things below. So, a quick fix for this problem is to make the Menu category come befor

Re: [Pharo-dev] Spotter feedback

Indeed. As Alex is saying, we are missing a couple of things, but this particular issue is the first on our to do list :) Doru On Wed, Dec 10, 2014 at 4:27 PM, Aliaksei Syrel wrote: > Hi Stef, > > It's not a bug it's a "feature" :) > Actually history is not fully implemented - nice presentation

Re: [Pharo-dev] Spotter feedback

Hi Kilon, I am happy you like it. Indeed, we also see it as having lots of potential for usage in all sorts of places. Cheers, Doru On Wed, Dec 10, 2014 at 4:36 PM, kilon alios wrote: > This tool is too awesome cant thank you enough guys. I was looking into > implementing something like this

Re: [Pharo-dev] About launching tools with Spotter

Hi, First, I am happy already that different people see GTSpotter as suitable for different things: some want to search for tools more, some want to search for code, and I am hoping others want to search for something else. This is great because it shows that GTSpotter can be quite versatile. We

Re: [Pharo-dev] GTInspector and huge arrays issue

Because we wanted to be both fast and flexible. Doru On Thu, Dec 11, 2014 at 12:03 PM, kilon alios wrote: > curious how come you guys did not use Spec ? > > On Thu, Dec 11, 2014 at 12:12 AM, Aliaksei Syrel > wrote: > >> Hi, >> >> Why the class you use is not available in Moose 5.0 ? >> >> Ther

Re: [Pharo-dev] Spotter searching for do:separatedBy:

Also, the latest package version of GT-SpotterExtensions-Core includes an implementors logic that will offer first the methods that start with the query string. So, do:something... will have precedence over somethingDo:. Doru On Thu, Dec 11, 2014 at 11:12 AM, Sven Van Caekenberghe wrote: > hmm,

Re: [Pharo-dev] spotter and exact matches

It should be improved in the latest GT-InspectorSpotter-Core. Please give it a try and see if it works for you. We will still have to improve this part. Doru On Wed, Dec 10, 2014 at 11:46 PM, Norbert Hartl wrote: > Is it possible to show exact matches in spotter first? Typing something > like

[Pharo-dev] how do you use scripts?

Hi, As input for designing new features that better support scripting in Pharo, we would benefit from a bit more input around the role scripts play in your development life. To this end, I would like to invite you to share your scripting experience. Here are some questions to start from, but feel

Re: [Pharo-dev] Spec TabManager clipping issues

+1 Doru On Tue, Dec 16, 2014 at 7:25 AM, Sven Van Caekenberghe wrote: > > Thanks (again) ! > > It is really remarkable how fast you can solve all these very diverse bugs. > > > On 16 Dec 2014, at 00:18, Nicolai Hess wrote: > > > > 2014-12-15 21:19 GMT+01:00 stepharo : > > Probably hard coded le

Re: [Pharo-dev] spotter on global vars

Spotter is certainly meant to search whatever you want, so it's hard to over use it :) I added you to the Moose team. Please commit your changes there. Doru On Fri, Dec 19, 2014 at 11:11 AM, Nicolai Hess wrote: > > I hope I don't overuse spotter. > > 14641

Re: [Pharo-dev] spotter on global vars

That one only exists in Pharo 4. Doru On Fri, Dec 19, 2014 at 11:59 AM, Nicolai Hess wrote: > > 2014-12-19 11:28 GMT+01:00 Marcus Denker : >> >> Do you need GTSpottedGlobalVars as a wrapper or could this not be part of >> #GlobalVariable? >> >> (and LiteralVariable in general should have support

Re: [Pharo-dev] GSpotter fonts of evaluation results

Good point. That is a theme issue but it should be fixed. Doru On Fri, Dec 19, 2014 at 9:46 AM, stepharo wrote: > The fonts used by GSpotter to display results does not change when > changing size and > this should be fixed for demo for example. > > Stef > > -- www.tudorgirba.com "Every thi

Re: [Pharo-dev] [Pharo-users] Do not forget to register to Pharo days...

Indeed. Please do not postpone the registration. And feel free to make noise :). Cheers, Doru On Mon, Dec 22, 2014 at 10:59 PM, stepharo wrote: > http://pharodays2015.pharo.org > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

Re: [Pharo-dev] Old inspector and explorer

Hi, What does a basic inspector mean for you? It's not a rhetorical question. I am actually interested in what you miss. Doru On Tue, Dec 23, 2014 at 6:06 PM, Clément Bera wrote: > Yes. > > World Menu >> Settings >> Glamourous toolkit > > then you can uncheck GTInspector and GTPlayground. > >

Re: [Pharo-dev] Old inspector and explorer

On Tue, Dec 23, 2014 at 7:37 PM, Sven Van Caekenberghe wrote: > > > On 23 Dec 2014, at 19:13, Tudor Girba wrote: > > > > Hi, > > > > What does a basic inspector mean for you? It's not a rhetorical > question. I am actually interested in what you mis

Re: [Pharo-dev] Old inspector and explorer

-variables-shown-in-gtinspector/ If not, then could you advise me as to how to get the internal state independent of the layout? Cheers, Doru On Tue, Dec 23, 2014 at 8:09 PM, Clément Bera wrote: > > > 2014-12-23 19:37 GMT+01:00 Sven Van Caekenberghe : > >> >> > On 2

Re: [Pharo-dev] Old inspector and explorer

The Raw view is a tree :) Doru On Tue, Dec 23, 2014 at 10:44 PM, Ben Coman wrote: > Sven Van Caekenberghe wrote: > >> On 23 Dec 2014, at 19:13, Tudor Girba wrote: >>> >>> Hi, >>> >>> What does a basic inspector mean for you? It's not a rhet

[Pharo-dev] [ann] moose 5.0

We are happy to announce Moose 5.0: *http://moosetechnology.org/#install* Description --- This is by far the most extensive Moose release to date. Just take a look at these two trailers. - Spotter: https://vimeo.com/113832673 - Inspector: https://vimeo.com/103463364 The key highlights are: - It

Re: [Pharo-dev] [Pharo-users] [ann] moose 5.0

BTW: Happy Holidays to all. > > Giorgio > > On Wed, Dec 24, 2014 at 12:09 AM, Tudor Girba > wrote: > >> We are happy to announce Moose 5.0: >> *http://moosetechnology.org/#install* >> >> >> Description >> --- >> >> This is by far the mo

Re: [Pharo-dev] Old inspector and explorer

g. Keep in mind that having it depend on the selection was a solution for the interface that provided only one playground per inspector, but now as you get one per pane/object we do not have that restriction. Cheers, Doru On Wed, Dec 24, 2014 at 12:17 AM, Nicolai Hess wrote: > 2014-12-2

Re: [Pharo-dev] Old inspector and explorer

Hi, I think there must be a misunderstanding. There can be a good reason for having a basic inspector around, but I think the reason is not because people cannot choose what to use. There is a toggle to enable/disable the GTInspector. But, even without it, the main feature of the GTInspector is

Re: [Pharo-dev] [Ann] a short Bloc demo

Very nice work! Thanks for pushing this. I think you will not be alone in working on Bloc for long :) Doru On Wed, Dec 24, 2014 at 3:41 PM, Alexandre Bergel wrote: > Wow! Impressive!!! > > Alexandre > > > > On Dec 24, 2014, at 3:19 PM, Alain Plantec > wrote: > > > > Hello all, > > > > I’ve ju

Re: [Pharo-dev] Old inspector and explorer

k the only possibility is to "offer" a new way of doing things > and give people time to adjust. > > Norbert > > Am 26.12.2014 um 13:18 schrieb Tudor Girba : > > Hi, > > I think there must be a misunderstanding. > > There can be a good reason for having a bas

Re: [Pharo-dev] Old inspector and explorer

Hi Norbert, My reply is inlined. On Wed, Dec 24, 2014 at 5:15 PM, Norbert Hartl wrote: > > Am 23.12.2014 um 22:46 schrieb Tudor Girba : > > The Raw view is a tree :) > > It looks like shallow tree :) Maybe I miss the point but my appearance to > this is something like tha

Re: [Pharo-dev] Old inspector and explorer

t > everyone should give the new tools a fair chance. > > And I fully agree with the 'emergency inspector' idea. > > > On 26 Dec 2014, at 13:18, Tudor Girba wrote: > > > > Hi, > > > > I think there must be a misunderstanding. > > > > T

Re: [Pharo-dev] Old inspector and explorer

her problems are forced upon us we get easily distracted and >> frustrated. The same goes for new tools. If I'm forced to use these it just >> means I have to deal with it first and only then I'm allowed to deal with >> my own problem. As it was in that spe

Re: [Pharo-dev] Old inspector and explorer

Hi Norbert, Great. Please play with the extension and let us know how it goes. Cheers, Doru On Fri, Dec 26, 2014 at 3:31 PM, Norbert Hartl wrote: > Doru, > > Am 26.12.2014 um 14:38 schrieb Tudor Girba : > > Hi Norbert, > > My reply is inlined. > > dito > >

Re: [Pharo-dev] Old inspector and explorer

5:30 PM, Ben Coman wrote: > > > On Fri, Dec 26, 2014 at 8:18 PM, Tudor Girba wrote: > >> >> What I cannot quite grasp is that while we pride ourselves with working >> on a reflective language, when we have reflective tools, we seem to not be >> able to take

<    1   2   3   4   5   6   7   8   9   10   >