May 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Alt-tab between windows

by Ben Coman

On Sat, May 16, 2015 at 5:35 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > my answer on stackoverflow: > > well... you hit one of our weaker spots :) > > Keybindings are not in his best shape, but: > > - Actually, alt+tab is already set to "switch window" activity. The > problem is that does not work all the time (for example, it does not work > on Playground). > - This is because there are some hardcoded logic there, who we are > removing slowly from the system (some of those parts have more than 15yrs > since they come from before Pharo has born). > - Someone (probably in a failed attempt to fix the playground, or the > hardcodes) forget a halt in the method who creates a new preview window... > so even if you reach that part of the system, you will have a debugger. Of > course, you will be able to restore correct behaviour by just removing the > breakpoint, but that will not correct the fact "switch windows" will not be > available everywhere. > - I opened a bug entry for it: https://pharo.fogbugz.com/f/cases/15546, > in case you want to follow the issue (you will need an account there, I'm > sorry for that). > > In any case, we are moving out this hardcode stuff, and you can check all > currently available settings going to **World Menu/System/Keymap Browser** > (they are a lot, we are also playing with ideas on how to show better this > combinations... emacs style, popup notifications, etc.) > > Esteban > > ps: I will like to have a solution for this, if anyone can help a bit in > this areaâ¦ but it has to be a solution using the keybindings framework. I > will deny integration to any hardcoded solution :) > I thought I'd have a look at this (a reason to dip my toe into the keybindings framework for the first time). Not sure if I'm heading down the right track, but the first part of just responding to key presses was much easier than I thought it might be, so I thought there might be general interest. So far I've just done... KMCategory subclass: #TaskListGlobalShortcut instanceVariableNames: '' classVariableNames: '' category: 'Morphic-Widgets-Taskbar' TaskListGlobalShortcut >> isGlobalCategory ^true TaskListGlobalShortcut >> cycleLeft <shortcut> ^ KMKeymap shortcut: $[ command action: [ self inform: 'cycle window left' ] TaskListGlobalShortcut >> cycleRight <shortcut> ^ KMKeymap shortcut: $] command action: [ self inform: 'cycle window right' ] KMRepository reset. </feeling='small sense of achievement'> cheers -ben

May 19, 2015

Re: [Pharo-users] Alt-tab between windows

by Esteban A. Maringolo

2015-05-19 11:41 GMT-03:00 Avdi Grimm <avdi(a)avdi.org>: > It took thousands of programmers decades of work in many different languages > to create this variety. I'd hate to see the smaller Pharo community pour > tons of effort into re-inventing these solutions. > > Which is why I'm suggesting that it may be more helpful to re-frame the > problem. General purpose window management is a problem that has been solved > many times over. Do you really want to do it yet again? I suspect that with > some careful examination of Pharo coding workflows, you could find a way to > obviate the need for zillions of windows, and solve a simpler problem > instead. +1 Esteban A. Maringolo

May 19, 2015

Re: [Pharo-users] Garage and SQLite file databases, general project structure

by Sven Van Caekenberghe

