- Pharo-dev - lists.pharo.org

[Pharo-project] How to have a package specific setting keyword (was Re: Draft chapter on Settings Framework for PBE2 now online )

by Alain Plantec

Hi Hernan, I've checked with #12272 and it works even with this version. but you must extends SettingTreeBuilder with your own pragma keyword method (with the <settingPragmaProcessor>), not SettingTree. A example package is attached. open the settingBrowser with: SettingBrowser browse: #('blobsettings') hope it helps. Alain Le 21/06/2011 01:59, HernÃ¡n Morales Durand a Ã©crit : > Hi Alain, > > Thank you for the nice answer. One thing that you may like to adapt is > the hard-coded reference in #nodeList, because is preventing in > #buildPragma: to understand #myAppSettings, after evaluating > SettingBrowser browse: #('myAppSettings' ) > > SettingTree>>nodeList > | builder | > ^ nodeList > ifNil: [ > builder := SettingTreeBuilder new. > self pragmasDo: [:p | builder buildPragma: p]. > nodeList := builder nodeList. > nodeList do: [:n | n model: self]. > self checkForUnknownParent. > self checkForUnknownTarget. > self nodeList] > > or maybe there is another way to specify my own tree builder? > (using Pharo1.2beta #12272) > > 2011/6/20 Alain Plantec<alain.plantec(a)yahoo.com>: >> Hi Hernan, >> >> First you have to declare your own keyword. >> To do that, extend SettingTreeBuilder for your application by >> adding a #myAppSettings method. >> >> SettingTreeBuilder>>myAppSettings >> <settingPragmaProcessor> >> "Process a<myAppSettings> pragma" >> currentPragma methodClass theNonMetaClass perform: currentPragma selector >> with: self. >> >> >> Then you can use<myAppSettings> as you do with<systemsettings> for the >> settings declarations. >> In order to open the SettingBrowser, just indicate the keywords you want: >> (SettingBrowser browse: #('myAppSettings' 'systemsettings')) >> or >> (SettingBrowser browse: #('myAppSettings' )) >> >> I will update the settings chapter with that. >> Cheers >> Alain >> >> >> >> Le 20/06/2011 00:18, HernÃ¡n Morales Durand a Ã©crit : >>> Hi Oscar, >>> >>> I would like to build my own application settings in a separated >>> Settings browser, can I use<myAppSettings> like the<systemsettings> >>> pragma? any example code how to do it? >>> >>> Cheers, >>> >>> 2011/2/8 Oscar Nierstrasz<oscar.nierstrasz(a)gmail.com>: >>>> Hi Folks, >>>> >>>> There is now a draft chapter on the Settings Framework for "Pharo by >>>> Example 2" available for review: >>>> >>>> https://gforge.inria.fr/frs/download.php/28243/Settings.pdf >>>> >>>> http://pharobyexample.org/ >>>> >>>> Cheers, >>>> - on

June 21, 2011

Re: [Pharo-project] initial Spoon modularization

by Craig Latta

Hi Ron-- Thanks! Yeah, this is a system that can serve a website for doing module discovery and management, appear as a filesystem through WebDAV, keep track of changes, and serve modules to other systems. Currently it's 300k, but there's another shrinking pass left. -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547

June 21, 2011

[Pharo-project] INRIAGForge Account was: [ Zinc Updates ]

by Sven Van Caekenberghe

On 20 Jun 2011, at 15:24, StÃ©phane Ducasse wrote: > Can you start to create an account on gforge.inria.fr (RMOD team) ? > And let me know. OK, I made an account with username 'svc'. Sven

June 21, 2011

[Pharo-project] Gofer dependent on Zinc

by Pavel Krivanek

Hi, I would like to point out to one new Pharo feature that is a potential issue. The package Zinc-Patch-HTTPSocket stole the ownership of several methods from the class HTTPSocket. That means that now this package doesn't act as an overlay patch. The consequences are not fatal. It only means that now the Gofer package that uses this methods is dependent on Zinc and it makes a headless Gofer image a little bit larger and less clean. Cheers, -- Pavel

June 21, 2011

[Pharo-project] [update 1.3] #13270

by Marcus Denker

13270 ----- Issue 4089: ScriptManager has the same icon as Transcript http://code.google.com/p/pharo/issues/detail?id=4089 Issue 4427: FlatMessageListBrowser add browse users http://code.google.com/p/pharo/issues/detail?id=4427 Issue 4328: Transcript: 5) Update problem when evaluating 1 to: ... http://code.google.com/p/pharo/issues/detail?id=4328 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 21, 2011

Re: [Pharo-project] roadmap for 1.4

by Dale Henrichs

