date:20140521


For SystemLogger here is my roadmap

steps

- note that SystemLogger has a special logger that pushes strings 
to Transcript so we can have the same as now.


- right now in Object we have
crTrace
crTrace:
trace
trace:
traceCr
traceCr:
logCr: deprecated
crLog: deprecated
so we can use trace: (I do not like it that much but this is ok)


- check all the Transcript left reference
- convert them to use the SystemLogger probably to trace: so 
that after we can simply rewrite trace:
- I think that it would be good to have a single entry point in 
Object (even at the cost to send another call to the main log recording 
method)


- check all the log:
- convert them (since a log is an entry we do not need to have 
explicit cr)


- may be use a circular structure for holding entries because right 
now the logger logs as much as possible.
- We should probably have different settings and the default 
should be circular



- produce a nice transcript with structured log entries
- log entries should be able to provide specific actions
- for example a compiler logentry could hold a reference to 
the compiled method and we could ask to jump there

- filter logentries

- make sure that all the crLog: logCr: are nicely funnel to the 
systemLogger

- and that everything works

Re: [Pharo-dev] Call for co-coders





As a general matter, I would be interested in:
- unifying with the ZnLogEvent


SystemLogger is infrastructure low level. So I do not see why Zn and 
SystemLogger should be unified.


If this means talking to Sven this is a definite yes. I don’t think we 
need to unify with the current ZnLogEvent. Syncing with zinc is 
probably not the way to go anyway. Zinc is still an external framework 
(hence the namespace prefix). I did a zinc bridge which operates an a 
single event bridging from zinc to SystemLogger. This is not clever 
performance wise. A better approach is to plug into zincs LogSupport. 
We should hook into there so we just get the invocations from zinc and 
we can emit the proper SystemLogger events into the Log framework.
Sven will come up with something announcement based. And that is still 
a task for us, too. To look where functionality of SystemLogger is 
doubled with announcements.


We should pay attention that it stays small and simple.


first we should integrate it and make sure that all the Transcript 
show are funnelled to the Log frameworks.


Yes. Maybe we need to sync our understanding of log levels first. The 
exchange adds a log level and adding a tag would be good, too.


I do not get it but this is not a problem. No need to reply.


- Split the Log class


we will not split it because we iterated over the design since 8 
months with norbert :)


I cannot find the proposals of Doru. But I’m interested. I splitted 
the Log class already into BasicLog and Log. I’m not fully satisfied 
with it so … My concern about the Log class is more how get it right 
supporting different kind of Log classes and still have a working 
filtering in the Logger. But that we can discuss in the groups that 
form I guess

I would like to stop iterating. And again we should keep the system small.
I studied all the logger framework available and I think that we can 
look for the graal forever or get done and I want to get done

because there are other many many topics that can get fixed.
Right now we went from 0% to 80% and this is a good ratio. We iterated 
with you. Now I do not want to pass time to go to an hypothetical 85%.




- Possibly support Fuel serialization for each log entry

Please go ahead.


Yes. I don’t even understand what it means :)

Send code!

Re: [Pharo-dev] NewList without Icons

2014-05-21 Thread Benjamin

On 21 May 2014, at 00:08, Nicolai Hess  wrote:

> Therefore, is there a way  to create the NewList and tell it to NEVER
> ask for icons?
> 

As far as I remember I did not implement this option :)

But having a flag for that should not be too complicated to add ;)

Good luck,
Ben

Re: [Pharo-dev] Pharo in Rasbian ?

Thank you JB for the answer.
I am waiting for the integration :)

Jannik


2014-05-20 18:41 GMT+02:00 Jean Baptiste Arnaud 
:

> FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago.
>
> Wait a second. Nope.
>
> FFI, have been implemented and integrated on CogVM repository by Doug
> since 3 week, yes, not in Pharo repository.
> There are small differences between CogVM and PharoVM.
> A simple operation of extraction, installation, test , merge with the
> stable pharoS-vm rasp.
>
> So 3 week ago I extracted the code of Doug from the CogVM repository, I
> install it on my own jenkins.
> But nothing is integrated yet, except in my repository.
> Where also the OSProcess is currently tested.
>
> But no it is not in the latest pharos on raspberry.
>
>
>
>
> On 20 May 2014, at 17:43, Alexandre Bergel 
> wrote:
>
> Ah okay, this is an answer that I understand :-)
>
> We are not really good at promoting what we are doing.
> For the the case of Rasbian, it seems not that difficult to have Phratch
> and Pharo installed per default, if there is Scratch and Squeak.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> On May 20, 2014, at 11:06 AM, Clément Bera  wrote:
>
> FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago.
>
> So I guess the Phratch team has not found the time yet to do that, but it
> should be possible.
>
>
>
>
>
>
> Best Regards
> Jean Baptiste Arnaud
> jbaptiste.arn...@gmail.com
>
>
>
>
>
>
>
>


-- 

~~Jannik Laval~~
École des Mines de Douai
Enseignant-chercheur
http://www.jannik-laval.eu
http://www.phratch.com
http://car.mines-douai.fr/

Re: [Pharo-dev] Pharo in Rasbian ?

The point is that I am not so involved in the dev for raspbian.
I do not tested sound and camera. Probably they should be recompiled for
RPi.

FileSystem is not stable because it depends on NativeBoost, not implemented
for RPi for now.
I added a fix for that, but it is not what I really want.

So, before proposing it, we need to make it more stable, and cleaner.

Cheers,
Jannik


2014-05-20 17:43 GMT+02:00 Alexandre Bergel :

> Ah okay, this is an answer that I understand :-)
>
> We are not really good at promoting what we are doing.
> For the the case of  Rasbian, it seems not that difficult to have Phratch
> and Pharo installed per default, if there is Scratch and Squeak.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> On May 20, 2014, at 11:06 AM, Clément Bera  wrote:
>
> > FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago.
> >
> > So I guess the Phratch team has not found the time yet to do that, but
> it should be possible.
> >
>
>
>


-- 

~~Jannik Laval~~
École des Mines de Douai
Enseignant-chercheur
http://www.jannik-laval.eu
http://www.phratch.com
http://car.mines-douai.fr/

Re: [Pharo-dev] Call for co-coders


Hi phil

Have a  look at
- http://smalltalkhub.com/#!/~StephaneDucasse/SystemLogger
- and the chapter :)
https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/Logger/

On 19/5/14 11:01, p...@highoctane.be wrote:

SystemLogger interests me as well.

Phil

On Mon, May 19, 2014 at 10:17 AM, Norbert Hartl > wrote:


Hi Stef,

I’m definitely in for the SystemLogger. But as I am involved in it
anyway a fresh look from another person on that stuff could be
benefitial.

Norbert

Am 19.05.2014 um 09:10 schrieb stepharo mailto:steph...@free.fr>>:

> Hi guys
>
> This is a call for some of you that committed code and would
like to do it with me :).
> I have some projects that I would like to push further in 4.0
and I'm thinking that
> he could be much more fun to do it with other people.
>
> Here are some topics
>- integrating the systemLogger
>- integrating/improving the new method categorizer
>- cleaning fonts
>- ...
>
> How this could work?
> We could have
>- some discussions
>- make a little roadmap
>- then we could work on the same slice and do code review
>
> I think that it can be fun and motivating. So let me know
because I would like to have more social
> coding.
>
> Stef
>

Re: [Pharo-dev] Grant for MetaRepoForPharo30


Copying is nice because people can load when they get to your repo.
I systematically copy configuration.

On 19/5/14 21:16, Maximiliano Taborda wrote:

Ready. You got it now.

I decided to not update the config from the aconcagua repo, and 
maintain up to date only the one in the meta repo, because I can´t 
find a way to publish the same config version to more than one repo 
and I don't see the point of "copy" the same package in more than one 
repo.


If it doesn't exist the option, is a craziness thinking in publish to 
more than one repo the same config just in one action?


Regards.
Maxi.


2014-05-19 15:06 GMT-03:00 Sean P. DeNigris >:


Maximiliano Taborda wrote
> I want to publish Chalten and Aconcagua to the meta repo for 3.0.

If it's safe, will you copy the config to
http://smalltalkhub.com/mc/maxi/Aconcagua/main/ (there is an outdated
version there now)? I'd like to depend on it in my project without
involving
meta repo for 3.0. In general I've found it's always a good idea
to keep
copies of configs with the main project because you never know how
users
will find you! Thanks :)



-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Grant-for-MetaRepoForPharo30-tp4755362p4759574.html
Sent from the Pharo Smalltalk Developers mailing list archive at
Nabble.com.

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

We would love to have a real update but I'm sure that you realize that 
something we

are modifying the system that modify the methods modifying the system.

So we should probably remove the software update button.
Now if somebody wants to work on an infrastructure supporting real 
atomic load.


Stef
PS: the last time I updated my iPhone it blocked and I had to fully 
reinstall everything.
And once when I updated my mac my mouse got blocked forever on the left 
top corner.

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

yeah I think "Update" needs to be removed from World Menu. Imagine first
time trying Pharo and you exploring the World Menu which is the No 1 thing
a newcomer does , you find Update and use it and BOOM! this happens. I
would not blame that person if he / she says "fuck this" and removes Pharo
from his/her system.

Its not just that it brakes Pharo , it makes you really worried what else
it may do to your system.

I think also that even if its hidden it should always display a message
like "Update may really brake your Pharo image, make sure you saved your
image before proceeding . You want to save now ? " and offer an option to
save image.

