Re: [Pharo-project] [Lsehub-staff] Quite a saturday night!

[Marcus Denker]

Could Helios be used to edit Pharo code?

On Mar 10, 2013, at 5:16 AM, Nicolas Petton  wrote:

> Hey guys,
> 
> Together with Ben we decided to take the evening and kick Helios[1]' ass!
> Here's the result, after 16 pomodoros:
> 
> helios speed, 2013-03-09 18:22:26 +, 25, 0, 0
> helios announcement fix, 2013-03-09 18:54:51 +, 25, 0, 0
> helios announcement fix, 2013-03-09 19:24:53 +, 25, 0, 0
> helios announcement fix 2, 2013-03-09 19:55:41 +, 25, 0, 0
> helios selectors cache, 2013-03-09 20:40:53 +, 25, 0, 0
> helios selectors cache 2, 2013-03-09 22:19:47 +, 25, 0, 0
> helios selectors cache 3, 2013-03-09 22:50:05 +, 25, 0, 0
> helios selectors cache 4, 2013-03-09 23:21:42 +, 25, 0, 0
> helios selectors cache 5, 2013-03-10 00:01:45 +, 25, 0, 0
> helios selectors cache 6, 2013-03-10 00:31:47 +, 25, 0, 0
> Helios Sytem Announcements, 2013-03-10 01:02:05 +, 25, 0, 0
> Helios Sytem Announcements, 2013-03-10 01:32:10 +, 25, 0, 0
> Helios Sytem Announcements 2, 2013-03-10 02:13:40 +, 25, 0, 0
> Helios Sytem Announcements 2, 2013-03-10 02:45:35 +, 25, 0, 0
> Helios Sytem Announcements 3 (Protocol), 2013-03-10 03:18:10 +, 25, 0, 0
> Helios Sytem Announcements 4, 2013-03-10 04:07:26 +, 25, 0, 0
> 
> As a result, Helios listens to all system announcements and it's something 
> like 10 times faster.
> 
> Cheers,
> Nico
> 
> [1] The next IDE of Amber

Re: [Pharo-project] fogbugz logins

[Benjamin]

I website to tackle this issue is ready to be deployed, but due to an issue 
with the IT crowd here, the website is not deployed yet.

We all hope that monday we will have a solution :) Let's cross fingers.

Anyway, I will of course send a mail as soon as possible with all the 
information needed :)

Ben

On Mar 10, 2013, at 3:34 AM, "Andrew P. Black"  wrote:

> I'm only an occasional reader here, but have noted (due to all of the reports 
> that bugs have been moved) that the bug database has moved.
> 
> It's very nice that I'm offered a link to view the status on the new fogbugz 
> site.
> 
> But how do I get an account?  I can't view anything without logging in.  
> There was no obvious "get an account" button.
> 
>   Andrew
> 
> 

[Pharo-project] Quite a saturday night!

[Nicolas Petton]

Hey guys,

Together with Ben we decided to take the evening and kick Helios[1]' ass!
Here's the result, after 16 pomodoros:

helios speed, 2013-03-09 18:22:26 +, 25, 0, 0
helios announcement fix, 2013-03-09 18:54:51 +, 25, 0, 0
helios announcement fix, 2013-03-09 19:24:53 +, 25, 0, 0
helios announcement fix 2, 2013-03-09 19:55:41 +, 25, 0, 0
helios selectors cache, 2013-03-09 20:40:53 +, 25, 0, 0
helios selectors cache 2, 2013-03-09 22:19:47 +, 25, 0, 0
helios selectors cache 3, 2013-03-09 22:50:05 +, 25, 0, 0
helios selectors cache 4, 2013-03-09 23:21:42 +, 25, 0, 0
helios selectors cache 5, 2013-03-10 00:01:45 +, 25, 0, 0
helios selectors cache 6, 2013-03-10 00:31:47 +, 25, 0, 0
Helios Sytem Announcements, 2013-03-10 01:02:05 +, 25, 0, 0
Helios Sytem Announcements, 2013-03-10 01:32:10 +, 25, 0, 0
Helios Sytem Announcements 2, 2013-03-10 02:13:40 +, 25, 0, 0
Helios Sytem Announcements 2, 2013-03-10 02:45:35 +, 25, 0, 0
Helios Sytem Announcements 3 (Protocol), 2013-03-10 03:18:10 +, 25, 0, 0
Helios Sytem Announcements 4, 2013-03-10 04:07:26 +, 25, 0, 0

As a result, Helios listens to all system announcements and it's something like 
10 times faster.

Cheers,
Nico

[1] The next IDE of Amber

signature.asc
Description: Message signed with OpenPGP using GPGMail

[Pharo-project] fogbugz logins

[Andrew P. Black]

I'm only an occasional reader here, but have noted (due to all of the reports 
that bugs have been moved) that the bug database has moved.

It's very nice that I'm offered a link to view the status on the new fogbugz 
site.

But how do I get an account?  I can't view anything without logging in.  There 
was no obvious "get an account" button.

Andrew

Re: [Pharo-project] access to pharoextras repository

[Ben Coman]

stephane ducasse wrote:

That is why, either we explicitly put the 'Tests' group in the 'default' group,



- I would go for this behavior because I do not like implicit behavior when 
this is about configuration
and I will start to write comments in all the configurations 


"default is used when nothing is specified by default it will load 
everything but better specify what everything is"


So once we agree I will start editing configurations like a mad.

Stef

  
In you book chapter about Configurations you might hint "why" it is 
preferred to include Tests in default.  For me...

* people fresh to the package get some examples.
* encourages new tests to be added.  Having to find & load a 'Tests' 
group at a later time would be an impediment to this.


