- Pharo-users - lists.pharo.org

Re: [Pharo-users] "Theming" dictionaries?

by Esteban Maringolo

On Wed, Feb 19, 2020 at 2:09 PM Richard Sargent <richard.sargent(a)gemtalksystems.com> wrote: > If you want to have a limited API, you wrap a dictionary with a new class that exposes just the API you desire consumers to use. > > In general, inheritance is often overused or/ misused. Composition is usually a better technique unless you want the full API of the hierarchy to be available and used. +1 to this. Inheriting means accepting the "interface contract" of being able to respond to all the messages understood by its superclasses. It also limits your model to future refactorings and modifications. I rarely, if ever, sub-classify any "base" class for domain modelling, and more so in the case of Collection classes, and when I had to deal with domain classes that did that, it always caused more problems than solutions. Regards, Esteban A. Maringolo

Feb. 19, 2020

Re: [Pharo-users] "Theming" dictionaries?

by Richard Sargent

See below. On Wed, Feb 19, 2020 at 8:49 AM Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > As some of you may know, I'm a "savage coder" who learned > Smalltalk/Pharo by himself, of course thanks to communities, books and > videos, but without formal training or peers in the same country and > guided mostly by necessity. All this to say that this maybe kind of a > silly question. > > Anyway, we have this project called Minipedia[1], that imports Wikipedia > articles and their history. A Minipedia language there, is just a > dictionary, where the key is the language two letters code and the value > for each key is an array of article titles. There is any way to > specialize a Dictionary to tell it, name your 'key' as language and your > 'value' as 'titles'? > There are several ways, depending on your intention. If you intend that the full Dictionary and Collection API is available to all the places where this artefact will be used, you can add extensions to the Dictionary class to provide alias accessing methods or you can also subclass Dictionary and only have your aliases (and whatever API) visible only to consumers of that class. The former is a quick and dirty approach. The latter is better, since every Dictionary is NOT a language keyed collection of article. If you want to have a limited API, you wrap a dictionary with a new class that exposes just the API you desire consumers to use. In general, inheritance is often overused or/ misused. Composition is usually a better technique unless you want the full API of the hierarchy to be available and used. > [1] https://mutabit.com/repos.fossil/minipedia/ > > Thanks, > > Offray > > > >

Feb. 19, 2020

Re: [Pharo-users] "Theming" dictionaries?

by Esteban Maringolo

I'm not sure I fully understand your question. But Dictionaries expect its elements to respond to #key/#value messages, and in the case of Pharo Dictionary is tightly bound to the Association class (and the #-> selector), so there is no way to subclassify Dictionary and specify the class of its elements. Otherwise you could subclassify Dictionary and have its elements to be instances of "MinipediaLanguage", that is polymorphic with Association but have language/titles instead of key/value. I don't see the need for it, though. Esteban A. Maringolo On Wed, Feb 19, 2020 at 1:49 PM Offray Vladimir Luna CÃ¡rdenas < offray.luna(a)mutabit.com> wrote: > Hi, > > As some of you may know, I'm a "savage coder" who learned > Smalltalk/Pharo by himself, of course thanks to communities, books and > videos, but without formal training or peers in the same country and > guided mostly by necessity. All this to say that this maybe kind of a > silly question. > > Anyway, we have this project called Minipedia[1], that imports Wikipedia > articles and their history. A Minipedia language there, is just a > dictionary, where the key is the language two letters code and the value > for each key is an array of article titles. There is any way to > specialize a Dictionary to tell it, name your 'key' as language and your > 'value' as 'titles'? > > [1] https://mutabit.com/repos.fossil/minipedia/ > > Thanks, > > Offray > > > >

Feb. 19, 2020

"Theming" dictionaries?

by Offray Vladimir Luna CÃ¡rdenas

Hi, As some of you may know, I'm a "savage coder" who learned Smalltalk/Pharo by himself, of course thanks to communities, books and videos, but without formal training or peers in the same country and guided mostly by necessity. All this to say that this maybe kind of a silly question. Anyway, we have this project called Minipedia[1], that imports Wikipedia articles and their history. A Minipedia language there, is just a dictionary, where the key is the language two letters code and the value for each key is an array of article titles. There is any way to specialize a Dictionary to tell it, name your 'key' as language and your 'value' as 'titles'? [1] https://mutabit.com/repos.fossil/minipedia/ Thanks, Offray

