- Pharo-dev - lists.pharo.org

Re: [Pharo-project] we cannot add attachment anymore on the bug tracker

by Tudor Girba

Yes. Lukas pointed us to the docs. You can find the answer here: http://code.google.com/p/support/wiki/FAQ#What_other_limits_exist? Cheers, Doru On 26 Feb 2011, at 22:05, StÃ©phane Ducasse wrote: > tx lukas > Do you know if there is a normal process to request such increase? > > Stef > > > On Feb 25, 2011, at 11:53 PM, Lukas Renggli wrote: > >> Thanks for letting me know. Getting the quota increased is pretty easy >> (kudos Nathaniel), if you ask the right people ;-) >> >> Lukas >> >> On 25 February 2011 22:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> On Feb 25, 2011, at 8:33 PM, Tudor Girba wrote: >>> >>>> Isn't it because you went passed the quota? The bad thing about attachments in Google Code is that you have only 50MB for it. >>>> >>>> You can find the current status in Administer/Advanced. >>>> >>> Maybe this is the hint to move to something else... what I really want (need) is a bugtracker that allows better sorting of bug reports. >>> Tags are great. But tags do not replace sub-projects. I want a bug tracker just for Cog. And one just for "the nuts", or one for morphic... >>> >>> This way we could actually get structure in the 560 reports... >>> >>> Redmine (http://www.redmine.org/) supports sub-projects. Or maybe https://www.chiliproject.org/ (a fork of redmine). >>> >>> >>> Marcus >>> >>> >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

Feb. 26, 2011

Re: [Pharo-project] Fwd: [ANN] pharo focused sprint - bern, feb 26

by Tudor Girba