You might also consider a convention for an 'Examples' group.

Re: [Pharo-project] Pharo consultants

[Mariano Martinez Peck]

Thanks Stef for the nice words :)
Maybe a first step which could be quite easy is to add a page of "Pharo
associated consultants" or something like that in the Pharo website. Like
the one we have now for contributors:
http://www.pharo-project.org/community/contributors
but for consultants. And each consultant can write a few keywords or small
paragraph about their expertise.

Best,

On Sat, Mar 9, 2013 at 7:11 PM, Sebastian Sastre <
sebast...@flowingconcept.com> wrote:

> Ah I get it, that's right.
>
> Probably what I mean is a better site of that goal which is answering *who
> is who in terms of what he/she did*
>
> thinking in https://angel.co/ as a benchmark
>
> sebastian 
>
> o/
>
>
>
>
>
> On Mar 9, 2013, at 5:39 PM, stephane ducasse wrote:
>
>
> That would be awesome.
>
> Glad to hear about an initiative to make things sustainable.
>
> A catalog of people who works using it would be great.
>
>
> We have the association just for that! In the next version we will add
> blogging facilities.
>
> No need to be a social network site, just a catalog for people to navigate
> who's working with it. Plus a subscribe/login for everyone manage its own
> profile so consultants can set a photo some bio and its portfolio
>
>
> Did you check the association web site :)
>
> Everybody could endorse skills or write reviews
>
>
> We cannot do that but you can link to linkedIn.
>
> I know I know... Linked In already kind of does that, but that's not the
> point
>
>
> so we are already linking into  linkedIn :)
>
>
> The point is that we have our little proprietary thing focused on Pharo
> and endorsed by Pharo itself
>
>
> We have the association and it points to linkedIn
>
>
> If I would have available time I would make flowing itself to sponsor with
> developing such a site/extension to current pharo site
>
>
> Sorry but I do not understand what you mean.
>
>
>
> sebastian 
>
> o/
>
>
>
>
>
> On Mar 8, 2013, at 6:05 PM, Stéphane Ducasse wrote:
>
> Hi guys
>
> I just got a nice chat with a cool Pharo expert (Mariano) that is doing
> consulting and development around Pharo and this is a cool feeling to know
> that smart guys in our community can find nice jobs that keeps them busy in
> Pharo.
> I think that we should market the community much more, because I think
> that this is important for other companies
> to know that they can find help with really talented people in our
> community.
> May be we should make more noise around:
> Pharo: a community with smart developers for cool business
>
> Stef
>
>
>
>
>
>
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com

Re: [Pharo-project] FMSound bass1 play

[p...@highoctane.be]

Never got that working on iOS. Obvious since:

- (void) ioBeep {
#ifdef BUILD_FOR_OSX
NSBeep();
#endif
}


On OSX

>From docs:

http://cocoadev.com/wiki/NSBeep

NSBeep() plays the system beep that the users have defined in the
Sound Panel of the System Preferences.

If sound effects aren't activated in there, no beep.

On a 2.0 image the Beeper primitiveBeep works perfectly with a VM
build from sources on 15/02/2013.

Phil

2013/3/9 stephane ducasse :
> but
>
> Beeper primitiveBeep
>
> still does not work
>
> Stef
>
> On Mar 9, 2013, at 11:05 PM, stephane ducasse  
> wrote:
>
>> The problem was that I had my headset plugged in and not on my ears => just 
>> one hour to find that is the indication that I should better go to sleep.
>>
>> Stef
>>
>> On Mar 9, 2013, at 10:21 PM, stephane ducasse  
>> wrote:
>>
>>> Hi guys
>>>
>>> I'm migrating the package Sound and MorphicSound to Pharo2.0 and 
>>> SmalltalkHub.
>>> But I cannot make
>>>
>>>  FMSound bass1 play
>>> produce a sound.
>>>
>>> Phil if i remember correctly you worked on that a couple of months ago.
>>> Can you summarize your findings?
>>>
>>> Stef
>>
>
>

Re: [Pharo-project] fogbugz entries

[Benjamin]

Most probably because during the migration, more specific status has been lost.

What you should do is list the open active cases
(I have something like First 50 open cases that are active which more or less 
is want I was used to have in Google Issue Tracker).


I will try to have a look at that and fix them by hand, but not now (pair 
programming on Amber with Nico) ^^ 

Ben

On Mar 9, 2013, at 8:55 PM, Camillo Bruni  wrote:

> I wanted to have a look at the new fogbugz entries.
> But when I list all active entries, I have quite a lot of entries with 
> "Closed (Active)", any clue what that means?

Re: [Pharo-project] FMSound bass1 play

[p...@highoctane.be]

Will have a look at my notes.

Phil

2013/3/9 stephane ducasse :
> The problem was that I had my headset plugged in and not on my ears => just 
> one hour to find that is the indication that I should better go to sleep.
>
> Stef
>
> On Mar 9, 2013, at 10:21 PM, stephane ducasse  
> wrote:
>
>> Hi guys
>>
>> I'm migrating the package Sound and MorphicSound to Pharo2.0 and 
>> SmalltalkHub.
>> But I cannot make
>>
>>   FMSound bass1 play
>> produce a sound.
>>
>> Phil if i remember correctly you worked on that a couple of months ago.
>> Can you summarize your findings?
>>
>> Stef
>
>

Re: [Pharo-project] Pharo consultants

[Sebastian Sastre]

Ah I get it, that's right.

Probably what I mean is a better site of that goal which is answering who is 
who in terms of what he/she did

thinking in https://angel.co/ as a benchmark

