- Pharo-dev - lists.pharo.org

Re: [Pharo-project] TilingWM improvements

by GastÃ³n Dall' Oglio

2011/5/31 laurent laffont <laurent.laffont(a)gmail.com> > >> I write a test, to do the following (but you can load this method and you >> can do now at hand to understand what I mean): maximize a window, use >> topWindowMoveTop, then topWindowMoveBottonLeft. The result is that the >> window is 1 / 8 the size of the screen (I attach screenshot). With the >> resolution size of the current monitors or the possibility of having >> multiple monitors and extend the main window Pharo through these, using >> windows of 1 / 4 of the screen can be a waste, plus there are tools that do >> not need more a small space. >> Moreover, this way you can only have 4 move operations: topWindowMoveTop / >> Bottom / Left / Rigth, since the rest of you combined the above. >> > > Ah OK. Estelle at our local coding-dojo today told me that in xmonad > there's this sort of behavior. > > Cool :) I don't know about xmonad, but I like this: xmonad is *tiling*.xmonad automates the common task of arranging windows, so you can concentrate on getting stuff done. > Maybe another way is to add #moveUpward / #moveDownward / #moveLeftward / > #moveRightward mapped to keyboard shortcuts. > yes, and these names are best for these operations. But considered to have the fewest possible operations: xmonad is *minimal*.out of the box, no window decorations, no status bar, no icon dock. just clean lines and efficiency. > > > Laurent. > > > > > > >> >> >> >>> I've implemented automatic refresh (see TilingWMSettings >>> class>>initialize). May break the first time you load it if you have a >>> version before the change. >>> >> >> Yes, I see, thanks. >> >> >>> >>> There's a first shot of GUI controls for world snapshot / navigation but >>> it needs more work to be intuitive. >>> >>> >> There are many new features, it is time to make a new screencast:) >> >> >> >> >>> Laurent. >>> >>> 2011/5/28 GastÃ³n Dall' Oglio <gaston.dalloglio(a)gmail.com> >>> >>>> Laurent, coincidere change this method (o part of): >>>> >>>> TilingWM>>newTopWindowBoundsInArea: aBlock >>>> SystemWindow topWindow bounds: (aBlock value: world clearArea). >>>> >>>> to this one: >>>> >>>> TilingWM>>newTopWindowBoundsInArea: aBlock >>>> | topWindow | >>>> (topWindow := SystemWindow topWindow) isMaximized >>>> ifTrue: [ topWindow expandBoxHit. topWindow bounds: (aBlock value: world >>>> clearArea) ] >>>> ifFalse: [ topWindow bounds: (aBlock value: topWindow bounds) ] >>>> >>>> >>>> For one hand this solve the problem of maximized state on moved window, >>>> and for other hand apply recursive "moving" of window based in their current >>>> bounds (but not usable display area) if that is not in state maximize (I >>>> choose this rule for my convenience). >>>> >>>> --- >>>> >>>> When I load new version of this package, I use the Settings to see new >>>> version de la barra, but the old version keep visible too, and I use >>>> SHIFT-ALT-Click to see the halos and remove this. Is possible clean up of >>>> older versions of bar automatically? >>>> >>>> ---- >>>> >>>> And I see that you comming work in TWMWindowSnapshot :) I like it, I >>>> hate wasting time accommodating the size and position of the windows >>>> manually because I want to have another hearing, again and again! >>>> >>>> >>>> >>> >> >

May 31, 2011

Re: [Pharo-project] Numerical packages

by Nicolas Cellier

