February 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo bootstrap with Ring and Calypso

by denker

Nice! It is interesting how all these projects are coming togetherâ¦ :-) Marcus > On 24 Feb 2017, at 13:36, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > I have published a short video of the Pharo bootstrapping from a Ring model that is browsed and modified by the Calypso browser. > > https://www.youtube.com/watch?v=QguZSPKo7-w <https://www.youtube.com/watch?v=QguZSPKo7-w> > > No audio, please enable subtitles for the description. > > Cheers, > -- Pavel

Feb. 24, 2017

Pharo bootstrap with Ring and Calypso

by Pavel Krivanek

Hi, I have published a short video of the Pharo bootstrapping from a Ring model that is browsed and modified by the Calypso browser. https://www.youtube.com/watch?v=QguZSPKo7-w No audio, please enable subtitles for the description. Cheers, -- Pavel

Feb. 24, 2017

[Pharo6][Issue Tracker] 80 Issues tagged for Pharo6

by Marcus Denker

Hi, We have 80 issues left that have the Milestone tag for Pharo6. https://pharo.fogbugz.com/f/filters/1192/6-0-All It would really be nice if people could check all the issues and decide: âIs this a release critical issue?â if yes â> increase priory to at least âMust Fixâ. If not, consider removing the Milestone tag and put it to âLaterâ. At the sprint next week we will automatically remove all Milestone-6 tags from all issues that are âWould be niceâ or lower. Marcus

Feb. 24, 2017

Re: [Pharo-dev] [VM] Windows VM SurfacePlugin.dll LoadLibrary failure

by Peter Uhnak

Well, I take that back. Today I had the same issue (with the latest VM). Closing the image and reopening it helped, but clearly there is something broken underneath. Peter On Wed, Feb 22, 2017 at 09:29:12PM +0100, Peter Uhnak wrote: > On Thu, Feb 16, 2017 at 12:19:00PM +0100, Cyril Ferlicot D. wrote: > > > > I got the same problem with the latest vm some weeks ago on Windows 7. > > It vanished by downloading a new vm some days after. > > I've downloaded the latest VM and it works as expected. Thanks! > > Peter

Feb. 24, 2017

Re: [Pharo-dev] Raw pane on byteStrings

by Thierry Goubier

Hi Andrei, 2017-02-24 11:31 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > Hi Thierry, > > Indeed that's the simplest option now that we are using fast table. > > Just now in the case of the Raw view an OrderedCollection is used to store > all displayed elements. > If you display large collections every time you open the Raw view it will > instantiate a collection of size 100k and instantiate 100k objects of > type GTInspectorIndexedNode. With FastTable we can lazily load elements so > we should be able to remove this behaviour and the limit. Just we need to > make sure it will play nicely with automatic refresh. There is also the > issue that when expanding an element in the tree if it's a collection you > don't want to expand all elements. > I'm not sure you need to worry too much about that one; in practical experiments, creating that 100k collection for viewing (and the associated nodes instances) isn't too costly (unless creating the GTInspectorIndexedNodes has hidden costs: I've only experimented with the EyeInspector framework). Opening the tree with all elements works fine in my experiments. Tuning scrolling as done in Bloc is necessary, however. > > I'm looking now on a lazy data source for FastTable that plays nicely with > GTInspector. Let's see how it will go. Help is always welcomed :) > As I said: do not overoptimize that part... just remove that limitation on the raw view and measure. > > I think I used the word paginator in the wrong way. If you have a very > large collection (millions of elements) I do not want to scroll through > elements but most likely jump to a certain element or view just a subset of > all elements. Not really add a paginator like in web pages. > Ok, millions of elements is a bit out of my scope... I'll look for filtering then. Regards, Thierry > > Cheers, > Andrei > > On Fri, Feb 24, 2017 at 10:37 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Andrei, >> >> if you're using fasttable for the Raw view, you should be able to reach >> one 100k elements without issues. I did some experiments and it handles the >> load very well. >> >> Avoid the paginator at any cost. This thing is really user-unfriendly. >> >> Regards, >> >> Thierry >> >> 2017-02-23 20:19 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: >> >>> Hi Stef, >>> >>> Currently that's the default behaviour of the Raw view: it displays for >>> collections only the first and the last 21 elements. The Items view however >>> always should display all the elements of a collection. >>> >>> The main problem with the Raw view in Pharo 5 is the speed. In Pharo 6 >>> now the speed of the Raw view is greately improved so we could increase >>> those limits. Still for now there should still be some limit for the Raw >>> view. Ideally we should add a small widget, something like a paginator, for >>> navigating through large and very large collections. >>> >>> Cheers, >>> Andrei >>> >>> On Feb 23, 2017 19:35, "stepharong" <stepharong(a)free.fr> wrote: >>> >>>> Hi >>>> >>>> I'm trying to debug citezen generation and I have to compare strings. >>>> Now I think that the raw views (in Pharo 50) is not good because we >>>> cannot see all the items in raw format. >>>> See the attachements. It jumps from 21 to 174 ... >>>> and what I want to see is of course in the middle. >>>> >>>> Is it me or there is something wrong there. >>>> Stef >>> >>> >> >

Feb. 24, 2017

Re: [Pharo-dev] Any idea for a cool name for the remote tool suite?

by Markus Fritsche

