February 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] fixTemps and BlockContext question

by Luc Fabresse

Hi all, I wonder why BlockContext>>fixTemps is still in PharoCore. I guess that it should be removed, isn't it? It has only one sender. Morever, should the BlockContext class be removed too? Depending on answers, I will write a bug report. Luc

Feb. 9, 2010

Re: [Pharo-project] Alternative implementation for Cursor>>show:

by Fernando olivero

Hi , i think this change could be performed regardless of the InputSensor fixes. It's just removing a double dispatch that does not add much On Feb 9, 2010, at 9:36 AM, Mariano Martinez Peck wrote: > > > On Tue, Feb 9, 2010 at 9:33 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > It is true? > Did you check what mike sent a while ago (or in the bugtracker about inputEventSensor? > > > I don't know what you are talking about. > > > > Yes, this seems reasonable, as we should delete all references to Cursor. > > > > Do you agree with this ? If true we need to create an issue and commit :) > > > > Cheers > > > > Mariano > > > > On Sat, Jan 23, 2010 at 12:28 PM, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: > > Hi, i think this send to Sensor could be avoided by replacing the Cursor>>show: method with > > > > Cursor>>show > > self class currentCursor: self. > > > > > > > > > > Instead of a: > > > > Cursor>>show > > "Make the hardware's mouse cursor look like the receiver" > > > > Sensor currentCursor: self > > > > > > InputSensor>>currentCursor: newCursor > > "The current cursor is maintained in class Cursor." > > > > Cursor currentCursor: newCursor. > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > <ATT00001..txt>

Feb. 9, 2010

[Pharo-project] about gofer and recovering changes from the change log

by Fernando olivero

Hi, if you're using gofer for committing the changes on the packages you're working on this is a tip if you happen to crash the image and want to recover your lost changes. 1. open a new image 2. open the recent changes window ( WorldMenu->Tools->recover lost changes..) 3. do a reject older 4. do a reject up to date. 5. install the packages ( using gofer or metacello or whatever you want) 6. look starting from the last change in the recent changes window for the first entry of the form: ' do it gofer commit:'..'.. ( where gofer is the binded name for the gofer instance you use, usually in a workspace). 7. From that line to the end of the list is you what you did since the latest commit!. Hope it helps! Fernando

Feb. 9, 2010