Now with configurations being so popular maybe a method that will iterate
through all Configurations , update them and then load their packages, may
be the way to go for an update. That means that we need also to create some
guidelines on how configurations should be created to make the experience
smoother.

On Wed, May 21, 2014 at 1:11 PM, stepharo  wrote:

> We would love to have a real update but I'm sure that you realize that
> something we
> are modifying the system that modify the methods modifying the system.
>
> So we should probably remove the software update button.
> Now if somebody wants to work on an infrastructure supporting real atomic
> load.
>
> Stef
> PS: the last time I updated my iPhone it blocked and I had to fully
> reinstall everything.
> And once when I updated my mac my mouse got blocked forever on the left
> top corner.
>
>
>

[Pharo-dev] Understanding Workspace

Hello guys, I have started a new experiment of mine, a tool I call "Talos".
I want Talos to become workspace on steroids.

The first thing I want to implement is emacs like navigation. With that I
mean keyboard shortcuts for moving inside the text like you can do with
arrow keys already and the ability to move to the next word , the first
character of next word, the last character of next word , previous world,
quickly rename variables and all the great things one can do with emacs and
vim.

Of course I don't want to do all that at once, one step at a time.

Now I have take a look at Workspace and it seems that it uses
PlaggableTextMorph , it also looks like I can get the contents via
PluggableTextMorph>>text instance side. The source code returned is also
send to RBParser using the parseBlock method , I think for syntax
highlighting.

However because the PluggableTextMorph is very big and it does not even
have a class comment, though quite a lot of methods are commented, I am
really open to advice and suggestions on to how to parse the contents and
manipulate the cursor position.

I know I could use PettitParser but I dont know if there are better options
out there, or maybe I am doing the whole thing wrong.

So any advice and suggestion is more than welcomed.

Re: [Pharo-dev] Understanding Workspace

The first suggestion is to not invest in the PluggableTextMorph :)

Ideally, we should get the new text widget soon, but in the meantime, you
would be better with using Rubric. It is a pragmatic solution developed by
Alain Plantec and that works now. This is where we are going with the
Glamorous Toolkit at the moment. You find it already in the Moose image, or
you can download it from here:
http://smalltalkhub.com/#!/~AlainPlantec/Rubric

Cheers,
Doru


On Wed, May 21, 2014 at 12:44 PM, kilon alios  wrote:

> Hello guys, I have started a new experiment of mine, a tool I call
> "Talos". I want Talos to become workspace on steroids.
>
> The first thing I want to implement is emacs like navigation. With that I
> mean keyboard shortcuts for moving inside the text like you can do with
> arrow keys already and the ability to move to the next word , the first
> character of next word, the last character of next word , previous world,
> quickly rename variables and all the great things one can do with emacs and
> vim.
>
> Of course I don't want to do all that at once, one step at a time.
>
> Now I have take a look at Workspace and it seems that it uses
> PlaggableTextMorph , it also looks like I can get the contents via
> PluggableTextMorph>>text instance side. The source code returned is also
> send to RBParser using the parseBlock method , I think for syntax
> highlighting.
>
> However because the PluggableTextMorph is very big and it does not even
> have a class comment, though quite a lot of methods are commented, I am
> really open to advice and suggestions on to how to parse the contents and
> manipulate the cursor position.
>
> I know I could use PettitParser but I dont know if there are better
> options out there, or maybe I am doing the whole thing wrong.
>
> So any advice and suggestion is more than welcomed.
>



-- 
www.tudorgirba.com

"Every thing has its own flow"

[Pharo-dev] NativeBoost and WKHTML

2014-05-21 Thread Torsten Bergmann

Hi,

tried to wrap the WKHTML library (wkhtmltopdf.org) with NB to easily generate a 
PDF 
using HTML from Pharo. I think this could serve as an easy printing solution
for Pharo.

Code for an initial wrapper is on 
http://smalltalkhub.com/#!/~TorstenBergmann/WKHTML2PDF
with a simple class calling the component using NativeBoost. See class 
"WKPDFLibrary example"
I used Windows and the wkhtmltox.dll.

The C example I follow with only a few function calls is very simple and can be 
found at 
the bottom of: http://m.blog.csdn.net/blog/pengqianhe/8089007

The component is called, I get correct structs in return - but still no PDF 
file is generated. 
Currently I cant see the forest for the trees. Maybe someone can have a short 
look what I'm 
doing wrong.

Thanks in advance
T.

Re: [Pharo-dev] Understanding Workspace

Thank you Tudor, thats looks definitely very useful .

I am downloading it now and studying it :)


On Wed, May 21, 2014 at 3:10 PM, Tudor Girba  wrote:

> The first suggestion is to not invest in the PluggableTextMorph :)
>
> Ideally, we should get the new text widget soon, but in the meantime, you
> would be better with using Rubric. It is a pragmatic solution developed by
> Alain Plantec and that works now. This is where we are going with the
> Glamorous Toolkit at the moment. You find it already in the Moose image, or
> you can download it from here:
> http://smalltalkhub.com/#!/~AlainPlantec/Rubric
>
> Cheers,
> Doru
>
>
> On Wed, May 21, 2014 at 12:44 PM, kilon alios wrote:
>
>> Hello guys, I have started a new experiment of mine, a tool I call
>> "Talos". I want Talos to become workspace on steroids.
>>
>> The first thing I want to implement is emacs like navigation. With that I
>> mean keyboard shortcuts for moving inside the text like you can do with
>> arrow keys already and the ability to move to the next word , the first
>> character of next word, the last character of next word , previous world,
>> quickly rename variables and all the great things one can do with emacs and
>> vim.
>>
>> Of course I don't want to do all that at once, one step at a time.
>>
>> Now I have take a look at Workspace and it seems that it uses
>> PlaggableTextMorph , it also looks like I can get the contents via
>> PluggableTextMorph>>text instance side. The source code returned is also
>> send to RBParser using the parseBlock method , I think for syntax
>> highlighting.
>>
>> However because the PluggableTextMorph is very big and it does not even
>> have a class comment, though quite a lot of methods are commented, I am
>> really open to advice and suggestions on to how to parse the contents and
>> manipulate the cursor position.
>>
>> I know I could use PettitParser but I dont know if there are better
>> options out there, or maybe I am doing the whole thing wrong.
>>
>> So any advice and suggestion is more than welcomed.
>>
>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>

Re: [Pharo-dev] NativeBoost and WKHTML

2014-05-21 Thread Sven Van Caekenberghe

Just out of curiosity, why not use Artefact, 
https://sites.google.com/site/artefactpdf ?

I haven't looked at the different approaches, but I have this natural tendency 
against native libraries, if we can do it directly in Pharo. That is why I am 
asking: why this road and not the other ?

On 21 May 2014, at 14:14, Torsten Bergmann  wrote:

> Hi,
> 
> tried to wrap the WKHTML library (wkhtmltopdf.org) with NB to easily generate 
> a PDF 
> using HTML from Pharo. I think this could serve as an easy printing solution
> for Pharo.
> 
> Code for an initial wrapper is on 
> http://smalltalkhub.com/#!/~TorstenBergmann/WKHTML2PDF
> with a simple class calling the component using NativeBoost. See class 
> "WKPDFLibrary example"
> I used Windows and the wkhtmltox.dll.
> 
> The C example I follow with only a few function calls is very simple and can 
> be found at 
> the bottom of: http://m.blog.csdn.net/blog/pengqianhe/8089007
> 
> The component is called, I get correct structs in return - but still no PDF 
> file is generated. 
> Currently I cant see the forest for the trees. Maybe someone can have a short 
> look what I'm 
> doing wrong.
> 
> Thanks in advance
> T.
> 
> 
> 
> 
>

Re: [Pharo-dev] Call for co-coders

Hi,

I really do not get the tone of these replies, but perhaps my mail was not
clear. So, let me start over.

You asked for who is interested in joining co-coding, and I said that I am
interested particularly in the area of the logger.

Specifically, I would be interested in splitting the Log class into two:
- a Log class holding the current class side methods
- a LogEvent (or LogEntry, or LogItem or whatever other name indicating the
result of a single log statement) that holds the instance side of the
current Log class.

As it is now, when I execute:
Log critical: 'message'

I get an instance of Log. This is confusing, and not needed. We can nicely
get an instance of LogEvent. This will not complicate things at all.

Next, I said that as we already have a Zinc logging mechanism, I would be
interested in consolidating Zinc to use the new mechanism. This would also
provide a case study for having explicit classes of LogEvents and see the
implications of that.

And finally, I mentioned the Fuel serialization. My idea was to offer a
cheap way to serialize a log into a file by serializing each log entry as a
fuel object, but I did not know that we already have a JSON serialization.
So, this is not that much of a priority anymore.

I will propose code for the splitting.

Doru


On Wed, May 21, 2014 at 9:05 AM, stepharo  wrote:

>
>
 As a general matter, I would be interested in:
 - unifying with the ZnLogEvent

>>>
>>>  SystemLogger is infrastructure low level. So I do not see why Zn and
> SystemLogger should be unified.
>
>
>  If this means talking to Sven this is a definite yes. I don’t think we
>> need to unify with the current ZnLogEvent. Syncing with zinc is probably
>> not the way to go anyway. Zinc is still an external framework (hence the
>> namespace prefix). I did a zinc bridge which operates an a single event
>> bridging from zinc to SystemLogger. This is not clever performance wise. A
>> better approach is to plug into zincs LogSupport. We should hook into there
>> so we just get the invocations from zinc and we can emit the proper
>> SystemLogger events into the Log framework.
>> Sven will come up with something announcement based. And that is still a
>> task for us, too. To look where functionality of SystemLogger is doubled
>> with announcements.
>>
>
> We should pay attention that it stays small and simple.
>
>
>
>  first we should integrate it and make sure that all the Transcript show
>>> are funnelled to the Log frameworks.
>>>
>>
>> Yes. Maybe we need to sync our understanding of log levels first. The
>> exchange adds a log level and adding a tag would be good, too.
>>
>
> I do not get it but this is not a problem. No need to reply.
>
>
>  - Split the Log class

