- Pharo-users - lists.pharo.org

Re: [Pharo-users] Persistant Taskbar Previews

by Sven Van Caekenberghe

I would guess you have 2 instances of the Morphic UI process, probably left over from some debugging. Kill one using the Process Browser. But this is just a blind guess. > On 13 Oct 2018, at 04:51, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Fri, 12 Oct 2018 at 18:57, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Hi, > > Using Pharo 6.1 for some hours, I ended up with quite a few previews from > (long gone) taskbar entries that refuse to go away. They seem to be > PanelMorphs. How do I get rid of them? > > Best, Steffen > > I'd guess like any morph you could meta-click on them and choose to delete them. > e.g. on Windows SHIFT-ALT-middleClick > > cheers -ben

Oct. 13, 2018

Re: [Pharo-users] Persistant Taskbar Previews

by Ben Coman

On Fri, 12 Oct 2018 at 18:57, Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Hi, > > Using Pharo 6.1 for some hours, I ended up with quite a few previews from > (long gone) taskbar entries that refuse to go away. They seem to be > PanelMorphs. How do I get rid of them? > > Best, Steffen > I'd guess like any morph you could meta-click on them and choose to delete them. e.g. on Windows SHIFT-ALT-middleClick cheers -ben

Oct. 13, 2018

Re: [Pharo-users] GlorpSQLite Github release management

by Ben Coman

