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

Re: [Pharo-users] Mocketry: what is used of #where ?

by Herbert VojÄÃk

Denis Kudriashov wrote: > Hi Herbert. > > It is a bit experimental API to allow more descriptive failures. > Evaluate following code: > > > (2@3) where x should equal: 10 > > It will give you failure message: Got "2" from (2@3) x but it should > equal "10". > But without #where it would be: Got "2" but it should equal "10". > > And it works with long message chains: > > (2@3 corner: 10@30) where origin x should equal: 10 > > It will show: Got "2" from (2@3) corner: (10@30) origin x but it should > equal "10". So in my case, I could see difference in something like this? responseCheck := (znClient username: (self uidy: 'Q7') asString, '/TEST' password: 'tk'; timeout: 1; post; response) where. responseCheck should be isSuccess. responseCheck where contentType should equal: ZnMimeType applicationJson. responseCheck where entity should not be: nil. In that case it would be nice to be able to write something like: (znClient username: (self uidy: 'Q7') asString, '/TEST' password: 'tk'; timeout: 1; post; response) where: [ :response | response should be isSuccess. response where contentType should equal: ZnMimeType applicationJson. response where entity should not be: nil ]. > I am still not sure is it good approach or not. But that is idea. > Besides It is possible to retrieve such information using magic with > thisContext and reflectivity. But again the question is same: does it > really make sense to do it for assertions? > > Best regards, > Denis > > > > 2018-05-04 16:28 GMT+03:00 Herbert VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>>: > > Hello, > > When I am writing tests using Mocketry's DSL, I get puzzled about > how / when to use #where, and how is it different when it's used and > when it is not? > > As far as i tried, I did not find any difference. That is, pasting > part of one of my tests: > > response := znClient > username: (self uidy: 'Q7') asString, '/TEST' > password: 'tk'; > timeout: 1; post; response. > response should be isSuccess. > response where contentType should equal: ZnMimeType > applicationJson. > response where entity should not be: nil. > (STON fromString: response entity contents) should equal: nil > > I get the same result (pass if ok, failure with DNU when thing is > not present) whether `where` is there or isn't. > > Could you explain what is it's purpose and correct usage? > > Thanks, Herby > >

May 4, 2018

Re: [Pharo-users] Saving a Smalltalk Project

by serge.stinckwich＠gmail.com

Arduinos&Raspberry boards + Lora radio board EnvoyÃ© de mon iPhone > Le 3 mai 2018 Ã 02:40, Todd Blanchard <tblanchard(a)mac.com> a Ã©crit : > > OK, so I'm curious what hardware platforms you guys use for your "things"? > > Been doing things with Particle lately. Interested to try their new mesh offering. > >> On May 2, 2018, at 12:30 PM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >> If they are interested, we can get in touch. We are working on IoT for environmental monitoring and Iâm working in Cameroon. >> >> Regards, >> >> EnvoyÃ© de mon iPad >> >>> Le 2 mai 2018 Ã 19:21, horrido <horrido.hobbies(a)gmail.com> a Ã©crit : >>> >>> I received the following message: >>> >>> *We started off doing a small project in conservation in South Africa that >>> involved tracking Rhinos in a remote GPS denied environment and ended up >>> with some impressive building blocks for a Big Data Platform for IoT. The >>> platform includes its own GIS subsystem and parts of an Expert System. >>> >>> Due to the choice made by my business partner and handful of contractors the >>> platform ended up being built in Smalltalk on Squeak VM and the Magma >>> Object Database. >>> >>> We now believe we may have the beginning of a commercial platform however >>> its notoriously difficult to find Smalltalk developers so I am in half minds >>> to migrate to a platform which uses a more mainstream language (Java / >>> Python) as I have been getting some strange reactions from Angel Investors / >>> VCs and mainstream developers. >>> >>> ... >>> >>> I wanted to ask you if you have information on how big the Smalltalk >>> community is and whether its better to migrate to Pharo from Squeak and what >>> types of recent industrial projects youve come across that use Smalltalk? >>> >>> Also I wondered if you know of any active smalltalk group in Silicon Valley >>> and what are the best forums for professional SmallTalk development.* >>> >>> I would very much like to save their project as a Smalltalk project. The >>> principal issue seems to be finding enough Smalltalk developers. I don't >>> know if they need on-site developers or if remote developers can pass >>> muster. I strongly suspect the former. >>> >>> How hard would it be to find Smalltalkers willing to work in Silicon Valley, >>> or South Africa? >>> >>> What is the best response to this person? Thanks. >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >> > >

May 4, 2018

Re: [Pharo-users] Mocketry: what is used of #where ?

by Sean P. DeNigris

Denis Kudriashov wrote > It will give you failure message: Got "2" from (2@3) x but it should equal > "10". > But without #where it would be: Got "2" but it should equal "10". Wow, that sounds really cool. I'll have to play with it a bit to see how much difference it makes in practiceâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 4, 2018

Pharo developers wanted in Toronto

by aglynn42＠gmail.com

Telna is looking for developers with Smalltalk experience, preferably Pharo, in Toronto Canada. The role is listed on indeed.ca if anyone is interested. Andrew Glynn

May 4, 2018

Re: [Pharo-users] Mocketry: what is used of #where ?

by Denis Kudriashov

