- Pharo-dev - lists.pharo.org

[Pharo-project] FFI and capturing external program input in Squeak/Pharo

by Dave Mason

I'm working on making a clean interface layer on top of FFI (and possibly Alien and NativeBoost). It will look something like: FFIParse createFFI: #System category: 'My-Category' library: 'System'. System parseSystemHeader: 'sys/resource.h'. rusage := System struct: #rusage. System getrusage: 0 with: rusage. Transcript show: 'Used '; show: rusage ru_utime tv_sec; show: '.'; show: rusage ru_utime tv_usec; show: ' seconds of user CPU time'; cr. System parseSystemHeaer: 'unistd.h'; sleep: 5. pid := System getpid I have a very compact, almost compete C header parser but I need to be able to get the output from popen("echo \"#include <unistd.h>\"|gcc -E -","r") or equivalent. The popen is easy enough to get at through FFI, but is there a way to connect either the FILE* or the file descriptor up to some ReadStream. In the worst case, I could probably use FFI to call fread(3) but is there a better way? I'd also appreciate any simple examples of using FFI, especially with ExternalStructure subclasses. Finally is there a way to get external variables such as 'extern int errno;' ? Thanks in advance! ../Dave

June 17, 2011

Re: [Pharo-project] TWM and Keymapping

by Guillermo Polito

