April 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Send smartphone message from Pharo and Gemstone

by Trussardi Dario Romano

Ciao Max, thanks. > Hi Dario, > > We use a service provider called eCall to do that for us. They provide an API (not a nice one). Of course they charge us. > > Using a service provider is the simplest way in my opinion. Not sure if you'd even need some sort of governmental approval to hook into the network. > > By âmessageâ du you mean text messages as in SMS? Yes, i need to send text message as in SMS. Dario > > Cheers, > Max > >> On 29 Apr 2016, at 12:24, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> wrote: >> >> Ciao, >> >> from my application ( development into Pharo and deployment into Gemstone ) >> >> i'm interested to send messages to the users smartphone. >> >> Considerations about it ? >> >> Thanks, >> >> Dario >> > >

April 29, 2016

Re: [Pharo-dev] Logging API discussion

by Denis Kudriashov

Hi Tudor. I think I super bad in explaining things because you not answer my question. As you said we should encourage people to create typed signals. I am not against it. But I try to explain that approach of Beacon is wrong. It is wrong to make this signals be subclasses of Beacon core component BeaconSignal. We have in Pharo 307 subclasses of Announcements (only 78 have some kind of time variable). Do not they all are signals for logging? But only way how to log them in Beacon is to wrap them by kink of WrapperSignal. Does my issue is clear now? At the end we will got logs with mix of normal events which created specially for logs and WrapperSignal's containing original application events. 2016-04-28 23:39 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi Denis, > > On Apr 28, 2016, at 4:43 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > > 2016-04-28 14:51 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > It is not the most elegant solution, but it is very malleable and good > enough for debugging purposes. If we would have instance-based filtering > for announcements, we could filter based on that without any extra effort. > Also, if we would have a composition mechanism in place, we could build > these objects with a more elegant API. > > Regarding your statement of logging domain objects, you will have to store > these objects with the additional information somewhere, and that will be a > wrapper class. I do not see the difference with the Signal. > > Difference with Beacon is that users will not depends on objects from > logging library. Nobody needs to subclass core components like Signal. > Instead domain objects will be added to logs inside general LogEntry > instances which will be hidden from user and only available inside logs. > And LogEntry will allow include additional information to itself by > appropriate logging API. > > Question is: does it better? > And this is what problem I see around Beacon: > > Beacon proposes to design log entries as events, as subclasses of > BeaconSignal. If nothing else exists it is good. We will see in logs > collection of such events. > But what to do with existing domain events which has no relation to logs? > How to log them if we decide to do it? > > They can be added to log inside WrapperSignal. But then we will see in > logs mix of normal events which created specially for logs and > WrapperSignal's containing original application events. > But both type of events belong to same application. We definitely want to > see them and to work with them in same way everywhere (especially inside > logs) > > Tudor what do you think about this problem? Maybe I misunderstood Beacon. > > > Thanks for the dialogue. I think the most important part is to identify > concerns and now we are getting concrete. So, letâs see :). > > Your LogEntry is exactly the same as BeaconSignal. There is no difference. > You will also need to transport the LogEntry from your application to the > logger object. Beacon reuses the Announcement framework to do just that. If > you avoid the Announcement framework, you will implement another engine > that has essentially the same responsibility. I think it is better to > consolidate in this case. > > So, I see no downside of using Beacon for your purpose. > > But, I think there is more. One example where we have an event that is > often worthwhile preserving is an Exception. In Beacon there is an > out-of-the-box ExceptionSignal. This is not just a wrapper around the > exception, but it also decides what to log from an Exception. For example, > in order to ensure that we can have proper navigation of the exception, we > capture the RB nodes for each stack entry. This is a naive implementation > and we should certainly improve it (for example, we would need to delegate > the computation of the stack information as late as possible), but it > exemplifies how when you log you want to choose what to log. It can be that > in another situation, we want to log the whole context of the exception. > Furthermore, because we have a typed signal, we can also have a Stack > presentation that depends on the strategy we used to log, not on the object > that we logged. I believe this is a recurrent case. > > Nothing would prevent us from logging the exception through a plain > WrapperSignal either. Only in that case we would not have the extra > information that the ExceptionSignal provides. So, from this point of view, > the ability to create types of signals is not a limitation, but an added > value. That is why in my message I said that we should encourage people to > create typed signals, but we should not enforce that. > > > You mentioned that maybe your event object has a timestamp already. This > timestamp is not the same as the logging timestamp, and it should be > treated separately. If it is the same, that situation is so rare that I > doubt we should optimize the whole framework around such a problem. > > Does this make sense? > > Cheers, > Doru > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Sometimes the best solution is not the best solution." > >