>>>
>>> we will not split it because we iterated over the design since 8 months
>>> with norbert :)
>>>
>>
>> I cannot find the proposals of Doru. But I’m interested. I splitted the
>> Log class already into BasicLog and Log. I’m not fully satisfied with it so
>> … My concern about the Log class is more how get it right supporting
>> different kind of Log classes and still have a working filtering in the
>> Logger. But that we can discuss in the groups that form I guess
>>
> I would like to stop iterating. And again we should keep the system small.
> I studied all the logger framework available and I think that we can look
> for the graal forever or get done and I want to get done
> because there are other many many topics that can get fixed.
> Right now we went from 0% to 80% and this is a good ratio. We iterated
> with you. Now I do not want to pass time to go to an hypothetical 85%.
>
>
>
>  - Possibly support Fuel serialization for each log entry

>>> Please go ahead.
>>>
>>
>> Yes. I don’t even understand what it means :)
>>
> Send code!
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Understanding Workspace

I tried ConfigurationOfRubic load, loadDefault and loadDevelopment , they
all fail with an error so I am loading each package manually now.


On Wed, May 21, 2014 at 3:17 PM, kilon alios  wrote:

> Thank you Tudor, thats looks definitely very useful .
>
> I am downloading it now and studying it :)
>
>
> On Wed, May 21, 2014 at 3:10 PM, Tudor Girba  wrote:
>
>> The first suggestion is to not invest in the PluggableTextMorph :)
>>
>> Ideally, we should get the new text widget soon, but in the meantime, you
>> would be better with using Rubric. It is a pragmatic solution developed by
>> Alain Plantec and that works now. This is where we are going with the
>> Glamorous Toolkit at the moment. You find it already in the Moose image, or
>> you can download it from here:
>> http://smalltalkhub.com/#!/~AlainPlantec/Rubric
>>
>> Cheers,
>> Doru
>>
>>
>> On Wed, May 21, 2014 at 12:44 PM, kilon alios wrote:
>>
>>> Hello guys, I have started a new experiment of mine, a tool I call
>>> "Talos". I want Talos to become workspace on steroids.
>>>
>>> The first thing I want to implement is emacs like navigation. With that
>>> I mean keyboard shortcuts for moving inside the text like you can do with
>>> arrow keys already and the ability to move to the next word , the first
>>> character of next word, the last character of next word , previous world,
>>> quickly rename variables and all the great things one can do with emacs and
>>> vim.
>>>
>>> Of course I don't want to do all that at once, one step at a time.
>>>
>>> Now I have take a look at Workspace and it seems that it uses
>>> PlaggableTextMorph , it also looks like I can get the contents via
>>> PluggableTextMorph>>text instance side. The source code returned is also
>>> send to RBParser using the parseBlock method , I think for syntax
>>> highlighting.
>>>
>>> However because the PluggableTextMorph is very big and it does not even
>>> have a class comment, though quite a lot of methods are commented, I am
>>> really open to advice and suggestions on to how to parse the contents and
>>> manipulate the cursor position.
>>>
>>> I know I could use PettitParser but I dont know if there are better
>>> options out there, or maybe I am doing the whole thing wrong.
>>>
>>> So any advice and suggestion is more than welcomed.
>>>
>>
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>>
>
>

[Pharo-dev] [REMINDER] CFP - IWST 2014 - Deadline June, 15

[Please accept our apologies if you receive multiple copies of this call]
[Please send to interested colleagues / mailing-lists]

CALL FOR PAPERS

IWST14 — International Workshop on Smalltalk Technologies

Cambridge, England; August 19, 2014
http://www.esug.org/Conferences/2014/IWST14


---
Goals and scopes
---

The goals of the workshop is to create a forum around advances or
experience in Smalltalk and to trigger discussions and exchanges of ideas.
The topics of your paper can be on all aspect of Smalltalk, theoretical as
well as practical. Participants are invited to submit research articles or
industrial papers. This year we want to open two different tracks: one
research track and one industrial track with less scientific constraints.

We expect papers of three kinds:

Short position papers describing emerging ideas
Long research papers with deeper description of experiments and of research
results.
Industrial papers with presentation of real and innovative Smalltalk
applications; this kind of paper should enlighten why Smalltalk is really
appropriate for your application.
We will not enforce any length restriction.


Important Dates


Submission deadline: June 15, 2014
Notification deadline: July 15, 2014
Workshop : August 19, 2014
All accepted papers will be published in ACM DL (To be confirmed)

---
Topics
---

We welcome contributions on all aspects, theoretical as well as practical,
of Smalltalk related topics such as:

Aspect-oriented programming,
Design patterns,
Experience reports,
Frameworks,
Implementation, new dialects or languages implemented in Smalltalk,
Interaction with other languages,
Meta-programming and Meta-modeling,
Tools

---
Best Paper Award
---

To encourage the submission of high-quality papers, the IWST organizing
committee is very proud to announce a Best Paper Award for this edition of
IWST.

We thank Lam Research Corporation for its financial contribution that makes
it possible a price for the three best papers: 1000 USD for first place,
600 USD for second place and 400 USD for third place.

The ranking will be decided by the program committee during the review
process. The awards will be given during the ESUG conference social event.

The Best Paper Award will take place only with a minimum of six
submissions. Notice also that to be illegible, a paper must be presented at
the workshop by one of the author and that the presenting author must be
registered at the ESUG conference.

---
Publication
---

Both submissions and final papers must be prepared using the ACM SIGPLAN 10
point format. Templates for Word and LaTeX are available at
http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also
contains links to useful informations on how to write effective submissions.

---
Submission
---

All submissions must be sent via easychair:
https://www.easychair.org/conferences/?conf=iwst2014

---
Program chairs
---

Alain Plantec (UMR 6265 Lab-STICC, University of Brest, France)
Jannik Laval (Ecole des Mines de Douai, France)

-- 

~~Jannik Laval~~
École des Mines de Douai
Enseignant-chercheur
http://www.jannik-laval.eu
http://www.phratch.com
http://car.mines-douai.fr/

Re: [Pharo-dev] Call for co-coders

2014-05-21 Thread Norbert Hartl


Am 21.05.2014 um 14:24 schrieb Tudor Girba :

> As it is now, when I execute:
> Log critical: 'message'
> 
> I get an instance of Log. This is confusing, and not needed. We can nicely 
> get an instance of LogEvent. This will not complicate things at all.
> 


Please take Object>>#asLog into account when doing it. 

Norbert

[Pharo-dev] Fixing configurations: XML-Parser

XML-Parser did have breaking tests in Pharo 2, due to the use
of selectorsInCategory:. This method is defined on TClassDescription.
We added a package XML-Pharo2-Parser containing a copy in an
extension method on TClassAndTraitDescription. It might be useful to add to 
Pharo 2.

Diego & Stephan

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

2014-05-21 Thread Esteban A. Maringolo

2014-05-21 7:11 GMT-03:00 stepharo :
> So we should probably remove the software update button.

+1


> Stef
> PS: the last time I updated my iPhone it blocked and I had to fully
> reinstall everything.
> And once when I updated my mac my mouse got blocked forever on the left top
> corner.

You might be one of the lots of unlucky persons that got issues while
updating iOS/MacOS, but sill you probably represent less than the 1%
of the total userbase (of which the rest updated with no issues).

The hard thing here is Pharo tries to update itself while running, it
is like trying to modify a plane while flying.



Esteban A. Maringolo

Re: [Pharo-dev] Understanding Workspace

Indeed, I just noticed that we are also loading the Rubric package directly
in Glamour. This is not good :)

Doru

On Wed, May 21, 2014 at 2:25 PM, kilon alios  wrote:

> I tried ConfigurationOfRubic load, loadDefault and loadDevelopment , they
> all fail with an error so I am loading each package manually now.
>
>
> On Wed, May 21, 2014 at 3:17 PM, kilon alios wrote:
>
>> Thank you Tudor, thats looks definitely very useful .
>>
>> I am downloading it now and studying it :)
>>
>>
>> On Wed, May 21, 2014 at 3:10 PM, Tudor Girba wrote:
>>
>>> The first suggestion is to not invest in the PluggableTextMorph :)
>>>
>>> Ideally, we should get the new text widget soon, but in the meantime,
>>> you would be better with using Rubric. It is a pragmatic solution developed
>>> by Alain Plantec and that works now. This is where we are going with the
>>> Glamorous Toolkit at the moment. You find it already in the Moose image, or
>>> you can download it from here:
>>> http://smalltalkhub.com/#!/~AlainPlantec/Rubric
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On Wed, May 21, 2014 at 12:44 PM, kilon alios wrote:
>>>
 Hello guys, I have started a new experiment of mine, a tool I call
 "Talos". I want Talos to become workspace on steroids.

 The first thing I want to implement is emacs like navigation. With that
 I mean keyboard shortcuts for moving inside the text like you can do with
 arrow keys already and the ability to move to the next word , the first
 character of next word, the last character of next word , previous world,
 quickly rename variables and all the great things one can do with emacs and
 vim.

 Of course I don't want to do all that at once, one step at a time.

 Now I have take a look at Workspace and it seems that it uses
 PlaggableTextMorph , it also looks like I can get the contents via
 PluggableTextMorph>>text instance side. The source code returned is also
 send to RBParser using the parseBlock method , I think for syntax
 highlighting.

 However because the PluggableTextMorph is very big and it does not even
 have a class comment, though quite a lot of methods are commented, I am
 really open to advice and suggestions on to how to parse the contents and
 manipulate the cursor position.

 I know I could use PettitParser but I dont know if there are better
 options out there, or maybe I am doing the whole thing wrong.

 So any advice and suggestion is more than welcomed.