sebastian

o/





On Mar 9, 2013, at 5:39 PM, stephane ducasse wrote:

> 
>> That would be awesome.
>> 
>> Glad to hear about an initiative to make things sustainable.
>> 
>> A catalog of people who works using it would be great.
> 
> We have the association just for that! In the next version we will add 
> blogging facilities. 
> 
>> No need to be a social network site, just a catalog for people to navigate 
>> who's working with it. Plus a subscribe/login for everyone manage its own 
>> profile so consultants can set a photo some bio and its portfolio
> 
> Did you check the association web site :)
> 
>> Everybody could endorse skills or write reviews
> 
> We cannot do that but you can link to linkedIn.
> 
>> I know I know... Linked In already kind of does that, but that's not the 
>> point
> 
> so we are already linking into  linkedIn :)
>> 
>> The point is that we have our little proprietary thing focused on Pharo and 
>> endorsed by Pharo itself
> 
> We have the association and it points to linkedIn
> 
> 
>> If I would have available time I would make flowing itself to sponsor with 
>> developing such a site/extension to current pharo site 
> 
> Sorry but I do not understand what you mean.
> 
> 
>> 
>> sebastian
>> 
>> o/
>> 
>> 
>> 
>> 
>> 
>> On Mar 8, 2013, at 6:05 PM, Stéphane Ducasse wrote:
>> 
>>> Hi guys
>>> 
>>> I just got a nice chat with a cool Pharo expert (Mariano) that is doing 
>>> consulting and development around Pharo and this is a cool feeling to know 
>>> that smart guys in our community can find nice jobs that keeps them busy in 
>>> Pharo. 
>>> I think that we should market the community much more, because I think that 
>>> this is important for other companies
>>> to know that they can find help with really talented people in our 
>>> community. 
>>> May be we should make more noise around:
>>> Pharo: a community with smart developers for cool business
>>> 
>>> Stef
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
> 

Re: [Pharo-project] FMSound bass1 play

[stephane ducasse]

but 

Beeper primitiveBeep

still does not work

Stef

On Mar 9, 2013, at 11:05 PM, stephane ducasse  wrote:

> The problem was that I had my headset plugged in and not on my ears => just 
> one hour to find that is the indication that I should better go to sleep.
> 
> Stef
> 
> On Mar 9, 2013, at 10:21 PM, stephane ducasse  
> wrote:
> 
>> Hi guys
>> 
>> I'm migrating the package Sound and MorphicSound to Pharo2.0 and 
>> SmalltalkHub.
>> But I cannot make 
>> 
>>  FMSound bass1 play
>> produce a sound.
>> 
>> Phil if i remember correctly you worked on that a couple of months ago.
>> Can you summarize your findings?
>> 
>> Stef
> 

Re: [Pharo-project] FMSound bass1 play

[stephane ducasse]

The problem was that I had my headset plugged in and not on my ears => just one 
hour to find that is the indication that I should better go to sleep.

Stef

On Mar 9, 2013, at 10:21 PM, stephane ducasse  wrote:

> Hi guys
> 
> I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub.
> But I cannot make 
> 
>   FMSound bass1 play
> produce a sound.
> 
> Phil if i remember correctly you worked on that a couple of months ago.
> Can you summarize your findings?
> 
> Stef

Re: [Pharo-project] access to pharoextras repository

[stephane ducasse]

> That is not what I said :).

ok I see :)

> 
> We often get at least two groups in a configuration:
> - Core - the real code
> - Tests - the associated tests

Yes I tried to get consistent.

> The question is what should be loaded by 'default' (this is what gets loaded 
> when you do not specify anything in the dependency).
Ok I forgot that one.

> By saying 
>   spec group: 'default' with: #('Core')
> we say that by default we do not load tests. 

Yes and by default I would prefer to get the tests too :)

> If we do not specify any 'default', it will take by default everything, hence 
> it will be equivalent in our case with
>   spec group: 'default' with: #('Core' 'Tests');

Does it really load everything?
So default is ALL by default --- I forgot again. 

> I would want to favor the loading of tests by default.

Me too.

> That is why, either we explicitly put the 'Tests' group in the 'default' 
> group,

- I would go for this behavior because I do not like implicit behavior when 
this is about configuration
and I will start to write comments in all the configurations 

"default is used when nothing is specified by default it will load 
everything but better specify what everything is"


So once we agree I will start editing configurations like a mad.

Stef


> or we do not specify a 'default' at all in trivial configurations like the 
> ConfigurationOfXMLParser.
> 
> Cheers,
> Doru
> 
> 
>>> Hi,
>>> 
>>> Could anyone provide me with access to the PharoExtras team on STHub?
>>> 
>>> I would need to modify a bit the ConfigurationOfXMLParser to load both Core 
>>> and Tests by default.
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> 
>>> --
>>> www.tudorgirba.com
>>> 
>>> "If you can't say why something is relevant, 
>>> it probably isn't."
>>> 
>>> 
>> 
>> 
> 
> --
> www.tudorgirba.com
> 
> "Speaking louder won't make the point worthier."
> 
> 

Re: [Pharo-project] customizing the CommandLineHandler to run Moose tests

[stephane ducasse]

thanks!

Stef

On Mar 9, 2013, at 10:41 PM, Tudor Girba  wrote:

