November 2017 - Pharo-users

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

by Alistair Grant

On 9 November 2017 at 00:00, Kjell Godo <squeaklist(a)gmail.com> wrote: > i like to collect some newspaper comics from an online newspaper > but it takes really long to do it by hand by hand > i tried Soup but i didnât get anywhere > the pictures were hidden behind a script or something > is there anything to do about that? Most of the web pages I want to scrape use javascript to construct the DOM, which makes Soup. XMLHTMLParser, etc. useless. I've extended Torsten's Pharo-Chrome library and use that to navigate the DOM in a way similar to Soup: https://github.com/akgrant43/Pharo-Chrome This gets around the issue with javascript since it waits for the browser to load the page, run the javascript and construct the DOM. HTH, Alistair > i donât want to collect them all > i have the XPath .pdf but i havenât read it yet > > these browsers seem to gobble up memory > and while open they just keep getting bigger till the OS session crash > might there be a browser that is more minimal? > > Vivaldi seems better at not bloating up RAM

Nov. 11, 2017

Re: [Pharo-users] Why is compile: breaking my image?

by Peter UhnÃ¡k

Never mind... I see now what is broken and I'll try to fix it (assuming my P7 image won't corrupt itself due to FreeType before I manage to push the changes... heh) On Sat, Nov 11, 2017 at 3:43 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > This applies to P61 (for some time) and P7. > > Object compile: '^'. > > Syntax Error popup -> close > > now you have two morphic UI processes running and World starts to get > corrupted with artifacts around. (and it also in one case manage to > actually corrupt the image to the point that I was no longer able to even > launch it). > > Peter >

Nov. 11, 2017

Why is compile: breaking my image?

by Peter UhnÃ¡k

This applies to P61 (for some time) and P7. Object compile: '^'. Syntax Error popup -> close now you have two morphic UI processes running and World starts to get corrupted with artifacts around. (and it also in one case manage to actually corrupt the image to the point that I was no longer able to even launch it). Peter

Nov. 11, 2017

RewriteTool maintained?

by Peter UhnÃ¡k

Hi, has Mark Rizun's Rewrite Tool been abandoned? Thanks, Peter

Nov. 11, 2017

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

by Stephane Ducasse

Hannes We will start to repackage pillar model so finding a mini pillar is interesting to us. Let let us know. Stef On Sat, Nov 11, 2017 at 7:51 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > >> On Nov 10, 2017, at 9:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Tudor Girba-2 wrote >>> As shown at ESUG, GT Documenter offers an advanced viewer (and editor) for >>> Pillar working on top of Bloc. >> >> Two questions after playing with it: >> 1. Can one save a live-edited file? > > The saving action is not implemented yet. > >> 2. Is it possible to make the markup codes invisible? That would seem more >> appropriate e.g. in a read-only context. > > That would be another renderer, but it is not difficult to build. That is something weâll do soon. > > Cheers, > Doru > >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > > -- > www.tudorgirba.com > www.feenk.com > > "Beauty is where we see it." > > > > >

Nov. 11, 2017

Re: [Pharo-users] Unable to load SmaCC on pharo6 (or pharo5)

by Stephane Ducasse

