March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3817 in pharo: make Object >> error: deprecated

by pharo＠googlecode.com

Comment #13 on issue 3817 by marianopeck: make Object >> error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 Thanks Guille. -1 too And +1 to use special errors when necessary (again, check my projects and you will see I do this)

March 15, 2011

Re: [Pharo-project] Issue 3247 breaks external packages

by StÃ©phane Ducasse

On Mar 15, 2011, at 5:58 AM, Miguel CobÃ¡ wrote: > I am trying to run Magma and uses TextConstants at: idiom. > > Before 3247 TextConstants was a Dictionary and the at: message works ok. > But now that it is a SharedPool there is no way to use the external code > without modify it before it works in Pharo 1.2. This change doesn't even > tries to present the same interface to acces the Text constants as > before. The TextConstants>>at: message in Pharo 1.2 is the Object>>at: > method that obviously doesn't work. How could we do that? If the system badly uses a global variable in all sort of different ways then there is no way that we can propose the same interface. Then TextConstants had different and bad use: - storing constants - storing volatile information about fonts and all sorts of registrations for fonts!!! in textConstants "oh yes this is the dictionary so lets us mess there" instead of using adequate classVariables in adequate classes (we should still clean this part). TextSharedInformation below is for the moment containing all the crap. > What is the reason of this change? Why is better than the dictionary (I > suppose that reifying it is a reason)? because TextConstants was the **last** global pool and it was like a jellyfish. In fact when SharedPool were introduced by andreas (it was a good idea BTW) TextConstants was left because it was touching a lot of code. If we want to be able to get a bootstrappable core (and eliot and us want that) then we should clean the mess. Yes all the sharedPool are subclasses of sharedPool except TextConstants.... imagine the code to manage that. Is it a class, a traits, a global is it a dictionary of may be this is textConstants..... > What is the intended usage for code that uses TextConstants the > dictionary access way? > Specifically, code like this doesn't work anymore in Pharo1.2 > > self ~~ (TextConstants at: #DefaultTabsArray) > and: [ self ~~ (TextConstants at: #DefaultMarginTabsArray) ] Using accessors to control access to defaultTabsArrat and DefaultMargin.... is the first steps. Like that migration is easier. Now I do not really understand why a database has to change that kind of text information. > > What should I do, I can't see a reopen status in the issue tracker. > Should I open a new ticket? Have a look in the SharedPool there is a classVariable SharedPool subclass: #TextConstants instanceVariableNames: '' classVariableNames: 'BS BS2 Basal Bold CR Centered Clear CrossedX CtrlA CtrlB CtrlC CtrlD CtrlDigits CtrlE CtrlF CtrlG CtrlH CtrlI CtrlJ CtrlK CtrlL CtrlM CtrlN CtrlO CtrlOpenBrackets CtrlP CtrlQ CtrlR CtrlS CtrlT CtrlU CtrlV CtrlW CtrlX CtrlY CtrlZ Ctrla Ctrlb Ctrlc Ctrld Ctrle Ctrlf Ctrlg Ctrlh Ctrli Ctrlj Ctrlk Ctrll Ctrlm Ctrln Ctrlo Ctrlp Ctrlq Ctrlr Ctrls Ctrlt Ctrlu Ctrlv Ctrlw Ctrlx Ctrly Ctrlz DefaultBaseline DefaultFontFamilySize DefaultLineGrid DefaultMarginTabsArray DefaultMask DefaultRule DefaultSpace DefaultTab DefaultTabsArray ESC EndOfRun Enter Italic Justified LeftFlush LeftMarginTab RightFlush RightMarginTab Space Tab TextSharedInformation' poolDictionaries: '' category: 'Collections-Text' Stef > > Cheers > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > >

March 15, 2011

Re: [Pharo-project] from bash to Coral

by StÃ©phane Ducasse