Hi, The sprint was quite exciting. Here is the twitter report: http://twitter.com/#!/search/pharosprint Here is a longer report: - Camillo looked into Keymapping. He spent several hours going through the code with the debugger. In the process he extracted more actions into keybindings (in the Keymapping-Settings). It's a commendable effort because it is quite a challenge to debug the system when playing with the keybindings :). The conclusion seems to be that Keymapping provides good functionality already, but that it needs some refactoring. In particular: --- There should be less decisions in the TextMorph. These should be delegated to the Dispatcher --- Some classes and methods would do with better names. For example, keyMapper / hasKeymap / Dispatcher. They should be all Keymapper --- There are a couple of symbols around (e.g., #complete) that are not quite clear and that should be modeled explicitly. --- Camillo, did I miss anything? - Lukas went over the WeakAnnouncements implementation to get the WeakMessageSend working. The code is in PharoTaskForces - Lukas worked on getting OB work with the changes in TextMorph from Pharo 1.2. - Adrian, Jorge and Toon worked on implementing a Debugger on top of Glamour. They got a first version working that is able to do basic actions: step, restart, step into. The challenge was to get to understand the model, and to figure out that <primitive: 19> is used for marking that a method should not be debugged. In any case, working with Glamour seemed to work quite smoothly. The code is available in the Glamorous Toolkit. Adrian, did I get it right? :) - Mircea built a new widget for searching multiple categories of items in the same time, similar to spotlight where you enter one string and you get multiple hits from multiple categories. The implementation was spawned from the OBCompletionDialog / OBCompletionRequest and currently it simply provides multiple lists one below the other. The idea is to use this kind of widget to search simultaneously for classes / methods / packages. The code is available in Glamour (Glamour-Morphic-Renderer). The widget can definitely be improved visually, but Mircea already did a nice job. - I showed the current prototypes available in the Glamorous Toolkit (built with Glamour). It looks like we got a consensus that we should focus on rethinking the IDEs, and that Glamour can be a promising infrastructure. For this to work, we distinguished between the work needed at the widget level (like the work of Mircea and Camillo), and the work needed at the level of playing with new metaphors for browsing. The Glamorous Toolkit already provides a number of examples for: ObjectFinder, Chaser, Playground (ex-Workspace), MessageTallyBrowser, ProfStef, and some Coders. If you want to play with the early versions of these tools, you can get them here (just keep in mind that they are intended as exercises at the moment): Gofer new squeaksource: 'glamoroust'; package: 'ConfigurationOfGlamoroust'; load. (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. Cheers, Doru On 26 Feb 2011, at 19:06, StÃ©phane Ducasse wrote: > so doru I just arrived after a trip from the nearly "westernest" town in france to nearly the "northest" one :) > What are the results of the sprint. > > > On Feb 26, 2011, at 9:42 AM, Tudor Girba wrote: > >> We are starting the sprint: >> - Twitter tag: #pharosprint >> - If someone wants to join remotely, let us know how to reach you. Gary, Alain? :) >> >> Cheers, >> Doru >> >> >> On 25 Feb 2011, at 20:39, Tudor Girba wrote: >> >>> Phenomenal :) >>> >>> Doru >>> >>> >>> On 24 Feb 2011, at 13:03, Jorge Ressia wrote: >>> >>>> I will be there too. >>>> >>>> Cheers, >>>> >>>> On Wed, Feb 23, 2011 at 10:44 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>>>> Excellent. >>>>> >>>>> Doru >>>>> >>>>> >>>>> On 23 Feb 2011, at 22:29, Lukas Renggli wrote: >>>>> >>>>>> I am coming too. >>>>>> >>>>>> Lukas >>>>>> >>>>>> On 23 February 2011 05:27, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>>>>>> Great. >>>>>>> >>>>>>> Doru >>>>>>> >>>>>>> >>>>>>> On 22 Feb 2011, at 19:47, Camillo Bruni wrote: >>>>>>> >>>>>>>> I'll be there. >>>>>>>> >>>>>>>> From what I have done this week so far, I would like to work on extending the IDE and reduce the amount of clicks / keystrokes to browse things... >>>>>>>> >>>>>>>> m(o_o)m >>>>>>>> camillo >>>>>>>> >>>>>>>> On 2011-02-21, at 19:42, Tudor Girba wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> I would like to remind you that this Saturday, February 26, we organize a Sprint at SCG, University of Berne, Switzerland (room 107): >>>>>>>>> http://scg.unibe.ch/contact/maps >>>>>>>>> >>>>>>>>> Further details can be found below. Please let us know by mail if you plan to attend and what you would wish to work on (see below). >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Doru >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Begin forwarded message: >>>>>>>>> >>>>>>>>>> From: Tudor Girba <tudor.girba(a)gmail.com> >>>>>>>>>> Date: 1 February 2011 16:38:30 CET >>>>>>>>>> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> >>>>>>>>>> Cc: Adrian Lienhard <alienhard(a)netstyle.ch> >>>>>>>>>> Subject: [ANN] pharo focused sprint - bern, feb 26 >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> We would like to organize a Pharo Sprint on Saturday, February 26 at SCG, University of Berne, Switzerland (room 107): >>>>>>>>>> http://scg.unibe.ch/contact/maps >>>>>>>>>> >>>>>>>>>> Unlike other sprints, this would not be about fixing things from the tracker, but about building something new and reviewing the situation around one central topic. For this one, the main topic will be Morphic and the IDE. Why? Because it is time to rethink our day-to-day tools and bring them closer to this century (ok, maybe decade :)). It is Ok if you are not a specialist. It is more important to want to participate and learn. The rest will come in time. >>>>>>>>>> >>>>>>>>>> ***** Please let us know by mail if you plan to attend and what you would wish to work on (see below). >>>>>>>>>> >>>>>>>>>> Proposed tasks (other tasks are possible in the same area): >>>>>>>>>> - Enhancements of Morphic widgets: >>>>>>>>>> --- TabGroupMorph with lazy pages, closable tabs, overflow handling and toolbars (a start exists in Glamour) >>>>>>>>>> --- High level support for collapsable panes (based on the input of Gary) >>>>>>>>>> --- SearchMorph with multiple groups of items (like in Spotlight) >>>>>>>>>> --- MorphTreeMorph integrated with GeneralScrollPane to allow for space filling >>>>>>>>>> --- BreadcrumbMorph >>>>>>>>>> --- Hyperlinks in TextMorphs >>>>>>>>>> - Test and enhance the current IDE >>>>>>>>>> - Evaluate TextMorphs: NewTextMorph, PluggableTextMorph, SMxPluggableTextMorph etc >>>>>>>>>> - Prototype a new ToolSet solution >>>>>>>>>> - Enhancements of Glamour and of the Glamorous Toolkit >>>>>>>>>> --- Debugger >>>>>>>>>> --- Coder >>>>>>>>>> --- Multipage Workspace >>>>>>>>>> --- CodeBubbles >>>>>>>>>> - Develop WeakAnnouncement (start from the implementation of Lukas) >>>>>>>>>> - Evaluate the various keybinding implementations >>>>>>>>>> - Evaluate ToolBuilder >>>>>>>>>> - Evaluate the path to adopt SimpleMorphic >>>>>>>>>> >>>>>>>>>> A second working topic is getting Monticello faster, but this will only be tackled if there are enough people for the first one. >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Adrian and Doru >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> www.tudorgirba.com >>>>>>>>>> >>>>>>>>>> "Be rather willing to give than demanding to get." >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> www.tudorgirba.com >>>>>>>>> >>>>>>>>> "It's not how it is, it is how we see it." >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> www.tudorgirba.com >>>>>>> >>>>>>> "Value is always contextual." >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> www.lukas-renggli.ch >>>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "There are no old things, there are only old ways of looking at them." >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Jorge Ressia >>>> www.jorgeressia.com >>> >>> -- >>> www.tudorgirba.com >>> >>> "Yesterday is a fact. >>> Tomorrow is a possibility. >>> Today is a challenge." >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> > > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

