July 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Visual element - Pogress bar.

by Benjamin

Just that you know, by opening the example, the slider is far too big. If you set its size properly, it will look like your screenshot (more or less ^^) Ben On Jul 5, 2013, at 12:03 PM, Mariano Vicente <m.vicent(a)gmail.com> wrote: > In the screenshot don't look like as a progress bar.â âHow can use it? I write in the workspace and is unknow. > Should download some package? â â(I'm using pharo 3.0) > > âRegards, > Mariano > > > On Fri, Jul 5, 2013 at 6:51 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Is a SlideMorph what you are looking for ? > > <Screen Shot 2013-07-05 at 11.51.04 AM.png> > Ben > > On Jul 5, 2013, at 11:36 AM, Mariano Vicente <m.vicent(a)gmail.com> wrote: > >> Hello >> I'm searching for a visual component such as â video âprogress bar â / seek bar or something like this: >> >> >> are there something like it ? >> >> âRegards, >> Mariano > >

July 5, 2013

Re: [Pharo-dev] Visual element - Pogress bar.

by Benjamin

SliderModel is the class producing what you can see in the screenshot. Usually, for video/audio progress bar, you use a slider, which is updated when the video/music is played. But the user can also move in the movie/music using it. To produce what the screenshot shows, do: SliderModel example Ben On Jul 5, 2013, at 12:03 PM, Mariano Vicente <m.vicent(a)gmail.com> wrote: > In the screenshot don't look like as a progress bar.â âHow can use it? I write in the workspace and is unknow. > Should download some package? â â(I'm using pharo 3.0) > > âRegards, > Mariano > > > On Fri, Jul 5, 2013 at 6:51 AM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Is a SlideMorph what you are looking for ? > > <Screen Shot 2013-07-05 at 11.51.04 AM.png> > Ben > > On Jul 5, 2013, at 11:36 AM, Mariano Vicente <m.vicent(a)gmail.com> wrote: > >> Hello >> I'm searching for a visual component such as â video âprogress bar â / seek bar or something like this: >> >> >> are there something like it ? >> >> âRegards, >> Mariano > >

July 5, 2013

Re: [Pharo-dev] Visual element - Pogress bar.

by Mariano Vicente

In the screenshot don't look like as a progress bar. â â How can use it? I write in the workspace and is unknow. Should download some package? â â (I'm using pharo 3.0) âRegards, Mariano On Fri, Jul 5, 2013 at 6:51 AM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Is a SlideMorph what you are looking for ? > > > Ben > > On Jul 5, 2013, at 11:36 AM, Mariano Vicente <m.vicent(a)gmail.com> wrote: > > Hello > I'm searching for a visual component such as > â video â > progress bar > â / seek bar or something like this: > [image: Inline image 1] > > are there something like it ? > > âRegards, > Mariano > > >

July 5, 2013

Re: [Pharo-dev] Visual element - Pogress bar.

by Benjamin

Is a SlideMorph what you are looking for ? Ben On Jul 5, 2013, at 11:36 AM, Mariano Vicente <m.vicent(a)gmail.com> wrote: > Hello > I'm searching for a visual component such as â video âprogress bar â / seek bar or something like this: > > > are there something like it ? > > âRegards, > Mariano

July 5, 2013

Visual element - Pogress bar.

by Mariano Vicente

Hello I'm searching for a visual component such as â video â progress bar â / seek bar or something like this: [image: Inline image 1] are there something like it ? âRegards, Mariano

July 5, 2013

Re: [Pharo-dev] Helping migration between 1.4 to 20

by Hilaire Fernandes

Ok, thanks playing with it. Hilaire Le 01/07/2013 16:17, StÃ©phane Ducasse a Ã©crit : > Here is the email of andre and it can help you. > > Stef > >> You can download the rules from: >> ------------------ >> Gofer new >> squeaksource: 'FindBugs'; >> package: 'MiningLintRules-PharoMigration'; "1.4 -> 2.0" >> package: 'MiningLintRules-PharoMigrationNew'; "some more rules 1.4 >> -> 2.0" >> package: 'MiningLintRules-Pharo13'; "1.3 -> 1.4" >> load. >> ------------------ >> >> You can run such rules by selecting the groups *Mined rules* in the >> the Critcs Browser. >> Note that this not the solution for all the problems, just a help :) >> >> The next plan is to create rules on demand (instead of providing >> predefined rules like the ones above). >> So, you ask how should I update "this", and then we give you a rule >> changing "this" for "that". >> > -- Dr. Geo - http://drgeo.eu

