- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GTInspector and huge arrays issue

by Usman Bhatti

On Thu, Dec 4, 2014 at 11:56 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > "So I am not the only one grumbling about the scrolling in lists. > My suggestion was to use paging for this purpose. > > See the discussion here on moose-list. > > > https://code.google.com/p/moose-technology/issues/detail?id=1099&can=4&cols… > > > regards, > > usman > " > > I cannot understand your problem and your solution to it. I am afraid I am > not familiar with the library you use or with GTInspector. If I could > assume I would say you dont like the continuous scroll solution currently > implemented in GTInspector but that is not my problem. > > My problem is that next 50 items icon button disappears each time I press > it and for me that makes no sense. Without changing the current > implementation at a fundamental level the button should be always visible > and allow you to press it multiple times and send you to the last first of > 50. So if I press it lets say 4 times, it will be nice if it would send the > cursor of the list display to the item 200 and the list be able to scroll > down to 250 assuming that the list was already at cursor 1 displaying 50 > items. > Did you try this script in the discussion that shows the other possibility of list scrolling in Morph without talking about GT-*: This covers your requirement of omnipresent buttons and a list showing a fix number of items (in your case 50). | treeMorph aWindow aModel | aModel := PaginatedMorphTreeModel new rootItems: (1 to: 100) asArray. aWindow := aModel theme newWindowIn: World for: aModel title: 'test'. treeMorph := aModel defaultTreeMorph. treeMorph pageSize: 30. treeMorph buildContents. aWindow addMorph: treeMorph fullFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 1) offsets: (0 @ 0 corner: 0 @ 0)). aWindow open. aModel expandItemPath: {50}.

Dec. 4, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by phil＠highoctane.be

On Thu, Dec 4, 2014 at 11:56 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 04 Dec 2014, at 11:45, phil(a)highoctane.be wrote: > > > > But further than that I want to edit values in inspectors. > > Yes ! > Is there a way to get back an old trusty inspector on something? (like anObject inspectClassic / anObject exploreClassic) Live yes, but live behind a wall of glass isn't that interactive. Phil > And auto refresh ! > > Both of these could be depending on presentation, so that heavy > presentations can opt out. > > > >

Dec. 4, 2014

Re: [Pharo-dev] Meaning of VirtualMachine>>incrementalGCCount

by Jan Vrany

On Thu, 2014-12-04 at 11:43 +0100, ClÃ©ment Bera wrote: > Hello Jan, > > > An incrementalGC, in the sense of the V3 memory manager, is a scavenge > (unrelated to what other people call an incremental GC). With the new > memory manager Spur the names were updated to match common vocabulary. > I thought so :-) but wanted to be sure. Thanks for explanation! > > Please ask such questions on vm-dev Right, that would have been better. I'm sorry. Best, Jan > > 2014-12-04 10:30 GMT+01:00 Jan Vrany <jan.vrany(a)fit.cvut.cz>: > Hi there, > > what's exact meaning of VirtualMachine>>incrementalGCCount? > Comment says: "Answer the total number of incremental GCs > since startup > (read-only)." But what exactly is called 'incremental CG' in > context of > PharoVM? > > Again, thanks for any clarification :-) > > Jan > > > > > >

Dec. 4, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by kilon alios

"So I am not the only one grumbling about the scrolling in lists. My suggestion was to use paging for this purpose. See the discussion here on moose-list. https://code.google.com/p/moose-technology/issues/detail?id=1099&can=4&cols… regards, usman " I cannot understand your problem and your solution to it. I am afraid I am not familiar with the library you use or with GTInspector. If I could assume I would say you dont like the continuous scroll solution currently implemented in GTInspector but that is not my problem. My problem is that next 50 items icon button disappears each time I press it and for me that makes no sense. Without changing the current implementation at a fundamental level the button should be always visible and allow you to press it multiple times and send you to the last first of 50. So if I press it lets say 4 times, it will be nice if it would send the cursor of the list display to the item 200 and the list be able to scroll down to 250 assuming that the list was already at cursor 1 displaying 50 items.

