November 2017 - Pharo-users

Re: [Pharo-users] FFIExternalEnumeration int versus long

by Ben Coman

On 15 November 2017 at 00:17, Todd Blanchard <tblanchard(a)mac.com> wrote: > Yeah, I don't know if that is necessarily worth doing TBH. > > Generally enumerations are going to be default int size unless you have > values that are out of range. > > In this case you have a function that returns a long. In a strictly typed > language you would be required to do a type cast anyhow. > > If this were done in Swift, you'd have to do something heinous like > > FPDF_ERR.fromRaw(FPDF_GetLastError()) // older Swift > FPDF_ERR(rawValue: FPDF_GetLastError()) > > even C++ would require you cast from unsigned long to the enum type. > > So, to me, it makes sense with this kind of api that you'd have to > explicitly convert in the method that does the ffiCall:, get the result, > then look up the proper enum. > To clarify, in this case its not a technical enumeration in the C header to be passed around the library, just a bunch of 10 defines for error return values. Initially I was thinking of doing it in Pharo as an enumeration just because they are numbers, but the GetLastError() function return type was 'long' so it made me curious. Now I've reevaluated I think it will work better to create a Error class to raise for each return value. Thanks for your thoughts. cheers -ben > > On Nov 14, 2017, at 2:44 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > right now FFIExternalEnumeration support int32 and uint32 types, but I > think is not hard to create a FFIExternalLongEnumeration or whatever is > need. > > FFIExternalEnumeration >> initializeEnumeration, however, could be better > refactored, I admit ;) > > On 13 Nov 2017, at 23:41, Ben Coman <btc(a)openInWorld.com> wrote: > > I have a C definition... > unsigned long FPDF_GetLastError(); > > whose return values are... > #define FPDF_ERR_SUCCESS 0 // No error. > #define FPDF_ERR_UNKNOWN 1 // Unknown error. > #define FPDF_ERR_FILE 2 // File not found or could not be opened. > #define FPDF_ERR_FORMAT 3 // File not in PDF format or corrupted. > #define FPDF_ERR_PASSWORD 4 // Password required or incorrect > password. > #define FPDF_ERR_SECURITY 5 // Unsupported security scheme. > #define FPDF_ERR_PAGE 6 // Page not found or content error. > > I was thinking of turning those #define's into an FFIExternalEnumeration, > but I was wondering if I'll hit some undefined behaviour with the > underlying representation being a "long" rather than an "int" ? > > I do see here that C enumerations can be a range of types including "long" > * https://stackoverflow.com/questions/7093360/c-sharp-enum-of-long-values > but I'm not sure how it works in the Pharo context to know what the size > underlying representation. > > cheers -ben > > > >

Nov. 15, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Offray Vladimir Luna CÃ¡rdenas

