- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Thierry Goubier

2014-12-16 13:23 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > > Just a clarification: > Playground is saving after each change, not only after a Go. To some > extent, it is some sort of duplication with the DoIt actions, but the > Playground saves the entire code, not just the executed one. > It doesn't make the distinction between a go on a selection or on the full code? I'd wonder about the correctness of the save, then. > It saves the contents in a play-cache folder by default, but you can > configure it to be in a central folder shared by multiple images. > Ok. If we have a better log format than the changes, could all this (changes and those scripts) be unified/integrated? > The idea is exactly to try to find a mechanism that is transparent and > let's you play without worrying about save/load. We still have to refine > the mechanism a bit though. > > Please also note that GTSpotter searches through past Playground pages > which means that discovery is now easier than before. > I expected that feature :) Thanks, Thierry > > Cheers, > Doru > > On Tue, Dec 16, 2014 at 1:17 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: >> >> >> >> 2014-12-16 13:00 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> >>> > On 16 Dec 2014, at 12:54, Thierry Goubier <thierry.goubier(a)gmail.com> >>> wrote: >>> > >>> > >>> > >>> > 2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>> > >>> > >>> > === >>> > >>> > We need something very low friction, like automatic saving/remembering. >>> > >>> > >>> > Why not searching among the doit(s) stored in the changes? >>> > >>> > Thierry >>> >>> Yes, that combined with Workspace's 'Previous contents' and the new >>> automatic saving of Playground after Go. >>> >> >> Isn't the Playground saving after go a duplication of the Changes >> recording of the associated doit? >> >> >>> >>> It just needs to become a really safe and dependable - so that you just >>> know you can safely close a workspace/playground with an important script >>> and always can get it back. >>> >> >> I rebuilt my images regularly, so it could be nice to have that linked to >> a repository. And yes, simple and dependable. Like in: there is no need to >> explain how it works... Or that the how is obvious. >> >> Saving states of the workspaces / playground in a kind of log and doits >> as actions on those? Visible in searches? Stored in the package cache? >> Robust to multiple images use on it? >> >> Thierry >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 16, 2014

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Tudor Girba

Just a clarification: Playground is saving after each change, not only after a Go. To some extent, it is some sort of duplication with the DoIt actions, but the Playground saves the entire code, not just the executed one. It saves the contents in a play-cache folder by default, but you can configure it to be in a central folder shared by multiple images. The idea is exactly to try to find a mechanism that is transparent and let's you play without worrying about save/load. We still have to refine the mechanism a bit though. Please also note that GTSpotter searches through past Playground pages which means that discovery is now easier than before. Cheers, Doru On Tue, Dec 16, 2014 at 1:17 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-12-16 13:00 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> >> > On 16 Dec 2014, at 12:54, Thierry Goubier <thierry.goubier(a)gmail.com> >> wrote: >> > >> > >> > >> > 2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> > >> > >> > === >> > >> > We need something very low friction, like automatic saving/remembering. >> > >> > >> > Why not searching among the doit(s) stored in the changes? >> > >> > Thierry >> >> Yes, that combined with Workspace's 'Previous contents' and the new >> automatic saving of Playground after Go. >> > > Isn't the Playground saving after go a duplication of the Changes > recording of the associated doit? > > >> >> It just needs to become a really safe and dependable - so that you just >> know you can safely close a workspace/playground with an important script >> and always can get it back. >> > > I rebuilt my images regularly, so it could be nice to have that linked to > a repository. And yes, simple and dependable. Like in: there is no need to > explain how it works... Or that the how is obvious. > > Saving states of the workspaces / playground in a kind of log and doits as > actions on those? Visible in searches? Stored in the package cache? Robust > to multiple images use on it? > > Thierry > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 16, 2014

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Thierry Goubier

2014-12-16 13:00 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > On 16 Dec 2014, at 12:54, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > > > > > 2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > > > === > > > > We need something very low friction, like automatic saving/remembering. > > > > > > Why not searching among the doit(s) stored in the changes? > > > > Thierry > > Yes, that combined with Workspace's 'Previous contents' and the new > automatic saving of Playground after Go. > Isn't the Playground saving after go a duplication of the Changes recording of the associated doit? > > It just needs to become a really safe and dependable - so that you just > know you can safely close a workspace/playground with an important script > and always can get it back. > I rebuilt my images regularly, so it could be nice to have that linked to a repository. And yes, simple and dependable. Like in: there is no need to explain how it works... Or that the how is obvious. Saving states of the workspaces / playground in a kind of log and doits as actions on those? Visible in searches? Stored in the package cache? Robust to multiple images use on it? Thierry

Dec. 16, 2014

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Sven Van Caekenberghe

> On 16 Dec 2014, at 12:54, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > === > > We need something very low friction, like automatic saving/remembering. > > > Why not searching among the doit(s) stored in the changes? > > Thierry Yes, that combined with Workspace's 'Previous contents' and the new automatic saving of Playground after Go. It just needs to become a really safe and dependable - so that you just know you can safely close a workspace/playground with an important script and always can get it back.

Dec. 16, 2014

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Thierry Goubier

2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > === > > We need something very low friction, like automatic saving/remembering. > > Why not searching among the doit(s) stored in the changes? Thierry

Dec. 16, 2014

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Thierry Goubier