>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Every thing has its own flow"
>>>
>>
>>
>

-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Call for co-coders

2014-05-21 Thread Norbert Hartl


Am 21.05.2014 um 09:05 schrieb stepharo :

> 
 
 As a general matter, I would be interested in:
 - unifying with the ZnLogEvent
>>> 
> SystemLogger is infrastructure low level. So I do not see why Zn and 
> SystemLogger should be unified.
> 
yep

>> If this means talking to Sven this is a definite yes. I don’t think we need 
>> to unify with the current ZnLogEvent. Syncing with zinc is probably not the 
>> way to go anyway. Zinc is still an external framework (hence the namespace 
>> prefix). I did a zinc bridge which operates an a single event bridging from 
>> zinc to SystemLogger. This is not clever performance wise. A better approach 
>> is to plug into zincs LogSupport. We should hook into there so we just get 
>> the invocations from zinc and we can emit the proper SystemLogger events 
>> into the Log framework.
>> Sven will come up with something announcement based. And that is still a 
>> task for us, too. To look where functionality of SystemLogger is doubled 
>> with announcements.
> 
> We should pay attention that it stays small and simple.
> 
It is and will be an extra anyway. You load zinc, you load SystemLogger, you 
load the glue code between them. Nothing to bloat the core.

> 
>>> first we should integrate it and make sure that all the Transcript show are 
>>> funnelled to the Log frameworks.
>> 
>> Yes. Maybe we need to sync our understanding of log levels first. The 
>> exchange adds a log level and adding a tag would be good, too.
> 
> I do not get it but this is not a problem. No need to reply.

The Log as it is at the moment contains log level and a tag. Going from a 
simple logCr: you have to add a log level. Not everything will be debug/trace. 
With the tag I meant the tag of the Log class. This is a first-class citizen 
for categorizing and should be something like „image“ or even better the name 
of the sub-system that emitted the message. Clear now?

Norbert

> 
 - Split the Log class
>>> 
>>> we will not split it because we iterated over the design since 8 months 
>>> with norbert :)
>> 
>> I cannot find the proposals of Doru. But I’m interested. I splitted the Log 
>> class already into BasicLog and Log. I’m not fully satisfied with it so … My 
>> concern about the Log class is more how get it right supporting different 
>> kind of Log classes and still have a working filtering in the Logger. But 
>> that we can discuss in the groups that form I guess
> I would like to stop iterating. And again we should keep the system small.
> I studied all the logger framework available and I think that we can look for 
> the graal forever or get done and I want to get done
> because there are other many many topics that can get fixed.
> Right now we went from 0% to 80% and this is a good ratio. We iterated with 
> you. Now I do not want to pass time to go to an hypothetical 85%.
> 
> 
 - Possibly support Fuel serialization for each log entry
>>> Please go ahead.
>> 
>> Yes. I don’t even understand what it means :)
> Send code!
> 
>

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

2014-05-21 Thread Guillermo Polito

But not also... Because right now the way changes are integrated is using
the same update mechanism if I'm not mistaken.

The very challenge of the update is that you are updating your image, which
has your objects, and your changes!

So, what if you made some changes in the core classes? update may fail on
merge or even remove your changes. If you keep your method you may lose a
bugfix
If there was a rename of that method you changed? what should the update do?
If you configured some shortcuts? the update may reset them
The changesets? they may be reset
And the list goes on...

On Wed, May 21, 2014 at 2:49 PM, Esteban A. Maringolo
wrote:

> 2014-05-21 7:11 GMT-03:00 stepharo :
> > So we should probably remove the software update button.
>
> +1
>
>
> > Stef
> > PS: the last time I updated my iPhone it blocked and I had to fully
> > reinstall everything.
> > And once when I updated my mac my mouse got blocked forever on the left
> top
> > corner.
>
> You might be one of the lots of unlucky persons that got issues while
> updating iOS/MacOS, but sill you probably represent less than the 1%
> of the total userbase (of which the rest updated with no issues).
>
> The hard thing here is Pharo tries to update itself while running, it
> is like trying to modify a plane while flying.
>
>
>
> Esteban A. Maringolo
>
>

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

what if updater becomes a separate application that operates on an image
without loading it. So in an update Pharo would save the image, close
itself, open the updater application which will perform the update and the
updater reopen Pharo loading the same image  ?


On Wed, May 21, 2014 at 3:59 PM, Guillermo Polito  wrote:

> But not also... Because right now the way changes are integrated is using
> the same update mechanism if I'm not mistaken.
>
> The very challenge of the update is that you are updating your image,
> which has your objects, and your changes!
>
> So, what if you made some changes in the core classes? update may fail on
> merge or even remove your changes. If you keep your method you may lose a
> bugfix
> If there was a rename of that method you changed? what should the update
> do?
> If you configured some shortcuts? the update may reset them
> The changesets? they may be reset
> And the list goes on...
>
>
> On Wed, May 21, 2014 at 2:49 PM, Esteban A. Maringolo <
> emaring...@gmail.com> wrote:
>
>> 2014-05-21 7:11 GMT-03:00 stepharo :
>> > So we should probably remove the software update button.
>>
>> +1
>>
>>
>> > Stef
>> > PS: the last time I updated my iPhone it blocked and I had to fully
>> > reinstall everything.
>> > And once when I updated my mac my mouse got blocked forever on the left
>> top
>> > corner.
>>
>> You might be one of the lots of unlucky persons that got issues while
>> updating iOS/MacOS, but sill you probably represent less than the 1%
>> of the total userbase (of which the rest updated with no issues).
>>
>> The hard thing here is Pharo tries to update itself while running, it
>> is like trying to modify a plane while flying.
>>
>>
>>
>> Esteban A. Maringolo
>>
>>
>

Re: [Pharo-dev] Call for co-coders

I started to write to files with roadmaps so that other people can work 
with me :).


https://github.com/pharo-project/pharo-workingRoadmaps

Nicola Heiss should prepare one or two on cleaning Nautilus, Theme, and 
or KeyMappings


Stef

Re: [Pharo-dev] Making screenshots programmatically for book


Stephan Eggermont wrote:

This code allows me to generate some screenshots.
The exporter deletes the old picture, if it exists.

|directory exporter window bounds |
directory := FileSystem workingDirectory / 'pictures' .
directory ensureCreateDirectory.
exporter := DOScreenshotExporter new.
exporter directory: directory.
exporter writeWorldAs: 'world.png'.
window := DOPartiesList new openWithSpec window.
exporter writeMorph: window value as: 'PartiesList.png'.
bounds := window fullBounds.
exporter writeMorph: window value rectangle: (bounds insetBy: 20@20) as: 
'PartOfPartiesList.png'.
window close.
  

Now what is the best way to associate such code with a Pillar source file.
1. Put screenshot generation script inline?
2. Put screenshot generation script in a separate file with same 
basename as the produced bitmap file?

  2a. Have a command line handler to manually invoke snapshot generation?
  2b. Have a Pillar notation that references the script rather than the 
produced file, and generate snapshot each time? (maybe good for CI, but 
slows user down)


cheers -ben

[Pharo-dev] NativeBoost and WKHTML

2014-05-21 Thread Torsten Bergmann

Sven wrote:
>Just out of curiosity, why not use Artefact, 
>https://sites.google.com/site/artefactpdf ?
>
>I haven't looked at the different approaches, but I have this natural tendency 
>against native >libraries, >if we can do it directly in Pharo. That is why I 
>am asking: why this road and not the other >?

Short Answer:  So you know the usual "Pharo does not yet rule the world" and 
the usual "designers do not 
   yet code in Smalltalk" discussion ;) 

Long Answer:

You half-way answered yourself "if we can do it directly in Pharo ..." which 
could be answered 
with "not yet out of the box".

It's not that I dislike the Artefact "Smalltalk only" approach. In fact I have 
contributed also to 
this project (cleaned and refactored it) and use it for simple stuff.
Still there are some small issues remaining (no support to embedd fonts, etc). 
Also there is 
no "visual template editor" - so currently you have to "code your layout".

So very often using HTML and CSS for an easy and good looking print is much 
better 
and easier to do than manually code each box, line, text manually. Also there 
are tons 
of visual HTML Editors, HTML is easy to generate and CSS allows you to style. 
If you work with Seaside then you also already have the HTML.

So far there is no HTML/CSS to Artfeact project and it would not be easy to 
reimplement
such a beast (if done for all possible cases).
WKHTML uses the  QT Webkit rendering engine and we do not have to reinvent the 
wheel.

I fully understand that the native library is not as portable as a ST only 
solution
but we already provide and use Cairo, Freetype and others with the default 
Pharo release. 

WKHTML is LGPL so if I understand correctly there is no conflict in using and
redistributing.

Bye
T.

Re: [Pharo-dev] Pharo in Rasbian ?

2014-05-21 Thread Clément Bera

2014-05-20 17:06 GMT+02:00 Clément Bera :

