Re: [Pharo-project] SmalltalkHub going beta in a week
Randal L. Schwartz wrote: > > OK, so if this is a general replacement for Squeaksource, the "tagging" > issue comes up again. How do we identify which branch of Squeak a package > might be for? And can we maintain forks for those things that > require it? > That's where the ConfigurationOf...'s and Metacello come in to ensure dependencies, versions and Smalltalk implementations. -- View this message in context: http://forum.world.st/SmalltalkHub-going-beta-in-a-week-tp3430480p3432602.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
[Pharo-project] [ANN] Pharo Release 1.2.1
The Pharo Project is proud to announce the release of Pharo 1.2.1, the third major release of this clean, innovative, open-source Smalltalk environment. Static URL for this ANN: http://www.pharo-project.org/pharo-download/release-1-2-1 French translation: http://code.google.com/p/pharo/wiki/Pharo12FrenchAnnouncement * Update #12345 On Tuesday, March 29th 2011, update #12345 was issued to Pharo's 1.2 development line, a line that started back in June 2010 and was frozen in January 2011. Next, Pharo's continuous integration machinery successfully started building various artifacts based on this 'Pharo Core 1.2', the most important one being 'Pharo 1.2' proper, the full featured development image. Pharo Core 1.2.1 passes 7.836 unit tests, Pharo 1.2.1 no less than 10.760. A large, international community of developers worked hard for several months to iron out all problems and to make Pharo compatible with various Smalltalk libraries and frameworks, among them Seaside 3.0.3 which passes its 1.599 tests. * Pharo Core Changes True to the Pharo philosophy, this release contains numerous small changes, refactorings, cleanups and bugfixes improving the overall quality. Important changes include: – Cleaned the Pluggable hierarchy – Added new undo framework – Cleaned Morph and PasteUpMorph – Added DummyUIManager, a UIManager for operating without a UI – Added NewTextMorph – Removed left overs from MVC: PopUpMenu, SelectionMenu and CustomMenu – Cleaned Utilities, Preferences and TheWorldMenu – Included SimpleMorphic preview – Removing empty classes – Added new TextEditor and SmalltalkEditor – Added new, clean and simple Glamorous, Glamorous Orange GUI Themes – Added new Pro GUI Theme – Added Cog compliant behavior – Added better blocks debugging – Better support for separating SmalltalkImage and SystemDictionary – Fixed package dependencies, providing a good platform for kernel images – Removed old JIT experiments – Migrated to MethodReferenceWithSource and friends – Added more pages under the Help system – Improved the number of commented classes – New Finder tool (replacing Messages Names and Method Finder) – New Recent Changes tool (replacing Recent Submissions) – Improved SpaceTally – Fixed pointer finders tools – Integrated SUnit 4 Started Continuous Integration: use Hudson/Jenkins to automatically build images, run tests, and compile VMs For the Core 1.2 Image development line, 693 issues were resolved. * Pharo Changes The full featured Pharo development image is built automatically by loading the Metacello configuration aptly called ConfigurationOfPharo. Important changes include: – Updated to latest Metacello and all configurations used to use symbolic versions – New tools: Metacello Configuration Browser, Memory Monitor, and Autotest – Updated versions of Shout, RoelTyper, OCompletion, OmniBrowser, AutomaticMethodCategorizer, RefactoringBrowsers, Nile, ProfStef – Added XML-Support, and more Help – Removed NewInspector For the Full Dev 1.2 Image development line, 57 issues were resolved. * Downloads: see http://www.pharo-project.org/pharo-download * Success Stories Pharo has a large user base spread all over the world. Hence there is a growing collection of success stories (www.pharo-project.org/about/success-stories), projects using Pharo that choose to go public with this. Recently, the following were added: DrGeo - an award winning interactive geometry application also used for teaching primary and secondary level students Issys Tracking - a workflow platform to support authorization procedures for the medical practice for a large social organization/health insurance in Argentina Inceptive's Custom ERP - an application for the event planning and resource management administration of a large cultural centre in Flanders __ www.adrian-lienhard.ch twitter.com/adrianlienhard
Re: [Pharo-project] On fixed release planning [was: Actions done in 1.3]
On Wed, Apr 6, 2011 at 10:32 PM, Eliot Miranda wrote: > > > On Wed, Apr 6, 2011 at 1:30 AM, laurent laffont > wrote: > >> >> On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko wrote: >> >>> Planning is also important. >>> >>> Time is good, but another thing is i think we should think about, >>> what features we want to be in new release, and do not release until >>> they delivered. >>> >> >> I don't really like this. I prefer rhythm, agility. Timeboxing enables >> maximum value in each release. If a feature is really important, it will be >> on time. If not on time, it means it was no so important. >> > > I couldn't disagree more. Especially with VisualWorks time-boxing has > caused problems with quality and delivery of functionality. Fundamentally > there is no point putting out a release for the sake of it. A release is > about functionality, both new functionality and bug fixes. Without either > of these there is absolutely no point in releasing anything beyond > marketing. Yes, during a release one can make the call that because a > subset of the functionality will arrive much later than the rest of the > functionality it makes sense for that late functionality to slip the release > and arrive in a later one. But that doesn't imply putting out an > essentially empty release for the sake of promptness. > Let me talk about my experience. Quality may suffer with timeboxing without continuous integration and good test coverage. CI + tests enable timeboxing because I can maintain high quality level. And now we have CI it's wonderful. As a user, I like software developed with fixed iterations because I know exactly when it wil be released, plan upgrades and validations. I'm easily in sync. As a developer I like fixed iterations because 1/ We care more about quality. Cannot develop all this feature in the iteration ? do only a part and check that it works well - write missing tests. Not enough time left to integrate this feature ? Just work on the many details that we need to fix and integrate the new feature soon in next iteration. 2/ We maintain energy. No long waiting period of stuff to be done without realeasing. The more we wait, the less productive we are. 3/ I like to change the planning from "what features this version can't be released without ?" to "what can we develop in 1 / 3 / 6 months (with high quality) ?". 4/ ok I stop here. Even every day at work I'm timeboxing with 25mn iterations (Pomodoro technique) for several years - I cannot live without now. That makes me deliver a lot of energy. I've never seen empty release because of fixed iterations. And even if the release contains only fixed bugs, details adjustment and no new big feature it's great. Details matters a lot. In a former job my team was doing a new features iteration, then a "care about details iteration", then a new features iteration, and so on it was a lot of fun and worked. Indeed I would like try and see if it works with Pharo. I also would like Pharo to be a reference of modern agile development - that would be a step forward. Laurent. > > One thing I do approve of is maintennance releases, where some time after > an initial release one puts out a maintennance release that only contains > bug fixes and no new functionality and I think there are good arguments for > and positive experience with scheduling the maintennance release to arrive > at some fixed time after the first release, e.g. 4 to 6 months. But major > releases must IMO be driven by content. > > best > Eliot > > >> >> Always green test is a must-have. >> >> >> >>> Besides bug fixing and minor improvements, there should be some >>> functionality which we want to have in new release, >>> >> >> That should be a goal, but don't delay a release because the feature is >> not here. If releases are often ( for example every 3 months), shorter, it >> won't be a big problem to wait for the next one. >> >> I prefer to have a release *now* without my feature and wait 3 months for >> the next release than no release and waiting for 3 months more with less and >> less energy. >> >> >> Laurent. >> >> >>> so then you could say: 1.x is better than previous because of A,B,C, >>> but not because a,b,c ( capital letters is major stuff, while regular >>> ones is for minor stuff ) :) >>> >>> >>> On 6 April 2011 10:01, Serge Stinckwich >>> wrote: >>> > On Wed, Apr 6, 2011 at 12:56 PM, laurent laffont >>> > wrote: >>> >> On Tue, Apr 5, 2011 at 10:49 PM, Mariano Martinez Peck >>> >> wrote: >>> >>> >>> >>> Yes!!! totally agree. Now that we release 1.2, I would freeze and >>> release >>> >>> PharoCore 1.3 beta. Update the link to stable pharo to that, and >>> start >>> >>> trying to load the dev tools there. >>> >> >>> >> +10 >>> >> And propose a fixed date for release - no compromise, will be release >>> at >>> >> this date. >>> > >>> > +1 >>> > Timeboxing sounds great. >>> > Podomoro for software development ;-) >>> > >>> > Regards, >>> > -- >>> > Serg
Re: [Pharo-project] Decode url form with Zinc-HTTP
Cool. Thanks Sven!
2011/4/7 Sven Van Caekenberghe :
> Hernán,
>
> From the class comment of ZnUrl:
>
> [...]
>
> The methods in accessing protocols do not do any encoding, those in
> printing do.
>
> [...]
>
> Taking your example:
>
> (ZnUrl fromString:
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D')
> pathSegments
>
> an OrderedCollection('entrez' 'eutils'
> 'esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]')
>
> (ZnUrl fromString:
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D')
> path
>
>
> 'entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]'
>
> (ZnUrl fromString:
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D')
> printString
>
>
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
>
> If you inspect a ZnUrl instance you will notice that the internal Smalltalk
> representation is unencoded. But its #printString and the argument to
> #fromString: are. You could programmatically build up a ZnUrl using accessors
> and supplying unencoded (path) elements.
>
> HTH,
>
> Sven
>
> On 06 Apr 2011, at 22:38, Hernán Morales Durand wrote:
>
>> Hi Sven,
>>
>> In WebUtils one can decode an URL this way
>>
>> ( WebUtils decodeUrlEncodedForm:
>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
>> ) keys anyOne
>>
>> resulting in
>>
>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]'
>>
>> In Zinc-HTTP I didn't find a method for decoding an encoded HTTP address:
>>
>> ( ZnUrl fromString:
>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
>> ) ?
>>
>> but there is #unescapePercents in Network package (by the way if it's
>> the opposite of #encodeForHTTP shouldn't be #decodeFromHTTP ?)
>>
>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
>> unescapePercents
>>
>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]'
>>
>> but I want to maximize package dependency and not system dependency.
>> Is there a way to decode url's in Zinc-HTTP without use
>> #unescapePercents ?
>>
>> Cheers,
>>
>> --
>> Hernán Morales
>> Information Technology Manager,
>> Institute of Veterinary Genetics.
>> National Scientific and Technical Research Council (CONICET).
>> La Plata (1900), Buenos Aires, Argentina.
>> Telephone: +54 (0221) 421-1799.
>> Internal: 422
>> Fax: 425-7980 or 421-1799.
>
Re: [Pharo-project] SmalltalkHub going beta in a week
Randal, Managing packages on a per platform basis is one of the things that Metacello was designed to do ... Dale On Apr 6, 2011, at 7:48 PM, Randal L. Schwartz wrote: >> "Serge" == Serge Stinckwich writes: > > Serge> On Thu, Apr 7, 2011 at 9:38 AM, Randal L. Schwartz > Serge> wrote: "Serge" == Serge Stinckwich writes: >>> > Serge> Yes, but this SmalltalkHub not PharoHub ;-) >>> >>> Oh, did I miss the parallel announcement on squeak-dev? Sorry. > > Serge> There was no announcement on squeak-dev. > Serge> Nicolas forget about that i guess. > > OK, so if this is a general replacement for Squeaksource, the "tagging" > issue comes up again. How do we identify which branch of Squeak a > package might be for? And can we maintain forks for those things that > require it? > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 > http://www.stonehenge.com/merlyn/> > Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. > See http://methodsandmessages.posterous.com/ for Smalltalk discussion >
Re: [Pharo-project] SmalltalkHub going beta in a week
On Thu, Apr 7, 2011 at 9:48 AM, Randal L. Schwartz wrote: >> "Serge" == Serge Stinckwich writes: > > Serge> On Thu, Apr 7, 2011 at 9:38 AM, Randal L. Schwartz > Serge> wrote: "Serge" == Serge Stinckwich writes: >>> > Serge> Yes, but this SmalltalkHub not PharoHub ;-) >>> >>> Oh, did I miss the parallel announcement on squeak-dev? Sorry. > > Serge> There was no announcement on squeak-dev. > Serge> Nicolas forget about that i guess. > > OK, so if this is a general replacement for Squeaksource, the "tagging" > issue comes up again. How do we identify which branch of Squeak a > package might be for? And can we maintain forks for those things that > require it? At the code level, you can manage several Squeak/Pharo branchs with the help of Metacello. At the repository level, i dunno if this possible to use this kind of information for the web site. And i guess not every projects use (or want to use) Metacello, so suitable tags might be needed. There is no obligation for every communities or projects to be on SmalltalkHub, like every git repositories is not on github. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Re: [Pharo-project] SmalltalkHub going beta in a week
> "Serge" == Serge Stinckwich writes: Serge> On Thu, Apr 7, 2011 at 9:38 AM, Randal L. Schwartz Serge> wrote: >>> "Serge" == Serge Stinckwich writes: >> Serge> Yes, but this SmalltalkHub not PharoHub ;-) >> >> Oh, did I miss the parallel announcement on squeak-dev? Sorry. Serge> There was no announcement on squeak-dev. Serge> Nicolas forget about that i guess. OK, so if this is a general replacement for Squeaksource, the "tagging" issue comes up again. How do we identify which branch of Squeak a package might be for? And can we maintain forks for those things that require it? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Re: [Pharo-project] SmalltalkHub going beta in a week
On Thu, Apr 7, 2011 at 9:38 AM, Randal L. Schwartz wrote: >> "Serge" == Serge Stinckwich writes: > > Serge> Yes, but this SmalltalkHub not PharoHub ;-) > > Oh, did I miss the parallel announcement on squeak-dev? Sorry. There was no announcement on squeak-dev. Nicolas forget about that i guess. Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Re: [Pharo-project] SmalltalkHub going beta in a week
> "Serge" == Serge Stinckwich writes: Serge> Yes, but this SmalltalkHub not PharoHub ;-) Oh, did I miss the parallel announcement on squeak-dev? Sorry. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Re: [Pharo-project] SmalltalkHub going beta in a week
On Thu, Apr 7, 2011 at 8:29 AM, Randal L. Schwartz wrote: >> "Janko" == Janko Mivšek writes: > >>> I think it's a good idea to *not* automatically migrate projects from >>> SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has >>> accumulated on SqueakSource during the last years... > > Janko> But still there can be something good and valuable. I'd migrate that > Janko> with some #archive tag or something. > > It's not like Squeaksource is going away any time soon. > > Remember, Pharo isn't the *only* Squeak out there. If the Pharo team > wants to move off Squeaksource, that's great! We were already talking > about how to tag various packages as "squeak-only" or "pharo-only". > This simplifies that. Yes, but this SmalltalkHub not PharoHub ;-) Regards. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Re: [Pharo-project] SmalltalkHub going beta in a week
> "Janko" == Janko Mivšek writes: >> I think it's a good idea to *not* automatically migrate projects from >> SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has >> accumulated on SqueakSource during the last years... Janko> But still there can be something good and valuable. I'd migrate that Janko> with some #archive tag or something. It's not like Squeaksource is going away any time soon. Remember, Pharo isn't the *only* Squeak out there. If the Pharo team wants to move off Squeaksource, that's great! We were already talking about how to tag various packages as "squeak-only" or "pharo-only". This simplifies that. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Re: [Pharo-project] Metacello chapter
https://github.com/SquareBracketAssociates/PharoByExample-english/pull/3 On Thu, Apr 7, 2011 at 3:10 AM, Stéphane Ducasse wrote: >> Cool. BTW, I have a pending pull request on the Socket chapter. > > what is it? > what do you mean? > what do you need? > > Stef > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Re: [Pharo-project] SmalltalkHub going beta in a week
On Thu, Apr 7, 2011 at 1:34 AM, Tudor Girba wrote: > Hi, > > Unless there is a scalability issue, I would not discard anything from > squeaksource. I believe the evolution is too valuable to simply drop it. > > But, maybe there are practical reasons. > > In any case, the idea of having programatic access is really cool. I would > love to use that for analysis purposes. Yes you are right, it might be difficult to say what is important and what is not. If you take the example of github and look at the explore dashboard here: https://github.com/explore you see only repositories with a lot of activities or the trendiest one. I guess there is also a lot of repositories non active or dormant on github also and nobody cares about that. You just need enough disk space ;-) Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
Re: [Pharo-project] Decode url form with Zinc-HTTP
Hernán,
From the class comment of ZnUrl:
[...]
The methods in accessing protocols do not do any encoding, those in
printing do.
[...]
Taking your example:
(ZnUrl fromString:
'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D')
pathSegments
an OrderedCollection('entrez' 'eutils'
'esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]')
(ZnUrl fromString:
'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D')
path
'entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]'
(ZnUrl fromString:
'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D')
printString
'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
If you inspect a ZnUrl instance you will notice that the internal Smalltalk
representation is unencoded. But its #printString and the argument to
#fromString: are. You could programmatically build up a ZnUrl using accessors
and supplying unencoded (path) elements.
HTH,
Sven
On 06 Apr 2011, at 22:38, Hernán Morales Durand wrote:
> Hi Sven,
>
> In WebUtils one can decode an URL this way
>
> ( WebUtils decodeUrlEncodedForm:
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
> ) keys anyOne
>
> resulting in
>
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]'
>
> In Zinc-HTTP I didn't find a method for decoding an encoded HTTP address:
>
> ( ZnUrl fromString:
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
> ) ?
>
> but there is #unescapePercents in Network package (by the way if it's
> the opposite of #encodeForHTTP shouldn't be #decodeFromHTTP ?)
>
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D'
> unescapePercents
>
> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]'
>
> but I want to maximize package dependency and not system dependency.
> Is there a way to decode url's in Zinc-HTTP without use
> #unescapePercents ?
>
> Cheers,
>
> --
> Hernán Morales
> Information Technology Manager,
> Institute of Veterinary Genetics.
> National Scientific and Technical Research Council (CONICET).
> La Plata (1900), Buenos Aires, Argentina.
> Telephone: +54 (0221) 421-1799.
> Internal: 422
> Fax: 425-7980 or 421-1799.
>
Re: [Pharo-project] Actions done in 1.3
On Wed, Apr 6, 2011 at 1:52 PM, Casimiro de Almeida Barreto < casimiro.barr...@gmail.com> wrote: > Em 06-04-2011 17:32, Eliot Miranda escreveu: > > > > (...) > > > I couldn't disagree more. Especially with VisualWorks time-boxing has > caused problems with quality and delivery of functionality. Fundamentally > there is no point putting out a release for the sake of it. A release is > about functionality, both new functionality and bug fixes. Without either > of these there is absolutely no point in releasing anything beyond > marketing. Yes, during a release one can make the call that because a > subset of the functionality will arrive much later than the rest of the > functionality it makes sense for that late functionality to slip the release > and arrive in a later one. But that doesn't imply putting out an > essentially empty release for the sake of promptness. > > +1 Here > > > One thing I do approve of is maintennance releases, where some time after > an initial release one puts out a maintennance release that only contains > bug fixes and no new functionality and I think there are good arguments for > and positive experience with scheduling the maintennance release to arrive > at some fixed time after the first release, e.g. 4 to 6 months. But major > releases must IMO be driven by content. > > +1 Here but... > > I think that maintenance releases must be presented in the form of > "software updates" (meaning, no need to install a new image & reinstall > everything in it). Ideally it should be possible to upgrade fixes without > breaking what's working. > Agreed. What I said about maintennance releases was rather 20th century of me. Forget I ever mentioned it :) > best > Eliot > > >> (...) >> >> Best regards, > > CdAB >
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
On 6 April 2011 22:54, Tudor Girba wrote: > And if we are at it, how would it be possible to get vertical resizers > between rows? > between rows.. > For example, in the case of GTCoder, I would like to be able to resize the > pane with code inside. > i think you'd better do a little different thing. You can put a resizer 'grip' into a corner of code pane, and then resize code using that grip, and parent morph(s) will(or should) adjust themselves accordingly. For example you can take a look how gmail web interface works: for text areas where i currently typing a message there is a resizer grip, using which i can resize the text pane. But there is no sizers every row which representing a separate mail in this thread. I guess you got an idea. > Cheers, > Doru > > > On 6 Apr 2011, at 18:01, Igor Stasenko wrote: > >> okay.. i found one bug >> >> forgot to add cellPositioning: #leftCenter; for colum wrapper morph >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > > > -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] Actions done in 1.3
On 6 April 2011 22:32, Eliot Miranda wrote: > > > On Wed, Apr 6, 2011 at 1:30 AM, laurent laffont > wrote: >> >> On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko wrote: >>> >>> Planning is also important. >>> >>> Time is good, but another thing is i think we should think about, >>> what features we want to be in new release, and do not release until >>> they delivered. >> >> I don't really like this. I prefer rhythm, agility. Timeboxing enables >> maximum value in each release. If a feature is really important, it will be >> on time. If not on time, it means it was no so important. > > I couldn't disagree more. Especially with VisualWorks time-boxing has > caused problems with quality and delivery of functionality. Fundamentally > there is no point putting out a release for the sake of it. A release is > about functionality, both new functionality and bug fixes. Without either > of these there is absolutely no point in releasing anything beyond > marketing. Yes, during a release one can make the call that because a > subset of the functionality will arrive much later than the rest of the > functionality it makes sense for that late functionality to slip the release > and arrive in a later one. But that doesn't imply putting out an > essentially empty release for the sake of promptness. > One thing I do approve of is maintennance releases, where some time after an > initial release one puts out a maintennance release that only contains bug > fixes and no new functionality and I think there are good arguments for and > positive experience with scheduling the maintennance release to arrive at > some fixed time after the first release, e.g. 4 to 6 months. But major > releases must IMO be driven by content. Right. That's exactly what i wanted to say. There's no point to make a release of a 'new version' if it doesn't contains a functionality which were planned to include. Maintenance is sufficient for this. -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
And if we are at it, how would it be possible to get vertical resizers between rows? For example, in the case of GTCoder, I would like to be able to resize the pane with code inside. Cheers, Doru On 6 Apr 2011, at 18:01, Igor Stasenko wrote: > okay.. i found one bug > > forgot to add cellPositioning: #leftCenter; for colum wrapper morph > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."
Re: [Pharo-project] Actions done in 1.3
Em 06-04-2011 17:32, Eliot Miranda escreveu: > > > (...) > > I couldn't disagree more. Especially with VisualWorks time-boxing has > caused problems with quality and delivery of functionality. > Fundamentally there is no point putting out a release for the sake of > it. A release is about functionality, both new functionality and bug > fixes. Without either of these there is absolutely no point in > releasing anything beyond marketing. Yes, during a release one can > make the call that because a subset of the functionality will arrive > much later than the rest of the functionality it makes sense for that > late functionality to slip the release and arrive in a later one. But > that doesn't imply putting out an essentially empty release for the > sake of promptness. +1 Here > > One thing I do approve of is maintennance releases, where some time > after an initial release one puts out a maintennance release that only > contains bug fixes and no new functionality and I think there are good > arguments for and positive experience with scheduling the maintennance > release to arrive at some fixed time after the first release, e.g. 4 > to 6 months. But major releases must IMO be driven by content. +1 Here but... I think that maintenance releases must be presented in the form of "software updates" (meaning, no need to install a new image & reinstall everything in it). Ideally it should be possible to upgrade fixes without breaking what's working. > > best > Eliot > > > (...) > Best regards, CdAB
Re: [Pharo-project] Transcript rant
On 6 April 2011 20:24, wrote:
> Em 06/04/2011 09:07, Igor Stasenko escreveu:
>> > On 6 April 2011 13:54, Fernando Olivero
> wrote:
>
>> > Hi Stef, i will as an initial step take Igor's suggestion and make
>> > Transcript a global wich points to an instance of TranscriptModel
>> > ( the new name i propose for the current class taken from CUIS).
>> > I still believe that composition is better then inheritance for
>> > handling different behaviors of the Transcript, so i argue against
>> > making it a subclass of WriteStream and making it polymorphic with
>> > a write stream instead.
>> >
>> That's totally not my concern. As long as thing which sits there
>> responds to writestream protocol , i don't care about rest.
>>
>
> Would it make sense then to lift the methods from {write}stream and
> put then in a Trait so the composition is made through reuse of code?
>
> My 0.019
hehe.. yes, but if to follow this road every time you need to do small
improvement,
then at some day you will discover that you rewriting whole system
from scratch :)
>
> --
> Cesar Rabak
--
Best regards,
Igor Stasenko AKA sig.
[Pharo-project] Decode url form with Zinc-HTTP
Hi Sven, In WebUtils one can decode an URL this way ( WebUtils decodeUrlEncodedForm: 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D' ) keys anyOne resulting in 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]' In Zinc-HTTP I didn't find a method for decoding an encoded HTTP address: ( ZnUrl fromString: 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D' ) ? but there is #unescapePercents in Network package (by the way if it's the opposite of #encodeForHTTP shouldn't be #decodeFromHTTP ?) 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26term%3Dscience%5Bjournal%5D%2BAND%2Bbreast%2Bcancer%2BAND%2B2009%5Bpdat%5D' unescapePercents 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]' but I want to maximize package dependency and not system dependency. Is there a way to decode url's in Zinc-HTTP without use #unescapePercents ? Cheers, -- Hernán Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.
Re: [Pharo-project] Actions done in 1.3
On Wed, Apr 6, 2011 at 1:30 AM, laurent laffont wrote: > > On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko wrote: > >> Planning is also important. >> >> Time is good, but another thing is i think we should think about, >> what features we want to be in new release, and do not release until >> they delivered. >> > > I don't really like this. I prefer rhythm, agility. Timeboxing enables > maximum value in each release. If a feature is really important, it will be > on time. If not on time, it means it was no so important. > I couldn't disagree more. Especially with VisualWorks time-boxing has caused problems with quality and delivery of functionality. Fundamentally there is no point putting out a release for the sake of it. A release is about functionality, both new functionality and bug fixes. Without either of these there is absolutely no point in releasing anything beyond marketing. Yes, during a release one can make the call that because a subset of the functionality will arrive much later than the rest of the functionality it makes sense for that late functionality to slip the release and arrive in a later one. But that doesn't imply putting out an essentially empty release for the sake of promptness. One thing I do approve of is maintennance releases, where some time after an initial release one puts out a maintennance release that only contains bug fixes and no new functionality and I think there are good arguments for and positive experience with scheduling the maintennance release to arrive at some fixed time after the first release, e.g. 4 to 6 months. But major releases must IMO be driven by content. best Eliot > > Always green test is a must-have. > > > >> Besides bug fixing and minor improvements, there should be some >> functionality which we want to have in new release, >> > > That should be a goal, but don't delay a release because the feature is not > here. If releases are often ( for example every 3 months), shorter, it won't > be a big problem to wait for the next one. > > I prefer to have a release *now* without my feature and wait 3 months for > the next release than no release and waiting for 3 months more with less and > less energy. > > > Laurent. > > >> so then you could say: 1.x is better than previous because of A,B,C, >> but not because a,b,c ( capital letters is major stuff, while regular >> ones is for minor stuff ) :) >> >> >> On 6 April 2011 10:01, Serge Stinckwich >> wrote: >> > On Wed, Apr 6, 2011 at 12:56 PM, laurent laffont >> > wrote: >> >> On Tue, Apr 5, 2011 at 10:49 PM, Mariano Martinez Peck >> >> wrote: >> >>> >> >>> Yes!!! totally agree. Now that we release 1.2, I would freeze and >> release >> >>> PharoCore 1.3 beta. Update the link to stable pharo to that, and >> start >> >>> trying to load the dev tools there. >> >> >> >> +10 >> >> And propose a fixed date for release - no compromise, will be release >> at >> >> this date. >> > >> > +1 >> > Timeboxing sounds great. >> > Podomoro for software development ;-) >> > >> > Regards, >> > -- >> > Serge Stinckwich >> > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> > Every DSL ends up being Smalltalk >> > http://doesnotunderstand.org/ >> > >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> >
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
Excellent job :). And very highly appreciated.
Cheers,
Doru
On 6 Apr 2011, at 22:06, Stéphane Ducasse wrote:
> Good! I'm happy. Igor and Ben are doing a great job.
>
> Stef
>
>> This is great!
>>
>> I tested it on Glamour and it looks pretty cool. And, it is definitely
>> snappier.
>>
>> I tested LazyMorphTreeMorph it on a list with 1 million items in the context
>> of Glamour with a pagination of 50 items I got:
>> - before: 6414 ms
>> - after: 3526 ms
>>
>> The code I used is (works in a Moose image, or after you load Glamour):
>>
>> Time millisecondsToRun: [
>> | browser |
>> browser := GLMTabulator new.
>> browser column: #one.
>> browser transmit to: #one; andShow: [ :a |
>> a tree
>> tags: [ :each | {each even printString} ];
>> showOnly: 50 ].
>> browser openOn: (1 to: 100)
>> ]
>>
>> Cheers,
>> Doru
>>
>>
>> On 6 Apr 2011, at 18:01, Igor Stasenko wrote:
>>
>>> okay.. i found one bug
>>>
>>> forgot to add cellPositioning: #leftCenter; for colum wrapper morph
>>>
>>>
>>> --
>>> Best regards,
>>> Igor Stasenko AKA sig.
>>>
>>
>> --
>> www.tudorgirba.com
>>
>> "What we can governs what we wish."
>>
>>
>>
>>
>
>
--
www.tudorgirba.com
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
[Pharo-project] Issue 3967 in pharo: Announcement enhancement
Status: Accepted Owner: stephane...@gmail.com New issue 3967 by stephane...@gmail.com: Announcement enhancement http://code.google.com/p/pharo/issues/detail?id=3967 Both solutions lead to remaining subscribers being notified when an error occurs. So which is decided upon, depends on which of their respective benefits are valued more. For that, it'd be nice if more than 2 people chimed in on. :) Short summary (not guaranteed to be 100% objective) Curtailing -> - Your image may crash in some cases, more specifically if you: 1) have errors in subscribers to announcements made in system-critical processes, as they will be suspended while debugging. 2) deliver announcements in a separate thread from where they're announced, and the announcing thread does so regularily. + Easy to debug. Entire call-chain available, no modification to state caused by subsequent subscribers. Restart should always lead in bug being reproduceable. The remove-from-subscriptions part of Error-handling and ifCurtailed could be combined as well, in which case #2 no longer applies. Error handling -> - Hard/impossible to debug because: 1) If your error was in ordering, debugger will step through flawlessly if restarted. 2) You start at the context of the subscriptions action, no idea where it came from. + More robust, none of the cases mentioned in Curtailing will crash your image. With the different pros/cons mentioned above in mind, here are .cs with example implementations for what both Igor / I would like. (minus remove-from-subscriptions for ifCurtailed: ) Attachments: AnnouncementErrorHandling.zip 1.7 KB
Re: [Pharo-project] SmalltalkHub going beta in a week
Le mercredi 06 avril 2011 à 20:30 +0200, Noury Bouraqadi a écrit : > Cool! I guess you didn't you use JTalkST (too young), did you? No, it's too young to be used in real world apps. Maybe in the future ;) cheers, Nico -- Nicolas Petton http://www.nicolas-petton.fr
Re: [Pharo-project] Import Package from VW to Pharo
Hi glenn What were your problems exactly? We port regularly code from VW for Moose. Now soemtimes we need some manual tweaking. Did you check the mailing-list because this topic was raised recently? Stef > I have a package in VW7.6 that I want to move to Pharo (Windows 7). I tried > Fileout30 but could not get it to work. I was thinking of reading the .PST > file using the XML parser and then programmatically add classes and methods > to Pharo. I've looked at various classes related to Class and am having > difficulty getting started. Can anyone provide some pointers? > > Regards, > Glenn
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
Thanks fernando! this is cool to see some work on this front. We should work step by step. What I wanted to say is that while I value some part of CUIS. Other parts are still old and odd like its ancestor. Pharo is moving on a lot of front and people may not notice it but soon we will have a lot of pieces of the puzzle ready to get real benefit of the infrastructure we are steadily building :). Stef > Thanks Ben and Stef, the answer was in concordance with what i was thinking. > > CUIS already has the TextModel class, and the PluggableTextModel > class. So together with the menu pragma builders of Pharo, they > provide the foundations for the implementation you just nicely > explained. > > Next week, once i finish writing something for my research, i will > finish the initial port. And hopefully provide a working example of > SMx in Pharo, applying the ideas here discussed. A somehow initial > port, which can get expanded gradually, from the list of widgets we > mentioned in previous emails: MorphTreeMorph, etc.. > (and at a final stage Polymorph). > > Fernando > pd: Alex, SMx is SimpleMorph, an older version of the cleaned up > Morphic from the CUIS image. > > > On Wed, Apr 6, 2011 at 6:19 PM, Stéphane Ducasse > wrote: >> YES!YES!YES! >> It is cool to see your impact on them. Excellent it will really helps >> bringing pharo IDE to the next level. >> >> Stef >> >> On Apr 6, 2011, at 2:11 PM, Igor Stasenko wrote: >> >>> On 6 April 2011 13:16, Stéphane Ducasse wrote: Because once people are dependent and drug addict then they will spend time fixing it :) No seriously this is mega hyper hyper important that we get - solid scalable listMorph and treeMorph So the best way is to stress it. The second answer is that nautilus is cool and needs tree :) >>> i second that. >>> trees and lists are basic widgets which could be used for different means. >>> So why we should limit ourselves and use some crappy lists to mimic >>> tree, instead of using trees, and improving this widget and making it >>> work well. >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >
Re: [Pharo-project] Metacello chapter
> Cool. BTW, I have a pending pull request on the Socket chapter. what is it? what do you mean? what do you need? Stef
Re: [Pharo-project] SmalltalkHub going beta in a week
> Hi, > > Unless there is a scalability issue, I would not discard anything from > squeaksource. I believe the evolution is too valuable to simply drop it. > > But, maybe there are practical reasons. May be we could have a second server where we copy everything there. We will see how we will manage that. The query are important because we can identify created but unused created but dormant created but not used ... and tag them > In any case, the idea of having programatic access is really cool. I would > love to use that for analysis purposes. :) I did not guess on that one :) and with the new EyeSee we may expect to have some cool looking infrastructure.
Re: [Pharo-project] SmalltalkHub going beta in a week
But you have the tool: Gofer :) Stef On Apr 6, 2011, at 6:40 PM, Mariano Martinez Peck wrote: > > > On Wed, Apr 6, 2011 at 6:34 PM, Adrian Lienhard wrote: > Wow, looks great! > > I think it's a good idea to *not* automatically migrate projects from > SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has > accumulated on SqueakSource during the last years... > > > +1 But providing a tool/script so that we know how to migrate manually our > own projects is a nice nice nice wish :) > > > Cheers, > Adrian > > > On Apr 6, 2011, at 13:07 , Tudor Girba wrote: > > > Phenomenal stuff :). I cannot wait to use it. Will there be a possibility > > to migrate the existing squeaksource there? > > > > Cheers, > > Doru > > > > > > On 6 Apr 2011, at 13:00, Nicolas Petton wrote: > > > >> Hi, > >> > >> We've been working on a new code repository & project management > >> application for Smalltalk with ESUG named SmalltalkHub. > >> > >> If everything goes fine, the app should be in public beta in a week. > >> The source code of SmalltalkHub will be available at the same moment > >> (the project itself is hosted by SmalltalkHub). > >> > >> Here's a screenshot in the meantime. > >> http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html > >> > >> Cheers, > >> Nicolas > >> -- > >> Nicolas Petton > >> http://www.nicolas-petton.fr > >> > >> > > > > -- > > www.tudorgirba.com > > > > "Being happy is a matter of choice." > > > > > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com >
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
Good! I'm happy. Igor and Ben are doing a great job.
Stef
> This is great!
>
> I tested it on Glamour and it looks pretty cool. And, it is definitely
> snappier.
>
> I tested LazyMorphTreeMorph it on a list with 1 million items in the context
> of Glamour with a pagination of 50 items I got:
> - before: 6414 ms
> - after: 3526 ms
>
> The code I used is (works in a Moose image, or after you load Glamour):
>
> Time millisecondsToRun: [
> | browser |
> browser := GLMTabulator new.
> browser column: #one.
> browser transmit to: #one; andShow: [ :a |
> a tree
> tags: [ :each | {each even printString} ];
> showOnly: 50 ].
> browser openOn: (1 to: 100)
> ]
>
> Cheers,
> Doru
>
>
> On 6 Apr 2011, at 18:01, Igor Stasenko wrote:
>
>> okay.. i found one bug
>>
>> forgot to add cellPositioning: #leftCenter; for colum wrapper morph
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>>
>
> --
> www.tudorgirba.com
>
> "What we can governs what we wish."
>
>
>
>
[Pharo-project] Import Package from VW to Pharo
I have a package in VW7.6 that I want to move to Pharo (Windows 7). I tried Fileout30 but could not get it to work. I was thinking of reading the .PST file using the XML parser and then programmatically add classes and methods to Pharo. I've looked at various classes related to Class and am having difficulty getting started. Can anyone provide some pointers? Regards, Glenn
[Pharo-project] [COTDC] 43 - TextStyleFontSelectorDialogWindow
Today: TextStyleFontSelectorDialogWindow Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
> pd: Alex, SMx is SimpleMorph, an older version of the cleaned up > Morphic from the CUIS image. Ok, thanks Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
Thanks Ben and Stef, the answer was in concordance with what i was thinking. CUIS already has the TextModel class, and the PluggableTextModel class. So together with the menu pragma builders of Pharo, they provide the foundations for the implementation you just nicely explained. Next week, once i finish writing something for my research, i will finish the initial port. And hopefully provide a working example of SMx in Pharo, applying the ideas here discussed. A somehow initial port, which can get expanded gradually, from the list of widgets we mentioned in previous emails: MorphTreeMorph, etc.. (and at a final stage Polymorph). Fernando pd: Alex, SMx is SimpleMorph, an older version of the cleaned up Morphic from the CUIS image. On Wed, Apr 6, 2011 at 6:19 PM, Stéphane Ducasse wrote: > YES!YES!YES! > It is cool to see your impact on them. Excellent it will really helps > bringing pharo IDE to the next level. > > Stef > > On Apr 6, 2011, at 2:11 PM, Igor Stasenko wrote: > >> On 6 April 2011 13:16, Stéphane Ducasse wrote: >>> Because once people are dependent and drug addict then they will spend time >>> fixing it :) >>> >>> No seriously this is mega hyper hyper important that we get >>> - solid scalable listMorph and treeMorph >>> So the best way is to stress it. >>> >>> The second answer is that nautilus is cool and needs tree :) >>> >> i second that. >> trees and lists are basic widgets which could be used for different means. >> So why we should limit ourselves and use some crappy lists to mimic >> tree, instead of using trees, and improving this widget and making it >> work well. >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > >
Re: [Pharo-project] Issue 3966 in pharo: String>>lines misses tests
Comment #3 on issue 3966 by nicolas@gmail.com: String>>lines misses tests http://code.google.com/p/pharo/issues/detail?id=3966 There could also be a test with mixed conventions because it is a feature of #lines
Re: [Pharo-project] Metacello chapter
Cool. BTW, I have a pending pull request on the Socket chapter. Noury On 6 avr. 2011, at 09:58, Stéphane Ducasse wrote: > Hi guys > > here is a new version of the metacello chapter. > So we wrote it, rewrote it, rerewrote it. > Now if this is of interest for you you can read it. > > But if you don't it means that I'm losing my time and I should stop writing > and like > that you can cry that there is no doc about Pharo. > > > > Stef > Noury Bouraqadi http://car.mines-douai.fr/noury -- -6th National Conference on “Control Architecture of Robots” 24-25 may 2011, Grenoble area, France http://car2011.inrialpes.fr/ -19th ESUG International Smalltalk Conference 22-26 August 2011, Edinburgh, UK http://www.esug.org/Conferences/2011 -19èmes Journées Francophones sur les Systèmes Multi-Agents (JFSMA’11) http://www.univ-valenciennes.fr/congres/jfsma2011/ 17-19 Octobre 2011, Valenciennes, France
Re: [Pharo-project] SmalltalkHub going beta in a week
Hi, Unless there is a scalability issue, I would not discard anything from squeaksource. I believe the evolution is too valuable to simply drop it. But, maybe there are practical reasons. In any case, the idea of having programatic access is really cool. I would love to use that for analysis purposes. Cheers, Doru On 6 Apr 2011, at 18:46, Janko Mivšek wrote: > On 06. 04. 2011 18:34, Adrian Lienhard wrote: >> Wow, looks great! >> >> I think it's a good idea to *not* automatically migrate projects from >> SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has >> accumulated on SqueakSource during the last years... > > But still there can be something good and valuable. I'd migrate that > with some #archive tag or something. > > The same goes with code from other Smalltalks. Like Smalltalk Goodies > archive back from 90's, there are quite some interesting code, which I'm > still using. > > Best regards > Janko > > > >> >> Cheers, >> Adrian >> >> >> On Apr 6, 2011, at 13:07 , Tudor Girba wrote: >> >>> Phenomenal stuff :). I cannot wait to use it. Will there be a possibility >>> to migrate the existing squeaksource there? >>> >>> Cheers, >>> Doru >>> >>> >>> On 6 Apr 2011, at 13:00, Nicolas Petton wrote: >>> Hi, We've been working on a new code repository & project management application for Smalltalk with ESUG named SmalltalkHub. If everything goes fine, the app should be in public beta in a week. The source code of SmalltalkHub will be available at the same moment (the project itself is hosted by SmalltalkHub). Here's a screenshot in the meantime. http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html Cheers, Nicolas -- Nicolas Petton http://www.nicolas-petton.fr > > > -- > Janko Mivšek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > -- www.tudorgirba.com "One cannot do more than one can do."
Re: [Pharo-project] SmalltalkHub going beta in a week
Cool! I guess you didn't you use JTalkST (too young), did you? On 6 avr. 2011, at 13:00, Nicolas Petton wrote: > Hi, > > We've been working on a new code repository & project management > application for Smalltalk with ESUG named SmalltalkHub. > > If everything goes fine, the app should be in public beta in a week. > The source code of SmalltalkHub will be available at the same moment > (the project itself is hosted by SmalltalkHub). > > Here's a screenshot in the meantime. > http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html > > Cheers, > Nicolas > -- > Nicolas Petton > http://www.nicolas-petton.fr > > Noury
Re: [Pharo-project] Transcript rant
Em 06/04/2011 09:07, Igor Stasenko escreveu:
> > On 6 April 2011 13:54, Fernando Olivero
wrote:
> > Hi Stef, i will as an initial step take Igor's suggestion and make
> > Transcript a global wich points to an instance of TranscriptModel
> > ( the new name i propose for the current class taken from CUIS).
> > I still believe that composition is better then inheritance for
> > handling different behaviors of the Transcript, so i argue against
> > making it a subclass of WriteStream and making it polymorphic with
> > a write stream instead.
> >
> That's totally not my concern. As long as thing which sits there
> responds to writestream protocol , i don't care about rest.
>
Would it make sense then to lift the methods from {write}stream and
put then in a Trait so the composition is made through reuse of code?
My 0.019
--
Cesar Rabak
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
This is great!
I tested it on Glamour and it looks pretty cool. And, it is definitely snappier.
I tested LazyMorphTreeMorph it on a list with 1 million items in the context of
Glamour with a pagination of 50 items I got:
- before: 6414 ms
- after: 3526 ms
The code I used is (works in a Moose image, or after you load Glamour):
Time millisecondsToRun: [
| browser |
browser := GLMTabulator new.
browser column: #one.
browser transmit to: #one; andShow: [ :a |
a tree
tags: [ :each | {each even printString} ];
showOnly: 50 ].
browser openOn: (1 to: 100)
]
Cheers,
Doru
On 6 Apr 2011, at 18:01, Igor Stasenko wrote:
> okay.. i found one bug
>
> forgot to add cellPositioning: #leftCenter; for colum wrapper morph
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
--
www.tudorgirba.com
"What we can governs what we wish."
Re: [Pharo-project] Question about the Refactoring Browser
>>> I do not think so. >>> Even if we are working on Ring just for this scenario I doubt it worked by >>> default. >> >> Sure it works by default. > > So you can have a model on code that is not in the image? Most refactorings start from the existing system: model := RBNamespace onEnvironment: BrowserEnvironment new But you can also start from nothing: model := RBNamespace onEnvironment: BrowserEnvironment new not > I imagine that you can create RBClass RBMethod but this is not my point. Why not? RBClass, RBMetaclass and RBMethod are central parts of the model. All reflection you do on these objects only affects what is defined inside this model. > How do you do that? which browser do you use? If you have OB-Refactory loaded you can use: model open Lukas -- Lukas Renggli www.lukas-renggli.ch
Re: [Pharo-project] SmalltalkHub going beta in a week
On 06. 04. 2011 18:34, Adrian Lienhard wrote: > Wow, looks great! > > I think it's a good idea to *not* automatically migrate projects from > SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has > accumulated on SqueakSource during the last years... But still there can be something good and valuable. I'd migrate that with some #archive tag or something. The same goes with code from other Smalltalks. Like Smalltalk Goodies archive back from 90's, there are quite some interesting code, which I'm still using. Best regards Janko > > Cheers, > Adrian > > > On Apr 6, 2011, at 13:07 , Tudor Girba wrote: > >> Phenomenal stuff :). I cannot wait to use it. Will there be a possibility to >> migrate the existing squeaksource there? >> >> Cheers, >> Doru >> >> >> On 6 Apr 2011, at 13:00, Nicolas Petton wrote: >> >>> Hi, >>> >>> We've been working on a new code repository & project management >>> application for Smalltalk with ESUG named SmalltalkHub. >>> >>> If everything goes fine, the app should be in public beta in a week. >>> The source code of SmalltalkHub will be available at the same moment >>> (the project itself is hosted by SmalltalkHub). >>> >>> Here's a screenshot in the meantime. >>> http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html >>> >>> Cheers, >>> Nicolas >>> -- >>> Nicolas Petton >>> http://www.nicolas-petton.fr -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
Re: [Pharo-project] Delay bug
We managed to resolve our initial problem with the process scheduling [1]. All Cmsbox customers have been migrated to Pharo and it works very reliably now. Gary, maybe you could open a ticket already now and post what you know at this time to get early feedback. [1] http://code.google.com/p/pharo/issues/detail?id=3498 Cheers Adrian On Apr 6, 2011, at 18:24 , Stéphane Ducasse wrote: > thanks gary. > Yes adrian got a problem on his server after two weeks of load. I do not know > how we can improve them. > > Stef > > On Apr 6, 2011, at 6:02 PM, Gary Chambers wrote: > >> Well, we have been having problems with applications appearing to hang every >> 6 days or so (sound familiar?). >> >> I have identified a bug in the Delay implementation, rather obscure, but >> highlighted by our applications that make HEAVY use of processes/(tight, a >> few tens of milliseconds)delays/semaphores etc. >> Naturally due to an edge case on millisecond clock rollover... >> >> Affects all Squeak/Pharo versions, as far as I can tell. (It is separate >> from the OSProcess issues I have posted about a few weeks ago). >> >> I've developed a potential fix, though I'll have to let you all know whether >> (hopefully) successful in a week or two... fingers crossed! >> >> I hope it is fixable, last hurdle for business applications, from our point >> of view. >> >> I'll post details when fix confirmed or failed then. >> >> Regards, Gary > >
Re: [Pharo-project] SmalltalkHub going beta in a week
On Wed, Apr 6, 2011 at 6:34 PM, Adrian Lienhard wrote: > Wow, looks great! > > I think it's a good idea to *not* automatically migrate projects from > SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has > accumulated on SqueakSource during the last years... > > +1 But providing a tool/script so that we know how to migrate manually our own projects is a nice nice nice wish :) > Cheers, > Adrian > > > On Apr 6, 2011, at 13:07 , Tudor Girba wrote: > > > Phenomenal stuff :). I cannot wait to use it. Will there be a possibility > to migrate the existing squeaksource there? > > > > Cheers, > > Doru > > > > > > On 6 Apr 2011, at 13:00, Nicolas Petton wrote: > > > >> Hi, > >> > >> We've been working on a new code repository & project management > >> application for Smalltalk with ESUG named SmalltalkHub. > >> > >> If everything goes fine, the app should be in public beta in a week. > >> The source code of SmalltalkHub will be available at the same moment > >> (the project itself is hosted by SmalltalkHub). > >> > >> Here's a screenshot in the meantime. > >> http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html > >> > >> Cheers, > >> Nicolas > >> -- > >> Nicolas Petton > >> http://www.nicolas-petton.fr > >> > >> > > > > -- > > www.tudorgirba.com > > > > "Being happy is a matter of choice." > > > > > > > > > > > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
Please! Stef On Apr 6, 2011, at 6:30 PM, Adrian Lienhard wrote: > I guess, the question is, *who* is sending the ANN mail?! > > It's not breaking news anymore, but we should still send one ;) > > Shall I do it? > > Adrian > > > On Apr 6, 2011, at 15:47 , Mariano Martinez Peck wrote: > >> But when are we going to send this mail to this mailing list? and >> pharo-users? etc... >> can we start to buzz arround ? > >
Re: [Pharo-project] SmalltalkHub going beta in a week
Wow, looks great! I think it's a good idea to *not* automatically migrate projects from SqueakSource ;). It's an opportunity to get rid of a lot of cruft that has accumulated on SqueakSource during the last years... Cheers, Adrian On Apr 6, 2011, at 13:07 , Tudor Girba wrote: > Phenomenal stuff :). I cannot wait to use it. Will there be a possibility to > migrate the existing squeaksource there? > > Cheers, > Doru > > > On 6 Apr 2011, at 13:00, Nicolas Petton wrote: > >> Hi, >> >> We've been working on a new code repository & project management >> application for Smalltalk with ESUG named SmalltalkHub. >> >> If everything goes fine, the app should be in public beta in a week. >> The source code of SmalltalkHub will be available at the same moment >> (the project itself is hosted by SmalltalkHub). >> >> Here's a screenshot in the meantime. >> http://nicolas-petton.fr/2011/04/06/smalltalkhub-beta-in-a-week.html >> >> Cheers, >> Nicolas >> -- >> Nicolas Petton >> http://www.nicolas-petton.fr >> >> > > -- > www.tudorgirba.com > > "Being happy is a matter of choice." > > > >
Re: [Pharo-project] Delay bug
Bear with me, hopefully my fix will work (yay for all then, especially Seaside peeps!). Regards, Gary - Original Message - From: "Stéphane Ducasse" To: Sent: Wednesday, April 06, 2011 5:24 PM Subject: Re: [Pharo-project] Delay bug thanks gary. Yes adrian got a problem on his server after two weeks of load. I do not know how we can improve them. Stef On Apr 6, 2011, at 6:02 PM, Gary Chambers wrote: Well, we have been having problems with applications appearing to hang every 6 days or so (sound familiar?). I have identified a bug in the Delay implementation, rather obscure, but highlighted by our applications that make HEAVY use of processes/(tight, a few tens of milliseconds)delays/semaphores etc. Naturally due to an edge case on millisecond clock rollover... Affects all Squeak/Pharo versions, as far as I can tell. (It is separate from the OSProcess issues I have posted about a few weeks ago). I've developed a potential fix, though I'll have to let you all know whether (hopefully) successful in a week or two... fingers crossed! I hope it is fixable, last hurdle for business applications, from our point of view. I'll post details when fix confirmed or failed then. Regards, Gary
Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
I guess, the question is, *who* is sending the ANN mail?! It's not breaking news anymore, but we should still send one ;) Shall I do it? Adrian On Apr 6, 2011, at 15:47 , Mariano Martinez Peck wrote: > But when are we going to send this mail to this mailing list? and > pharo-users? etc... > can we start to buzz arround ?
Re: [Pharo-project] Metacello chapter
I already asked oscar so it will come. > Stef, can we upload it to http://pharobyexample.org/ (on the right of the > page) > > Thanks > > Mariano > > On Wed, Apr 6, 2011 at 9:58 AM, Stéphane Ducasse > wrote: > Hi guys > > here is a new version of the metacello chapter. > So we wrote it, rewrote it, rerewrote it. > Now if this is of interest for you you can read it. > > But if you don't it means that I'm losing my time and I should stop writing > and like > that you can cry that there is no doc about Pharo. > > > > > Stef > > > > > > -- > Mariano > http://marianopeck.wordpress.com >
Re: [Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
Thanks Torsten, I updated the download page. Adrian On Apr 6, 2011, at 15:39 , Torsten Bergmann wrote: > Hi, > > now that Pharo 1.2.1. is available on the website > I've also updated the Win32 Setup. You can grab it here: > > https://gforge.inria.fr/frs/download.php/28467/setup_pharo1.2.1-12345-release11.04.06.exe > > Compared to the one click (26MB) this download is only 13MB > in size and provides better windows integration. So if > you are on Windows you can use this > > Whats new: > == > - Pharo 1.2.1.#12345 is included > - Cog VM is included (CogVM VM.r2378) with a custom CogVM/Pharo icon > > Maybe Adrian is able to change: > http://www.pharo-project.org/pharo-download > to point to the new executable. > > Thx > T. > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
Re: [Pharo-project] Question about the Refactoring Browser
On Apr 6, 2011, at 6:19 PM, Lukas Renggli wrote: >>> If I understand correctly I can get a refactoring code model of the >>> unloaded code, >> >> I do not think so. >> Even if we are working on Ring just for this scenario I doubt it worked by >> default. > > Sure it works by default. So you can have a model on code that is not in the image? I imagine that you can create RBClass RBMethod but this is not my point. How do you do that? which browser do you use? > Cheers, > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch
Re: [Pharo-project] Delay bug
thanks gary. Yes adrian got a problem on his server after two weeks of load. I do not know how we can improve them. Stef On Apr 6, 2011, at 6:02 PM, Gary Chambers wrote: > Well, we have been having problems with applications appearing to hang every > 6 days or so (sound familiar?). > > I have identified a bug in the Delay implementation, rather obscure, but > highlighted by our applications that make HEAVY use of processes/(tight, a > few tens of milliseconds)delays/semaphores etc. > Naturally due to an edge case on millisecond clock rollover... > > Affects all Squeak/Pharo versions, as far as I can tell. (It is separate from > the OSProcess issues I have posted about a few weeks ago). > > I've developed a potential fix, though I'll have to let you all know whether > (hopefully) successful in a week or two... fingers crossed! > > I hope it is fixable, last hurdle for business applications, from our point > of view. > > I'll post details when fix confirmed or failed then. > > Regards, Gary
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
so can you open an issue with all the stuff that the slaveMasters = me or marcus or igor or alain :) should integrate. Stef On Apr 6, 2011, at 6:01 PM, Igor Stasenko wrote: > okay.. i found one bug > > forgot to add cellPositioning: #leftCenter; for colum wrapper morph > > > -- > Best regards, > Igor Stasenko AKA sig. >
Re: [Pharo-project] Links section for url shortcuts in the Pharo website
Hi Mariano They are right there, on the front page. I recently moved them up so they even show without scrolling. Cheers, Adrian On Apr 6, 2011, at 15:03 , Mariano Martinez Peck wrote: > Hi Adrian. Lots of times I found myself trying to remember the Pharo url > shortcuts. I mean all of these: > > http://www.pharo-project.org/pharo-download/stable-core > http://www.pharo-project.org/pharo-download/stable > http://www.pharo-project.org/pharo-download/unstable-core > http://www.pharo-project.org/pharo-download/unstable > > http://issues.pharo-project.org > http://ci.pharo-project.org > http://book.pharo-project.org > http://wiki.pharo-project.org > > Can we create a new section somewhere in the Pharo website and list all > those links ? > > Thanks a lot in advance, > > -- > Mariano > http://marianopeck.wordpress.com
Re: [Pharo-project] Metacello chapter
Thanks you all. If you find problems or errors let us know. The chapter is now available on the inria gforge. Stef >> here is a new version of the metacello chapter. >> So we wrote it, rewrote it, rerewrote it. >> Now if this is of interest for you you can read it. >> >> But if you don't it means that I'm losing my time and I should stop writing >> and like >> that you can cry that there is no doc about Pharo. >> > > Well written, article/book class documentation, like the PBE & Seaside book, > and chapters like the one above, are really important. > I know this takes a lot of time, so thanks for the effort! > > Sven
Re: [Pharo-project] Question about the Refactoring Browser
>> If I understand correctly I can get a refactoring code model of the unloaded >> code, > > I do not think so. > Even if we are working on Ring just for this scenario I doubt it worked by > default. Sure it works by default. Cheers, Lukas -- Lukas Renggli www.lukas-renggli.ch
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
YES!YES!YES! It is cool to see your impact on them. Excellent it will really helps bringing pharo IDE to the next level. Stef On Apr 6, 2011, at 2:11 PM, Igor Stasenko wrote: > On 6 April 2011 13:16, Stéphane Ducasse wrote: >> Because once people are dependent and drug addict then they will spend time >> fixing it :) >> >> No seriously this is mega hyper hyper important that we get >>- solid scalable listMorph and treeMorph >> So the best way is to stress it. >> >> The second answer is that nautilus is cool and needs tree :) >> > i second that. > trees and lists are basic widgets which could be used for different means. > So why we should limit ourselves and use some crappy lists to mimic > tree, instead of using trees, and improving this widget and making it > work well. > > -- > Best regards, > Igor Stasenko AKA sig. >
Re: [Pharo-project] Question about the Refactoring Browser
Hi jan > Thanks, > > If I understand correctly I can get a refactoring code model of the unloaded > code, I do not think so. Even if we are working on Ring just for this scenario I doubt it worked by default. > but I cannot run the code critics on the model. > > Ok, I will have a look what functionality this model provides. And I have to > figure out how to construct this model using a collection of Monticello > packages. May be you can be interested by RING: the new source code meta model developed by Veronica (the woman behind Torch) She did an excellent job and we need people to use it and give feedback. Our vision is that we want to use RING (a meta model with the same interface as the one of the Smalltalk runobject) so that we can do remote access file browsing version comparison using the same tools. We have a paper under submission if you are interested. Stef > > Jan. > > > > On Wed, Apr 6, 2011 at 2:53 PM, Mariano Martinez Peck > wrote: > This week there was similar thread: > http://forum.world.st/Code-Critics-for-unloaded-projects-td3425020.html > > > On Wed, Apr 6, 2011 at 2:47 PM, Jan van de Sandt wrote: > Hi, > > I want to analyze some Smalltalk code in a collection of Monticello packages > without actually loading these packages in the image. Can I use the > Refactoring Browser for this? > > Jan. > > > > -- > Mariano > http://marianopeck.wordpress.com > >
Re: [Pharo-project] SmalltalkHub going beta in a week
What we ask is: - scripting api so that we do not have to click click click click but write programs - tagging of projects - management of projects (admin I want to be able to tag projects with students and do not see them). - handling of ^%$$%&*#^&*^$&$* long list of any items - in the future: a solid backend Basically we need scalability at the interface level. Now INRIA gracefully will offer a real back up of data (replicated in three different labs) and people will be able to use smalltalkhub and burn the machine processors :). Stef On Apr 6, 2011, at 2:15 PM, Fernando Olivero wrote: > Excellent ! It's time to move past squeaksource.com. > > Would be nice to know the features that will be offered, at least in > comparison with current squeaksource (besides the image crashing, and > bothering the always helpful Bern phd students). > > Fernando > > > On Wed, Apr 6, 2011 at 2:00 PM, Mariano Martinez Peck > wrote: >> >> >> On Wed, Apr 6, 2011 at 1:45 PM, Nicolas Petton >> wrote: >>> >>> Le mercredi 06 avril 2011 à 13:07 +0200, Tudor Girba a écrit : Phenomenal stuff :). I cannot wait to use it. Will there be a possibility to migrate the existing squeaksource there? >>> >>> There is nothing at the moment to migrate. >>> >>> I guess you'll just have to move your packages from squeaksource to >>> smalltalkhub, so a simple script could do the trick. >> >> This is awesome. THanks ESUG! >> >> And the history? I mean, is this a new front end for a squeaksource server >> ? >> >> thanks >> >>> >>> Cheers, >>> Nicolas >>> >>> -- >>> Nicolas Petton >>> http://www.nicolas-petton.fr >>> >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >
[Pharo-project] Delay bug
Well, we have been having problems with applications appearing to hang every 6 days or so (sound familiar?). I have identified a bug in the Delay implementation, rather obscure, but highlighted by our applications that make HEAVY use of processes/(tight, a few tens of milliseconds)delays/semaphores etc. Naturally due to an edge case on millisecond clock rollover... Affects all Squeak/Pharo versions, as far as I can tell. (It is separate from the OSProcess issues I have posted about a few weeks ago). I've developed a potential fix, though I'll have to let you all know whether (hopefully) successful in a week or two... fingers crossed! I hope it is fixable, last hurdle for business applications, from our point of view. I'll post details when fix confirmed or failed then. Regards, Gary
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
okay.. i found one bug forgot to add cellPositioning: #leftCenter; for colum wrapper morph -- Best regards, Igor Stasenko AKA sig. Tree2.3.cs Description: Binary data
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
On 6 April 2011 17:22, Igor Stasenko wrote: > On 6 April 2011 15:52, Alain Plantec wrote: >> Le 06/04/2011 15:14, Igor Stasenko a écrit : >>> >>> and a little more cleanup (should be applied after theTreee) >>> >>> now a block which responsible for providing an icon for concrete item, >>> actually could provide a morph, >>> which means that one could put there an iconic button instead of simple >>> image. >> >> super. >> I've tested and it seems ok for MorphTreeMorph >> >> LazyMorphTreeMorph seems to have row refresh/building problem now. >> try with >> LazyClassListExample new openOn: Object. >> then move the scrollbar to the bottom, then click on the arrow button to get >> the entire list >> and then scroll manually. >> I've observed that some rows are not built correctly now. >> I can't be sure that it is due to your improvements >> > hmm.. on my image it works fine. > > maybe i didn't included something into changeset... let me take a look > no, it works fine. >> Alain >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
On 6 April 2011 15:52, Alain Plantec wrote: > Le 06/04/2011 15:14, Igor Stasenko a écrit : >> >> and a little more cleanup (should be applied after theTreee) >> >> now a block which responsible for providing an icon for concrete item, >> actually could provide a morph, >> which means that one could put there an iconic button instead of simple >> image. > > super. > I've tested and it seems ok for MorphTreeMorph > > LazyMorphTreeMorph seems to have row refresh/building problem now. > try with > LazyClassListExample new openOn: Object. > then move the scrollbar to the bottom, then click on the arrow button to get > the entire list > and then scroll manually. > I've observed that some rows are not built correctly now. > I can't be sure that it is due to your improvements > hmm.. on my image it works fine. maybe i didn't included something into changeset... let me take a look > Alain > > > -- Best regards, Igor Stasenko AKA sig.
[Pharo-project] Metacello chapter
On 06 Apr 2011, at 09:58, Stéphane Ducasse wrote: > here is a new version of the metacello chapter. > So we wrote it, rewrote it, rerewrote it. > Now if this is of interest for you you can read it. > > But if you don't it means that I'm losing my time and I should stop writing > and like > that you can cry that there is no doc about Pharo. > Well written, article/book class documentation, like the PBE & Seaside book, and chapters like the one above, are really important. I know this takes a lot of time, so thanks for the effort! Sven
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
On Apr 6, 2011, at 1:19 PM, Stéphane Ducasse wrote: > > On Apr 5, 2011, at 2:32 PM, Fernando Olivero wrote: > >> Hi Ben, i was thinking about the discussion of the menus: >> >> Since you are using menu pragma builder, and have explicit views for >> each tool, then the CodeHolder hierarchy is no longer needed. Because >> the specialized views get the behavior for answering the actions in >> the menus (which currently is spread across the StringHolder >> hierarchy). > > I would say yes but I will let ben replied with more depth if necessary. There is two kinds of menus, menus provided by the lists/trees and menus provided by the pluggable text morph. They're different because first ones really act on the model elements (here classes/methods/etc), when second ones act on text For lists/trees menus, because they act on your model have to be handled locally ( by your model or your view depending of the action ). For text menus, they act on text, and will always act on text, so they should be managed by a kind of TextModel, because it's not the role of your Browser to tell how to implement copy/paste, or implementors :) > > >> So this is the main reason why you simple need a pluggable text model, >> for the model of the views. And a pluggable TextModel (or StringHolder >> in Pharo) would suffice? Is this correct? >> >> >> Thanks, >> Fernando > StringHolder shouldn't exist anymore :) For Nautilus, menus actions are handled by the view, but could/should be moved in the model for some of them, but it can be a bit hard to separate the ones only related to the view, and ones relatives to the model ... And text menus are handled by the PluggableTextMorph whose model is SmalltalkEditor. So it's SmalltalkEditor responsibility to know how to look for senders/implementors/etc I hope it answer your question ^^ Ben
Re: [Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
On Apr 6, 2011, at 4:48 PM, Torsten Bergmann wrote: > Geert wrote: >> I reckon the OneClick should also use this excellent Pharo branded Cog VM :) > > We already take care. I mailed it to Marcus, I guess he has to > find the time to integrate it. > Yes, OOPSLA deadline is on Friday... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
[Pharo-project] Draft Pharo 1.2.1 Release Announcement
Laurent wrote: >I've started :) http://linuxfr.org/news/pharo12 I guess James Robertson was first (when we still talked about it). See http://www.jarober.com/blog/blogView?showComments=true&printTitle=Pharo_1.2.1_is_Out&entry=3479531512 and it is therefore already on http://planet.smalltalk.org However - I now followed too: http://astares.blogspot.com Bye T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
[Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
Geert wrote: >I reckon the OneClick should also use this excellent Pharo branded Cog VM :) We already take care. I mailed it to Marcus, I guess he has to find the time to integrate it. Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone
Re: [Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
I reckon the OneClick should also use this excellent Pharo branded Cog VM :) -- View this message in context: http://forum.world.st/ANN-Pharo-1-2-1-Setup-for-Win32-including-CogVM-tp3430814p3430887.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
On Wed, Apr 6, 2011 at 3:47 PM, Mariano Martinez Peck wrote: > But when are we going to send this mail to this mailing list? and > pharo-users? etc... > can we start to buzz arround ? I've started :) http://linuxfr.org/news/pharo12 Laurent. > > > > On Wed, Apr 6, 2011 at 10:51 AM, Adrian Lienhard wrote: > >> Thanks for checking, Mariano. I fixed it. >> >> Adrian >> >> On Apr 6, 2011, at 10:09 , Mariano Martinez Peck wrote: >> >> > I think this part is wrong (see screenshot) >> > >> > >> > >> > On Wed, Apr 6, 2011 at 10:05 AM, Adrian Lienhard >> wrote: >> > On Apr 5, 2011, at 22:27 , Adrian Lienhard wrote: >> > >> > > As far as I see there's one thing missing on the website: the download >> sticker for the one click image (top right on the page) still points to >> 1.1.1. I'll try to change the sticker and link tomorrow morning. >> > >> > The new sticker is online. I've linked to the non-COG one-click image. >> Is that what we want? >> > >> > I've also updated the one-click image links on >> http://www.pharo-project.org/pharo-download >> > >> > So, as far as I can tell, the website is ready. >> > >> > Cheers >> > Adrian >> > >> > >> > >> > -- >> > Mariano >> > http://marianopeck.wordpress.com >> > >> > >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
Le 06/04/2011 15:14, Igor Stasenko a écrit : and a little more cleanup (should be applied after theTreee) now a block which responsible for providing an icon for concrete item, actually could provide a morph, which means that one could put there an iconic button instead of simple image. super. I've tested and it seems ok for MorphTreeMorph LazyMorphTreeMorph seems to have row refresh/building problem now. try with LazyClassListExample new openOn: Object. then move the scrollbar to the bottom, then click on the arrow button to get the entire list and then scroll manually. I've observed that some rows are not built correctly now. I can't be sure that it is due to your improvements Alain
Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
But when are we going to send this mail to this mailing list? and pharo-users? etc... can we start to buzz arround ? On Wed, Apr 6, 2011 at 10:51 AM, Adrian Lienhard wrote: > Thanks for checking, Mariano. I fixed it. > > Adrian > > On Apr 6, 2011, at 10:09 , Mariano Martinez Peck wrote: > > > I think this part is wrong (see screenshot) > > > > > > > > On Wed, Apr 6, 2011 at 10:05 AM, Adrian Lienhard > wrote: > > On Apr 5, 2011, at 22:27 , Adrian Lienhard wrote: > > > > > As far as I see there's one thing missing on the website: the download > sticker for the one click image (top right on the page) still points to > 1.1.1. I'll try to change the sticker and link tomorrow morning. > > > > The new sticker is online. I've linked to the non-COG one-click image. Is > that what we want? > > > > I've also updated the one-click image links on > http://www.pharo-project.org/pharo-download > > > > So, as far as I can tell, the website is ready. > > > > Cheers > > Adrian > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
Please, for the important ANN don't forget the pharo-users ;) On Wed, Apr 6, 2011 at 3:39 PM, Torsten Bergmann wrote: > Hi, > > now that Pharo 1.2.1. is available on the website > I've also updated the Win32 Setup. You can grab it here: > > > https://gforge.inria.fr/frs/download.php/28467/setup_pharo1.2.1-12345-release11.04.06.exe > > Compared to the one click (26MB) this download is only 13MB > in size and provides better windows integration. So if > you are on Windows you can use this > > Whats new: > == > - Pharo 1.2.1.#12345 is included > - Cog VM is included (CogVM VM.r2378) with a custom CogVM/Pharo icon > > Maybe Adrian is able to change: > http://www.pharo-project.org/pharo-download > to point to the new executable. > > Thx > T. > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl > > -- Mariano http://marianopeck.wordpress.com
[Pharo-project] [ANN] Pharo 1.2.1. Setup for Win32 (including CogVM)
Hi, now that Pharo 1.2.1. is available on the website I've also updated the Win32 Setup. You can grab it here: https://gforge.inria.fr/frs/download.php/28467/setup_pharo1.2.1-12345-release11.04.06.exe Compared to the one click (26MB) this download is only 13MB in size and provides better windows integration. So if you are on Windows you can use this Whats new: == - Pharo 1.2.1.#12345 is included - Cog VM is included (CogVM VM.r2378) with a custom CogVM/Pharo icon Maybe Adrian is able to change: http://www.pharo-project.org/pharo-download to point to the new executable. Thx T. -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
Re: [Pharo-project] Links section for url shortcuts in the Pharo website
heheheheh I should have checked before...sorry for the noise..I checked a couple of days ago and I forget to send the email. Today I remembered that but I didn't check the website.. thanks Adrian! mariano On Wed, Apr 6, 2011 at 3:17 PM, Marcus Denker wrote: > > On Apr 6, 2011, at 3:03 PM, Mariano Martinez Peck wrote: > > Hi Adrian. Lots of times I found myself trying to remember the Pharo url > shortcuts. I mean all of these: > > http://www.pharo-project.org/pharo-download/stable-core > http://www.pharo-project.org/pharo-download/stable > http://www.pharo-project.org/pharo-download/unstable-core > http://www.pharo-project.org/pharo-download/unstable > > http://issues.pharo-project.org > http://ci.pharo-project.org > http://book.pharo-project.org > http://wiki.pharo-project.org > > Can we create a new section somewhere in the Pharo website and list all > those links ? > > > Adrian did put them directl on the front page yesterday: > > http://www.pharo-project.org/home > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] Metacello chapter
I read it (Mariano sent to me last week, because I needed to build some complex configuration). I think it is really helpful, clear and well written :) In my opinion, is a great chapter! cheers, Esteban El 06/04/2011, a las 4:58a.m., Stéphane Ducasse escribió: > Hi guys > > here is a new version of the metacello chapter. > So we wrote it, rewrote it, rerewrote it. > Now if this is of interest for you you can read it. > > But if you don't it means that I'm losing my time and I should stop writing > and like > that you can cry that there is no doc about Pharo. > > > > Stef >
Re: [Pharo-project] Question about the Refactoring Browser
Thanks, If I understand correctly I can get a refactoring code model of the unloaded code, but I cannot run the code critics on the model. Ok, I will have a look what functionality this model provides. And I have to figure out how to construct this model using a collection of Monticello packages. Jan. On Wed, Apr 6, 2011 at 2:53 PM, Mariano Martinez Peck wrote: > This week there was similar thread: > http://forum.world.st/Code-Critics-for-unloaded-projects-td3425020.html > > > On Wed, Apr 6, 2011 at 2:47 PM, Jan van de Sandt wrote: > >> Hi, >> >> I want to analyze some Smalltalk code in a collection of Monticello >> packages without actually loading these packages in the image. Can I use the >> Refactoring Browser for this? >> >> Jan. >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >
Re: [Pharo-project] Links section for url shortcuts in the Pharo website
On Apr 6, 2011, at 3:03 PM, Mariano Martinez Peck wrote: > Hi Adrian. Lots of times I found myself trying to remember the Pharo url > shortcuts. I mean all of these: > > http://www.pharo-project.org/pharo-download/stable-core > http://www.pharo-project.org/pharo-download/stable > http://www.pharo-project.org/pharo-download/unstable-core > http://www.pharo-project.org/pharo-download/unstable > > http://issues.pharo-project.org > http://ci.pharo-project.org > http://book.pharo-project.org > http://wiki.pharo-project.org > > Can we create a new section somewhere in the Pharo website and list all those > links ? > Adrian did put them directl on the front page yesterday: http://www.pharo-project.org/home -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
and a little more cleanup (should be applied after theTreee) now a block which responsible for providing an icon for concrete item, actually could provide a morph, which means that one could put there an iconic button instead of simple image. -- Best regards, Igor Stasenko AKA sig. Tree2.1.cs Description: Binary data
Re: [Pharo-project] [Vm-dev] OSS sound plugin.
Hi. Does someone know if this was finally done? On Tue, Mar 15, 2011 at 11:27 PM, Lemuus wrote: > > Hi, is it possible to include the vm-sound-OSS sound plugin in the cog > build on Hudson?. This is the only plugin that seems to work on linux. > Thanks. > Daniel Galdames G. > > > -- Mariano http://marianopeck.wordpress.com
[Pharo-project] Links section for url shortcuts in the Pharo website
Hi Adrian. Lots of times I found myself trying to remember the Pharo url shortcuts. I mean all of these: http://www.pharo-project.org/pharo-download/stable-core http://www.pharo-project.org/pharo-download/stable http://www.pharo-project.org/pharo-download/unstable-core http://www.pharo-project.org/pharo-download/unstable http://issues.pharo-project.org http://ci.pharo-project.org http://book.pharo-project.org http://wiki.pharo-project.org Can we create a new section somewhere in the Pharo website and list all those links ? Thanks a lot in advance, -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] Question about the Refactoring Browser
This week there was similar thread: http://forum.world.st/Code-Critics-for-unloaded-projects-td3425020.html On Wed, Apr 6, 2011 at 2:47 PM, Jan van de Sandt wrote: > Hi, > > I want to analyze some Smalltalk code in a collection of Monticello > packages without actually loading these packages in the image. Can I use the > Refactoring Browser for this? > > Jan. > -- Mariano http://marianopeck.wordpress.com
[Pharo-project] Question about the Refactoring Browser
Hi, I want to analyze some Smalltalk code in a collection of Monticello packages without actually loading these packages in the image. Can I use the Refactoring Browser for this? Jan.
Re: [Pharo-project] Fwd: Actions done in 1.3
On Wed, Apr 6, 2011 at 1:55 PM, Igor Stasenko wrote: > -- Forwarded message -- > From: Igor Stasenko > Date: 6 April 2011 13:55 > Subject: Re: [Pharo-project] Actions done in 1.3 > To: laurent laffont > > > On 6 April 2011 10:30, laurent laffont wrote: > > > > On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko > wrote: > >> > >> Planning is also important. > >> > >> Time is good, but another thing is i think we should think about, > >> what features we want to be in new release, and do not release until > >> they delivered. > > > > I don't really like this. I prefer rhythm, agility. Timeboxing enables > > maximum value in each release. If a feature is really important, it will > be > > on time. If not on time, it means it was no so important. > > Always green test is a must-have. > > > >> > >> Besides bug fixing and minor improvements, there should be some > >> functionality which we want to have in new release, > > > > That should be a goal, but don't delay a release because the feature is > not > > here. If releases are often ( for example every 3 months), shorter, it > won't > > be a big problem to wait for the next one. > > I prefer to have a release *now* without my feature and wait 3 months for > > the next release than no release and waiting for 3 months more with less > and > > less energy. > > > > But you don't have to wait, if you want to stay on bleeding edge, you > know how to do that. > Just go to hudson and dowload freshly built 1.3 image. > I won't do this for production. We need a officially released image. Because if you can pick any image at any moment and declare it new release, > then i don't understand why do we need releases at all? > Because people build applications / frameworks they declare compatible with a fixed version of Pharo. > What makes release to be release , when you can download latest > version at any moment? > The date :) Ubuntu is released every 6 months. That gives a rhythm. Integrates new stuff, freeze, release. Same for Gnome and KDE. Linux kernel has a 2 weeks merge window then go rc. We have learned the benefits of fixed iteration with agile methods & extreme programming. > That's why i saying that from release to release cleanup and fixes is > good, but there should be some major functional changes, > which worth to be labeled as a new version. > And if you don't have them, then there is no point to make a release. > In three months there's a lot of stuff which enters Pharo. That's enough for me to justify a release and get feedback from users. Laurent. > > > Laurent. > > > > > -- > Best regards, > Igor Stasenko AKA sig. > > > > -- > Best regards, > Igor Stasenko AKA sig. > >
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
I think that as soon as MorphTreeMorph is improved, you can use it for SMx, or take it as it is right now, and apply fixes ^^ Ben On Apr 6, 2011, at 10:17 AM, Fernando Olivero wrote: > what about my initial question? it got buried beneath other > discussions in this thread. > Ben, can you give your opinion ? Im interested because for the SMx > port, this would help in narrowing the classes to import. > > Fernando > > On Wed, Apr 6, 2011 at 9:08 AM, Tudor Girba wrote: >> Hi, >> >> On 6 Apr 2011, at 08:16, Alain Plantec wrote: >> >>> Le 05/04/2011 22:03, Alain Plantec a écrit : Le 05/04/2011 20:57, Stéphane Ducasse a écrit : > A new browser :) > Supporting >- groups >- package >- declarative menus >- environment selection >- scoped actions >- soon refactoring > > but right now a bit too slow because of the HUGGEE trees build by > TreeMorphTreeMorph yes, maybe MorphTreeMorph is not the good tree to use here. why not use a simpler one ? >>> or try with LazyMorphTreeMorph even it should be improved. (it should be >>> changed to build the list in background). >> >> That would be super cool :) >> >> Doru >> >> Alain >> Squeaksource simply says "A new browser" >> >> Cheers, >> Alexandre > > >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> >> >
Re: [Pharo-project] SmalltalkHub going beta in a week
Excellent ! It's time to move past squeaksource.com. Would be nice to know the features that will be offered, at least in comparison with current squeaksource (besides the image crashing, and bothering the always helpful Bern phd students). Fernando On Wed, Apr 6, 2011 at 2:00 PM, Mariano Martinez Peck wrote: > > > On Wed, Apr 6, 2011 at 1:45 PM, Nicolas Petton > wrote: >> >> Le mercredi 06 avril 2011 à 13:07 +0200, Tudor Girba a écrit : >> > Phenomenal stuff :). I cannot wait to use it. Will there be a >> > possibility to migrate the existing squeaksource there? >> >> There is nothing at the moment to migrate. >> >> I guess you'll just have to move your packages from squeaksource to >> smalltalkhub, so a simple script could do the trick. > > This is awesome. THanks ESUG! > > And the history? I mean, is this a new front end for a squeaksource server > ? > > thanks > >> >> Cheers, >> Nicolas >> >> -- >> Nicolas Petton >> http://www.nicolas-petton.fr >> >> > > > > -- > Mariano > http://marianopeck.wordpress.com > >
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
On 6 April 2011 13:16, Stéphane Ducasse wrote: > Because once people are dependent and drug addict then they will spend time > fixing it :) > > No seriously this is mega hyper hyper important that we get > - solid scalable listMorph and treeMorph > So the best way is to stress it. > > The second answer is that nautilus is cool and needs tree :) > i second that. trees and lists are basic widgets which could be used for different means. So why we should limit ourselves and use some crappy lists to mimic tree, instead of using trees, and improving this widget and making it work well. -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] Transcript rant
On 6 April 2011 13:54, Fernando Olivero wrote: > Hi Stef, i will as an initial step take Igor's suggestion and make > Transcript a global wich points to an instance of TranscriptModel ( > the new name i propose for the current class taken from CUIS). > > I still believe that composition is better then inheritance for > handling different behaviors of the Transcript, so i argue against > making it a subclass of WriteStream and making it polymorphic with a > write stream instead. > That's totally not my concern. As long as thing which sits there responds to writestream protocol , i don't care about rest. > Fernando > > > On Tue, Apr 5, 2011 at 8:54 PM, Stéphane Ducasse > wrote: >> Guys >> >> I need an update status. >> Do we keep or not the changes in the system? >> >> I will come back to you until we reach a decision :) >> >> Stef >> >> > > -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] Metacello chapter
On Wed, Apr 6, 2011 at 9:58 AM, Stéphane Ducasse wrote: > Hi guys > > here is a new version of the metacello chapter. > So we wrote it, rewrote it, rerewrote it. > Now if this is of interest for you you can read it. > > But if you don't it means that I'm losing my time and I should stop writing > and like > that you can cry that there is no doc about Pharo. > > > > > Stef > > > -- Mariano http://marianopeck.wordpress.com
Re: [Pharo-project] SmalltalkHub going beta in a week
On Wed, Apr 6, 2011 at 1:45 PM, Nicolas Petton wrote: > Le mercredi 06 avril 2011 à 13:07 +0200, Tudor Girba a écrit : > > Phenomenal stuff :). I cannot wait to use it. Will there be a possibility > to migrate the existing squeaksource there? > > There is nothing at the moment to migrate. > > I guess you'll just have to move your packages from squeaksource to > smalltalkhub, so a simple script could do the trick. > This is awesome. THanks ESUG! And the history? I mean, is this a new front end for a squeaksource server ? thanks > Cheers, > Nicolas > > -- > Nicolas Petton > http://www.nicolas-petton.fr > > > -- Mariano http://marianopeck.wordpress.com
[Pharo-project] Fwd: Actions done in 1.3
-- Forwarded message -- From: Igor Stasenko Date: 6 April 2011 13:55 Subject: Re: [Pharo-project] Actions done in 1.3 To: laurent laffont On 6 April 2011 10:30, laurent laffont wrote: > > On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko wrote: >> >> Planning is also important. >> >> Time is good, but another thing is i think we should think about, >> what features we want to be in new release, and do not release until >> they delivered. > > I don't really like this. I prefer rhythm, agility. Timeboxing enables > maximum value in each release. If a feature is really important, it will be > on time. If not on time, it means it was no so important. > Always green test is a must-have. > >> >> Besides bug fixing and minor improvements, there should be some >> functionality which we want to have in new release, > > That should be a goal, but don't delay a release because the feature is not > here. If releases are often ( for example every 3 months), shorter, it won't > be a big problem to wait for the next one. > I prefer to have a release *now* without my feature and wait 3 months for > the next release than no release and waiting for 3 months more with less and > less energy. > But you don't have to wait, if you want to stay on bleeding edge, you know how to do that. Just go to hudson and dowload freshly built 1.3 image. Because if you can pick any image at any moment and declare it new release, then i don't understand why do we need releases at all? What makes release to be release , when you can download latest version at any moment? That's why i saying that from release to release cleanup and fixes is good, but there should be some major functional changes, which worth to be labeled as a new version. And if you don't have them, then there is no point to make a release. > Laurent. > -- Best regards, Igor Stasenko AKA sig. -- Best regards, Igor Stasenko AKA sig.
Re: [Pharo-project] Transcript rant
Hi Stef, i will as an initial step take Igor's suggestion and make Transcript a global wich points to an instance of TranscriptModel ( the new name i propose for the current class taken from CUIS). I still believe that composition is better then inheritance for handling different behaviors of the Transcript, so i argue against making it a subclass of WriteStream and making it polymorphic with a write stream instead. Fernando On Tue, Apr 5, 2011 at 8:54 PM, Stéphane Ducasse wrote: > Guys > > I need an update status. > Do we keep or not the changes in the system? > > I will come back to you until we reach a decision :) > > Stef > >
Re: [Pharo-project] SmalltalkHub going beta in a week
Le mercredi 06 avril 2011 à 13:07 +0200, Tudor Girba a écrit : > Phenomenal stuff :). I cannot wait to use it. Will there be a possibility to > migrate the existing squeaksource there? There is nothing at the moment to migrate. I guess you'll just have to move your packages from squeaksource to smalltalkhub, so a simple script could do the trick. Cheers, Nicolas -- Nicolas Petton http://www.nicolas-petton.fr
Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph
Okay, here the updated version. GTCoder open looks fine Settings look fine. and SimpleGridExample new open looking fine as well -- Best regards, Igor Stasenko AKA sig. theTreee.8.cs Description: Binary data
Re: [Pharo-project] jtalk fun
On Wed, Apr 6, 2011 at 12:48 PM, Nicolas Petton wrote: > Le mercredi 06 avril 2011 à 12:28 +0200, Noury Bouraqadi a écrit : > > Cool. But how do we move parts? > > Hmm, you don't... > > I only wrote the field and pieces, the game isn't working yet (and I > didn't think someone would find it... kudos to Laurent :-) > Ahaha I was just looking for examples and this is in the example category ;) Laurent > > Cheers, > Nico > > > > > > On 5 avr. 2011, at 15:16, laurent laffont wrote: > > > > > Go to http://jtalk-project.org/ > > > > > > Open development tools -> Workspace > > > > > > Evaluate: > > > > > > Tetris new appendToJQuery: 'body' asJQuery > > > > > > play. > > > > > > > > > Laurent. > > > > Noury Bouraqadi > > http://car.mines-douai.fr/noury > > -- > > -6th National Conference on > > “Control Architecture of Robots” > > 24-25 may 2011, Grenoble area, France > > http://car2011.inrialpes.fr/ > > > > -19th ESUG International Smalltalk Conference > > 22-26 August 2011, Edinburgh, UK > > http://www.esug.org/Conferences/2011 > > > > -19èmes Journées Francophones sur les Systèmes Multi-Agents (JFSMA’11) > > http://www.univ-valenciennes.fr/congres/jfsma2011/ > > 17-19 Octobre 2011, Valenciennes, France > > > > > > > > > > > > > > -- > Nicolas Petton > http://www.nicolas-petton.fr > > >
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
It works. Toon, am I wrong? Cheers, Doru On 6 Apr 2011, at 13:18, Stéphane Ducasse wrote: > > On Apr 6, 2011, at 1:08 PM, Tudor Girba wrote: > >> Hi, >> >> Indeed, it would be great to have a Debugger model. Toon produced one in the >> context of the Glamorous Toolkit. Perhaps it would be good if we merged it >> in the Core. > > As soon as it works I want that in the core :) > imagine a model not mixed with UI concerned :) > Stef > >> >> Cheers, >> Doru >> >> >> On 6 Apr 2011, at 12:54, Michael Roberts wrote: >> >>> Ok. And is the idea to build a new core debugger in this effort? I wanted >>> to check we would only build 1 debugger model; and to know where it is. (I >>> only see one in glamourst source). >>> >>> Thanks >>> Mike >>> >>> On 6 Apr 2011, at 07:01, Stéphane Ducasse wrote: >>> It is not. The idea is to have a default browser and set of tools that we can use in bare core image and that are not based on toolBuilder or stringHolder. After if Glamour produces a nice IDE then we can load it and use it. In addition benjamin is fixing a lot of problems in default widgets like multiple selection, hilighting Stef > Hi, how does it relate to glamourost? > > thanks, > Mike > > On Tue, Apr 5, 2011 at 7:57 PM, Stéphane Ducasse > wrote: >> >> On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote: >> >>> Hi Guys, >>> >>> Maybe I missed part of the discussion, but what is Nautilus? >> >> A new browser :) >> Supporting >>- groups >>- package >>- declarative menus >>- environment selection >>- scoped actions >>- soon refactoring >> >> but right now a bit too slow because of the HUGGEE trees build >> by TreeMorphTreeMorph >> >>> Squeaksource simply says "A new browser" >>> >>> Cheers, >>> Alexandre >> >> >> > >>> >> >> -- >> www.tudorgirba.com >> >> "Being happy is a matter of choice." >> >> >> >> > > -- www.tudorgirba.com "We are all great at making mistakes."
Re: [Pharo-project] Issue 3966 in pharo: String>>lines misses tests
Comment #2 on issue 3966 by stephane...@gmail.com: String>>lines misses tests http://code.google.com/p/pharo/issues/detail?id=3966 tx!
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
On Apr 5, 2011, at 2:32 PM, Fernando Olivero wrote: > Hi Ben, i was thinking about the discussion of the menus: > > Since you are using menu pragma builder, and have explicit views for > each tool, then the CodeHolder hierarchy is no longer needed. Because > the specialized views get the behavior for answering the actions in > the menus (which currently is spread across the StringHolder > hierarchy). I would say yes but I will let ben replied with more depth if necessary. > So this is the main reason why you simple need a pluggable text model, > for the model of the views. And a pluggable TextModel (or StringHolder > in Pharo) would suffice? Is this correct? > > Thanks, > Fernando >
Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy
Geert Claes wrote: > > How does one load Nautilus? I tried by adding the nautilus repository and > using the ConfigurationOf on a clean 1.2 OneClick but I get a DNU > readStream? > Mmm, seems to be a network issue because I get the same message for other stuff :( -- View this message in context: http://forum.world.st/abouth-nautilus-and-the-removal-of-CodeHolder-hierarchy-tp3427890p3430512.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
