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

Re: [Pharo-dev] Making ASTInterpreter work with opal bindings

by ClÃ©ment Bera

Sorry with the strike and no metro I cannot be at INRIA today. I'm at Marcus right now we will have a look at your slice now :) I don't know why this morning I hadn't received yet your mails from yesterday. 2013/5/14 Guillermo Polito <guillermopolito(a)gmail.com> > > On Tue, May 14, 2013 at 1:03 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > >> Hey Guille, >> >> To debug AST-interpreter there is a specific AIContextInspector. What you >> can do is just to inspect in the debugger the latest AIContext created by >> the AST-interpreter and you should see the stack of AIContext in the >> inspector. It is not perfect but it helps a lot. There is also the >> AST-Debugger but it is just a prototype so you can hardly use it. >> > > Buu, how do I get the ASTDebugger? Maybe I can give it a try... > AST-Debugger is at Smalltalkhub user : dh83 project : ast-interpreter package AST-debugger there is no config. But it's just a quick prototype, there is some work to do. To try you should copy AST-debugger test in workspace (in test it does not works because of problem with test thread / UI thread) and then run. The into button works a little, the other not, but the stack and inspectors works. > > >> >> testEnsureTricky is the one that checks ensure nested in the on:do: works >> correctly. Basically it checks when you unwind the context up to the >> exception handler that you executes the ensure blocks code. It's kind of >> the trickiest one to fix :/. In the exception chapter of Deep into Pharo I >> added a section somewhere in Exception implementation about that, it might >> help you to read it. >> >> Take care, AST-interpreter tests might not be enough. You should check >> the console output of the AST-interpreter-regression build too. (here : >> https://ci.inria.fr/rmod/job/ast-interpreter-regression/89/console) But >> it is failing since some new updates in Pharo 3.0 ... >> > > I'm looking at https://ci.inria.fr/rmod/job/ast-interpreter-regression/. > What does this job test/do? We can add that to the description :) > This test runs all the Pharo Kernel tests with the AST-interpreter. Then you can guarantee the AST-interpreter can interpret the whole Pharo Kernel suite, which is much more than just AST-interpreter tests. > > Anyway, I'm loading the same as the job, so I can test the slice locally > in my machine :) > > >> >> Are you committing on the AST-interpreter repository or on Pharo directly >> ? >> > > Pharo... Should I commit to the other repo? Don't have grants =^). > There is currently no dev any more on AST-interpreter but it would be nice to commit to the other repo first for the 2 jenkins jobs to run. Ask Camillo to have the rights to write on it. > > >> I don't think there are but there might be some fixes already on the dev >> branch > Smalltalkhub user: dh83 project: ast-interpreter >> > > Will check. Actually, I just loaded bleeding edge + merged my slice, and > the same test still fails. > > >> >> I would like to work on Opal test this afternoon but if you come to lille >> this week (not today because there is the strike) we can have a look >> together. >> > > Tomorrow! > Not possible there is still the strike... Are you at INRIA ? > > >> For M4te I've also fixed some stuff in Hz on the m4te repo (basically >> compatibility with the new RB visitor API) it might be nice to commit it on >> your repo too. >> > > cool :) > > >> >> See you, >> >> >> >> 2013/5/14 Guillermo Polito <guillermopolito(a)gmail.com> >> >>> Right now, in the image there exist two ways to annotate an AST: >>> - the Opal way >>> - the RB Way >>> >>> We should simplify that by having only one. So far, the only user of the >>> RB bindings is the ASTInterpreter + the RB tests. >>> >>> So, I prepared a slice and issue [1], with the following details >>> >>> - annotate ast using opal annotator >>> - extended OCBindings to read and write from an AST interpreter >>> - not yet made a difference between arg nodes with a different class >>> (just put an if) >>> - i didnt add inst vars into the opal bindings for the binding->node >>> relation as in RB, I send the node as a parameter >>> - I had to adapt the #compile: into ASTInterpreter because >>> - opal does not annotate other than method nodes >>> - undeclared variables raised warnings, not errors >>> >>> There is one problem yet, I have only one failing test: >>> #testEnsureTricky. I don't understand yet why it is failing and debugging >>> it is pretty complex :). So any help is welcome in reviewing the changes. >>> >>> Guille >>> >>> [1] >>> https://pharo.fogbugz.com/f/cases/10610/Make-ASTInterpreter-use-OC-Opal-bin… >>> >> >> >> >> -- >> ClÃ©ment BÃ©ra >> Mate Virtual Machine Engineer >> BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq* >> > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

