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

Re: [Pharo-users] a 'doesNotUnderstand' message that I do not understand...

by Alain Busser

So it was that simple! Thanks alot for these messages, now I will be able to make *new* and *classy* things instantly :-D Alain On Tue, May 14, 2013 at 10:21 PM, Chris <cpmbailey(a)btinternet.com> wrote: > This method is on the instance side of the class and therefore requires > TextEditorDialogWindow new newTextEditorMorph. If it were on the class > side, it would be like you were trying it. > > Hi all, > > Exploring the system browser (Pharo 2.0), I see that there exists a class > called TextEditorDialogWindow; as this name sounds interesting to me, I > want to test one, and I see that there is only one method in the category > 'create': this method is called newTextEditorMorph. So, I send the > message newTextEditorMorph to the class TextEditorDialogWindow, daring a: > > TextEditorDialogWindow newTextEditorMorph > > At the 'Do It', I get this error message: 'TextEditorDialogWindow > class(Object) doesNotUnderstand: #newTextEditorMorph' > > That's what I don't understand: If the class has a method called this > way, why does it not understand the corresponding message? What did I miss? > > Alain > > >

May 15, 2013

Re: [Pharo-users] InputEventSensor and polling

by stephane ducasse

Hi eric > Hi all, > I've been working on Phratch, a port of MIT Scratch to Pharo, mostly to learn Smalltalk and also because Scratch is a great learning environment and I can't bear to see it end up in Flash. > > So I've been digging about in the old code to fix bugs and I'm getting a sense that there's some conflict between the way the Scratch team got things working in Squeak, and the way the Pharo team things want things done. > > I must say I think the Pharo team have things right in their drive for a cleaner, simpler system, however that means I'm a bit stuck. > > See the attached image of my Scratch script. > > Here's where I am... > 1. Keyboard events for 'When <key> pressed' HatBlockMorph (with then pen commands) work fine as these follow the regular Morphic event model > 2. But 'if <key> pressed' operation (with the stamp command inside) doesn't work because it relies on polling the InputEventSensor, and I think this bit of this class doesn't work as I expect. > > My view right now is that for 2, I need to use some kind of polling, and InputEventSensor has methods such as keyboardPeek and peekKeyboardEvent that imply you can poll, Why do you need to poll for event? In Pharo 30 we should integrate a fix and normally you can just register to get notified when a new event is happening. May be have a look at the EventModel package http://www.squeaksource.com/EventModel/ I hope it gets the latest version of the code. Fernando used it in gaucho so soon it will be in Pharo3.0 but we should do another serious pass on it. > but looking at the implementation, which uses WaitfreeQueue I can see that calling these methods results in events being consumed, hence my post to Stack Overflow... > http://stackoverflow.com/questions/16395418/cant-peek-keyboard-events-multi… > > I've hacked around to come up with something that sort of works, outlined in this post: > http://stackoverflow.com/questions/16495436/saving-modifications-to-existin… > ...but I get the feeling I'm doing the wrong thing here, and that I should come up with a solution that better fits the 'Pharo way'. > > So, let me know what you think. I'm happy to provide more info and to research better solutions, let me know... > > Finally, apologies for the long post! > > Best regards, > -Eric. > > -- > Eric Clack > ericclack(a)googlemail.com > East Sussex, England. > <keypress.gif>

May 15, 2013

Re: [Pharo-users] Zn maximumEntitySize

by Pierce Ng

On Tue, May 14, 2013 at 01:51:15PM +0200, Sven Van Caekenberghe wrote: > If you do > ConfigurationOfZincHTTPComponents project bleedingEdge load. > from > http://mc.stfx.eu/ZincHTTPComponents > you will find some new ZnServerTests > http://ws.stfx.eu/D8X1CFAEQODI Cool! I'll try that. Thanks again Sven. -- Pierce Ng http://samadhiweb.com/blog/

May 15, 2013

Re: [Pharo-users] Zn maximumEntitySize

by Pierce Ng

On Mon, May 13, 2013 at 03:58:12PM +0200, Sven Van Caekenberghe wrote: > ZnEntityTooLarge is a condition that is signaled by the server when it is > receiving (reading) an incoming entity that is too large. This is done to > protect the server. This condition is only applicable to ZnEntity and > subclasses. A ZnRequest consists of other parts as well (request line and > headers). For these other conditions apply: ZnLineTooLong and > ZnTooManyDictionaryEntries. > > In the above example, you could try to add 4096 $a's to trigger a > ZnLineTooLong. > > To trigger ZnEntityTooLarge you should PUT or POST data. Sven, thanks for your explanation. I did trigger ZnLineTooLong during my experimentation. -- Pierce Ng http://samadhiweb.com/blog/

May 15, 2013

InputEventSensor and polling

by Eric Clack

Hi all, I've been working on Phratch, a port of MIT Scratch to Pharo, mostly to learn Smalltalk and also because Scratch is a great learning environment and I can't bear to see it end up in Flash. So I've been digging about in the old code to fix bugs and I'm getting a sense that there's some conflict between the way the Scratch team got things working in Squeak, and the way the Pharo team things want things done. I must say I think the Pharo team have things right in their drive for a cleaner, simpler system, however that means I'm a bit stuck. See the attached image of my Scratch script. Here's where I am... 1. Keyboard events for 'When <key> pressed' HatBlockMorph (with then pen commands) work fine as these follow the regular Morphic event model 2. But 'if <key> pressed' operation (with the stamp command inside) doesn't work because it relies on polling the InputEventSensor, and I think this bit of this class doesn't work as I expect. My view right now is that for 2, I need to use some kind of polling, and InputEventSensor has methods such as keyboardPeek and peekKeyboardEvent that imply you can poll, but looking at the implementation, which uses WaitfreeQueue I can see that calling these methods results in events being consumed, hence my post to Stack Overflow... http://stackoverflow.com/questions/16395418/cant-peek-keyboard-events-multi… I've hacked around to come up with something that sort of works, outlined in this post: http://stackoverflow.com/questions/16495436/saving-modifications-to-existin… ...but I get the feeling I'm doing the wrong thing here, and that I should come up with a solution that better fits the 'Pharo way'. So, let me know what you think. I'm happy to provide more info and to research better solutions, let me know... Finally, apologies for the long post! Best regards, -Eric. -- Eric Clack ericclack(a)googlemail.com East Sussex, England.

May 15, 2013

Re: [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-users] [amber-lang] [Pharo-dev] 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

Fwd: do:displayingProgress: Question/Problem

by Juan Ignacio Vaccarezza

Hi all I detected a behavior and Im not sure how to classify it (most sure is ignorance :P). Maybe some one can explain me. Given the code: *Smalltalk allClasses do:[:aClass| (Delay forMilliseconds: 1) wait] displayingProgress:[:aClass| 'Processing ', aClass name].* (Which is the example on the Collection class) In 1.4 the result is a dialog that shows a progres bar titled with each classname In 2.0 the result is a dialog showing only a progress bar. Thanks in advance, Juan

May 15, 2013

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

by Nicolas Petton

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

May 15, 2013

Old Malinglists: delivering slowly

by Marcus Denker

Hi, So the old lists started to deliver the mails send over the last week slowly. I have put them on emergency moderation, so please use the new list to answer. Marcus

May 15, 2013