Dec. 4, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by Sven Van Caekenberghe

> On 04 Dec 2014, at 11:45, phil(a)highoctane.be wrote: > > But further than that I want to edit values in inspectors. Yes ! And auto refresh ! Both of these could be depending on presentation, so that heavy presentations can opt out.

Dec. 4, 2014

Re: [Pharo-dev] fixing 'format on display' and 'format on accept'

by Marcus Denker

> On 04 Dec 2014, at 10:41, Otto Behrens <otto(a)finworks.biz> wrote: > > Hi, > > We just upgraded to Pharo 3 (after using pharo 1.4 for a looong time). > I'm a bit new to some things, so pardon my ignorance. > > We're so used to auto formatting the code, it drives us nuts not to have it. > > I eventually figured out that the Pharo30 inbox is here: > http://smalltalkhub.com/mc/Pharo/Pharo30Inbox/main. > > Is a slice is something I can "patch in"? How do I get hold of this? > -> opem Monticello Browser -> open inbox -> search for 14387 -> âMergeâ (not load). > Thanks a lot > Otto > > On Tue, Nov 4, 2014 at 9:25 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> Slice is in the Pharo30Inbox >> >> https://pharo.fogbugz.com/f/cases/14387/ressurrect-format-on-accept-and-for… >> >> It uses the settings browser as described below and auto-formats methods (on >> display or accept or both) in Nautilus and the senders/implementors browser. >> >> >> >> >> Paul DeBruicker wrote >>> Hi - >>> >>> I'm going to get 'format on display' and 'format on accept' working in >>> Nautilus. In Pharo 3 in the settings browser under 'code browsing' there >>> is a 'pretty print' check box. As far as I can tell it doesn't affect >>> code displaying at all in Nautilus. >>> >>> >>> Is it OK to repurpose that checkbox as a control for 'format on display' >>> and to also add a check box right there for 'format on accept' ? If not >>> what would be better? >>> >>> >>> Thanks >>> >>> Paul >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/fixing-format-on-display-and-format-on-accept-tp47883… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >

Dec. 4, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by phil＠highoctane.be

On Thu, Dec 4, 2014 at 11:33 AM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > So I am not the only one grumbling about the scrolling in lists. > Yeah, painful. I want a search box too. But further than that I want to edit values in inspectors. Is there a way? Phil > My suggestion was to use paging for this purpose. > > See the discussion here on moose-list. > > > https://code.google.com/p/moose-technology/issues/detail?id=1099&can=4&cols… > > > regards, > > usman > > On Thu, Dec 4, 2014 at 11:13 AM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> so I am enjoying the new Inspector but I have come to a problem. I >> inspected Smalltalk global variable and has gave me an array with 4000+ >> items . >> >> My problem is that there is no way to quickly scroll those items for >> example to go forward i have to scroll down and then press next page icon. >> I think it would be better if the next page icon is always displayed , it >> does not make sense to me for it to become visible only when I scroll down. >> >> Something that would have been following normal GUI behavior it would be >> just few button presses, now its scroll down to make the next page button >> visible , then repeat. Very tedious. >> >> also if I put "image" in the search box it gives me an MNU >> >> UndefinedObject(Object)>>doesNotUnderstand: #ifTrue: >> GLMTreeMorphModel>>ExecuteUnOptimizedIn: >> UndefinedObject(Object)>>mustBeBooleanInMagic: >> UndefinedObject(Object)>>mustBeBoolean >> [ :each | >> check := self glamourPresentation searchStrategy value: self inputText >> value: each item. >> check >> ifTrue: [ newSelection add: each path ] ] in >> GLMTreeMorphModel>>executeSearch in Block: [ :each | ... >> OrderedCollection>>do: >> GLMTreeMorphModel>>executeSearch >> GLMTreeMorphModel>>doSearchOrFilter >> GLMTreeMorphModel>>inputText: >> PluggableTextFieldMorph>>acceptTextInModel >> PluggableTextFieldMorph(PluggableTextMorph)>>acceptBasic >> PluggableTextFieldMorph>>accept >> TextMorphForFieldView(TextMorphForEditView)>>acceptContents >> TextEditor>>accept >> TextMorphForFieldView(TextMorphForEditView)>>keyStroke: >> TextMorphForFieldView>>keyStroke: >> TextMorphForFieldView(TextMorph)>>handleKeystroke: >> KeyboardEvent>>sentTo: >> TextMorphForFieldView(Morph)>>handleEvent: >> TextMorphForFieldView(Morph)>>handleFocusEvent: >> [ >> ActiveHand := self. >> ActiveEvent := anEvent. >> result := focusHolder handleFocusEvent: (anEvent transformedBy: >> (focusHolder transformedFrom: self)) ] in >> HandMorph>>sendFocusEvent:to:clear: in Block: [ ... >> BlockClosure>>on:do: >> WorldMorph(PasteUpMorph)>>becomeActiveDuring: >> HandMorph>>sendFocusEvent:to:clear: >> HandMorph>>sendEvent:focus:clear: >> HandMorph>>sendKeyboardEvent: >> HandMorph>>handleEvent: >> HandMorph>>processEvents >> [ :h | >> ActiveHand := h. >> h processEvents. >> ActiveHand := nil ] in WorldState>>doOneCycleNowFor: in Block: [ :h | ... >> Array(SequenceableCollection)>>do: >> >> >> >

