January 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Releasing to Catalog

by Evan Donahue

Ok, that works. Thanks. My last question is about adding a development symbolic version. Can I use my existing BaselineOf class somehow as a baseline from within my ConfigurationOf "<symbolicVersion: #development>" method, or should I define a redundant "baseline: spec" method in the Configuration of the old fashioned way? Thanks, Evan -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 3, 2018

Re: [Pharo-users] Metacello with Git

by Sean P. DeNigris

EstebanLM wrote > yep. that seems to be a bug. Okay, I hacked a solution. Before I submit the fix I want to verify: no one has been successfully using gitlab:// URLs in a MetaC baseline spec for a private dependent project (accessed via SSH keys), right? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 2, 2018

Re: [Pharo-users] Solver for the Stable Marriage problem in Pharo

by Sean P. DeNigris

Julien wrote > Continuing to announce what I have. Hooray!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 2, 2018

Re: [Pharo-users] More named colors

by Stephane Ducasse

Thanks cyril for the links I will read that. On Mon, Jan 1, 2018 at 3:52 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On lun. 1 janv. 2018 at 15:32, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Hi >> >> Since for some experiences in moose we needed more named colors >> I started to gather together some old extensions and I cleaned the >> implementation. >> Now we have emacs colors and XKCD i.e around 1600 named colors. >> >> Gofer new >> smalltalkhubUser: 'StephaneDucasse' project: 'Colors'; >> package: 'MoreColors'; load. >> Color initializeNames >> >> I would really like to see how we can model the notion of color palettes. > > > Hi, > > Material Design have some recommandations that are nice. > > They recommande to have two colors for an application: > - A primary color > - An accent color > > The primary color is the main color of the application and the accent color > is to make some highlights (links, important buttons...) > > For each color they defined scales. Each color have a code (50, 100, 200, > 300, 400, 500, 600, 700, 800, 900). > > The base code is 500. If you need something "less important", with less > contrast, you takes a lower code. For more contrast, you takes a higher > code. > > See here: https://www.materialui.co/colors > > Also they have recommendation for text color. > > Dependently of the background color they define if the text should be white > or black. (This is defined by the luminescence of the color in Pharo). Also, > they define different text color if you have a primary text or a secondary > text. > > See: https://material.io/guidelines/style/color.html > >> >> Stef >> > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France

Jan. 2, 2018

Re: [Pharo-users] [ANN] Python3Generator and MatplotLibBridge

by Stephane Ducasse

On Mon, Jan 1, 2018 at 8:22 PM, Julien <julien.delplanque(a)inria.fr> wrote: > Hello, > > My new year main resolution: stop keeping my side-projects for me. I ***LOVE IT*** Last year I took as decision, release all the books that I had half finished :) and I ended up creating the booklets to flush my hardisc. Stef > > Itâs been like 1 year that I created these two projects, one coming from a > refactoring of the other. > Now it is time to take time to announce them. > > I initially come from Python world and during my bachelor & master, I really > liked to use matplotlib to plot data using Python. > > So I wanted to be able to use this Python module from Pharo. I did it by > generating Python 3 code from Pharo and making Python 3 executing it. So, > first I implemented everything in MatplotLibBridge package and then I split > it in two package in order to be able to eventually create bridges to other > Python 3 modules. > > So, Python3Generator [1] is made for generating programatically Python 3 > code from Pharo. Basically, it allows you to easily build a Python 3 AST, > to serialize it in Python 3 source code and eventually to execute it. For > now you can transfer data from Pharo to Python (e.g. providing arguments to > functions that are Pharoâs objects) but you can not retrieve data stored in > Python variable from Pharo (but it should be possible, just I donât need to > do that for my bridge to matplotlib). Some examples are provided on the > githubâs README. > > MatplotLibBridge [2] is made for creating plots using matplotlib [3] from > Pharo. There is a bunch of examples of what you can do on the README. The > two features from matplotlib I like the most are: 1. You can generate your > plot in a lot of file formats (png, pdf, svg, ps, etcâ¦) 2. It allows to > embed LaTeX mathematical formulae everywhere in the plot (which can be > really cool). All the possible plots in matplotlib are not available in > Pharoâs side because I build parts of the bridge when I need them but it is > not hard to do. I someone is interested in a plot type not available yet, > please tell me. > > So, it is announced, if someone want to do something with those, please do > it! > > Happy new year. > > Regards, > > Julien > > [1]: https://github.com/juliendelplanque/Python3Generator > [2]: https://github.com/juliendelplanque/MatplotLibBridge > [3]: https://matplotlib.org > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille 1 > http://juliendelplanque.be/phd.html > Equipe Rmod, Inria > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >

Jan. 2, 2018

Re: [Pharo-users] Another post about our experience with Pharo at OSOCO

by Stephane Ducasse

Hi Rafael Thanks a lot for sharing that with us. This is super interesting to see the process. I wish you a lot of other Pharo microservices and systems :) Stef On Tue, Jan 2, 2018 at 3:30 PM, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Not at the moment, but we have plans to release both the code generator and > the EDA framework shortly, so I will back to you when we publish them. > > Rafa. > > 2018-01-02 14:26 GMT+00:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: >> >> Hi Rafael, >> >> Did you published your code generator somewhere? >> I would like to check since I am writing a code generator for Pharo >> http://www.smalltalkhub.com/#!/~hernan/CodeGenerator >> Cheers, >> >> HernÃ¡n >> >> 2018-01-02 8:48 GMT-03:00 Rafael Luque <rafael.luque.leiva(a)gmail.com>: >> > Hi all, >> > >> > We've published the second part of our experiences introducing Pharo at >> > OSOCO. >> > >> > The post is in spanish: >> > https://osoco.es/thoughts/2017/12/pharo-en-osoco-parte-2/ >> > >> > However, I've checked that Google Translate does a good job with it: >> > >> > https://translate.google.com/translate?sl=es&tl=en&js=y&prev=_t&hl=es&ie=UT… >> > >> > Cheers, >> > Rafael Luque >> > >> > >> > >> > >> >

Jan. 2, 2018

[ANN] PoLYgon file format parser/model

by Julien

Hello again, Last announcement for today. 1 year ago I created a PLY (PoLYgon file format [1] ) parser/model in Pharo [2] using PetitParser. I took some time to remove the dust it accumulated and to create a baseline so I announce it. To install it: Metacello new baseline: 'PLY'; repository: 'github://juliendelplanque/PLY/repository'; load. It has tests and an example of usage in the README. Regards, Julien Links: [1]: https://en.wikipedia.org/wiki/PLY_(file_format) <https://en.wikipedia.org/wiki/PLY_(file_format)> [2]: https://github.com/juliendelplanque/PLY <https://github.com/juliendelplanque/PLY> --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille 1 http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

Jan. 2, 2018

Re: [Pharo-users] [ANN] Orientation

by Julien

