- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Announcements for Pharo?

by Ramon Leon

> + 1 > > I also use the Lukas' version. > That is the version that we should use and standarize to. > > Miguel CobÃ¡ +1 for me as well, I also use Lukas' implementation. Ramon Leon http://onsmalltalk.com

Feb. 26, 2009

Re: [Pharo-project] Announcements for Pharo?

by Rob Rothwell

+1 Even as a beginner, it made sense to me! Rob On Wed, Feb 25, 2009 at 8:40 PM, Miguel Enrique CobÃ¡ MartÃnez < m.coba.m(a)gmail.com> wrote: > Tudor Girba wrote: > > That would be cool, actually. I have used the implementation of Lukas > > and it works just fine. > > > > + 1 > > I also use the Lukas' version. > That is the version that we should use and standarize to. > > Miguel CobÃ¡ > > > Lukas pointed out that the VW Announcements code is under Cincom > > copyright. The nice thing about his implementation is that he did not > > look at the code. He only implemented the idea as he read it from the > > blog :). > > > > Cheers, > > Doru > > > > > > On 26 Feb 2009, at 01:28, Michael Rueger wrote: > > > >> Hi all, > >> > >> should we add Announcements as part of the core image? > >> And if so, which of the existing implementations? > >> > >> Michael > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > www.tudorgirba.com > > > > "Presenting is storytelling." > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 26, 2009

Re: [Pharo-project] Announcements for Pharo?

by Miguel Enrique CobÃ¡ MartÃnez

Tudor Girba wrote: > That would be cool, actually. I have used the implementation of Lukas > and it works just fine. > + 1 I also use the Lukas' version. That is the version that we should use and standarize to. Miguel CobÃ¡ > Lukas pointed out that the VW Announcements code is under Cincom > copyright. The nice thing about his implementation is that he did not > look at the code. He only implemented the idea as he read it from the > blog :). > > Cheers, > Doru > > > On 26 Feb 2009, at 01:28, Michael Rueger wrote: > >> Hi all, >> >> should we add Announcements as part of the core image? >> And if so, which of the existing implementations? >> >> Michael >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Presenting is storytelling." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 26, 2009

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by David T. Lewis

On Wed, Feb 25, 2009 at 09:48:08PM +0000, Nicolas Cellier wrote: > Marcus Denker <denker@...> writes: > > > On 25.02.2009, at 22:27, Matthew Fulmer wrote: > > > > >> > > >> Each command will then be a message sent to the object referenced by > > >> the variable 'shell'. > > >> > > >> entering 'ls' will then invoke 'shell.ls'... > > > > I would say that a command like "ls" is not a method. It's an object > > (instance of a sublass of "Script" or "Command"). > > > > You want, for example, inherit things like command line parsing, > > standard options > > (e.g. --help) and things liket that. A command like ls is far too > > complex to be > > just one method. > > I would say ls is a message, and Shell ls answer with a LSCommand which is > kindOf: Command. > A Command use lazy evaluation: it does not evaluate until a end of line or pipe > message triggers evaluation (i mean send the message #value). > > Before being evaluated, Command behaviour can be modified by sending all sort of > message, like -l --help etc... > Of course, apart options which are messages sent to the command (eventually with > arguments), a list of arguments can be passed to the Command itself (Command > valueWithArguments: aList). > > Just have to invent the syntax now... You may be interested in ExternalCommandShell which is part of the CommandShell package (SqueakMap, SqueakSource, etc). This lets you use Squeak as a command line shell replacing /bin/sh, and uses pipes to connect Smalltalk expressions, command objects, and external OS programs. http://wiki.squeak.org/squeak/6023 http://wiki.squeak.org/squeak/2153 http://wiki.squeak.org/squeak/1914 The syntax is a mashup of Smalltalk and unix shell conventions. The pipes are OS pipes where necessary to interact with external programs, or an object that minics OS pipe behavior if the "commands" being connected are Smalltalk expressions or command objects. For example, if you enter "help | cat" at the command prompt, you will get a Smalltalk command object that evaluates "help" and writes its output to a Unix pipe connected to an OS process running the /bin/cat command, which reads the output of the "help" command, and copies it to the shell output: sqsh> help | cat cd [path] - change default directory help - help on sqsh commands history - display command history list pwd - print current working directory sls [filepatterns] - list current directory contents snapshot - save the Squeak image exit - exit shell and quit Squeak without saving image type [names...] - indicate how each name would be interpreted if used as a command simple Smalltalk expression! evaluates a simple expression as a doIt <ctl-C> to interrupt a running program <ctl-D> to end input to a running program sqsh> Dave