> Hi,
> 
> I wanted to investigate it a bit more before announcing the problem. You can 
> reproduce it on Mac, quite consistently: just run the attached script (you 
> need to have wget installed), or do it manually:
> 
> 1. download and unzip the latest Moose 4.8:
> https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/artifact/Moose-latest-dev-4.8.zip
> 2. download and unzip the latest Pharo VM:
> http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip
> 3. execute:
> ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest
> 
> 
> The VM crashes, but there is no trace of the error.
> 
> Cheers,
> Doru
> 
> 
> On Mar 9, 2013, at 1:35 PM, stephane ducasse  wrote:
> 
>> Hi doru
>> 
>> can you report precisely because now we cannot take any action?
>> 
>> Stef
>> 
>>> 
>>> p.s. The VM still crashes when running the tests though (at least on Mac)
>> 
> 
> --
> www.tudorgirba.com
> 
> "What is more important: To be happy, or to make happy?"
> 
> 

Re: [Pharo-project] access to pharoextras repository

[Tudor Girba]

Hi,

On Mar 9, 2013, at 12:27 PM, stephane ducasse  wrote:

> It would be good to have a discussion because all the packages I did do not 
> follow this. 
> 
> what is the point to have a Tests group if the core and default already load 
> them?

That is not what I said :).

We often get at least two groups in a configuration:
- Core - the real code
- Tests - the associated tests

The question is what should be loaded by 'default' (this is what gets loaded 
when you do not specify anything in the dependency).

By saying 
spec group: 'default' with: #('Core')
we say that by default we do not load tests. 

If we do not specify any 'default', it will take by default everything, hence 
it will be equivalent in our case with
spec group: 'default' with: #('Core' 'Tests');

I would want to favor the loading of tests by default. That is why, either we 
explicitly put the 'Tests' group in the 'default' group, or we do not specify a 
'default' at all in trivial configurations like the ConfigurationOfXMLParser.

Cheers,
Doru


>> Hi,
>> 
>> Could anyone provide me with access to the PharoExtras team on STHub?
>> 
>> I would need to modify a bit the ConfigurationOfXMLParser to load both Core 
>> and Tests by default.
>> 
>> Cheers,
>> Doru
>> 
>> 
>> --
>> www.tudorgirba.com
>> 
>> "If you can't say why something is relevant, 
>> it probably isn't."
>> 
>> 
> 
> 

--
www.tudorgirba.com

"Speaking louder won't make the point worthier."

Re: [Pharo-project] customizing the CommandLineHandler to run Moose tests

[Tudor Girba]

Hi,

I wanted to investigate it a bit more before announcing the problem. You can 
reproduce it on Mac, quite consistently: just run the attached script (you need 
to have wget installed), or do it manually:

1. download and unzip the latest Moose 4.8:
https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/artifact/Moose-latest-dev-4.8.zip
2. download and unzip the latest Pharo VM:
http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip
3. execute:
./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest


The VM crashes, but there is no trace of the error.

Cheers,
Doru


On Mar 9, 2013, at 1:35 PM, stephane ducasse  wrote:

> Hi doru
> 
> can you report precisely because now we cannot take any action?
> 
> Stef
> 
>> 
>> p.s. The VM still crashes when running the tests though (at least on Mac)
> 

--
www.tudorgirba.com

"What is more important: To be happy, or to make happy?"

[Pharo-project] is the latest Pharo VM beep enabled?

[Stéphane Ducasse]

Hi 

Beeper primitiveBeep but I do not get any sounds.

primitiveBeep
"Make a primitive beep. Not to be called directly.
It is much better to use Beeper class>>beep
or Beeper class>>beepPrimitive
since this method bypasses the current
registered playable entity and does not
check SoundSettings class>>soundEnabled."


self primitiveFailed

Stef

[Pharo-project] FMSound bass1 play

[stephane ducasse]

Hi guys

I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub.
But I cannot make 

FMSound bass1 play
 produce a sound.

Phil if i remember correctly you worked on that a couple of months ago.
Can you summarize your findings?

Stef

[Pharo-project] Deprecating MetaRepoForPharo13

[Stéphane Ducasse]

Hello Pharoers

I suggest that we deprecate MetaRepoForPharo13 on squeaksource. We can either 
turn it as private or at least readonly.
What do you think?
I like cleaning….

Stef

Re: [Pharo-project] [Pharo-users] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

[Stéphane Ducasse]

Janko

I sent some topics now I think that it would be better to edit directly the web 
site because else somebody will have to do it again.
So if you need I can edit directly a form. 

Stef


