- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Status bar

by Gary Chambers

We have used a Panel with a TextMorph inside... Regards, Gary ----- Original Message ----- From: "Hilaire Fernandes" <hilaire.fernandes(a)gmail.com> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Sunday, March 13, 2011 9:54 AM Subject: [Pharo-project] Status bar > Hello, > > Do we have nay thing close as a status bar in Polymorph? > A widget you plug in the bottom of a window and where you print textual > information. > > Hilaire > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > >

March 15, 2011

Re: [Pharo-project] the glamorous toolkit project

by Fernando Olivero

Regarding selection and multiple selections i recommend reading [1] , the chapter on Unification, section 5-2-1. It explains the current issues with the selection and provides hints on implementing a better scheme. [1] Jef Raskin, The Humane Interface. On Mon, Mar 14, 2011 at 8:31 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Mariano, > > Thanks for the suggestions. > > As I said, you are welcome to participate. It does not have to be much. You can just spend a bit of time to learn Glamour and then play 15 minutes per day :). > > Cheers, > Doru > > > > On 14 Mar 2011, at 19:34, Mariano Martinez Peck wrote: > >> Hi Tudor? Â do you want to succeed? Â Do a kind of OB but with multiple selection :) >> I would like to remove, for example, several methods together... >> >> cheers >> >> mariano >> >> On Sun, Mar 13, 2011 at 10:45 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> Thanks, Esteban. >> >> Jorge did a nice job at improving it to handle special objects. There are still a couple of situations left, but it is Â already reliable. >> >> Cheers, >> Doru >> >> >> On 13 Mar 2011, at 19:33, Esteban Lorenzano wrote: >> >> > wow.... GTInspector is really great :) >> > gamorous tools are becoming very interesting... keep going that way! >> > >> > I do believe in the near future GT can replace OB as our default IDE, if we continue improving like this :) >> > >> > cheers, >> > Esteban >> > >> > El 13/03/2011, a las 10:34a.m., Marcus Denker escribiÃ³: >> > >> >> >> >> On Mar 13, 2011, at 2:05 PM, Tudor Girba wrote: >> >> >> >>> I think that this is a good idea. Having the Core tools better is definitely a good thing. >> >>> >> >> >> >> One thing to keep in mind is that we need (ass soon as possible) to have *one* set >> >> of tools... with OB we have seen that we have just not the manpower to in parallel >> >> maintain two sets of tools (Core vs. Dev). >> >> >> >> The notion of "Core Tools" is broken. Whichever tools we do in the future need >> >> to *replace* the old tools. >> >> >> >> Â Â Â Marcus >> >> >> >> >> >> -- >> >> Marcus Denker Â -- http://www.marcusdenker.de >> >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> >> >> > >> > >> >> -- >> www.tudorgirba.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> >> >> > > -- > www.tudorgirba.com > > "From an abstract enough point of view, any two things are similar." > > > > >

March 15, 2011

[Pharo-project] Deadline for the RMLL 2011 is 31 of march and it would be good to have a Smalltalk presence there.

by StÃ©phane Ducasse

http://2011.rmll.info/appel.html I'm planning to attend but may be some other people want to join. Stef

March 15, 2011

[Pharo-project] Pharogenesis anew

by Max Leske

I just pushed the (hopefully) final version of Pharogenesis to github (github.com/pharogenesis/pharogenesis) I appologize to the followers for deleting and recreating the repository but that's the only way to keep the history clean. Max

March 15, 2011

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