Re: [Pharo-users] Pillar parser rewrite: PetitParser or not?

2015-03-11 Thread Norbert Hartl

> Am 11.03.2015 um 23:03 schrieb Damien Cassou :
> 
> Hi,
> 
> The current pillar parser has several problems:
> 
> - it is hard to understand and change
> - it discards input locations
> 
> I think a refactor or rewrite is necessary. What are the pros and cons of 
> using PetitParser to do that? 
> 
The cons are that petit parser is a heavier component and we should never 
underestimate that (just a reaction to a notion on this list). So we should 
avoid making things more complex, especially dependency wise.
The pros is that petit parser will make it easier to extend and maintain the 
pillar parser. I've read something about a new version of petit parser that has 
a speedup of aprox. 1.000.000x. If that is the case then it is no downgrade 
speed wise :) Another pro is IMHO that are some people that would like to move 
petit parser closer (not too close) to the core. That again would make it a 
more standard component that makes it easy to write parsers for everyone. A 
good companion if you have regex and you exceed to possibilities it provides.

I really have a bad feeling while saying: It would be good to have pillar based 
on petit parser.

Norbert






Re: [Pharo-users] Pillar parser rewrite: PetitParser or not?

2015-03-11 Thread Tudor Girba
I completely agree.

I think there are mostly pros. It can be that the parsing will be slower,
but I do not think this is a critical issue for Pillar. It would be more
important to have an extensible parser.

Cheers,
Doru



On Wed, Mar 11, 2015 at 11:03 PM, Damien Cassou 
wrote:

> Hi,
>
> The current pillar parser has several problems:
>
> - it is hard to understand and change
> - it discards input locations
>
> I think a refactor or rewrite is necessary. What are the pros and cons of
> using PetitParser to do that?
>
> Best




-- 
www.tudorgirba.com

"Every thing has its own flow"


[Pharo-users] [ANN] TODO List of Requested Features

2015-03-11 Thread Damien Cassou
I've just written a list of nice features we miss in Pillar:

http://www.smalltalkhub.com/#!/~Pier/Pillar

Please contribute by either making the list longer or, and I would prefer that, 
making it shorter. 

[Pharo-users] Pillar parser rewrite: PetitParser or not?

2015-03-11 Thread Damien Cassou
Hi,

The current pillar parser has several problems:

- it is hard to understand and change
- it discards input locations

I think a refactor or rewrite is necessary. What are the pros and cons of using 
PetitParser to do that? 

Best

[Pharo-users] using spotter to navigate through the file system

2015-03-11 Thread Tudor Girba
Hi,

Here is a little post that describes how you can use GTSpotter to navigate
through the file system:
http://www.humane-assessment.com/blog/searching-file-system-with-gtspotter/

If you combine this with the GTInspector ability of allowing you interact
with the file references, you get a pretty powerful tool:
http://www.humane-assessment.com/blog/browsing-files-with-gtinspector/

This is probably the simplest 3-minute demo you can give to a newcomer :).

Cheers,
Doru

-- 
www.tudorgirba.com

"Every thing has its own flow"


Re: [Pharo-users] GTTools and Mongo

2015-03-11 Thread Tudor Girba
Hi,

On Wed, Mar 11, 2015 at 7:41 PM, Torsten Bergmann  wrote:

> Ben wrote:
> >A blog article on that would be cool :)
>
> This was already in the pipe:
> https://medium.com/@astares/building-a-mongo-browser-in-pharo-fe2104052843
> but dont tell anyone otherwise our community will be even cooler ;)


Beautiful :)


>
> Tudor wrote:
> >And I see you used yet another undocumented feature: filtering the
> >inspector :)
>
> Sorry for making this more documented ;)
>

:). Looking at it, I see you already are using the icons inspection as
well. Man, nothing escapes you :)



> Thanks to Sven - his articles are inspiring!
>

Indeed.

Cheers,
Doru




> Bye
> T.
>



-- 
www.tudorgirba.com

"Every thing has its own flow"


[Pharo-users] Jenkins build trigger

2015-03-11 Thread Christophe Demarey

Thanks to Esteban add-on on Smalltalkhub, it is now possible to notify Jenkins 
that there is a new package published for your project.
What we do for now is to poll very often (each minute) smalltalkub to check if 
there is an update. It is a big waste of resources!
Now we can do better! It would be very nice to update your jobs to now use the 
commit hook.

Here is the way to go:
go to your job configuration on Jenkins
In the build triggers section, 
enable Trigger builds remotely (e.g., from scripts) and choose an 
authentication token. 
disable [URLTrigger] - Poll with a URL
go to smalltalkhub, on your project settings page
Fill in the commit hook url field with 
https://ci.inria.fr/pharo-contribution/buildByToken/build?job=JOBNAME&token=TOKEN
 by replacing JOBNAME and TOKEN by the Jenkins job name and the token chosen.

In the end, the build is now triggered immediately after the commit (no more 
delay).

