November 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] SmalltalkImage

by Benjamin

On Nov 7, 2010, at 10:51 AM, StÃ©phane Ducasse wrote: > SmalltalkImage current > instVarAt: #globals put: SystemDictionary new > > Something like that. > This code initialize Smalltalk, but I haven't found where Smalltalk is stored. Smalltalk is not a SmalltalkImage inst var nor class var neither Smalltalk class inst var ... So I wonder where to find it ... Ben > ? > On Nov 7, 2010, at 2:46 AM, Benjamin wrote: > >> Hi guys, >> >> I wonder how SmalltalkImage create the Smalltalk instance. >> >> Can someone explain me that ? >> >> >> >> >> Thank you >> >> Ben >> > >

Nov. 7, 2010

Re: [Pharo-project] Fwd:Dr.geo en Arabe

by Hilaire Fernandes

Thanks for the info. I don't have the resource to work on that topic. I was just in need to know what I could reply to these request for an Arabian version of DrGeo. So far only doeable under Etoys with Pango, so in Linux only context. Hilaire Le 06/11/2010 22:04, YossiDM a Ã©crit : > > I've had problems with Hebrew fonts which should fall in the same problem > space. > > I just tried some true type ones and the glyphs don't show (same fonts work > just fine in eclipse and visual studio). Maybe a bitmap version would work. > In any case, it's hard enough getting right to left working in my > experience. I don't believe it works particularly well in morphic and in the > editors to be useful and you end up being reduced to cut and paste with > strings (assuming you can get the string text to even display correctly). > > I've fooled around with unicode and utf-8 without much luck, but perhaps > someone more familiar with Pharo internals can come up with better > internationalization solutions. Also keep in mind there are both specialized > keyboards and ones that just map font glyphs based on querty, and also > overlays. Most of this comes from the host OS of course - check it out on > Mac OSX, lots of settings here, but nothing I've tried works with Pharo. > > > -- Dr. Geo, to discover geometry on Linux, Windows, MAC and XO http://community.ofset.org/index.php/DrGeo

Nov. 7, 2010

Re: [Pharo-project] Date time iso8601 format

by laurent laffont

On Sun, Nov 7, 2010 at 1:50 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > The other way. For example > > DateAndTime now printISO8601 > > Laurent > It seems Chronos http://chronos-st.org/ has such formatters (ISO8601PrintPolicy) but AnsiStandardCalendarClock is missing in Pharo.... Laurent > > > On Sun, Nov 7, 2010 at 1:28 PM, Johan Brichau <johan(a)inceptive.be> wrote: > >> Laurent, >> >> DateAndTime readFrom: '2008-02-10T12:00:00Z' readStream >> >> Does that yield what you want? >> >> cheers >> Johan >> >> On 06 Nov 2010, at 15:07, laurent laffont wrote: >> >> Hi, >> >> I cannot find which method to use to get a Date in iso 8601 format like >> '2008-02-10T12:00:00Z' ? >> >> >> Cheers, >> >> Laurent Laffont >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> >> >> >

Nov. 7, 2010

Re: [Pharo-project] Date time iso8601 format

by laurent laffont

The other way. For example DateAndTime now printISO8601 Laurent On Sun, Nov 7, 2010 at 1:28 PM, Johan Brichau <johan(a)inceptive.be> wrote: > Laurent, > > DateAndTime readFrom: '2008-02-10T12:00:00Z' readStream > > Does that yield what you want? > > cheers > Johan > > On 06 Nov 2010, at 15:07, laurent laffont wrote: > > Hi, > > I cannot find which method to use to get a Date in iso 8601 format like > '2008-02-10T12:00:00Z' ? > > > Cheers, > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > > >

Nov. 7, 2010

Re: [Pharo-project] Date time iso8601 format

by Johan Brichau

Laurent, DateAndTime readFrom: '2008-02-10T12:00:00Z' readStream Does that yield what you want? cheers Johan On 06 Nov 2010, at 15:07, laurent laffont wrote: > Hi, > > I cannot find which method to use to get a Date in iso 8601 format like '2008-02-10T12:00:00Z' ? > > > Cheers, > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/

Nov. 7, 2010

[Pharo-project] squeaksource down

by Max Leske

Squeaksource seems to be down again... Max

Nov. 7, 2010

Re: [Pharo-project] Morphic 3, Cuis, Simple Morphic and Esug's sponsoring

by StÃ©phane Ducasse

