January 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14277
by stephane ducasse Jan. 2, 2012

Jan. 2, 2012

14277 ----- - Issue 5143: Replacing Monitor with Semaphore in Announcer. Thanks Igor Stasenko and StÃ©phane Ducasse. http://code.google.com/p/pharo/issues/detail?id=5143 - Issue 5140: Some cleanup of unused (but defined) stuff. Thanks Igor Stasenko and StÃ©phane Ducasse. http://code.google.com/p/pharo/issues/detail?id=5140 - Issue 5138: Remove TextConstants from Array. Thanks Igor Stasenko and StÃ©phane Ducasse. http://code.google.com/p/pharo/issues/detail?id=5138 - Issue 5134: Comment of Collection>>#reduce: http://code.google.com/p/pharo/issues/detail?id=5134 - Issue 5098: Settings browser wants to repeatedly safe changes. Thanks Alain Plantec http://code.google.com/p/pharo/issues/detail?id=5098 - Issue 5098: Settings browser wants to repeatedly safe changes. Thanks Alain Plantec http://code.google.com/p/pharo/issues/detail?id=5098 - Issue 5099: Regexp button in settings browser is slow. Thanks Alain Plantec http://code.google.com/p/pharo/issues/detail?id=5099 Stef

1 0

[Pharo-project] Experience with Monitor
by StÃ©phane Ducasse Jan. 2, 2012

Jan. 2, 2012

I remember reading somewhere that Monitor was broken in Pharo/Squeak? I do not remember where. Does anybody have experience with bad monitor behavior? Because we got some bad experience with Monitor. THe funny part is that now doing self inform: freezes to death our image. Stef

2 2

[Pharo-project] [ANN] Aida 6.4 Christmas Edition released
by Janko MivÅ¡ek Jan. 2, 2012

Jan. 2, 2012

Dear Smalltalkers, Well, Christmas is over but to keep with a tradition here is a new Aida 6.4 on Squeak/Pharo and VisualWorks, as a present for Smalltalk community in New Year :) This one is mostly a maintenance release with two new features: * image backup before hourly snapshot * event handling: WebElement #on: anEventSymbol do: aBlock Enhancements: * Widget simplifications and enhancements * form support now works in all possible combinations * Widget examples added to demos More in Release notes: http://www.aidaweb.si/release-notes-6.4 The easiest way to Aida is One-Click Pharo image accessible from: http://www.aidaweb.si/download If you want to load by yourself: on Pharo it is really simple to load, just evaluate this script: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfAida'; load. (Smalltalk at: #ConfigurationOfAida) load. Then simply open http://localhost:8888 . Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

1 0

Re: [Pharo-project] About announcements
by Henrik Sperre Johansen Jan. 2, 2012

Jan. 2, 2012

On 02.01.2012 15:50, Henrik Sperre Johansen wrote: > On 02.01.2012 14:45, Igor Stasenko wrote: >> On 2 January 2012 10:42, Lukas Renggli<renggli(a)gmail.com> wrote: >> >>> 6. It wraps each announcement delivery into a curtailed block. It does >>> that even for those that are never actually announced. >>> >> yeah, this can be optimized > With subs parameter a sequenceable collection, it could be made nearly > non-existant by iterating manually rather than through do:, moving > ifCurtailed to the outer scope. (resuming from index rather than a > copy after failed delivery). > Code would be uglier though. By "nearly non-existant", I meant you pay the overhead once per delivery rather than once per subscriber. It's still an overhead when you have a large number of deliveries to a few subscribers. >> 5. It iterates over all announcements, it doesn't even try to group >> announcements of the same kind. >> > it is pointless to group them, and makes no real difference. Forgot to comment this, I partly agree with both really. Of course it is not pointless to group them, algorithmically speaking. Is the scale at which it matters a usual occurance? Don't think so. Do you fix your announcement lookup by doing so? Yes. Is that necessarily a bad thing? I'm not sure. IIRC, it was one of the discussions Igor "won" (plus, it was simpler to mess about with) :) Cheers, Henry

1 0

[Pharo-project] Image input sensors blocked
by Janko MivÅ¡ek Jan. 2, 2012

Jan. 2, 2012

Hi guys, There is opportunity for someone of you to finally catch this bug! My image is blocked again, but Aida is still working and my backdoor too :) So, I can run any code on image. 'Sensor startUp' didn't help, what can yet try? Last action was OSProcess related, can this be a problem, some sempahore related stuff? Even better, contact me privately to get access to this image via web and debug it by yourself. Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

4 6

[Pharo-project] string hash collisions?
by Philippe Marschall Jan. 2, 2012

Jan. 2, 2012

Hi As you probably noted string hash collisions are all the rage these days [1]. Has anybody looked into whether this applies to Pharo as well? [1] http://events.ccc.de/congress/2011/Fahrplan/events/4680.en.html Cheers Philippe