> Hi Stef,
> 
> Post on the mailing list for each project idea by following this template:
> 
>  Level: (beginner, intermediate, advanced)
> 
>  Possible mentor:
> 
>  Possible second mentor:
> 
>  Description
> 
>  Technical Details
> 
>  Benefits to the Student
> 
>  Benefits to the Community
> 
> Best regards
> Janko
> 
> Dne 09. 03. 2013 13:46, piše stephane ducasse:
>> Hi janko
>> 
>> How do you want to proceed for the topics?
>> I have a list of topics now where do we write them.
>> 
>>  - tool support rewrite rules
>>  - new generation debugger 
>>  - new change model and session manager (with martin dias)
>>  - improving roassal (with alexandre bergel et vanessa pena)
>>  - improving eyesee (with alexandre bergel et vanessa pena)
>>  - support touch event
>>  - UIPainter (with esteban lorenzano)
>>  - New widgets
>>  
>> 
>> Stef
>> 
>> 
>>> Dear Smalltalkers,
>>> 
>>> Time for your cool project ideas on this year Smalltalk GSoC!
>>> 
>>> For now just express any idea you have here on the mailing list. Later
>>> we will together develop it to be in complete format together with two
>>> mentors needed. Deadline is end of Mart, so we have three weeks of time.
>>> To see how fully developed ideas look like please look at 2012 ones at:
>>> http://gsoc2012.esug.org/ideas.
>>> 
>>> Note also that students yourselves can propose a GSoC project. So if you
>>> like to be a student on this year GSoC and have a nice idea, don't be
>>> shy and propose it here! The community will listen you and guide to the
>>> really nicely proposed project. Last year 6 student proposed projects
>>> were accepted and finished successfully!
>>> 
>>> For the community, start looking around for students. Think about how to
>>> approach the universities near by you, do you know who to contact
>>> there, etc.
>>> 
>>> We are namely preparing an application to this year Smalltalk Google
>>> Summer of Code under ESUG umbrella, as last year. If accepted, Google
>>> will pay few stipendiums to students on our Smalltalk projects.
>>> 
>>> More on our special Smalltalk GSoC 2013 website:
>>> 
>>> http://gsoc2013.esug.org
>>> 
>>> I'm specially inviting mentors of all past GSoCs to rejoin the mentors
>>> mailing list, where we discuss all details about this year GSoC:
>>> 
>>> http://groups.google.com/group/smalltalk-gsoc-mentors
>>> 
>>> While students interested on GSoC please join a special Smalltalk GSoC
>>> mailing list for you:
>>> 
>>> http://groups.google.com/group/smalltalk-gsoc-students
>>> 
>>> Best regards
>>> Janko
>>> 
>>> 
>>> -- 
>>> Janko Mivšek
>>> Aida/Web
>>> Smalltalk Web Application Server
>>> http://www.aidaweb.si
>>> 
>> 
>> 
>> 
> 
> -- 
> Janko Mivšek
> Aida/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
> 

Re: [Pharo-project] [Pharo-users] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

[Stéphane Ducasse]

===

UIPainter

===

 Level: advanced

 Possible mentor: Stéphane Ducasse

 Possible second mentor: Esteban Lorenzano

 Description: The purpose is to offer a way to easily describe and create UI 
using a point and click interface.
This interface should be extendable, as well as the widget proposed. The 
Painter should also propose a simple way
to link widgets together, and to locally redefine behaviours.

 Technical Details: using Spec, the UIPainter should be able to generate the 
needed methods (and Layouts).
The UI corresponding class could also be generated.

 Benefits to the Student: A deep understanding of UI creation. A good set of 
knowledges about widgets interactions.
The students will also benefits of an understanding of Spec at all the levels.

 Benefits to the Community: The community will benefit of a new tool for 
generating UIs easily using the new platform independent UI framework.
A UIPainter will help developers by improving the widgets reuse and simply the 
process of UI creation.

===

Spec platform/framework Independence

===

 Level: intermediate

 Possible mentor: Stéphane Ducasse

 Possible second mentor: Nicolas Petton

 Description: The goal is to improve and ensure the platform independence of 
Spec. 
Indeed, one of Spec goals is to generate widgets on multiple UI rendering 
framework (Morphic, Seaside, etc).
The student could improve Spec by providing a set of widgets for multiple 
framework, and ensure the usability of Spec in different Smalltalk dialect.

 Technical Details: Currently running only in Pharo, Spec should be able to be 
used easily on Squeak.
One interesting target is to be able to use it in Amber by example.

 Benefits to the Student: the student will acquire knowledge and experience 
about different Smalltalk implementation.
He will also experience different UI framework, and trough Spec how widgets 
interact with each others.

 Benefits to the Community: The community will benefit of the coolness of Spec, 
and will also have a single way to define UIs
regardless of the framework used to render them.

===

Nautilus In Spec

===

 Level: intermediate

 Possible mentor: Stéphane Ducasse

 Possible second mentor: Benjamin Van Ryseghem

 Description: Nautilus is the new default browser for Pharo3.0. But because the 
UI is fully platform dependent, it can not be used in other dialects (contrary 
to OB by example).
The goal is to migrate the entire Nautilus UI to a Spec based version, ti be 
able to export Nautilus.

 Technical Details: Currently Nautilus is fully written using Morphic (and even 
have its own morphic widgets). The idea is to redefine the existing UI using 
Spec, rethink the way interaction between sub widget is done,
and provide a way to statically describe Nautilus UI.

 Benefits to the Student: the student will acquire knowledge about Morphic. He 
will also learn how Spec is working and its mechanisms for event propagation as 
well as widget static description.
He will also learn how to define new Spec widgets and how to link them to 
already existing Morphic widgets.

 Benefits to the Community: The community will benefit of a more modular UI for 
Nautilus (since every one can then specify its one Nautilus UI), as well as a 
browser which may be
used in different dialects.

===

Re: [Pharo-project] Pharo consultants

[stephane ducasse]

> That would be awesome.
> 
> Glad to hear about an initiative to make things sustainable.
> 
> A catalog of people who works using it would be great.

We have the association just for that! In the next version we will add blogging 
facilities. 

> No need to be a social network site, just a catalog for people to navigate 
> who's working with it. Plus a subscribe/login for everyone manage its own 
> profile so consultants can set a photo some bio and its portfolio

Did you check the association web site :)

> Everybody could endorse skills or write reviews

We cannot do that but you can link to linkedIn.

> I know I know... Linked In already kind of does that, but that's not the point

so we are already linking into  linkedIn :)
> 
> The point is that we have our little proprietary thing focused on Pharo and 
> endorsed by Pharo itself

We have the association and it points to linkedIn


> If I would have available time I would make flowing itself to sponsor with 
> developing such a site/extension to current pharo site 

Sorry but I do not understand what you mean.


