July 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Re: [Pharo-users] [ann] gt documenter

by Sven Van Caekenberghe

> On 17 Jun 2018, at 15:09, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi Tudor. > > This is super impressive. +10 > What's next? Do you plan to implement IDE for writing documents, navigation, refactorings? (senders, renames should find all places in documents) > > 2018-06-13 21:57 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: > https://github.com/feenkcom/gtoolkit-documenter > > Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. > > Attached you can see a preview of how documents look like: > > <gt-documenter.png> > > At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: > â¢ code documentation > â¢ tutorials > â¢ interactive data notebook > > > Code documentation > ---- > Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: > https://twitter.com/feenkcom/status/973899862482866176 > > You can see a live example of documentation by inspecting the following snippet: > GtDocumenter editorForText: BrToggleExamples comment. > > > Tutorials: > ---- > Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: > https://twitter.com/feenkcom/status/999975333972541440 > > The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. > > The size of the preview can also be adjusted live: > https://twitter.com/feenkcom/status/1001152789874167808 > https://twitter.com/feenkcom/status/1001407762285375490 > > You can see a live tutorial by inspecting: > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. > > > Interactive data notebook: > ---- > A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: > â¢ it supports defining variables in code snippets, and > â¢ the execution of code shows an embedded inspector. > > For example: > https://twitter.com/feenkcom/status/996310432225820672 > https://twitter.com/feenkcom/status/1002851190475026432 > > An example, can be seen by inspecting: > IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. > > > As always, please do let us know what you think. > > Enjoy, > The feenk team > > > -- > www.tudorgirba.com > www.feenk.com > > "If you can't say why something is relevant, > it probably isn't." > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

July 2, 2018

[Pharo 7.0-dev] Build #1108: Small improvement of DateAndTimeTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1108 was: SUCCESS. The Pull Request #1625 was integrated: "Small improvement of DateAndTimeTest" Pull request url: https://github.com/pharo-project/pharo/pull/1625 Issue Url: https://pharo.fogbugz.com/f/cases/22240 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 2, 2018

[Pharo 7.0-dev] Build #1107: 22235-unsafe-TextMorphForFieldViewminimumExtent

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1107 was: SUCCESS. The Pull Request #1620 was integrated: "22235-unsafe-TextMorphForFieldViewminimumExtent" Pull request url: https://github.com/pharo-project/pharo/pull/1620 Issue Url: https://pharo.fogbugz.com/f/cases/22235 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 2, 2018

Esteban's ChangeLog week of 25 June 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 25 June 2018 to 1 July 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=25/6/2018&to=1/7/2018 ChangeLog ========= 27 June 2018: ------------- * I made a [small PR](https://github.com/pharo-project/pharo/pull/1590) to ensure pharo will load correct freetype library when using windows 64bit platform. * I finally was able to build a windows 64bit VM with all dependencies: [https://ci.appveyor.com/project/OpenSmalltalk/vm/build/job/5q50v90myxu4bxxi… This is an important milestone in our Path to have Pharo running in 64bit in all platforms, but sadly this is not finish. While most of the 64bit things I tested are working properly, the cairo plugin (hence Athens) is still not. So I need to spend some more time here, looking at the possible problems :( 25 June 2018: ------------- * I spent some time digging on some issues of Pharo catalog. At the end, it was not very problematic, but at least I took the oportunity to add the repository for Pharo 7.0 :) cheers! Esteban

July 2, 2018

Re: [Pharo-dev] [squeak-dev] Why do we have SmallDictionary?

by Chris Muller

>>>> This discussion has limited its context to comparing *in-memory* >>>> Dictionary implementations, where open-addressing has an advantage. >>>> Using Magma reveals another context where chained Dictionary's can have >>>> some advantages: When they're large, persistent, and shared in a >>>> multi-user >>>> system -- e.g., when grow rehashing is not an option. >>> >>> >>> >>> B-trees were designed for that use case. >>> If growing is not an option, then your dictionary's performance will >>> degrade >>> as its size increases, won't it? >> >> >> Yes, but only logarithmically. But I was not making a >> performance-based comparison, only a possibility-based one. > > > Why is it logarithmic? If I have a hash table with an array of size 100, > and I insert 100000 elements into this table, then the best case scenario is > that all the lists are of length 1000. So, the operation cost is not > logarithmic but linear with a small constant: 0.01. Ah, you misunderstood. By "growing is not an option," I meant one would therefore use a _different_ Dictionary implementation, such as one based on a B-Tree, for example. A dictionary whose impelementation organizes or chains its associations into linked lists... - Chris

July 2, 2018