Ben, (comments inline) > On 18 May 2015, at 17:46, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Mon, May 18, 2015 at 7:06 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 18 May 2015, at 12:13, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > Hi Sven, I'll take that into account. I did not think about using an empty host/port pair, maybe because of the extra slash. > > > > Also, I do not need to convert the file name to a file reference. That is done in sqlite by the sqlite library itself, so it's less work for the driver. The only need I need to do is: > > - for nbsqlite get the file name > > - for opendbx get the full file name and split into directory + file name because they are two different arguments for the library. > > I think that if you want to view (part of) a URL as a file system path and/or if you want to work with that path (splitting it directory/file for example), converting to a file reference is a good idea. ZnUrl can do file interpretation to some degree (#directory & #file, #isDirectoryPath & #isFilePath), but not very well (it is not its primary application). > > ZnUrl>>#path is actually not the best selector to use. It uses the internal representation. Like #directory & #file, #isDirectoryPath & #isFilePath, these leak some internals. ZnUrl>>#pathString is better, and will give you a leading $/ while encoding everything correctly. > > Also, relative File URLs simply do not exist. > > This sparked my interest to read RFC3986 (https://tools.ietf.org/html/rfc3986#section-5.2.4) > which says: > > A relative reference that begins with a single slash character is termed > an absolute-path reference. A relative reference that does not begin with > a slash character is termed a relative-path reference." > > The path segments "." and "..", also known as dot-segments, are defined > for relative reference within the path name hierarchy. They are intended for > use at the beginning of a relative-path reference to indicate relative position > within the hierarchical tree of names." > > Within a representation with a well defined Base URI of > "http://a/b/c/d;p?q" > a relative reference is transformed to its Target URI as follows. > "g:h" = "g:h" > "g" = "http://a/b/c/g" > "./g" = "http://a/b/c/g" > "../g" = "http://a/b/g" > "/g" = "http://a/g" > > So slightly as an aside, this makes me wonder if we should consider that when the Image is a opened as a file, its Base URI can be considered to be > 'file:///b/c/Pharo.image' > such that its reasonable to have the following relative references transformed as follows: > 'g:h' asUrl asString "--> 'g:h' > 'g' asUrl asString "--> 'file:///b/c/g' > './g' asUrl asString "--> 'file:///b/c/g' > '../g' asUrl asString "--> 'file:///b/g' > '/g' asUrl asString "--> 'file:///g' > > Effectively, the default scheme is #file rather than nil, as it is currently. > > > RFC3986 5.2.2. "Transform References" shows a non-strict case where it seems that following intuitive example is valid > 'file:///./g' asUrl asString "--> file:///b/c/g' " > per this line... > T.path = merge(Base.path, R.path); > > > RFC3986 5.1.2. "Base URI from the Encapsulating Entity" indicates we could consider the Base URI for the sqlite3 scheme to derive from the Image's 'file:///b/c/Pharo.image' URI to be... > 'sqlite3:///b/c/Pharo.image' > such that per 5.2.2. the following would be valid... > 'sqllite3:///./g' asUrl asString "--> sqllite3:///b/c/g' " > > > All that is from a patchy skim of RFC3986, so maybe I got it wrong, but maybe its a view worth considering. I made the following commits: === Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.53 Author: SvenVanCaekenberghe Time: 19 May 2015, 4:31:02.297452 pm UUID: 55fd5688-02f5-4ac7-b112-3ef2721000e5 Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.52 Extend the ZnUrl API a bit, for convenience: ZnUrl class>>#image returns a File URL to the current image (Thx Ben Coman) ZnUrl>>#+ as an alias for ZnUrl>>#withRelativeReference: ZnUrl>>#asFileUrl return a copy with the scheme changed to file:// ZnUrl>>#portIfAbsent: to handle missing ports Add some unit tests for the new API === Name: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.36 Author: SvenVanCaekenberghe Time: 19 May 2015, 4:31:30.415175 pm UUID: a4779a63-c75e-4cae-b35e-c9a5861a68eb Ancestors: Zinc-Resource-Meta-Tests-monty.35 Extend the ZnUrl API a bit, for convenience: ZnUrl class>>#image returns a File URL to the current image (Thx Ben Coman) ZnUrl>>#+ as an alias for ZnUrl>>#withRelativeReference: ZnUrl>>#asFileUrl return a copy with the scheme changed to file:// ZnUrl>>#portIfAbsent: to handle missing ports Add some unit tests for the new API === Name: Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.8 Author: SvenVanCaekenberghe Time: 19 May 2015, 4:32:04.050748 pm UUID: a84ff5a8-584c-4160-93f2-0f305679a9e0 Ancestors: Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.7 Add ZnFileUrlTests>>#testImage === This does not change the current default behaviour, but it makes it a lot easier to work with relative references: ZnUrl image + 'foo.txt' => "file:///Users/sven/Develop/Smalltalk/foo.txt" You just have to choose an appropriate base URL: 'postgresql://user:password@localhost:5432/default' asUrl + 'test' => "postgresql://user:password@localhost:5432/test" However, when you override the host, the port (actually the whole authority) is reset as well (according to my interpretation of the RFC anyway), that is why I added #portIfAbsent: 'postgresql://production/user-db' asUrl portIfAbsent: 5432 => 5432 I also added #asFileUrl to help in the common case of interpreting any scheme as referring to a file path. After that conversion, one will probably want to do an #asFileReference. > But there is #withRelativeReference: which follows the relevant specs (check the tests). > > FileReference should also deal better with platform issue, ZnURL is much more abstract, by definition. > > I hope this makes sense ;-) > > > Now, having a look at what we can do with znurl > > > > In windows it looks that we are ok > > 'sqlite3:///c:/myDirectory/myfile.db' asUrl path. > > "'c:/myDirectory/myfile.db'" > > 'sqlite3:///c:\myDirectory\myfile.db' asUrl path. > > "'c:\myDirectory\myfile.db'" > > See also #testWindowsDriveNamesInFileUrl > > > But in linux even if I put extra slashes it keeps removing them... And it makes difficult to recognize relative from absolute file paths: > > > > "Relative path c/myDirectory/myfile.db OK" > > 'sqlite3:///c/myDirectory/myfile.db' asUrl path. > > "'c/myDirectory/myfile.db'" > > > > "Absolute path /c/myDirectory/myfile.db not OK" > > 'sqlite3:///c/myDirectory/myfile.db' asUrl path. > > "'c/myDirectory/myfile.db'" > > > > Adding Slashes > > 'sqlite3:////////c/myDirectory/myfile.db' asUrl path. > > "'c/myDirectory/myfile.db'" > > > > > An intuitive semantic would be... > ''sqlite3:///./c/myDirectory/myfile.db' asUrl pathPrintString > "--> /my/pharoImagePath/c/myDirectory/myfile.db" > > > > > Another concern is that garage as it is works in Pharo 3, 4 and 5. Then if we update Zn I'll have to add Zn to my dependencies and load the correct version accordingly, what do you think? (I prefer that to back porting) > > Just depend on the latest stable release of Zinc, it is (still) supported for 2.0 and up. > > > Guille > > > > > > El lun., 18 de may. de 2015 a la(s) 11:27 a. m., Sven Van Caekenberghe <sven(a)stfx.eu> escribiÃ³: > > Hi Guile, > > > > > On 18 May 2015, at 10:48, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > > > Well, I wanted in general to have a single easy-to-learn way to build a database connection string for all drivers. > > > > > > [driverid]://[host][:port]/[databasename]?[properties] > > > > > > Then, for sqlite I would like to have: > > > > > > sqlite3://myDirectory/myfile.db > > > > > > or > > > > > > sqlite3://memory > > > > > > Now, for Garage 0.1 I was using ZnUrl to parse the connection strings and that is not working for urls like the following because if the schema is not 'file' then the parser fails to to transform the port (an empty string in this case for the parser) to an integer > > > > > > sqlite3://c:/myDirectory/myfile.db > > > > > > In bleeding edge I am using an alternative parser that does no conversions and allows urls like that one. > > > > I understand the reasoning here, but I would suggest that you at least consider changing your mind. Over time, a lot of work went into ZnUrl, and many people used it and helped fixing many problems. Recently we tried to improve the situation for special schemes a bit (for git URLs). We're not yet there, but you (your use case) could help improving the situation. > > > > I tried to take a principled approach regarding the specs (not that there is one clear spec, haha), but edge cases should still be possible. > > > > Consider the following: > > > > 'postgresql://localhost:14433/test-db?username=john&password=123456' asUrl. > > 'postgresql://john:123456@localhost:14433/test-db?encoding=utf8' asUrl. > > 'postgresql://localhost/default' asUrl. > > > > 'sqlite3:///myDirectory/myfile.db' asUrl. > > 'sqlite3://memory' asUrl. > > > Would memory have a hierarchical structure? i.e. if I wanted to run two sqllite3 instances in memory? > > > > 'sqlite3:///c:/myDirectory/myfile.db' asUrl. > > > > According to me, these all parse correctly. Of course, ZnUrl does not know or understand what is possibly special about any particular scheme (apart from HTTP(S)). Still, it is just an object that can be manipulated. > > > > The default port can be computed along the lines of #portOrDefault, maybe we could add a #portIfAbsent: ? > > > > Conversion to a file references can be done as follows: > > > > 'sqlite3:///c:/myDirectory/myfile.db' asUrl > > copy scheme: #file; asFileReference. > > > > Which basically reads as: 'I know this is not a file:// URL proper, still I want to interpret it as if it were one'. Maybe we could add a #forceAsFileReference ? > > > > Anyway, you get the idea. You know I am willing to help. > > > > Sven > > > > > > > > > > > Looking through Zinc I notice that the schemes are symbols. Any plans to make these classes? To maybe(?) make it easier to extend to other schemes (http://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml) ? Or do you consider that outside the scope of Zinc ? Well, it is a 'problem area' (design/implementation wise). Your suggestion makes sense though: to make the schemes objects so that they could implement specific behaviour (rather than making many subclasses of ZnUrl). I will think about this, thanks for the idea ! Sven > cheers -ben

May 19, 2015

Re: [Pharo-users] Smalltalkhub password reset

by Dimitris Chloupis

add to your list also Bitbucket. I am not so sure if Dale also supports mecurial apart from git but in that case I dont think there is anything similar to gitfiletree for pharo. I have been using Github for my Pharo projects for over a year now and I add my projects also in Configuration Browser (I have three projects currently , Ephestos, Nireas and MorphicDoc) and I have had zero issues so far. On Tue, May 19, 2015 at 4:16 PM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 19 May 2015, at 15:11, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > VW/Envy FTW :-P > > > but in Pharo you can choose to use sthub, ss3 or github. ENVY, however, is > out of the menuâ¦ soâ¦ out of order! :) > > Esteban > > > On May 19, 2015, at 07:58, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > I stay with Github ;) > > On Tue, May 19, 2015 at 10:51 AM mtk <kemper.mt(a)googlemail.com> wrote: > >> Hi Steph, >> >> would it be better to stay with SqueakSource3? >> >> Kind regards >> >> Marcus >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Smalltalkhub-password-reset-tp4827089p4827230.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com >> <http://nabble.com/>. >> >> > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > >

May 19, 2015

Re: [Pharo-users] Alt-tab between windows

by Avdi Grimm

On Tue, May 19, 2015 at 3:53 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > > About general GUI and UI designs its not any less nightmarish to open > multiple windows in Pharo than it is to open multiple buffers in emacs. The > diffirence between the two is that with emacs you have the nightmare of > lack of any GUI while in pharo you have the lack of sophisticated editing. > With respect, this is manifestly untrue. Buffer management is a solved problem in Emacs. In fact, it's been solved and re-solved many times over, to the point where it can suit anyone's tastes. Whether you want: * To simply toggle between the last few buffers * To list, sort, and filter buffers quickly until you find the one you want * To do fuzzy-completed searches on buffers * To manage buffers in tabs and tab groups * To have sidebars listing open buffers * To kill or operate on many buffers at once based on what project they are in or some other criteria * To have a fully window-managed interface that can save, reload, and switch between different window configurations for different contexts at a keypress * To forget about buffers completely, and just navigate to the thing you want to see (and let Emacs worry about what buffers happen to be in memory) (And lest anyone say that buffer management is a different problem from window management, remember that Emacs is an application environment, and that a "buffer" may be a full application window, such as an IRC channel or even a Smalltalk-style browser.) Whether you want any of these features or many others, there are mature and well-tests solutions for all of them. Whereas as many longtime users have confirmed in this thread, Smalltalk environments don't even have the window management to match the Emacs built-in features, let alone the mature extension ecosystem. I made my original seven-minute Pharo video with the intent of getting traditionally IDE-averse Ruby programmers to realize some of the things they are missing. It's way too easy to say "oh, no one else has solved this any better". And as a result, a number of people said "wow, I usually hate IDEs but I need to check this out". But this cuts both ways. > Pharo is doing some good work on this area but realistically , the > community is too small to solve such a huge problem even with pharo ease of > use. > This I agree with completely. My favorite OS for programming is Linux. In linux, window management is a problem that has been solved many times over. There are dozens of window managers (hundreds, if you count inactive projects). There are high-tech compositing window managers that can do MacOS-style Expose zoom-out for quickly locating windows. There are WMs that rigidly control where windows show up, based on a policy you decide. There are all kinds of different aids for quickly listing and navigating between windows. It took thousands of programmers decades of work in many different languages to create this variety. I'd hate to see the smaller Pharo community pour tons of effort into re-inventing these solutions. Which is why I'm suggesting that it may be more helpful to re-frame the problem. General purpose window management is a problem that has been solved many times over. Do you really want to do it yet again? I suspect that with some careful examination of Pharo coding workflows, you could find a way to obviate the need for zillions of windows, and solve a simpler problem instead.