There are two things that need to be done with MetacelloBrowser before it is really ready... 1) is to clean up the menu organization ... there is a purpose for each of the menu items, but some work needs to be done to reorganize the panes/operations/windows so that not so many menu items are needed ... 2) is that the configuration creation logic is not very intuitive ... a wizard of sorts needs to be put together for simplifying the creation of configurations ... At the moment there is an OB and Morphic implementation for the MetacelloBrowser, but you can't do wizards in OB, so the wizard needs to be done in Morphic and that means that there won't be an OB mapping ... GemStone/GemTools is based upon OB and I really need to have a MetacelloBrowser that works in GemStone ... My solution has been to create tODE. tODE is a javascript/web-browser based development environment that is implemented on top of Seaside and I am currently in the process of building the MetacelloBrowser functionality in tODE... The upshot is that I am not actively developing the morphic interface for MetacelloBrowser ... about 80% of the code is shared between the morphic variant and the tODE variant of the MetacelloBrowser ... ...There are three things that need to be done:)... 3) performance improvement... I will be tackling the performance issues as they are smack dab in the middle of the shared code, but someone with Morphic experience needs to tackle the usability and wizard issues... Dale ----- Original Message ----- | From: "Guillermo Polito" <guillermopolito(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr, metacello(a)googlegroups.com | Sent: Sunday, June 19, 2011 7:08:25 AM | Subject: Re: [Pharo-project] roadmap for 1.4 | | What if we try integrating MetacelloBrowser in that | PharoCoreWithVitamins? That can solve our one-click-download | problem! | | Dale, Alex, how's the state of MetacelloBrowser? I've just downloaded | it in 1.3 and it works. I got ashamed by the amount of options in | the menu, but I managed to find how to load a configuration and a | version, jeje. | | Cheers, | Guille | | | On Sun, Jun 19, 2011 at 7:02 AM, StÃ©phane Ducasse < | stephane.ducasse(a)inria.fr > wrote: | | | | | On Jun 19, 2011, at 7:27 AM, Pavel Krivanek wrote: | | > Hi, | > | > I think that the best idea is to have one image for the system | > developers and end-users (for example, I almost never used full | > Pharo so it lost one tester). On the other hand we should continue | > with the modularization to allow to generate headless kernel | > image, gopher image, basic morphic image etc. on the request with | > bootstrapping. To have smallest possible image is not the main | > goal of the effort around PharoKernel. The main goal is to have | > beauty modular system where all dependencies all described well | > and packages can be easily loaded and unloaded. The buildserver | > can generate all the set of images for special purposes so it will | > be more natural then now when we have two main images. | | Yes yes yes but :) we should have a set of tools that are working | together and we should not be responsible of making sure that all | the possible combination work. | I would like to get a process (as I mentioned in the other mail) | seed + MetacelloSpec + modification => seed' + MetacelloSpec' | | and that we are able to build hudson that takes | aSeed + a spec | => run all the tests + run all the quality check | | Right now we have | seed + list of package + modification => seed' + list of package' | | and we get in trouble when we modify seed parts that influence | external package | | so what we want is to have | seed + metacello = the minimal tools that we need to be efficient | modifying seed | for me | OB Engine | Shout | O/Ecompletion | | Stef | | | | | | > | > -- Pavel | > | > | > | > 18.6.2011 v 22:29, Guillermo Polito < guillermopolito(a)gmail.com >: | > | >> Hi Stef! | >> | >> do you mean integrating all them in the Core? Or maybe follow | >> Markus' idea of having just one image? Maybe that's an important | >> discussion to have too :). | >> I can give a hand for the repository stuff. Should we replicate | >> repositories + metacello configs in order to be able to freeze | >> them, isn't it? | >> | >> Guille | >> | >> On Sat, Jun 18, 2011 at 9:59 AM, StÃ©phane Ducasse < | >> stephane.ducasse(a)inria.fr > wrote: | >> Hi guys | >> | >> here is a kind of dump of roadmap for 1.4 first level is to make | >> sure that we have only one single image. | >> | >> - load FileSystem | >> -> so that we can start to integrate and improve the fileSystem | >> API | >> | >> - Load shout, Ocompletion, RBEngine (not OB) so that we can change | >> what should be changed for RPackage to work | >> | >> - Ring | >> -> so that we can start to integrate it | >> | >> - Fuel | >> -> so that we can deprecate SmartRefStream (there may be a problem | >> with mcz (not sure)). | >> | >> - I want Opal in 1.4 too. | >> | >> - continue to remove StringHolder hierarchy | >> | >> - Morphic improvements | >> | >> Comments are welcomed. | >> | >> Stef | >> | >> | >> | | | |

June 21, 2011

Re: [Pharo-project] Draft chapter on Settings Framework for PBE2 now online