> 
> sebastian
> 
> o/
> 
> 
> 
> 
> 
> On Mar 8, 2013, at 6:05 PM, Stéphane Ducasse wrote:
> 
>> Hi guys
>> 
>> I just got a nice chat with a cool Pharo expert (Mariano) that is doing 
>> consulting and development around Pharo and this is a cool feeling to know 
>> that smart guys in our community can find nice jobs that keeps them busy in 
>> Pharo. 
>> I think that we should market the community much more, because I think that 
>> this is important for other companies
>> to know that they can find help with really talented people in our 
>> community. 
>> May be we should make more noise around:
>>  Pharo: a community with smart developers for cool business
>> 
>> Stef
>> 
>> 
>> 
>> 
>> 
> 

Re: [Pharo-project] Pharo consultants

[Sebastian Sastre]

That would be awesome.

Glad to hear about an initiative to make things sustainable.

A catalog of people who works using it would be great.

No need to be a social network site, just a catalog for people to navigate 
who's working with it. Plus a subscribe/login for everyone manage its own 
profile so consultants can set a photo some bio and its portfolio

Everybody could endorse skills or write reviews

I know I know... Linked In already kind of does that, but that's not the point

The point is that we have our little proprietary thing focused on Pharo and 
endorsed by Pharo itself

If I would have available time I would make flowing itself to sponsor with 
developing such a site/extension to current pharo site 

sebastian

o/





On Mar 8, 2013, at 6:05 PM, Stéphane Ducasse wrote:

> Hi guys
> 
> I just got a nice chat with a cool Pharo expert (Mariano) that is doing 
> consulting and development around Pharo and this is a cool feeling to know 
> that smart guys in our community can find nice jobs that keeps them busy in 
> Pharo. 
> I think that we should market the community much more, because I think that 
> this is important for other companies
> to know that they can find help with really talented people in our community. 
> May be we should make more noise around:
>   Pharo: a community with smart developers for cool business
> 
> Stef
> 
> 
> 
> 
> 

[Pharo-project] fogbugz entries

[Camillo Bruni]

I wanted to have a look at the new fogbugz entries.
But when I list all active entries, I have quite a lot of entries with "Closed 
(Active)", any clue what that means?

Re: [Pharo-project] Pharo Command Line

[Igor Stasenko]

@Stef in the attached.. conclusion seems highly unrelated to zero conf :)

On 8 March 2013 22:14, Stéphane Ducasse  wrote:
> Because in Pharo we are doing more than talking and we value documentation ……
> Yes guys you can twitt that one!
>
> :)
>
>
>
>
>
>
>
> On Mar 8, 2013, at 2:50 PM, Torsten Bergmann  wrote:
>
>> Sven wrote:
>>> The last couple of days I have been using the new command line tools and 
>>> zero conf scripts for real and I must say that I am >truly impressed and 
>>> happy.
>>>
>>> The save, printVersion, eval, st, config and test handlers are a joy to 
>>> work with. The terminal colours add a nice polish.
>>
>> Any documentation on it, blog posts or pharocasts available?
>>
>> Thx
>> Torsten
>>
>>
>>
>
>



-- 
Best regards,
Igor Stasenko.

Re: [Pharo-project] Pharo Command Line

[Camillo Bruni]

On 2013-03-09, at 13:52, stephane ducasse  wrote:
> On Mar 9, 2013, at 12:49 AM, Camillo Bruni  wrote:
>> On 2013-03-08, at 22:14, Stéphane Ducasse  wrote:
>> 
>>> Because in Pharo we are doing more than talking and we value documentation 
>>> ……
>>> Yes guys you can twitt that one!
>> 
>> thanks stef.
>> 
>> though something to nag about... :P why is code not in a fixed-width font in 
>> the
>> pdf? :D It breaks all the formatting for the help comments.
> 
> 
> Because I ***HATE*** \tt in pdf because it slows reading :)
> This is like that in all the books I wrote.

it's called source code, not english prose text or a roman.
and in this particular case you broke readability 100% because my help output 
was aligned.

Re: [Pharo-project] [Pharo-users] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

[Janko Mivšek]

Hi Stef,

Post on the mailing list for each project idea by following this template:

  Level: (beginner, intermediate, advanced)

  Possible mentor:

  Possible second mentor:

  Description

  Technical Details

  Benefits to the Student

  Benefits to the Community

Best regards
Janko

Dne 09. 03. 2013 13:46, piše stephane ducasse:
> Hi janko
> 
> How do you want to proceed for the topics?
> I have a list of topics now where do we write them.
> 
>   - tool support rewrite rules
>   - new generation debugger 
>   - new change model and session manager (with martin dias)
>   - improving roassal (with alexandre bergel et vanessa pena)
>   - improving eyesee (with alexandre bergel et vanessa pena)
>   - support touch event
>   - UIPainter (with esteban lorenzano)
>   - New widgets
>   
> 
> Stef
> 
> 
>> Dear Smalltalkers,
>>
>> Time for your cool project ideas on this year Smalltalk GSoC!
>>
>> For now just express any idea you have here on the mailing list. Later
>> we will together develop it to be in complete format together with two
>> mentors needed. Deadline is end of Mart, so we have three weeks of time.
>> To see how fully developed ideas look like please look at 2012 ones at:
>> http://gsoc2012.esug.org/ideas.
>>
>> Note also that students yourselves can propose a GSoC project. So if you
>> like to be a student on this year GSoC and have a nice idea, don't be
>> shy and propose it here! The community will listen you and guide to the
>> really nicely proposed project. Last year 6 student proposed projects
>> were accepted and finished successfully!
>>
>> For the community, start looking around for students. Think about how to
>> approach the universities near by you, do you know who to contact
>> there, etc.
>>
>> We are namely preparing an application to this year Smalltalk Google
>> Summer of Code under ESUG umbrella, as last year. If accepted, Google
>> will pay few stipendiums to students on our Smalltalk projects.
>>
>> More on our special Smalltalk GSoC 2013 website:
>>
>>  http://gsoc2013.esug.org
>>
>> I'm specially inviting mentors of all past GSoCs to rejoin the mentors
>> mailing list, where we discuss all details about this year GSoC:
>>
>>  http://groups.google.com/group/smalltalk-gsoc-mentors
>>
>> While students interested on GSoC please join a special Smalltalk GSoC
>> mailing list for you:
>>
>>  http://groups.google.com/group/smalltalk-gsoc-students
>>
>> Best regards
>> Janko
>>
>>
>> -- 
>> Janko Mivšek
>> Aida/Web
>> Smalltalk Web Application Server
>> http://www.aidaweb.si
>>
> 
> 
> 