May 15, 2013

Re: [Pharo-dev] [Pharo-project] Understanding NBOpenGL

by stephane ducasse

I usually add a nice class comment in the configurationof... On May 15, 2013, at 9:37 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On May 14, 2013, at 12:45 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> How did you loaded NBOpenGL? >> For 2.0/3.0 pharo image use >> (ConfigurationOfNBOpenGL project version: '2.0') load > > I added this important piece of information into http://smalltalkhub.com/#!/~PharoExtras/NBOpenGL :) > It would be a lot better to make > > ConfigurationOfNBOpenGL load. > > work out of the box, and also to copy them to MetaRepoForPharo20... so everybody can load without needing to thing a lot about. > > Esteban

May 15, 2013

Re: [Pharo-dev] AsmJit refactoring

by Norbert Hartl

That's great! Norbert Am 15.05.2013 um 14:37 schrieb Camillo Bruni <camillobruni(a)gmail.com>: > I started to work on a basic ARM model for AsmJit with Damien Pollet and on the fly we continue the refactoring I started last week: > > - no more PoolDictionaries > - no more global registers > - reducing the number of class variables > - more specific register classes for x86 to avoid nasty bit masking/checking operations on an integer > > All in all this makes the code much more accessible and you can be sure that changing a register (aka renaming it) is a local cation. > > What do you think?

May 15, 2013

Re: [Pharo-dev] [Pharo-users] success story: NTed

by Norbert Hartl

Manfred, thanks. Maybe I missed that when starting with the old version of amber. I'm glad google closure compiler is supposed to work. If it works for the server I'm positive it'll work on the client. Major problems are IMHO if you have variable additions that use underscore as prefix etc. and this should be the same situation on client and server because it is amber dependent. Norbert Am 14.05.2013 um 11:37 schrieb Norbert Hartl <norbert(a)hartl.name>: > I think my last post of this message fell into the time the old mailing list dies. So here it is again > > --- > > We (@2denker in cooperation with a local university) built a monitoring tool for disaster scenario recovery rehearsals. Several times a year universities, red cross, THW und hospitals are planning a rehearsal together. For this an environment is prepared for a simulated disaster (car accidents, explosions in civil areas, â¦). The local environment is prepared to look real as well as film make-up artist prepare people for injuries (broken legs, open head, â¦). > The rehearsal should improve the coordination of several hospitals, firemenâ¦as well as the quickest possible treatment for the injured. > > One important part of the rehearsal is monitoring of what happens. This is achieved by installing a local position system and using our tool. Every injured person gets a wireless tablet. On the tablet there are UI elements that indicate treatment done to them. Whenever a doctor comes visiting the injured person activates the corresponding UI button. The events are transmitted to a server and are prepared for another analysis software. The tablet enables the HQ to make contact to individual persons or groups. The tablet measures times of needed treatments and instructs the injured to be dead if measurements weren't taken in time. > > Technically it is done in smalltalk solo. > > The server is a pharo image. It has > > - web admin interface with complex forms for managing injuries, injured, groups, etc. For this we used seaside because it is best suited for this job. Forms are done with magritte, magritte-bootstrap. The interface also displays the live incoming events and other data > - a static file server that delivers static resources to client tablets > - a websocket connector that is used by the clients to connect to the server > - a http handler to export data to other analysis tools > > The client is done with amber smalltalk. It > > - loads the web page containing amber from the server > - connects back to the server > - downloads a UI spec for the injured using the tablet to display personalized UI elements > - stores events on the tablet in case the injured is offline > - measures times to instruct the injured > > If you have any questions please don't hesitate to ask. > > Norbert

May 15, 2013

Re: [Pharo-dev] [amber-lang] [Pharo-users] success story: NTed

by Norbert Hartl