by HernÃ¡n Morales Durand

Hi Alain, Thank you for the nice answer. One thing that you may like to adapt is the hard-coded reference in #nodeList, because is preventing in #buildPragma: to understand #myAppSettings, after evaluating SettingBrowser browse: #('myAppSettings' ) SettingTree>>nodeList | builder | ^ nodeList ifNil: [ builder := SettingTreeBuilder new. self pragmasDo: [:p | builder buildPragma: p]. nodeList := builder nodeList. nodeList do: [:n | n model: self]. self checkForUnknownParent. self checkForUnknownTarget. self nodeList] or maybe there is another way to specify my own tree builder? (using Pharo1.2beta #12272) 2011/6/20 Alain Plantec <alain.plantec(a)yahoo.com>: > Hi Hernan, > > First you have to declare your own keyword. > To do that, extend SettingTreeBuilder for your application by > adding a #myAppSettings method. > > SettingTreeBuilder>>myAppSettings > <settingPragmaProcessor> > Â Â "Process a <myAppSettings> pragma" > Â Â currentPragma methodClass theNonMetaClass perform: currentPragma selector > with: self. > > > Then you can use <myAppSettings> as you do with <systemsettings> for the > settings declarations. > In order to open the SettingBrowser, just indicate the keywords you want: > (SettingBrowser browse: #('myAppSettings' Â 'systemsettings')) > or > (SettingBrowser browse: #('myAppSettings' )) > > I will update the settings chapter with that. > Cheers > Alain > > > > Le 20/06/2011 00:18, HernÃ¡n Morales Durand a Ã©crit : >> >> Hi Oscar, >> >> I would like to build my own application settings in a separated >> Settings browser, can I use<myAppSettings> Â like the<systemsettings> >> pragma? any example code how to do it? >> >> Cheers, >> >> 2011/2/8 Oscar Nierstrasz<oscar.nierstrasz(a)gmail.com>: >>> >>> Hi Folks, >>> >>> There is now a draft chapter on the Settings Framework for "Pharo by >>> Example 2" available for review: >>> >>> https://gforge.inria.fr/frs/download.php/28243/Settings.pdf >>> >>> http://pharobyexample.org/ >>> >>> Cheers, >>> - on

June 21, 2011

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

by Dave Mason

Hi Javier, On 2011-Jun-20, at 18:51 , Javier PimÃ¡s wrote: > Hi! It's nice to hear this. As Mariano said, I started to work in > something like this some months ago, but I couldn't make something > useful yet because I don't have much free time. I can give you a > hand if you need. I don't know about OS Process, but I have some > experience with FFI, so I'll look for some examples. That would be great. FFI, Alien, and NativeBoost evidence an itch... but actual uses that depend on the code seem to be harder to find. I get the impression that many potential users have devolved to writing their own purpose-built plugins. > I also have some questions, > > - how did you implement the parser, by hand or with a framework? By hand. It doesn't handle all of C, but that part you will find in include files. > - did you implement a preprocessor or used the output of something > like CPP? I'm using CPP at the moment. The only serious downside that I see is that lots of C headers pre-date the introduction of enums into C, so constants are often #defined rather than being part of an enum. So I may end up adding a pre-processor to recover these constants. > - what about the output of the parser, do you create an AST? No, I directly build the data structures I need to generate the FFI interfaces. > On Fri, Jun 17, 2011 at 1:34 PM, Dave Mason <dmason(a)mason-rose.ca> > wrote: > I'm working on making a clean interface layer on top of FFI (and > possibly Alien and NativeBoost).

June 21, 2011

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

by Javier PimÃ¡s

Hi! It's nice to hear this. As Mariano said, I started to work in something like this some months ago, but I couldn't make something useful yet because I don't have much free time. I can give you a hand if you need. I don't know about OS Process, but I have some experience with FFI, so I'll look for some examples. I also have some questions, - how did you implement the parser, by hand or with a framework? - did you implement a preprocessor or used the output of something like CPP? - what about the output of the parser, do you create an AST? Regards, Javier On Fri, Jun 17, 2011 at 1:34 PM, Dave Mason <dmason(a)mason-rose.ca> wrote: > 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 > > -- Javier PimÃ¡s Ciudad de Buenos Aires

June 21, 2011

[Pharo-project] [ANN] Moose Suite 4.5

by Tudor Girba

We are happy to announce the Moose Suite version 4.5: http://moosetechnology.org/download This is a minor release. What is new: â¢ Important fixes in FAMIX to deal better with Java systems â¢ Better EyeSee engine for scripting visual charts â¢ Improved VerveineJ compatibility for Java parsing Have fun, The Moose Team http://moosetechnology.org

June 20, 2011