> 2014-05-20 16:23 GMT+02:00 Juan :
>
> Jannik
>>
>>
>> the phratch proyect  provides  access to GPIO port?
>>  ffi to achieve such access is available?
>> any ideas?
>>
>
> FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago.
>

Sorry as JB pointed me out, the FFI for the Raspberry Pie is working, but
is not integrated into the Pharo VM yet.

>
> So I guess the Phratch team has not found the time yet to do that, but it
> should be possible.
>
>
>> thanks in advance
>> best
>>
>> jmdc
>>
>>
>> On Tue, May 20, 2014 at 10:36 AM, jannik laval wrote:
>>
>>> Hi,
>>>
>>> Probably he does not know phratch for Rasberry-Pi:
>>> https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick-RPi/
>>>
>>> Cheers :)
>>>
>>>
>>> 2014-05-20 15:32 GMT+02:00 Alexandre Bergel :
>>>
>>> Hi!

 A friend of mine recently bought a Raspberry pi and installed Rasbian,
 a Debian-like OS for Raspberry. Squeak and Scratch are installed per
 default. There is room to fill here...


 Cheers,
 Alexandre
 --
 _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
 Alexandre Bergel  http://www.bergel.eu
 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




>>>
>>>
>>> --
>>>
>>> ~~Jannik Laval~~
>>> École des Mines de Douai
>>> Enseignant-chercheur
>>> http://www.jannik-laval.eu
>>> http://www.phratch.com
>>> http://car.mines-douai.fr/
>>>
>>
>>
>

Re: [Pharo-dev] Making screenshots programmatically for book

Ben Coman wrote:

Stephan Eggermont wrote:

This code allows me to generate some screenshots.
The exporter deletes the old picture, if it exists.

|directory exporter window bounds |
directory := FileSystem workingDirectory / 'pictures' .
directory ensureCreateDirectory.
exporter := DOScreenshotExporter new.
exporter directory: directory.
exporter writeWorldAs: 'world.png'.
window := DOPartiesList new openWithSpec window.
exporter writeMorph: window value as: 'PartiesList.png'.
bounds := window fullBounds.
exporter writeMorph: window value rectangle: (bounds insetBy: 20@20)
as: 'PartOfPartiesList.png'.

window close.

Now what is the best way to associate such code with a Pillar source
file.

1. Put screenshot generation script inline?
2. Put screenshot generation script in a separate file with same
basename as the produced bitmap file?

2a. Have a command line handler to manually invoke snapshot generation?
2b. Have a Pillar notation that references the script rather than
the produced file, and generate snapshot each time? (maybe good for
CI, but slows user down)

cheers -ben

Thinking further on this, it could be useful when Pillar processes a
source file to mark code to be executed in the image running Pillar.
For instance when the reader is asked to do something, sometimes a
snapshot taken manually might be done out of order and something
not-yet-done (in the sequence of the tutorial) slips into the snapshot.
For example, if the reader is asked to add a class, Pillar source might
hypothetically look like this...

[[[
Object subclass: #BlankCell
instanceVariableNames: ''
classVariableNames: ''
category: 'LaserGame-Model'
]]] executeInImage
+First class
created>generateFrom://figures/firstClass.st>file://figures/firstClass.png|width=50|label=firstClass+

This would ensure the snapshots a synchronised with the narrative.

That is how it might work for code blocks that are shown in the
narrative, but you might also want to be able to execute support code in
the background. Probably you would want to save the image to a new file
to avoid accidentally corrupting the Pillar program.

This is not something I'd want to play with right now, but just
interested in feedback while its fresh in my mind.

cheers -ben

Re: [Pharo-dev] a Pharo talk from a ruby conference





Hilaire Fernandes wrote:

  Once, when I told an old friend I was doing Smalltalk, he asked me "Are
you doing computer archeology?" It is difficult to fight this.

Hilaire

Le 15/05/2014 22:09, Sergi Reyner a écrit :
  
  
"Pharo is a Smalltalk for the 21st century." - Sergi Reyner.

Cheers,
Sergi

  
  
  

Maybe the marketing needs some "Why Smalltalk is new again..."

Re: [Pharo-dev] Roassal2 starting point

2014-05-21 Thread Alexandre Bergel

Hi Uko,

Roassal2 has not been officially announced and released. The reason is simple: 
Roassal2 targets an audience larger than the Pharo/VW/Amber communities. We 
would love to see Journalists, Data scientists, Artists, Educators and software 
engineers enjoying our tools. However, we have to be ready to expose Roassal2 
to the World. There are many missing pieces: the font problem has to be solved, 
we need for a proper documentation, need more sexy examples, nicer integration 
on the web…

Roassal2 is largely compatible with Roassal1. However, you probably want to do 
some significant rewriting to benefit from all the cool animations, color 
fading, fancy interactions, and much more.

We do not have much documentation so far. It will soon come. A book is 
currently being written (by the way, I am looking to see the effort of Pillar).

A large Chilean crew will be present at esug to demonstrate Roassal2 with 
fireworks and trumpets. 

Cheers,
Alexandre

On May 21, 2014, at 5:31 AM, Yuriy Tymchuk  wrote:

> Hi everyone. Is Roassal2 released? I guess is was already integrated into 
> Moose, and from time to time I see amazing pictures and video on 
> Twitter/Facebook. But is there any new guide? Or changes list from Roassal1?
> 
> Cheers.
> Uko

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] Pharo in Rasbian ?

2014-05-21 Thread Alexandre Bergel

> So, before proposing it, we need to make it more stable, and cleaner.

Sure! I am just suspecting there is a great opportunity for a larger adoption 
of our tools

Alexandre

> 
> Cheers,
> Jannik
> 
> 
> 2014-05-20 17:43 GMT+02:00 Alexandre Bergel :
> Ah okay, this is an answer that I understand :-)
> 
> We are not really good at promoting what we are doing.
> For the the case of  Rasbian, it seems not that difficult to have Phratch and 
> Pharo installed per default, if there is Scratch and Squeak.
> 
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
> On May 20, 2014, at 11:06 AM, Clément Bera  wrote:
> 
> > FFI for the raspberry pie was finished for the Pharo vm 3 weeks ago.
> >
> > So I guess the Phratch team has not found the time yet to do that, but it 
> > should be possible.
> >
> 
> 
> 
> 
> 
> -- 
> ~~Jannik Laval~~
> École des Mines de Douai
> Enseignant-chercheur
> http://www.jannik-laval.eu
> http://www.phratch.com
> http://car.mines-douai.fr/
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

[Pharo-dev] Coral is green

PetitParser 1.6 instead of 1.5.
Tests only work when no Nautilus browser is open. Some notification problem 
when creating classes. 

OSProcess ci has lots of failing tests, so we don't know if it actually works…

Diego & Stephan

Verstuurd vanaf mijn iPhone

[Pharo-dev] Installing Rubric

Besides the reported problem of configurationsOfRubic not working as every
class method returns an error I have also a problem with
RubicTextAreaDecoratorExample package that seems to missing some
dependencies and it particular

"This package depends on the following classes:
  PPCompositeParser
You must resolve these dependencies before you will be able to load these
definitions:
  RbEPersonColorizer
  parseAndShowInAWorkspace
  attribute
  attributeList
  attributeValue
  blanks
  identifier
  person
  personKW
  registry
  start ''

Also I tried the RubTextFieldExample open, it creates the text field and I
can put text inside it but if I press ESC it sends a MNU:
RubTextFieldExample>>menu. Right clicking too sends the same messages as
well .

Re: [Pharo-dev] Installing Rubric

You'll probably be happier loading #development of ConfigurationOfGlamour, and 
you might want to add ConfigurationOfPetitParser. I'll take a look at the 
configuration of Rubric

Stephan

Verstuurd vanaf mijn iPhone

Re: [Pharo-dev] Installing Rubric

no that does not work either I am getting dependancies warning as well

this (taken from
http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
)

Gofer new
smalltalkhubUser: 'Moose' project: 'PetitParser';
package: 'ConfigurationOfPetitParser';
load.

(Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.

gives me this :

"This package depends on the following classes:
  GLMHighlighterTextDecorator
You must resolve these dependencies before you will be able to load these
definitions:
  GLMPersonStyler
  key
  parser

Select Proceed to continue, or close this window to cancel the operation."

and this :

Gofer new
  smalltalkhubUser: 'Moose' project: 'Glamour';
  package: 'ConfigurationOfGlamour';
  load.
(Smalltalk at: #ConfigurationOfGlamour)
  perform: #loadDevelopment.

gives me same dependencies missing.

On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont  wrote:

> You'll probably be happier loading #development of ConfigurationOfGlamour,
> and you might want to add ConfigurationOfPetitParser. I'll take a look at
> the configuration of Rubric
>
> Stephan
>
> Verstuurd vanaf mijn iPhone
>

Re: [Pharo-dev] Installing Rubric

2014-05-21 Thread Andrei Chis

Seems that I placed some classes in the wrong packages.
Give it another try.

Cheers,
Andrei


On Wed, May 21, 2014 at 5:26 PM, kilon alios  wrote:

> no that does not work either I am getting dependancies warning as well
>
> this (taken from
> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
> )
>
> Gofer new
> smalltalkhubUser: 'Moose' project: 'PetitParser';
> package: 'ConfigurationOfPetitParser';
> load.
>
> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
>
> gives me this :
>
> "This package depends on the following classes:
>   GLMHighlighterTextDecorator
> You must resolve these dependencies before you will be able to load these
> definitions:
>   GLMPersonStyler
>   key
>   parser
>
>
> Select Proceed to continue, or close this window to cancel the operation."
>
> and this :
>
> Gofer new
>   smalltalkhubUser: 'Moose' project: 'Glamour';
>   package: 'ConfigurationOfGlamour';
>   load.
> (Smalltalk at: #ConfigurationOfGlamour)
>   perform: #loadDevelopment.
>
> gives me same dependencies missing.
>
>
>
>
> On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont wrote:
>
>> You'll probably be happier loading #development of
>> ConfigurationOfGlamour, and you might want to add
>> ConfigurationOfPetitParser. I'll take a look at the configuration of Rubric
>>
>> Stephan
>>
>> Verstuurd vanaf mijn iPhone
>>
>
>

Re: [Pharo-dev] Making screenshots programmatically for book

I haven't given the way to integrate this in the Pillar workflow enough 
thought. I need new pictures when:
- I don't have any yet;
- Possibly when the text changed;
- When the image changed;
- With a different UITheme.

For web applications, I need to integrate with something like Selenium 
Webdriver to get browser screenshots

Stephan

Verstuurd vanaf mijn iPhone

Re: [Pharo-dev] Installing Rubric

2014-05-21 Thread Andrei Chis

Now you should also be able to load Rubric through its configuration.
I also updated Glamour to load Rubric through the configuration instead of
directly loading the package.


Cheers,
Andrei


On Wed, May 21, 2014 at 5:38 PM, Andrei Chis wrote:

> Seems that I placed some classes in the wrong packages.
> Give it another try.
>
> Cheers,
> Andrei
>
>
>
> On Wed, May 21, 2014 at 5:26 PM, kilon alios wrote:
>
>> no that does not work either I am getting dependancies warning as well
>>
>> this (taken from
>> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
>> )
>>
>> Gofer new
>> smalltalkhubUser: 'Moose' project: 'PetitParser';
>> package: 'ConfigurationOfPetitParser';
>> load.
>>
>> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
>>
>> gives me this :
>>
>> "This package depends on the following classes:
>>   GLMHighlighterTextDecorator
>> You must resolve these dependencies before you will be able to load these
>> definitions:
>>   GLMPersonStyler
>>   key
>>   parser
>>
>>
>> Select Proceed to continue, or close this window to cancel the operation."
>>
>> and this :
>>
>> Gofer new
>>   smalltalkhubUser: 'Moose' project: 'Glamour';
>>   package: 'ConfigurationOfGlamour';
>>   load.
>> (Smalltalk at: #ConfigurationOfGlamour)
>>   perform: #loadDevelopment.
>>
>> gives me same dependencies missing.
>>
>>
>>
>>
>> On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont wrote:
>>
>>> You'll probably be happier loading #development of
>>> ConfigurationOfGlamour, and you might want to add
>>> ConfigurationOfPetitParser. I'll take a look at the configuration of Rubric
>>>
>>> Stephan
>>>
>>> Verstuurd vanaf mijn iPhone
>>>
>>
>>
>

Re: [Pharo-dev] Pharo in Rasbian ?

2014-05-21 Thread Chris Muller

One reason might be that Phratch is kind of redundant isn't it?
Smalltalk already has a foothold on the Pi in the form of Squeak, and
Tim Rowledge is being paid by that organization right now to improve
Scratch.  So if you're interested in helping kids learn programming
with Scratch, why not check with Tim see if you can find a way help
with what he's doing..?

On Tue, May 20, 2014 at 10:41 AM, Alexandre Bergel
 wrote:
> Hi!
>
> My point was the following: why Phratch is not included in the default 
> setting of Rasbian?
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> On May 20, 2014, at 9:36 AM, jannik laval  wrote:
>
>> Hi,
>>
>> Probably he does not know phratch for Rasberry-Pi: 
>> https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick-RPi/
>>
>> Cheers :)
>>
>>
>> 2014-05-20 15:32 GMT+02:00 Alexandre Bergel :
>> Hi!
>>
>> A friend of mine recently bought a Raspberry pi and installed Rasbian, a 
>> Debian-like OS for Raspberry. Squeak and Scratch are installed per default. 
>> There is room to fill here...
>>
>> 
>>
>> Cheers,
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> --
>> ~~Jannik Laval~~
>> École des Mines de Douai
>> Enseignant-chercheur
>> http://www.jannik-laval.eu
>> http://www.phratch.com
>> http://car.mines-douai.fr/
>>
>
>

Re: [Pharo-dev] Installing Rubric

yeah it looks fine now, thank you Andrei :)


On Wed, May 21, 2014 at 7:05 PM, Andrei Chis wrote:

> Now you should also be able to load Rubric through its configuration.
> I also updated Glamour to load Rubric through the configuration instead of
> directly loading the package.
>
>
> Cheers,
> Andrei
>
>
> On Wed, May 21, 2014 at 5:38 PM, Andrei Chis 
> wrote:
>
>> Seems that I placed some classes in the wrong packages.
>> Give it another try.
>>
>> Cheers,
>> Andrei
>>
>>
>>
>> On Wed, May 21, 2014 at 5:26 PM, kilon alios wrote:
>>
>>> no that does not work either I am getting dependancies warning as well
>>>
>>> this (taken from
>>> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
>>> )
>>>
>>> Gofer new
>>> smalltalkhubUser: 'Moose' project: 'PetitParser';
>>> package: 'ConfigurationOfPetitParser';
>>> load.
>>>
>>> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
>>>
>>> gives me this :
>>>
>>> "This package depends on the following classes:
>>>   GLMHighlighterTextDecorator
>>> You must resolve these dependencies before you will be able to load
>>> these definitions:
>>>   GLMPersonStyler
>>>   key
>>>   parser
>>>
>>>
>>> Select Proceed to continue, or close this window to cancel the
>>> operation."
>>>
>>> and this :
>>>
>>> Gofer new
>>>   smalltalkhubUser: 'Moose' project: 'Glamour';
>>>   package: 'ConfigurationOfGlamour';
>>>   load.
>>> (Smalltalk at: #ConfigurationOfGlamour)
>>>   perform: #loadDevelopment.
>>>
>>> gives me same dependencies missing.
>>>
>>>
>>>
>>>
>>> On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont wrote:
>>>
 You'll probably be happier loading #development of
 ConfigurationOfGlamour, and you might want to add
 ConfigurationOfPetitParser. I'll take a look at the configuration of Rubric

 Stephan

 Verstuurd vanaf mijn iPhone

>>>
>>>
>>
>

Re: [Pharo-dev] Installing Rubric

hmm weird now I am getting this warning with both installs

This package depends on the following classes:
  GLMRubricTextPresentation
You must resolve these dependencies before you will be able to load these
definitions:
  GLMNewSmalltalkCodePresentation
  compileTextIn:from:
  debugSelection
  defaultSelectionActions
  evaluateSelection
  evaluateSelectionAndDo:
  installDefaultSelectionActions
  printSelection
  profileSelection
  GLMPharoMethodPresentation
  highlightSmalltalkContext
  renderGlamorouslyOn:
  smalltalkClass:
  GLMPharoPlaygroundPresentation
  renderGlamorouslyOn:
  updateVariableBindings
  variableBindings
  variableBindings:


On Wed, May 21, 2014 at 7:12 PM, kilon alios  wrote:

> yeah it looks fine now, thank you Andrei :)
>
>
> On Wed, May 21, 2014 at 7:05 PM, Andrei Chis 
> wrote:
>
>> Now you should also be able to load Rubric through its configuration.
>> I also updated Glamour to load Rubric through the configuration instead
>> of directly loading the package.
>>
>>
>> Cheers,
>> Andrei
>>
>>
>> On Wed, May 21, 2014 at 5:38 PM, Andrei Chis 
>> wrote:
>>
>>> Seems that I placed some classes in the wrong packages.
>>> Give it another try.
>>>
>>> Cheers,
>>> Andrei
>>>
>>>
>>>
>>> On Wed, May 21, 2014 at 5:26 PM, kilon alios wrote:
>>>
 no that does not work either I am getting dependancies warning as well

 this (taken from
 http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
 )

 Gofer new
 smalltalkhubUser: 'Moose' project: 'PetitParser';
 package: 'ConfigurationOfPetitParser';
 load.

 (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.

 gives me this :

 "This package depends on the following classes:
   GLMHighlighterTextDecorator
 You must resolve these dependencies before you will be able to load
 these definitions:
   GLMPersonStyler
   key
   parser


 Select Proceed to continue, or close this window to cancel the
 operation."

 and this :

 Gofer new
   smalltalkhubUser: 'Moose' project: 'Glamour';
   package: 'ConfigurationOfGlamour';
   load.
 (Smalltalk at: #ConfigurationOfGlamour)
   perform: #loadDevelopment.

 gives me same dependencies missing.




 On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont wrote:

> You'll probably be happier loading #development of
> ConfigurationOfGlamour, and you might want to add
> ConfigurationOfPetitParser. I'll take a look at the configuration of 
> Rubric
>
> Stephan
>
> Verstuurd vanaf mijn iPhone
>


>>>
>>
>

Re: [Pharo-dev] Pharo in Rasbian ?

Hi Chris

2014-05-21 18:11 GMT+02:00 Chris Muller :

> One reason might be that Phratch is kind of redundant isn't it?
>

For sure, not !

> Smalltalk already has a foothold on the Pi in the form of Squeak, and
> Tim Rowledge is being paid by that organization right now to improve
> Scratch.  So if you're interested in helping kids learn programming
> with Scratch, why not check with Tim see if you can find a way help
> with what he's doing..?
>

Yes, we already discussed about that with Tim.
Our goal is not the same.
I don't want to say something wrong, but Tim want to do Scratch on a recent
Squeak, then including BYOB. He is working hard to integrate it on RPi.
Phratch is something different: it is based on Scratch, but the goal is to
be as much extendable as possible. For example, I use it for robotics. This
is not possible in Scratch. Yes there is Enchanting, but it is based on a
plugin if I understood well.
Another goal is to access to Smalltalk code. As a good learning language, I
think that using phratch should help developers to learn smalltalk, which
is not a goal of Scratch.

So, as I said, we already discussed with Tim, and I am sure we will reuse
our work. If I remember, Tim already has a look at phratch source code. For
my part, if Tim do plugins that work on RPi, I will probably use them.
And I hope to meet Tim at ESUG if he will come to discuss about all of that.

Cheers,
Jannik

>
> On Tue, May 20, 2014 at 10:41 AM, Alexandre Bergel
>  wrote:
> > Hi!
> >
> > My point was the following: why Phratch is not included in the default
> setting of Rasbian?
> >
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> > On May 20, 2014, at 9:36 AM, jannik laval 
> wrote:
> >
> >> Hi,
> >>
> >> Probably he does not know phratch for Rasberry-Pi:
> https://ci.inria.fr/pharo-contribution/view/Phratch/job/Phratch-OneClick-RPi/
> >>
> >> Cheers :)
> >>
> >>
> >> 2014-05-20 15:32 GMT+02:00 Alexandre Bergel :
> >> Hi!
> >>
> >> A friend of mine recently bought a Raspberry pi and installed Rasbian,
> a Debian-like OS for Raspberry. Squeak and Scratch are installed per
> default. There is room to fill here...
> >>
> >> 
> >>
> >> Cheers,
> >> Alexandre
> >> --
> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> >> Alexandre Bergel  http://www.bergel.eu
> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> ~~Jannik Laval~~
> >> École des Mines de Douai
> >> Enseignant-chercheur
> >> http://www.jannik-laval.eu
> >> http://www.phratch.com
> >> http://car.mines-douai.fr/
> >>
> >
> >
>
>

-- 

~~Jannik Laval~~
École des Mines de Douai
Enseignant-chercheur
http://www.jannik-laval.eu
http://www.phratch.com
http://car.mines-douai.fr/

Re: [Pharo-dev] Call for co-coders

2014-05-21 Thread Juraj Kubelka

Hi Stef,

this is great. I would like to participate on fonts, because I want to 
understand how it works. I have just read 
https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/CleaningFontRoadmap.md

FT means FreeType? Thanks.
There is a lot of issues. Where do you recommend to start?

Cheers,
Juraj

El 19-05-2014, a las 3:10, stepharo  escribió:

> Hi guys
> 
> This is a call for some of you that committed code and would like to do it 
> with me :).
> I have some projects that I would like to push further in 4.0 and I'm 
> thinking that
> he could be much more fun to do it with other people.
> 
> Here are some topics
>- integrating the systemLogger
>- integrating/improving the new method categorizer
>- cleaning fonts
>- ...
> 
> How this could work?
> We could have
>- some discussions
>- make a little roadmap
>- then we could work on the same slice and do code review
> 
> I think that it can be fun and motivating. So let me know because I would 
> like to have more social
> coding.
> 
> Stef
>

Re: [Pharo-dev] Installing Rubric

On the other hand ConfigurationOfRubic seems to work now :)


On Wed, May 21, 2014 at 7:19 PM, kilon alios  wrote:

> hmm weird now I am getting this warning with both installs
>
> This package depends on the following classes:
>   GLMRubricTextPresentation
> You must resolve these dependencies before you will be able to load these
> definitions:
>   GLMNewSmalltalkCodePresentation
>   compileTextIn:from:
>   debugSelection
>   defaultSelectionActions
>   evaluateSelection
>   evaluateSelectionAndDo:
>   installDefaultSelectionActions
>   printSelection
>   profileSelection
>   GLMPharoMethodPresentation
>   highlightSmalltalkContext
>   renderGlamorouslyOn:
>   smalltalkClass:
>   GLMPharoPlaygroundPresentation
>   renderGlamorouslyOn:
>   updateVariableBindings
>   variableBindings
>   variableBindings:
>
>
> On Wed, May 21, 2014 at 7:12 PM, kilon alios wrote:
>
>> yeah it looks fine now, thank you Andrei :)
>>
>>
>> On Wed, May 21, 2014 at 7:05 PM, Andrei Chis 
>> wrote:
>>
>>> Now you should also be able to load Rubric through its configuration.
>>> I also updated Glamour to load Rubric through the configuration instead
>>> of directly loading the package.
>>>
>>>
>>> Cheers,
>>> Andrei
>>>
>>>
>>> On Wed, May 21, 2014 at 5:38 PM, Andrei Chis >> > wrote:
>>>
 Seems that I placed some classes in the wrong packages.
 Give it another try.

 Cheers,
 Andrei



 On Wed, May 21, 2014 at 5:26 PM, kilon alios wrote:

