- Pharo-users - lists.pharo.org

Re: [Pharo-users] ExtendedNumberParser now has its own repository

by stepharo

thanks! :) It is good that people create this configuration. I did it because I thought that we lost it. Le 16/3/15 18:58, Werner Kassens a Ã©crit : > Hi Stefane, > i understand, fwiw i have no idea whether that helps Mariano, but in > that repository exponentLetters looks like this: > ExtendedNumberParser>>exponentLetters > "Allow uppercase exponent letter." > > ^'edqEDQ' > werner > > >

March 16, 2015

Re: [Pharo-users] Pharo 4 - current state?

by Esteban Lorenzano

Yes it should and for some reason it continues resetting to the old one :( > On 16 Mar 2015, at 19:48, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > > Thanks Esteban it worked! The only think I did was in "Code Completion" to move from NECController to NOCController to get the same as your screenshot. Should this be made the default one? > > Cheers, > > Offray > >> El 16/03/15 a las 13:09, Esteban Lorenzano escribiÃ³: >> >>> On 16 Mar 2015, at 19:03, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net >>> <mailto:offray@riseup.net>> wrote: >>> >>> >>> >>> El 16/03/15 a las 12:09, Esteban Lorenzano escribiÃ³: >>> >>> [...] >>> >>>>> 1. Proper tab-autocompletion: it works, but feels unresponsive compared with >>>>> the one on Pharo 3. >>>> >>>> nothing changed there, so it is just your feeling :) >>>> >>>> Esteban >>> >>> Well, is a feeling so objective that I can record a video of the two >>> behaviours :). On Pharo 3 tab after writing some letters shows a list of >>> possible options containing that letters, on Pharo 4, it inserts a tab, with >>> no auto-completion at all :-/. >> >> check your settings, you should have something like this: >> >> >> >>> >>> Cheers, >>> >>> Offray > >

March 16, 2015

Re: [Pharo-users] Pharo 4 - current state?

by Offray Vladimir Luna CÃ¡rdenas

Thanks Esteban it worked! The only think I did was in "Code Completion" to move from NECController to NOCController to get the same as your screenshot. Should this be made the default one? Cheers, Offray El 16/03/15 a las 13:09, Esteban Lorenzano escribiÃ³: > >> On 16 Mar 2015, at 19:03, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net >> <mailto:offray@riseup.net>> wrote: >> >> >> >> El 16/03/15 a las 12:09, Esteban Lorenzano escribiÃ³: >> >> [...] >> >>>> 1. Proper tab-autocompletion: it works, but feels unresponsive compared with >>>> the one on Pharo 3. >>> >>> nothing changed there, so it is just your feeling :) >>> >>> Esteban >>> >> >> Well, is a feeling so objective that I can record a video of the two >> behaviours :). On Pharo 3 tab after writing some letters shows a list of >> possible options containing that letters, on Pharo 4, it inserts a tab, with >> no auto-completion at all :-/. > > check your settings, you should have something like this: > > > >> >> Cheers, >> >> Offray >> >

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by Thierry Goubier

Hi Kilon, like a monday :) I made a mistake in the configuration, and you are apparently the first one to try the stable version of SmaCC. It's just an error in the url. I have uploaded a new version of the configuration. Note to the SmaCC users at a certain place... I'm not sure I'll maintain SmaCC v1 for Pharo 4, so it could be appropriate to think about pushing your parsers to the new version, no? Thierry Le 16/03/2015 19:18, kilon alios a Ã©crit : > Thierry this is not your lucky week , Smacc is also fails to load from > Configuration Browser with PrimitiveFailed: primitive #basicNew: in > ByteString class failed Snip ...

March 16, 2015

Re: [Pharo-users] Error while loading GitFileTree in Pharo 4.0

by kilon alios

