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

Re: [Pharo-dev] [update 3.0] #30125

by Esteban Lorenzano

May 14, 2013

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

by Norbert Hartl

Good idea. I need to collect them first from mobile devices and other systems. Until then here are some of the admin interface (it's all in german) Norbert Am 14.05.2013 um 11:43 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Great success story, Norbert, it is really good to hear it ! > > One request though: sexy screenshots ;-) > > Sven > > On 14 May 2013, at 11:37, 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 > > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

May 14, 2013

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

by Sven Van Caekenberghe

Great success story, Norbert, it is really good to hear it ! One request though: sexy screenshots ;-) Sven On 14 May 2013, at 11:37, 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 -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

May 14, 2013

success story: NTed

by Norbert Hartl

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 14, 2013

Re: [Pharo-project] XPath issue ?

by StÃ©phane Ducasse

herve did you try pastell? Stef On May 8, 2013, at 11:23 PM, Herve Verjus <herve.verjus(a)univ-savoie.fr> wrote: > Dear All, > > I try a very simple example: > > mydoc.xml document: > > > <?xml version="1.0" encoding="UTF-8" ?> > > <first> > <second> > <item type="attvalue">nodevalue</item> > </second> > </first> > > > And the Pharo code found in the book.pharo-project.org: > > | doc results | > doc := XMLDOMParser parseFileNamed: 'mydoc.xml'. > results := ( XPath for: 'first' ) in: doc. > results explore > > > As a result, I obtain an empty OrderedCollection...It should contain an element. Then a make some changes using different XPath expressions (i.e. '/first/second/item/@type", etc.) but no way. > > Then I discover the first element of the XPath expression must not be the root of the XML doc. If I change the mydoc.xml, introducing a new root element: > > > <?xml version="1.0" encoding="UTF-8" ?> > > <foo> > <first> > <second> > <item type="attvalue">nodevalue</item> > </second> > </first> > </foo> > > Everything is ok (the same code as above). Here, XPath assumes that the first tag we are looking for is not the root of the doc, otherwise it fails. I'm not so sure but it seems that such implementation doesn't follow the XPath specs. I tried another example from http://www.w3schools.com/xpath/xpath_syntax.asp and same results: I obtain an empty collection when using an XPath expression beginning with the 'bookstore' tag, the root element of the doc: > > | doc results | > doc := XMLDOMParser parseFileNamed: 'books.xml'. > results := ( XPath for: '/bookstore' ) in: doc. > results explore > > Maybe, I missed something... > > Note: I have had to replace the isTag (deprecated) with isElement in some piece of XPath code. > > Cheers, > > Herve >

May 14, 2013

Re: [Pharo-dev] [update 3.0] #30125

by Camillo Bruni

May 14, 2013

Re: [Pharo-dev] [update 3.0] #30125

by Sven Van Caekenberghe

May 14, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 14, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 14, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 14, 2013