>> >> Hi thierry >> >> we are working and soon we will have a much simpler installation and >> everything :) > > > Out of a minimal image? That would be very cool. Uh? The problem is latex and not Pharo here. Guille removes the need for makefiles and clean the archetypes we will be able to move on. > >> Now just commit and I will check and fix :) > > > I committed, created a pull request and merged. It should be Ok apart from: > > - can hyphenating be desactivated in ==sequences==? It is allways strange to > see a class name or a method name split by a hypen, like in SmaCC-Parser No > - how does one writes a reference to a section or a chapter? *@xxx* > > Thierry > > >> >> Stef >> >> On Fri, Nov 10, 2017 at 6:47 AM, Thierry Goubier >> <thierry.goubier(a)gmail.com> wrote: >>> >>> Le 09/11/2017 Ã 21:02, Stephane Ducasse a Ã©crit : >>>> >>>> >>>> Yes thierry :) your turn now :) >>> >>> >>> >>> That's will be harder than I expected. I have issues in the LaTeX setup >>> used >>> by the booklet. >>> >>> Thierry >>> >>> >>>> >>>> Stef >>>> >>>> On Thu, Nov 9, 2017 at 8:41 PM, Thierry Goubier >>>> <thierry.goubier(a)gmail.com> wrote: >>>>> >>>>> >>>>> Le 09/11/2017 Ã 20:15, Federico.Balaguer a Ã©crit : >>>>>> >>>>>> >>>>>> >>>>>> I am following this tutorial >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> http://files.pharo.org/books-pdfs/booklet-Smacc/2017-05-05-Smacc-Spiral.pdf >>>>>> >>>>>> I typed the first example and when I try to compile either LR(1) or >>>>>> LALR(1) >>>>>> there is a pop-up saying that both clases where not specified. I also >>>>>> tried >>>>>> adding the classes for the scanner and parser manually but I got the >>>>>> result. >>>>> >>>>> >>>>> >>>>> >>>>> Yes. I changed the GUI and that means I need to update the booklet. >>>>> >>>>> This part: >>>>> >>>>> â¢ Edit the definition the pane below the compile LR(1) buttons. >>>>> â¢ Once you are done: >>>>> â Click on the Scanner class and type ExpressionScanner. >>>>> â Click on the Parser class and type ExpressionParser. >>>>> â¢ press either Compiler LR(1) or Compiled LALR(1) buttons. >>>>> >>>>> Should now be: >>>>> >>>>> â¢ Edit the definition the pane below the compile LR(1) buttons. >>>>> â¢ Once you are done: >>>>> â Type ExpressionParser and return in the text field left of Parser:. >>>>> â¢ press either Compiler LR(1) or Compiled LALR(1) buttons. >>>>> >>>>>> There are a couple other things in the tutorial at the very start that >>>>>> didn't add up. I can send an annotated pdf if that is of any help >>>>> >>>>> >>>>> >>>>> >>>>> Yes, that would be very helpfull! >>>>> >>>>> Thanks, >>>>> >>>>> Thierry >>>>> >>>>> >>>>>> >>>>>> Thanks!! >>>>>> >>>>>> Federico >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >

Nov. 11, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

> > Itâs quite a moving target with so many fundamental changes (GIT being one, Bootstrap another huge one). I would not call it moving target. The API changes slowly and we deprecate most of them. > But I have the opposite impression (of course I donât have to maintain a big project like yours - I wouldnât say youâre the hobby user :) ). But I really find P6 more consistent than what I used to try in the past (last squeaks up to 3.9 and firsts pharo). Me too. > And the bootstrapping of P7 will (I think) finally solve big image issues (allowing to build cleaner distributions). I believe it will be a huge step forward. At least for me and especially to convince others to try out Pharo. > I just dream of having a network of small images running and communicating, eventually accessed and programmed by a larger developper image (with TelePharo). Yes we want the same. > I havenât tried the bootstrap yet but sure in the future. It is working already and you can use the Bootstrap. Pavel has been working on providing package and configurations that we can reload. > Plus I have the impression Morphic mess is about to be solved. Well I hope :) > Whatâs more problematic to me (as I guess for newcomers) is to find the âgoodâ packages'. For instance, Iâm still puzzled when I have to choose between OSProcess and OSSubprocess (and sometimes depending on loaded projects, we need bothâ¦). People should document their packages and publish them in the meta catalog. We cannot do more. We should publish a package market but we are behind our plans. > >> >> I decided I will not finish porting DrGeo to P6 or P7, and it will likely die with P3. >> >> Pharo should have been clean up to the bones before adding. It was the initial moto, no? > > I have the (naive) impression that bootstrap will help a lot here, so be patient ;). Maybe porting to P7/P8 will be more appropriate. > What I would like, is a kind of notation for package to know its state and usage possibilities. > We see for instance that several I18N exists already (but not 100% integrated hence this post)... > > My 2 cents, > > CÃ©drick > > > OT question: Would it be possible in the future to generate a bootstrap image of a given program from a bigger developer image containing running program (like if running tests where activating all code dependancies ? â¦ like tracing usageâ¦ I guess this is not trivial at all ! I guess this is particularly difficult to trace all use cases and as dynamically bound, it sure must be hard). Yes guille did it with tornado. Now it was experiemental. You will be in better shape to take the miniimage and load what you need. > >> >> >> Le 10/11/2017 Ã 11:14, Marcus Denker a Ã©crit : >>> It would be nice if someone who uses it would take the lead >>> so we can improve the default that is shipped with Pharo. >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> > >

