January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] About documentation

by StÃ©phane Ducasse

yes you can remove them On Jan 5, 2010, at 8:41 PM, Simon Denier wrote: > > On 5 janv. 2010, at 20:09, StÃ©phane Ducasse wrote: > >> It means that people can edit page, leave note and that a person/group of person with a password >> can edit/delete.... >> since you get an rss feed you can monitor the complete book. > > > One of the interest I see in such a project is that it can be of great help for future chapters. I can see an editor creating a chapter with basic stuff, for example about Morphic and Announcements, just to track small scripts and knowledge, before one takes over to write a full chapter (ok, maybe I'm dreaming, but that would be great for the yet-to-come "Morphic tutorial for pro applications") > > With respect to the previous thread about documentation, it is obvious that such a book complement comments and do not replace them. > > > I wonder, is there a way to hide/delete comments which got "deprecated" after a while? > > >> Stef >> >> On Jan 5, 2010, at 7:46 PM, Simon Denier wrote: >> >>> >>> On 5 janv. 2010, at 19:14, StÃ©phane Ducasse wrote: >>> >>>> Hi guys >>>> >>>> I discussed with lukas and we could get the same infrastructure than for the seaside book >>>> http://book.seaside.st >>>> - editable but with editor control. >>>> - able to generate latex >>>> >>>> Now I want to know if some of you want to control that because I cannot. >>> >>> What does 'control' mean in this case? >>> >>> >>> -- >>> Simon >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 5, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by John M McIntosh

That's a bug, let me see about fixing it tonight On 2010-01-05, at 4:49 AM, Nicolas Cellier wrote: > Hi John, > > I noticed that control + arrow does not work in text editors (it used > to skip to next/previous word) > > Nicolas -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 5, 2010

Re: [Pharo-project] Permutations and Combinations in SequenceableCollection

by John Toohey

But this doesn't get 1-1, 2-2 or 3-3. I had tried something like that use #reverse on each combination, but #combinations does not generate -duplicates- from the number sequences. On Tue, Jan 5, 2010 at 12:16, Henrik Johansen <henrik.s.johansen(a)veloxit.no>wrote: > On Jan 5, 2010, at 5:19 32PM, John Toohey wrote: > > > Hi, > > I'm trying to generate the permutations of a sequence of numbers. I've > found # permutationsDo: aBlock, but this generated the permutation of the > entire sequence. I want to do it in groups of 2. The #combinations: > anInteger atATimeDo: aBlock method does what I need for combinations, but I > cannot find the equivalent for permutations. Does something like this exist > in the standard library, or in an external package. > > > > -- > > -JT > > How about: > #(1 2 3 4) combinations: 2 atATimeDo: [:array | array permutationsDo: > [:each | Transcript show: each printString; cr]] ? > > Cheers, > Henry > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- -JT

Jan. 5, 2010

Re: [Pharo-project] About documentation

by Simon Denier

On 5 janv. 2010, at 20:09, StÃ©phane Ducasse wrote: > It means that people can edit page, leave note and that a person/group of person with a password > can edit/delete.... > since you get an rss feed you can monitor the complete book. One of the interest I see in such a project is that it can be of great help for future chapters. I can see an editor creating a chapter with basic stuff, for example about Morphic and Announcements, just to track small scripts and knowledge, before one takes over to write a full chapter (ok, maybe I'm dreaming, but that would be great for the yet-to-come "Morphic tutorial for pro applications") With respect to the previous thread about documentation, it is obvious that such a book complement comments and do not replace them. I wonder, is there a way to hide/delete comments which got "deprecated" after a while? > Stef > > On Jan 5, 2010, at 7:46 PM, Simon Denier wrote: > >> >> On 5 janv. 2010, at 19:14, StÃ©phane Ducasse wrote: >> >>> Hi guys >>> >>> I discussed with lukas and we could get the same infrastructure than for the seaside book >>> http://book.seaside.st >>> - editable but with editor control. >>> - able to generate latex >>> >>> Now I want to know if some of you want to control that because I cannot. >> >> What does 'control' mean in this case? >> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

Jan. 5, 2010

Re: [Pharo-project] What about killing PharoWeb images?

by StÃ©phane Ducasse

Let us be pragmatic and focused. I would say that I would prefer to have one single pharo-dev image than a middle pharo-dev image and a pharo-web. We can focus on pharo-dev And let lukas ship a one-click seaside image. With the time the pharo-dev will support easy configuration to load seaside aida and a lot more so we will just offer one good image and let people decide. so I would focus on our customers first :) Stef

Jan. 5, 2010

Re: [Pharo-project] About documentation

by StÃ©phane Ducasse

It means that people can edit page, leave note and that a person/group of person with a password can edit/delete.... since you get an rss feed you can monitor the complete book. Stef On Jan 5, 2010, at 7:46 PM, Simon Denier wrote: > > On 5 janv. 2010, at 19:14, StÃ©phane Ducasse wrote: > >> Hi guys >> >> I discussed with lukas and we could get the same infrastructure than for the seaside book >> http://book.seaside.st >> - editable but with editor control. >> - able to generate latex >> >> Now I want to know if some of you want to control that because I cannot. > > What does 'control' mean in this case? > > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 5, 2010

Re: [Pharo-project] About documentation

by StÃ©phane Ducasse

yes :) And the result could even be printed on lulu :) > Would we also be able to generate PDF ? > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > Blog: lamneth.wordpress.com > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > > > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> > Sent: Tue, January 5, 2010 1:14:01 PM > Subject: [Pharo-project] About documentation > > Hi guys > > I discussed with lukas and we could get the same infrastructure than for the seaside book > http://book.seaside.st > - editable but with editor control. > - able to generate latex > > Now I want to know if some of you want to control that because I cannot. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > The new Internet ExplorerÂ® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free!_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 5, 2010

