I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
Have a look at Script Manager. http://catalog.pharo.org/catalog/project/ScriptManager  ----------------- Benoît St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein) From: Andy Burnett <andy.burnett@knowinnovation.com> To: "pharo-users@lists.pharo.org" <pharo-users@lists.pharo.org> Sent: Saturday, November 25, 2017 12:35 PM Subject: [Pharo-users] How do you store and manage small programs? I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue. | | Virus-free. www.avg.com |
I use github and Package Browser, Package Browser is for intalling packages from inside image. For small code snippets I use Gist which supports Smalltalk syntax. For example https://gist.github.com/kilon/ef8a99d94637eadfac339107e1ace233 On Sat, Nov 25, 2017 at 7:35 PM Andy Burnett < andy.burnett@knowinnovation.com> wrote:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
Hi Andy, On 25/11/17 12:34, Andy Burnett wrote:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
You can try Grafoscopio[1]. It allows you to store, give context, document and organize your scripts as interactive notebooks, intertwining text + code and export them to PDF and HTML (via Pandoc). [1] http://mutabit.com/grafoscopio/index.en.html Cheers, Offray
re Script Manager "We would recommend users to switch to QuickAccess which is a better script manager than this tool." QuickAccess here's a video and everything https://pharoweekly.wordpress.com/2015/11/06/quickaccess/ For QA I also have a startup script that installs it on first startup, and then reloads its state on every startup (so the scripts are shared between images) https://github.com/peteruhnak/pharo-scripts/blob/master/config/6.0/quickAcce... for "maybe-sometimes-useful-scripts" or when I just want to write a code memo for myself, I tend to use gist ( https://gist.github.com/peteruhnak ) Peter On Sat, Nov 25, 2017 at 6:51 PM, Offray Vladimir Luna Cárdenas < offray.luna@mutabit.com> wrote:
Hi Andy,
On 25/11/17 12:34, Andy Burnett wrote:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
You can try Grafoscopio[1]. It allows you to store, give context, document and organize your scripts as interactive notebooks, intertwining text + code and export them to PDF and HTML (via Pandoc).
[1] http://mutabit.com/grafoscopio/index.en.html
Cheers,
Offray
On 26 November 2017 at 01:34, Andy Burnett <andy.burnett@knowinnovation.com> wrote:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
One way is to create a package and add your scripts on the class-side of a class MyDataWrangling. Then save the package with Monticello. cheers -ben
Hi Andy As you saw there are plenty of solutions. Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more. So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized. Stef On Sat, Nov 25, 2017 at 6:34 PM, Andy Burnett <andy.burnett@knowinnovation.com> wrote:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
+1 And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation. Cheers, Alistair
QuickAccess is also a great option. *https://pharoweekly.wordpress.com/2015/11/06/quickaccess/ <https://pharoweekly.wordpress.com/2015/11/06/quickaccess/>* On Mon, Nov 27, 2017 at 11:16 AM, Alistair Grant <akgrant0710@gmail.com> wrote:
On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
+1
And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation.
Cheers, Alistair
Wow - I never noticed that extension - thatâs amazing.
On 27 Nov 2017, at 10:56, phil@highoctane.be wrote:
QuickAccess is also a great option.
https://pharoweekly.wordpress.com/2015/11/06/quickaccess/ <https://pharoweekly.wordpress.com/2015/11/06/quickaccess/>
On Mon, Nov 27, 2017 at 11:16 AM, Alistair Grant <akgrant0710@gmail.com <mailto:akgrant0710@gmail.com>> wrote: On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self@gmail.com <mailto:stepharo.self@gmail.com>> wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
+1
And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation.
Cheers, Alistair
It is useful for presentations. https://www.youtube.com/watch?v=JhmmoEtAq20&t=269s Phil On Mon, Nov 27, 2017 at 1:06 PM, Tim Mackinnon <tim@testit.works> wrote:
Wow - I never noticed that extension - thatâs amazing.
On 27 Nov 2017, at 10:56, phil@highoctane.be wrote:
QuickAccess is also a great option.
*https://pharoweekly.wordpress.com/2015/11/06/quickaccess/ <https://pharoweekly.wordpress.com/2015/11/06/quickaccess/>*
On Mon, Nov 27, 2017 at 11:16 AM, Alistair Grant <akgrant0710@gmail.com> wrote:
On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
+1
And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation.
Cheers, Alistair
Super cool tshirt! Stef On Mon, Nov 27, 2017 at 1:18 PM, phil@highoctane.be <phil@highoctane.be> wrote:
It is useful for presentations.
https://www.youtube.com/watch?v=JhmmoEtAq20&t=269s
Phil
On Mon, Nov 27, 2017 at 1:06 PM, Tim Mackinnon <tim@testit.works> wrote:
Wow - I never noticed that extension - thatâs amazing.
On 27 Nov 2017, at 10:56, phil@highoctane.be wrote:
QuickAccess is also a great option.
https://pharoweekly.wordpress.com/2015/11/06/quickaccess/
On Mon, Nov 27, 2017 at 11:16 AM, Alistair Grant <akgrant0710@gmail.com> wrote:
On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
+1
And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation.
Cheers, Alistair
Stephane Ducasse-3 wrote
Super cool tshirt!
Ha ha ha +1!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
On 27 November 2017 at 11:16, Alistair Grant <akgrant0710@gmail.com> wrote:
On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
+1
And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation.
Often better than a printOn: is to create a #gtInspectIn: method, allowing you to display tables, graphs, etc. as appropriate in the inspector. Actually, this has worked so well that I haven't written a "real UI" for anything I use in my personal environment, which includes downloading media, all my note keeping, tracking finances, etc. Cheers, Alistair
Yes. Plenty of solutions, from just open your Playground in a scripts folder, to QuickAccess, to objects, to embedding scripts into more complete data narratives. They serve different purposes, so explore them and see which ones serves better your taste and user case. Cheers, Offray On 26/11/17 07:07, Stephane Ducasse wrote:
Hi Andy
As you saw there are plenty of solutions.
Now what I learned is that it is often better in the long to have a little object because suddenly it opens your mind and you realise that you can teach him something more.
So I often find myself realising that I created some class methods and that it was stupid better have a real little object because it can do more and in particular for open new path
So now I do not use scripts but plain little classes with nice little printOn: methods and arguments to get customized.
Stef
On Sat, Nov 25, 2017 at 6:34 PM, Andy Burnett <andy.burnett@knowinnovation.com> wrote:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
Andy, I use the filesystem for it. Letâs say you have a directory called âscriptsâ. If you inspect âscriptsâ asFileReference you get kind of a browser of the files in there. If the have the file extension .st syntax highlighting is enabled if you look at it. You can create new scripts there,too. I like that the most because the scripts are not in the image anymore and the probability to loose them is lower. I have a scripts folder in my home directory (global) and one in the project folder (project specific). And inspectors to bith location are opened by the script that prepares a new image. Norbert
Am 25.11.2017 um 18:34 schrieb Andy Burnett <andy.burnett@knowinnovation.com>:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
On 26 November 2017 at 20:36, Norbert Hartl <norbert@hartl.name> wrote:
Andy,
I use the filesystem for it. Letâs say you have a directory called âscriptsâ. If you inspect
âscriptsâ asFileReference
nice trick cheers -ben
you get kind of a browser of the files in there. If the have the file extension .st syntax highlighting is enabled if you look at it. You can create new scripts there,too. I like that the most because the scripts are not in the image anymore and the probability to loose them is lower.
I have a scripts folder in my home directory (global) and one in the project folder (project specific). And inspectors to bith location are opened by the script that prepares a new image.
Norbert
Am 25.11.2017 um 18:34 schrieb Andy Burnett < andy.burnett@knowinnovation.com>:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
Hi Norbert, I tried this in a 6.1 image but I only get a normal inspector. What do I miss? Bernhard
Am 26.11.2017 um 13:36 schrieb Norbert Hartl <norbert@hartl.name>:
Andy,
I use the filesystem for it. Letâs say you have a directory called âscriptsâ. If you inspect
âscriptsâ asFileReference
you get kind of a browser of the files in there. If the have the file extension .st syntax highlighting is enabled if you look at it. You can create new scripts there,too. I like that the most because the scripts are not in the image anymore and the probability to loose them is lower.
I have a scripts folder in my home directory (global) and one in the project folder (project specific). And inspectors to bith location are opened by the script that prepares a new image.
Norbert
Am 25.11.2017 um 18:34 schrieb Andy Burnett <andy.burnett@knowinnovation.com>:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
That most probably means there are no files in the directory. If you create one then you will see. Norbert
Am 02.12.2017 um 15:02 schrieb Bernhard Pieber <bernhard@pieber.com>:
Hi Norbert,
I tried this in a 6.1 image but I only get a normal inspector. What do I miss?
Bernhard
Am 26.11.2017 um 13:36 schrieb Norbert Hartl <norbert@hartl.name>:
Andy,
I use the filesystem for it. Letâs say you have a directory called âscriptsâ. If you inspect
âscriptsâ asFileReference
you get kind of a browser of the files in there. If the have the file extension .st syntax highlighting is enabled if you look at it. You can create new scripts there,too. I like that the most because the scripts are not in the image anymore and the probability to loose them is lower.
I have a scripts folder in my home directory (global) and one in the project folder (project specific). And inspectors to bith location are opened by the script that prepares a new image.
Norbert
Am 25.11.2017 um 18:34 schrieb Andy Burnett <andy.burnett@knowinnovation.com>:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
That was the problem. Thanks, Norbert! Bernhard
Am 02.12.2017 um 17:01 schrieb Norbert Hartl <norbert@hartl.name>:
That most probably means there are no files in the directory. If you create one then you will see.
Norbert
Am 02.12.2017 um 15:02 schrieb Bernhard Pieber <bernhard@pieber.com>:
Hi Norbert,
I tried this in a 6.1 image but I only get a normal inspector. What do I miss?
Bernhard
Am 26.11.2017 um 13:36 schrieb Norbert Hartl <norbert@hartl.name>:
Andy,
I use the filesystem for it. Letâs say you have a directory called âscriptsâ. If you inspect
âscriptsâ asFileReference
you get kind of a browser of the files in there. If the have the file extension .st syntax highlighting is enabled if you look at it. You can create new scripts there,too. I like that the most because the scripts are not in the image anymore and the probability to loose them is lower.
I have a scripts folder in my home directory (global) and one in the project folder (project specific). And inspectors to bith location are opened by the script that prepares a new image.
Norbert
Am 25.11.2017 um 18:34 schrieb Andy Burnett <andy.burnett@knowinnovation.com>:
I have just created a couple of small playground scripts that do some useful data wrangling. The chances are that I will reuse them from time to time, but with tweaks. Does version 6 Have some way to store them? I think I am after a sort of scripts catalogue.
participants (13)
-
Alistair Grant -
Andy Burnett -
Ben Coman -
Benoit St-Jean -
Bernhard Pieber -
Dimitris Chloupis -
Norbert Hartl -
Offray Vladimir Luna Cárdenas -
Peter Uhnák -
phil＠highoctane.be -
Sean P. DeNigris -
Stephane Ducasse -
Tim Mackinnon