4 6

Re: [Pharo-project] glamour and pharo
by Stephan Eggermont Jan. 1, 2012

Jan. 1, 2012

There are a number of separate problems here, I think. Mixing them up makes the situation a bit complex. I'll try separating them here. At what abstraction level should the basic tools be build. From my point of view, Glamour provides the right level. It is very easy to build browsers and it is easy to keep them maintainable. When the underlying stack is going to be replaced it makes sense to have an abstraction layer that is is easy to implement on both the old and the new stack. The alternatives (Morphic, PolyMorph, OmniBrowser, ToolBuilder) are much less accessible. OmniBrowser looks much more comprehensive, but I don't feel qualified to comment on its usability as abstraction layer. I have taken a look at creating a google issue browser with Glamour (before ssl support) and think the committer workflow should be able to be improved with a few specialized Glamour browsers. But my opinion does not matter so much. That decision should be taken by the people maintaining the core of Pharo. Does Glamour provide enough functionality to build a whole tool chain? The focus of Glamour is on navigation in a single window, the language for updating and editing is limited. Drag-and-drop support is missing. Should the programming style of Glamour be the style to build basic tools in Pharo? Would it be better to use something more similar to the Seaside canvas style? The behavior change based on the number of block parameters is very powerful but imho also confusing. On the other hand I'm pretty sure HelpBrowser initWindow is worse than the equivalent Glamour code would be. At the moment the modularization of Pharo is not yet good enough. It is not easy enough to (de)compose images, so the maintainers need to have in the core image code to create user interfaces (web-based :) or direct). When we can create very small images and work with them using remote tools, this need will disappear. Committing to a tool chain build on top of Glamour would mean either back porting Glamour to earlier versions of Squeak/Pharo, so the new tools can replace the old ones everywhere, or breaking old tools and having to maintain them all ourselves. That is, if current maintainers agree with that. Happy new year, Stephan

1 0

[Pharo-project] seaside and pharo (was: glamour and pharo)
by Lukas Renggli Jan. 1, 2012

Jan. 1, 2012

Let's take this on the Pharo mailing list. I do think that Seaside should be considered for being part of the Pharo infrastructure. At least the Core and the basic HTML rendering (i.e., without JQuery, Magritte and Pier). And I also think your analysis is not accurate. Here is why (I apologize for the long list): 1. Seaside is quite well documented. There are two books describing it. There are a tone of examples documenting all sorts of features. There comments are not as good as they could be, but there are lots of comments. 2. It is quite well tested. This part can be improved, but the core has some 80% coverage. 3. I am not the only one that knows how to mingle with it. To give some examples, more than 30 people helped fixing some intricate bugs directly in the core (http://www.seaside.st/community/contributors) I would also mention that countless student projects are on Squeaksource. So, maybe it's not that difficult. 4. The core is quite stable since more than 10 years. There were changes, but they were mostly related to new features and bug fixes. 5. The main point of using this infrastructure is not to replace Morphic, and to empower more people to build more applications. For example, the Seaside counter has less than 5 lines of code in total (and one instance variable only). This is really tiny for the amount of things it offers (you can even step through it with a debugger). And it is highly extensible (subclassing), too. 6. It's actually not that large: the core has 152 classes, and if you consider all the other packages, helper classes and specialized frameworks (but without the example code), you get some 1162 classes. 7. But, perhaps the most important part is that there have been literally thousands of applications built on top of it. Not all of them are useful now, but they were when they were built. And it seems that people can build one quite fast without much knowledge of the web either. That is the whole point of this infrastructure. Esteban even used it for building commercial applications. I built a couple, too. The whole of Pier (SmallWiki) is now using this infrastructure, too. I am not saying that Seaside is perfect. There are quite a couple of things I would like to enhance (for example, the AJAX ideas from Reef, or the components from ExtJS), but it has proved to be quite solid until now. So, before dismissing Seaside, perhaps it would be useful to actually look into it. Cheers, Lukas PS: If you don't like Seaside, I might have some other additions to pharo core ready that fit as well into the template ... On 31 December 2011 17:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Let's take this on the Pharo mailing list. > > I do think that Glamour should be considered for being part of the Pharo infrastructure. At least the Core and the basic Morphic rendering (i.e., without Mondrian, EyeSee and Magritte). > > And I also think your analysis is not accurate. Here is why (I apologize for the long list): > > 1. Glamour is quite well documented. There is a chapter describing it. There are a tone of examples documenting all sorts of features. There comments are not as good as they could be, but there are comments, and I can help documenting more. > > 2. It is quite well tested. This part can be improved, but the core has some 80% coverage. > > 3. I am not the only one that knows how to mingle with it. To give some examples, Jorge, Damien (Cassou) and Esteban helped fixing some intricate bugs directly in the core. Lukas built the first Seaside rendering quite fast. I would also mention that as a student, Andrei Chis took about 1 month of work to produce a working version of a Seaside rendering almost from scratch. So, maybe it's not that difficult. > > 4. The core is quite stable since more than 1 year. There were changes, but they were mostly related to bug fixes. > > 5. The main point of using this infrastructure is not to replace Morphic, but it is to limit the maintenance of the browsers, and to empower more people to build more browsers. For example, the Glamorous Inspector has less than 200 lines of code in total. This is really tiny for the amount of things it offers. And it is highly extensible, too. > > 6. It's actually not that large: the core has 36 classes, and if you consider all the other presentations, helper classes and specialized browsers (but without the rendering code), you get some 93 classes. > > 7. But, perhaps the most important part is that there have been literally hundreds of browsers built on top of it. Not all of them are useful now, but they were when they were built. And it seems that people can build one quite fast without much knowledge of the internals either. That is the whole point of this infrastructure. Esteban even used it for building commercial applications. I built a couple, too. The whole of Moose is now using this infrastructure, too. > > > I am not saying that Glamour is perfect. There are quite a couple of things I would like to enhance (for example, the request ideas from Omnibrowser, or the wizard workflows from Merlin), but it has proved to be quite solid until now. > > So, before dismissing Glamour, perhaps it would be useful to actually look into it. > > Cheers, > Doru > > >> On Dec 31, 2011, at 1:00 PM, Tudor Girba wrote: >> >>> Hi Stef, >>> >>> You seem to say that it is bad that Glamour provides a good infrastructure that appeals to people. Maybe a better conclusion is that Glamour is something to be considered for the infrastructure of Pharo. >> >> Do you think so? >> I do not think that we can base our infrastructure on something that only one person understand and can modify. >> You will tell that this is the same for Morphic but this is not true. >> >> Stef >> > > -- > www.tudorgirba.com > > "Beauty is where we see it." > -- Lukas Renggli www.lukas-renggli.ch