Dec. 4, 2014

Re: [Pharo-dev] Meaning of VirtualMachine>>incrementalGCCount

by ClÃ©ment Bera

Hello Jan, An incrementalGC, in the sense of the V3 memory manager, is a scavenge (unrelated to what other people call an incremental GC). With the new memory manager Spur the names were updated to match common vocabulary. Please ask such questions on vm-dev 2014-12-04 10:30 GMT+01:00 Jan Vrany <jan.vrany(a)fit.cvut.cz>: > Hi there, > > what's exact meaning of VirtualMachine>>incrementalGCCount? > Comment says: "Answer the total number of incremental GCs since startup > (read-only)." But what exactly is called 'incremental CG' in context of > PharoVM? > > Again, thanks for any clarification :-) > > Jan > > > > >

Dec. 4, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by Usman Bhatti

So I am not the only one grumbling about the scrolling in lists. My suggestion was to use paging for this purpose. See the discussion here on moose-list. https://code.google.com/p/moose-technology/issues/detail?id=1099&can=4&cols… regards, usman On Thu, Dec 4, 2014 at 11:13 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > so I am enjoying the new Inspector but I have come to a problem. I > inspected Smalltalk global variable and has gave me an array with 4000+ > items . > > My problem is that there is no way to quickly scroll those items for > example to go forward i have to scroll down and then press next page icon. > I think it would be better if the next page icon is always displayed , it > does not make sense to me for it to become visible only when I scroll down. > > Something that would have been following normal GUI behavior it would be > just few button presses, now its scroll down to make the next page button > visible , then repeat. Very tedious. > > also if I put "image" in the search box it gives me an MNU > > UndefinedObject(Object)>>doesNotUnderstand: #ifTrue: > GLMTreeMorphModel>>ExecuteUnOptimizedIn: > UndefinedObject(Object)>>mustBeBooleanInMagic: > UndefinedObject(Object)>>mustBeBoolean > [ :each | > check := self glamourPresentation searchStrategy value: self inputText > value: each item. > check > ifTrue: [ newSelection add: each path ] ] in > GLMTreeMorphModel>>executeSearch in Block: [ :each | ... > OrderedCollection>>do: > GLMTreeMorphModel>>executeSearch > GLMTreeMorphModel>>doSearchOrFilter > GLMTreeMorphModel>>inputText: > PluggableTextFieldMorph>>acceptTextInModel > PluggableTextFieldMorph(PluggableTextMorph)>>acceptBasic > PluggableTextFieldMorph>>accept > TextMorphForFieldView(TextMorphForEditView)>>acceptContents > TextEditor>>accept > TextMorphForFieldView(TextMorphForEditView)>>keyStroke: > TextMorphForFieldView>>keyStroke: > TextMorphForFieldView(TextMorph)>>handleKeystroke: > KeyboardEvent>>sentTo: > TextMorphForFieldView(Morph)>>handleEvent: > TextMorphForFieldView(Morph)>>handleFocusEvent: > [ > ActiveHand := self. > ActiveEvent := anEvent. > result := focusHolder handleFocusEvent: (anEvent transformedBy: > (focusHolder transformedFrom: self)) ] in > HandMorph>>sendFocusEvent:to:clear: in Block: [ ... > BlockClosure>>on:do: > WorldMorph(PasteUpMorph)>>becomeActiveDuring: > HandMorph>>sendFocusEvent:to:clear: > HandMorph>>sendEvent:focus:clear: > HandMorph>>sendKeyboardEvent: > HandMorph>>handleEvent: > HandMorph>>processEvents > [ :h | > ActiveHand := h. > h processEvents. > ActiveHand := nil ] in WorldState>>doOneCycleNowFor: in Block: [ :h | ... > Array(SequenceableCollection)>>do: > > >

