- Pharo-dev - lists.pharo.org

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

by Marcus Denker

On 25.02.2009, at 21:26, Alexandre Bergel 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 > > Microsoft's OO shell (I forgot the name. And it changed multiple times) is quite cool. It shows how typical Shell things fit into OO nicely. e.g. dir | sort would communicate via a pipe, but and OO one, that is, objects describing files, not text would be exchanged. And, they had a cool framework for making these commands. Your script inherits from the general superclass all the cool stuff, e.g. command line parsing and things like that. Smalltalk would be very powerfull as an OO shell... Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 25, 2009

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

by Alexandre Bergel

> 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 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2009

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

by Alexandre Bergel

Coral combining with Rio looks promising. A prompt will be great although. > There is only "fileout" syntax. (expressions seperated by ! that get > evaluated when > loaded). > > Nobody wants to write scripts that way. And the proof is that nobody > does it. GNUSmalltalk also adopted a proper syntax. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 25, 2009

Re: [Pharo-project] UI dragging improvement

by Marcus Denker

Hi, cool stuff... I will have a look (as a morpic non-expert :-) after moving 900 books from switerland to germany saturday...). One small thing: could you attach .gz or .zip version of the changeset? Some mail-clients are overly clever to show you changeset not as attachments but as inline text. Marcus On 25.02.2009, at 14:36, Henrik Johansen wrote: > Had a look at drawWorld:submorphs:invalidAreasOn: today, the > "Experimental top-down drawing" there does not seem to be working > optimally. > Basically, when there's many windows behind one you're resizing, > this many times leads to ALL of them getting repainted. > Attached is a fix for this, so only the system window areas which > are visible and affected are updated. > It will not speed up cases when resizing a complex morph (like the > Changes Log), but helps when resizing simple ones with many other > windows in the background. > If anyone interested in faster resizing (without fastDragWindow) > would review the code/check if it helps them it'd be nice. > A simple test is to open up a couple system browsers, put them on > top of eachother, and resize a simple window (Like the "Welcome to > Pharo" window) over their bounds. > Then load the changes, and see if you notice a difference. > In a test i did (same windows open/resized, as described above), > time spent in drawWorld:submorphs:invalidAreasOn: was reduced from > 86% to 65.7% after filing in changes. > > If anyone with a better understanding of Morphic know if anything > larger than the clippingBounds is safe to use as default in > Morph>>areasRemainingToFill: , that would probably help as well. > > Cheers, > Henry > 'From Pharo0.1 of 16 May 2008 [Latest update: #10243] on 25 February > 2009 at 2:30:25 pm'! > > !Morph methodsFor: 'drawing' stamp: 'Henrik Sperre Johansen > 2/25/2009 12:06'! > areasRemainingToFill: aRectangle > "May be overridden by any subclasses with opaque regions" > > ^ Array withAll: (aRectangle areasOutside: self clippingBounds)! ! > > > !WorldState methodsFor: 'update cycle' stamp: 'Henrik Sperre > Johansen 2/25/2009 13:52'! > drawWorld: aWorld submorphs: submorphs invalidAreasOn: aCanvas > "Redraw the damaged areas of the given canvas and clear the damage > list. Return a collection of the areas that > were redrawn." > > | rectList c i n mm morphs rects rectToFill remnants > remnantIntersects rect validList | > rectList := damageRecorder invalidRectsFullBounds: aWorld viewBox. > "sort by areas to draw largest portions first" > rectList := rectList asArray sort: [:r1 :r2 | r1 area > r2 area]. > damageRecorder reset. > n := submorphs size. > morphs := OrderedCollection new: n * 2. > rects := OrderedCollection new: n * 2. > validList := OrderedCollection new: n * 2. > rectList do: > [:dirtyRect | > dirtyRect allAreasOutsideList: validList > do: > [:r | > "Experimental top-down drawing -- > Traverses top to bottom, stopping if the entire area is filled. > If only a single rectangle remains, then continue with the > reduced rectangle." > > rectToFill := r. > remnants := OrderedCollection with: r. > i := 1. > [remnants isEmpty or: [i > n]] whileFalse: > [mm := submorphs at: i. > ((remnantIntersects := remnants select: [:each | (mm > fullBounds intersects: each)]) notEmpty and: [mm visible]) > ifTrue: > [morphs addLast: mm. > > rects addLast: (Rectangle merging: (remnantIntersects > collect: [:each | mm fullBounds intersect: each])). > remnants removeAll: remnantIntersects. > remnantIntersects do: [:eachIntersect | remnants addAll: > (mm areasRemainingToFill: eachIntersect)]. > remnants size = 1 ifTrue: [rectToFill := remnants first]. > remnants isEmpty ifTrue: [rectToFill := nil]]. > i := i + 1]. > "Now paint from bottom to top, but using the reduced rectangles." > rectToFill > ifNotNil: [aWorld drawOn: (c := aCanvas copyClipRect: > rectToFill)]. > [morphs isEmpty] whileFalse: > [(rect := rects removeLast) == rectToFill > ifFalse: [c := aCanvas copyClipRect: (rectToFill := rect)]. > c fullDrawMorph: morphs removeLast]. > morphs reset. > rects reset. > validList add: r]]. > ^validList! ! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 25, 2009

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

by Marcus Denker

On 25.02.2009, at 19:59, Keith Hodges wrote: > Oscar Nierstrasz wrote: >> Hi Folks, >> >> I spent some time yesterday together with Stef to take a closer look >> at the Pharo scripting project. >> >> We have repackaged and renamed the project as "Coral". It is >> available >> on SqueakSource at: >> >> http://www.squeaksource.com/Coral >> >> > I really didnt understand what Coral Saphire was all about, in > InstallerLauncher you could ask squeak to execute a script and > output to > stdout. When I looked at Saphir I could see all sorst of parsers etc. > Whats it all for? Having a grammar? Smalltalk has no language element to define classes and methods. There is only "fileout" syntax. (expressions seperated by ! that get evaluated when loaded). Nobody wants to write scripts that way. And the proof is that nobody does it. Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 25, 2009