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

Re: [Pharo-users] #ast vs. #parseTree

by Ben Coman

On 4 May 2018 at 08:02, Ramon Leon <ramon.leon(a)allresnet.com> wrote: > On 05/03/2018 12:02 PM, Guillermo Polito wrote: > >> I don't think so... any compiler book talks about ASTs using acronyms. >> Acronyms are good when acronyms are good. >> > > Boo, acronyms bad, virtually always. Jargon is awful when speaking and > awful when Smalltalk'ing, use words, they're not in short supply. > > a TMA situation?

May 4, 2018

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

by Cyril Ferlicot D.

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 > cheers -ben > -- Cyril Ferlicot https://ferlicot.fr

May 4, 2018

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

by Ben Coman

On 3 May 2018 at 23:27, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Hi! > > I'm happy to announce the release v1.0.0 of ChartJs for Seaside. > > This is a binding of ChartJs v1. We did not got the time to bind v2 of > ChartJs. > > v1.0.0 includes: > Creation of 1D charts > Creation of 2D charts > Creation of Boxplots > Callbacks on 1D and 2D charts > Tooltips on charts > Style customization > ... > > The project can be found at: https://github.com/DuneSt/ChartJs > > Demo at: https://demos.ferlicot.fr/ChartJs > Sounds cool, but I got "404 Not Found" cheers -ben

May 4, 2018

Re: [Pharo-users] Saving a Smalltalk Project

by ClÃ©ment Bera

That is the answer I would give: Biggest Smalltalk community in Silicon valley is likely the Lam Research one (dozens of devs). On my blog post talking about Smalltalk, I have 2k views per Smalltalk community-wide audience post, so the community is at least that big. Smalltalk conferences (Smalltalks and Esug) have usually around 200 attendees. To hire Smalltalk developers, a job offer mail through esug or pharo mailing list is one of the best way to get people to apply, other solutions include giving a 10 min talk at ESUG (Europe) or Smalltalks (Argentina) conference and say loud and clear you are hiring (people may be able to move to other countries). Getting a few developers should not be that hard if you accept remote positions. Migrating from Squeak to Pharo is something to discuss with the developers you hire, things like IoT and Magma DB support might not be easy to port, so it is difficult to tell with the little information provided. Pharo's community is likely the easiest to hire new Smalltalk developers though, and you can check the Pharo consortium website for support and success stories to ease communication with your investors and partners. On Wed, May 2, 2018, 20:21 horrido <horrido.hobbies(a)gmail.com> wrote: > 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] #ast vs. #parseTree

by Sven Van Caekenberghe

> On 3 May 2018, at 10:56, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > How about: #newAst & #cachedAst? Best suggestion yet. +1 > Cheers, > Doru > > >> On May 3, 2018, at 9:30 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> method newAst ? >> >> On Wed, May 2, 2018 at 11:03 PM, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> wrote: >> a "parse tree" is not equal to an "ast"(abstract syntax tree) >> but its difficult to find a name for an ast that is not cached. >> maybe >> parsedAst >> parseAst >> .... >> >> >> On Wed, May 2, 2018 at 3:28 PM, Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: >> On Wed, May 2, 2018 at 11:06 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> Hi. >> >> Maybe #parseSourceCode would be better name for #parseTree. >> >> I've always found it good advice to avoid using a verb phrase to name something which does not entail some kind of action. >> #parseSourceCode realy reads like something which would parse the source code. #parseTree also has that effect, except for the lack of a tree to parse. >> >> >> >> 2018-05-02 16:33 GMT+03:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >> >>> On 27 Apr 2018, at 21:36, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> >>> Marcus Denker-4 wrote >>>> I will add commentsâ¦ >>> >>> I got confused by this again and created an issue: >>> https://pharo.manuscript.com/f/cases/21806/Document-Difference-between-ast-… >>> >>> And then Peter Uhnak reminded me on Discord about this thread. I'm happy to >>> add the comments, but not sure I understand the issue well enough. IIUC #ast >>> is cached, but #parseTree is not. What I don't understand is the purpose of >>> this difference and when one would use one over the other. >> >> the cached #ast is for one interesting for speed (that is, in situations where you ask for it often). >> >> The other use-case is if you want to annotate the AST and keep that annotation around (till the next >> image save, but you can subscribe to ASTCacheReset and re-install the AST in the cache after cleaning. >> (This is used by MetaLinks to make sure they survive image restart). >> >> The last thing that it provides is that we do have a quite powerful mapping between bytecode/text/context >> and the AST. Regardless how you navigate, you get the same object. >> >> e.g. even this one works: >> >> [ 1+2 ] sourceNode == thisContext method ast blockNodes first >> >>> For example, >>> when, if ever, would a user want to access a CM's #ast (as opposed to >>> #parseTree) and could modifying it create problems? >>> >> >> Modification is a problem, yes.. code that wants to modify the AST without making sure the compiledMethod is in sync later >> should use #parseTree. >> >> Code that does not modify the AST (or makes sure to compile it after modification) is free to use #ast. >> or if you want to annotate the AST (which is a modification, after all). >> >> This is not perfect (not at allâ¦) but the simplest solution to get (to some extend) what you would have if the system would have >> a real persistent, first class ASTâ¦ >> >> To be improved. The ASTCache with itâs naive âlets just cache everything till the next image saveâ was done with the idea to see >> when it would show that it is too naiveâ¦ for that it worked amazingly well till now. >> >> Marcus >> >> >> >> >> >> -- >> Bernardo E.C. >> >> Sent from a cheap desktop computer in South America. >> >> >> >> -- >> >> Guille Polito >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> CRIStAL - UMR 9189 >> French National Center for Scientific Research - http://www.cnrs.fr >> >> Web: http://guillep.github.io >> Phone: +33 06 52 70 66 13 > > -- > www.tudorgirba.com > www.feenk.com > > "What is more important: To be happy, or to make happy?" > >