> no that does not work either I am getting dependancies warning as well
>
> this (taken from
> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
> )
>
> Gofer new
> smalltalkhubUser: 'Moose' project: 'PetitParser';
> package: 'ConfigurationOfPetitParser';
> load.
>
> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
>
> gives me this :
>
> "This package depends on the following classes:
>   GLMHighlighterTextDecorator
> You must resolve these dependencies before you will be able to load
> these definitions:
>   GLMPersonStyler
>   key
>   parser
>
>
> Select Proceed to continue, or close this window to cancel the
> operation."
>
> and this :
>
> Gofer new
>   smalltalkhubUser: 'Moose' project: 'Glamour';
>   package: 'ConfigurationOfGlamour';
>   load.
> (Smalltalk at: #ConfigurationOfGlamour)
>   perform: #loadDevelopment.
>
> gives me same dependencies missing.
>
>
>
>
> On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont 
> wrote:
>
>> You'll probably be happier loading #development of
>> ConfigurationOfGlamour, and you might want to add
>> ConfigurationOfPetitParser. I'll take a look at the configuration of 
>> Rubric
>>
>> Stephan
>>
>> Verstuurd vanaf mijn iPhone
>>
>
>

>>>
>>
>

Re: [Pharo-dev] Installing Rubric

2014-05-21 Thread Andrei Chis

Now also Glamour should load without any of the previous warnings.


On Wed, May 21, 2014 at 7:21 PM, kilon alios  wrote:

> On the other hand ConfigurationOfRubic seems to work now :)
>
>
> On Wed, May 21, 2014 at 7:19 PM, kilon alios wrote:
>
>> hmm weird now I am getting this warning with both installs
>>
>> This package depends on the following classes:
>>   GLMRubricTextPresentation
>> You must resolve these dependencies before you will be able to load these
>> definitions:
>>   GLMNewSmalltalkCodePresentation
>>   compileTextIn:from:
>>   debugSelection
>>   defaultSelectionActions
>>   evaluateSelection
>>   evaluateSelectionAndDo:
>>   installDefaultSelectionActions
>>   printSelection
>>   profileSelection
>>   GLMPharoMethodPresentation
>>   highlightSmalltalkContext
>>   renderGlamorouslyOn:
>>   smalltalkClass:
>>   GLMPharoPlaygroundPresentation
>>   renderGlamorouslyOn:
>>   updateVariableBindings
>>   variableBindings
>>   variableBindings:
>>
>>
>> On Wed, May 21, 2014 at 7:12 PM, kilon alios wrote:
>>
>>> yeah it looks fine now, thank you Andrei :)
>>>
>>>
>>> On Wed, May 21, 2014 at 7:05 PM, Andrei Chis >> > wrote:
>>>
 Now you should also be able to load Rubric through its configuration.
 I also updated Glamour to load Rubric through the configuration instead
 of directly loading the package.


 Cheers,
 Andrei


 On Wed, May 21, 2014 at 5:38 PM, Andrei Chis <
 chisvasileand...@gmail.com> wrote:

> Seems that I placed some classes in the wrong packages.
> Give it another try.
>
> Cheers,
> Andrei
>
>
>
> On Wed, May 21, 2014 at 5:26 PM, kilon alios wrote:
>
>> no that does not work either I am getting dependancies warning as
>> well
>>
>> this (taken from
>> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
>> )
>>
>> Gofer new
>> smalltalkhubUser: 'Moose' project: 'PetitParser';
>> package: 'ConfigurationOfPetitParser';
>> load.
>>
>> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
>>
>> gives me this :
>>
>> "This package depends on the following classes:
>>   GLMHighlighterTextDecorator
>> You must resolve these dependencies before you will be able to load
>> these definitions:
>>   GLMPersonStyler
>>   key
>>   parser
>>
>>
>> Select Proceed to continue, or close this window to cancel the
>> operation."
>>
>> and this :
>>
>> Gofer new
>>   smalltalkhubUser: 'Moose' project: 'Glamour';
>>   package: 'ConfigurationOfGlamour';
>>   load.
>> (Smalltalk at: #ConfigurationOfGlamour)
>>   perform: #loadDevelopment.
>>
>> gives me same dependencies missing.
>>
>>
>>
>>
>> On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont 
>> wrote:
>>
>>> You'll probably be happier loading #development of
>>> ConfigurationOfGlamour, and you might want to add
>>> ConfigurationOfPetitParser. I'll take a look at the configuration of 
>>> Rubric
>>>
>>> Stephan
>>>
>>> Verstuurd vanaf mijn iPhone
>>>
>>
>>
>

>>>
>>
>

Re: [Pharo-dev] Installing Rubric

yeah all three configurations work now , Rubric , Glamour and Pettit. Great
work Andrei, keep rocking :)