-- 
Janko Mivšek
Aida/Web
Smalltalk Web Application Server
http://www.aidaweb.si

Re: [Pharo-project] Pharo Command Line

[stephane ducasse]

On Mar 9, 2013, at 12:49 AM, Camillo Bruni  wrote:

> 
> On 2013-03-08, at 22:14, Stéphane Ducasse  wrote:
> 
>> Because in Pharo we are doing more than talking and we value documentation ……
>> Yes guys you can twitt that one!
> 
> thanks stef.
> 
> though something to nag about... :P why is code not in a fixed-width font in 
> the
> pdf? :D It breaks all the formatting for the help comments.


Because I ***HATE*** \tt in pdf because it slows reading :)
This is like that in all the books I wrote.

Stef

Re: [Pharo-project] building traits programmatically

[stephane ducasse]

On Mar 8, 2013, at 11:50 PM, Ciprian Teodorov  
wrote:

> 
> 
> On Fri, Mar 8, 2013 at 10:32 PM, stephane ducasse  
> wrote:
> 
> On Mar 8, 2013, at 7:57 PM, Ciprian Teodorov  
> wrote:
> 
>> Hi guys,
>> 
>> Can anyone give me some pointers on how to create traits dynamically?
> 
> you mean with the refactoring engine?
> Yes something like it, I am little confused with all ring, rb stuff.

ring is simple: imagine that all the tools can manipulate objects that 
represent objects that get executed.
for RB you have an engine to transform code.
Now to programmatically create traits you do not need RB nor ring

> But I know that I can build classes, add methods, and see changes (and apply 
> them) using RBNamespace api... it does not seem to work with traits. Some 
> time ago I have spend some time patching the RB thingy to accept trait 
> also... but then I have run into other problems (i don't remember exactly 
> what)... Moreover, it was just hacks to make it work... so I've lost them 
> over time... and I don't like patching every new image that I download with 
> my changes to make It work...
> 
> So maybe, I don't use them right... or there are things that should be 
> done... I'm willing to contribute, if it helps.

looking a the enhancements proposed to make rb handle traits would be good

> 
> I know that one argentinian student added support for traits in RB but I 
> never got the time to have a look and integrate it.
> cool, maybe we should have a look...
> 
> Then again, it is not clear in my head what is the politics of traits and 
> pharo... I know that there were some discussions about them being bad because 
> their methods are copied to classes, not being well integrated….

it was just for implementors. 

> how exactly do they fit in the big picture (next pharo versions). Can we use 
> them as they are now, or the implementation is likely to change in the near 
> future? -- stateful traits, or something else? 

No stateful traits in the horizon.
For now traits will stay but we should have a look at the internal 
implementation to simplify it.
Second the internal change should not impact external users and will be 
transparent.


