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

2014-12-08 Thread Andrei Chis
On Mon, Dec 8, 2014 at 8:02 PM, kilon alios wrote: > Dont know if this is auto completion replacement or not, from the looks of > it seem a lot more than that. Auto completion is one of the thing that > annoys me in Pharo and this looks like a very good replacement. > > So the gui is also made wi

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

2014-12-08 Thread kilon alios
Dont know if this is auto completion replacement or not, from the looks of it seem a lot more than that. Auto completion is one of the thing that annoys me in Pharo and this looks like a very good replacement. So the gui is also made with Glamour ? Look very good looking and very useful cant wait

Re: [Pharo-users] STON - new release?

2014-12-08 Thread Sven Van Caekenberghe
Hi Usman, Your are right, the configuration was running a bit behind - fixed: === Name: ConfigurationOfSton-SvenVanCaekenberghe.11 Author: SvenVanCaekenberghe Time: 8 December 2014, 11:39:39.045546 pm UUID: 06b682e1-4589-41db-9a63-56bde6aaf34d Ancestors: ConfigurationOfSton-SvenVanCaekenberghe.10

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

2014-12-08 Thread Tudor Girba
Thanks for the suggestions, Johan. I will change the text and we will definitely look into making the shortcuts more apparent. Cheers, Doru On Mon, Dec 8, 2014 at 5:17 PM, Johan Fabry wrote: > > OK now I get it … thanks for clarifying! > I think my confusion stems from the use of ‘category' and

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

2014-12-08 Thread Tudor Girba
Hi, Thanks. Indeed, I noticed that too. I added a mentioning of the shortcut at the beginning of the post. Cheers, Doru On Mon, Dec 8, 2014 at 11:34 PM, Edward Povazan wrote: > Hi, > > This is really great - one minor thing - I didn’t know how to launch the > search screen until I accidental

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

2014-12-08 Thread Edward Povazan
Hi, This is really great - one minor thing - I didn’t know how to launch the search screen until I accidentally hit cmd+enter (muscle memory from another IDE). Would be nice to explain cmd+enter to launch in the description page. Cheers, -Ed On Dec 7, 2014, at 5:14 AM, Tudor Girba wrote: >

Re: [Pharo-users] [ Article ] LampSort, a non-recursive QuickSort implementation

2014-12-08 Thread Tudor Girba
Very nice :) I really like these pieces of work. A couple more and you'll have a book ready :). Doru On Mon, Dec 8, 2014 at 8:17 PM, Sven Van Caekenberghe wrote: > > > On 08 Dec 2014, at 19:59, Alexandre Bergel > wrote: > > > > Well written and very dictactic. > > Thanks, that was the idea. >

Re: [Pharo-users] [ Article ] LampSort, a non-recursive QuickSort implementation

2014-12-08 Thread Sven Van Caekenberghe
> On 08 Dec 2014, at 19:59, Alexandre Bergel wrote: > > Well written and very dictactic. Thanks, that was the idea. > Do you have this text as a class comment in your class? Well, not completely, but there are links to the article in the class comment: https://github.com/svenvc/lampsort/tre

Re: [Pharo-users] [ Article ] LampSort, a non-recursive QuickSort implementation

2014-12-08 Thread Alexandre Bergel
Well written and very dictactic. Do you have this text as a class comment in your class? Cheers, Alexandre > Le 08-12-2014 à 15:36, Sven Van Caekenberghe a écrit : > > Hi, > > Here is another article I just published > > LampSort, a non-recursive QuickSort implementation > > The divide a

[Pharo-users] [ Article ] LampSort, a non-recursive QuickSort implementation

2014-12-08 Thread Sven Van Caekenberghe
Hi, Here is another article I just published LampSort, a non-recursive QuickSort implementation The divide and conquer partitioning is at the heart of QuickSort https://medium.com/@svenvc/lampsort-a-non-recursive-quicksort-implementation-4d4891b217bd Pharo makes it easy to implement thi

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Tommaso Dal Sasso
On 08/12/14 17:32, Sven Van Caekenberghe wrote: On 08 Dec 2014, at 17:12, Marcus Denker wrote: We should add this explanation to the tool itself… Marcus Yes, and maybe also show the actual stack trace and other info that will be sent in dialog so that the user can see precisely what

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Sven Van Caekenberghe
> On 08 Dec 2014, at 17:12, Marcus Denker wrote: > >> >> On 08 Dec 2014, at 16:34, Tommaso Dal Sasso >> wrote: >> >> >> On 08/12/14 14:47, Sven Van Caekenberghe wrote: >>> Hi Tommaso, >>> >>> I think this is a cool initiative, many environments have something >>> similar, so this is a wel

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