Feb. 26, 2011

Re: [Pharo-project] About 1.2

by Miguel CobÃ¡

I think that is reasonble but I also think that at least you should give the people working on the issues (like Dale's solo sprint) a couple of day to sort all the issues. What about this, let people until monday and then release the tuesday at the end of day. Cheers El vie, 25-02-2011 a las 21:50 +0100, StÃ©phane Ducasse escribiÃ³: > Hi guys > > 1.2 should go out. Marcus and me should spend their time on 1.3, OPAL and the rest. > > Now for PharoDev we want to remove packages that are not about tools. > If you want XML, openDBX... help us using Metacello to build distributions = something that will work in 1.2 when > we will be in Pharo 10. Right now this is not normal that a problem in XML in 1.2 impacts the builds in 1.1. > > Proposing bloated images DOES NOT HELP US. Why? Because the goal is to have an INFRASTRUCTURE to take > a small image with a metacello description repository and load whatever we want. In the future we want to use > metacello to manage core and not to have a distinction between core and dev. We should be able to load all the time > RBEngine and use it all the time to fix the system. > > Right now we are LOSING TIME on fixing 1.2 configs while we should invest in the infrastructure that will enable > to be agile and load whatever configuration we/you will develop. > > So can we be focus on the infrastructure? The concept and tools that we will make us be really powerful in the > future? > > So if the community does not hear our call, we the board will take actions. We do not want to do that but if this > is necessary we will do it because we want 1.2 to get out. > > Stef > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Feb. 26, 2011

Re: [Pharo-project] introducing RPackage :)

by jannik.laval

