January 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Bug Report: 6 of 6: Settings

by Alain Plantec

Le 03/01/2012 11:57, S Krish a Ã©crit : > This works... > > Guess I should have tried that.. thanks. but you are not the first one to forget to enter a cr. not user friendly, this is in my todo list to improve that :) Cheers Alain > thx. > > On Tue, Jan 3, 2012 at 4:10 PM, Alain Plantec <alain.plantec(a)yahoo.com > <mailto:alain.plantec@yahoo.com>> wrote: > > Le 03/01/2012 11:24, S Krish a Ã©crit : > > 6. Settings: > On Ubuntu Linux and on Windows: Go to the Network node and > change the values for HTTP Proxy/ Proxy Authentication and > quit and comeback.. > > Does not retain the settings.. > > strange, it work here with 1.3 and 1.4. > did you accept you input with a cr ? > Alain > > > ******************** > Also .. I add it here.. though disconnected from the above.. > but for Settings issue.. > Sound Package: > > Well this one set of hack throughs to get it working on Linux.. > Straight after loading the packages: > > Settings tab does not show up the 3+ lines of setting > on loading the SoundSetting package.. > Fails on Phenome** method not being initialized.. > > Go hack and comment some places in the code it starts to work > beautifully thereafter.. will try and reap/ move hacks to more > usable code and submit.. > > > >

Jan. 3, 2012

Re: [Pharo-project] glamour and pharo

by Igor Stasenko

On 2 January 2012 18:44, Lukas Renggli <renggli(a)gmail.com> wrote: >> is not that *it can't* is that, as a development platform, Pharo needs to provide kernel+tools, not just kernel. >> Anyway, I was not arguing against having a small kernel, I was arguing against pharo "just doing" the kernel. >> Linux itself can't be distributed just as a kernel, it is distributed with a full set of different tools: GNU/Linux, Ubuntu Linux, etc. (btw... this is one of the arguments Stallman allways says about Linux: it was possible because there was already a lot of tools) And, in that case, just as Linux, we can't just do the kernel, we need to provide development tools... otherwise, people wont use it. I myself wont use it for my commercial applications if I do not have something like OmniBrowser to develop. > > I totally agree, the Pharo Kernel alone is not very useful for an > end-user. However, with the emerging Pharo architecture you can hardly > build a different distribution. > > To use the Linux analogy: You are trying to convince GNU/Linux to > rebuild their system on top of a full-fledged Ubuntu distribution. > >> What I'm NOT saying: Kernel and Tools should be coupled. (If ppl whant kernel+other things, they are welcome to have it... I myself will want it) > > This coupling is exactly what is happening. How do you propose to > build your kernel+other distribution? What coupling you are talking about? Can you give an example? Instead we striving to decouple components of the system and improve infrastructure. If you speaking about announcements, so here the vision: - there are tons of different event driving mechanisms in image and we want to leave only one, replacing all of them with announcements. Will this couple tools to announcements? Of course. Will this add unnecessary coupling between layers? No. Because announcements is inherently serving for decoupling event source(s) from event consumers. -- Best regards, Igor Stasenko.

Jan. 3, 2012

Re: [Pharo-project] About announcements

by Igor Stasenko

On 2 January 2012 21:04, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Now for me you don't need to change the semantics of the Pharo >>> Announcements again. Now for my code I will just use my own >>> implementation that has exactly the behavior and performance >>> characteristics I need. >> >> Lukas our state of mind is that we want the infrastructure gets better so we like to change >> for a better one if this better one is better. > > Seems that the understanding of what is better/worse and what is > progress/regress is rather different among people. > >> If everybody has its own version then we do not improve the infrastructure. > > Performance issues aside, the current implementation forces me to use > a different implementation because Pharo's announcements have a > different implementation of selecting the handler (point 7). However, > the really weird thing is that Pharo's announcements are now suddenly > inconsistent with the Pharo exceptions and how they select the > handler. Do you think this is better or worse? > you lost me here. why announcements have to be consistent with exceptions? something which is completely orthogonal to them? it is like saying that apples are inconsistent with oranges. aside of that, i added the changeset, so you can now choose whether your announcement subscription is handling announcement or not based on announcement object itself, not its class. see http://code.google.com/p/pharo/issues/detail?id=5145 -- Best regards, Igor Stasenko.