Feb. 26, 2009

Re: [Pharo-project] Announcements for Pharo?

by Tudor Girba

That would be cool, actually. I have used the implementation of Lukas and it works just fine. Lukas pointed out that the VW Announcements code is under Cincom copyright. The nice thing about his implementation is that he did not look at the code. He only implemented the idea as he read it from the blog :). Cheers, Doru On 26 Feb 2009, at 01:28, Michael Rueger wrote: > Hi all, > > should we add Announcements as part of the core image? > And if so, which of the existing implementations? > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Presenting is storytelling."

Feb. 26, 2009

[Pharo-project] Announcements for Pharo?

by Michael Rueger

Hi all, should we add Announcements as part of the core image? And if so, which of the existing implementations? Michael

Feb. 26, 2009

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by Alexandre Bergel

> Please, please, keep UI feel homogeneous ! > Why not HOME, END, CTRL + -> like any other text editor in the world ? > Even squeak is following that convention in TextMorphs ! > Also let SHIFT+CONTROL+-> select over words and typed characters > overwrite > selection. > You don't have to imitate a poor man's shell! You could have several ways to get at the first character. Actually, not only "could", but "should". Why not "home", "end" ? because there is no such keys on a mac. > Let history cycle when at beginning/end of list (with some form of > advertising). > And let restrict history crawling among lines matching the first > letters if you > typed some (like Matlab does). As most shell do as well. Would be great to have, indeed. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2009

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by Alexandre Bergel

> I would say that a command like "ls" is not a method. It's an object > (instance of a sublass of "Script" or "Command"). > > You want, for example, inherit things like command line parsing, > standard options > (e.g. --help) and things liket that. A command like ls is far too > complex to be > just one method. could also be a trait. But I understand what you're saying. Entering 'ls' will actually be translated into a 'ls executeInContext: currentContext' or something. currentContext will then be aware of the current path. Looks like to be an exciting project! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2009

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by Nicolas Cellier

Marcus Denker <denker@...> writes: > > > On 25.02.2009, at 22:27, Matthew Fulmer wrote: > > >> > >> Each command will then be a message sent to the object referenced by > >> the variable 'shell'. > >> > >> entering 'ls' will then invoke 'shell.ls'... > > I would say that a command like "ls" is not a method. It's an object > (instance of a sublass of "Script" or "Command"). > > You want, for example, inherit things like command line parsing, > standard options > (e.g. --help) and things liket that. A command like ls is far too > complex to be > just one method. > > Marcus > > -- > Marcus Denker -- denker@... > http://www.marcusdenker.de > I would say ls is a message, and Shell ls answer with a LSCommand which is kindOf: Command. A Command use lazy evaluation: it does not evaluate until a end of line or pipe message triggers evaluation (i mean send the message #value). Before being evaluated, Command behaviour can be modified by sending all sort of message, like -l --help etc... Of course, apart options which are messages sent to the command (eventually with arguments), a list of arguments can be passed to the Command itself (Command valueWithArguments: aList). Just have to invent the syntax now... Nicolas

Feb. 25, 2009

Re: [Pharo-project] Pharo scripting -- reborn as "Coral"

by Nicolas Cellier

Michael van der Gulik <mikevdg@...> writes: > > > On Thu, Feb 26, 2009 at 9:26 AM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > please > > try it out and let me know what you would expect from a real Smalltalk > > scripting environment. > Something that would really push me in using Coral is an intelligent > prompt. A list of the things the prompt should do: > - crawling into the history of typed commands using up and down key > arrow > - tab completion (classes and method name) > - colored output > - Ctl-D to quit > - Keybinds: > * Ctlr-A beginning of the line > * Ctrl-E end of the line > * Alt- -> / Alt- <- to jump words > > Please, please, keep UI feel homogeneous ! Why not HOME, END, CTRL + -> like any other text editor in the world ? Even squeak is following that convention in TextMorphs ! Also let SHIFT+CONTROL+-> select over words and typed characters overwrite selection. You don't have to imitate a poor man's shell! Let history cycle when at beginning/end of list (with some form of advertising). And let restrict history crawling among lines matching the first letters if you typed some (like Matlab does). Nicolas

Feb. 25, 2009