2011/5/31 Eliot Miranda <eliot.miranda(a)gmail.com>: > HiÂ Nicolas, > > On Tue, May 31, 2011 at 1:22 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> I can tell you about Smallapack as author. >> >> First advantage: using a state of the art robust library >> LAPACK + BLAS is the core of Matlab/Octave/Scilab/R/etc... >> It is robust in terms of API stability, numerical stability, and >> number of bugs (try finding known ones). >> >> Second advantage: combine advantages of >> - a fast and efficient number crunching library for low level primitives >> - and our favourite IDE for higher level code (interpreter debugger >> browser etc...) >> That's the exact strategy developped by Matlab. >> As a bonus, Smalltalk interpreter is faster than Matlab, and don't ask >> me about Matlab language design (non) choices ;) >> To reach Matlab core preformances, you need an optimized version of >> BLAS (ATLAS for example). >> I imagine versions of these libraries could exploit multi-core >> parallelism (but I did not check status of >> http://www.netlib.org/scalapack/) >> >> Good news, I have a working Smallapack in both Dolphin and VW. >> Unfortunately, the main drawback is that Squeak/Pharo is not in that list. >> >> First, Smallapack may crash the image in Squeak/Pharo... >> I've not found the reasons, but suspect some FFI problems. >> Maybe I should try using a plugin rather than FFI. That seems doable >> since low level FFI code is generated automatically from Lapack >> comments. It's just a matter of changing code generator to generate >> slang rather than FFI... > > How easy is this to test? Â What does one have to install? Â Is it all freely > available? Â I'd like to find time to test this in the ReentrantFFIPlugin. > Â Seems like a good test case. > http://www.squeaksource.com/Smallapack.html - is MIT - has a few tests For compiling 16+ args, there is a Compiler mcz in the repository (a few versions back trunk, so a merge might be necessary). This is useless if you can upgrade to 31 args. See the wiki tab for load order. At my last attempts, MC failed to initialize correctly; if a debugger opens on a nil class var, then try redoing some initialize... I may help this week end (thursday thru saturday). Nicolas >> >> Second drawback is that loading Smallapack in a Squeak/Pharo image >> requires some pre-requisite. >> This is because LAPACK has the bad property of having functions with >> more than 16 arguments. >> Squeak/Pharo Compiler cannot handle methods with that many arguments. >> I have a Compiler hack ready for handling this case. > > That's easy to fix. Â The bytecode set supports up to 31 args. Â e just need > to push fixes to the compiler front-end right? > >> >> I have not automated the process because I'm not so sure that >> Gofer/Metacello are good for installing such hack (Compiler overrides >> may seem evil). >> But I can help any good will. >> >> So, if you're after an off-the-shelf library working out of the box, >> Smallapack is not OK. >> However, if above goals fit yours, and you're willing to help, I'll be >> happy to revive the project and inject a few hours into it. >> >> Nicolas > > best, > Eliot >> >> 2011/5/31 Ignacio Vivona <altobarba(a)gmail.com>: >> > Hi all! I'm currently planning on doing some work related to resolving >> > partial differential equations (shallow water) in pharo. I'm seeing a >> > couple >> > of project for dealing with vectors, matrices and some other math >> > things. >> > http://www.squeaksource.com/DHBNumerical.html >> > http://www.squeaksource.com/MatrixPlugin.html >> > http://www.squeaksource.com/Numerics.html >> > http://www.squeaksource.com/Smallapack.html >> > Has anyone any experience working with these? >> > Also I'm looking at Mathmorphs (does it work in >> > pharo?)Â http://mate.dm.uba.ar/~caniglia/mathMorphs.htmlÂ and >> > DrGEOÂ http://community.ofset.org/index.php/DrGeoÂ for doing the graphical >> > interaction. >> > If someone knows of some other project related please guide me. >> > Thanks in advance, >> > Ignacio Vivona >> > >

May 31, 2011

Re: [Pharo-project] A radical proposal (to cut down dead code)

by Casimiro de Almeida Barreto

Em 31-05-2011 16:12, Igor Stasenko escreveu: > On 31 May 2011 21:44, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> Another idea (don't know how hard it is) is to have test coverage + comment >> coverage in Hudson. >> Then we can start to consider that dead code = code with no test or no >> comment. > Laurent, have you tried to run lint rule checker in pharo image? > I tried once and if i remember correctly, there are like 30000 notices. > Now, what you think, is it possible for any human to visit all of them > step by step > analyze and then fix the code? It is enormous amount of data (and most > of it is just white noise, > or insignificant detail). Now how to filter that noise and address the > only things which you should take care of? Here comes the importance of having a foundation or any other kind of entity enabled to run for financial resources necessary to keep people, doing these "insane tasks" :) as well as physical resources (computers with versions of OS, etc)... > And since we're continuting development, every time you doing an > update, this stuff should be revisited, > compared and cross-checked again. And we don't have such facility: > take image A and B, and compare their lint output. Here comes the importance of agreeing about a closed (in terms of scope) and reduced (in terms of size (ie, # of classes and messages)) core that can be frozen while cleaning is done. Otherwise it's like manufacturing an airplane while it's flying from factory to owner... which increases the "insanity factor" several orders of magnitude. > I imagine this would require a quite sophisticated database , with UI > on top of that, which will allow you to navigate > through these notices mark them as invalid, or fixed etc etc.. > What i mean that automated tools is cool. But they cannot solve all > our problems: every such issue should be analyzed and considered by > developer. > Because we're still not yet at the point, where system can reason > about itself and automatically improve itself without need of our > attention :) > If this day will come, then it will be the end of humanity (at least > in its current form - homo sapiens sapiens ;) > >> Laurent. >> Additionally, one issue with metacello is that it incorporates both infra-structure stuff and things that are more like end-user applications. It's not a tradition to keep things orthogonal: there is code that inserts/deletes/modifies things in places that should constitute foundations. For instance, some time ago there was discussion about ad-hoc (thus mostly undocumented) methods/messages in places like OrderedCollection... What's the sense in this state of affairs? IMHO it's an ad-hoc situation and cleaning process must fix & transform it into a sustainable situation. That's overcoming past. CdAB

May 31, 2011

Re: [Pharo-project] Metacello as the system evolves... (Fwd from Seaside-General: Which image for deployment?)

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > can you quote the name of the person who wrote the mail? > Sure, I wrote the original post, and the response was from Lukas. Sean -- View this message in context: http://forum.world.st/Metacello-as-the-system-evolves-Fwd-from-Seaside-Gene… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 31, 2011

Re: [Pharo-project] Numerical packages

by Eliot Miranda

Hi Nicolas, On Tue, May 31, 2011 at 1:22 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > I can tell you about Smallapack as author. > > First advantage: using a state of the art robust library > LAPACK + BLAS is the core of Matlab/Octave/Scilab/R/etc... > It is robust in terms of API stability, numerical stability, and > number of bugs (try finding known ones). > > Second advantage: combine advantages of > - a fast and efficient number crunching library for low level primitives > - and our favourite IDE for higher level code (interpreter debugger > browser etc...) > That's the exact strategy developped by Matlab. > As a bonus, Smalltalk interpreter is faster than Matlab, and don't ask > me about Matlab language design (non) choices ;) > To reach Matlab core preformances, you need an optimized version of > BLAS (ATLAS for example). > I imagine versions of these libraries could exploit multi-core > parallelism (but I did not check status of > http://www.netlib.org/scalapack/) > > Good news, I have a working Smallapack in both Dolphin and VW. > Unfortunately, the main drawback is that Squeak/Pharo is not in that list. > > First, Smallapack may crash the image in Squeak/Pharo... > I've not found the reasons, but suspect some FFI problems. > Maybe I should try using a plugin rather than FFI. That seems doable > since low level FFI code is generated automatically from Lapack > comments. It's just a matter of changing code generator to generate > slang rather than FFI... > How easy is this to test? What does one have to install? Is it all freely available? I'd like to find time to test this in the ReentrantFFIPlugin. Seems like a good test case. > > Second drawback is that loading Smallapack in a Squeak/Pharo image > requires some pre-requisite. > This is because LAPACK has the bad property of having functions with > more than 16 arguments. > Squeak/Pharo Compiler cannot handle methods with that many arguments. > I have a Compiler hack ready for handling this case. > That's easy to fix. The bytecode set supports up to 31 args. e just need to push fixes to the compiler front-end right? > I have not automated the process because I'm not so sure that > Gofer/Metacello are good for installing such hack (Compiler overrides > may seem evil). > But I can help any good will. > > So, if you're after an off-the-shelf library working out of the box, > Smallapack is not OK. > However, if above goals fit yours, and you're willing to help, I'll be > happy to revive the project and inject a few hours into it. > > Nicolas > best, Eliot > 2011/5/31 Ignacio Vivona <altobarba(a)gmail.com>: > > Hi all! I'm currently planning on doing some work related to resolving > > partial differential equations (shallow water) in pharo. I'm seeing a > couple > > of project for dealing with vectors, matrices and some other math things. > > http://www.squeaksource.com/DHBNumerical.html > > http://www.squeaksource.com/MatrixPlugin.html > > http://www.squeaksource.com/Numerics.html > > http://www.squeaksource.com/Smallapack.html > > Has anyone any experience working with these? > > Also I'm looking at Mathmorphs (does it work in > > pharo?) http://mate.dm.uba.ar/~caniglia/mathMorphs.html and > > DrGEO http://community.ofset.org/index.php/DrGeo for doing the graphical > > interaction. > > If someone knows of some other project related please guide me. > > Thanks in advance, > > Ignacio Vivona > >

May 31, 2011

Re: [Pharo-project] [squeak-dev] Fwd: usability of Pharo and Squeak

by Eliot Miranda

2011/5/31 Janko MivÅ¡ek <janko.mivsek(a)eranova.si> > On 31. 05. 2011 18:35, Ramon Leon wrote: > > > Tabs would make it more like practically every other program available > > that needs multiple edit windows. Tabs are better than multiple > > windows. Look around, tabs won; the battle is over. Tabbed browsing of > > the net or 15 instances of Firefox open? Seriously, you think multiple > > windows are better? Really? > > Agreed, tabs won, therefore we need to implement it and this will be a > big step forward for usability of our tools. Not only for newcomers, for > us too. You will see sooner or later that tabbed windows are better than > full ones. I had such experience from VW and other VisualWorkers would > probably confirm that. > > Ok, a right combo of both, tabbed and full. Say two browsers windows > with a reasonable amount of methods open in tabs. And adding back button > .. well that would be near nirvana considering current state :) > Take a look at my multi-window browser in Squeak trunk. Its not tabs. Instead its a drop-down menu from the window title area of windows sharing the one main menu. It works well for me and doesn't waste vertical real estate on the tabs themselves. You can also populate them programmatically, look at openCogMultiWindowBrowser in the VMMaker-oscog fork. You need to enable the Multi-Window Browser preference in browsing and open a new browser to enable them. HTH Eliot > Best regards > Janko > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si > >