Jan. 3, 2012

Re: [Pharo-project] Bug reports: 2 of 6:

by Ben Coman

S Krish wrote: > 2. bug with mouseUp not passing through for event handling with > on:send:to: target... > > click all over the World and you will keep getting the dialog though you > are not clicking the morph. > #clickClient in MouseClickState holds the morph as the recipient morph for > clicks.. rather than the modal dialog.. > > ( SimpleButtonMorph new extent: 80@60 ; label: 'test' ; on:#click send: > #value to:[ UIManager default inform: 'test']; color: Color red) > openInWorld. > > Replicated on: Pharo-1.2.1-OneClick Pharo-1.3-13315-OneCLick Pharo-1.4-14263. Additional observation is that specifically clicking the <OK> button on the dialog does not close it. Right-clicking anywhere fixes the behaviour such that clicking <OK> does close the dialog rather than creating a new one.

Jan. 3, 2012

Re: [Pharo-project] About announcements

by Igor Stasenko

On 2 January 2012 16:12, Lukas Renggli <renggli(a)gmail.com> wrote: > Ok, first of all I did not know who wrote the code. I was just fixing > some of my code that suddenly broke and was astonished what the > announcer all does when stepping through the announcement procedure > with the debugger ... > >>>> 3. It enters a critical section of a monitor: This is rarely useful >>>> and the slowest kind of concurrency control available in Pharo (a >>>> Mutex would be enough for what it is used for, and instantiate >>>> multiple semaphores and queues), and btw the lazy initialization of >>>> the monitor is the prime example of a race condition. >>>> >>> agreed here. I would even leave a semaphore. >>> I think it is overlooked by Henrik. >>> It also don't needs a lazy initialization in #protected: , since in >>> #initialize it can just create a ready for use fresh >>> synchronization object. > > A semaphore might block, because an announcement could register > another announcement. So probably the Mutex would be the right thing > to use. > no, the trick there is that we leaving a critical section before returning (or calling) client code, so there is no chance that it may recurse (attempt enter critical section twice) due to some weird client code. >>>> 4. It creates a copy of the collection of all the subscriptions: This >>>> is rarely useful and wouldn't be necessary if an immutable data >>>> structure was used. >>>> >>> propose better solution how to deal with situation when during >>> handling an announcement, >>> your handler unsubscribing from announcer. > > Array. Slower for registration, but faster at announcing (the common operation). > maybe. >>>> 5. It iterates over all announcements, it doesn't even try to group >>>> announcements of the same kind. >>>> >>> it is pointless to group them, and makes no real difference. >>> Because announcer doesn't knows what kinds of announcements will be >>> announcement, >>> and it knows only about subscriptions. >>> Suppose i have a subscription to Announcement. And i announcing >>> AnnouncementA (a subclass of it). > > Fair enough, probably it doesn't matter. > >>>> 7. It then tests each announcement if it matches, again it doesn't >>>> even try to group the announcements of the same kind. Aside, the match >>>> test was changed so that it doesn't allow instance-based announcements >>>> anymore, breaking some of my code. >>>> >>> what is instance-based announcements? > > If you have a client with 1000 different possibly dynamically changing > properties and you want a way to register for announcements of a > single property. The current implementation forces you to create a > class per property, previously you could fake a "kind of > announcements" with an instance. > >>> you can use any object as Â a subscription selector, just make sure it >>> understands #handles: message. >>> i.e. > > No, because the Announcement>>#handles: takes a class, not an instance. > you mean here: deliver: anAnnouncement " deliver an announcement to receiver. In case of failure, it will be handled in separate process" ^ (self handles: anAnnouncement class ) ifTrue: [ [action cull: anAnnouncement cull: announcer] on: UnhandledError fork: [:ex | ex pass ]] we can simply change the 'anAnnouncement class' to just 'anAnnouncement' so the receiver of #handles: will see an announcement itself not its class. It is probably right thing to do, because then you can do: announcer on: foo do: [... ]. announcer announce: 10. Then foo will receive: foo handles: 10. and in your own #handles: implementation you can do something like: handles: anAnnouncement ^ anAnnouncement isInteger >>>> 9. It then culls the announcement and announcer into the block. Not >>>> sure why the announcer is useful, after all the block was registered >>>> with the announcer at some point. >>>> >>> cull there is for passing optional arguments. > > I didn't complain about #cull:, but about the useless announcer passed in. > > Now for me you don't need to change the semantics of the Pharo > Announcements again. Now for my code I will just use my own > implementation that has exactly the behavior and performance > characteristics I need. > -- Best regards, Igor Stasenko.