Re: [Pharo-project] About documentation

by Simon Denier

On 5 janv. 2010, at 19:14, StÃ©phane Ducasse wrote: > Hi guys > > I discussed with lukas and we could get the same infrastructure than for the seaside book > http://book.seaside.st > - editable but with editor control. > - able to generate latex > > Now I want to know if some of you want to control that because I cannot. What does 'control' mean in this case? -- Simon

Jan. 5, 2010

Re: [Pharo-project] About documentation

by Benoit St-Jean

Would we also be able to generate PDF ? ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Blog: lamneth.wordpress.com A standpoint is an intellectual horizon of radius zero. (Albert Einstein) ________________________________ From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Tue, January 5, 2010 1:14:01 PM Subject: [Pharo-project] About documentation Hi guys I discussed with lukas and we could get the same infrastructure than for the seaside book http://book.seaside.st - editable but with editor control. - able to generate latex Now I want to know if some of you want to control that because I cannot. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com.

Jan. 5, 2010

[Pharo-project] Fwd: traits :)

by StÃ©phane Ducasse

Some emails about traits from their father @ google :) > Hi Stef > > Sorry for the late reply. I'm just going through my email after the Christmas break... > > > Could someone please come up with ONE example where MI (traits in particular) solve an *actual* problem and not just some academic BS? > > I have encountered a bunch of cases in my every-day work at Google where single inheritance was not good enough to write the functionality that we needed without (a) code duplication and/or (b) boilerplate for object delegation (plus the associated complexity/slow-down/etc.). This was getting so annoying that I went through the hassle of implementing a template-based traits mechanism in C++ that we have been using quite regularly. > > For example, we have been designing and implementing a very complex framework for efficient handling of massive entity/relation graphs (billions of nodes). Since we needed this framework to be general across multiple aspects, we simply couldn't come up with a good way of doing this without some sort of MI, and traits proved to be extremely useful. So, based on my experience, I certainly have seen plenty of real-world applications where traits can make a tremendous difference!! > > That said, I can absolutely see that an overuse of traits can also add a lot of additional complexity. But in my opinion, this is not specific to traits and much more applies to almost any concept when it is overused. Consider for example single inheritance. If someone needs a class with 50 methods and decide to split this into a 10-level deep class hierarchy (just in case that somebody might want to reuse a part of it later), this will annoy a lot of other people and make things unnecessary complex. Similarly, if somebody splits a method with a 20 line algorithm into 10 helper methods with hard-to-understand names and consisting of only 2 lines each, this will probably make things much harder to understand (although having small methods is generally a good thing). > So, despite the fact that the concepts of single inheritance and (helper-)methods can be overused, I'm sure that neither of us would argue that they are bad/useless in the first place. And this is the same for any of the other nice programming concepts that come to mind, like meta-programming and closures (as much as I love closures for parametrization, overuse of functional elements can make code really hard to understand as well...) > > From my point of view, the same applies to traits: If traits are used in cases where they actually bring a benefit, i.e., they factor together a set of methods that conceptually and logically belong together and actually facilitate code reuse, they have been very useful to me. > > > Happy New Year and all the best, > Nathanael >

Jan. 5, 2010