Nico, thanks for your helpful input. I will try all of these when the project enters the next phase. Well, I will measure the startup times soon because it influences the do or don't of using it in new projects. Norbert Am 15.05.2013 um 12:12 schrieb Nicolas Petton <petton.nicolas(a)gmail.com>: > Hi Norbert, > > I'm answering inside your email. If you'd like more explanations about some of the points, please just tell me. I'm also forwarding to Amber ML. > > On May 14, 2013, at 5:37 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Hi Nico, >> >>> I do have one question: what was your experience with Amber? >>> >> >> as an overall statement I would say it was a pleasure to use amber to develop the app. The initial setup until the class browser opens is easy. Learning how to create packages and knowing that code persistence is based on packages is also quite ok because amber includes a WebDav Server that can be started from the downloaded amber repo. So no big problems in starting. >> >> Thinks that go less smooth: >> >> - the web app I'm developing is checked into git. Amber puts all files (js and st) in the same directory. This makes managing files in version control system a bit cumbersome. > > One approach that worked for me and others is to ignore the .js files and recompile the .st files of your project using a git hook when you pull. > > >> - all code is put in the same directory. The amber code checked out from the repository is in the same place as the code that I produced myself. Again you need to do additional steps to do to clean it up > > You can now deal with that. loadAmber() takes additional optional arguments to deal with project paths. > >> - tools for combining code are missing. That is not a big problem because a simple cat on the console can solve this but would be nice not have to. > > bin/amberc does that. That's actually how the WebDAV of Amber is compiled into one file :) > >> - I prepared two different locations on my web server for the same app. One that is used to develop (the WebDav server access it) and one where only the combined javascript source code is used. This is needed to test the target deployment. Something that could ease this would be wonderful >> >> What keeps me from using it in every project: >> >> - The startup times for amber can be quite huge. All the class initialization is a lot of stuff that burns CPU cycle. On an iphone you don't notice really but on the Nexus 7 tablet it takes 2-4 seconds for initialization and the first page to appear. This is a not a problem for desktop browsers but for mobile ones where I find amber extremely good for. I only used amber in pre pre 1.0 versions and I know there have been optimizations that I didn't test, yet. > > The latest stable release of Amber should be *a lot* faster to load. > >> >> And the annoying "You didn't ask for but I add it anyway wishlist": >> >> - I need to test Helios because I think it solves a lot of issues with the current browser. I don't know how it is supposed to work that you have a second window with the IDE that accesses a page. But I'm sure it works flawlessly or I misunderstood it from the screenshots > > yes, it does :) > >> - retarget files on the disc. I would like to have different paths on disc for separate packages. > > You can also do that now with loadAmber() > >> - amber using websockets to connect to a backend pharo server. This can be used for comfortable code management, amber support for state transport client->server and server->client and to replicate console log to the pharo transcript (or whatever). This is important on mobile devices where sometimes you cannot access the browser console. > > ok, that's an interesting point :) > >> - it would be fine to have support for obfuscation. It is not only for hiding code but also for making it smaller thus saving bandwidth and startup times. This could be the case if the produced javascript code would be work with google closure compiler. Even better would be to have visitor for AST/IR to make it even more effective/less dangerous. > > it does work with Google Closure Compiler, there's an option in bin/amberc too for that ;) >> > > Cheers, > Nico > >> Norbert >> >> Am 14.05.2013 um 15:32 schrieb Nicolas Petton <petton.nicolas(a)gmail.com>: >> >>> Nico >>> >>> >>> On May 14, 2013, at 11:37 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> I think my last post of this message fell into the time the old mailing list dies. So here it is again >>>> >>>> --- >>>> >>>> We (@2denker in cooperation with a local university) built a monitoring tool for disaster scenario recovery rehearsals. Several times a year universities, red cross, THW und hospitals are planning a rehearsal together. For this an environment is prepared for a simulated disaster (car accidents, explosions in civil areas, â¦). The local environment is prepared to look real as well as film make-up artist prepare people for injuries (broken legs, open head, â¦). >>>> The rehearsal should improve the coordination of several hospitals, firemenâ¦as well as the quickest possible treatment for the injured. >>>> >>>> One important part of the rehearsal is monitoring of what happens. This is achieved by installing a local position system and using our tool. Every injured person gets a wireless tablet. On the tablet there are UI elements that indicate treatment done to them. Whenever a doctor comes visiting the injured person activates the corresponding UI button. The events are transmitted to a server and are prepared for another analysis software. The tablet enables the HQ to make contact to individual persons or groups. The tablet measures times of needed treatments and instructs the injured to be dead if measurements weren't taken in time. >>>> >>>> Technically it is done in smalltalk solo. >>>> >>>> The server is a pharo image. It has >>>> >>>> - web admin interface with complex forms for managing injuries, injured, groups, etc. For this we used seaside because it is best suited for this job. Forms are done with magritte, magritte-bootstrap. The interface also displays the live incoming events and other data >>>> - a static file server that delivers static resources to client tablets >>>> - a websocket connector that is used by the clients to connect to the server >>>> - a http handler to export data to other analysis tools >>>> >>>> The client is done with amber smalltalk. It >>>> >>>> - loads the web page containing amber from the server >>>> - connects back to the server >>>> - downloads a UI spec for the injured using the tablet to display personalized UI elements >>>> - stores events on the tablet in case the injured is offline >>>> - measures times to instruct the injured >>>> >>>> If you have any questions please don't hesitate to ask. >>>> >>>> Norbert >>> >>> -- >>> Nicolas Petton >>> http://www.nicolas-petton.fr >>> >>> >> >> > > -- > Nicolas Petton > http://www.nicolas-petton.fr > > -- > You received this message because you are subscribed to the Google Groups "amber-lang" group. > To unsubscribe from this group and stop receiving emails from it, send an email to amber-lang+unsubscribe(a)googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > >

May 15, 2013

Re: [Pharo-dev] AsmJit refactoring

by Esteban Lorenzano

cool :) On May 15, 2013, at 3:05 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-05-15, at 14:58, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Le 15/05/2013 14:37, Camillo Bruni a Ã©crit : >>> I started to work on a basic ARM model for AsmJit with Damien Pollet and on the fly we continue the refactoring I started last week: >>> >>> - no more PoolDictionaries >>> - no more global registers >>> - reducing the number of class variables >>> - more specific register classes for x86 to avoid nasty bit masking/checking operations on an integer >>> >>> All in all this makes the code much more accessible and you can be sure that changing a register (aka renaming it) is a local cation. >>> >>> What do you think? >>> >>> >> Really? For ARM? This is great :) > > > don't get too excited :P (we, or at least I am just about to learn the arm specs...)

May 15, 2013

[update 3.0] #30132

by Esteban Lorenzano

30132 ----- 10630 move FamFam package to Polymorph https://pharo.fogbugz.com/f/cases/10630 (second attempt) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-EstebanLore… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-TaskbarIcons-Esteba…

May 15, 2013

Re: [Pharo-dev] AsmJit refactoring

by Camillo Bruni

On 2013-05-15, at 14:58, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 15/05/2013 14:37, Camillo Bruni a Ã©crit : >> I started to work on a basic ARM model for AsmJit with Damien Pollet and on the fly we continue the refactoring I started last week: >> >> - no more PoolDictionaries >> - no more global registers >> - reducing the number of class variables >> - more specific register classes for x86 to avoid nasty bit masking/checking operations on an integer >> >> All in all this makes the code much more accessible and you can be sure that changing a register (aka renaming it) is a local cation. >> >> What do you think? >> >> > Really? For ARM? This is great :) don't get too excited :P (we, or at least I am just about to learn the arm specs...)

May 15, 2013

Re: [Pharo-dev] AsmJit refactoring

by Goubier Thierry

Le 15/05/2013 14:37, Camillo Bruni a Ã©crit : > I started to work on a basic ARM model for AsmJit with Damien Pollet and on the fly we continue the refactoring I started last week: > > - no more PoolDictionaries > - no more global registers > - reducing the number of class variables > - more specific register classes for x86 to avoid nasty bit masking/checking operations on an integer > > All in all this makes the code much more accessible and you can be sure that changing a register (aka renaming it) is a local cation. > > What do you think? > > Really? For ARM? This is great :) 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

May 15, 2013

Support from printer device

by Dario Trussardi

Ciao, thanks for the development, from my point of view is fantastic ! ! ! ! ! Now for my application, i need to print ticket with a specific printer device. The device is managed with specific command: LF CR ESC 2 ESC 3 ......... Someone to work around this problem? There is something to start with, even a minimal framework about it? Thanks for any considerations, Dario

May 15, 2013