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

Re: [Pharo-dev] FastTable - beExplicite?

by Denis Kudriashov

Hi. 2016-05-08 22:31 GMT+02:00 Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > Hi Stef, > > A FastTable can have a function to extends it. For example a Search or a > Filter. By default this function is not explicitly shown to the user. > For example in Nautilus the user have to know he can type the name of a > method in the list to search a method. > > With beExplicit the functionality is shown to the user. For the search > and the filter there will be a text field added to the FastTable. > I would call it #showTools/#hideTools

May 9, 2016

Re: [Pharo-dev] Online documentation (was: Help on using Git with Pharo)

by Sven Van Caekenberghe

> On 09 May 2016, at 09:37, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > How about WebDoc (or similar) serving up the API with class comments to > make it searchable on the web > > Although the in-image help is really bad, I would argue that for the API itself it's quite the opposite. > Pharo is centered around code, so there is a lot of different and amazing ways to search the API and easily find what you are looking for (including trivially scripted searching). > I don't think that any web interface can compete with that (unless it's powered by Pharo itself). > > In fact there used to be WebDoc for Pharo API, however as there are no comments and examples it wasn't useful at all. You can do better search and actually try the code directly in the image, or search for examples. See http://files.pharo.org/doc/ for WebDoc. I do totally agree with the fact that Pharo is first and foremost an in-image IDE, we should concentrate on that. The web based documentation is mostly relevant for search indexing and newcomers. > The wiki would also act as a place where the documentation can evolve > until it is considered stable enough to include in the image. > > For this we have books imho. Simple documentation should be added to image. > > also have links to other blogs, etc. that may not be appropriate for > in-image documentation > > I don't see why not, but it would be better to just copy the content without having to click (depends on the content).

May 9, 2016

Re: [Pharo-dev] Online documentation (was: Help on using Git with Pharo)

by Peter UhnÃ¡k

> > How about WebDoc (or similar) serving up the API with class comments to > make it searchable on the web Although the in-image help is really bad, I would argue that for the API itself it's quite the opposite. Pharo is centered around code, so there is a lot of different and amazing ways to search the API and easily find what you are looking for (including trivially scripted searching). I don't think that any web interface can compete with that (unless it's powered by Pharo itself). In fact there used to be WebDoc for Pharo API, however as there are no comments and examples it wasn't useful at all. You can do better search and actually try the code directly in the image, or search for examples. The wiki would also act as a place where the documentation can evolve > until it is considered stable enough to include in the image. For this we have books imho. Simple documentation should be added to image. > also have links to other blogs, etc. that may not be appropriate for > in-image documentation > I don't see why not, but it would be better to just copy the content without having to click (depends on the content).

May 9, 2016

Re: [Pharo-dev] PhD Thesis offer

by jannik laval

Yes ! Now, I need a great student ;), like a smalltalker. Jannik 2016-05-04 18:21 GMT+02:00 stepharo <stepharo(a)free.fr>: > looks like a job for mOose :) > > Le 4/5/16 Ã 12:37, jannik laval a Ã©crit : > > Dear friends, > > I am looking for a french student (or someone speaking french) who wants > to engage in a CIFRE PhD thesis (it is a thesis with a french company). > > The subject is attached to the mail. > > Best regards, > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me > d'Information > IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re > laboratoire DISP > http://www.jannik-laval.eu > http://www.phratch.com > http://www.approchealpes.info > > > -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨me d'Information IUT LumiÃ¨re, UniversitÃ© Lyon LumiÃ¨re laboratoire DISP http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info

May 9, 2016

Online documentation (was: Help on using Git with Pharo)

by Alistair Grant