PS: I am amazed the amount of stuff it loaded. What you guys feed those
things ? Tons of code to study. Oh boy :D


On Wed, May 21, 2014 at 8:49 PM, Andrei Chis wrote:

> Now also Glamour should load without any of the previous warnings.
>
>
> On Wed, May 21, 2014 at 7:21 PM, kilon alios wrote:
>
>> On the other hand ConfigurationOfRubic seems to work now :)
>>
>>
>> On Wed, May 21, 2014 at 7:19 PM, kilon alios wrote:
>>
>>> hmm weird now I am getting this warning with both installs
>>>
>>> This package depends on the following classes:
>>>   GLMRubricTextPresentation
>>> You must resolve these dependencies before you will be able to load
>>> these definitions:
>>>   GLMNewSmalltalkCodePresentation
>>>   compileTextIn:from:
>>>   debugSelection
>>>   defaultSelectionActions
>>>   evaluateSelection
>>>   evaluateSelectionAndDo:
>>>   installDefaultSelectionActions
>>>   printSelection
>>>   profileSelection
>>>   GLMPharoMethodPresentation
>>>   highlightSmalltalkContext
>>>   renderGlamorouslyOn:
>>>   smalltalkClass:
>>>   GLMPharoPlaygroundPresentation
>>>   renderGlamorouslyOn:
>>>   updateVariableBindings
>>>   variableBindings
>>>   variableBindings:
>>>
>>>
>>> On Wed, May 21, 2014 at 7:12 PM, kilon alios wrote:
>>>
 yeah it looks fine now, thank you Andrei :)


 On Wed, May 21, 2014 at 7:05 PM, Andrei Chis <
 chisvasileand...@gmail.com> wrote:

> Now you should also be able to load Rubric through its configuration.
> I also updated Glamour to load Rubric through the configuration
> instead of directly loading the package.
>
>
> Cheers,
> Andrei
>
>
> On Wed, May 21, 2014 at 5:38 PM, Andrei Chis <
> chisvasileand...@gmail.com> wrote:
>
>> Seems that I placed some classes in the wrong packages.
>> Give it another try.
>>
>> Cheers,
>> Andrei
>>
>>
>>
>> On Wed, May 21, 2014 at 5:26 PM, kilon alios 
>> wrote:
>>
>>> no that does not work either I am getting dependancies warning as
>>> well
>>>
>>> this (taken from
>>> http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
>>> )
>>>
>>> Gofer new
>>> smalltalkhubUser: 'Moose' project: 'PetitParser';
>>> package: 'ConfigurationOfPetitParser';
>>> load.
>>>
>>> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.
>>>
>>> gives me this :
>>>
>>> "This package depends on the following classes:
>>>   GLMHighlighterTextDecorator
>>> You must resolve these dependencies before you will be able to load
>>> these definitions:
>>>   GLMPersonStyler
>>>   key
>>>   parser
>>>
>>>
>>> Select Proceed to continue, or close this window to cancel the
>>> operation."
>>>
>>> and this :
>>>
>>> Gofer new
>>>   smalltalkhubUser: 'Moose' project: 'Glamour';
>>>   package: 'ConfigurationOfGlamour';
>>>   load.
>>> (Smalltalk at: #ConfigurationOfGlamour)
>>>   perform: #loadDevelopment.
>>>
>>> gives me same dependencies missing.
>>>
>>>
>>>
>>>
>>> On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont >> > wrote:
>>>
 You'll probably be happier loading #development of
 ConfigurationOfGlamour, and you might want to add
 ConfigurationOfPetitParser. I'll take a look at the configuration of 
 Rubric

 Stephan

 Verstuurd vanaf mijn iPhone

>>>
>>>
>>
>

>>>
>>
>

[Pharo-dev] Readline build is green

Updated configuration to use OSProcess 4.5.8
Updated CI to use PharoExtras/readline

Stephan

Re: [Pharo-dev] a Pharo talk from a ruby conference

2014-05-21 Thread Hilaire Fernandes

Alan's "Back to the future"

Le 21/05/2014 16:17, Ben Coman a écrit :
>>
>>   
> Maybe the marketing needs some "Why Smalltalk is new again..."
> 

-- 
Dr. Geo http://drgeo.eu

Re: [Pharo-dev] Installing Rubric

Thanks, Andrei!

Doru


On Wed, May 21, 2014 at 8:10 PM, kilon alios  wrote:

> yeah all three configurations work now , Rubric , Glamour and Pettit.
> Great work Andrei, keep rocking :)
>
> PS: I am amazed the amount of stuff it loaded. What you guys feed those
> things ? Tons of code to study. Oh boy :D
>
>
> On Wed, May 21, 2014 at 8:49 PM, Andrei Chis 
> wrote:
>
>> Now also Glamour should load without any of the previous warnings.
>>
>>
>> On Wed, May 21, 2014 at 7:21 PM, kilon alios wrote:
>>
>>> On the other hand ConfigurationOfRubic seems to work now :)
>>>
>>>
>>> On Wed, May 21, 2014 at 7:19 PM, kilon alios wrote:
>>>
 hmm weird now I am getting this warning with both installs

 This package depends on the following classes:
   GLMRubricTextPresentation
 You must resolve these dependencies before you will be able to load
 these definitions:
   GLMNewSmalltalkCodePresentation
   compileTextIn:from:
   debugSelection
   defaultSelectionActions
   evaluateSelection
   evaluateSelectionAndDo:
   installDefaultSelectionActions
   printSelection
   profileSelection
   GLMPharoMethodPresentation
   highlightSmalltalkContext
   renderGlamorouslyOn:
   smalltalkClass:
   GLMPharoPlaygroundPresentation
   renderGlamorouslyOn:
   updateVariableBindings
   variableBindings
   variableBindings:


 On Wed, May 21, 2014 at 7:12 PM, kilon alios wrote:

> yeah it looks fine now, thank you Andrei :)
>
>
> On Wed, May 21, 2014 at 7:05 PM, Andrei Chis <
> chisvasileand...@gmail.com> wrote:
>
>> Now you should also be able to load Rubric through its configuration.
>> I also updated Glamour to load Rubric through the configuration
>> instead of directly loading the package.
>>
>>
>> Cheers,
>> Andrei
>>
>>
>> On Wed, May 21, 2014 at 5:38 PM, Andrei Chis <
>> chisvasileand...@gmail.com> wrote:
>>
>>> Seems that I placed some classes in the wrong packages.
>>> Give it another try.
>>>
>>> Cheers,
>>> Andrei
>>>
>>>
>>>
>>> On Wed, May 21, 2014 at 5:26 PM, kilon alios 
>>> wrote:
>>>
 no that does not work either I am getting dependancies warning as
 well

 this (taken from
 http://pharobooks.gforge.inria.fr/PharoByExampleTwo-Eng/latest/PetitParser.pdf
 )

 Gofer new
 smalltalkhubUser: 'Moose' project: 'PetitParser';
 package: 'ConfigurationOfPetitParser';
 load.

 (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault.

 gives me this :

 "This package depends on the following classes:
   GLMHighlighterTextDecorator
 You must resolve these dependencies before you will be able to load
 these definitions:
   GLMPersonStyler
   key
   parser


 Select Proceed to continue, or close this window to cancel the
 operation."

 and this :

 Gofer new
   smalltalkhubUser: 'Moose' project: 'Glamour';
   package: 'ConfigurationOfGlamour';
   load.
 (Smalltalk at: #ConfigurationOfGlamour)
   perform: #loadDevelopment.

 gives me same dependencies missing.




 On Wed, May 21, 2014 at 6:12 PM, Stephan Eggermont <
 step...@stack.nl> wrote:

> You'll probably be happier loading #development of
> ConfigurationOfGlamour, and you might want to add
> ConfigurationOfPetitParser. I'll take a look at the configuration of 
> Rubric
>
> Stephan
>
> Verstuurd vanaf mijn iPhone
>


>>>
>>
>

>>>
>>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"

Re: [Pharo-dev] Improving Pharo By Example





kilon alios wrote:

  In section 1.9  page 18 there is this text
  
  
  
  
  
  
  "At
other times you may have a good idea that a method exists, but will
have no idea what it might be called. The method finder can still help!
For
example, suppose that you would like to find a method that turns a
string
into upper case, for example, it would translate 'eureka' into 'EUREKA'.
   
  
  
  
  The
method finder will suggest a method that does what you want.8
  
  An
asterisk at the beginning of a line in the right pane of the method
finder indicates that this method is the one that was actually used to
obtain
the requested result. So, the asterisk in front of String asUppercase lets us know
that the method asUppercase defined on the
class String
  was
executed and
returned the result we wanted. The methods that do not have an asterisk
are
just the other methods that have the same name as the ones that
returned the
expected result. So Character»asUppercase
  was
not executed on our example,
because 'eureka'
  is
not a Character
  object.
  
  You can
also use the method finder for methods with arguments; for
example, if you are looking for a method that will find the greatest
common
factor of two integers, you might try 25. 35. 5 as an example. You
can also
give the method finder multiple examples to narrow the search space;
the
help text in the bottom pane explains how. "
  
  
  
  I tried " 'eureka' .
'EUREKA '" and the other suggestion it does not seem to work , should I
remove this section ? 
  
  
  
  
  

It works for me...
* World > Tools > Finder
* Type...   'eureka' . 'EUREKA'
* Change [Selectors] to [Examples]

Re: [Pharo-dev] JQueryWidgetBox build is green