April 29, 2016

Re: [Pharo-dev] Send smartphone message from Pharo and Gemstone

by Max Leske

Hi Dario, We use a service provider called eCall to do that for us. They provide an API (not a nice one). Of course they charge us. Using a service provider is the simplest way in my opinion. Not sure if you'd even need some sort of governmental approval to hook into the network. By âmessageâ du you mean text messages as in SMS? Cheers, Max > On 29 Apr 2016, at 12:24, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> wrote: > > Ciao, > > from my application ( development into Pharo and deployment into Gemstone ) > > i'm interested to send messages to the users smartphone. > > Considerations about it ? > > Thanks, > > Dario >

April 29, 2016

Send smartphone message from Pharo and Gemstone

by Trussardi Dario Romano

Ciao, from my application ( development into Pharo and deployment into Gemstone ) i'm interested to send messages to the users smartphone. Considerations about it ? Thanks, Dario

April 29, 2016

Re: [Pharo-dev] Collection with spatiotemporal indexation - Ideas and discussions ?

by Henrik Johansen

I agree with Alistair; a pattern like EventSourcing works well for building efficient query structures for a set of data along different as-yet-to-be-determined dimensions. In Pharo terms, you can implement this using a EventStream that announces new entries, then install announcement handlers each updating a dimension-specific data structure. Also makes it easy to add new dimensions if you find you need them; simply add a new handler and replay the EventStream (with the other handlers temporarily disabled). Cheers, Henry > On 23 Apr 2016, at 2:13 , CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > Hi Alistair, > > Thanks, this sounds like a nice suggestion. > > I have to think about it. > Adding altitude would be also interesting in some cases but not as a start (quite limited usage). > > When you say to package it separately, youâre talking about Geolocation, Spatiotemporal classes ? or also the collection ? > I can try something but I think this will deserve more Â« computational thinking Â» power than I have ^^ > > Cheers, > > CÃ©drik > >> Le 23 avr. 2016 Ã 13:57, Alistair Grant <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>> a Ã©crit : >> >> I don't have a data structures book handy, but how about 3 SortedCollections? (Assuming 3 dimensions: latitude, longitude & time). >> >> It would support a reasonably efficient binary search, and allow for areas and time ranges. >> >> Regardless of which solution you choose I agree that it would be a useful general class, so please package it separately. >> >> Cheers, >> Alistair >> (Sent from my mobile) >> >> On 23/04/2016 1:47 PM, "CÃ©drick BÃ©ler" <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >> A dictionary with keys being the timestamp or the spatiotemporal object would probably do it... >> I think Iâll do that but I wonder if there are better solutions out there ^^. >> >> Cheers, >> >> CÃ©drik >

April 29, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50735 Home: https://github.com/pharo-project/pharo-core

April 29, 2016

[pharo-project/pharo-core] 23693c: 50735

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 23693cf982f632740934bc5879abd35314a3a138 https://github.com/pharo-project/pharo-core/commit/23693cf982f632740934bc58… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-29 (Fri, 29 Apr 2016) Changed paths: R BlueInk-Tests.package/BIConfigurableFormatterTest.class/README.md R BlueInk-Tests.package/BIConfigurableFormatterTest.class/definition.st M GT-EventRecorder.package/GlobalIdentifierFuelPersistence.class/instance/load and saving/load.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50734.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50735.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50734.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50735.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50735 18135 On issue tracker: GlobalIdentifierWithFuel failing now https://pharo.fogbugz.com/f/cases/18135 18134 BIConfigurableFormatterTest is empty and useless https://pharo.fogbugz.com/f/cases/18134 http://files.pharo.org/image/50/50735.zip

April 29, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50734 Home: https://github.com/pharo-project/pharo-core

April 29, 2016