On Sun, May 08, 2016 at 05:08:37PM +0200, Peter UhnÃ¡k wrote: > ## 1. Help in general: > > The in-image help sucks hardâ¦ monospaced walls of text, no formatting, no > styling, no images, and zero discoverability. > > Some ideas â this is food for thought for moving forward, not something that I > would expect anyone would do tomorrow: > > ### Simple-ish: online frontend > > * have an online frontend for all the help â because the first place most > people will look is Google, and in-image help doesn't even have elementary > search > * use formattingâ¦ Pillar, Markdown, RST, AsciiDoc, whateverâ¦ for the web > frontend it doesn't matter, there are nice outputs for all of them > * even for the in-image help having some formatting markers might be better > than nothing > > ### Complex-ish > > * improving in-image helpâ¦ Offray is/was working on Jupyter (https:// > try.jupyter.org/) style notebooks. That sounds like a good replacement. > * have at least some basic formattingâ¦ some time ago there was in-image Pillar > editor using GT, so it's doable. +1 How about WebDoc (or similar) serving up the API with class comments to make it searchable on the web, and a wiki that lowers the cost of contributing? The wiki would also act as a place where the documentation can evolve until it is considered stable enough to include in the image. It can also have links to other blogs, etc. that may not be appropriate for in-image documentation Speaking of wikis, what is the status of the collaborActive book? It usually appears near the top of my google searches, but appears to be quite out of date. I'd be happy to update it a bit while still in the learning phase of Pharo if someone can provide credentials. Cheers, Alistair

May 9, 2016

Re: [Pharo-dev] call for cleaning ideas around Spec

by Stephan Eggermont

On 08-05-16 18:34, Peter UhnÃ¡k wrote: > If the difference is 10% maybe the word "most" isn't appropriate, but > you are looking at system, not Spec. There is exactly one user of NewValueHolder outside Spec > Most widgets will instantiate the value holder and then immediately > subscribe to it (either directly in #initialize, or in > #registerEvents), at least for ValueHolders that propagate changes to > Morphic. Most properties in a user interface are optional. We need to design for that > Regardless of that I said _will_, because that's the idea behind the > new Adapters, currently in the image only TabModel/MorphicTabAdapter > use it. What is the impact of that on debugability? Stephan

May 8, 2016

Re: [Pharo-dev] FastTable - beExplicite?

by Cyril Ferlicot D.

Le 08/05/2016 21:54, stepharo a Ã©crit : > Hi guys > > > I have no idea what is > > beExplicite > > but it does not look correct > > beExplicit > > > beExplicite > "This method is call by the FastTable if the user want the widget to > be explicit. Describe what to do to be explicit." > > > We should improve the quality of the comment. > > Hi Stef, A FastTable can have a function to extends it. For example a Search or a Filter. By default this function is not explicitly shown to the user. For example in Nautilus the user have to know he can type the name of a method in the list to search a method. With beExplicit the functionality is shown to the user. For the search and the filter there will be a text field added to the FastTable. Sorry for the typo, I will try to find some time to correct the typo and improve the comment. https://pharo.fogbugz.com/f/cases/18182/FastTable-beExplicit-have-a-typo-an… > > Stef > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 8, 2016

FastTable - beExplicite?

by stepharo

Hi guys I have no idea what is beExplicite but it does not look correct beExplicit beExplicite "This method is call by the FastTable if the user want the widget to be explicit. Describe what to do to be explicit." We should improve the quality of the comment. Stef

May 8, 2016

About

by stepharo

Hi When I execute FTTableMorph exampleListWithExplicitFilterAndActionButton2 I get a list and I can filter the items Now when I click one of them, the list does not show the selection. exampleListWithExplicitFilterAndActionButton2 <example> | list | list := FTTableMorph new extent: 300 @ 300; dataSource: (FTExampleDataSource elements: (Smalltalk allClassesAndTraits sorted: [ :a :b | a name < b name ])); enableFilterWithAction: [ :dataSource :searchPattern :selectedRow | selectedRow browse ]; yourself. list openInWindow What is the way to see the selection? Stef

May 8, 2016

FastTable easyList examples are broken

by stepharo

Hi I started to play with FastTable and some of the examples are broken. For example exampleEasyList* Stef

May 8, 2016