Hello, I guess the vote is already cast, but I'd like to add my two Cents: the packages now have a description that give an idea about what the package is supposed to do. Still, discoverability should be considered when finding a name. That's why I would prefer something like TelePharo, since the name already hints at the core functionality. Best regards, Markus Am 29.01.2017 15:14, schrieb stepharong: > Hi guys > > Since we will push the remote tools (videos/web...) I would like to > get some ideas for a cool name. > Any ideas? > > Because Pharmide (looks like medicine or chemical product). > Since I vaguely remember some german Pharmide made me think about > Fern(sehen) but this is not a good name. > > Stef > > > --

Feb. 24, 2017

Re: [Pharo-dev] Raw pane on byteStrings

by Andrei Chis

Hi Thierry, Indeed that's the simplest option now that we are using fast table. Just now in the case of the Raw view an OrderedCollection is used to store all displayed elements. If you display large collections every time you open the Raw view it will instantiate a collection of size 100k and instantiate 100k objects of type GTInspectorIndexedNode. With FastTable we can lazily load elements so we should be able to remove this behaviour and the limit. Just we need to make sure it will play nicely with automatic refresh. There is also the issue that when expanding an element in the tree if it's a collection you don't want to expand all elements. I'm looking now on a lazy data source for FastTable that plays nicely with GTInspector. Let's see how it will go. Help is always welcomed :) I think I used the word paginator in the wrong way. If you have a very large collection (millions of elements) I do not want to scroll through elements but most likely jump to a certain element or view just a subset of all elements. Not really add a paginator like in web pages. Cheers, Andrei On Fri, Feb 24, 2017 at 10:37 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Hi Andrei, > > if you're using fasttable for the Raw view, you should be able to reach > one 100k elements without issues. I did some experiments and it handles the > load very well. > > Avoid the paginator at any cost. This thing is really user-unfriendly. > > Regards, > > Thierry > > 2017-02-23 20:19 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > >> Hi Stef, >> >> Currently that's the default behaviour of the Raw view: it displays for >> collections only the first and the last 21 elements. The Items view however >> always should display all the elements of a collection. >> >> The main problem with the Raw view in Pharo 5 is the speed. In Pharo 6 >> now the speed of the Raw view is greately improved so we could increase >> those limits. Still for now there should still be some limit for the Raw >> view. Ideally we should add a small widget, something like a paginator, for >> navigating through large and very large collections. >> >> Cheers, >> Andrei >> >> On Feb 23, 2017 19:35, "stepharong" <stepharong(a)free.fr> wrote: >> >>> Hi >>> >>> I'm trying to debug citezen generation and I have to compare strings. >>> Now I think that the raw views (in Pharo 50) is not good because we >>> cannot see all the items in raw format. >>> See the attachements. It jumps from 21 to 174 ... >>> and what I want to see is of course in the middle. >>> >>> Is it me or there is something wrong there. >>> Stef >> >> >

Feb. 24, 2017

Re: [Pharo-dev] Pharo 60 : 60410 DNU on commit and no idea how to copy the stack :((((((((((((((((((((((((((((((((((((((((((((((

by Andrei Chis

On Fri, Feb 24, 2017 at 8:44 AM, stepharong <stepharong(a)free.fr> wrote: > On Fri, 24 Feb 2017 00:05:10 +0100, Andrei Chis < > chisvasileandrei(a)gmail.com> wrote: > > >> >> - How do we get the old textual stack description? >> > > In the toolbar menu of the stack you find 'Fuel out stack' and 'Copy to > clipboard'. > 'Copy to clipboard' copies a textual description of the stack that can > then be pasted in an email. > Is this the "old textual description" or are you referring to something > else? > > > Ok this is what I was looking for. > It looks like a generic copy past entry so I did not tried it. > Can you rename it into copy textual stack? > Indeed the name is confusing (even if it's always been like that). I renamed it yesterday to 'Copy Stack to Clipboard'. Is that better? (It fits also with 'Fuel out Stack') Cheers, Andrei > > Then I do not get why we could not get action about the current context > and action about the complete stack together. > Because these are not method that we see but contexts. > > > > >> Now I wanted to report it and share with you the stack..... oh >> boy! >> I thought it was file out but no it just save one method >> definition (So great) >> > > What action did you use to file our the textual description? > > > fileout in the main menu when you clik on the stack element. > I never ever used it since 2006. > > > Cheers, > Andrei > > > >> >> I got Fuelout the stack in the menu but this is not what I want. >> :((((((((((((((((((((((((((((((( > > >> - Finally >> BTW I clicked on report and I have no idea what it does not mean. >> The fly by help is empty :((((( > > > > do you have an idea about what is this Send a report: it looks totally > obscure and useless. > > >> >> >> So like an idiot I did a screen capture. >> This broke totally my feel. In less than 10 min I left like either the >> system became less good or I'm totally stupid. >> >> Stef > > > > > > -- > Using Opera's mail client: http://www.opera.com/mail/ >

Feb. 24, 2017

Re: [Pharo-dev] Raw pane on byteStrings

by Denis Kudriashov

2017-02-24 10:37 GMT+01:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Hi Andrei, > > if you're using fasttable for the Raw view, you should be able to reach > one 100k elements without issues. I did some experiments and it handles the > load very well. > > Avoid the paginator at any cost. This thing is really user-unfriendly. > +100

Feb. 24, 2017

Re: [Pharo-dev] [ANN] Woden 2 first release for OS X and Linux

by nolwenn

Wonderful ! I will try it soon. Thanks ! Nolwenn -- View this message in context: http://forum.world.st/ANN-Woden-2-first-release-for-OS-X-and-Linux-tp493569… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 24, 2017