Jan. 3, 2012

Re: [Pharo-project] Bug Report: 6 of 6: Settings

by S Krish

This works... Guess I should have tried that.. thx. On Tue, Jan 3, 2012 at 4:10 PM, Alain Plantec <alain.plantec(a)yahoo.com>wrote: > Le 03/01/2012 11:24, S Krish a Ã©crit : > > 6. Settings: >> On Ubuntu Linux and on Windows: Go to the Network node and change the >> values for HTTP Proxy/ Proxy Authentication and quit and comeback.. >> >> Does not retain the settings.. >> > strange, it work here with 1.3 and 1.4. > did you accept you input with a cr ? > Alain > > >> ******************** >> Also .. I add it here.. though disconnected from the above.. but for >> Settings issue.. >> Sound Package: >> >> Well this one set of hack throughs to get it working on Linux.. >> Straight after loading the packages: >> >> Settings tab does not show up the 3+ lines of setting on loading >> the SoundSetting package.. >> Fails on Phenome** method not being initialized.. >> >> Go hack and comment some places in the code it starts to work beautifully >> thereafter.. will try and reap/ move hacks to more usable code and submit.. >> > > >

Jan. 3, 2012

Re: [Pharo-project] Bug Report: 6 of 6: Settings

by Alain Plantec

Le 03/01/2012 11:24, S Krish a Ã©crit : > 6. Settings: > On Ubuntu Linux and on Windows: Go to the Network node and change the > values for HTTP Proxy/ Proxy Authentication and quit and comeback.. > > Does not retain the settings.. strange, it work here with 1.3 and 1.4. did you accept you input with a cr ? Alain > > ******************** > Also .. I add it here.. though disconnected from the above.. but for > Settings issue.. > Sound Package: > > Well this one set of hack throughs to get it working on Linux.. > Straight after loading the packages: > > Settings tab does not show up the 3+ lines of setting on > loading the SoundSetting package.. > Fails on Phenome** method not being initialized.. > > Go hack and comment some places in the code it starts to work > beautifully thereafter.. will try and reap/ move hacks to more usable > code and submit..

Jan. 3, 2012

[Pharo-project] Bug Report: 6 of 6: Settings

by S Krish

6. Settings: On Ubuntu Linux and on Windows: Go to the Network node and change the values for HTTP Proxy/ Proxy Authentication and quit and comeback.. Does not retain the settings.. ******************** Also .. I add it here.. though disconnected from the above.. but for Settings issue.. Sound Package: Well this one set of hack throughs to get it working on Linux.. Straight after loading the packages: Settings tab does not show up the 3+ lines of setting on loading the SoundSetting package.. Fails on Phenome** method not being initialized.. Go hack and comment some places in the code it starts to work beautifully thereafter.. will try and reap/ move hacks to more usable code and submit..

Jan. 3, 2012

[Pharo-project] Bug Report 5 of 6: Minor annoyance in SimpleButtonMorph

by S Krish

5. SimpleButtonMorph>> updateVisualState: evt flashes the button with a color fill. For buttons that I have bitmap style, this is annoying.. ? I can override.. but better not have this for default buttons..?

Jan. 3, 2012

[Pharo-project] Bug Report 4 of 6: PasteUpMorph>>processEvent:

by S Krish

4. For PasteUpMorph>> processEvent: anEvent using: defaultDispatcher "Why not reject events not on the morph.. rather than send rejectEvent call to the morph" (anEvent isMouse | anEvent isKeyboard and: [(self fullContainsPoint: anEvent cursorPoint) not]) ifTrue: [^ #rejected]. (self rejectsEvent: anEvent) ifTrue: [^ #rejected]. ^ defaultDispatcher dispatchEvent: anEvent with: self

Jan. 3, 2012