Nov. 11, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

Hilaire I think that Pharo is getting a lot more modular. Do you imagine that we can reload Morphic? That we have a minimal image that does not rely on the compiler? and that we can reload the compiler, SUnit and more. We will start another pass because we will run an experience to get microPharo. Did you see the amazonLambda experience? Many people are telling to us that Pharo and that the system is improving and it is really improving. Now we do not make progress without breaking eggs. And we are cleaning but probably things that you do not care: such as startup list, streams, layouts We will throw away a lot of code with Bloc too. > A cleaner Pharo will help there. > > To be frank, I found later Pharo releases not inspiring. Bigger, bigger and > bigger with added code, protocol changes, and bugs at will. Hilaire - when did you report bugs that we did not consider? and that we did not fix if it was something that we could do fast? > It is becoming > too complicated for a hobby use of it. > > I decided I will not finish porting DrGeo to P6 or P7, and it will likely > die with P3. I'm sad that you decided that because we like DrGeo. Now we cannot do much if you do not want to do it. May be you should come to visit us from time to time. > Pharo should have been clean up to the bones before adding. It was the > initial moto, no? And this is what we are doing. But seriously do you think that it is easy? Did you look at the ESUG videos of Prague. I can tell you that christophe, pavel and guille worked several months and this is not just for hacking around. So you probably do not know what we did and what we are doing. Stef > > > Le 10/11/2017 Ã 11:14, Marcus Denker a Ã©crit : >> >> It would be nice if someone who uses it would take the lead >> so we can improve the default that is shipped with Pharo. > > > -- > Dr. Geo > http://drgeo.eu > > >

Nov. 11, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

Marcus translate is incomplete and I would not focus on translating Pharo. I would prefer to improve the self documentation in english. Let us concentrate where we can get better. Stef On Fri, Nov 10, 2017 at 11:20 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 10 Nov 2017, at 11:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > On 10 Nov 2017, at 04:05, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > 2017-11-09 23:50 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >> I think this is two different problems: >> >> 1. pharo itself supporting different languages/keyboards, etc. >> 2. pharo allowing the development of i18n applications >> >> I think we still need to work on point 1, but for point 2 we already have >> gettext package, which is a standard we can/should use. Maybe that needs to >> be better documented (as everything), but wellâ¦ we have a solution there :) > > > Will we include it into the standard image? > > > No. The whole idea with PharoExtras was âthere are packages we care about > and we want to make them available, but there is no reason to keep them *in* > imageâ. > I do not see why we should change that policy. > > Now, we definitively need better documentation about it. > > > But having I18 support is not badâ¦ e.g. there are many programs out there > that provide translated menus. > It would not be completely a bad idea to do that for Pharo, too. > > Marcus >

Nov. 11, 2017

Re: [Pharo-users] I18n in pharo

by Stephane Ducasse

tx hiliare for the feedback. On Fri, Nov 10, 2017 at 11:10 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > You can go with http://smalltalkhub.com/#!/~PharoExtras/Gettext > > For non latin language you will have to provide extra font at load time. > > It works fine on DrGeo based on P3, wtih Latin, Cyrilic, Korean, Chinese > ideogram, Japanese[1] messages. > > I have no idea regarding its compatibility with P7 however. > > Will not work with right to left languages, though. > > For asian input methods, a no go too. > > Hilaire > > [1] https://twitter.com/GNUDrGeo/status/832878470216691712 > > > Le 09/11/2017 Ã 21:29, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² a Ã©crit : >> >> It is very important for huge commercial applications, especially with >> lots of UI forms, dialogs and user-messages. > > > -- > Dr. Geo > http://drgeo.eu > > >

Nov. 11, 2017