tx david. > FYI, rudimentary scripting on top of OSProcess/CommandShell is in class > CommandShell, method category "command scripting". Possibly the shell > syntax parsing, file name globbing etc from CommandShell could be tied > in with Coral, although I have not looked into this. > > Dave > > On Mon, Mar 14, 2011 at 03:20:06PM +0100, Adrien BARREAU wrote: >> >> Hi Laurent, >> >> I would say yes, because Coral can execute any piece of Smalltalk. >> So if you can do what that script does with OSProcess, there is no reason you can't put it in a Coral script. >> >> At that time, there is no Coral API to make your life easier on top on things like OSProcess, but perhaps I should write some things like that. >> If you have any ideas while trying, don't hesitate to tell me :). >> >> Adrien. >> >> From: laurent.laffont(a)gmail.com >> Date: Mon, 14 Mar 2011 12:33:30 +0100 >> To: pharo-project(a)lists.gforge.inria.fr >> Subject: [Pharo-project] from bash to Coral >> >> Hi, >> Is it possible today to write this using Coral ? >> find application library -type f $ -name "*.php" -o -name "*.phtml" $ -exec /usr/local/bin/xgettext -j -L PHP --from-code=utf-8 --keyword=traduire --keyword=_ -o library/translation/fr.pot {} \; >> >> for i in `ls library/translation/*.po`do /usr/local/bin/msgmerge -s $i library/translation/fr.pot -o $i /usr/local/bin/msgfmt -o `echo $i|cut -d '.' -f1`.mo $i >> >> done >> >> >> I need to write several scripts like this - would be cool to start with Coral. >> >> Laurent Laffont - @lolgzs >> >> >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> Developer group: http://cara74.seasidehosting.st >> >> >> >

March 15, 2011

Re: [Pharo-project] Question about the design of the setting browser

by Alain Plantec

Le 14/03/2011 21:44, StÃ©phane Ducasse a Ã©crit : > Hi alain > > I was reading the settingbrowser code and I have a question: > why the settingbrowser inherits from MorphTreeModel. > > Why it does not inherits from Object or Model and has different widgets > that may or not inherits from MorphTreeModel. no particular reason behind > To me it fits better the composition. yes, it seems better for re-composition but with the price of more classes. Alain > Stef > >

March 15, 2011

Re: [Pharo-project] Jtalk, a Smalltalk for web developers

by StÃ©phane Ducasse

I will read the rest :) eval: aString ^{'return eval(aString);'} ! visitBlockNode: aNode stream nextPutAll: '(function('. aNode parameters do: [:each | stream nextPutAll: each] separatedBy: [stream nextPutAll: ', ']. stream nextPutAll: '){'. aNode nodes do: [:each | self visit: each]. stream nextPutAll: '})' visitMethodNode: aNode | str currentSelector | currentSelector := aNode selector asSelector. nestedBlocks := 0. earlyReturn := false. stream nextPutAll: 'smalltalk.method({', String cr; nextPutAll: 'selector: "', aNode selector, '",', String cr; nextPutAll: 'source: unescape("', aNode source escaped, '"),', String cr; nextPutAll: 'fn: function('. aNode arguments do: [:each | stream nextPutAll: each] separatedBy: [stream nextPutAll: ', ']. stream nextPutAll: '){', String cr; nextPutAll: 'var self=this;', String cr. str := stream. stream := '' writeStream. aNode nodes do: [:each | self visit: each]. earlyReturn ifTrue: [ str nextPutAll: 'try{']. str nextPutAll: stream contents. stream := str. stream nextPutAll: String cr; nextPutAll: 'return self;'. earlyReturn ifTrue: [ stream nextPutAll: String cr, '} catch(e) {if(e.name === ''stReturn'' && e.selector === ', currentSelector printString, '){return e.fn()} throw(e)}']. stream nextPutAll: '}', String cr; nextPutAll: '})' ok now I understand. Stef

March 15, 2011

Re: [Pharo-project] [ANN] Sandcastles themes for Pharo 1.2

by StÃ©phane Ducasse