Christophe

smime.p7s
Description: S/MIME cryptographic signature


Re: [Pharo-users] GTTools and Mongo

2015-03-11 Thread Tudor Girba
Hi Phil,

The extensions should without problems on the stable version of GTInspector
for Pharo 3.

Cheers,
Doru


On Wed, Mar 11, 2015 at 8:48 AM, p...@highoctane.be 
wrote:

> And now for 2 images...
>
> Pharo 4 for tools like this.
> Pharo 3 for production code...
>
> Any way to get this on 3 you think?
> MongoTalk works fine there.
>
> Am switching betweeen Pharo and Robomongo all the time here :-)
>
> FWIW Mapless and its mongo support is quite awesome. I am using it for a
> feature and it has tremendous potential.
>
> Your tool will be a great inspiration for builing one for it.
>
> Phil
>
>
>
> Le 11 mars 2015 07:49, "Tudor Girba"  a écrit :
>
> He he.
>>
>> When the cost of building a tool gets too low, developers feel compelled
>> to work on embellishments just to feel like they did something :).
>>
>> And I see you used yet another undocumented feature: filtering the
>> inspector :)
>>
>> Nice job!
>>
>> Doru
>>
>>
>>
>> On Tue, Mar 10, 2015 at 9:14 PM, Torsten Bergmann  wrote:
>>
>>> I spend some more minutes. So using GTTools in Pharo 4beta and a few
>>> more methods,
>>> pragmas, icons later we now have:
>>>
>>> MongoBrowser open
>>>
>>> which I also made available in the Tools menu. If you want to try out go
>>> to
>>> "Tools" -> "ConfigurationBrowser" and load MongoTalk in Pharo 4beta.
>>>
>>> See attached screenshot.
>>>
>>> This makes:
>>>
>>>   3 methods as class extensions for a custom GT inspector on each mongo
>>> domain object (mongo, database, collection)
>>>   4 methods to provide the 4 icons
>>>   1 method to provide the pragma for inclusion into world menu
>>> (#menuCommandOn:)
>>>   1 method to open
>>>
>>> which makes 9 methods to build a Mongo database UI browser in Pharo
>>> Smalltalk! Without the icons and menu item only 4 !!!
>>> Hey - Pharo rocks already and with GTTools we get even more empowered!
>>>
>>> Thanks to anyone who contributed to MongoTalk (especially Kent Beck for
>>> the initial implementation).
>>>
>>> Have fun
>>> T.
>>>
>>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"


Re: [Pharo-users] GTTools and Mongo

2015-03-11 Thread Christophe Demarey
Hi Phil,

Le 11 mars 2015 à 08:48, p...@highoctane.be a écrit :

> FWIW Mapless and its mongo support is quite awesome. I am using it for a 
> feature and it has tremendous potential.
> 

I would be interested to have a small comparison between voyage and mapless 
(pros and cons). Do you have enough feedback to list pros/cons for each library?

Christophe

smime.p7s
Description: S/MIME cryptographic signature


Re: [Pharo-users] GTTools and Mongo

2015-03-11 Thread p...@highoctane.be
And now for 2 images...

Pharo 4 for tools like this.
Pharo 3 for production code...

Any way to get this on 3 you think?
MongoTalk works fine there.

Am switching betweeen Pharo and Robomongo all the time here :-)

FWIW Mapless and its mongo support is quite awesome. I am using it for a
feature and it has tremendous potential.

Your tool will be a great inspiration for builing one for it.

Phil



Le 11 mars 2015 07:49, "Tudor Girba"  a écrit :

> He he.
>
> When the cost of building a tool gets too low, developers feel compelled
> to work on embellishments just to feel like they did something :).
>
> And I see you used yet another undocumented feature: filtering the
> inspector :)
>
> Nice job!
>
> Doru
>
>
>
> On Tue, Mar 10, 2015 at 9:14 PM, Torsten Bergmann  wrote:
>
>> I spend some more minutes. So using GTTools in Pharo 4beta and a few more
>> methods,
>> pragmas, icons later we now have:
>>
>> MongoBrowser open
>>
>> which I also made available in the Tools menu. If you want to try out go
>> to
>> "Tools" -> "ConfigurationBrowser" and load MongoTalk in Pharo 4beta.
>>
>> See attached screenshot.
>>
>> This makes:
>>
>>   3 methods as class extensions for a custom GT inspector on each mongo
>> domain object (mongo, database, collection)
>>   4 methods to provide the 4 icons
>>   1 method to provide the pragma for inclusion into world menu
>> (#menuCommandOn:)
>>   1 method to open
>>
>> which makes 9 methods to build a Mongo database UI browser in Pharo
>> Smalltalk! Without the icons and menu item only 4 !!!
>> Hey - Pharo rocks already and with GTTools we get even more empowered!
>>
>> Thanks to anyone who contributed to MongoTalk (especially Kent Beck for
>> the initial implementation).
>>
>> Have fun
>> T.
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>