The last was a question :-P Is PharoChrome expecting to be logged in to some Google account to work? Cheers, Offray On 14/11/17 18:18, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi Alistair, > > The example is not working for me. When I run it, a chrome session is > open but nothing happens there, except that my image gets frozen until I > close chrome and then I get this message: "ConnectionTimedOut: Cannot > connect to 127.0.0.1:9222". What is the expected behavior? PharoChrome > expects the user to have a Google account or be logged in by default to > work (that would be a shame for those of us that don't a Google account > and still value our privacy). > > Thanks, > > Offray > > > On 14/11/17 11:26, Alistair Grant wrote: >> I've committed some fixes to the development branch: >> >> 1. MacOS hopefully works now (I don't have access to the platform, so >> can't test it). >> 2. The development version of Beacon is loaded (which is required for >> the InMemoryLogger). >> 3. The README is a tiny bit better. >> 4. Added #extractTables. >> >> As an example of how historical stock market data can be extracted, >> the following retrieves data for the Australian S&P200 index from >> yahoo: >> >> >> | rootNode tables historicalData dataFrame | >> >> rootNode := GoogleChrome get: >> 'https://finance.yahoo.com/quote/%5EAXJO/history?p=%5EAXJO'. >> tables := rootNode extractTables. >> historicalData := (tables sorted: #size ascending) last. >> dataFrame := DataFrame fromRows: (historicalData select: [ :each | >> each size = 7 ]). >> dataFrame asStringTable. >> >> " >> | 1 2 3 4 5 6 >> 7 >> -----+----------------------------------------------------------------------------- >> 1 | Date Open High Low Close* Adj >> Close** Volume >> 2 | Nov 14, 2017 6,021.80 6,021.80 5,957.10 5,966.00 5,966.00 >> - >> 3 | Nov 13, 2017 6,029.40 6,029.40 6,010.70 6,021.80 6,021.80 >> - >> 4 | Nov 10, 2017 6,049.40 6,049.40 6,020.70 6,029.40 6,029.40 >> - >> etc. >> " >> >> >> To load the development version on MacOS or Linux in a 32 bit image: >> >> "Assuming you don't have OSProcess loaded:" >> Metacello new >> configuration: 'OSSubprocess'; >> repository: 'github://marianopeck/OSSubprocess:master/repository'; >> version: #stable; >> load. >> >> Metacello new >> baseline: 'Chrome'; >> repository: 'github://akgrant43/Pharo-Chrome:development/repository'; >> load. >> >> >> Cheers, >> Alistair >> >> >> On 12 November 2017 at 20:09, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> Hi Sean, >>> >>> Thanks for your feedback! (responses below) >>> >>> >>> On 12 November 2017 at 18:11, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>>> Alistair Grant wrote >>>>> https://github.com/akgrant43/Pharo-Chrome >>>> Wow, that was a wild ride! >>> Sorry about that. >>> >>> >>>> Lessons learned along the way: >>>> 1. On a Mac, to use the snazzy `chrome` terminal command referenced all over >>>> the place in the docs, you must first `alias chrome="/Applications/Google\ >>>> Chrome.app/Contents/MacOS/Google\ Chrome"` >>> I'm an Ubuntu Linux user, however if you look at OSXChromePlatform >>> class>>defaultExecutableLocation you can see that is where it should >>> be looking for the exe, so the alias shouldn't really be necessary. >>> Torsten wrote this, so maybe has more insight. >>> >>> >>>> 2. Chrome must be started with certain flags: `chrome >>>> --remote-debugging-port=9222 --disable-gpu` (not sure if the last flag is >>>> needed, but `#get:` seemed to hang before using; reference >>>> https://developers.google.com/web/updates/2017/04/headless-chrome) >>> I've been using this without headless mode. I'll add a headless flag >>> that also disables the gpu. >>> >>> >>> >>>> 3. Beacon has renamed InMemoryLogger to MemoryLogger >>>> 4. I guess Beacon has renamed `#log` to `#emit` >>> Sorry about that. I didn't realise that the Pharo-Chrome baseline is >>> loading Beacon stable while my install script upgrades it to >>> #development. #development is more recent, so I'll update the >>> baseline. >>> >>> >>> >>>> 5. I had to comment out `chromeProcess sigterm.` because `chromeProcess` was >>>> nil and also #sigterm seemed not to be defined anywhere in the image. I'm >>>> not sure what the issue is there. >>> chromeProcess is set in GoogleChrome>>openURL:. Can you give me a >>> small example that demonstrates the problem? >>> >>> #sigterm is implemented by OSSUnixSubprocess, which is what I >>> ultimately use to launch the Chrome process on Ubuntu. >>> >>> But... this will be broken on Mac at the moment because the current >>> method of launching chrome doesn't keep track of the process, so >>> doesn't support #sigterm. Do you know if OSSUnixSubprocess works on >>> Mac? If it does, I can update the code (but not test it :-(). >>> >>> >>>> Pull request issued for #3 & #4. >>> Once I update the baseline this shouldn't be required. >>> >>> >>>> Also, I'm not sure what platforms you >>>> support, but you may want to tag the example methods with <gtExample> or >>>> similar so that they are runnable from the browser and open an inspector if >>>> there is an interesting return value. >>> Good idea, I'll do this. >>> >>> I'm also making a few other changes: >>> >>> 1. Add an #extractTables method that searches through the page and >>> returns an array of rows for each table it finds in the page >>> (something that can easily be loaded in to DataFrame using #fromRows:, >>> but I don't want to make Pharo-Chrome dependent on DataFrame at the >>> moment). Most of the time I use Pharo-Chrome it is extracting data >>> from tables. >>> >>> 2. I don't know of any reliable way to tell when a page has loaded >>> since there can always be javascript that periodically updates the >>> page. At the moment it waits until the page hasn't changed for a >>> configurable amount of time. I'm planning to add a check for specific >>> content to determine if the page is considered loaded. >>> >>> 3. Add some documentation to the readme :-) >>> >>> >>> >>>> ----- >>>> Cheers, >>>> Sean >>> I'll let you know when I have a new version available (hopefully in >>> the next few days). >>> >>> >>> Thanks again, >>> Alistair > > >

Nov. 14, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Offray Vladimir Luna CÃ¡rdenas

Hi Alistair, The example is not working for me. When I run it, a chrome session is open but nothing happens there, except that my image gets frozen until I close chrome and then I get this message: "ConnectionTimedOut: Cannot connect to 127.0.0.1:9222". What is the expected behavior? PharoChrome expects the user to have a Google account or be logged in by default to work (that would be a shame for those of us that don't a Google account and still value our privacy). Thanks, Offray On 14/11/17 11:26, Alistair Grant wrote: > I've committed some fixes to the development branch: > > 1. MacOS hopefully works now (I don't have access to the platform, so > can't test it). > 2. The development version of Beacon is loaded (which is required for > the InMemoryLogger). > 3. The README is a tiny bit better. > 4. Added #extractTables. > > As an example of how historical stock market data can be extracted, > the following retrieves data for the Australian S&P200 index from > yahoo: > > > | rootNode tables historicalData dataFrame | > > rootNode := GoogleChrome get: > 'https://finance.yahoo.com/quote/%5EAXJO/history?p=%5EAXJO'. > tables := rootNode extractTables. > historicalData := (tables sorted: #size ascending) last. > dataFrame := DataFrame fromRows: (historicalData select: [ :each | > each size = 7 ]). > dataFrame asStringTable. > > " > | 1 2 3 4 5 6 > 7 > -----+----------------------------------------------------------------------------- > 1 | Date Open High Low Close* Adj > Close** Volume > 2 | Nov 14, 2017 6,021.80 6,021.80 5,957.10 5,966.00 5,966.00 > - > 3 | Nov 13, 2017 6,029.40 6,029.40 6,010.70 6,021.80 6,021.80 > - > 4 | Nov 10, 2017 6,049.40 6,049.40 6,020.70 6,029.40 6,029.40 > - > etc. > " > > > To load the development version on MacOS or Linux in a 32 bit image: > > "Assuming you don't have OSProcess loaded:" > Metacello new > configuration: 'OSSubprocess'; > repository: 'github://marianopeck/OSSubprocess:master/repository'; > version: #stable; > load. > > Metacello new > baseline: 'Chrome'; > repository: 'github://akgrant43/Pharo-Chrome:development/repository'; > load. > > > Cheers, > Alistair > > > On 12 November 2017 at 20:09, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Sean, >> >> Thanks for your feedback! (responses below) >> >> >> On 12 November 2017 at 18:11, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> Alistair Grant wrote >>>> https://github.com/akgrant43/Pharo-Chrome >>> Wow, that was a wild ride! >> Sorry about that. >> >> >>> Lessons learned along the way: >>> 1. On a Mac, to use the snazzy `chrome` terminal command referenced all over >>> the place in the docs, you must first `alias chrome="/Applications/Google\ >>> Chrome.app/Contents/MacOS/Google\ Chrome"` >> I'm an Ubuntu Linux user, however if you look at OSXChromePlatform >> class>>defaultExecutableLocation you can see that is where it should >> be looking for the exe, so the alias shouldn't really be necessary. >> Torsten wrote this, so maybe has more insight. >> >> >>> 2. Chrome must be started with certain flags: `chrome >>> --remote-debugging-port=9222 --disable-gpu` (not sure if the last flag is >>> needed, but `#get:` seemed to hang before using; reference >>> https://developers.google.com/web/updates/2017/04/headless-chrome) >> I've been using this without headless mode. I'll add a headless flag >> that also disables the gpu. >> >> >> >>> 3. Beacon has renamed InMemoryLogger to MemoryLogger >>> 4. I guess Beacon has renamed `#log` to `#emit` >> Sorry about that. I didn't realise that the Pharo-Chrome baseline is >> loading Beacon stable while my install script upgrades it to >> #development. #development is more recent, so I'll update the >> baseline. >> >> >> >>> 5. I had to comment out `chromeProcess sigterm.` because `chromeProcess` was >>> nil and also #sigterm seemed not to be defined anywhere in the image. I'm >>> not sure what the issue is there. >> chromeProcess is set in GoogleChrome>>openURL:. Can you give me a >> small example that demonstrates the problem? >> >> #sigterm is implemented by OSSUnixSubprocess, which is what I >> ultimately use to launch the Chrome process on Ubuntu. >> >> But... this will be broken on Mac at the moment because the current >> method of launching chrome doesn't keep track of the process, so >> doesn't support #sigterm. Do you know if OSSUnixSubprocess works on >> Mac? If it does, I can update the code (but not test it :-(). >> >> >>> Pull request issued for #3 & #4. >> Once I update the baseline this shouldn't be required. >> >> >>> Also, I'm not sure what platforms you >>> support, but you may want to tag the example methods with <gtExample> or >>> similar so that they are runnable from the browser and open an inspector if >>> there is an interesting return value. >> Good idea, I'll do this. >> >> I'm also making a few other changes: >> >> 1. Add an #extractTables method that searches through the page and >> returns an array of rows for each table it finds in the page >> (something that can easily be loaded in to DataFrame using #fromRows:, >> but I don't want to make Pharo-Chrome dependent on DataFrame at the >> moment). Most of the time I use Pharo-Chrome it is extracting data >> from tables. >> >> 2. I don't know of any reliable way to tell when a page has loaded >> since there can always be javascript that periodically updates the >> page. At the moment it waits until the page hasn't changed for a >> configurable amount of time. I'm planning to add a check for specific >> content to determine if the page is considered loaded. >> >> 3. Add some documentation to the readme :-) >> >> >> >>> ----- >>> Cheers, >>> Sean >> I'll let you know when I have a new version available (hopefully in >> the next few days). >> >> >> Thanks again, >> Alistair >

Nov. 14, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Offray Vladimir Luna CÃ¡rdenas

OK, the development branch solve this, as shown in http://ws.stfx.eu/O6J4CJ1FZF89. Now I'm getting an unresponsive image until I close Chrome, but I think that was talked in the thread. I'll revise. Cheers, Offray On 14/11/17 17:28, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi Alistar, > > I have tried to run the examples, but seems that installation doesn't > include all needed package. At the beginning I installed OSUnix and then > OSLinuxUbuntu. None of them seems to include "AKGOSProcess", so the > "GoogleChrome get: 'http://pharo.org'" example raises: > "#command:arguments: was sent to nil". What package provides the proper > installation for a 64 bits Manjaro Linux including the dependencies? > > Thanks, > > Offray > > > On 14/11/17 13:14, Alistair Grant wrote: >> On 14 November 2017 at 19:13, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> Hi Sean, >>> >>> On 14 November 2017 at 19:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>>> Alistair Grant wrote >>>>> I've committed some fixes to the development branch: >>>> Thanks! >>>> >>>> I tried your example, but apparently the OSXProcess class, which is >>>> referenced in openChromeWith: is missing. Also, no class in the image seems >>>> to define #createProcess:, which is sent to OSXProcess there >>> This looks like you are using an old (cached?) version. Maybe try >>> "Pull incoming commits" from Iceberg? >>> >>> You should have (minus the broken formatting from pasting): >>> >>> >>> OSXChromePlatform>>openChromeWith: arguments >>> >>> | executableLocation process | >>> executableLocation := self defaultExecutableLocation copyReplaceAll: ' >>> ' with: '\ '. >>> process := AKGOSProcess command: executableLocation arguments: arguments. >>> process run. >>> ^process >> P.S. Don't forget this is on the development branch. >> >> Cheers, >> Alistair >> >> > > >

Nov. 14, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Offray Vladimir Luna CÃ¡rdenas

Hi Alistar, I have tried to run the examples, but seems that installation doesn't include all needed package. At the beginning I installed OSUnix and then OSLinuxUbuntu. None of them seems to include "AKGOSProcess", so the "GoogleChrome get: 'http://pharo.org'" example raises: "#command:arguments: was sent to nil". What package provides the proper installation for a 64 bits Manjaro Linux including the dependencies? Thanks, Offray On 14/11/17 13:14, Alistair Grant wrote: > On 14 November 2017 at 19:13, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Sean, >> >> On 14 November 2017 at 19:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> Alistair Grant wrote >>>> I've committed some fixes to the development branch: >>> Thanks! >>> >>> I tried your example, but apparently the OSXProcess class, which is >>> referenced in openChromeWith: is missing. Also, no class in the image seems >>> to define #createProcess:, which is sent to OSXProcess there >> This looks like you are using an old (cached?) version. Maybe try >> "Pull incoming commits" from Iceberg? >> >> You should have (minus the broken formatting from pasting): >> >> >> OSXChromePlatform>>openChromeWith: arguments >> >> | executableLocation process | >> executableLocation := self defaultExecutableLocation copyReplaceAll: ' >> ' with: '\ '. >> process := AKGOSProcess command: executableLocation arguments: arguments. >> process run. >> ^process > > P.S. Don't forget this is on the development branch. > > Cheers, > Alistair > >

Nov. 14, 2017

PhD in IoT and Pharo

by Stephane Ducasse

Hi we have a PhD position in France around IoT and Pharo. Description Over the last years, the RMOD team of INRIA Lille and the CAR theme of IMT Lille Douai have been working together on creating tiny language core. For example, Guillermo Polito demonstrated in his PhD a fully reflective kernel that fits into 80 kb of memory and that it is possible to have hyper specialized kernels down to 11 kb. We have also worked on remote debugging (PhD of N. Papoulias) and dynamic code updates (PhD of P. Tesone) of such kernels. All of these works are prototyped in Pharo. More recently, RMOD have been working on advanced probes mechanisms (M. Denker) and a solid remote debugging infrastructure (D. Krudiaskov). The goal of this PhD is to revisit the architecture around such mini-kernels for building IoT applicatons. The following tasks are foreseen : â improve the tools to : edit, compile, debug, deploy and update such kernels on IoT devices. Learning how to debug remotely and dynamically update such IoT systems using the PharmID Pharo environment. This task will be in cooperation with M. Denker and D. Krudiakov on remote debugging for IoT and G. Polito for the kernel edition and tooling, â define some language extensions to manage groups of IoT devices to program them at once. Managing hundreds or even thousands of IoT devices is a challenging task. We want to explore different solutions to help deploying and updating groups of IoT devices using some registration mechanism in a cloud server or some groups/roles based approaches for example, â expressing the architecture of IoT applications. We would like to explore also how to express IoT architectures and what are the abstractions that should be offered to developers such as expressing event-driven architectures with declarative ECA (Event-Conditions-Actions) rules. But we will study a couple of typical IoT appli- cations. â dynamically update an IoT application. An IoT application needs to adapt itself because unreachable or faulty devices or the diminution of available bandwith. We would like that the whole application can reconfigure itself in such situations as Guillaume Grondin proposes it in its PhD. â Lighweight virtual machines. Virtual machines in the IoT context are very powerful for incremental deployment or dynamic updates. Although they are tuned for speed,they consume space compared to a non VM-based program. In this task, we would like to investigate what is the minimal memory consumption that we can reach for a VM usable for IoT. To do so we will use a standard VM such as Cog (the open- source virtual machine of Pharo) and degrade it. We will use it since our minimal kernels are running on it. Note that ZweiDenker GmbH is interested in collaboration on the IoT management cloud infrastructure. Application To apply, please send us : â a CV, â a copy of your Master diploma â a copy of your Master thesis â 2 (two) reference letters, with the contact details of the referents â links to videos of demos of your experiments and/or simulations The application materials should be sent by email to Prof. S. Ducasse stephane.ducasse(a)inria.fr. Email subject must start with : [PhD-RMoD- CAR-2017]. Bibliography â G Polito, St Ìephane Ducasse, N Bouraqadi, L Fabresse, M Mattone. Virtualization Support for Dynamic Core Library Update. Onward !, Oct 2015, Pittsburg, USA. â Guillermo Polito. Virtualization Support for Application Runtime Virtualization and Extension. Ph.D. Thesis 2015. Co-delivr Ìee par lâUniversit Ìe de Lille et lâE Ìcole des Mines de Douai. â Extended results of Tornado : A Run-Fail-Grow approach for Dynamic Application Tayloring. Commanditeur : E Ìcole des mines de Douai, France. 50p, July 2014 â Nick Papoulias, Noury Bouraqadi, Luc Fabresse, St Ìephane Ducasse and Marcus Denker, Mercury : Properties and Design of a Remote Debugging Solution using Reflection, Journal of Object Technology, 14, 1 :1-36, 2015 â Madcar:anabstractmodelfordynamicandautomatic(re-)assemblingofcomponent- based applications G Grondin, N Bouraqadi, L Vercouter. International Symposium on Component-Based Software Engineering, 360-367. Stef and Luc

Nov. 14, 2017

Re: [Pharo-users] FileReference basename of current dir

by Alistair Grant

On 10 November 2017 at 22:30, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 9 November 2017 at 22:12, Norbert Hartl <norbert(a)hartl.name> wrote: >> is there a good explanation why >> >> âfooâ asFileReference parent basename >> >> gives â/â ? > > I'd like to think about this a bit more, but at first glance the > problem seems to be that Path>>basename was written only taking > Absolute paths in to consideration. > > So RelativePath>>basename needs to be added: > > basename > "Returns the base of the basename, > i.e. > foo/gloops.taz basename is 'gloops.taz' > . basename is '.'" > self size == 0 > "the current directory" > ifTrue: [ ^ '.']. > ^ self at: self size Fogbugz 20693: https://pharo.fogbugz.com/f/cases/20693/Incorrect-basename-of-empty-relativ… I've got the code changes done, but am having troubles with Iceberg (which I'll post about if I can't get it working). Thanks, Alistair

Nov. 14, 2017

Re: [Pharo-users] About implementing a "Mini Pillar" in-image renderer for Pharo ...

by Offray Vladimir Luna CÃ¡rdenas

Hi, The readme is clearer now about Iceberg integration as an option not as prerequisite. Installation works, but Pillar preview tab is grey and clicking on it rises: "Instance of FFIExternalResourceManager class did not understand #removeResource:". Also the syntax highlighting in the (plain) Pillar tab is not working and neither the image preview. A plain installation of just Pillar (without GT Documenter) got those two working once. Cheers, OffrayÂ On 14/11/17 12:37, Tudor Girba wrote: > Hi, > > We changed the baseline to not require Moz2D on Linux. Could you please try again? > > I also updated the README. > > Cheers, > Doru > > >> On Nov 14, 2017, at 6:25 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Alex, >> I understand that frustration on installation could be motivated by other issues instead of GT Documenter, but if the team ask to use "Iceberg enableMetacelloIntegration: true." in the project readme, where it also says that is supported for Pharo 6.1 and 7.0, is natural to think that something is wrong with documentation and/or in the project's expectations about its intended users and their will to invest the effort, time and motivation for "living in the edge". I understand that if we want stuff to be improved it should be tested, but also that not all the people that is willing to test stuff for Pharo 6.1 needs to live in such edge. Or the project is sending a message that is not giving the bests firsts impressions, or is going to users which are not intended . I would go for a smooth install first and then for collaboration with git. I'll make a pull request with the proposal for a better documentation, but my understanding about how you can go from the first (user of GT Documenter) to the second (developer using Git integration) is not clear. >> >> GT Tools has been pretty empowering. I have told that several times and I don't think that I have wrote a single line of code in their repos. But is getting more difficult just to test and use them and I think that is related with the idea that my user *needs* to be also my co-developer, starting with their ssh git key pair. If we don't make easier to contribute by just making easier to install, there will be no evolution either. >> >> Cheers, >> >> Offray >> >> On 14/11/17 11:45, Aliaksei Syrel wrote: >>> Hi Offray, >>> >>> I understand your frustration, but with all respect, the fact that you have problems with Iceberg does not mean that GT Documenter or any other GT tool is responsible for described problems. >>> >>> Most complains about bloc, brick, whatever is because of unrelated stuff. It is a little bit disappointing. Especially for me, as one of the maintainers. But it is ok, I got used to it :) >>> >>> I donât remember when last time I used stable Pharo (not because it does not exist), simply live on the edge since Pharo4. If no one will use Git and report problems Iceberg will never progress. If no one will use Bloc it will never get âthereâ. Unfortunately, living on the edge is dangerous, requires effort, motivation and time. >>> >>> The script that Doru provided works flawlessly on OSX, we load it almost everyday. !! Bloc is tested on CI and builds are green on Windows, Linux and OSX !!. If computer (CI) manages to install it, I am pretty sure human can do it too. Looks like there is something missing in your configuration, something tiny :) Error handling in Iceberg can be definitely improved, but it is a different story. >>> >>> P.S. Documenter can be installed without enabled Iceberg integration. This is how CI does it. You will just not be able to contribute. >>> >>> Cheers, >>> Alex >>> >>> On Tue, 14 Nov 2017 at 16:37, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>> I have been just trying to install GT Documenter and is really frustrating (I have been unable to install it even for the first time!). >>> >>> This was the list of errors I got and steps I followed, in almost sequential order, just to get a (bittersweet!) taste of GT Documenter: >>> >>> â¢ 1st: LGit_GIT_ERROR: No ssh-agent suitable credentials found. So I go to GitHub, follow the five pages of documentation to get my SSH credentials that start at [1], then, because I still get the same error, go to the Iceberg FAQ [2], try to surpass the erro,r via command line and doesn't work, so I go to the Iceberg settings and try the manual configuration, going to the next item >>> >>> [1] https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-… >>> [2] https://github.com/pharo-vcs/iceberg/blob/master/README.md >>> >>> â¢ Now I get "Instance of LGitCredentialsSSH class did not understand #ifTrue:ifFalse:". I try to make sense of it in the debugger, but is something I cannot. Anyway, I rerun it and now I get: LGit_GIT_EEXISTS: '/home/offray/Programas/Pharo/6.1a/Dev24/pharo-local/iceberg/feenkcom/gtoolkit' exists and is not an empty directory. I delete that directory and try an installation... again >>> â¢ Now I get: "Instance of FileReference did not understand #notEmpty". I try to make sense of it in the debugger. My user is git, my public and private ssh keys are not empty. Despite of not making sense of all I understand that is trying to clone something at git@github.com:feenkcom/gtoolkit.git. I go to my image dir and then to `iceberg/feenkcom/gtoolkit/`. There is a git repository there, but is empty. >>> â¢ Now I wonder, maybe if I can just clone the directory there, but how I say Iceberg to load it? So I run now only the Metacello part. Same error and solution that the last time but now for gtoolkit-visualizer, Brick, gtoolkit-examples, Bloc and Sparta. >>> â¢ After getting my ssh keys, overcome config problems in shell and the Pharo settings, chasing these errors and solving them by cloning the repositories manually, I'm, a couple of hours later, ready to test GT Documenter, but with the last Iceberg's duplicated repository message about Sparta I give up. Is not nice to start your day accumulating frustration... that sets a bad mood for the rest of it, and you need to actively fight against. >>> I have thought that Git is overcomplicated for most of the developers' tasks and communities. I don't know if the root of previous issues is in the "Iceberg enableMetacelloIntegration: true" line, but having to get your pair of keys working to just install software is overkill for the common user (and when LibGit errors are present, the documented solutions don't work seamlessly). Maybe a more sensitive solution would be just to use libgit, without any ssh auth to clone repositories and its prerequisites or even better, some download that goes to the files in the tip (or other) version without all this overhead. >>> >>> Anyway, as I said, I have been unable to test GT Documenter properly and getting feedback over GT Tools from the team usually requires a lot of effort in my case (insisting on getting answers or getting none). And that is just to test a promising tech that still doesn't offer saving features (just and awesome preview). I think that a more sensible approach for a good documentation toolkit for now is on Spec and creating custom syntax highlighters with SmaCC[3], that is well documented and works today. >>> [3] https://medium.com/@juliendelplanque/hacking-a-simple-syntactic-highlighter… >>> I understand that community is trying its best, but expressing how current offerings are not mature and constructive criticism can help on that. At the moment my feeling is that if you want to try the new shinny alpha stuff from GT Documenter, you will need to be prepared for a lot of frustration and silence. >>> >>> Cheers, >>> >>> Offray >>> >>> >>> On 10/11/17 12:41, Tudor Girba wrote: >>>> Hi, >>>> >>>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for Pillar working on top of Bloc. >>>> >>>> You can get it by loading: >>>> >>>> Iceberg enableMetacelloIntegration: true. >>>> Metacello new >>>> baseline: 'GToolkit'; >>>> repository: 'github://feenkcom/gtoolkit/src'; >>>> load. >>>> >>>> For example, you can then inspect: >>>> 'PATH_TO_ICEBERG/feenkcom/gtoolkit/doc/transcript/index.pillarâ asFileReference >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> >>>>> On Nov 10, 2017, at 12:58 PM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>>> wrote: >>>>> >>>>> A note: >>>>> >>>>> Tudor Girba wrote: >>>>> >>>>> <tudor(a)tudorgirba.com> >>>>> Fri, Aug 25, 2017 at 1:31 PM >>>>> Reply-To: Any question about pharo is welcome >>>>> <pharo-users(a)lists.pharo.org> >>>>> >>>>> To: Any question about pharo is welcome >>>>> <pharo-users(a)lists.pharo.org> >>>>> >>>>> >>>>> Hi, >>>>> >>>>> As mentioned in an announcement about 10 days ago, we are building a >>>>> Pillar editor with inline viewing abilities in Bloc. Here is how it >>>>> looked like. Please note the embedded picture. We continued working on >>>>> it since then and we will probably announce the next version this >>>>> weekend: >>>>> >>>>> >>>>> Maybe there is now enough progress to do simple presentations in Bloc? >>>>> >>>>> >>>>> On 11/10/17, H. Hirzel >>>>> <hannes.hirzel(a)gmail.com> >>>>> wrote: >>>>> >>>>>> Hello >>>>>> >>>>>> In the thread 'including Pillar in Pharo image by default' it was >>>>>> suggested by Stephane Ducasse to include a subset of Pillar in the >>>>>> Pharo image[1] . >>>>>> >>>>>> I'd like to extend that proposal a little bit it in order to do very >>>>>> simple presentations. This should allow to describe at least part of >>>>>> the slides used in the MOOC course [3]. >>>>>> >>>>>> This will be _a possible_ solution to the question brought up in the >>>>>> thread 'Writing "powerpoint" like presentations in Pharo?'. >>>>>> >>>>>> Another use is to write instructions with executable content within >>>>>> the image ("Assistants"). >>>>>> >>>>>> So below is the a proposal for a Pillar syntax _subset_ for class >>>>>> comments and _simple_ presentations. >>>>>> The numbering scheme follows the 'Pillar syntax cheat sheet' [2] >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> MINI PILLAR SYNTAX (a subset of Pillar) >>>>>> >>>>>> 1. Headers >>>>>> >>>>>> !Header 1 >>>>>> !!Header 2 >>>>>> !!!Header 3 >>>>>> >>>>>> >>>>>> 2. Lists >>>>>> >>>>>> - Unordered List >>>>>> # Ordered list >>>>>> >>>>>> >>>>>> >>>>>> 5. Emphasis >>>>>> >>>>>> ""bold"" >>>>>> >>>>>> >>>>>> 6. Code blocks >>>>>> >>>>>> [[[ >>>>>> Transcript show: 'Hello World'. >>>>>> \]]] >>>>>> >>>>>> >>>>>> 9. Annotation >>>>>> >>>>>> ${slide:title=About Pharo}$ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Next week I plan to implement the rendering of this 'Mini Pillar' in >>>>>> Morphic using the Morphic API subset that works in Pharo and Squeak. >>>>>> >>>>>> A renderer using Bloc would also be nice. [4] >>>>>> >>>>>> Comments, suggestions, code snippets and other help is welcome. >>>>>> >>>>>> Regards >>>>>> Hannes >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -------------------------------------------------------------------------------------------------- >>>>>> [1] Pillar subset for class comments >>>>>> >>>>>> Stephane Ducasse >>>>>> >>>>>> <stepharo.self(a)gmail.com> >>>>>> Fri, Aug 11, 2017 at 7:09 PM >>>>>> To: Any question about pharo is welcome >>>>>> <pharo-users(a)lists.pharo.org> >>>>>> >>>>>> >>>>>> Tx cyril >>>>>> >>>>>> For class comment I image that we want >>>>>> >>>>>> ! >>>>>> >>>>>> - >>>>>> - >>>>>> *url* >>>>>> and bold >>>>>> [[[ >>>>>> >>>>>> ]]] >>>>>> >>>>>> Did I miss something. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -------------------------------------------------------------------------------------------------- >>>>>> [2] >>>>>> >>>>>> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet >>>>>> >>>>>> -------------------------------------------------------------------------------------------------- >>>>>> >>>>>> >>>>>> 1. Headers >>>>>> >>>>>> !Header 1 >>>>>> !!Header 2 >>>>>> !!!Header 3 >>>>>> !!!!Header 4 >>>>>> !!!!!Header 5 >>>>>> !!!!!!Header 6 >>>>>> >>>>>> 2. Lists >>>>>> >>>>>> - Unordered List >>>>>> # Ordered list >>>>>> >>>>>> 3. Table >>>>>> >>>>>> |! Left |! Right |! Centered >>>>>> |{Left |}Right| Centered >>>>>> >>>>>> >>>>>> 4. Description >>>>>> Note >>>>>> on a new line >>>>>> >>>>>> ;head >>>>>> :item >>>>>> >>>>>> >>>>>> 5. Emphasis >>>>>> >>>>>> ""bold"" >>>>>> ''italic'' >>>>>> --strikethrough-- >>>>>> __underscore__ >>>>>> ==inline code== >>>>>> @@subscript@@ >>>>>> ^^sub-script^^ >>>>>> >>>>>> 6. Code blocks >>>>>> >>>>>> [[[labÂel=ÂhelÂloSÂcriÂpt|ÂcapÂtioÂn=How to print Hello >>>>>> World|ÂlanÂguaÂge=ÂSmaÂlltalk >>>>>> Transcript show: 'Hello World'. >>>>>> \]]] >>>>>> >>>>>> >>>>>> 7. Raw >>>>>> >>>>>> >>>>>> {{{latex: >>>>>> this is how you inject raw \LaTeX in your output file >>>>>> }}} >>>>>> >>>>>> {{{marÂkdown: >>>>>> this is how you inject raw `markdown` in your output file >>>>>> }}} >>>>>> >>>>>> {{{html: >>>>>> this is how you inject raw <b>ÂhtmÂl</Âb> in your output file >>>>>> }}} >>>>>> >>>>>> >>>>>> 8. Links >>>>>> >>>>>> Anchor @anchor (new line) >>>>>> Internal link *anchor* >>>>>> External link *Google> >>>>>> http://google.com >>>>>> * >>>>>> Image +Caption> >>>>>> file://image.png|width=50|label=label+ >>>>>> >>>>>> >>>>>> >>>>>> 9. Annotation >>>>>> Note >>>>>> on a new line >>>>>> >>>>>> Annotation @@note this is a note >>>>>> Todo item @@todo this is to do >>>>>> >>>>>> >>>>>> 10. Comments >>>>>> >>>>>> % each line starting with % is commented >>>>>> >>>>>> >>>>>> 11. References >>>>>> >>>>>> This document is copied from >>>>>> >>>>>> http://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ---------------------------------------------------------------------- >>>>>> [3] Example pillar code for slides >>>>>> ---------------------------------------------------------------------- >>>>>> >>>>>> >>>>>> https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/1-T… >>>>>> >>>>>> >>>>>> { >>>>>> "title":"To the Roots of Objects", >>>>>> "subtitle":"Learning from beauty", >>>>>> "author":"Stephane Ducasse", >>>>>> "complement": >>>>>> "http://stephane.ducasse.free.fr/ \\\\ >>>>>> stephane.ducasse(a)inria.fr" >>>>>> >>>>>> } >>>>>> >>>>>> >>>>>> ${toc:depthLevel=2|level=0|highlight=0}$ >>>>>> >>>>>> %Les sections ne sont pas des titres de slide mais dÃ©finnissent la >>>>>> structure du doucment. Il est possible de rajouter >>>>>> "renderStructureAsSlide":false dans pillar.conf pour ne pas crÃ©er de >>>>>> slide Ã partir d'un titre. >>>>>> >>>>>> >>>>>> ${slide:title=License}$ >>>>>> >>>>>> +> >>>>>> file://figures/CreativeCommons.png|width=50|label=figCreativeCommons+ >>>>>> >>>>>> >>>>>> >>>>>> ! Introduction >>>>>> >>>>>> % >>>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>>> >>>>>> >>>>>> ${slide:title=Really?!|label=really}$ >>>>>> >>>>>> ${columns}$ >>>>>> >>>>>> ${column:width=50}$ >>>>>> >>>>>> %the width parameter take an Int between 1 and 100 >>>>>> %For now we have to pass a line before and after an annotation, I'll >>>>>> correct that soon in Pillar. >>>>>> - No primitive types >>>>>> - No hardcoded constructs for conditional >>>>>> - Only messages >>>>>> - Only objects >>>>>> >>>>>> ${column:width=50}$ >>>>>> >>>>>> - and this works? >>>>>> - I mean really? >>>>>> - Not even slow? >>>>>> - Can't be real! >>>>>> >>>>>> ${endColumns}$ >>>>>> >>>>>> ${slide:title=Motto}$ >>>>>> >>>>>> - Let's open our eyes, look, understand, and deeply understand the >>>>>> underlying design aspects of object-oriented programming. >>>>>> >>>>>> >>>>>> *@really* >>>>>> >>>>>> *TEST !>@really* >>>>>> >>>>>> ${slide:title=Booleans}$ >>>>>> >>>>>> [[[language=smalltalk >>>>>> 3 > 0 >>>>>> ifTrue: ['positive'] >>>>>> ifFalse: ['negative'] >>>>>> -> 'positive' >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Yes ifTrue\:ifFalse\: is a message!}$ >>>>>> >>>>>> [[[language=smalltalk >>>>>> Weather isRaining >>>>>> ifTrue: [self takeMyUmbrella] >>>>>> ifFalse: [self takeMySunglasses] >>>>>> ]]] >>>>>> >>>>>> - Conceptually ==ifTrue:ifFalse:== is a message sent to an object: a >>>>>> boolean! >>>>>> - ==ifTrue:ifFalse:== is in fact radically optimized by the compiler >>>>>> but you can implement another one such ==siAlors:sinon:== and check. >>>>>> >>>>>> ${slide:title=Booleans}$ >>>>>> >>>>>> In Pharo booleans have nothing special >>>>>> - & | not >>>>>> - or: and: (lazy) >>>>>> - xor: >>>>>> - ifTrue:ifFalse: >>>>>> - ifFalse:ifTrue: >>>>>> - ... >>>>>> >>>>>> ${slide:title=Lazy Logical Operators}$ >>>>>> >>>>>> *LINK>@frm:really* >>>>>> >>>>>> [[[language=smalltalk >>>>>> false and: [1 error: 'crazy'] >>>>>> -> false and not an error >>>>>> ]]] >>>>>> >>>>>> ! Exercices >>>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>>> >>>>>> !! Exercise 1: Implement not >>>>>> >>>>>> ${slide:title=Exercise 1\: Implement not}$ >>>>>> >>>>>> - Propose an implementation of not in a world where you do not have >>>>>> Booleans. >>>>>> - You only have objects and messages. >>>>>> [[[language=smalltalk >>>>>> false not >>>>>> -> true >>>>>> >>>>>> true not >>>>>> -> false >>>>>> ]]] >>>>>> >>>>>> !!Exercise 2: Implement | (Or) ifTrue: ifFalse: >>>>>> >>>>>> ${toc:depthLevel=2|level=0|highlight=1}$ >>>>>> >>>>>> ${slide:title=Exercise 2\: Implement \| (Or)}$ >>>>>> >>>>>> - Propose an implementation of or in a world where you do not have >>>>>> Booleans. >>>>>> - You only have objects and messages. >>>>>> >>>>>> [[[language=smalltalk >>>>>> true | true -> true >>>>>> true | false -> true >>>>>> true | anything -> true >>>>>> >>>>>> false | true -> true >>>>>> false | false -> false >>>>>> false | anything -> anything >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Exercise2\: Variation - Implement ifTrue\:ifFalse\:}$ >>>>>> >>>>>> - Propose an implementation of not in a world where you do not have >>>>>> Booleans. >>>>>> - You only have objects, messages and closures. >>>>>> >>>>>> [[[language=smalltalk >>>>>> false ifTrue: [ 3 ] ifFalse: [ 5 ] >>>>>> -> 5 >>>>>> true ifTrue: [ 3 ] ifFalse: [ 5 ] >>>>>> -> 3 >>>>>> ]]] >>>>>> >>>>>> ! Boolean Implementation >>>>>> >>>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>>> >>>>>> ${slide:title=Booleans Implementation Hint One}$ >>>>>> >>>>>> - The solution does not use conditionals >>>>>> - else we would obtain a recursive definition of ==ifTrue:ifFalse:== >>>>>> >>>>>> ${slide:title=Boolean Implementation Hint Two}$ >>>>>> >>>>>> - The solution uses three classes: ==Boolean==, ==True== and ==False== >>>>>> - ==false== and ==true== are unique instances described by their own >>>>>> classes >>>>>> - ==false== is an instance of the class ==False== >>>>>> - ==true== is an instance of the class ==True== >>>>>> >>>>>> +Boolean Hierarchy> >>>>>> file://figures/BooleanHiearchyAndInstances.png|width=50+ >>>>>> >>>>>> >>>>>> ${slide:title=How do we express choice in OOP?}$ >>>>>> >>>>>> - We send messages to objects >>>>>> >>>>>> [[[language=smalltalk >>>>>> aButton color >>>>>> -> Color red >>>>>> >>>>>> aPane color >>>>>> -> Color blue >>>>>> >>>>>> aWindow color >>>>>> -> Color grey >>>>>> ]]] >>>>>> >>>>>> - Let's the receiver decide >>>>>> >>>>>> - Do not ask, tell >>>>>> >>>>>> ${slide:title=Boolean not implementation}$ >>>>>> >>>>>> - Class ==Boolean== is an abstract class that implements behavior >>>>>> common to true and false. Its subclasses are ==True== and ==False==. >>>>>> Subclasses must implement methods for logical operations ==&==, >>>>>> ==not==, and controls ==and:==, ==or:==, ==ifTrue:==, ==ifFalse:==, >>>>>> ==ifTrue:ifFalse:==, ==ifFalse:ifTrue:== >>>>>> >>>>>> [[[language=smalltalk >>>>>> Boolean>>not >>>>>> "Negation. Answer true if the receiver is false, answer false if the >>>>>> receiver is true." >>>>>> self subclassResponsibility >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Not implementation in two methods}$ >>>>>> >>>>>> [[[language=smalltalk >>>>>> False>>not >>>>>> "Negation -- answer true since the receiver is false." >>>>>> ^ true >>>>>> ]]] >>>>>> >>>>>> [[[language=smalltalk >>>>>> True>>not >>>>>> "Negation--answer false since the receiver is true." >>>>>> ^ false >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Not implementation in two methods}$ >>>>>> >>>>>> +Not >>>>>> implementation.> >>>>>> file://figures/BooleanHiearchyAndInstancesWithNotMethods.png|width=80+ >>>>>> >>>>>> >>>>>> ${slide:title=\| (Or)}$ >>>>>> [[[language=smalltalk >>>>>> >>>>>> true | true -> true >>>>>> true | false -> true >>>>>> true | anything -> true >>>>>> >>>>>> false | true -> true >>>>>> false | false -> false >>>>>> false | anything -> anything >>>>>> >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Boolean>> \| aBoolean}$ >>>>>> >>>>>> [[[language=smalltalk >>>>>> Boolean>> | aBoolean >>>>>> "Evaluating disjunction (OR). Evaluate the argument. Answer true if >>>>>> either the receiver or the argument is >>>>>> true." >>>>>> self subclassResponsibility >>>>>> ]]] >>>>>> >>>>>> ${slide:title=False>> \| aBoolean}$ >>>>>> >>>>>> [[[language=smalltalk >>>>>> false | true -> true >>>>>> false | false -> false >>>>>> false | anything -> anything >>>>>> ]]] >>>>>> >>>>>> [[[language=smalltalk >>>>>> False >> | aBoolean >>>>>> "Evaluating disjunction (OR) -- answer with the argument, aBoolean." >>>>>> ^ aBoolean >>>>>> ]]] >>>>>> >>>>>> ${slide:title=True>> \| aBoolean}$ >>>>>> >>>>>> [[[language=smalltalk >>>>>> true | true -> true >>>>>> true | false -> true >>>>>> true | anything -> true >>>>>> ]]] >>>>>> >>>>>> [[[language=smalltalk >>>>>> True>> | aBoolean >>>>>> "Evaluating disjunction (OR) -- answer true since the receiver is true." >>>>>> ^ self >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Or implementation in two methods}$ >>>>>> >>>>>> +> >>>>>> file://figures/BooleanHiearchyAndInstancesWithOrMethods.png|width=80+ >>>>>> >>>>>> >>>>>> ${slide:title=Implementing ifTrue\:ifFalse\:}$ >>>>>> >>>>>> - Do you see the pattern? >>>>>> - Remember that a closure freezes execution and that value launches >>>>>> the execution of a frozen code. >>>>>> >>>>>> [[[language=smalltalk >>>>>> True>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>>>> ^ aTrueBlock value >>>>>> ]]] >>>>>> >>>>>> [[[language=smalltalk >>>>>> False>>ifTrue: aTrueBlock ifFalse: aFalseBlock >>>>>> ^ aFalseBlock value >>>>>> ]]] >>>>>> >>>>>> ${slide:title=Implementation Note}$ >>>>>> >>>>>> - Note that the Virtual Machine shortcuts calls to boolean such as >>>>>> condition for speed reason. >>>>>> - But you can implement your own conditional method and debug to see >>>>>> that sending a message is dispatching to the right object. >>>>>> >>>>>> ! So what ? >>>>>> >>>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>>> >>>>>> ${slide:title=Ok so what?}$ >>>>>> >>>>>> - You will probably not implement another Boolean classes >>>>>> - So is it really that totally useless? >>>>>> >>>>>> >>>>>> ${slide:title=Message sends act as case statements}$ >>>>>> >>>>>> - The execution engine will select the right method in the class of the >>>>>> receiver >>>>>> - The case statements is dynamic in the sense that it depends on the >>>>>> classes loaded and the objects to which the message is sent. >>>>>> - Each time you send a message, the system will select the method >>>>>> corresponding to the receiver. >>>>>> >>>>>> >>>>>> ${slide:title=A Class Hierarchy is a Skeleton for Dynamic Dispatch}$ >>>>>> >>>>>> - If we would have said that the ==Boolean== would be composed of only >>>>>> one class, we could not have use dynamic binding. >>>>>> - A class hierarchy is the exoskeleton for dynamic binding >>>>>> >>>>>> - Compare the solution with one class vs. a hierarchy. >>>>>> >>>>>> +One single class vs. a nice >>>>>> hierarchy.> >>>>>> file://figures/Design-FatVsDispatch.png|width=70+ >>>>>> >>>>>> >>>>>> - The hierarchy provides a way to specialize behavior. >>>>>> - It is also more declarative in the sense that you only focus on one >>>>>> class. >>>>>> - It is more modular in the sense that you can package different >>>>>> classes in different packages. >>>>>> >>>>>> ${slide:title=Avoid Conditionals}$ >>>>>> >>>>>> - Use objects and messages, when you can >>>>>> - The execution engine acts as a conditional switch: Use it! >>>>>> - Check the AntiIfCampaign. >>>>>> >>>>>> ${slide:title=Follow-up: Implement ternary logic}$ >>>>>> >>>>>> - Boolean: ==true==, ==false==, ==unknown== >>>>>> +Ternaru Logic decision table >>>>>> >>>>>>> file://figures/ArrayBoolean.png|width=30|label=fig:ternLogic+ >>>>>> - Implementing in your own classes. >>>>>> >>>>>> ! Summary >>>>>> >>>>>> ${toc:depthLevel=1|level=0|highlight=1}$ >>>>>> >>>>>> ${slide:title=Summary}$ >>>>>> - Tell, do not ask >>>>>> - Let the receiver decide >>>>>> - Message sends as potential dynamic conditional >>>>>> - Class hiearchy builds a skeleton for dynamic dispatch >>>>>> - Avoid conditional >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ----------------------------------------- >>>>>> [4] Bloc >>>>>> Load Bloc with executing in a playground (Pharo 6.1) >>>>>> >>>>>> Metacello new >>>>>> baseline: 'Bloc'; >>>>>> repository: 'github://pharo-graphics/Bloc:pharo6.1/src'; >>>>>> load: #core >>>>>> >>>>>> >>>>>> A tutorial to use bloc is available on >>>>>> >>>>>> http://files.pharo.org/books/ >>>>>> >>>>>> Bloc Memory Game (alpha) is a first tutorial on Bloc the new graphics >>>>>> core for Pharo. Booklet written by A. Chis, S. Ducasse, A. Syrel. >>>>>> >>>>>> >>>>>> http://files.pharo.org/books-pdfs/booklet-Bloc/2017-11-09-memorygame.pdf >>>>>> >>>>>> >>>>>> To load the memory game >>>>>> >>>>>> Metacello new >>>>>> baseline: 'BlocTutorials'; >>>>>> repository: 'github://pharo-graphics/Tutorials/src'; >>>>>> load >>>>>> >>>>>> >>>>>> A similar booklet could be done for the title >>>>>> 'Doing a presentation / slide show / assitant with Bloc' (or similar, >>>>>> adapt .....) >>>>>> >>>>>> >>>> -- >>>> >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> >>>> "Obvious things are difficult to teach." >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> -- >>> Cheers, >>> Alex > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > >

Nov. 14, 2017

Re: [Pharo-users] About suggestions on Pillar editor (was Re: [ann] pillar text editor)

by Offray Vladimir Luna CÃ¡rdenas

Thanks Doru, Installation works, but syntax hightligthning and image preview are disabled. I don't know if this is because is the same image with the installation of GT Documenter, installed. Cheers, Offray On 14/11/17 12:15, Tudor Girba wrote: > Hi, > > Please retry again by loading the #development version in Pharo 6.1: > > Gofer new > smalltalkhubUser: 'Pier' project: 'Pillar'; > configuration; > loadDevelopment. > > You should get the extension out of the box. > > Please let me know if it works. > > Cheers, > Doru > > >> On Nov 14, 2017, at 5:55 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >> >> Hi, >> >> A suggestion from one year ago. Should be this converted into issues? >> >> Cheers, >> >> Offray >> >> On 10/10/16 13:26, Offray Vladimir Luna CÃ¡rdenas wrote: >>> Hi Doru, >>> >>> I was exploring Stephan Eggermont's code Panel because the zooming in/out behavior implemented there, but I would like to add your Pillar text editor to the exploration. >>> I would like to add two things: >>> >>> 1. Font decrease/increase buttons/shorcuts, because for long documents, default font size can be tiresome. >>> >>> 2. Augmenting the amount of syntax highlighting languages, starting with markdown. I think that this would be strategic in making writing inside the image, more appealing, giving the spread of markdown as a documentation syntax in different context (GitHub, Scholar markdown, wikis, discussion, Slack clones, etc). >>> I installed the extension today on a Pharo 5 system, but trying to use it, bring me the error detailed at the end of this mail, so after having it working on Pharo, I would like to explore/help in implementing items 1 and 2, avove. >>> >>> Cheers, >>> >>> Offray >>> >>> Error report >>> =========== >>> Author: OffrayLuna >>> >>> Array(Object)>>shouldNotImplement >>> Array(ArrayedCollection)>>add: >>> [ :each | self add: each ] in Array(Collection)>>addAll: >>> Array(SequenceableCollection)>>do: >>> Array(Collection)>>addAll: >>> [ :array | >>> ({array first} >>> addAll: array last; >>> yourself) >>> collect: [ :each | >>> ('' join: each first) >>> -> (each second ifNotNil: [ :second | '' join: second ]) ] ] in GTPillarHighlighter>>scriptParameters >>> PPActionParser>>parseOn: >>> PPDelegateParser>>parseOn: >>> PPSequenceParser>>parseOn: >>> PPActionParser>>parseOn: >>> PPDelegateParser>>parseOn: >>> PPChoiceParser>>parseOn: >>> PPDelegateParser>>parseOn: >>> PPChoiceParser>>parseOn: >>> PPPossessiveRepeatingParser>>parseOn: >>> PPDelegateParser>>parseOn: >>> PPEndOfInputParser>>parseOn: >>> GTPillarHighlighter(PPDelegateParser)>>parseOn: >>> GTPillarHighlighter(PPParser)>>parseWithContext: >>> GTPillarHighlighter(PPParser)>>parse:withContext: >>> GTPillarHighlighter(PPParser)>>parse: >>> GTPillarHighlighterTextDecorator>>parse:onError: >>> GLMHighlighterTextParserStyler>>privateStyle: >>> [ self privateStyle: text. >>> view ifNotNil: [ view stylerStyledInBackground: text ] ] in [ backgroundProcess := [ self privateStyle: text. >>> view ifNotNil: [ view stylerStyledInBackground: text ] ] >>> forkAt: Processor userBackgroundPriority ] in GLMHighlighterTextParserStyler(SHTextStyler)>>styleInBackgroundProcess: >>> [ self value. >>> Processor terminateActive ] in BlockClosure>>newProcess >>> =============== >>> >>> On 09/10/16 16:23, Tudor Girba wrote: >>>> Hi, >>>> >>>> Pillar now ships with a text editor that also features a syntax highlighter. >>>> >>>> So, now, if you load the development version of Pillar: >>>> >>>> Gofer new >>>> smalltalkhubUser: 'Pier' project: 'Pillar'; >>>> configuration; >>>> loadDevelopment. >>>> >>>> You will have an extra presentation when inspecting a .pillar file: >>>> >>>> <gjkebecengkghnjk.png> >>>> >>>> The new thing here is that the highlighter is based on the Pillar PetitParser, and it is extensible for highlighting more parts if needed. The highlighting also can support actions. For example, the picture above shows the file to the right after clicking on the reference. >>>> >>>> Please take a look and let me know what you think. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> www.feenk.com >>>> >>>> "Things happen when they happen, >>>> not when you talk about them happening." >>>> > -- > www.tudorgirba.com > www.feenk.com > > "We are all great at making mistakes." > > > > > > > > > >

Nov. 14, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Alistair Grant

On 14 November 2017 at 19:13, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Sean, > > On 14 November 2017 at 19:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Alistair Grant wrote >>> I've committed some fixes to the development branch: >> >> Thanks! >> >> I tried your example, but apparently the OSXProcess class, which is >> referenced in openChromeWith: is missing. Also, no class in the image seems >> to define #createProcess:, which is sent to OSXProcess there > > This looks like you are using an old (cached?) version. Maybe try > "Pull incoming commits" from Iceberg? > > You should have (minus the broken formatting from pasting): > > > OSXChromePlatform>>openChromeWith: arguments > > | executableLocation process | > executableLocation := self defaultExecutableLocation copyReplaceAll: ' > ' with: '\ '. > process := AKGOSProcess command: executableLocation arguments: arguments. > process run. > ^process P.S. Don't forget this is on the development branch. Cheers, Alistair

Nov. 14, 2017