[pharo-project/pharo-core] ba6d49: 50734

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ba6d492605af1dbb09aaca265e2a00cd59de91ef https://github.com/pharo-project/pharo-core/commit/ba6d492605af1dbb09aaca26… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-04-29 (Fri, 29 Apr 2016) Changed paths: A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline10_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline11_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline12_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline15_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline16_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline17_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline181_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline182_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline18_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline192_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline193_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline194_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline19AlphaForTanker_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-1/baseline19_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-2/baseline200_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines-2/baseline210_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline10_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline11_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline12_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline15_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline16_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline17_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline181_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline182_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline18_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline192_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline193_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline194_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline19AlphaForTanker_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline19_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline200_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/baselines/baseline210_.st M ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/symbolic versions/stable_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version10_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version11_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version12_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version13_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version14_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version15_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version161_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version16_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version17_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version181_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version182_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version18ForMarea_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version18_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version18beta1_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version191_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version192_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version193_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version194_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version19AlphaForTanker_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-1/version19_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version200_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version201_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version210_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version211_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version212_.st A ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions-2/version213_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version10_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version11_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version12_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version13_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version14_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version15_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version161_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version16_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version17_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version181_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version182_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version18ForMarea_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version18_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version18beta1_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version191_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version192_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version193_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version194_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version19AlphaForTanker_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version19_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version200_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version201_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version210_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version211_.st R ConfigurationOfFuel.package/ConfigurationOfFuel.class/instance/versions/version212_.st M Files.package/File.class/instance/streaming/readStreamDo_.st M Files.package/File.class/instance/streaming/writeStreamDo_.st M Fuel.package/FLMaterializer.class/class/materializing-shortcuts/materializationFromFileNamed_.st M Fuel.package/FLMaterializer.class/class/materializing-shortcuts/materializationHeaderFromFileNamed_.st M Fuel.package/FLSerializer.class/instance/serializing/serialize_toFileNamed_.st M FuelPlatform.package/FLPharo1Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLPharo2Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLPharo3Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLPharo4Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLPharo5Platform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLPharo5Platform.class/instance/accessing-files/fileNamed_writeStreamDo_.st M FuelPlatform.package/FLPlatform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLPlatform.class/instance/accessing-files/fileNamed_writeStreamDo_.st M FuelPlatform.package/FLSqueakPlatform.class/instance/accessing-files/fileNamed_readStreamDo_.st M FuelPlatform.package/FLSqueakPlatform.class/instance/accessing-files/fileNamed_writeStreamDo_.st M Kernel-Tests.package/BehaviorTest.class/instance/tests/testBehaviorRespectsPolymorphismWithTraitBehavior.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50733.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50734.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50733.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50734.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50734 18107 Failing on windows: GlobalIdentifierWithFuel>>#testBackwardCompatibility4 https://pharo.fogbugz.com/f/cases/18107 18119 Failing again: BehaviorTest>>>#testBehaviorRespectsPolymorphismWithTraitBehavior https://pharo.fogbugz.com/f/cases/18119 18131 File>>readStreamDo: and #writeStreamDo: should answer block value https://pharo.fogbugz.com/f/cases/18131 http://files.pharo.org/image/50/50734.zip

April 29, 2016

Re: [Pharo-dev] new collaborators in Pharo 5

by Max Leske

mml is me. I use that for stuff at Netstyle and mixed it up :) > On 29 Apr 2016, at 10:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > So, according to my script, this are the new collaborators (people who started contributing after 1st march 2015): > > Maxleske > CyrilFerlicot > Latsabben > Nicolaihess > synectique > BorisSpasojevic > Stef > Bite > hn > SvenVanCaekebenberghe > StefnReichhart > NicoPasserini > DEMAREYChristophe > HenrikNergrd > SkipLentz > Spirita > Fuel > TravisCI > HolgerHansPeterFreyther > SpurBootstrap > qdq > SergioFedi > jeanbaptisteArnaud > AutoGenTutorial > PabloTesone > ThomasHeniart > ValentinRyckewaert > mml > HenrikNergaard > MarcusDenkr > DenisKudriashov > Alexandre > mcamp > Matthieu > w3ertyu > VincentBlondeauAbdelghaniAlidra > TH > MerwanOuddane > ChristopherCoat > AlainRastoul > FranckWarlouzet > AbdelghaniLaidra > ThibaultArloing > pad > RogerStebler > DavidAllouche > RM > tr > > Obviouslyâ¦ many are wrong since they started contributing a lot before (like Sven and Stef :P â¦ I wonder why the difference gave me thisâ¦ but wellâ¦ ) > > Anyway, I need to know who are this guys: > > - synectique (I suppose is Guillome, Usman or Cyril) > - Bite (I hope this is not a french guy, because in that case is soooooo rudeâ¦ or proud of himself :P) > - hn > - Spirita > - qdq > - mml > - Alexandre (Bergel?) > - mcamp > - Matthieu > - w3ertyu > - TH > - pad > - RM > - tr > > Soâ¦ any hints about authors? > > thanks, > Esteban

April 29, 2016