Hi Herbert. It is a bit experimental API to allow more descriptive failures. Evaluate following code: (2@3) where x should equal: 10 It will give you failure message: Got "2" from (2@3) x but it should equal "10". But without #where it would be: Got "2" but it should equal "10". And it works with long message chains: (2@3 corner: 10@30) where origin x should equal: 10 It will show: Got "2" from (2@3) corner: (10@30) origin x but it should equal "10". I am still not sure is it good approach or not. But that is idea. Besides It is possible to retrieve such information using magic with thisContext and reflectivity. But again the question is same: does it really make sense to do it for assertions? Best regards, Denis 2018-05-04 16:28 GMT+03:00 Herbert VojÄÃk <herby(a)mailbox.sk>: > Hello, > > When I am writing tests using Mocketry's DSL, I get puzzled about how / > when to use #where, and how is it different when it's used and when it is > not? > > As far as i tried, I did not find any difference. That is, pasting part of > one of my tests: > > response := znClient > username: (self uidy: 'Q7') asString, '/TEST' password: > 'tk'; > timeout: 1; post; response. > response should be isSuccess. > response where contentType should equal: ZnMimeType > applicationJson. > response where entity should not be: nil. > (STON fromString: response entity contents) should equal: nil > > I get the same result (pass if ok, failure with DNU when thing is not > present) whether `where` is there or isn't. > > Could you explain what is it's purpose and correct usage? > > Thanks, Herby > >

May 4, 2018

Mocketry: what is used of #where ?

by Herbert VojÄÃk

Hello, When I am writing tests using Mocketry's DSL, I get puzzled about how / when to use #where, and how is it different when it's used and when it is not? As far as i tried, I did not find any difference. That is, pasting part of one of my tests: response := znClient username: (self uidy: 'Q7') asString, '/TEST' password: 'tk'; timeout: 1; post; response. response should be isSuccess. response where contentType should equal: ZnMimeType applicationJson. response where entity should not be: nil. (STON fromString: response entity contents) should equal: nil I get the same result (pass if ok, failure with DNU when thing is not present) whether `where` is there or isn't. Could you explain what is it's purpose and correct usage? Thanks, Herby

May 4, 2018

Re: [Pharo-users] [Seaside] [ANN] TelescopeCytoscape for Seaside v1.0.0

by Mariano Martinez Peck

I will just join the rest of the public thanking Cyril! It's very nice to see more people pushing and evolving Seaside! Thank you! On Thu, May 3, 2018 at 11:36 PM, Chris Muller <asqueaker(a)gmail.com> wrote: > Oh my that looks geared and ready to do Maui in the browser! > > This is exciting! > > A nice set of demos, well done... > > On Thu, May 3, 2018 at 10:29 AM, Cyril Ferlicot D. > <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > > > Telescope is an engine for efficiently creating meaningful > > visualizations. It allow users to create models of visualizations and to > > render them via connectors to visualization frameworks. > > > > Until now, it was hosted on SmalltalkHub and we just migrated it to > Github. > > > > https://github.com/TelescopeSt/Telescope > > > > We also finished the v1.0.0 of the CytoscapeJs > > (http://js.cytoscape.org/) Telescope connector. It is build on top of > > Seaside to use visualizations as components. > > > > You can find the project at: > > https://github.com/TelescopeSt/TelescopeCytoscape > > > > And a demo at: https://demos.ferlicot.fr/TelescopeDemo > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

May 4, 2018

Re: [Pharo-users] Pharo70 session start and silent failures

by Denis Kudriashov

I had similar problem with SSDP server. When I tried to stop it during shutdown of image the image didn't closed. It hangs forever. In some cases I was able to open debugger which pointed to exactly same place which you mentioned. My guess was that process termination during shutdown is not safe anymore. But I had no time to check deeply. 2018-05-03 16:13 GMT+03:00 Holger Freyther <holger(a)freyther.de>: > I am facing a problem with the new SessionManager>>#snapshot:andQuit: > code. I have had plenty Pharo70 images that didn't restore anymore as the > code is waiting for the "wait" semaphore. For sure it is something my code > is doing but could anyone think of ways to make it more robust and handle > failures more gracefully? My main concerns are: > > * When the failure becomes noticeable it is too late. :( > * It fails silently. Maybe WorkingSession>>#runStartup: shouldn't rely on > the UIManager doing the right thing (before the UI was fully initialized?) > * Debugging is hard, there is no indication of why it broke, and getting > to the situation of breakage takes a bit of time (installing the > baseline..). > > holger > > > >

May 4, 2018

Re: [Pharo-users] [ANN] ChartJs for Seaside v1.0.0

by Cyril Ferlicot D.

On 04/05/2018 10:40, Ben Coman wrote: > > > There seems something wrong with the 1D Demo values. > Sleeping is more important than Coding? ... ;) > Of course :P > > Looks real nice, but I'm getting a 10 second delay changing between > demos.Â Is it running on a shared server? > cheers -benÂ > I have many seaside demo on this server. That might be the problem. -- Cyril Ferlicot https://ferlicot.fr

May 4, 2018

Re: [Pharo-users] [ANN] ChartJs for Seaside v1.0.0

by Ben Coman

On 4 May 2018 at 16:12, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > On 04/05/2018 10:09, Ben Coman wrote: > > > > Sounds cool, but I got "404 Not Found" > > > > Arf, I used the wrong link. > > The good one is: https://demos.ferlicot.fr/ChartJsDemo > > Thank you for the report > > There seems something wrong with the 1D Demo values. Sleeping is more important than Coding? ... ;) Looks real nice, but I'm getting a 10 second delay changing between demos. Is it running on a shared server? cheers -ben

May 4, 2018