May 4, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Ramon Leon

On 05/03/2018 12:02 PM, Guillermo Polito wrote: > I don't think so... any compiler book talks about ASTs using acronyms. > Acronyms are good when acronyms are good. Boo, acronyms bad, virtually always. Jargon is awful when speaking and awful when Smalltalk'ing, use words, they're not in short supply. -- Ramon Leon

May 4, 2018

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

by Cyril Ferlicot D.

Le 04/05/2018 Ã 00:13, Tim Mackinnon a Ã©critÂ : > +100 and also for helping advance iceberg - weâre all desperate for a stable version with a reliable UI, and it sounds like this latest incarnation is really getting there? > As a quick answer I think that the new UI is much more user friendly and stable than the old one. I still miss some features but we are getting there step by step. With the old UI I would say I did 50% of the work with Iceberg and 50% with external git tools. Now I think it's more 80%-20%. And there is less blocking bugs (and I use the dev version ;) ) If the subject continue on Iceberg, it's better to open a new thread to keep this one around the Cytoscape connector for Telescope. Thanks. > Tim > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Cyril Ferlicot https://ferlicot.fr

May 3, 2018

Re: [Pharo-users] #ast vs. #parseTree

by Francisco Garau

There is quite a difference between a compiler book using the AST acronym and a message with the #ast selector. Whoever starts reading a compiler book already knows about AST. We shouldn't assume the same about any Pharo developer. - Francisco > On 3 May 2018, at 20:02, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > I don't think so... any compiler book talks about ASTs using acronyms. Acronyms are good when acronyms are good. > >> Le jeu. 3 mai 2018 Ã 20:48, Esteban A. Maringolo <emaringolo(a)gmail.com> a Ã©crit : >> +1 to avoid acronyms. >> >> Esteban A. Maringolo >> >> 2018-05-03 12:47 GMT-03:00 Francisco Garau <francisco.garau(a)gmail.com>: >>> I'd rather be also explicit in the name and avoid acronyms. #newAbstractSyntaxTree and #cachedAbstractSyntaxTree >>> >>> - Francisco > -- > > Guille Polito > Research Engineer > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

May 3, 2018

Re: [Pharo-users] [Voyage] How to declare an instance variable as transient?

by sergio ruiz

ah! thanks! On May 3, 2018 at 5:06:18 PM, Alejandro Infante (alejandroinfante91(a)gmail.com) wrote: Hi Sergio, You have to add a method to the class side with a pragma. In my case, I wanted to set the instance variable âquestionReferencesâ to transient. myClass class>>mongoQuestionReferences <mongoDescription> ^VOTransientDescription new attributeName: 'questionReferences'; yourself Cheers! Alejandro On Apr 30, 2018, at 3:21 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: Hi, all.. I have an instance variable that I donât want to save as part of the full project. I was wondering how to set this up. The documentation says: Lastly, attributes can be excluded from storage (and hence retrieval) by re- turning aÂ VOMongoTransientDescriptionÂ instance as the attribute descrip- tor. But I am not sure how to set this up in my class. thanks!Â ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

May 3, 2018

Re: [Pharo-users] [Voyage] How to declare an instance variable as transient?

by Alejandro Infante

Hi Sergio, You have to add a method to the class side with a pragma. In my case, I wanted to set the instance variable âquestionReferencesâ to transient. myClass class>>mongoQuestionReferences <mongoDescription> ^VOTransientDescription new attributeName: 'questionReferences'; yourself Cheers! Alejandro > On Apr 30, 2018, at 3:21 PM, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > Hi, all.. > > I have an instance variable that I donât want to save as part of the full project. I was wondering how to set this up. > > The documentation says: > Lastly, attributes can be excluded from storage (and hence retrieval) by re- turning a VOMongoTransientDescription instance as the attribute descrip- tor. > > But I am not sure how to set this up in my class. > > thanks! > > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: http://bit.ly/29z9fG0 <http://bit.ly/29z9fG0> > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > http://www.codeandmusic.com <http://www.codeandmusic.com/> > http://www.twitter.com/sergio_101 <http://www.twitter.com/sergio_101> > http://www.facebook.com/sergio101 <http://www.facebook.com/sergio101>

May 3, 2018