May 31, 2011

Re: [Pharo-project] testing ui errors in headless mode

by Tudor Girba

Hi, On 31 May 2011, at 22:32, Igor Stasenko wrote: > On 31 May 2011 23:15, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi Igor, >> >> Sorry for the late reply. >> >> >> >> On 26 May 2011, at 17:48, Igor Stasenko wrote: >> >>> On 26 May 2011 17:03, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> Hi, >>>> >>>> I tried several ways to get my head around this problem, but I do not know how to proceed. Can anyone help? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 25 May 2011, at 21:21, Tudor Girba wrote: >>>> >>>>> Hi, >>>>> >>>>> We have some smoke tests in Moose that basically spawn a UI and check for Error. >>>>> >>>>> This used to work when running headless in Pharo 1.2 but now they fail in Pharo 1.3. I believe this has to do with the new changes in the UI Manager, but I do not know what to do. >>>>> >>>>> To reproduce the problem, you can simply call a Pharo-1.3.image in headless mode and file in the attached st file that: >>>>> >>>>> - installs a simple test: >>>>> HeadlessTest>>testStartup >>>>> self shouldnt: [1 inspect] raise: Error >>> >>> Tudor, your test is wrong. >>> During image startup and in headless mode calling inspector will and >>> should raise an error. >>> Because inspecting object requires a presence of UI. >>> But there's no UI in headless mode and prohibited from use during >>> image startup phase, because >>> you cannot start asking questions from user before properly >>> initializing everything related to startup. >>> Startup is called startup on purpose: is should not be interrupted nor >>> require user's interaction. >>> >>> Assume that you don't have Morphic loaded in your image, then what you >>> expect to happen if you do >>> 1 inspect >>> ? >> >> I understand now that the test is wrong. I just wanted to offer an example of spawning a ui, but I think I found the problem like this :). >> >> Now, the thing is that my test tests that triggering the entries from a menu does not result in an error. And inspect or browse happen to be among the menu entries. Is there a way to still have this test working on the server? >> >> Should I put a guard condition in the method triggering the inspector? That sounds bad. Any other ideas? >> > > Yes, you could swallow all ErrorNonInteractive. > So if you will know that something will lead to UI interaction, you > can catch ErrorNonInteractive. > Since there is no UI you won't proceed further, but still will know > that during running the test some UI is involved. > > So, actually a following should pass: > > UIManager default isInteractive ifFalse: [ > self should: [1 inspect] raise: ErrorNonInteractive > ] > > The problem is that there is some missing protocol in > NonInteractiveUIManager (because at the time i was adding it , i > covered all methods, > but then some more stuff were added to morphic ui manager without > parallel extension to other ui managers, > so the test above can fail because you will get DNU error instead of > ErrorNonInteractive ) I tried it: testStartup self shouldnt: [[1 inspect] on: ErrorNonInteractive do: [:x | ]] raise: Error But this still fails. You can try using the attached st file. Cheers, Doru >> Cheers, >> Doru >> > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