Thanks juan. You conclusion is good and I'm happy that we made it that way. Stef > Hi Folks, > > All what Stef said wrt these issues is correct. I just want to (perhaps) make some detail clearer. > > Esug agreed to sponsor Morphic 3 about one year ago. At that time I expected to have a working and usable system by the end of this year. This is not going to happen. Main reasons are: > 1) I underestimated the effort. > 2) Inflation and other issues meant I needed to make more money that I was currently making. So I had to reduce the hours I devote to volunteer work to spend them in paid work. > 3) I failed to get sponsors for this project outside the Smalltalk community (although I did try). > 4) Some of the ideas in Morphic 3 are novel enough that I need to protect them from being patented by others from, before disclosing them. I don't like software patents, so I believe the best way to do this (and get more people to know these ideas) is to submit a paper to a journal such as ACM Transactions on Graphics. This will obviously require additional time. > So work on Morphic 3 is not stopped, but right now it is paused. > > It seemed to me that instead of just telling Esug "I'm sorry, but you'll get nothing by the date I promised results", I could do a more practical, down to earth contribution to the Smalltalk community in return for Esug's support. I believe that many in the Pharo community share my opinion that the current Morphic implementation is obfuscated, that it is too hard to write applications with it, and that it is too hard to fix bugs and evolve it. > > The Morphic implementation in Cuis is the main result of many (I guess about 6) years of part time work on simplifying the system. I think it could be of great value for Pharo, and an enabler for evolution. So, I did a request to Esug, to deliver this, naming it "SimpleMorphic", ready to run in Pharo, instead of Morphic 3. Esug approved it, and I thank them for this. SimpleMorphic is the result of this. I started by extracting the Morphic in Cuis. This was not trivial, as I had to think carefully where to draw the line between what I'd migrate to Pharo and what I'd use from Pharo. Then I adapted it to some differences between Cuis and Pharo, and also tweaked Pharo to enable using alternative UIs. I worked about 80 hours on this and delivered this week. > > After all this, I think it is fair to say that Esug sponsored Cuis as SimpleMorphic is part of it. I hope this helps and does not add confusion. > > Cheers, > Juan Vuletich >

Nov. 7, 2010

Re: [Pharo-project] SmalltalkImage

by StÃ©phane Ducasse

SmalltalkImage current instVarAt: #globals put: SystemDictionary new Something like that. ? On Nov 7, 2010, at 2:46 AM, Benjamin wrote: > Hi guys, > > I wonder how SmalltalkImage create the Smalltalk instance. > > Can someone explain me that ? > > > > > Thank you > > Ben >

Nov. 7, 2010

Re: [Pharo-project] The next milestone reached!

by StÃ©phane Ducasse

Pavel can you point our such initializations problems so that we fix them. Stef On Nov 6, 2010, at 11:19 PM, Pavel Krivanek wrote: > Hi Hilaire, > > I do not think that PharoCore image generated from PharoKernel will be > better for your needs. It is not significantly smaller, it has almost > the same code base and bugs are common because the original image did > a lot of forgotten ad hoc initializations. > > -- Pavel > > On Sat, Nov 6, 2010 at 7:44 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com> wrote: >> Pavel, I would like to be your first user. I am planing for a DrGeo >> release in the coming weeks, so I will definitely take a look. >> >> >> Hilaire >> >> Le 06/11/2010 12:47, Pavel Krivanek a Ã©crit : >>> This screenshot is more representative ;-) >>> >>> -- Pavel >>> >>> On Sat, Nov 6, 2010 at 12:12 PM, Pavel Krivanek >>> <pavel.krivanek(a)gmail.com> wrote: >>>> Hi all, >>>> >>>> I successfully loaded the the rest of PharoCore packages into the >>>> PharoKernel. The Morphic initialization works too. See the attached >>>> screenshot. I will publish the scripts later today. >>>> >>>> Cheers, >>>> -- Pavel >>>> >> >> >> -- >> Dr. Geo, to discover geometry on Linux, Windows, MAC and XO >> http://community.ofset.org/index.php/DrGeo >> >> >> >

Nov. 7, 2010

[Pharo-project] About SimpleMorphic

by Juan Vuletich

Hi Folks, I apologize for not answering the original messages properly, I had mail deliver disabled, so I can't. I have enabled it, so I'll answer properly from now on. To Hillarie: If you don't use Polymorph, but want to build your own Morphs from scratch, SimpleMorphic is simpler, easier to understand, tweak and fix. To Doru: Let's do a comparison: Size of 4 core classes (Morph, MorphExtension, PasteUpMorph and WorldState) Pharo / Squeak / Cuis totalIvars: 39 / 46 / 26 totalClassVars: 15 / 10 / 5 totalInstMethods: 1170 / 1764 / 663 totalClassMethods: 55 / 71 / 16 Size of the whole Morph hierarchy Pharo / Squeak / Cuis totalClasses: 197 / 331 / 58 totalIvars: 649 / 1063 / 257 totalClassVars: 54 / 138 / 28 totalInstMethods: 6651 / 9186 / 2115 totalClassMethods: 303 / 858 / 127 SimpleMorphic is much smaller. Core classes are simpler and easier to understand, fix and extend. The most important part is that this is not blind removal of unused code. A lot of the functionality has been redesigned to make it simpler, and the removal was done with great care to result in a consistent system. This work started in 2004, so we're talking of about 6 years of careful work. All this means that SimpleMorphic does not support all the features that Pharo or Squeak might support. Please use the browsers and other tools in Cuis to check what it indeed can do. Talking about complexity, let's take for example, morph layout. This is started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic. In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in: (149), #layoutProportionallyIn: (10), #computeCellArrangement:in:horizontal:target: (87), #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31), #computeCellSizes:in:horizontal: (30), #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in: (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target: (70). The numbers in parenthesis are the sum of the lines of code of the implementors. Total lines of code for layout (taking only these most important methods) is 714. I doubt there are many people who really understand all of this code. In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10), #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45. I believe any smalltalker could understand these in just minutes. I hope this makes makes it clearer to you what SimpleMorphic is. Cheers, Juan Vuletich

Nov. 7, 2010