Hi, There is also a nighty build in hudson server. Cheers, Jannik On Feb 26, 2011, at 21:48 , StÃ©phane Ducasse wrote: > > On Feb 26, 2011, at 8:12 PM, Tudor Girba wrote: > >> Hi, >> >> We use RPackage in Moose, and it works fine. We only encountered a small problem raised when renaming a class, but Cyrille fixed that, too. I am quite confident in it. >> >> The way to load it is like this (different repo): >> Gofer new >> squeaksource: 'PharoTaskForces'; >> package: 'ConfigurationOfRPackage'; >> load. >> (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. >> >> The translation of SystemChangeNotifier into Announcements happens in SystemAnnouncements package. > > thanks doru I will talk with cyrille monday. > >> >> Just a note, until we can remove the SystemChangeNotifier, we have to first get Monticello work with RPackage and > > What do you mean by "we have to first get Monticello work with RPackage " It does not? > > I will have a look. > >> SystemAnnouncements. Afterwards, we should hook Announcements directly in the system, and yet afterwards remove the categories and get the tools work with RPackage. >> >> Cheers, >> Doru >> >> >> On 26 Feb 2011, at 18:59, StÃ©phane Ducasse wrote: >> >>> Hi guys >>> >>> I would like to give a try to introduce RPackage = a complete rewrite of PackageInfo. >>> Moose people use it and I will sync with them to know. >>> >>> It would be great if some of you could load and play with the system >>> >>> >>> Gofer new >>> squeaksource: 'PharoInbox'; >>> package: 'ConfigurationOfRPackage'; >>> load. >>> (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. >>> >>> Note that RPackage is based on announcement. So there is just one place that register to systemNotifier. >>> So one of the following goal is to remove SystemChangeNotifier and replace it with announcement. >>> >>> Stef >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Every thing should have the right to be different." >> >> >> >> > >

Feb. 26, 2011

Re: [Pharo-project] we cannot add attachment anymore on the bug tracker

by StÃ©phane Ducasse

tx lukas Do you know if there is a normal process to request such increase? Stef On Feb 25, 2011, at 11:53 PM, Lukas Renggli wrote: > Thanks for letting me know. Getting the quota increased is pretty easy > (kudos Nathaniel), if you ask the right people ;-) > > Lukas > > On 25 February 2011 22:29, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Feb 25, 2011, at 8:33 PM, Tudor Girba wrote: >> >>> Isn't it because you went passed the quota? The bad thing about attachments in Google Code is that you have only 50MB for it. >>> >>> You can find the current status in Administer/Advanced. >>> >> Maybe this is the hint to move to something else... what I really want (need) is a bugtracker that allows better sorting of bug reports. >> Tags are great. But tags do not replace sub-projects. I want a bug tracker just for Cog. And one just for "the nuts", or one for morphic... >> >> This way we could actually get structure in the 560 reports... >> >> Redmine (http://www.redmine.org/) supports sub-projects. Or maybe https://www.chiliproject.org/ (a fork of redmine). >> >> >> Marcus >> >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

Feb. 26, 2011

Re: [Pharo-project] introducing RPackage :)

by StÃ©phane Ducasse