BTW, thanks for pushing this! :) On Fri, Jun 17, 2011 at 10:57 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > > > On Fri, Jun 17, 2011 at 3:24 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Hi Guillermo, >> >> Now TWM works with ConfigurationOfKeymapping 1.8. >> >> Gofer it >> squeaksource: 'TilingWindowManager'; >> package: 'ConfigurationOfTilingWindowManager'; >> load. >> ConfigurationOfTilingWindowManager loadDevelopment. >> >> >> >> Something I want to fix: if an editor has the focus, TWM shortcuts don't >> work. >> > I've tried: >> >> TilingTWMSettings class>>buildKeyMappingSettingsOn: aBuilder >> <keymap> >> ..... >> {PasteUpMorph. SystemWindow. TextEditor. SmalltalkEditor} >> do: [:aClass| aBuilder attachShortcutCategory: #twmShortcut to: aClass ]. >> >> but no success ..... >> > > Probably the TextEditor overrides a shortcut in a non desired way... Does > it happen for every twm shortcut? We should write a testcase... > > >> >> >> >> Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> >> >> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >> Blog: http://magaloma.blogspot.com/ >> Developer group: http://cara74.seasidehosting.st >> >> >

June 17, 2011

Re: [Pharo-project] TWM and Keymapping

by Guillermo Polito

On Fri, Jun 17, 2011 at 3:24 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi Guillermo, > > Now TWM works with ConfigurationOfKeymapping 1.8. > > Gofer it > squeaksource: 'TilingWindowManager'; > package: 'ConfigurationOfTilingWindowManager'; > load. > ConfigurationOfTilingWindowManager loadDevelopment. > > > > Something I want to fix: if an editor has the focus, TWM shortcuts don't > work. > I've tried: > > TilingTWMSettings class>>buildKeyMappingSettingsOn: aBuilder > <keymap> > ..... > {PasteUpMorph. SystemWindow. TextEditor. SmalltalkEditor} > do: [:aClass| aBuilder attachShortcutCategory: #twmShortcut to: aClass ]. > > but no success ..... > Probably the TextEditor overrides a shortcut in a non desired way... Does it happen for every twm shortcut? We should write a testcase... > > > > Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > Developer group: http://cara74.seasidehosting.st > >

June 17, 2011

Re: [Pharo-project] Morphic on HTML+CSS

by Janko MivÅ¡ek

S, Igor Stasenko piÅ¡e: >>>> 2. is this a clear signal that we need to rebuild Morphic on top of >>>> HTML+CSS, to leverage all Morphic advantages and come back >>>> to bleeding edge again? >>> >>> Dan Ingalls has done it already: http://lively-kernel.org/ >> >> Lively is a project to watch and study, but Lively is JavaScript only, >> not using HTML and CSS, as far as I know. >> >> Separation of design with CSS is namely something which really raised >> the creativity fo designers on the web. This can help building better >> and nicely looking Smalltalk apps too! >> > > indeed. this separation is good. > And it would be even better if you separate HTML from the web :) You actually can. There is no need for HTML to render webpages, as Lively show nicely. Pages can be composed just from JavaScript by DOM manipulation API. Same with CSS. And even a combination is possible: JS built page, but with classical external CSS. External CSS is ideal for web designers and Lively can be actually improved visualy that way. Whic would also make it more popular, we shouldn't forget aesthetics even for academic work to be successful these days :) Best regards Janko -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

June 17, 2011

Re: [Pharo-project] MethodFinder should use pragmas

by Benjamin

(my 2 cents) So maybe it can be cool to implement a way to annotate methods ... I think we should be able to provide more information about methods/classes/packages etc like which is the corresponding class test ? is this method well written ? is this method an extension ? and even comments At some point, it was useful (and maybe the only way to do it) to put such info in source code, but maybe now we should decide not to use strings anymore to attach specific behavior (I mean, is that obvious that an extension is a category starting by * ? or that a test method's selector must begin with 'test' ? ). I know it's easier to say than to do, but I think that a system based on string is out dated today :) So let's start 1.4 and break everything :D Ben On Jun 17, 2011, at 1:40 PM, Marcus Denker wrote: > > On Jun 17, 2011, at 10:33 AM, Damien Cassou wrote: > >> I would like to have your opinion on >> http://code.google.com/p/pharo/issues/detail?id=4426 >> > > > The problem is that it looks not nice to have pragmas in all methods as part of the source code.. > Imagine we do that for 5 different things (e.g. Slint), than the source is smaller than the annotations > and readability suffers... > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

June 17, 2011

Re: [Pharo-project] MethodFinder should use pragmas

by Marcus Denker

On Jun 17, 2011, at 10:33 AM, Damien Cassou wrote: > I would like to have your opinion on > http://code.google.com/p/pharo/issues/detail?id=4426 > The problem is that it looks not nice to have pragmas in all methods as part of the source code.. Imagine we do that for 5 different things (e.g. Slint), than the source is smaller than the annotations and readability suffers... -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 17, 2011

[Pharo-project] MethodFinder should use pragmas

by Damien Cassou

I would like to have your opinion on http://code.google.com/p/pharo/issues/detail?id=4426 Thanks -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 17, 2011

Re: [Pharo-project] Fuel - a fast object deployment tool

by Martin Dias

Hi Eliot, I am very happy to read your mail. On Wed, Jun 15, 2011 at 3:29 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi Martin & Mariano, > > regarding filtering. Yesterday my colleague Yaron and I successfully > finished our port of Fuel to Newspeak and are successfully using it to save > and restore our data sets; thank you, its a cool framework. We had to > implement two extensions, the first of which the ability to save and restore > Newspeak classes, which is complex because these are instantiated classes > inside instantiated Newspeak modules, not static Smalltalk classes in the > Smalltalk dictionary. The second extension is the ability to map specific > objects to nil, to prune objects on the way out. I want to discuss this > latter extension. > > In our data set we have a set of references to objects that are logically > not persistent and hence not to be saved. I'm sure that this will be a > common case. The requirement is for the pickling system to prune certain > objects, typically by arranging that when an object graph is pickled, > references to the pruned objects are replaced by references to nil. One way > of doing this is as described below, by specifiying per-class lists of > instance variables whose referents shoudl not be saved. But this can be > clumsy; there may be references to objects one wants to prune from e.g. more > than one class, in which case one may have to provide multiple lists of the > relevant inst vars; there may be references to objects one wants to prune > from e.g. collections (e.g. sets and dictionaries) in which case the > instance variable list approach just doesn't work. > > Here are two more general schemes. VFirst, most directly, Fuel could > provide two filters, implemented in the default mapper, or the core > analyser. One is a set of classes whose instances are not to be saved. Any > reference to an instance of a class in the toBePrunedClasses set is saved as > nil. The other is a set of instances that are not to be saved, and also any > reference to an instance in the toBePruned set is saved as nil. Why have > both? It can be convenient and efficient to filter by class (in our case we > had many instances of a specific class, all of which should be filtered, and > finding them could be time consuming), but filtering by class can be too > inflexible, there may indeed be specific instances to exclude (thing for > example of part of the object graph that functions as a cache; pruning the > specific objects in the cache is the right thing to do; pruning all > instances of classes whose instances exist in the cache may prune too much). > > As an example here's how we implemented pruning. Our system is called > Glue, and we start with a mapper for Glue objects, FLGlueMapper: > > FLMapper subclass: #FLGlueMapper > instanceVariableNames: 'prunedObjectClasses newspeakClassesCluster > modelClasses' > classVariableNames: '' > poolDictionaries: '' > category: 'Fuel-Core-Mappers' > > It accepts newspeak objects and filters instances in the > prunedObjectsClasses set, and as a side-effect collects certain classes that > we need in a manifest: > > FLGlueMapper>>accepts: anObject > "Tells if the received object is handled by this analyzer. We want to > hand-off > instantiated Newspeak classes to the newspeakClassesCluster, and we want > to record other model classes. We want to filter-out instances of any > class > in prunedObjectClasses." > ^anObject isBehavior > ifTrue: > [(self isInstantiatedNewspeakClass: anObject) > ifTrue: [true] > ifFalse: > [(anObject inheritsFrom: GlueDataObject) ifTrue: > [modelClasses add: anObject]. > false]] > ifFalse: > [prunedObjectClasses includes: anObject class] > > It prunes by mapping instances of the prunedObjectClasses to a special > cluster. It can do this in visitObject: since any newspeak objects it is > accepting will be visited in its visitClassOrTrait: method (i.e. it's > implicit that all arguments to visitObjects: are instances of the > prunedObjectsClasses set). > > FLGlueMapper>>visitObject: anObject > > analyzer > mapAndTrace: anObject > to: FLPrunedObjectsCluster instance > into: analyzer clustersWithBaselevelObjects > > FLPrunedObjectsCluster is a specialization of the nil,true,false cluster > that maps its objects to nil: > > FLNilTrueFalseCluster subclass: #FLPrunedObjectsCluster > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'Fuel-Core-Clusters' > > FLPrunedObjectsCluster >>serialize: aPrunedObject on: aWriteStream > > super serialize: nil on: aWriteStream > > > So this would generalize by the analyser having an e.g. FLPruningMapper as > the first mapper, and this having a prunedObjects and a priunedObjectClasses > set and going something like this: > > FLPruningMapper>>accepts: anObject > ^(prunedObjects includes: anObject) or: [prunedObjectClasses includes: > anObject class] > > FLPruningMapper >>visitObject: anObject > analyzer > mapAndTrace: anObject > to: FLPrunedObjectsCluster instance > into: analyzer clustersWithBaselevelObjects > > and then one would provide accessors in FLSerialzer and/or FLAnalyser to > add objects and classes to the prunedObjects and prunedObjectClasses set. > > For efficiency one could arrange that the FLPruningMapper was not added to > the sequence of mappers unless and until objects or classes were added > to the prunedObjects and prunedObjectClasses set. > > Excellent. I love the botanical metaphor of pruning! Of course we can include FLPruningMapper and FLPrunedObjectsCluster in Fuel. We are also interested in pruning objects but not necessarily replacing them by nil, but for another user defined objects. For example proxies. We can extend the pruning stuff for doing that. > I think both Yaron and I feel the Fuel framework is comprehensible and > flexible. We enjoyed using it and while we took two passes at coming up > with the pruning scheme we liked (our first was based on not serializing > specific ins vars and was much more complex than our second, based on > pruning instances of specific classes) we got there quickly and will very > little frustration along the way. Thank you very much. > :-) thank you! > Finally, a couple of things. First, it may be more flexible to implement > fuelCluster as fuelClusterIn: anFLAnalyser so that if one is trying to > override certain parts of the mapping framework an implementation can access > the analyser to find existing clusters, e.g. > > MyClass>>fuelClusterIn: anFLAnalyser > ^self shouldBeInASpecialCluster > ifTrue: [anFLAnalyser clusterWithId: MySpecialCluster id] > ifFalse: [super fuelClusterIn: anFLAnalyser] > > This makes it easier to find a specific unique cluster to handle a group of > objects specially. > I can't imagine a concrete example but I see that it is more flexible... the cluster obtained via double dispatch can be anything polymorphic with MySpecialCluster... that's the point? > Lastly, the class-side cluster ids are a bit of a pain. It would be nice > to know a) are these byte values or general integer values, i.e. can there > be more than 256 types of cluster?, and b) is there any meaning to the ids? > For example, are clusters ordered by id, or is this just an integer tag? > Also, some class-side code to assign an unused id would be nice. > > You might think of virtualizing the id scheme. For example, if FLCluster > maintained a weak array of all its subclasses then the id of a cluster could > be the index in the array, and the array could be cleaned up occasionally. > Then each fuel serialization could start with the list of cluster class > names and ids, so that specific values of ids are specific to a particular > serialization. > I do agree, these ids are an heritage from the first prototypes of fuel, they should be revised. a) yes, it is encoded in only one byte; b) just an integer tag, the only purpose of the id was for decoding fast: read a byte and then look in a dictionary for the corresponding cluster instance. We could even store the cluster class name but that's inefficient. Virtualizing the id scheme is a good idea. Much more elegant and extensible. The current mechanism not only limits the number of possible clusters, but also "user defined" extensions can collide, for example if your Glue cluster id is the same of the Moose cluster id. I added an issue in our tracker. If it makes sense, maybe the weak array you suggest can be also used to avoid instantiating lots of FLObjectCluster like we are doing in Object: fuelCluster ^ self class isVariable ifTrue: [ FLVariableObjectCluster for: self class ] ifFalse: [ FLFixedObjectCluster for: self class ] the second time you send fuelCluster to an object, it can reuse the cluster instance. > again thanks for a great framework. > Thanks for your words and the feedback. Is Glue published somewhere? regards Martin > best, > Eliot > > > On Mon, Jun 13, 2011 at 10:16 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Thu, Jun 9, 2011 at 3:35 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: >> >>> Hi Martin and Mariano, >>> >>> a couple of questions. What's the right way to exclude certain >>> objects from the serialization? Is there a way of excluding certain inst >>> vars from certain objects? >>> >>> >> >> Eliot and the rest....Martin implemented this feature in >> Fuel-MartinDias.258. For the moment, we decided to put >> #fuelIgnoredInstanceVariableNames at class side. >> >> Behavior >> fuelIgnoredInstanceVariableNames >> "Indicates which variables have to be ignored during serialization." >> >> ^#() >> >> >> MyClass class >> fuelIgnoredInstanceVariableNames >> ^ #('instVar1') >> >> >> The impact in speed is nothing, so this is good. Now....we were thinking >> if it is common to need that 2 different instances of the same class need >> different instVars to ignore. Is this common ? do you usually need this ? >> We checked in SIXX and it is at instance side. Java uses the prefix >> 'transient' so it is at class side... >> >> thanks >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >

June 17, 2011

[Pharo-project] [update 1.4] #14002

by Marcus Denker

For testing the 1.4 infrastructure.... 14002 ----- - remove ToolBuilder -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 17, 2011

[Pharo-project] TWM and Keymapping

by laurent laffont

Hi Guillermo, Now TWM works with ConfigurationOfKeymapping 1.8. Gofer it squeaksource: 'TilingWindowManager'; package: 'ConfigurationOfTilingWindowManager'; load. ConfigurationOfTilingWindowManager loadDevelopment. Something I want to fix: if an editor has the focus, TWM shortcuts don't work. I've tried: TilingTWMSettings class>>buildKeyMappingSettingsOn: aBuilder <keymap> ..... {PasteUpMorph. SystemWindow. TextEditor. SmalltalkEditor} do: [:aClass| aBuilder attachShortcutCategory: #twmShortcut to: aClass ]. but no success ..... Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

June 17, 2011