- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50075 Home: https://github.com/pharo-project/pharo-core

May 30, 2015

Re: [Pharo-dev] System Morphs in OSWindows

by Matthieu Lacaton

> > I think it would be better to name these for their function rather > than the package: > Nautilus openInExternalWindowOnPackage: nil. > GTPlayground external openInExternalWindow. > ThreadSafeTranscript external openInExternalWindow. > > I don't know if its a workable idea, but maybe something like > Nautilus external openInOSWindowOnPackage: nil. > GTPlayground external openInOSWindow. > ThreadSafeTranscript external openInOSWindow. It is a workable idea, we just need to agree on a syntax. Also good would be if an existing Morph could be moved to an external > window. From a menu choice would be entirely sufficient, but > super-bonus points for being able to drag it. This might also > facilitate a usage like this (but again not sure if thats a desirable > paradigm)... > > (Nautilus external openInOnPackage: nil) moveToExternalWindow. > (GTPlayground external openInOSWindow) moveToExternalWindow. > (ThreadSafeTranscript external openInOSWindow) moveToExternalWindow. > This should be possible but I see two different ways of doing so : - First we could keep the same Morph and dynamically change some of its features to match the requirements of an external window ( for example the action done when clicking on the close / expand / reduce boxes are not the same but there are other differences). Then we remove it from the World and open it in an OSWindow. - Or we could "save the state of the Morph" then delete it and directly open a new one suited for external window. I've quoted "save the state of the Morph" because if this option is chosen it will need to be refined. As for the "drag it outside part" I am sure it could be done. Currently when you are dragging a Morph, as soon as the HandMorph goes out of the World, when you release the mouse button the Morph goes back at its initial place so we could just change this behavior to make it move to an external window instead. But to be more flexible,maybe we could just keep both behavior and chose between one and the other by pressing a hotkey while dragging the Morph. BTW, I've recorded a short video to show you what it is possible to do with the new SDL version (it should also illustrate what I told Nicolai earlier) : https://www.dropbox.com/s/m27aa0flanocnlr/OSWindowMorph.mkv?dl=0 As you can see if you put the Morph inside the boundaries of the World, it seems as if it was actually opened in the world (put aside some differences like the fonts etc. but this is only due to the Athens rendering of Morphs and it won't matter in Bloc). For now it is heavily buggued (you can't opened two windows like that without crashing the VM :/) but SDL 2.0.4 is still in developement so I won't work more on it until it is released. Where we have for example Meta-O-O to open a browser, it could be > Meta-E-O to open in an external window. > Also, a hotkey could be held down when opening from a menu - similar > paradigm to web browsers between opening a new tab or opening a new > window. > Yeah that's a good idea. For the moment when opening from a menu the left and right clicks have the same behavior so it could even be something like left click => world and right click => external window. As well a Preference so that this can be set globally. A multitude of > open windows could be handled with a menu item in the task bar "Close > all > external windows". > > btw, I presume Morphs in these windows would still appear in the task > bar as usual. > I am not sure about that because as OS - Windows they appear in the taskbar of your OS and you can already manage them from here. How will the existing World paradigm play into this? Will external > windows be part of the same World? Or maybe the existing World can > have another level below it called like World-Screen? > The existing World paradigm will probably change with Bloc I guess. At first I thought that all these windows could be part of the same Bloc-space and that this Bloc-space would be dedicated to held external windows but I really need to speak with Alain about that. Many thanks for your feedback and ideas ! Cheers, Matthieu 2015-05-30 8:16 GMT+02:00 stepharo <stepharo(a)free.fr>: > > - If possible I'd like not to have to modify any Bloc code. If it is not > possible then as little as possible. > > What is the aversion here? Bloc is still developing and since its >> semantics are based on old-Morphic maybe this use-case is not >> considered. Adding this use-case may be an opportunity to make the >> overall system architecture simpler instead of needing workarounds. >> To what degree would Bloc already support this? >> > > What matthieu wants to say is that opening a window in an external sufrace > should > not impose to have some hacks into bloc and alain agrees with that and > will modify the > bloc architecture to handle separate native windows. > >> - These windows should be persistent but maybe not exactly like morphs. It >>> could be a button that the user needs to press in the window to toggle >>> the >>> persistence on and off (a bit like in the world menu to stick it to the >>> world if you see what I mean). >>> >> > I'm not sure that you want to have that behavior. Open windows should be > persisted. > > As well a Preference so that this can be set globally. A multitude of >> open windows could be handled with a menu item in the task bar "Close >> all > external windows". >> >> btw, I presume Morphs in these windows would still appear in the task >> bar as usual. >> >> >> > >

May 30, 2015

Re: [Pharo-dev] any idea about the broken Nautilus tests?

by stepharo

I fixed them.! Le 30/5/15 09:44, stepharo a Ã©crit : > Hi > > I wanted to integrate some changes but when I run the tests I get a > bunch of broken tests in Nautilus. > > Stef > >

May 30, 2015

Re: [Pharo-dev] untypeable key combination

by stepharo

For now could not we use when: send: to: instead of a block in key registration? Stef

May 30, 2015

Re: [Pharo-dev] untypeable key combination

by stepharo

Can anyone help me with this. I need a way to break the circular references. > a class is referenced by its compiled method > the compiled method is referenced by the method context > the method context is reference by a block context (the keymapping > action) > the block context is referenced by the registration item > the registration item is referenced by the pragma registration builder > the builder is reference by the method context (it is the method > argument) and here the > circle closes. > > > anyone? We did the same analysis when we were chasing memory leaks in 30. And this is why we favored when: send: to: instead of when:do: This is why igor hacked a ephemeron support. Now the right solution is nearly there: Spur

May 30, 2015

Re: [Pharo-dev] untypeable key combination

by stepharo

Definitively ephemerons will help to solve that nicely. I cannot wait for Spur. Stef Le 30/5/15 02:20, Eliot Miranda a Ã©crit : > Hi Nicolai, > > On Mon, May 18, 2015 at 12:28 PM, Nicolai Hess <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>> wrote: > > > > 2015-05-15 9:55 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de > <mailto:nicolaihess@web.de>>: > > > We now use a new class for the space-key as key combination. > fixed and included in 50045 > (https://pharo.fogbugz.com/default.asp?15529) > This way we don't end up with hundreds of obsolete class > instances. > > But the problem with circular references still exist. > 15535 <https://pharo.fogbugz.com/default.asp?15535> > break circular reference for keymappings > > I could need some help here, any idea how to work with the key > mapping registration without holding (or how to release) > strong references? > > > thanks in advance > nicolai > > > Can anyone help me with this. I need a way to break the circular > references. > > a class is referenced by its compiled method > the compiled method is referenced by the method context > the method context is reference by a block context (the keymapping > action) > the block context is referenced by the registration item > the registration item is referenced by the pragma registration builder > the builder is reference by the method context (it is the method > argument) and here the > circle closes. > > > Are there any dictionaries in the above? If there are then we can > probably use ephemerons to break the circularity. This will require > Spur and Pharo 5 or ^ (which ever is going to be based on Spur; I > can't remember which). This may seem like a ways off but it isn't. > > 2015-02-20 9:26 GMT+01:00 Marcus Denker > <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: > > > > On 19 Feb 2015, at 10:19, Nicolai Hess > <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: > > > > Fogbugz issue 14936 > > and slice in inbox > > > > After loading this slice, there are still many > references to the (now) obsolete class > KMUntypeableSingleKeyCombination. > > I tried to remove these references with the following code : > > > > NECPreferences popupShowWithShortcut: nil. > > KMSingleKeyCombination reset. > > KMSpecialCharSingleKeyCombination reset. > > KMRepository reset. > > > > > > But they arent removed. > > > > Anyone knows how to re-init all users of > KMUntypeableSingleKeyCombination ? > > > > > > Very strangeâ¦ using âexplore pointersâ with the old > inspector, it shows lots of instancesâ¦ I sadly have no > time to now look deeper, but the pointer explorer should > be a way to find who holds onto themâ¦ > > Marcus > > > > > > > > > -- > best, > Eliot

May 30, 2015

any idea about the broken Nautilus tests?

by stepharo

Hi I wanted to integrate some changes but when I run the tests I get a bunch of broken tests in Nautilus. Stef

May 30, 2015

Re: [Pharo-dev] System Morphs in OSWindows

by stepharo

- If possible I'd like not to have to modify any Bloc code. If it is not possible then as little as possible. > What is the aversion here? Bloc is still developing and since its > semantics are based on old-Morphic maybe this use-case is not > considered. Adding this use-case may be an opportunity to make the > overall system architecture simpler instead of needing workarounds. > To what degree would Bloc already support this? What matthieu wants to say is that opening a window in an external sufrace should not impose to have some hacks into bloc and alain agrees with that and will modify the bloc architecture to handle separate native windows. >> - These windows should be persistent but maybe not exactly like morphs. It >> could be a button that the user needs to press in the window to toggle the >> persistence on and off (a bit like in the world menu to stick it to the >> world if you see what I mean). I'm not sure that you want to have that behavior. Open windows should be persisted. > As well a Preference so that this can be set globally. A multitude of > open windows could be handled with a menu item in the task bar "Close > all > external windows". > > btw, I presume Morphs in these windows would still appear in the task > bar as usual. > >

May 30, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]13315) Morphic - NewList without icons

by stepharo

https://pharoweekly.wordpress.com/2015/05/30/future-new-widget-sets-is-comi… Le 29/5/15 21:24, Aliaksei Syrel a Ã©crit : > If you want to play load: http://ws.stfx.eu/F4DRC0CVSDII > Examples included. > > Cheers, > Alex

May 30, 2015

Re: [Pharo-dev] FogBugz (Case [Issue]13315) Morphic - NewList without icons

by stepharo

Aliaksei do you have a configuration of Brick? I can do one and do you have a jenkins job? Because we can do it. Stef Le 29/5/15 21:24, Aliaksei Syrel a Ã©crit : > Hi, > > We do some kind of a List for Bloc: > > Inline image 1 > > Main features: > > - List doesn't care what kind of morphs to contain. > - Flexible height of elements. Any will do. > - Items can resize. > - Elements can be partially visible. > - Different kind of caches. > - Selection strategies. > > Short demo video: > â > Bloc-Brick-List.mov > <https://docs.google.com/file/d/0B-bMBVDOi3oTMnNKVHhCQUJ2UlU/edit?usp=drive_…> > â > If you want to play load: http://ws.stfx.eu/F4DRC0CVSDII > Examples included. > > Cheers, > Alex

May 30, 2015