Dec. 4, 2014

GTInspector and huge arrays issue

by kilon alios

so I am enjoying the new Inspector but I have come to a problem. I inspected Smalltalk global variable and has gave me an array with 4000+ items . My problem is that there is no way to quickly scroll those items for example to go forward i have to scroll down and then press next page icon. I think it would be better if the next page icon is always displayed , it does not make sense to me for it to become visible only when I scroll down. Something that would have been following normal GUI behavior it would be just few button presses, now its scroll down to make the next page button visible , then repeat. Very tedious. also if I put "image" in the search box it gives me an MNU UndefinedObject(Object)>>doesNotUnderstand: #ifTrue: GLMTreeMorphModel>>ExecuteUnOptimizedIn: UndefinedObject(Object)>>mustBeBooleanInMagic: UndefinedObject(Object)>>mustBeBoolean [ :each | check := self glamourPresentation searchStrategy value: self inputText value: each item. check ifTrue: [ newSelection add: each path ] ] in GLMTreeMorphModel>>executeSearch in Block: [ :each | ... OrderedCollection>>do: GLMTreeMorphModel>>executeSearch GLMTreeMorphModel>>doSearchOrFilter GLMTreeMorphModel>>inputText: PluggableTextFieldMorph>>acceptTextInModel PluggableTextFieldMorph(PluggableTextMorph)>>acceptBasic PluggableTextFieldMorph>>accept TextMorphForFieldView(TextMorphForEditView)>>acceptContents TextEditor>>accept TextMorphForFieldView(TextMorphForEditView)>>keyStroke: TextMorphForFieldView>>keyStroke: TextMorphForFieldView(TextMorph)>>handleKeystroke: KeyboardEvent>>sentTo: TextMorphForFieldView(Morph)>>handleEvent: TextMorphForFieldView(Morph)>>handleFocusEvent: [ ActiveHand := self. ActiveEvent := anEvent. result := focusHolder handleFocusEvent: (anEvent transformedBy: (focusHolder transformedFrom: self)) ] in HandMorph>>sendFocusEvent:to:clear: in Block: [ ... BlockClosure>>on:do: WorldMorph(PasteUpMorph)>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendKeyboardEvent: HandMorph>>handleEvent: HandMorph>>processEvents [ :h | ActiveHand := h. h processEvents. ActiveHand := nil ] in WorldState>>doOneCycleNowFor: in Block: [ :h | ... Array(SequenceableCollection)>>do:

Dec. 4, 2014