2014-12-16 12:44 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > On 12 Dec 2014, at 12:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > As input for designing new features that better support scripting in > Pharo, we would benefit from a bit more input around the role scripts play > in your development life. > > > > To this end, I would like to invite you to share your scripting > experience. Here are some questions to start from, but feel free to diverge: > > Every image that I am working in for some time contains multiple open > workspaces that I need and depend on, that I dare not close because they > might contain important stuff. > > > - What kind of actions do you put in scripts? > > Starting points for coding, exploring, starting/stopping services, loading > code, generally useful expressions, snippets of code that will evolve in > something else later on. > > > - Do you rely on script files stored on the disk at all? > > Not really, but I tried (both using save/load and ScriptManager) - I think > the extra step is too much, a permanent workspace in an image is so much > easier. > > > - Where do you store your scripts (in one folder, in many folders)? > > Just next to the image, mostly. But I tried structured saving with > ScriptManager. > > > - Do you version your scripts? > > No > > > - Do you store them in separate files with dedicated names, or tend to > put multiple snippets in one larger file? > > Both > > > - Do you rely on the names of the scripts? > > If there are names, yes. > > > - Why do you use a script file and not a class? > > Some tools end up as class methods, if not real code. > > But changing a class (code) is more serious than > playing/experimenting/exploring code in a workspace. > > === > > One of the things that I do is mail snippets around internally, so that I > and others have them in their mailbox for later reference. > > === > > We need something very low friction, like automatic saving/remembering. > > > Cheers, > > Doru > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > >

Dec. 16, 2014

Re: [Pharo-users] [Pharo-dev] how do you use scripts?

by Sven Van Caekenberghe

> On 12 Dec 2014, at 12:14, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > As input for designing new features that better support scripting in Pharo, we would benefit from a bit more input around the role scripts play in your development life. > > To this end, I would like to invite you to share your scripting experience. Here are some questions to start from, but feel free to diverge: Every image that I am working in for some time contains multiple open workspaces that I need and depend on, that I dare not close because they might contain important stuff. > - What kind of actions do you put in scripts? Starting points for coding, exploring, starting/stopping services, loading code, generally useful expressions, snippets of code that will evolve in something else later on. > - Do you rely on script files stored on the disk at all? Not really, but I tried (both using save/load and ScriptManager) - I think the extra step is too much, a permanent workspace in an image is so much easier. > - Where do you store your scripts (in one folder, in many folders)? Just next to the image, mostly. But I tried structured saving with ScriptManager. > - Do you version your scripts? No > - Do you store them in separate files with dedicated names, or tend to put multiple snippets in one larger file? Both > - Do you rely on the names of the scripts? If there are names, yes. > - Why do you use a script file and not a class? Some tools end up as class methods, if not real code. But changing a class (code) is more serious than playing/experimenting/exploring code in a workspace. === One of the things that I do is mail snippets around internally, so that I and others have them in their mailbox for later reference. === We need something very low friction, like automatic saving/remembering. > Cheers, > Doru > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Dec. 16, 2014

Re: [Pharo-users] Problem with Spec icon

by Tommaso Dal Sasso

On 15/12/14 22:02, stepharo wrote: >> Sorry, I wrote it badly. Of course it is an issue of Morphic, thanks >> for your clarification. >> So, is it a bug or it just works that way and it is supposed to do so >> by architectural design? > > this is a bug. > And we should open a bug entry about it. I opened a bug report at https://pharo.fogbugz.com/f/cases/14629/Morphic-click-event-and-modal-windo… Tommaso

Dec. 16, 2014

Re: [Pharo-users] Problem with Spec icon

by stepharo

> Sorry, I wrote it badly. Of course it is an issue of Morphic, thanks > for your clarification. > So, is it a bug or it just works that way and it is supposed to do so > by architectural design? this is a bug. And we should open a bug entry about it. > > The interesting thing is that with a button it works. > > Tommaso > >> >> >> >> I'll try to investigate more. >> Thanks for the feedback, >> >> Tommaso >> >> >> Stef. >> Le 14/12/14 20:26, Tommaso Dal Sasso a Ã©crit : >> >> I have a weird behavior building an interface with Spec. >> >> I have a window built with Spec, and I want to add a >> button that shows a dialog with some text. >> To display the dialog I use the following line: >> >> UIManager default longMessage: 'a text message' title: >> 'some title'. >> >> And I hooked this code to a widget through the #action: >> method. >> The problem is: If I use a ButtonModel, the code behaves >> correctly showing the dialog. >> If I use an instance of the class ImageModel to display an >> icon, the dialog is displayed but the interface "hangs", >> in the sense that the "ok" button won't close the dialog >> and every click would spawn a new dialog. >> >> I would like to use an icon because it integrates better >> with the interface. >> Do you know if it is a bug or if I am doing something wrong? >> >> Thanks, >> Tommaso >> >> >> P.s.: Steps to reproduce >> >> If you need a working example you can inspect the code on >> the bleeding edge version of ShoreLine Reporter by >> following these instructions: >> 1. download a recent Pharo 4 image; >> 2. open a workspace and run: >> ConfigurationOfShoreLineReporter loadBleedingEdge >> 3. trigger an exception (for example by running 3/0 in a >> workspace). >> 4. click 'Report' >> 5. click the '?' button on the right side of the window. >> >> >> >> >> >> >> > > >

Dec. 15, 2014

How to open the Settings style dialog?

by Rafael Luque

Hi all, I was reading about the Settings framework (Deep Into Pharo, chapter 5) and I don't find the way to popup the style dialog shown in Figure 5.11 in page 71 ( https://books.google.es/books?id=Qki8BQAAQBAJ&lpg=PA68&dq=pharo%20the%20sty… ). I'm using a Pharo 4 image. Thank you

Dec. 15, 2014