6 7

[Pharo-project] Happy new year..
by Krishsmalltalk Jan. 1, 2012

Jan. 1, 2012

Wishing all Pharoer's a very warm n happy new year Since last few weeks, I have been experimenting with Pharo as a tablet interface inside a tiny core Linux. The dev though happens on ubuntu. Some more playing around for a group of trainees with pharo on windows 7, platform I do not very much like. How far is it a nice to have framework that provides for a complete UI, IDE like a tablet interface and behaves akin to android that has it's own AppStore, and application launcher in full screen on icon click. Anyone can download the base, and proceed to download the app source, files archive thru an app installer, that verifies , validates and installs as well as creates a launcher icon ( I will provide the screenshots once I have them fine tuned) Rest of ideas and process are similar to android marketplace or iStore, with definite controls on absolute stability and experience of the apps Some observations i will like the veterans to clue me on forward . I find Pharo 1.2 more stable than 1.3 latest... . Is morphic capable of supporting error free runtime GUI I enjoy it's capabilities, but feel it demands more intrinsic Pharo, debugging ability to keep hacking n fixing. Crashes , damaged rectangle painting are just few of the troubles I expect a simple answer, not necessarily a longer explanation of morphic and it's issues with global coordinates, polling event handling which are nuisances. I have read thru as much of links, docs on morphic as i could find, little working on it, but not enough to get an expert hang of it. . Is system browser the best to study for morphic or should I look through any other package..Debug n learn.. . Simple way to get an embedded submorph from it's chain by it's name, #subMorphNamed: does help but only in a limited way.. For those that it digs. . Simpler way to bar extensions from a contributed older package, overriding base class methods, not really the final as in java but at least prevent overwriting methods. A listing post file in of uncompiled methods of this kind. Hacking in FilePackage does help.. But anything better and more complete...and part of a base system. . Mechanism to autosave a defined package every method commit to a packagename.mcz by default to ease crash recovery, use monticello only when I need to version it as a done base. . Event handling of mouseLeave mouseEnter of a PluggableTextMorph, the on:send: did not work, not that I have dug into it... But would like to link it to the models methods directly in the builder method interface like we do for PluggableButtonMorph click.... . Color of a morph is not updated when selecting it thru the halo. Minor hack i have here, to get thru. . Why is extent attribute not updated when we use addMorph:fullFrame: which changes the bounds for the submorphs in some cases at least as i have noticed in debug step thru. . What are clear do not do rules in using morphic framework as it exists today, as people have already experienced and attempted. . Debugger stepping through has most times an out of step highlighting. Any fix on this.. . Settings window seems to have glitches in network settings, font updates from OS... . Autocompletion in windows seems to work on cr, but in Linux you have to type thru. . The easiest way to have a core Pharo runtime image stripped of all dev tools, classes, size is not the limitation here, but stable n bug free base is a must. . Tools n tips to make Pharo base with its loaded apps crash proof, just isolate and close the app that causes the problem rest of the image should continue to run. issue not directly related: . Windows support for OSProcess, i have read the threads and the note from Eliot that it works on windows for cadence, but I cannot get it to work, the ProcessWrapper works but is limited. If I do get it working does it support interactive shell, viz i invoke a command that enters into it's own loop of inputs n output till you send a quit. Lots more i will come up with in the next couple of weeks as I bring out what i have. Sudhakar krishnamachari Extn 91-40403012 Cell 9902104814

