- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3971 in pharo: OBSystemBrowserAdaptor does not correctly find classes

by pharo＠googlecode.com

Updates: Status: Invalid Comment #1 on issue 3971 by renggli: OBSystemBrowserAdaptor does not correctly find classes http://code.google.com/p/pharo/issues/detail?id=3971 Sure, it contains it as a sub-string: A*b*stractA*u*to*t*est*T*estL*o*ngRu*n* This is a feature.

April 8, 2011

Re: [Pharo-project] Initial PetitC parser

by Ricardo Moran

On Fri, Apr 8, 2011 at 12:37 AM, Javier PimÃ¡s <elpochodelagente(a)gmail.com>wrote: > Hi, > I took some time to start developing a C parser with PetitParser. I > used the slides of the smalltalk school, they were pretty useful, and after > some hours I have a very basic tokens scanner. The idea of this work is to > be able to feed the parser with C headers and automagically get the C > bindings done in smalltalk. > > Hi Javier, That's a great project and I'm highly interested in it. I'm not experienced in PetitParser so I won't be a lot of help, but I'll give it a try. > Now I have to actually start doing something with the scanned code. How > should I do that, all in the same class? What if I want to generate bindings > for different kinds of FFIs? Other question, how should I handle > preprocessing? (now there isn't any kind of preprocessing) > Maybe you already thought of this but what if you make your parser build some simple C AST and then you make specific visitors for each kind of FFI? Cheers Richo > > You can see the code, download it and commit improvements to the repo at > www.squeaksource.com/Bindings > > Anybody who is interested is welcomed to help in the development! > > Regards, > Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires >

April 8, 2011

Re: [Pharo-project] Initial PetitC parser

by Javier PimÃ¡s

by the way, the grammar is based on http://www.quut.com/c/ANSI-C-grammar-l-1998.html <http://www.quut.com/c/ANSI-C-grammar-l-1998.htm>and http://www.quut.com/c/ANSI-C-grammar-y.html I'd be very grateful if you contribute to cover the full extent of it! On Fri, Apr 8, 2011 at 12:37 AM, Javier PimÃ¡s <elpochodelagente(a)gmail.com>wrote: > Hi, > I took some time to start developing a C parser with PetitParser. I > used the slides of the smalltalk school, they were pretty useful, and after > some hours I have a very basic tokens scanner. The idea of this work is to > be able to feed the parser with C headers and automagically get the C > bindings done in smalltalk. > > Now I have to actually start doing something with the scanned code. How > should I do that, all in the same class? What if I want to generate bindings > for different kinds of FFIs? Other question, how should I handle > preprocessing? (now there isn't any kind of preprocessing) > > You can see the code, download it and commit improvements to the repo at > www.squeaksource.com/Bindings > > Anybody who is interested is welcomed to help in the development! > > Regards, > Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > -- Javier PimÃ¡s Ciudad de Buenos Aires

April 8, 2011

[Pharo-project] Initial PetitC parser

by Javier PimÃ¡s

