Re: [Pharo-users] A little expression interpreter for new forthcoming book

Okay! Alexandre > On Jan 8, 2017, at 4:34 PM, stepharong wrote: > > fixed. > Alex > this chapter alone is really nice to present OOP and OOD and Pharo to people > can start. > I'm adding some points to answer question raised by my son and it will be > ready to rest. > > Stef -- _,.;:~^~:;

Re: [Pharo-users] A little expression interpreter for new forthcoming book

fixed. Alex this chapter alone is really nice to present OOP and OOD and Pharo to people can start. I'm adding some points to answer question raised by my son and it will be ready to rest. Stef

Re: [Pharo-users] A little expression interpreter for new forthcoming book

excellent catch :) On Sun, 08 Jan 2017 19:02:01 +0100, Alexandre Bergel wrote: Hi Stef! You have written a lot of material. This is great! I had a look at the chapter about the interpreter. Looks great! Figure 17.3 Multiplication>>evaluate It should be “*”, not “+" Alexandre On Jan

Re: [Pharo-users] A little expression interpreter for new forthcoming book

Hi sven for now I'm dumping what I have in my head. Once I will finish to "vomit" I will redo a full pass. Looks very promising. It is a great, much needed subject area. And a huge task as well. I personally like chapter 7 as introduction, a lot, in terms of conceptual approach. If it w

Re: [Pharo-users] A little expression interpreter for new forthcoming book

Looks very promising. It is a great, much needed subject area. And a huge task as well. I personally like chapter 7 as introduction, a lot, in terms of conceptual approach. If it were me, I would put it first (but the current intro reflects that already a bit, so I am not sure). Also, personal

Re: [Pharo-users] Pharo and WebAssembly

Richard Start to think about your vocabulary. If you give me 0.1 % of the money put in Java or JS we will do a lot more. Now we do what is important for the community with the ressources we get. And again take one little topics: - writing a tutorial - coding an app -

Re: [Pharo-users] A little expression interpreter for new forthcoming book

Hi Stef! You have written a lot of material. This is great! I had a look at the chapter about the interpreter. Looks great! Figure 17.3 Multiplication>>evaluate It should be “*”, not “+" Alexandre > On Jan 8, 2017, at 1:24 PM, Stephane Ducasse wrote: > > I released a version of a little e

[Pharo-users] A little expression interpreter for new forthcoming book

I released a version of a little expression interpreter for the new book: Object-oriented programming and design with Pharo. https://ci.inria.fr/pharo-contribution/view/Books/job/LearningObjectOrientedProgramming/63/artifact/book.pdf Typos are welcome as pull requests. Stef

Re: [Pharo-users] Amazing Grace

Yes, a more correct statement would be a man alone can spark a lot of things, but renaissance is a collective endeavor. In all of he examples you mention, small teams work in tandem with more broader cultural phenomena, like acceptance of a movie or programming language. My point was this orga

Re: [Pharo-users] Mongo voyage connect to database with authentication fails

For unknown reasons my mail did not go through the mailing list - perhaps this answer does ist. after switching the authentification mechanism to MONGODB-CR instead of SCRAM-SHA-1, it works. So, I assume, Mongo voyage does not support SCRAM-SHA-1. Will there be a support in future, anyone know

Re: [Pharo-users] understanding existing code

2017-01-08 11:28 GMT+01:00 Hilaire : > Yet, the pane feature of Calypso will not help when browsing for > implementors > It will always help :). For example I want to add matcher/rewrite tool as tab which will work on selected scope. So in system browser it will allow search/rewrite in selected p

Re: [Pharo-users] understanding existing code

Le 08/01/2017 à 10:44, Stephane Ducasse a écrit : > We think about it since long time ago. This is why we rewrote and > produce Nautilus (but the design was not good) - remember in nautilus we > could edit mutliple methods but it was not good and why that because we > needed also panes and .

Re: [Pharo-users] understanding existing code

2017-01-07 11:42 GMT+01:00 Siemen Baader : > Thanks for all these tips and reflections. There are a number of things > for me to try now. > > @Hilaire: I'll try try Calypso. > And please, report any ideas on UI, missing features, bugs here . It is ver

Re: [Pharo-users] Amazing Grace

That is not quite true. As a matter of fact the vast majority of examples of huge success were started by one person or a very small team of people. Rarely big successes come from large companies with huge amount of people and investing ridiculous amount on marketing. Take films for example , the

Re: [Pharo-users] understanding existing code

We think about it since long time ago. This is why we rewrote and produce Nautilus (but the design was not good) - remember in nautilus we could edit mutliple methods but it was not good and why that because we needed also panes and . I agree with you about tooltip and ghost for input. You se