> Le 2 janv. 2018 Ã 17:26, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> a Ã©crit : > > Julien wrote >> Hello, >> >> I developed a small framework to model orientation (north, east, south, >> west). It defines some common operations that can be done on such objects >> (turning, getting the opposite orientation, moving on n steps on a >> discrete grid from a given position following certain orientation, etcâ¦). >> Also, it supporte composed orientations (e.g. north-east). >> >> This is not a lot but it is tested and I think it does its job well. So if >> you need to model orientation, consider to use it. :-) >> >> If any ideas of what I could add to this API, Iâm interested. > > A special class for holding a set of Orientations with associated value(s) > <https://en.wikipedia.org/wiki/Wind_rose> could be a useful addition. > In addition to the orientations/data itself, such a set would benefit from > specifying both > - An interpolation method to use * > - An offset from physical orientation to set-local orientations. > > From my experience, the following can be bug-prone scenarios if the above > two are not part of such a model: > - Querying a dataset for orientations not part of the original set**. > Example: Your source data consists of 6 equally spaced data points, but in > use, values for 8 equally spaced orientations are queried. > - Representing/converting different types in a good way. > Example: You model some entity where North(0@1) in design, is WSW in > physical terms (presumably, because it makes the entity align more nicely > with x/y axis), but source datasets are received in terms of Physical > directions.*** > - Redefine logical north of datasets with a preexisting logical north, while > maintaining toPhysical(preRotDataset) = toPhysical(postRotDataset) **** > Example: The physical orientation of the entity should be rotated, and you > update the logical north to compensate, but the data should remain the same > wrt. physical orientations. > > Cheers, > Henry > > * Both for converting to a different set of orientations, and when queried > for the value of a non-specified orientation > ** With an interpolation method specified, you have the choice of tradeoff > between speed (convert internal set to queried orientation, direct lookup), > and adherence to original data set (keep internal set, interpolate each > query) > *** And avoiding physical -> model local orientation translation on each > query can be nice, performance-wise > **** Obviously, this is only troublesome if one does convert physical -> > model local orientations > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > It looks like a big additionâ¦ :-) Iâll open an issue on the GitHub in case someone has some time to implement it (I may not do it myself since I do not need this feature for now). Thanks for the idea. Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille 1 http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

Jan. 2, 2018

Re: [Pharo-users] Metacello with Git

by Stephane Ducasse

Hi Alistair About pillar, we are working on a new pipeline and lot of cleaning compared to the version available on smalltalkhub. The new version Branch new pipeline seems broken (I will check it tomorrow it cannot handle internal references). I want to be able to build the old books with the new version. Now it is not working. Stef On Tue, Jan 2, 2018 at 6:08 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Sean, > > On 2 January 2018 at 18:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> EstebanLM wrote >>> if you have iceberg metacello integration enabledâ¦ Then it works on >>> baselines, etc. >> >> Strange. I did `Iceberg enableMetacelloIntegration: true.` first and still >> got the error. I can't easily test in 7 because it depends on Magritte which >> depends on Grease which doesn't seem to load yet. Maybe I can cobble >> together a simpler test case. > > This may not help, but... > > Pharo 7.0 > Build information: > Pharo-7.0+alpha.build.398.sha.52a28a857deec25612d302aba8ab09bdd6212b31 > (32 Bit) > > I have Pillar loaded, which in turn loads: > > ConfigurationOfMagritte3-topa.126 > Magritte-Model-SeanDeNigris.465 > Magritte-Morph-SeanDeNigris.95 > Magritte-Pharo3-Model-JohnCBorden.4 > ConfigurationOfGrease-StephanEggermont.348 > Grease-Core-JohanBrichau.97 > Grease-Pharo30-Core-PavelKrivanek.22 > > The image was built about 4 days ago. > > HTH, > Alistair > > > >> The Git error I mentioned in my OP was caused because `LGitRepository >> >> clone:options:to:` is trying to clone >> 'git@bitbucket.org:nDeNigris/Quote-Me.git' based on >> `gitlab://SeanDeNigris/Quote-Me:master/repository` from the baseline spec. >> Earlier in the stack, `IceProviderRepositoryType >> mcRepository` is using >> `MCBitbucketRepository` which is hardcoded. >> >> All of the above is with iceberg metacello integration enabled. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >

Jan. 2, 2018

Examples of Garage for DB2

by Andrei Stebakov

I need to be able to navigate DB2 connection. As we discussed it a few days ago on the mailing list, the suggestion was to use Garage. I downloaded Garage to my Pharo 6.1 on windows. But in Garage I only see drivers for MySql, Postgres and Sqlite3. Does it mean that for DB2 I should look somewhere else or there is a way to create a connection for DB2 using existing Garage functionality? If there is a way, could you send some example? Thanks! Andrei

Jan. 2, 2018