Hi, I took some time to start developing a C parser with PetitParser. I used the slides of the smalltalk school, they were pretty useful, and after some hours I have a very basic tokens scanner. The idea of this work is to be able to feed the parser with C headers and automagically get the C bindings done in smalltalk. Now I have to actually start doing something with the scanned code. How should I do that, all in the same class? What if I want to generate bindings for different kinds of FFIs? Other question, how should I handle preprocessing? (now there isn't any kind of preprocessing) You can see the code, download it and commit improvements to the repo at www.squeaksource.com/Bindings Anybody who is interested is welcomed to help in the development! Regards, Javier. -- Javier PimÃ¡s Ciudad de Buenos Aires

April 8, 2011

Re: [Pharo-project] [COTDC] 43 - TextStyleFontSelectorDialogWindow

by HwaJong Oh

Example code your provided in comment reminds me of Google Sketchup Ruby API. http://code.google.com/apis/sketchup/docs/ourdoc/face.html UITheme >> newFontSelector used by ComposableMorph, ExampleBuilderMorph, MorphicUIManager, StandardWindow,TEasilyThemed classes. I'm not sure it can be removed. -- View this message in context: http://forum.world.st/COTDC-43-TextStyleFontSelectorDialogWindow-tp3431614p… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 8, 2011

Re: [Pharo-project] A step toward reducing complexity

by Tudor Girba

Hi, I refactored the GLMUITheme to inherit from UITheme. I followed your steps and fixed a number of other issues. There are still a couple of places to fix (like a remaining orange highlight of the text area), but it is pretty much working. Cheers, Doru On 25 Mar 2011, at 09:08, Tudor Girba wrote: > Thanks, Doug. This was on my to do list for a long time. > > Just a note: GLMUITheme is part of Glamour. Please do not fork it in Pharo and integrate fixes there because then it will just get messy. I will integrate it in Glamour. > > If you want to evolve it in the context of Pharo, you should rename it an put it in a different package (this would probably make sense anyway). > > Cheers, > Doru > > > On 25 Mar 2011, at 08:44, StÃ©phane Ducasse wrote: > >> Thanks. >> May be the windowActiveDropShadowStyle could be just added to the UITheme class? >> >> Open a bug entry and attach code or slice there so that >> - have a look >> - not forget to integrate the fix. >> >> Stef >> >>> Reduce the complexity of user interface themes >>> >>> In general, user interface themes should inherit directly from UITheme, not >>> from a chain of themes. When you have a chain of themes, you are stuck with >>> the intermediate themes, whether you need/use them or not. Consider >>> GLMUITheme. Currently it is under UIThemeWatery2, which is under >>> UIThemeWatery, which is under UITheme. >>> >>> Some characteristics inherited from the chain are missing, but in principal, >>> GLMUITheme can be moved directly under UITheme with just 3 changes. >>> >>> 1. Add an instanceVariable 'windowActiveDropShadowStyle' >>> >>> UITheme subclass: #GLMUITheme >>> instanceVariableNames: 'windowActiveDropShadowStyle' >>> classVariableNames: '' >>> poolDictionaries: '' >>> category: 'Glamour-Morphic-Theme' >>> >>> 2. Add a class method >>> >>> isAbstract >>> "Answer whether the receiver is considered to be abstract." >>> ^false >>> >>> 3. Add an instance method >>> >>> windowActiveDropShadowStyle: anObject >>> "Set the value of windowActiveDropShadowStyle" >>> windowActiveDropShadowStyle := anObject >>> >>> >>> Because GLMOrangeUITheme inherits these changes, it does not need >>> modification. >>> >>> >>> -- >>> View this message in context: http://forum.world.st/A-step-toward-reducing-complexity-tp3404504p3404504.h… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >> >> > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > -- www.tudorgirba.com "Reasonable is what we are accustomed with."

April 7, 2011

Re: [Pharo-project] Issue 3969 in pharo: MorphTreeMorph performance

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #3 on issue 3969 by marcus.d...(a)gmail.com: MorphTreeMorph performance http://code.google.com/p/pharo/issues/detail?id=3969 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 3430 in pharo: SystemProgressMorph possible enh

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #1 on issue 3430 by marcus.d...(a)gmail.com: SystemProgressMorph possible enh http://code.google.com/p/pharo/issues/detail?id=3430 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 3346 in pharo: Socket bug fixes

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #1 on issue 3346 by marcus.d...(a)gmail.com: Socket bug fixes http://code.google.com/p/pharo/issues/detail?id=3346 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 3135 in pharo: Monticello Browser does not answer to key position

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #2 on issue 3135 by marcus.d...(a)gmail.com: Monticello Browser does not answer to key position http://code.google.com/p/pharo/issues/detail?id=3135 (No comment was entered for this change.)

April 7, 2011