Feb. 19, 2020

Re: [Pharo-users] Hi-DPI Support

by Renaud de Villemeur

For the mouse pointer, if you're on Windows, you can have a look at VistaCursor Metacello new repository: 'github://astares/Pharo-VistaCursors/src'; baseline: 'VistaCursors'; load It has scale factor available in the settings application. Renaud Feb. 18, 2020, 11:43 by wild.ideas(a)gmail.com: > I'm also looking forward to Hi-DPI support being fully implemented in Pharo. > > Until then, there is the "Display scale factor" slider and the ability to > change the font size. However, most have probably already noticed that > these controls don't affect the size of the mouse pointer, which can be > annoying as it's much harder to find on big screens. > > I recently found this posting, which is helpful: > > Scaling for HiDPI in Pharo: > 1.) Evaluating "MenubarMorph reset" will fix the menu bar scaling factor. > 2.) There's a SQUEAK_FAKEBIGCURSOR env var which you can set to 1 to have > the VM > display the cursor twice as big as normal. I've no idea why the word 'FAKE' > is > part of this; from the source it looks like it just creates a normal X11 > cursor > that's twice as big as normal. This should work with Cuis, Squeak, and > Pharo, > as it's part of the VM. > > I found that entering "export SQUEAK_FAKEBIGCURSOR=1" will cause standalone > Pharo to have a normal-looking pointer on 4K displays, but this does not > seem to work as expected with Pharo Launcher, or images launched with Pharo > Launcher. > > After some investigation, I determined that the 'pharo-launcher', 'pharo' > and 'pharo-ui' bash scripts (for Pharo Launcher and Pharo IOT) can be > modified to make this work. > > The trick is to add "env SQUEAK_FAKEBIGCURSOR=1" to the front of the command > that launches the VM/image within the above scripts. > > I've fashioned a set of 'sed' one-liners to automate editing these scripts > accordingly, and am in the process of making a bash script that will use > them to add/remove/verify these edits in a user-friendly fashion. (I also > have scripts that install Pharo Launcher and Pharo IOT in Linux, that create > & add clickable launcher icons; my plan was to modify these scripts to write > the cursor size correction scripts into their respective folders when > they're installed.) > > I'll make this available when it's complete, likely in the next couple of > days. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Feb. 19, 2020

Ubuntu64 install fine, would like to port to Slackware64

by tty

Hi Folks, Pharo 64 launch on Ubuntu 64 launches fine. When I launch Pharo 64 on Slackware 64 I get library call errors . This is probably because Slackware64 stores its libraries in /lib64. Ubuntu stores its 64 bit libs in /lib I much prefer Slackware to Ubuntu. Is there a variable I can set within the Pharo Launcher or elsewhere to have it hit the /lib64 location ? thanks in advance -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2020

Re: [Pharo-users] About DuneSt / ChartJs

by Sven Van Caekenberghe

I added a comment and some code to https://github.com/DuneSt/ChartJs/issues/1 > On 12 Feb 2020, at 10:54, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Guillaume, > > Thank you for your reply. > > I see that the version supported/implemented in DuneSt/ChartJs is 1.0.2 (from 2015) while the current Chart.js version is 2.0, so it would probably be time for an upgrade. > > I also don't know the perfect answer to the Seaside dependency, I'll write some more in another reply. > > I tried making a sub class of ChartBar called ChartHorizontalBar overwriting only > > forChartJS > ^ 'HorizontalBar' > > and then using that as an argument to #chartType: but alas that did not work. > > I must admit that I do not really understand how I have to mentally map the official JavaScript documentation to the model in Pharo and how it is implemented (#forChartJS does not seem to be used as argument/value but as a function call). > > Sven > >> On 11 Feb 2020, at 20:12, Guillaume Larcheveque <guillaume.larcheveque(a)gmail.com> wrote: >> >> >> >> Le mar. 11 fÃ©vr. 2020 Ã 17:07, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : >> Hi, >> >> I am trying to use DuneSt / ChartJs [ https://github.com/DuneSt/ChartJs ] and it looks good. Thanks for another nice library. >> You're welcome and we are pleased that you use it :-) >> >> My first question is about loading the code. I would like to load the minimum possible. I guess the stylesheet code is needed, but not the prism code ? >> You are totally right, Prism is required by the demo to display the code. You will not load it by using the 'core' group >> >> NeoJSON and Seaside are already in my project's dependencies, but Seaside3 seems to never resolve to the same thing, so I would like to skip that. Is that possible ? I have this issue often with Seaside. I could fork and edit the baseline, but I'd rather not. >> I have the same opinion, if you have a solution to manage it in a nice way i would be pleased to add it. I only see as a solution to create a group that do not load Seaside3 but maybe Cyril know a better way to do it (he is far better than me about baselines) >> >> I got a Bar chart on 2D data running right away. >> >> But how can I use 'horizontalBar' as type ? >> >> var myBarChart = new Chart(ctx, { >> type: 'horizontalBar', >> data: data, >> options: options >> }); >> >> I see that the types are encoded a classes, but the list seems rather limited. >> We implemented the minimum that is required for us. It is really easy to add new ones as you already discovered. I will add these as soon as possible or if you already did it, create a pull request. There is many improvement that can be done in this project and it would be great to have your contribution about it. >> >> We will move to the new version of the ChartJs library when we will have time to improve it. Of course the API of our project will stay the same and changes will not impact your project. >> >> Thx, >> >> Sven >> >> >> >> >> -- >> Guillaume Larcheveque >> >