> 
> cheers,
> ciprian
> 
> 
>> I have tried something like: 
>> 
>> model := RBNamespace new.
>> 
>> model defineClass: ('Trait named: #TMyTrait
>>  uses: {}
>>  category: ''My-Tests''').
>> 
>> and I get a DNU: RBAddTraitChange>>superclassName
>> 
>> Cheers,
>> -- 
>> Dr. Ciprian TEODOROV
>> Ingénieur Développement CAO
>> 
>> tél : 06 08 54 73 48
>> mail : ciprian.teodo...@gmail.com
>> www.teodorov.ro
> 
> 
> 
> 
> -- 
> Dr. Ciprian TEODOROV
> Ingénieur Développement CAO
> 
> tél : 06 08 54 73 48
> mail : ciprian.teodo...@gmail.com
> www.teodorov.ro

Re: [Pharo-project] [squeak-dev] GSoC13: Google Summer of Code started, your ideas please!

[stephane ducasse]

Hi janko

How do you want to proceed for the topics?
I have a list of topics now where do we write them.

- tool support rewrite rules
- new generation debugger 
- new change model and session manager (with martin dias)
- improving roassal (with alexandre bergel et vanessa pena)
- improving eyesee (with alexandre bergel et vanessa pena)
- support touch event
- UIPainter (with esteban lorenzano)
- New widgets


Stef


> Dear Smalltalkers,
> 
> Time for your cool project ideas on this year Smalltalk GSoC!
> 
> For now just express any idea you have here on the mailing list. Later
> we will together develop it to be in complete format together with two
> mentors needed. Deadline is end of Mart, so we have three weeks of time.
> To see how fully developed ideas look like please look at 2012 ones at:
> http://gsoc2012.esug.org/ideas.
> 
> Note also that students yourselves can propose a GSoC project. So if you
> like to be a student on this year GSoC and have a nice idea, don't be
> shy and propose it here! The community will listen you and guide to the
> really nicely proposed project. Last year 6 student proposed projects
> were accepted and finished successfully!
> 
> For the community, start looking around for students. Think about how to
> approach the universities near by you, do you know who to contact
> there, etc.
> 
> We are namely preparing an application to this year Smalltalk Google
> Summer of Code under ESUG umbrella, as last year. If accepted, Google
> will pay few stipendiums to students on our Smalltalk projects.
> 
> More on our special Smalltalk GSoC 2013 website:
> 
>   http://gsoc2013.esug.org
> 
> I'm specially inviting mentors of all past GSoCs to rejoin the mentors
> mailing list, where we discuss all details about this year GSoC:
> 
>   http://groups.google.com/group/smalltalk-gsoc-mentors
> 
> While students interested on GSoC please join a special Smalltalk GSoC
> mailing list for you:
> 
>   http://groups.google.com/group/smalltalk-gsoc-students
> 
> Best regards
> Janko
> 
> 
> -- 
> Janko Mivšek
> Aida/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
> 

Re: [Pharo-project] customizing the CommandLineHandler to run Moose tests

[stephane ducasse]

this is cool :)

> Hi,
> 
> Now that the continuous integration build is using the cool ZeroConf 
> infrastructure, we needed a clean way to run all tests from Moose based on 
> the information gathered from the ConfigurationOfMoose. More precisely we 
> want to run all the tests from all packages that are in the 'Tests' group 
> from all configurations referred from ConfigurationOfMoose (including itself) 
> :).
> 
> It's sounds more complicated than it actually is:
> packages
>   | packages |
>   packages := Set new.
>   (self mooseDevelopmentVersion packagesForSpecNamed: 'Tests') do: [ 
> :spec | packages add: spec name ].
>   self mooseDevelopmentVersion projects do: [ :each | 
>   (each version packagesForSpecNamed: 'Tests') do: [ :spec | 
> packages add: spec name ] ].
>   ^ packages
> 
> We used to have this logic in an .st file that was ran through the builder 
> from Lukas.
> 
> But, now, I simply created the MooseTestRunnerCommandLineHandler as a 
> subclass of TestRunnerCommandLineHandler, and provided the new packages. I 
> gave it the commandName of 'moosetest' and now I can simply call from the 
> command line:
> 
> Pharo ./Moose-latest-dev-4.8.image moosetest
> 
> In Moose, we have a little package named: Moose-Development-Tools that is 
> loaded by the configuration. I added the new class to it, and I can easily 
> integrate the whole test running in the ci job after loading the 
> configuration.
> 
> I'd say it's pretty neat.
> 
> Cheers,
> Doru
> 
> p.s. The VM still crashes when running the tests though (at least on Mac)
> 
> --
> www.tudorgirba.com
> 
> "Beauty is where we see it."
> 
> 
> 
> 

Re: [Pharo-project] customizing the CommandLineHandler to run Moose tests

[stephane ducasse]

Hi doru

can you report precisely because now we cannot take any action?

Stef

> 
> p.s. The VM still crashes when running the tests though (at least on Mac)

[Pharo-project] GSoC13: Google Summer of Code started, your ideas please!

[Janko Mivšek]

Dear Smalltalkers,

Time for your cool project ideas on this year Smalltalk GSoC!

For now just express any idea you have here on the mailing list. Later
we will together develop it to be in complete format together with two
mentors needed. Deadline is end of Mart, so we have three weeks of time.
To see how fully developed ideas look like please look at 2012 ones at:
http://gsoc2012.esug.org/ideas.

Note also that students yourselves can propose a GSoC project. So if you
like to be a student on this year GSoC and have a nice idea, don't be
shy and propose it here! The community will listen you and guide to the
really nicely proposed project. Last year 6 student proposed projects
were accepted and finished successfully!

For the community, start looking around for students. Think about how to
approach the universities near by you, do you know who to contact
there, etc.

We are namely preparing an application to this year Smalltalk Google
Summer of Code under ESUG umbrella, as last year. If accepted, Google
will pay few stipendiums to students on our Smalltalk projects.

More on our special Smalltalk GSoC 2013 website:

http://gsoc2013.esug.org

I'm specially inviting mentors of all past GSoCs to rejoin the mentors
mailing list, where we discuss all details about this year GSoC:

http://groups.google.com/group/smalltalk-gsoc-mentors

While students interested on GSoC please join a special Smalltalk GSoC
mailing list for you:

http://groups.google.com/group/smalltalk-gsoc-students

Best regards
Janko


-- 
Janko Mivšek
Aida/Web
Smalltalk Web Application Server
http://www.aidaweb.si

Re: [Pharo-project] access to pharoextras repository

[stephane ducasse]

It would be good to have a discussion because all the packages I did do not 
follow this. 

what is the point to have a Tests group if the core and default already load 
them?

> Hi,
> 
> Could anyone provide me with access to the PharoExtras team on STHub?
> 
> I would need to modify a bit the ConfigurationOfXMLParser to load both Core 
> and Tests by default.
> 
> Cheers,
> Doru
> 
> 
> --
> www.tudorgirba.com
> 
> "If you can't say why something is relevant, 
> it probably isn't."
> 
> 

Re: [Pharo-project] access to pharoextras repository

[Camillo Bruni]

aaan, you're a member

On 2013-03-09, at 03:28, Tudor Girba  wrote:

> Hi,
> 
> Could anyone provide me with access to the PharoExtras team on STHub?
> 
> I would need to modify a bit the ConfigurationOfXMLParser to load both Core 
> and Tests by default.
> 
> Cheers,
> Doru
> 
> 
> --
> www.tudorgirba.com
> 
> "If you can't say why something is relevant, 
> it probably isn't."
> 
>