On Fri, 12 Oct 2018 at 14:04, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Pierce, > > On Fri, 12 Oct 2018 at 06:21, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > > > Hi all, > > > > So GlorpSQLite works on Pharo 5 and 6, but not yet on Pharo 7. > > I've been using GlorpSQLite in Pharo 7 since development started. It > is loaded from another package's baseline as: > > spec > baseline: 'GlorpSQLite' with: [ > spec repository: 'github://pharo-rdbms/glorp-sqlite3' ]. > > I have some patches for date and time handling which I load on top > (and should really submit as a patch), but I don't think these are > Pharo 7 related. > > > > Currently, I have the following: > > > > https://github.com/PierceNg/glorp > > https://github.com/PierceNg/glorp-sqlite3 > > > > Which are forks of these: > > > > https://github.com/pharo-rdbms/glorp > > https://github.com/pharo-rdbms/glorp-sqlite3 > > I'll take a look. > > > > I'm thinking to create a release, say, v1.0, for the current known > > working GlorpSQLite combo for Pharo 5 and 6 in my repos, then, ... > > create a branch for Pharo 7? Then turn the branch into release v2.0 when > > ready? If there is no change to the GlorpSQLite API, but just the implementation (i.e. on Pharo 7), then v1.1 seems a better choice of version number. > I do all of these actions in my repo, and through pull requests > > to upstream, Git will take care of synchronizing across the forks? > Note that git branches are simply pointers to a particular commit hash. There is no computational link between the "branch name" in your repo and the "branch name" in the target repo. On github you can create a PR from any repo/branch to any other repo/branch that exists. As Alistar indicated, if you want a particular "branch name" in the target repo, it needs to have already been created there. Then you can submit a PR to it from any branch in your repo. > I'm not a git expert either, but I suspect the branches will need to > be created in the main repository. The modifications can then be > applied to the appropriate branch as a PR. > btw, for a reproducability of a "release" version, my understanding is that in the canonical repo, tags are better than branches because tags are permanently tied to a particular while branches move. (However I've not direct experience with this) cheers -ben

Oct. 13, 2018

Re: [Pharo-users] [Moose-dev] Re: Re: Plotting genome scale values with Roassal

by Alexandre Bergel

Hi HernÃ¡n, Sorry for the late reply. Regarding your first question, you can do: -=-=-=-=-=-= g := RTGrapher new. d := RTData new. d connectColor: Color blue. d noDot. d points: (-3.14 to: 3.14 by: 0.1). d y: #sin. d x: #yourself. g add: d. g axisX numberOfTicks: 10; numberOfLabels: 5. g -=-=-=-=-=-= As you can see, the line "g axisX numberOfTicks: 10; numberOfLabels: 5.â allows you to set the number of ticks and the number of labels. Regarding your second question, where can I find the file OrderedCollection_3712516797.obj ? Or, how can I reproduce it. Anyway, I believe the problem is that you have too many points. In this case, I suggest you to reduce the number of points. For example, a slight variation of the previous example [DO NOT RUN IT]: -=-=-=-=-=-= points := -3.14 to: 3.14 by: 0.000001. g := RTGrapher new. d := RTData new. d connectColor: Color blue. d noDot. d points: points. d y: #sin. d x: #yourself. g add: d. g axisX numberOfTicks: 10; numberOfLabels: 5. g -=-=-=-=-=-= The script tries to build the same graph but with 6 280 001 points. Which obviously, is way too many. Instead, you can do something like: -=-=-=-=-=-= points := SortedCollection new. 1000 timesRepeat: [ points add: (-3.14 to: 3.14 by: 0.000001) atRandom ]. g := RTGrapher new. d := RTData new. d connectColor: Color blue. d noDot. d points: points. d y: #sin. d x: #yourself. g add: d. g axisX numberOfTicks: 10; numberOfLabels: 5. g -=-=-=-=-=-= Which only display the graph with 1000 points. Cheers, Alexandre > On Oct 4, 2018, at 12:49 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > This is weird, could you check: > > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2018-October/0… > > HernÃ¡n > > El miÃ©., 3 oct. 2018 a las 22:41, Alexandre Bergel > (<alexandre.bergel(a)me.com>) escribiÃ³: >> >> I am lost. What are the questions? I do not see them in the mailing list. >> >> Alexandre >> >>> On Oct 3, 2018, at 11:11 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>> >>> Hi Alex, >>> >>> Thanks. Please note there are two questions related to Roassal :) >>> I have isolated the script so you don't need to load BioSmalltalk >>> >>> Maybe someone can check or give a hint? >>> >>> El mar., 2 oct. 2018 a las 22:31, Alexandre Bergel >>> (<alexandre.bergel(a)me.com>) escribiÃ³: >>>> >>>> Pretty cool! >>>> >>>> Alexandre >>>> >>>>> On Oct 2, 2018, at 2:21 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >>>>> >>>>> <a TRMorph(28411392).png><skew_diagram_ecoli.png> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)list.inf.unibe.ch >>>> https://www.list.inf.unibe.ch/listinfo/moose-dev >>> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev >

Oct. 12, 2018

Persistant Taskbar Previews

by Steffen MÃ¤rcker

Hi, Using Pharo 6.1 for some hours, I ended up with quite a few previews from (long gone) taskbar entries that refuse to go away. They seem to be PanelMorphs. How do I get rid of them? Best, Steffen

Oct. 12, 2018

Re: [Pharo-users] GlorpSQLite Github release management

by Alistair Grant

Hi Pierce, On Fri, 12 Oct 2018 at 06:21, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > Hi all, > > So GlorpSQLite works on Pharo 5 and 6, but not yet on Pharo 7. I've been using GlorpSQLite in Pharo 7 since development started. It is loaded from another package's baseline as: spec baseline: 'GlorpSQLite' with: [ spec repository: 'github://pharo-rdbms/glorp-sqlite3' ]. I have some patches for date and time handling which I load on top (and should really submit as a patch), but I don't think these are Pharo 7 related. > Currently, I have the following: > > https://github.com/PierceNg/glorp > https://github.com/PierceNg/glorp-sqlite3 > > Which are forks of these: > > https://github.com/pharo-rdbms/glorp > https://github.com/pharo-rdbms/glorp-sqlite3 I'll take a look. > I'm thinking to create a release, say, v1.0, for the current known > working GlorpSQLite combo for Pharo 5 and 6 in my repos, then, ... > create a branch for Pharo 7? Then turn the branch into release v2.0 when > ready? I do all of these actions in my repo, and through pull requests > to upstream, Git will take care of synchronizing across the forks? I'm not a git expert either, but I suspect the branches will need to be created in the main repository. The modifications can then be applied to the appropriate branch as a PR. > Does the above sound workable? Is there a better approach? > > Pierce, Git noob >

Oct. 12, 2018

GlorpSQLite Github release management

by Pierce Ng

Hi all, So GlorpSQLite works on Pharo 5 and 6, but not yet on Pharo 7. Currently, I have the following: https://github.com/PierceNg/glorp https://github.com/PierceNg/glorp-sqlite3 Which are forks of these: https://github.com/pharo-rdbms/glorp https://github.com/pharo-rdbms/glorp-sqlite3 I'm thinking to create a release, say, v1.0, for the current known working GlorpSQLite combo for Pharo 5 and 6 in my repos, then, ... create a branch for Pharo 7? Then turn the branch into release v2.0 when ready? I do all of these actions in my repo, and through pull requests to upstream, Git will take care of synchronizing across the forks? Does the above sound workable? Is there a better approach? Pierce, Git noob

Oct. 12, 2018

Re: [Pharo-users] World Cup 2018 with Glorp : SQL dump for SQLite : wc2018.sql

by Pierce Ng

On Thu, Oct 11, 2018 at 06:45:07PM +0200, H. Hirzel wrote: > Hi Pierce > > In your blog entry > 'World Cup 2018 with Glorp' > you write about an SQL dump file wc2018.sql and mention a repo? > > https://github.com/openfootball/world-cup/tree/master/2018--russia > > seems to be a candidate, but on SQL. > > In which repo is it? Hi Hannes, I built SQLite databases from the data in https://github.com/openfootball/datafile.git, then generated the SQLite dump files, which went into the 'data' directory in my repo https://github.com/PierceNg/footballdb-Glorp. I don't remember whether the WC 2018 dump file has the match results, but the WC 2014 one ought to contain the full tournament data. Pierce

Oct. 12, 2018

Re: [Pharo-users] What is the easiest way to get SQLite3 support in Pharo7? (Ubuntu)

by Pierce Ng

On Thu, Oct 11, 2018 at 06:27:21PM +0200, H. Hirzel wrote: > Great! Just this very minute before I saw your mail I found your > website with a lot of Pharo related SQLite posts. Enjoy! :-) > Are you the maintainer of GlorpSQLite? Yes, I wrote it and I am maintaining it. Pierce