On Feb 26, 2011, at 8:12 PM, Tudor Girba wrote: > Hi, > > We use RPackage in Moose, and it works fine. We only encountered a small problem raised when renaming a class, but Cyrille fixed that, too. I am quite confident in it. > > The way to load it is like this (different repo): > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'ConfigurationOfRPackage'; > load. > (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. > > The translation of SystemChangeNotifier into Announcements happens in SystemAnnouncements package. thanks doru I will talk with cyrille monday. > > Just a note, until we can remove the SystemChangeNotifier, we have to first get Monticello work with RPackage and What do you mean by "we have to first get Monticello work with RPackage " It does not? I will have a look. > SystemAnnouncements. Afterwards, we should hook Announcements directly in the system, and yet afterwards remove the categories and get the tools work with RPackage. > > Cheers, > Doru > > > On 26 Feb 2011, at 18:59, StÃ©phane Ducasse wrote: > >> Hi guys >> >> I would like to give a try to introduce RPackage = a complete rewrite of PackageInfo. >> Moose people use it and I will sync with them to know. >> >> It would be great if some of you could load and play with the system >> >> >> Gofer new >> squeaksource: 'PharoInbox'; >> package: 'ConfigurationOfRPackage'; >> load. >> (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. >> >> Note that RPackage is based on announcement. So there is just one place that register to systemNotifier. >> So one of the following goal is to remove SystemChangeNotifier and replace it with announcement. >> >> Stef >> >> > > -- > www.tudorgirba.com > > "Every thing should have the right to be different." > > > >

Feb. 26, 2011

Re: [Pharo-project] [ANN] More on Keymappings

by Francisco Ortiz PeÃ±aloza

You're telling me that if i do a clean installation of 1.5 it would work? Thanks in advance, Francisco On Sat, Feb 26, 2011 at 3:50 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Mmm, If you had 1.4 and updated to 1.5, you will have some problems because > I did some refactorings on that... :/. > > On Sat, Feb 26, 2011 at 10:12 AM, Francisco Ortiz PeÃ±aloza > <patchinko(a)gmail.com> wrote: >> >> Guille i was using 1.4 and worked excellent, just tried 1.5 and on >> every stroke i made i've got a DNU on #realtarget >> >> Installed on last PharoCore 1.2, should i try it on 1.3? >> >> Great work, >> Fran >> >> On Sat, Feb 26, 2011 at 5:29 AM, laurent laffont >> <laurent.laffont(a)gmail.com> wrote: >> > >> > On Sat, Feb 26, 2011 at 5:42 AM, Guillermo Polito >> > <guillermopolito(a)gmail.com> wrote: >> >> >> >> What do we have now? >> >> >> >> - Can provide settings for a set of morphs >> >> >> >> - Can provide settings for a TextEditors (Smalltalk editor and related) >> >> >> >> - Settings integration >> >> I added some methods to the Settings Tree Builder in order to avoid >> >> references from the users code. >> >> >> >> - I ran Slint over it and cleaned it a lot more :). ( And learnt that >> >> Slint is there :P ) >> >> >> >> More info in here:Â http://guilleel3.blogspot.com/ >> > >> > A new blog, cool ! >> > Can I have Emacs-like keybinding in code editor, to switch browser, ... >> > ? >> > Laurent. >> > >> >> >> >> Guille >> > >> > >> > >

Feb. 26, 2011

Re: [Pharo-project] introducing RPackage :)

by Tudor Girba

Hi, We use RPackage in Moose, and it works fine. We only encountered a small problem raised when renaming a class, but Cyrille fixed that, too. I am quite confident in it. The way to load it is like this (different repo): Gofer new squeaksource: 'PharoTaskForces'; package: 'ConfigurationOfRPackage'; load. (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. The translation of SystemChangeNotifier into Announcements happens in SystemAnnouncements package. Just a note, until we can remove the SystemChangeNotifier, we have to first get Monticello work with RPackage and SystemAnnouncements. Afterwards, we should hook Announcements directly in the system, and yet afterwards remove the categories and get the tools work with RPackage. Cheers, Doru On 26 Feb 2011, at 18:59, StÃ©phane Ducasse wrote: > Hi guys > > I would like to give a try to introduce RPackage = a complete rewrite of PackageInfo. > Moose people use it and I will sync with them to know. > > It would be great if some of you could load and play with the system > > > Gofer new > squeaksource: 'PharoInbox'; > package: 'ConfigurationOfRPackage'; > load. > (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. > > Note that RPackage is based on announcement. So there is just one place that register to systemNotifier. > So one of the following goal is to remove SystemChangeNotifier and replace it with announcement. > > Stef > > -- www.tudorgirba.com "Every thing should have the right to be different."

Feb. 26, 2011

Re: [Pharo-project] [ANN] More on Keymappings

by Camillo Bruni

Hey Guille, Step by step I will try to add most of the TextEditor / SmalltalkEditor keymappings. so far I have committed a basic set. generally I commit on a 1h basis, so that should be sufficient to track progress ;) camillo On 2011-02-26, at 18:54, Guillermo Polito wrote: > Camillo, > > What's a more complete set of commands? Can you be more Specific? hehe. > > Next thing I want to do is get rid of every hardcoded mapping (i.e from > Editor and SmalltalkEditor) and configure it this way... But It's a lot of > work I couldn't do. Maybe this two weeks I can do something on it since I > am on vacation, but my girlfriend will kill me :). > > I'd love to know what you're working on so we don't do innecesary work! > > Guille > > On Sat, Feb 26, 2011 at 12:55 PM, Camillo Bruni <camillo.bruni(a)inria.fr>wrote: > >> Hi, >> >> I am currently writing a more complete set of commands for the editors. I >> ll post soon. >> >> m(^_-)m >> camillo >> >> On 2011-02-26, at 14:12, Francisco Ortiz PeÃ±aloza wrote: >> >>> Guille i was using 1.4 and worked excellent, just tried 1.5 and on >>> every stroke i made i've got a DNU on #realtarget >>> >>> Installed on last PharoCore 1.2, should i try it on 1.3? >>> >>> Great work, >>> Fran >>> >>> On Sat, Feb 26, 2011 at 5:29 AM, laurent laffont >>> <laurent.laffont(a)gmail.com> wrote: >>>> >>>> On Sat, Feb 26, 2011 at 5:42 AM, Guillermo Polito >>>> <guillermopolito(a)gmail.com> wrote: >>>>> >>>>> What do we have now? >>>>> >>>>> - Can provide settings for a set of morphs >>>>> >>>>> - Can provide settings for a TextEditors (Smalltalk editor and related) >>>>> >>>>> - Settings integration >>>>> I added some methods to the Settings Tree Builder in order to avoid >>>>> references from the users code. >>>>> >>>>> - I ran Slint over it and cleaned it a lot more :). ( And learnt that >>>>> Slint is there :P ) >>>>> >>>>> More info in here: http://guilleel3.blogspot.com/ >>>> >>>> A new blog, cool ! >>>> Can I have Emacs-like keybinding in code editor, to switch browser, ... >> ? >>>> Laurent. >>>> >>>>> >>>>> Guille >>>> >>>> >>> >> >> >>

Feb. 26, 2011

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Comment #13 on issue 3707 by stephane...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 here is the one of 1.1 defaultStyleTable "color can be a valid argument to Color class>>colorFrom: , or nil to use the editor text color. Multiple emphases can be specified using an array e.g. #(bold italic). If emphasis is not specified, #normal will be used. if pixel height is not specified , then the editor font size will be used. " ^#( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default ( black ) ) (invalid ( red ) ) (excessCode ( red ) ) (comment ( green muchDarker ) ) (unfinishedComment ( green muchDarker ) ) (#'$' ( magenta muchDarker) ) (character ( magenta muchDarker) ) (integer ( magenta muchDarker) ) (number ( magenta muchDarker) ) (#- ( magenta muchDarker) ) (symbol ( magenta muchDarker) ) (stringSymbol ( magenta muchDarker) ) (literalArray ( magenta muchDarker) ) (string ( magenta muchDarker) ) (unfinishedString ( magenta muchDarker) ) (assignment ( black ) ) (ansiAssignment ( black ) ) (literal ( black ) ) (keyword ( black ) ) (binary ( black ) ) (unary ( black ) ) (incompleteKeyword ( black ) ) (incompleteBinary ( black ) ) (incompleteUnary ( black ) ) (undefinedKeyword ( red ) ) (undefinedBinary ( red ) ) (undefinedUnary ( red ) ) (patternKeyword ( black ) bold ) (patternBinary ( black ) bold ) (patternUnary ( black ) bold ) (#self ( cyan muchDarker ) ) (#super ( cyan muchDarker ) ) (#true ( cyan muchDarker ) ) (#false ( cyan muchDarker ) ) (#nil ( cyan muchDarker ) ) (#thisContext ( cyan muchDarker ) ) (#return ( black ) ) (patternArg ( blue muchDarker ) ) (methodArg ( blue muchDarker ) ) (blockPatternArg ( blue muchDarker ) ) (blockArg ( blue muchDarker ) ) (argument ( blue muchDarker ) ) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 black ) (rightParenthesis1 black ) (leftParenthesis2 black ) (rightParenthesis2 black ) (leftParenthesis3 black ) (rightParenthesis3 black ) (leftParenthesis4 black ) (rightParenthesis4 black ) (leftParenthesis5 black ) (rightParenthesis5 black ) (leftParenthesis6 black ) (rightParenthesis6 black ) (leftParenthesis7 black ) (rightParenthesis7 black ) (blockStart black ) (blockEnd black ) (blockStart1 black ) (blockEnd1 black ) (blockStart2 black ) (blockEnd2 black ) (blockStart3 black ) (blockEnd3 black ) (blockStart4 black ) (blockEnd4 black ) (blockStart5 black ) (blockEnd5 black ) (blockStart6 black ) (blockEnd6 black ) (blockStart7 black ) (blockEnd7 black ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (byteArrayStart black ) (byteArrayEnd black ) (byteArrayStart1 black ) (byteArrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black ) (primitiveOrExternalCallEnd black ) (methodTempBar black ) (blockTempBar black ) (blockArgsBar black ) (primitive gray ) (externalFunctionCallingConvention gray ) (module gray ) (blockTempVar ( blue muchDarker ) ) (blockPatternTempVar ( blue muchDarker ) ) (instVar ( blue muchDarker ) ) (workspaceVar ( blue muchDarker ) ) (undefinedIdentifier ( red ) ) (incompleteIdentifier ( blue muchDarker ) ) (tempVar ( blue muchDarker ) ) (patternTempVar ( blue muchDarker ) ) (poolConstant ( blue muchDarker ) ) (classVar ( blue muchDarker ) ) (globalVar ( blue muchDarker ) ) )

Feb. 26, 2011