July 5, 2013

[update 3.0] #30256

by Marcus Denker

July 5, 2013

Re: [Pharo-dev] NativeBoost with no access to sources

by Goubier Thierry

Le 04/07/2013 19:11, Igor Stasenko a Ã©crit : > On 4 July 2013 13:07, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >> >> >> I wondered if it could be both (name and number), but went for the shortest >> path, that is the simplest solution: >> >> NBFFICallout>>loaderFromMethodArgsNamed: argName >> >> methodArgs >> ifNotNil: [ >> | index | >> (argName first = $_ and: [ argName allButFirst >> isAllDigits ]) >> ifTrue: [ ^ NBSTMethodArgument new >> stackIndex: methodArgs size - argName asUnsignedInteger ]. >> index := methodArgs indexOf: argName ifAbsent: [ nil >> ]. >> index >> ifNotNil: [ >> "ok, this is a method argument" >> ^ NBSTMethodArgument new stackIndex: >> methodArgs size - index ] ]. >> ^ nil >> > This looks fine , and i will add it into NB. Could you rather test for unability to get the source of the method and raise a NB-defined error? So that I could write a fallback on non-NB code with a on: do:. Please :) (it would then both handle startup related errors and unreadable sources as well). And with a backport to 2.0, because the odds of seeing an Opal based solution on 2.0 are fairly low. >> Then I tried to change all calls to use numbers, but it ended in a Segfault >> (not in NB itself, but somewhere else as if I had a corrupted heap). The end >> result with all changes is there: >> > >> http://ss3.gemstone.com/ss/PharoInbox/SLICE-Issue-11102-FileSystemError-Pat… >> >> If you see where I missed something, I'd be happy to know. >> > > you probably made a mistake somewhere. ;) > because counting the argument index, instead of putting its name is > error prone. Well, in almost all cases, arguments were used in the order they were given, which should have been almost foolproof ;) > not cache, just put it into method's attributes, so i can access them later. > And not when method added/removed, but at compilation time. Is there a real, practical difference between "at compilation time" and "when receiving MethodAdded event"? i.e. is the complexity added in the compilation process worthwhile? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

July 5, 2013

We need you for a software integration survey (reminder)

by Martin Dias

Hi all, Some time ago we sent an email to ask you contributing to a research to improve tools for software integration. If you maintain a project with multiple contributors, we will greatly appreciate your participation. Your answers will be used for research purposes and to support the development of new tools. You can later access the results of this study, make free use of our tools to support the integration of changes, and maybe receive a gift. We found out that the survey was not properly working on Safari (and may be also some other browsers). And we have now corrected this issue. Up to now, we received 36 full answers and 166 incomplete answers. So we decided to give you an extra month, if you started to fill the survey, please consider resuming filling the survey. For this you only need to go back to the same site: https://sondages.inria.fr/index.php/667625/lang-en If you did not yet fill in the survey, please consider doing it now. Best regards, Martin Dias, Nicolas Anquetil, Veronica Isabel Uquillas, StÃ©phane Ducasse and the RMOD Inria team

July 5, 2013

[Issue tracker] Please have a look at your issues!

by Marcus Denker

Hi, We should do a pass over all issues. e.g. -> is your bug still relevant? -> if you submitted a fix, maybe the bug status is wrong and therefore nobody looked at it? -> if you added a verbal description of how to fix something, consider submitting code in addition (people have just no idea how much easier it is to deal with machine readable code than half-a-page of proseâ¦) -> You where involved in a discussion about a bug. So now go trough it and summarize: What is the next *action* that needs to be done to close the issue? You can get a list of *all* open issues: https://pharo.fogbugz.com/f/filters/33/All-Opened or just the ones for 2.0: https://pharo.fogbugz.com/f/filters/8/2-0-Work-Needed and 3.0: https://pharo.fogbugz.com/f/filters/37/3-0-Work-Needed For the 2.0/3.0 issues, we should decide: are they really of a kind that they need to fixed before we can release? (in 2.0: do we really need to back port? or is it enough to fix in 3.0?) Marcus

July 5, 2013