BTW one of the goal of alain is too make sure that creating a new theme is (most of the time) just a matter of pushing the right value to a theme. Stef On Mar 15, 2011, at 8:08 AM, laurent laffont wrote: > I like the Beach one - really clean. Feedback: > - background colors of raws in settings browser don't really match > - a beach-colored background for the world would be nice -- indeed we can change it in settings > - I prefer the window title icons of the Pharo way one (especially the "Pharo" at top-right) > > Evaluate UITheme exampleBasicControls: > - there's rounded-corners border in the window with a padding, excepted on the top - strange > - rounded widgets in the right column have minor glitches. > > I would love a theme with dark-gray background instead of white for code / list / workspace because my eyes suffer (I work on dark Emacs almost all day - far better).... there's no setting for that. > > Great job. > > Laurent. > > On Mon, Mar 14, 2011 at 9:51 PM, Patrick Barroca <patrick.barroca(a)gmail.com> wrote: > Hi all, > > I'm pleased to announce here our UIThemes for Pharo 1.2 > "Sandcastle Beach" adopts sand shades and "Sandcastle Pharoway" showcases our favorite lighthouse in blue shades. > > Give them a try, repository is http://www.squeaksource.com/SandcastlesThemes. > > Once the package is loaded, themes can be chosen in System/Settings menu and Appearance>Morphic section. > > Regards, > > -- > Claire & Patrick Barroca >

March 15, 2011

Re: [Pharo-project] [ANN] Sandcastles themes for Pharo 1.2

by StÃ©phane Ducasse

the log is neat I want it :) Stef On Mar 14, 2011, at 9:51 PM, Patrick Barroca wrote: > Hi all, > > I'm pleased to announce here our UIThemes for Pharo 1.2 > "Sandcastle Beach" adopts sand shades and "Sandcastle Pharoway" showcases our favorite lighthouse in blue shades. > > Give them a try, repository is http://www.squeaksource.com/SandcastlesThemes. > > Once the package is loaded, themes can be chosen in System/Settings menu and Appearance>Morphic section. > > Regards, > > -- > Claire & Patrick Barroca > <SandcastleBeach.png><SandcastlePharoway.png>

March 15, 2011

Re: [Pharo-project] [ANN] Sandcastles themes for Pharo 1.2

by laurent laffont

I like the Beach one - really clean. Feedback: - background colors of raws in settings browser don't really match - a beach-colored background for the world would be nice -- indeed we can change it in settings - I prefer the window title icons of the Pharo way one (especially the "Pharo" at top-right) Evaluate UITheme exampleBasicControls: - there's rounded-corners border in the window with a padding, excepted on the top - strange - rounded widgets in the right column have minor glitches. I would love a theme with dark-gray background instead of white for code / list / workspace because my eyes suffer (I work on dark Emacs almost all day - far better).... there's no setting for that. Great job. Laurent. On Mon, Mar 14, 2011 at 9:51 PM, Patrick Barroca <patrick.barroca(a)gmail.com>wrote: > Hi all, > > I'm pleased to announce here our UIThemes for Pharo 1.2 > "Sandcastle Beach" adopts sand shades and "Sandcastle Pharoway" showcases > our favorite lighthouse in blue shades. > > Give them a try, repository is > http://www.squeaksource.com/SandcastlesThemes. > > Once the package is loaded, themes can be chosen in System/Settings menu > and Appearance>Morphic section. > > Regards, > > -- > Claire & Patrick Barroca >

March 15, 2011

[Pharo-project] Fwd: [squeak-dev] Re: SqueakSource down... again

by StÃ©phane Ducasse

