- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] System Morphs in OSWindows

by Ben Coman

On Sat, May 30, 2015 at 4:16 PM, Matthieu Lacaton <matthieu.lacaton(a)gmail.com> wrote: >> 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. Sure one option is to have a native window for every Morph. The other is to have only a WorldMorph as a native window holding other Morphs. I'm not sure which one I'd prefer, but I'd sure like the option of the latter. An example use-case... Torsten's recent video of Pharo on Raspberry Pie... not sure if the hardware is up to it, but it would be great to have a Pharo application displaying on a low resolution embedded LCD screen, with a normal development environment on a standard sized screen running off the same Pie. cheers -ben > > >> 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] untypeable key combination

by Nicolai Hess

2015-05-30 16:01 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Nicolai Hess wrote > > I don't fully understand what to change. > > If Spur will be ready for the next release, why don't we just wait... > I would like to better understand what is the problem and I am sure there is some kind of software pattern to prevent this circular reference situation. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/untypeable-key-combination-tp4794607p4829511.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 30, 2015

TxText first line top offset

by Aliaksei Syrel

Hi, is there a way to force first line in TxText to have custom offset from the top? Thanks Cheers, Alex

May 30, 2015

Re: [Pharo-dev] untypeable key combination

by Sean P. DeNigris

Nicolai Hess wrote > I don't fully understand what to change. If Spur will be ready for the next release, why don't we just wait... ----- Cheers, Sean -- View this message in context: http://forum.world.st/untypeable-key-combination-tp4794607p4829511.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 30, 2015

[pharo-project/pharo-core]

by GitHub

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

May 30, 2015

[pharo-project/pharo-core] 64aaee: 50077

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 64aaee4df4aab40ef01edff500f795063f37a6d9 https://github.com/pharo-project/pharo-core/commit/64aaee4df4aab40ef01edff5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-30 (Sat, 30 May 2015) Changed paths: M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1216_.st M Kernel.package/Number.class/instance/mathematical functions/interpolateTo_at_.st M Kernel.package/Point.class/instance/interpolating/interpolateTo_at_.st M Rubric.package/RubAbstractTextArea.class/class/settings/textColor.st M Rubric.package/RubScrolledTextMorph.class/README.md M Rubric.package/RubScrolledTextMorph.class/instance/defaults/defaultBackgroundColor.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50076.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50077.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50076.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50077.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50077 15639 rubric has a lot of hardcoded defaults (for colors, etc.) https://pharo.fogbugz.com/f/cases/15639 15138 inprecise interpolateTo:at: for floats https://pharo.fogbugz.com/f/cases/15138 http://files.pharo.org/image/50/50077.zip

May 30, 2015

styling in spotter preview broken ?

by Nicolai Hess

since 50064 some methods lost syntaxhighlight when previewed in spotter. This does not happens for all methods (but most of them) and I can not see a pattern. Styling is lost on short and or long methods

May 30, 2015

Re: [Pharo-dev] untypeable key combination

by Nicolai Hess

2015-05-30 10:53 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > > > 2015-05-30 9:49 GMT+02:00 stepharo <stepharo(a)free.fr>: > >> For now could not we use >> >> when: send: to: instead of a block in key registration? >> > > I will check. > That are many many senders. And I don't fully understand what to change. For example, a keymapping registration like (aBuilder shortcut: #browseIt) category: #SmalltalkEditor default: PharoShortcuts current browseShortcut do: [ :morph | morph browseIt ]. how to define it without the block? (aBuilder shortcut: #browseIt) category: #SmalltalkEditor default: PharoShortcuts current browseShortcut send: #browseIt to: ?what > > Thank you for your response. > > > >> >> Stef >> > >

May 30, 2015

monticello problems

by Esteban Lorenzano

Hi, Iâm having a lot of problems with monticello lately. And it is not just the change of MCLazyVersionInfo (that affects just the history). Now, looks like packages are keeping their own private list of repositories. Look at the example: Notice the âAllâ selection. Now see with âPackageâ selected: And it is breaking not just my nerves, but a lot of tools, etc. So, I donât know it this was on purpose to avoid repositories pollutionâ¦ but this is a bug or a bad change :) Can you confirm the problem? Esteban

May 30, 2015

shortcut change in pharo 50075

by Nicolai Hess

in pharo 50075 some shortcuts are removed (issue 15630 <https://pharo.fogbugz.com/default.asp?15630> Remove duplicate shortcut definition (TextEditors actionMap vs KM)) This is by intention. They were defined in text editors action maps and with the Keymapping framework (pragma keymap). Those were defined with two different "command"-keys (alt and ctrl). This change is not yet visible, although I defined a postload you will see the change only after TextEditor/SmalltalkEditior initialize (all alt+ shortcut are removed now, only the ctrl+ shortcuts should work) alt+space / ctrl+space -> select word alt+b/ctrl+b browseIt alt+c/ctrl+c copy alt+x/ctrl+x cut alt+v/ctrl+v paste alt+f/ctrl+f find Some "duplicate" shortcuts weren't removed because the shortcut defined with the keymap pragma don't work (at least on windows). For example: ctrl+a/alt+a defined with the action map and ctrl+a defined by keymap pragam this wasn't remove, because ctrl+a does not work on windows vm ctrl+m/alt+m defined by the action map ctrl+m defined by keymap pragma this wasn't remove, because ctrl+m does not work on windows vm please test the 50075 image, reinitialize editors subclasses and give feedback (linux and mac users too). thank you nicolai

May 30, 2015