2014-12-08 Thread Johan Fabry
OK now I get it … thanks for clarifying! I think my confusion stems from the use of ‘category' and then talking about 'the collection object’, which made me think about collections and source code and protocols and packages and I got lost. I think that the sentence of the blog would be clearer

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Marcus Denker
> On 08 Dec 2014, at 16:34, Tommaso Dal Sasso > wrote: > > > On 08/12/14 14:47, Sven Van Caekenberghe wrote: >> Hi Tommaso, >> >> I think this is a cool initiative, many environments have something similar, >> so this is a welcome addition. >> >> However, you must be clearer about the secur

[Pharo-users] STON - new release?

2014-12-08 Thread Usman Bhatti
Hi Sven, I have used STON to serialize some of my objects and it is really simple and cool to work with STON. For my project, I loaded the stable version. When I tried to customize the names of my classes for serialization using stonName, I got errors of MetaClass DNU. I saw that you already fixed

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

2014-12-08 Thread Tudor Girba
Hi, Ok. Let's take it step by step and see if we cannot find a better way of explaining. Take a look at the first picture in the blog post. Entering GTSpo shows results both for Classes and for Packages. These "Classes" and "Packages" are what we call search categories, and they have associated a

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Tommaso Dal Sasso
On 08/12/14 14:47, Sven Van Caekenberghe wrote: Hi Tommaso, I think this is a cool initiative, many environments have something similar, so this is a welcome addition. However, you must be clearer about the security implications (and/or tell us how these concerns are dealt with in other plac

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

2014-12-08 Thread Johan Fabry
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? > On Dec 7, 2014, at 11:16, Tudor Girba

[Pharo-users] [ANN] RProjectConnector V1.0

2014-12-08 Thread Blondeau Vincent
Hello everyone, I am glad to announce the first version of the RProjectConnector, a binding between Pharo and R using NativeBoost. You can now call directly your R methods from Pharo: data := (1 to: 1000) collect: #yourself. res := (#acf asRFunctionWith: {data}) eval To use it, you should copy

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Sven Van Caekenberghe
Hi Tommaso, > On 08 Dec 2014, at 14:27, Tommaso Dal Sasso > wrote: > > Hello everybody, > > I am excited to announce that ShoreLine Reporter is now part of Pharo 4. > ShoreLine Reporter is a tool to detect and report errors in Pharo: whenever a > user encounters an exception, she can select t

Re: [Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Tudor Girba
This is really great news! Thanks a lot for doing that. I see this as the first step in a completely new direction for Pharo. Cheers, Doru On Mon, Dec 8, 2014 at 2:27 PM, Tommaso Dal Sasso < tommaso.dalsa...@gmail.com> wrote: > Hello everybody, > > I am excited to announce that ShoreLine Repo

[Pharo-users] ShoreLine Reporter is in Pharo 4

2014-12-08 Thread Tommaso Dal Sasso
Hello everybody, I am excited to announce that ShoreLine Reporter is now part of Pharo 4. ShoreLine Reporter is a tool to detect and report errors in Pharo: whenever a user encounters an exception, she can select the "Report" option from the Pre Debug Window and send a stack trace to the ShoreL

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

2014-12-08 Thread Tudor Girba
Hi Christophe, On Mon, Dec 8, 2014 at 10:43 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi Doru and all, > > Great work. All these tools are really moving the development experience a > step forward :) > I will try it ASAP. > At this time, I just wonder if it is possible to sea

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

2014-12-08 Thread Christophe Demarey
Hi Doru and all, Great work. All these tools are really moving the development experience a step forward :) I will try it ASAP. At this time, I just wonder if it is possible to search text in method sources. It is often useful. Another related thing I don't know how to do, is to refactor a set o

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

2014-12-08 Thread Tudor Girba
I am happy you found the problem. Please continue asking questions. Cheers, Doru On Mon, Dec 8, 2014 at 10:33 AM, Edward Povazan wrote: > I found the problem. I forgot a simple fact - with Smalltalk I have access > to all the code! Anyways, I discovered that I had somehow zapped > Moose/Hash

Re: [Pharo-users] Emergency evaluator and GTGenericStackDebugger

2014-12-08 Thread Edward Povazan
I found the problem. I forgot a simple fact - with Smalltalk I have access to all the code! Anyways, I discovered that I had somehow zapped Moose/HashTable (no idea how) and so in the layout code "HashTable new” was raising the exception, sending “new” to UndefinedObject. Makes sense to me now.