It would be nice if somebody would give a try to install this version of squeaksource Stef Begin forwarded message: > From: "Pape, Tobias" <Tobias.Pape(a)student.hpi.uni-potsdam.de> > Date: March 15, 2011 12:06:58 AM GMT+01:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Cc: Michael Haupt <mhaupt(a)gmail.com>, "Hirschfeld, Robert" <Robert.Hirschfeld(a)hpi.uni-potsdam.de> > Subject: Re: [Pharo-project] [squeak-dev] Re: SqueakSource down... again > > Dear Stephane > > Am 2011-02-24 um 22:28 schrieb Michael Haupt: > >> Stephane, >> >> I forward your question to Robert and Tobias; Tobias is maintaining our installation. >> >> Michael >> >> Am 24.02.2011 um 18:32 schrieb StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> Hi michael >>> >>> where can we find the code for such a GemStone backend source? > > > Please accept my apologies for my rather late > reply; I had student projects to finish and I > still have examinations going on. > > For SqueakSource with a GemStone-Backend, > look at: http://seaside.gemstone.com/ss/ss2.html > IIRC, I used ConfigurationOfGsSqueakSource-DaleHenrichs.8.mcz > to Load it into my Gemstone 2.3. > > Please Note, this is tested only for > > â¢ GemStone 2.3 > â¢ Seaside 2.8 > â¢ Magritte (1) > > And Email-support is not working at all. > Furthermore, Migrating from a âNormalâ squeaksource with > file-based storage requires some administrative effort. > I had used some small scripts at the time I was doing this > at the SWA group. > > Nevertheless, I am working on an improved version, > that shall work with Seaside3.0/Magritte2 on Gemstone 3 (or even 4) > Email-Support will be back then and I heavily focus on migration. > However, this code is all untested and I don't expect it to > be any usable before April, if not May. > > I hope that helps you. > > Regards > -Tobias > >

March 15, 2011

[Pharo-project] Keymapping development issues

by Tudor Girba