Feb. 18, 2020

Re: [Pharo-users] Hi-DPI Support

by tbrunz

I'm also looking forward to Hi-DPI support being fully implemented in Pharo. Until then, there is the "Display scale factor" slider and the ability to change the font size. However, most have probably already noticed that these controls don't affect the size of the mouse pointer, which can be annoying as it's much harder to find on big screens. I recently found this posting, which is helpful: Scaling for HiDPI in Pharo: 1.) Evaluating "MenubarMorph reset" will fix the menu bar scaling factor. 2.) There's a SQUEAK_FAKEBIGCURSOR env var which you can set to 1 to have the VM display the cursor twice as big as normal. I've no idea why the word 'FAKE' is part of this; from the source it looks like it just creates a normal X11 cursor that's twice as big as normal. This should work with Cuis, Squeak, and Pharo, as it's part of the VM. I found that entering "export SQUEAK_FAKEBIGCURSOR=1" will cause standalone Pharo to have a normal-looking pointer on 4K displays, but this does not seem to work as expected with Pharo Launcher, or images launched with Pharo Launcher. After some investigation, I determined that the 'pharo-launcher', 'pharo' and 'pharo-ui' bash scripts (for Pharo Launcher and Pharo IOT) can be modified to make this work. The trick is to add "env SQUEAK_FAKEBIGCURSOR=1" to the front of the command that launches the VM/image within the above scripts. I've fashioned a set of 'sed' one-liners to automate editing these scripts accordingly, and am in the process of making a bash script that will use them to add/remove/verify these edits in a user-friendly fashion. (I also have scripts that install Pharo Launcher and Pharo IOT in Linux, that create & add clickable launcher icons; my plan was to modify these scripts to write the cursor size correction scripts into their respective folders when they're installed.) I'll make this available when it's complete, likely in the next couple of days. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 18, 2020

[Pharo-dev] [ANN] Pharo TechTalk Feb 20: The Colony

by Marcus Denker

*** this Thursday *** A regular chat about Pharo. Happens on Discord. This month a bit a special TechTalk, not about Pharo but about a tool that might be interesting for us to use. Topic: The Colony https://colony.io <https://colony.io/> Introduction to "The Colony", a new platform to Organize and Incentivize Collaborators, Contributors, and Communities. Short demo, followed by some Q&A, help to get people onboarded. https://association.pharo.org/event-3697011 <https://association.pharo.org/event-3697011> 20 Feb 2020 â¢ 1:30 PM - 2:30 PM (EST) NOTE: this is EST time, for Europe, this is 19:30 (the easiest is to download the calendar entry)

Feb. 18, 2020

Hi-DPI Support

by Steffen MÃ¤rcker

Hi, I'd like to ask about the state of Hi-DPI support for Pharo. I already found two related GitHub issues which where inconclusive so far. Does the discussion take place elsewhere? If so, where? If not: - What is the current state? - Does a plan exist how to get there? - What are the missing pieces? - How can I support this endeavor in practice? Best, Steffen

Feb. 18, 2020