Re: [Pharo-project] World Menu (was [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2)

by Mariano Martinez Peck

http://code.google.com/p/pharo/issues/detail?id=1945 On Sun, Feb 7, 2010 at 9:49 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > can you point us to the class? > > > On Feb 6, 2010, at 9:54 PM, Alain Plantec wrote: > > > StÃ©phane Ducasse a Ã©crit : > >> we need a registration mechanism for the menu > >> > > yes, I have built one which is using pragma but it needs a > > to reviewed a little bit. > > Alain > >> > >> On Feb 5, 2010, at 9:53 PM, Mariano Martinez Peck wrote: > >> > >> > >>> On Fri, Feb 5, 2010 at 9:23 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >>> Hi Mariano, > >>> > >>> You will find a changeset attached here > http://code.google.com/p/pharo/issues/detail?id=1937 which add the Help > menu. > >>> > >>> > >>> Thanks Laurent! Thanks cool !!! > >>> > >>> Now, I have another question. It would be cool that the help menu is in > the core image. But then, there will be items that should be from the core, > suppose a workspace with the shortcuts or something similar and items that > are from the PharoDev image, for example, ProfStef. > >>> > >>> So, my question is, can I integrate this menu in PharoCore, with the > current items of PharoCore and then, from outside, suppose when building > PharoDev I add things there ? or even ProfStef for example could add > himself there when installing (in the metacello post doit). > >>> > >>> I think this is similar to the problem of the ToolSet. I want to be > able to build or modify in runtime the items of a menu :) > >>> > >>> Is this possible ? > >>> > >>> Cheers > >>> > >>> Mariano > >>> > >>> Laurent > >>> > >>> > >>> > >>> On Fri, Feb 5, 2010 at 9:51 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >>> > >>> 2010/2/5 Mariano Martinez Peck <marianopeck(a)gmail.com> > >>> > >>> > >>> > >>> 2010/2/4 laurent laffont <laurent.laffont(a)gmail.com> > >>> > >>> Hi, > >>> > >>> I was thinking that there's no entry in the world menu to re-open the > welcome workspace. For beginners it may be useful ? > >>> > >>> Yes, I agree. I also though about that but I didn't know where to put > it in the menu neither how to code it. Ok, I have several examples to look > how to do it, but nil time for the last week :( > >>> > >>> Where exactly do you think is the best place to put it in the menu ? I > said several times about the issue: > >>> > >>> http://code.google.com/p/pharo/issues/detail?id=1042 > >>> > >>> (search in mailing list also) > >>> > >>> It is OBVIOUS that we are missing a "help menu". > >>> > >>> > >>> I agree > >>> > >>> > >>> > >>> > >>> There we can put also this thing to reopen the welcome workspace. > >>> > >>> Now....do we have time to do this for 1.0 ? someone ? > >>> > >>> > >>> I will take a look. No promise. > >>> > >>> > >>> In World > Tools: > >>> - duplicated entries: Class Browser, Workspace, Test Runner, Monticello > Browser > >>> > >>> These are the most common used tools, that's why they are there. > >>> > >>> > >>> I prefer one thing at one place :) > >>> > >>> > >>> Laurent > >>> > >>> > >>> > >>> In World > Tools > More: > >>> - Language editor / language editor for.... these tools look strange > :) > >>> > >>> And I don't know if they are even working, > >>> > >>> - duplicated entries: Monticello Browser, Preference Browser, Test > Runner > >>> - someone use Search Browser and Services Browser ? > >>> - MCConfigurationBrowser: what is the purpose of this tool ? > >>> (may be we can remove this "Other tools" menu, merging it with tools) > >>> > >>> > >>> Cheers, > >>> > >>> Laurent Laffont > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 9, 2010

[Pharo-project] release a new 1.1 core - 11196 on gforge

by StÃ©phane Ducasse

Hi I released a new 1.1 core - 11196 on gforge. I will try to get some time to integrate some issues. later in the evening. Stef

Feb. 9, 2010

Re: [Pharo-project] broken polymorph example in 1.1?

by Henrik Johansen

I couldn't help noticing there are also a few Undefined entries resulting from the Squeak-ToolBuilder merge, should also be looked into :) Cheers, Henry Den 09.02.2010 08:22, skrev StÃ©phane Ducasse: > Really may be one of my mistakes. > > stef > > On Feb 8, 2010, at 12:30 PM, Gary Chambers wrote: > > >> Looks like PluggableDialogWindow has had its superclass changed (was >> DialogWindow)... >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Hilaire Fernandes" <hilaire(a)ofset.org> >> To: <pharo-project(a)lists.gforge.inria.fr> >> Sent: Saturday, February 06, 2010 5:04 PM >> Subject: [Pharo-project] broken polymorph example in 1.1? >> >> >> >>> Is it me or examples of the Polymorph usage are broken? >>> >>> For example exampleOtherControls break >>> >>> Hilaire >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

Feb. 9, 2010

Re: [Pharo-project] something in 1.1 broke ImageSegment

by Henrik Johansen

Den 09.02.2010 06:14, skrev Levente Uzonyi: > On Mon, 8 Feb 2010, Henrik Sperre Johansen wrote: > > >> I believe its due to stream positioning when crossing buffer boundries in >> basicChunk, I have to debug a bit further for a solution though, sorry... >> > It seems to be an easy one, though I didn't try the fix, just reviewed > the code. So the cause of the issue is in MultiByteFileStream >> > #basicChunk, which doesn't care about readLimit. When readLimit is less > than "collection size", the end of the returned chunk may be the end of a > previous chunk. > Thanks Levente, in my original-author-blindness, I couldn't see past that position was apparently set wrong compared to the original approach. When you say it like that, it's obvious :) > This method has at least two other flaws (These probably won't hurt > anyone in the near future, though both can be avoided): > 1. if read buffering is disabled it will raise an error > Yes, this should be fixed. I assume a collection ifNil: [^nil] is enough? > 2. it assumes that the encoding of the stream is ascii compatible > > Yes, that was a tradeoff. (Which I hoped was a clear implication from the method comment) Only Converter with this characteristic currently existing (afaict) is QuotedPrintable, I doubt that or another format will ever be used for storage of code. The method you wrote in Squeak doesn't have this limitiation, on the other hand that does little for encodings other than utf8 (which, of course, could be successfully argued to be the important case). This way, you also avoid a Stream creation/String copy in the common case, as well as not let encodings in addition to streams contain special logic to read in code chunks. > Levente > > Cheers, Henry

Feb. 9, 2010

Re: [Pharo-project] Alternative implementation for Cursor>>show:

by Mariano Martinez Peck

On Tue, Feb 9, 2010 at 9:33 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > It is true? > Did you check what mike sent a while ago (or in the bugtracker about > inputEventSensor? > > I don't know what you are talking about. > > > Yes, this seems reasonable, as we should delete all references to Cursor. > > > > Do you agree with this ? If true we need to create an issue and commit > :) > > > > Cheers > > > > Mariano > > > > On Sat, Jan 23, 2010 at 12:28 PM, Fernando olivero <oliverof(a)lu.unisi.ch> > wrote: > > Hi, i think this send to Sensor could be avoided by replacing the > Cursor>>show: method with > > > > Cursor>>show > > self class currentCursor: self. > > > > > > > > > > Instead of a: > > > > Cursor>>show > > "Make the hardware's mouse cursor look like the receiver" > > > > Sensor currentCursor: self > > > > > > InputSensor>>currentCursor: newCursor > > "The current cursor is maintained in class Cursor." > > > > Cursor currentCursor: newCursor. > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 9, 2010

Re: [Pharo-project] Alternative implementation for Cursor>>show:

by StÃ©phane Ducasse

It is true? Did you check what mike sent a while ago (or in the bugtracker about inputEventSensor? > Yes, this seems reasonable, as we should delete all references to Cursor. > > Do you agree with this ? If true we need to create an issue and commit :) > > Cheers > > Mariano > > On Sat, Jan 23, 2010 at 12:28 PM, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: > Hi, i think this send to Sensor could be avoided by replacing the Cursor>>show: method with > > Cursor>>show > self class currentCursor: self. > > > > > Instead of a: > > Cursor>>show > "Make the hardware's mouse cursor look like the receiver" > > Sensor currentCursor: self > > > InputSensor>>currentCursor: newCursor > "The current cursor is maintained in class Cursor." > > Cursor currentCursor: newCursor. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 9, 2010

Re: [Pharo-project] Pharo screencasts - how to

by StÃ©phane Ducasse

as I idea I would like to show how to - load XML documents - get an image over the web Stef On Feb 8, 2010, at 10:20 PM, laurent laffont wrote: > Hi, > > I want to share how I record screencasts for Pharocasts http://pharocasts.blogspot.com/ in case someone wants to participate. Now there's 11 screencasts. The difficult part is to have a good idea / scenario for a screencast. Comments and ideas are welcome. > > If you want to publish on Pharocasts I can give you write access. Or if you have a "draft" screencast I can edit it / re-record it for publishing. I try to record screencasts with a minimum duration of 5 mn. > > These instructions are for Linux (but I'm a beginner in video stuff). I don't know which software to use on other operating systems. Have advices ? > > I record with xvidcap http://xvidcap.sourceforge.net/. I define a capture zone of 800x600 (use 4:3 or 16:9 standard resolution. If not you can have poor encoding results). > Set multi-frame mode (you have to right-click on the file button to access preferences, not very intuitive). > I choose AVI format / MPEG 4 codec. > If you open / close applications for the screencast, note that KDE has very good options to memorize / force windows positions, so they are always opened in your capture zone.(Other window managers like E17 have these sort of options). > The trick is to not stop recording when you write errors, you can cut the "wrong" parts later. > > To edit the video, I use avidemux http://fixounet.free.fr/avidemux/. It has Qt and Gtk GUI and work on Linux / Windows / OSX / BSD ..... It's really easy to use. When you want to cut a part, you define the beginning with the A button ( Ctrl-[ ), the end with B button ( Ctrl-] ), then Edit -> Cut ( Ctrl-X ). You can navigate using arrow keys. > When finished, click on save (Choose another filename !!). > > So now you have your screencast in .mpeg file. Note that people using MacOSX Tiger or older have problems to watch this video. So I convert in .mov using ffmpeg http://www.ffmpeg.org/ like this: > ffmpeg -i my_video.mpeg -b 500k my_video.mov. > > (but I think it's not the best command as the video size is bigger and quality lower). > > To publish the video I use Vimeo http://vimeo.com/. I've tried YouTube and Daily Motion but the quality is lower or the video duration is limited. I had problems using the "standard uploader", so I switch to the "basic uploader" on the download page, works better. > > It's really fun to record screencasts, and a good way to show development practices. > > Cheers, > > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 9, 2010