Oct. 12, 2018

Re: [Pharo-users] [vwnc] Parsing in Smalltalk

by Steffen MÃ¤rcker

Hi, I tried it some more times and things are different now: - image appeared to lock up (1st) - no network traffic at all (2nd) - image unresponsive, loading successful after 2 minutes (3rd) Call me a fool, but I didn't do anything different. Notably, it succeeded each time in 7.0. =) > There is no specific reason to use SmallInteger maxVal... and nobody > ever thought it might be too little. Maybe it makes sense to change this? It appears to be just wrong and on 32bit the limit is well in practical reach. With a little guidance, I'd try to do a first PR myself (if the change is considered sensible). I was mentioning #min: since it is implemented in terms of 'min: min max: SmallInteber maxVal'. Is there an easy way to create a character class, similar to [1-2x-z]? Best, Steffen > Use $- asPParser for characters, e.g: > $- asPParser parse: '-' > > [1]: https://travis-ci.org/kursjan/petitparser2/builds/438358467 > > On Thu, Oct 11, 2018 at 8:13 PM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > >> Reading the code of PetitParser, I wonder why PPRepeatingParser >> initializes 'max' with SmallInteger maxVal instead of some notion of >> infinity, like Float infinity (and PP2RepeatingNode as well). If I >> understand the code correctly, PParser>>min: fails if the number of >> repetitions exceeds SmallInteger maxVal, doesn't it? >> >> Best, Steffen >> >> >> Am .10.2018, 17:10 Uhr, schrieb Steffen MÃ¤rcker <merkste(a)web.de>: >> >> > I am using MacOS 10.13.6 and the 32bit VM: >> > >> > Pharo 6.0 >> > Latest update: #60546 >> > >> > ... the String in about is wrong, it should be 6.1. I installed it via >> > the launcher as "Official Distribution: Pharo 6.1 - 32Bit (stable)" I >> > just noticed, that the sources file is missing from vms/private/6521/, >> > too. >> > >> > Am .10.2018, 17:02 Uhr, schrieb Sean P. DeNigris >> <sean(a)clipperadams.com >> >: >> > >> >> Steffen MÃ¤rcker wrote >> >>> I did the following: >> >>> 1) Download and start Pharo 6.1 stable via the launcher. >> >>> 2b) Attempt to install PP2 via the scripts from GitHub: >> >>> Metacello new >> >>> baseline: 'PetitParser2'; >> >>> repository: 'github://kursjan/petitparser2'; >> >>> load. >> >>> Metacello new >> >>> baseline: 'PetitParser2Gui'; >> >>> repository: 'github://kursjan/petitparser2'; >> >>> load. >> >> >> >> This way worked for me in Pharo #60546 (check in >> World->System->About). >> >> What >> >> exact Pharo version/OS are you on? 32 or 64-bit >> >> >> >> >> >> >> >> ----- >> >> Cheers, >> >> Sean >> >> -- >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> > >> > >>

Oct. 11, 2018