October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] new GT features: disk memory, ws.stfx.eu sharing, closeable panes and others

by stepharo

On 25/10/14 01:48, Tudor Girba wrote: > Hi Steph, > > No. It's just a stupid dump on the harddisk of the current contents as > soon as there is a change. Where do I find more about the undo mechanism? Look in the history package in the image A HistoryIterator holds an UndoRedoGroup in order to store an history of commands with the possibility of undoing and redoing. The iterator cursor is represented by the index inst var. Index always contains the position of the command that can be currently undone. So, undo decrease index and redo increase index. When a new record is stored, then, index contains the newly added record position. See HistoryIteratorTest for examples. > > Cheers, > Doru > > > > On Sat, Oct 25, 2014 at 8:40 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > For Instant caching did you use the undo mechanism of Alain? > > Stef > On 25/10/14 06:19, Tudor Girba wrote: >> Hi, >> >> We are quite actively working on GT. >> >> First of all, thanks everyone for the feedback. We take it quite >> seriously and we do our best to take it into account. Please keep >> the discussions flowing. >> >> I summarized some of the things that happened recently in the >> playground and inspector here: >> http://www.humane-assessment.com/blog/gt-developments-endless-playground-me… >> >> Let us know what you think. >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> "Every thing has its own flow" > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Oct. 26, 2014

Re: [Pharo-dev] Run Spur run!!

by stepharo

> > Yes, I'm very excited. It's so great to have strong collaborators > like ClÃ©ment, Ronie, Doug and Tim. But there's lots of room for more > to join us. For a really cool project how about grabbing Bert > Freudenberg's VMMakerJS Squeak-vm-on-JavaScript, extract the event > handling and rendering part and connect it to the Cog VM via sockets > to give us a really fast web plugin? I thought that the event handling was what JB is doing with the idle process on android. Stef > > -- > best, > Eliot

Oct. 26, 2014

Re: [Pharo-dev] PackageChooser logic

by stepharo

On 26/10/14 03:20, Hilaire wrote: > It is the packager choose from the Finder tools. > I don't say the tools is wrong: in the contrary both the Finder and > PackageChooser are pretty well designed from usability point of view, I > like them very much! > > What I suggest from an usability point of view: > when you click in the "Packages..." button, by default the > PackageChooser dialog could open with no package selected (or the > previously selected ones) and not the whole packages of the system as it > is now. > > >From the user point of view when you click the "Packages..." button you > expect to start from an empty list and select a few package to search in. > > It is really a minor detail, and other people may have different > different view, or so? Usuability is important and little glitches are annoying. So can you open a bug entry with step by step description? Tx Stef > > > Le 24/10/2014 14:08, stepharo a Ã©crit : >> Hilaire could you describe how to get the PackageChooser because people >> may interpret it in different ways. >> On 24/10/14 11:53, Hilaire wrote: >>> I found the logic of the PackageChooser from the finder to be pretty >>> weird. >>> >>> You can't directly select the packages you want to search in: you need >>> to select all, reject, then reselect the ones you want to search in. >>> >>> >>> How do you think about it? >>> >>> >> >> >

Oct. 26, 2014

Re: [Pharo-dev] PackageChooser logic

by Hilaire

It is the packager choose from the Finder tools. I don't say the tools is wrong: in the contrary both the Finder and PackageChooser are pretty well designed from usability point of view, I like them very much! What I suggest from an usability point of view: when you click in the "Packages..." button, by default the PackageChooser dialog could open with no package selected (or the previously selected ones) and not the whole packages of the system as it is now. >From the user point of view when you click the "Packages..." button you expect to start from an empty list and select a few package to search in. It is really a minor detail, and other people may have different different view, or so? Le 24/10/2014 14:08, stepharo a Ã©crit : > Hilaire could you describe how to get the PackageChooser because people > may interpret it in different ways. > On 24/10/14 11:53, Hilaire wrote: >> I found the logic of the PackageChooser from the finder to be pretty >> weird. >> >> You can't directly select the packages you want to search in: you need >> to select all, reject, then reselect the ones you want to search in. >> >> >> How do you think about it? >> >> > > > -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Oct. 26, 2014

Compiler evaluate: - How to only allow access to given classes or capabilities?

by phil＠highoctane.be

