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

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

by Cyril Ferlicot D.

Le 03/05/2018 Ã 21:02, Esteban A. Maringolo a Ã©critÂ : > You announced so many things, that I'll use this last one to thank you > for sharing this. > > I found a few of the projects very interesting and I look forward to > use them for real. It was all the open source projects in which I participated and that we never took the time to release. I decided to move them to github to try the new iceberg and to have a stable version on which people can rely. Now it's done and I hope the community will find them helpful and participate (even if it's just opening issues) :) > > Thank you again. > Esteban A. Maringolo > _______________________________________________ > 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 Guillermo Polito

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 <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 3, 2018

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

by Esteban A. Maringolo

You announced so many things, that I'll use this last one to thank you for sharing this. I found a few of the projects very interesting and I look forward to use them for real. Thank you again. Esteban A. Maringolo 2018-05-03 12:29 GMT-03:00 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > 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

May 3, 2018

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

by Esteban A. Maringolo

+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 > > >

May 3, 2018

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

by Francisco Garau

I'd rather be also explicit in the name and avoid acronyms. #newAbstractSyntaxTree and #cachedAbstractSyntaxTree - Francisco > On 3 May 2018, at 09:59, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Ahh explicitness :) > >> On Thu, May 3, 2018 at 10:56 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> How about: #newAst & #cachedAst? >> >> 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?" > > > > -- > > 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

[ANN] TelescopeCytoscape for Seaside v1.0.0

by Cyril Ferlicot D.

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

May 3, 2018

Re: [Pharo-users] [Pharo-dev] [Ann] Iceberg 0.7.5

by Guillermo Polito

On Thu, May 3, 2018 at 5:25 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > Will it be too hard to do 6.2? I encourage the backport but it will break > stuff which is also really annoying. > @esteban? :) I'd really like to have that or a 6.1.1, a way to actually differentiate them... > > Norbert > > > Am 03.05.2018 um 17:16 schrieb Guillermo Polito <guillermopolito(a)gmail.com > >: > > Time for the weekly Iceberg update. > > Iceberg 0.7.5. will be in the next Pharo build. > Thanks to all brave users, issue reporters and contributors :). > > Key improvements: > - Several improvements in metacello integration. (see #625, #664, #688 + > more tests) > - For those using CI, we think this release will also fix > https://github.com/pharo-vcs/iceberg/issues/643 > > Infrastructure improvements: > - In 0.7.4 we introduced in the build tests againt pharo 6.1 and 64 bits > * https://travis-ci.org/pharo-vcs/iceberg/builds/372408795 > - In 0.7.5 all iceberg tests run green on Pharo 6.1 32 bits > * https://travis-ci.org/pharo-vcs/iceberg/builds/374433920 > - In the next release we plan to do a pass on 64 bits > > ** Pharo 6.1 backport ** > - We plan to backport this version to Pharo 6.1 > - Cyril has been using the development version of Iceberg on Pharo 6.1 > for a couple of weeks now. > - This plus the green CI encourages us to backport to Pharo 6.1 > > Detailed ChangesLog: > > #625 Non explicit error while loading a project > #758 [Regression] Repair action clone is not setting pharo repository > #756 Iceberg dev-0.7 is broken in Pharo6.1 (Instance of > IceTipURLLabelMorph did not understand #addEmphasis:) > #749 Adding repair actions to the code subdirectory missing problem > #655 Rename extension method buildToolbarItem of CommandActivator > #755 Extracting the URL label behavior as a component that we can reuse > #468 Commiting via Iceberg does not commit package removal > #750 Add possibility to see current commit in Repositories/Package view > #754 Showing and coping the Commit ID > #753 Create branch dialog layout is broken > #664 Package wrongly shown with "uncommited changes" status > #752 Add "invalid ssh" > #747 Cloning a Git repository should change the path with the project name. > #738 Remove "pharo" Repository with "also remove from filesystem" gives > error > #746 Make tests run on pharo 6 > #735 Issue while registering a new project on Pharo 6.1 > #733 Add license file > #740 Fogbugz panel: Improve label, focus order and layout > #549 IceRestoreRepositoryModel should have a class comment > #688 Duplicated project error when loading in a fresh image > > Enjoy, > Guille in behalf of all people that contributed :) > > > -- 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 <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

May 3, 2018

[ANN] Heimdall logging manager for Seaside v1.0.0

by Cyril Ferlicot D.

Hi! Guillaume Larcheveque begun a simple login manager for Seaside. I just finished to port it to github and we released the v1.0.0. It is still experimental and help is welcomed. Project can be found at: https://github.com/DuneSt/Heimdall -- Cyril Ferlicot https://ferlicot.fr

May 3, 2018

[ANN] PrismCodeDisplayer for Seaside v1.0.0

by Cyril Ferlicot D.

Hi! We just finished the release v1.0.0 of PrismCodeDisplayer for Seaside. Prism (https://github.com/PrismJS/prism/) is a lightweight, robust, elegant syntax highlighting library. The Seaside binding allows to: Display code See line numbers Select code and act on the selection Customize the style of some text intervals Add links to text intervals Add a search feature Have a dynamic loading of the text content Copy the text content Have a minimap Project can be found at: https://github.com/DuneSt/PrismCodeDisplayer Demo at: https://demos.ferlicot.fr/PrismDemo -- Cyril Ferlicot https://ferlicot.fr

May 3, 2018

[ANN] ChartJs for Seaside v1.0.0

by Cyril Ferlicot D.

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

May 3, 2018