Hi, It seems to me that there are problems due to the merging of Keymapping sub packages into one Keymapping package: - first, camillo seems to publish in Keymapping, while Guillermo publishes in Keymapping-*. This means that one or the other will most certainly lose code. - second, the version published by Camillo reached Keymapping-CamilloBruni.3, but there already were versions that reached Keymapping-cds.113, which makes Monticello list the new commits by Camillo at the bottom Would it be possible if you two would get synchronized? Also, ConfigurationOfKeymapping is still broken: - loading "(self project version: '1.5') load" still raises the Character>>+ problem due to the initialization - however, loading "(self project version: '1.5-baseline') load" works because it takes the new versions into account Would it be possible to update the configuration? Cheers, Doru On 14 Mar 2011, at 15:20, Camillo Bruni wrote: > > On 2011-03-14, at 15:17, Tudor Girba wrote: > >> I saw :). Just two questions: >> - Is the ConfigurationOfKeymapping updated? > > that I pushed to the existing branch > >> - Is it already usable? > not yet, didn't have too much time so far, but the basic tests are working. > the interface will stay the same, but the internals will be much cleaner and more explicit > >> Cheers, >> Doru >> >> >> On 14 Mar 2011, at 15:15, Camillo Bruni wrote: >> >>> I pushed everying into a single Keymapping package for now. As soon as there is full functionality we should separate it again. >>> >>> >>> camillo >>> >>> >>> On 2011-03-13, at 22:40, Tudor Girba wrote: >>> >>>> Excellent initiative Camillo! >>>> >>>> Regarding multiple packages: Having multiple packages limits the conflicts, and saving them individually (for now) it's a small price to pay. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 13 Mar 2011, at 22:28, Camillo Bruni wrote: >>>> >>>>> furthermore, lets use a single repos/package (or whatever this is called in MC). >>>>> I do not like to commit 3 times while refactoring. >>>>> later on we can still split it up so people can actually decide on what to load. >>>>> >>>>> camillo >>>>> >>>>> On 2011-03-13, at 22:20, Camillo Bruni wrote: >>>>> >>>>>> I can push my changes. but I don't think we should rely too much on your old code. >>>>>> >>>>>> Im trying to keep the structure of the classes, that was already very nice IMO. >>>>>> I manly adress the following issues: >>>>>> >>>>>> - use of arrays as result (dedicatet results object) >>>>>> - string to match the shortcuts with the incoming keyboard event (dropped all of that and started to work on tests to use the shortcuts directly) >>>>>> - weird event matching directly on morph (simplified and using a recursive function call now) >>>>>> - horrible unreadable variable names (wherever I started I tried to put long names to make the code readable) >>>>>> >>>>>> I suggest we can work together on the new code base, since the interface will stay fairly compatible. >>>>>> >>>>>> camillo >>>>>> >>>>>> On 2011-03-13, at 22:08, Guillermo Polito wrote: >>>>>> >>>>>>> Camillo, I was fixing some tests and going to refactor some ugly parts of >>>>>>> the package. >>>>>>> >>>>>>> Is there a way to join forces so we don't step into the other work? >>>>>>> >>>>>>> Guille >>>>>>> >>>>>>> On Sun, Mar 13, 2011 at 6:04 PM, Camillo Bruni <camillo.bruni(a)inria.fr>wrote: >>>>>>> >>>>>>>> I started on the last Lille sprint a complete rewrite of the Keymapping >>>>>>>> package. As of now it is not yet functional but the growing test-coverage >>>>>>>> should help to solve this issue. >>>>>>>> >>>>>>>> m(^_-)m >>>>>>>> camillo >>>>>>>> >>>>>>>> On 2011-03-03, at 15:16, Camillo Bruni wrote: >>>>>>>> >>>>>>>>> Right, >>>>>>>>> >>>>>>>>> the stable has a preconditio which limits it to pharo 1.2. >>>>>>>>> Furthermore the initialization code seems to be incompatible as it uses >>>>>>>> to:do: on Character which is AFAIK not implemented in the core image Pharo >>>>>>>> 1.3. Hence apply the following changes: >>>>>>>>> >>>>>>>>> KMKeyEvent class >> initializeControlSequences >>>>>>>>> >>>>>>>>> ... >>>>>>>>> $a asciiValue to: $z asciiValue do: [:each | >>>>>>>>> d add: each asCharacter -> (each - $a asciiValue + 1)]. >>>>>>>>> ... >>>>>>>>> >>>>>>>>> then it should work. >>>>>>>>> >>>>>>>>> m(^_-)m >>>>>>>>> camillo >>>>>>>>> >>>>>>>>> >>>>>>>>> On 2011-03-03, at 09:25, Tudor Girba wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I am very interested to get Keymapping integrated into Glamour. Could >>>>>>>> someone help me to load it? >>>>>>>>>> >>>>>>>>>> I tried: >>>>>>>>>> - in Pharo 1.2: >>>>>>>>>> Gofer it squeaksource: 'Keymapping'; package: >>>>>>>> 'ConfigurationOfKeymapping'; load. >>>>>>>>>> (ConfigurationOfKeymapping project version: #stable) load >>>>>>>>>> >>>>>>>>>> - in Pharo 1.3: >>>>>>>>>> Gofer it squeaksource: 'Keymapping'; package: >>>>>>>> 'ConfigurationOfKeymapping'; load. >>>>>>>>>> (ConfigurationOfKeymapping project version: '1.5') load >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Doru >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 27 Feb 2011, at 09:59, Tudor Girba wrote: >>>>>>>>>> >>>>>>>>>>> I also I cannot load Keymapping 1.5 in Pharo 1.2. I get DNU for >>>>>>>> Character>>+. This is due to an initialization in KMKeyEvent (see the >>>>>>>> attached debug log). >>>>>>>>>>> >>>>>>>>>>> I did the followings: >>>>>>>>>>> Gofer it >>>>>>>>>>> squeaksource: 'Keymapping'; >>>>>>>>>>> package: 'ConfigurationOfKeymapping'; >>>>>>>>>>> load. >>>>>>>>>>> >>>>>>>>>>> (ConfigurationOfKeymapping project version: #stable) load >>>>>>>>>>> >>>>>>>>>>> Am I missing something, or is this version not supposed to work in >>>>>>>> Pharo 1.2? >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Doru >>>>>>>>>>> >>>>>>>>>>> <PharoDebug.log> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 26 Feb 2011, at 21:08, Francisco Ortiz PeÃ±aloza wrote: >>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> www.tudorgirba.com >>>>>>>>>>> >>>>>>>>>>> "Every thing has its own flow." >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> www.tudorgirba.com >>>>>>>>>> >>>>>>>>>> "Every thing should have the right to be different." >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Value is always contextual." >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "If you interrupt the barber while he is cutting your hair, >> you will end up with a messy haircut." >> >> > > -- www.tudorgirba.com "Some battles are better lost than fought."

March 15, 2011