"Compiler evaluate: source" is a powerful feature. Now, how can I disallow "dangerous" calls from the source? A bit like in java where we have the security manager. http://www.securingjava.com/chapter-two/chapter-two-8.html What do we have in stock? To avoid things like a Smalltalk quitPrimitive ... TIA Phil

Oct. 26, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40327 Home: https://github.com/pharo-project/pharo-core

Oct. 25, 2014

[pharo-project/pharo-core] 0c709e: 40327

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 0c709e15cabdc7bee8b67555db17a20b0c48fa44 https://github.com/pharo-project/pharo-core/commit/0c709e15cabdc7bee8b67555… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-26 (Sun, 26 Oct 2014) Changed paths: M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/buildInitializeCodeFor_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script327.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40327.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/extension/Array/instance/generateSpecFormatArray.st Log Message: ----------- 40327 13115 unnecessary concatenation https://pharo.fogbugz.com/f/cases/13115 13158 Adding class-side #initialize should not template with /super initialize/ https://pharo.fogbugz.com/f/cases/13158 http://files.pharo.org/image/40/40327.zip

Oct. 25, 2014

New Cog VMs available

by Eliot Miranda

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3114/. CogVM binaries as per VMMaker.oscog-eem.913/r3114 Spur: Fix baaaad bug in checking for still-married contexts in Spur. One *cannot* simply follow what is assumed to be the frameContext field of what is presumed to be a context. On Spur we need to *know* whether we have a valid frameContext field, and for that we have to know there is a valid frame. So refactor, moving isFrame:onPage: from StackInterpreterPrimitives to StackInterpreter, and use it to validate the frame pointer of a maybe married context before testing the context for being forwarded. All: Avoid cogging methods containing unknown bytecodes early in scanMethod. Use a hack to avoid a test on the common path. Fix assert fail cases in ceInterpretMethodFromPIC:receiver: Both of these together fix assert fails due to cogging methods containing unknown bytecodes. Spur: Implement image segments. Use Igor's idea of splitting the computation of the transitive closure from the writing of the image segment for simplicity, even if the two are together into a single primitive for backwards-compatibility. All: Rewrite the two image segment primitives to pass back an error code on failure, and rewrite the (New)ObjectMemory code to answer informative failure codes. Print slots of word objects in longPrintOop: Fix parenthesization bugs in validation code in some Alien plugin primtiives. Make findClassContainingMethod:startingAt: et al robust in the face of faulted-out classes (nil method dictionaries). Include the AioPlugin in the Newspeak linux VMs; recent reports indicate it's essential to good performance in recent versions of OSProcessPlugin. Unix startup script: Quote the LD_LIBRARY_PATH setting to tolerate directory names with spaces. -- best, Eliot

Oct. 25, 2014

Modbus project

by Jesus Mari Aguirre

I'm interested in this project http://gsoc2013.esug.org/projects/modbus, anyone knows if this project is alive, I am working in a fuzzy logic lib and it could be useful in order to connect my lib to the "real world"

Oct. 25, 2014

Re: [Pharo-dev] Run Spur run!!

by Thierry Goubier

Le 25/10/2014 19:20, Eliot Miranda a Ã©crit : > Hi Thierry, ... > > If Amber is useful then a Squeak/Pharo/Scratch/whatever plugin is > useful. Amber has limitations (no thisContext, no become, no > run-time class redefinition, no instance migration there-on, limited > performance, especially for non-local return), but it is still useful > enough for people to go through that extra deployment and > verification step to check that the code still works under Amber. If > one can't live with those limitations or if one doesn't want to pay > the cost of the extra deployments step then a plugin solves that > problem. > > Don't confuse an absence as a lack of need. Because there has been > no "plugin" solution for a few years doesn't mean it's not needed. > That people have put significant effort into alternatives like Amber > and JalapeÃ±o proves it is useful. Or that Smalltalk is great and worth reimplementing on top of whatever run system you have available :) >> Moreover, I see that the only thing with potential linked to the >> web today is to handle tablets/smartphones, and this is a bit why >> I'm asking about ARM support (also embedding in small stuff, like >> Cortex M0-M4 stuff with BLE, solar cells and batteries). For now, >> the only use we have for Smalltalk in there is as C code generation >> / deployment IDEs on the desktop (aka B. Pottier Netgen), and as >> back-end on web deployment with Seaside + others. > > There doesn't need to be an either/or in a growing community. Point well taken :) Thierry

Oct. 25, 2014