4 6

[Pharo-project] Fwd: Morphic queries
by Krishsmalltalk Jan. 1, 2012

Jan. 1, 2012

> What is that prevents picking lessons learnt, fixes from cuis into Pharo or is it considered a totally different line altogether. > > I am not calling of absolute merge or throwing morphic 2 .. But picking what is nice out there.. > > > > On Jan 1, 2012, at 11:52 AM, Krishsmalltalk <krishnamachari.sudhakar(a)gmail.com> wrote: > >> Wishing all Pharoer's a very warm n happy new year >> >> Since last few weeks, I have been experimenting with Pharo as a tablet interface inside a tiny core Linux. The dev though happens on ubuntu. Some more playing around for a group of trainees with pharo on windows 7, platform I do not very much like. >> >> How far is it a nice to have framework that provides for a complete UI, IDE like a tablet interface and behaves akin to android that has it's own AppStore, and application launcher in full screen on icon click. >> >> Anyone can download the base, and proceed to download the app source, files archive thru an app installer, that verifies , validates and installs as well as creates a launcher icon ( I will provide the screenshots once I have them fine tuned) >> >> Rest of ideas and process are similar to android marketplace or iStore, with definite controls on absolute stability and experience of the apps >> >> Some observations i will like the veterans to clue me on forward >> >> . I find Pharo 1.2 more stable than 1.3 latest... >> >> . Is morphic capable of supporting error free runtime GUI >> I enjoy it's capabilities, but feel it demands more intrinsic Pharo, debugging ability to keep hacking n fixing. Crashes , damaged rectangle painting are just few of the troubles >> >> I expect a simple answer, not necessarily a longer explanation of morphic and it's issues with global coordinates, polling event handling which are nuisances. I have read thru as much of links, docs on morphic as i could find, little working on it, but not enough to get an expert hang of it. >> >> . Is system browser the best to study for morphic or should I look through any other package..Debug n learn.. >> >> . Simple way to get an embedded submorph from it's chain by it's name, #subMorphNamed: does help but only in a limited way.. For those that it digs. >> >> . Simpler way to bar extensions from a contributed older package, overriding base class methods, not really the final as in java but at least prevent overwriting methods. A listing post file in of uncompiled methods of this kind. Hacking in FilePackage does help.. But anything better and more complete...and part of a base system. >> >> . Mechanism to autosave a defined package every method commit to a packagename.mcz by default to ease crash recovery, use monticello only when I need to version it as a done base. >> >> . Event handling of mouseLeave mouseEnter of a PluggableTextMorph, the on:send: did not work, not that I have dug into it... But would like to link it to the models methods directly in the builder method interface like we do for PluggableButtonMorph click.... >> >> . Color of a morph is not updated when selecting it thru the halo. Minor hack i have here, to get thru. >> >> . Why is extent attribute not updated when we use addMorph:fullFrame: which changes the bounds for the submorphs in some cases at least as i have noticed in debug step thru. >> >> . What are clear do not do rules in using morphic framework as it exists today, as people have already experienced and attempted. >> >> . Debugger stepping through has most times an out of step highlighting. Any fix on this.. >> >> . Settings window seems to have glitches in network settings, font updates from OS... >> >> . Autocompletion in windows seems to work on cr, but in Linux you have to type thru. >> >> . The easiest way to have a core Pharo runtime image stripped of all dev tools, classes, size is not the limitation here, but stable n bug free base is a must. >> >> . Tools n tips to make Pharo base with its loaded apps crash proof, just isolate and close the app that causes the problem rest of the image should continue to run. >> >> >> issue not directly related: >> . Windows support for OSProcess, i have read the threads and the note from Eliot that it works on windows for cadence, but I cannot get it to work, the ProcessWrapper works but is limited. If I do get it working does it support interactive shell, viz i invoke a command that enters into it's own loop of inputs n output till you send a quit. >> >> Lots more i will come up with in the next couple of weeks as I bring out what i have. >> >> >> Sudhakar krishnamachari >> >> Extn 91-40403012 >> Cell 9902104814 >> >>

2 1