Hi, don't get too hung up on the 3 hr+, it's a really old machine running Xubuntu I use to test my stuff runs lean. Better to look at the 'normal' machine's time of 71 minutes, vs 15. Ubuntu, with no nasties running. I previously reported that I find System update slow. Mariano, do you run in a folder with a package cache present? I run in a clean install, so it has to download everything. The process I use: create new folder seaside3buildTest2 paste and unzip a Seaside-3.0a5.app.zip one clickloadprocess.txt, to have a full environment paste and unzip pharo1.0-10505-rc1dev10.01.1.zip copy pharo1.0-10505-rc1dev10.01.1.image .changes into Resources folder delete Seaside.image, .changes edit Seaside.sh to be pharo1.0-10505-rc1dev10.01.1.sh, opening pharo1.0-10505-rc1dev10.01.1.image pharo1.0-10505-rc1dev10.01.1.sh open with sh I find it most convenient to start with a one click image like that. MessageTally attached. Also found my first bug: MessageTally tallySends: [Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRefactoringBrowser'; load]. Throws code simulation error in Project class>>spawnNewProcess UIProcess := [ [World doOneCycle. Processor yield. false] whileFalse: []. ] newProcess priority: Processor userSchedulingPriority. UIProcess resume ...Stan |
In reply to this post by Miguel Cobá
Also, the changes files, shouldn't be compressed for each RC and for the In addition to do a Smalltalk condenseChanges is it necessary to do also a Smalltalk condenseSources ? I ask because I have really no idea. Thanks Mariano Also, the packages.txt file talks about PharoCore1.0 (#10505). Has _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
On Jan 11, 2010, at 4:37 PM, Mariano Martinez Peck wrote: > > > Also, the changes files, shouldn't be compressed for each RC and for the > final release? > > > In addition to do a Smalltalk condenseChanges is it necessary to do also a Smalltalk condenseSources ? I ask because I have really no idea. > No, we did that when going RC1... there is already a PharoV10.sources. Marcus _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stan Shepherd
On Mon, Jan 11, 2010 at 3:41 PM, Stan Shepherd <[hidden email]> wrote:
Are you sure ? ;) Also found my first bug: _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Miguel Cobá
http://code.google.com/p/pharo/issues/detail?id=1778
Stef On Jan 9, 2010, at 11:59 PM, Miguel Enrique Cobá Martinez wrote: >> >> MCFileBasedRepository flushAllCaches. >> MCDefinition clearInstances. >> Smalltalk removeEmptyMessageCategories. >> Utilities cleanseOtherworldlySteppers. >> Undeclared removeUnreferencedKeys. >> Categorizer sortAllCategories. >> Symbol compactSymbolTable. >> Smalltalk at: #ReleaseBuilderDeveloper ifPresent: [:builder | >> builder new fixObsoleteReferences]. >> RequiredSelectors initialize. >> ProvidedSelectors initialize. >> LocalSends initialize. >> Smalltalk organization removeEmptyCategories. >> SystemBrowser removeObsolete. >> TheWorldMenu removeObsolete. >> AppRegistry removeObsolete. >> Set rehashAllSets. >> Smalltalk cleanOutUndeclared. >> Smalltalk garbageCollect. >> > > Respect to this list, and maybe this should be a ticket. Shouldn't be > better to have an established message to cleanup the image on release. > Something like the cleanUpForImageRelease but generalized and then, the > classes that need to do something like this, they implement that > message. > > So on release a new image version you only call something like > > Smalltalk cleanUpForImageRelease. > > and inside it search all the classes that implements the message and > call them. So, your post-script becomes a single line and each package > is responsible of putting inside its own cleanUpForImageRelease whatever > needed to initialize itself. > But well, just an idea for subsequent releases. _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Mariano Martinez Peck
Was there a reason you opted not to include RB spelling? I don't know how may people use it- I find it really handy, so my vote would be for inclusion. ...Stan |
Good question. I really appreacite the feedback. Thanks. No, actually the only reason is because I didn realize it :) because, I don't explicity load RB, it is loaded because as a dependency of OB-refactory, but it only needs the Refactoring-Core, not spelling, and that's why it wasen't loaded. However, it is really easy to change if we want. I just put the complete RB as requiered in in Pharo and that's all. In summary, no problem, if we want, I add it. I don't think even it is much problem to load it. And in the previous images it is was loaded, so, I like to idea to load it. What other things? cheers mariano -- _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stan Shepherd
Hi Stan, can you check if there is another package missing from the previous dev image ?
Thanks! Mariano On Mon, Jan 11, 2010 at 9:45 PM, Stan Shepherd <[hidden email]> wrote:
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stan Shepherd
>
> Was there a reason you opted not to include RB spelling? I don't know how > may people use it- I find it really handy, so my vote would be for > inclusion. if I remember it depends on some mac library Stef _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
>> Was there a reason you opted not to include RB spelling? I don't know how
>> may people use it- I find it really handy, so my vote would be for >> inclusion. > > if I remember it depends on some mac library No, it does not depend on the mac primitive. I've implemented an alternative that works on all platforms, less performant and of a lesser quality, but it should basically work. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Mariano Martinez Peck
Hi Mariano, attached is the list of differences from 10502 to 10505. All missing packages seem to relate to O2, except for Spelling. Is this what you meant? Cheers, ...Stan packagesDiff10502to10505.ods |
In reply to this post by Stéphane Ducasse
There is also an internal spell check, for other platforms. RBInternalSpellChecker. ...Stan |
In reply to this post by Stan Shepherd
On Mon, Jan 11, 2010 at 10:56 PM, Stan Shepherd <[hidden email]> wrote:
did you know about the Gmail feature (it is in Lab) that detects certain key words like "attached" or "attach" and when you are going to send an email, a popup brigns saying "Are you sure you don't have to attach something? " ;) is the list of differences from 10502 to 10505. All But, yes, exactly that. Don't care that there is a changelog.txt for each dev images comparing exactly this, but I had a problem for the moment with that. Thanks a lot. Cheers, ...Stan _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stan Shepherd
On 1/11/2010 10:59 PM, Stan Shepherd wrote:
> There is also an internal spell check, for other platforms. > RBInternalSpellChecker. <broken record on> in Sophie we built a platform independent spell checker </broken record on> ;-) Michael _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stan Shepherd
On Mon, Jan 11, 2010 at 10:59 PM, Stan Shepherd <[hidden email]> wrote:
How do you use it or enable it ? I have been using dev images for two years and I have ever seen a spell checker :( ...Stan _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
>> There is also an internal spell check, for other platforms.
>> RBInternalSpellChecker. > > How do you use it or enable it ? I have been using dev images for two years > and I have ever seen a spell checker :( This is an extension to SmallLint. Like Slime. It is run when you run code critics. Alternatively you can execute it like this: ORLintBrowser openRule: (RBCompositeLintRule rules: (RBCompositeLintRule rulesGroupedFor: RBSpellingRule) name: 'Spelling') environment: (BrowserEnvironment new forPackageNames: #('Kernel' 'Collections-Abstract')) Maybe I should add a menu to the already long refactoring commands? Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Mariano Martinez Peck
Hi, I only browse the forum through Nabble, and it's attaching fine. http://n2.nabble.com/file/n4288408/packagesDiff10502to10505.ods see: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10505-rc1dev10-01-1-td4278312i80.html sorry if it's not coming through on email. Previous file is http://n2.nabble.com/file/n4285691/loadprocess.txt Do those links work? ...Stan |
In reply to this post by Lukas Renggli
> This is an extension to SmallLint. Like Slime. It is run when you run
> code critics. > > Alternatively you can execute it like this: > > ORLintBrowser > openRule: (RBCompositeLintRule rules: (RBCompositeLintRule > rulesGroupedFor: RBSpellingRule) name: 'Spelling') > environment: (BrowserEnvironment new forPackageNames: #('Kernel' > 'Collections-Abstract')) > > Maybe I should add a menu to the already long refactoring commands? With Helvetia you get it live in the text editor as a wavy red line. Along with the other lint rules as a wavy yellow line. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Stan Shepherd
On Mon, Jan 11, 2010 at 11:26 PM, Stan Shepherd <[hidden email]> wrote:
Sorry, I don't know why, I didn't receive the attach in the email. But a anyway, the links work perfect (I always forget to attach file) I have no idea what your problem is. Now I am confused: you have two things: you sent me the difference from the packages and also the stacktrace from messagetally. This piece of thread is from changes, but your links are for the MessageTally. Anyway, this thread is already too big. I would send a separate and clear mail to the mailing list to see if someone can help you. Thanks about the packages info and the testing. Cheers Mariano ...Stan _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
In reply to this post by Lukas Renggli
On Mon, Jan 11, 2010 at 11:26 PM, Lukas Renggli <[hidden email]> wrote:
Yes, maybe this will be easier to use than having to run the lints.
_______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Free forum by Nabble | Edit this page |