Thierry this is not your lucky week , Smacc is also fails to load from Configuration Browser with PrimitiveFailed: primitive #basicNew: in ByteString class failed ByteString class(Object)>>primitiveFailed: ByteString class(Object)>>primitiveFailed ByteString class(Behavior)>>basicNew: ByteString class(String class)>>new: ByteString(SequenceableCollection)>>copyFrom:to: MCGitHubRepository class>>parseLocation:version: MCGitHubRepository class>>location:version: MCGitHubRepository class>>location: [ :cl | type = 'github' ifTrue: [ ^ cl location: aRepositorySpec description ] ] in MetacelloPharo30Platform(MetacelloPlatform)>>createRepository: in Block: [ :cl | ... BlockClosure>>cull: SystemDictionary(Dictionary)>>at:ifPresent: SmalltalkImage>>at:ifPresent: MetacelloPharo30Platform(MetacelloPlatform)>>createRepository: MetacelloPharo30Platform(MetacelloPharoCommonPlatform)>>createRepository: MetacelloMCProject>>createRepository: MetacelloRepositorySpec>>createRepository [ aSpec createRepository ] in [ :aSpec | | description repo | description := aSpec description. (repo := repositories detect: [ :rep | rep description = description ] ifNone: [ aSpec createRepository ]) ~~ nil ifTrue: [ repos add: repo ] ] in MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: [ aSpec createRepository ] Array(Collection)>>detect:ifFound:ifNone: Array(Collection)>>detect:ifNone: [ :aSpec | | description repo | description := aSpec description. (repo := repositories detect: [ :rep | rep description = description ] ifNone: [ aSpec createRepository ]) ~~ nil ifTrue: [ repos add: repo ] ] in MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: in Block: [ :aSpec | ... Array(SequenceableCollection)>>do: MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom:ignoreOverrides: MetacelloEnsureFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>repositoriesFrom: MetacelloPackageSpec>>explicitLoadUsing: MetacelloPackageSpec>>ensureLoadUsing: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>ensureLoadUsing: MetacelloMCBaselineOfProjectSpec(MetacelloMCProjectSpec)>>ensureLoadedForDevelopmentUsing: [ :pkg | pkg ensureLoadedForDevelopmentUsing: mcLoader. mcLoader ignoreImage ifFalse: [ (pkg compareCurrentVersion: self operator targetVersionStatus: #(#allLoadedToSpec) using: mcLoader) ifTrue: [ packages removeKey: pkg name ] ] ] in MetacelloMCVersionSpecLoader>>load in Block: [ :pkg | ... Array(SequenceableCollection)>>do: MetacelloMCVersionSpecLoader>>load On Mon, Mar 16, 2015 at 11:21 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Can you check if the missing file is present in the zip, and in the > decompressed part on disk? > > Note that we are dealing with a Metacello/FileTree error, not a > GitFileTree one. > > Thierry > > 2015-03-16 9:56 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: > >> Yes Sir. >> I have checked 'em all. >> >> [image: Inline image 2][image: Inline image 1][image: Inline image 4][image: >> Inline image 3] >> >> On Mon, Mar 16, 2015 at 2:22 PM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> This is strange. >>> >>> I tried both the Gofer and the Metacello script before replying to you, >>> and they both worked. >>> >>> Do you have a file named >>> github-dalehenrichfiletreepharo40dev<number>.zip in your pharo repository? >>> Do you have a directory named >>> >>> >>> github-cache/dalehenrich/filetree/pharo4.0_dev/dalehenrich-filetree-7f998e5 >>> >>> Thierry >>> >>> 2015-03-16 9:43 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>> >>>> Sir >>>> I have cleared the previous files and tried to load directly from >>>> github as directed by you. >>>> The error still persists. There are missing files again. >>>> >>>> Thanks >>>> Jigyasa Grover >>>> >>>> On Mon, Mar 16, 2015 at 2:07 PM, Thierry Goubier < >>>> thierry.goubier(a)gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> an alternative solution is to load directly from github, with: >>>>> >>>>> Metacello new >>>>> baseline: 'FileTree'; >>>>> repository: 'github://dalehenrich/filetree:pharo4.0_dev/repository'; >>>>> load: 'Git' >>>>> >>>>> Missing files may mean a leftover from a previous, failed load attempt. >>>>> >>>>> Thierry >>>>> >>>>> 2015-03-16 8:19 GMT+01:00 Jigyasa Grover <grover.jigyasa1(a)gmail.com>: >>>>> >>>>>> Thanks! >>>>>> >>>>>> The error now says = File missing : >>>>>> ..\repository\MonticelloFileTree-Git.package\monticello.meta\version >>>>>> >>>>>> What is the way out ? >>>>>> >>>>>> >>>>> >>>> >>> >> >