May 31, 2011

Re: [Pharo-project] [Pharo-users] Tiling Window Manager - status update

by laurent laffont

On Tue, May 31, 2011 at 8:25 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > I'll change Meta and stuff to match Ctrl, Cmd and Alt tonight. > > In the current bleeding edge i've splitted shortcut declaration from > settings declaration, so we can put shortcuts without putting them in > settings. And it avoids the error you had yesterday when resetting the > keymaps ;). > Cool ! Don't forget to sleep :) Laurent > > The problem with CTRL has to do with: > > > http://code.google.com/p/pharo/issues/detail?id=3748&q=events&colspec=ID%20… > > That I think is a VM bug :( > Maybe it has to be one of the first things to have a look at 1.4 > > > On Tue, May 31, 2011 at 3:16 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Thanks Guillermo. >> >> KeyMapping is really really really important !!! >> >> Actually shortcuts using CTRL don't work and I would like CTRL + xxx >> rather META + xxx for TWM >> >> Laurent. >> >> On Tue, May 31, 2011 at 5:08 PM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> I've freezed the version of keymapping you use in TilingWindowManager >>> with number 1.7: >>> >>> Gofer it >>> squeaksource: 'ShortWays'; >>> package: 'ConfigurationOfKeymapping'; >>> load. >>> >>> (Smalltalk at: #ConfigurationOfKeymapping project version: '1.7') load. >>> >>> Because I'm doing some changes >>> >>> >>> On Mon, May 30, 2011 at 6:22 PM, laurent laffont < >>> laurent.laffont(a)gmail.com> wrote: >>> >>>> First thanks to all people that send patches (and tests !!). Still not >>>> haven't merged all of them - don't hesitate to post in repository so code is >>>> not lost. Yes I will merge layout policies. >>>> >>>> Gofer it >>>> squeaksource: 'TilingWindowManager'; >>>> package: 'TWM'; >>>> load. >>>> (Smalltalk at: #StandardUITheme) beCurrent. >>>> (Smalltalk at: #TWMBar) showTWMBar:true. >>>> >>>> Tested on PharoCore 1.2 and Pharo 1.3. >>>> >>>> Now this has support for world snapshot, that means you can arrange the >>>> windows and take a snapshot of the layout. Then you can restore these >>>> layouts later. (icons camera, <, > and trash). I'm not entirely satisfied >>>> with this, thanks for feedback. >>>> >>>> >>>> In Pharo 1.3 there's initial integration with KeyMapping. To load: >>>> >>>> >>>> Gofer it >>>> squeaksource: 'ShortWays'; >>>> package: 'ConfigurationOfKeymapping'; >>>> load. >>>> >>>> (Smalltalk at: #ConfigurationOfKeymapping project version: >>>> #bleedingEdge) load. >>>> >>>> >>>> Then in settings browser > Keymappings > Tiling Window Managers you have >>>> all actions of the dock mapped. >>>> >>>> Not all shortcuts are working, don't know why, if people can test and >>>> find good shortcuts thank you. >>>> >>>> Creating a nice Metacello Configuration for TWM will be appreciated :) >>>> >>>> >>>> Cheers, >>>> >>>> Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> >>>> >>>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>>> Blog: http://magaloma.blogspot.com/ >>>> Developer group: http://cara74.seasidehosting.st >>>> >>>> >>> >> >

May 31, 2011

Re: [Pharo-project] A radical proposal (to cut down dead code)

by laurent laffont

On Tue, May 31, 2011 at 9:12 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 31 May 2011 21:44, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > Another idea (don't know how hard it is) is to have test coverage + > comment > > coverage in Hudson. > > Then we can start to consider that dead code = code with no test or no > > comment. > > Laurent, have you tried to run lint rule checker in pharo image? > No - I talk about test coverage, not lint. I don't think lint worth running on a full image. Test coverage is really useful. Indeed, I use test coverage on my projects every day. Lint once a year :) Laurent. > I tried once and if i remember correctly, there are like 30000 notices. > Now, what you think, is it possible for any human to visit all of them > step by step > analyze and then fix the code? It is enormous amount of data (and most > of it is just white noise, > or insignificant detail). Now how to filter that noise and address the > only things which you should take care of? > And since we're continuting development, every time you doing an > update, this stuff should be revisited, > compared and cross-checked again. And we don't have such facility: > take image A and B, and compare their lint output. > I imagine this would require a quite sophisticated database , with UI > on top of that, which will allow you to navigate > through these notices mark them as invalid, or fixed etc etc.. > What i mean that automated tools is cool. But they cannot solve all > our problems: every such issue should be analyzed and considered by > developer. > Because we're still not yet at the point, where system can reason > about itself and automatically improve itself without need of our > attention :) > If this day will come, then it will be the end of humanity (at least > in its current form - homo sapiens sapiens ;) > > > Laurent. > > > -- > Best regards, > Igor Stasenko AKA sig. > >

May 31, 2011

[Pharo-project] TilingWM - layout policies

by laurent laffont

Thanks to Stefan, Serge, Patrick and Estelle now you can choose a Layout Strategy in settings. Actually there's Horizontal (default) and Vertical (last used windows fills all remaining space) strategies. To add your own just subclass TWMLayoutStrategy and implement #tileWindows: Cheers, Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

May 31, 2011