May 19, 2015

Re: [Pharo-users] Silent compilation

by Sergio Fedi

Thanks for the explanation. Now I understand. â

May 19, 2015

Re: [Pharo-users] Alt-tab between windows

by Stephan Eggermont

On 19-05-15 01:08, Avdi Grimm wrote: > Then the web started to take off, throwing UI design back two decades ;), > and UX designers started rethinking > the whole paradigm. They started keeping things in the same window, but > adding back/forward buttons, and navigation histories, and sidebars, and > address bars, and tabs, and other affordances to make it easier to > switch between "things" without necessarily adding more windows. We found that what works well for browsing and reading text not necessarily works for code. I regularly have 80 tabs open in 10 windows of more or less interesting stuff to read. Having a lot of edited buffers open at the same time is a problem, if only because "save all" might run into dependency issues. The current design stimulates working in short cycles, and keeping code well-organized. I'd like not to lose that aspect of the UI. And I also like a navigation history. > These days, most IDEs and editors have followed suit. I can't think of a > single editor in common use among the programmers I know which > encourages multiple windows. Which seems like a mistake, as displays keep growing in size and the IDEs and editors in common use have no way to use the space a 4K display offers. > Whether it's Vim, Emacs, Sublime, IntelliJ, > while you *can* open lots of windows if you really want to, they all > focus on making it easy to manage lots of buffers in a single window > rather than encouraging lots of windows. That actually sounds like a really bad idea when you have a large display. I want to see all relevant code at the same time. Switching is slow. > Personally, I'm a fan of this trend. I'm much happier typing a few > characters to auto-complete the buffer I want to return to in Emacs, > than I am hunting around in an OS window list for it. I would welcome an auto-complete based navigation to one of my open windows. > This is all a long-winded way of saying: just because this is currently > a problem, doesn't mean it's the *right* problem. It would be > interesting to see what a "fewer windows" approach to Smalltalk > development might look like. A simple first step is Hopscotch. https://youtu.be/d6tj6KQtD1s On a small-screen device like an iPad I like the approach taken by Cel: http://cel.inf.usi.ch/ And have you seen Gaucho? http://www.inf.usi.ch/faculty/lanza/Downloads/Oliv2013a.pdf Stephan