March 16, 2015

Re: [Pharo-users] Pharo 4 - current state?

by Esteban Lorenzano

> On 16 Mar 2015, at 19:03, Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net> wrote: > > > > El 16/03/15 a las 12:09, Esteban Lorenzano escribiÃ³: > > [...] > >>> 1. Proper tab-autocompletion: it works, but feels unresponsive compared with the one on Pharo 3. >> >> nothing changed there, so it is just your feeling :) >> >> Esteban >> > > Well, is a feeling so objective that I can record a video of the two behaviours :). On Pharo 3 tab after writing some letters shows a list of possible options containing that letters, on Pharo 4, it inserts a tab, with no auto-completion at all :-/. check your settings, you should have something like this: > > Cheers, > > Offray >

March 16, 2015

Re: [Pharo-users] Pharo 4 - current state?

by Offray Vladimir Luna CÃ¡rdenas

El 16/03/15 a las 12:09, Esteban Lorenzano escribiÃ³: [...] >> 1. Proper tab-autocompletion: it works, but feels unresponsive compared with the one on Pharo 3. > > nothing changed there, so it is just your feeling :) > > Esteban > Well, is a feeling so objective that I can record a video of the two behaviours :). On Pharo 3 tab after writing some letters shows a list of possible options containing that letters, on Pharo 4, it inserts a tab, with no auto-completion at all :-/. Cheers, Offray

March 16, 2015

Re: [Pharo-users] ExtendedNumberParser now has its own repository

by Werner Kassens

Hi Stefane, i understand, fwiw i have no idea whether that helps Mariano, but in that repository exponentLetters looks like this: ExtendedNumberParser>>exponentLetters "Allow uppercase exponent letter." ^'edqEDQ' werner

March 16, 2015

Re: [Pharo-users] ExtendedNumberParser now has its own repository

by stepharo

too bad I lost my time... I will add a link to it in the smalltalkhub wiki. Now for me www.squeaksource.com is a read only system and Arbitrary precision was not equal to extendedNumberParser. Le 16/3/15 09:21, Werner Kassens a Ã©crit : > On 03/15/2015 09:41 PM, stepharo wrote: >> Hi >> >> I did not want to lose the work of Nicolas Cellier around alternate >> number parsers so I went >> back in Pharo 30 and packaged them as a separate package (may be it was >> already done but I could not find it). > > Hi Stephane, > you can find ExtendedNumberParser in: > http://www.squeaksource.com/ArbitraryPrecisionFl > it is used by the class ArbitraryPrecisionFloat and since > ArbitraryPrecisionFloat is actively held up to date by Nicolas, i'd > guess the same is true for ExtendedNumberParser in this repository. > werner > >

March 16, 2015

Re: [Pharo-users] [Pharo4] Please test Pharo4 *now*

by Sven Van Caekenberghe

> On 16 Mar 2015, at 17:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > As every year: We can only fix what we know. > > And this means that no, just because *you* think that X and Y obviously needs to be fixed, > it will only be fixed if > a) there is an issue on the issue tracker > b) someone fixes it. > > I should repeat: *Nothing*, even the most obvious or trivial, happens by itself. > > Marcus Maybe it is also important to add that we are talking about bugs, not features. This is not the time for free wheeling discussions about anything, we need help in QA, to finalize the 4.0 release. Please load your code and give it a spin. Sven

March 16, 2015