May 19, 2015

Re: [Pharo-users] Smalltalkhub password reset

by Esteban Lorenzano

> On 19 May 2015, at 15:11, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > VW/Envy FTW :-P but in Pharo you can choose to use sthub, ss3 or github. ENVY, however, is out of the menuâ¦ soâ¦ out of order! :) Esteban > >> On May 19, 2015, at 07:58, Dimitris Chloupis <kilon.alios(a)gmail.com <mailto:kilon.alios@gmail.com>> wrote: >> >> I stay with Github ;) >> >> On Tue, May 19, 2015 at 10:51 AM mtk <kemper.mt(a)googlemail.com <mailto:kemper.mt@googlemail.com>> wrote: >> Hi Steph, >> >> would it be better to stay with SqueakSource3? >> >> Kind regards >> >> Marcus >> >> >> >> -- >> View this message in context: http://forum.world.st/Smalltalkhub-password-reset-tp4827089p4827230.html <http://forum.world.st/Smalltalkhub-password-reset-tp4827089p4827230.html> >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com <http://nabble.com/>. >> > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD lab - Computer Science Department (DCC) - University of Chile >

May 19, 2015

Re: [Pharo-users] Smalltalkhub password reset

by Johan Fabry

VW/Envy FTW :-P > On May 19, 2015, at 07:58, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I stay with Github ;) > > On Tue, May 19, 2015 at 10:51 AM mtk <kemper.mt(a)googlemail.com <mailto:kemper.mt@googlemail.com>> wrote: > Hi Steph, > > would it be better to stay with SqueakSource3? > > Kind regards > > Marcus > > > > -- > View this message in context: http://forum.world.st/Smalltalkhub-password-reset-tp4827089p4827230.html <http://forum.world.st/Smalltalkhub-password-reset-tp4827089p4827230.html> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

May 19, 2015

Re: [Pharo-users] Silent compilation

by ClÃ©ment Bera

Silent compilation is when the compilation is done without telling any other objects. In the regular compilation of a method, for example, you tell all the class browsers opened that the method was compiled so that if a class browser shows an old version of the same method it is refreshed to show the new version. If you use silent compilation, the class browsers won't be updated. Silent compilation can be used in specific frameworks that wants to edit the methods without the tools to be aware, for example, when you do bytecode manipulation, which does not change the source code of methods, and that the bytecode manipulation is done frequently so that you don't want the overhead of the tool updates. 2015-05-19 12:55 GMT+02:00 Sergio Fedi <sergio.fedi(a)gmail.com>: > Hi guys, > > What is a silent compilation? > > When should it be used? >

May 19, 2015