September 2015 - Pharo-users

Re: [Pharo-users] Adding a #development version of a Git project in the catalog

by Dale Henrichs

On 09/21/2015 10:46 AM, Dale Henrichs wrote: > > > On 09/21/2015 06:31 AM, Damien Cassou wrote: >> Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: >> >>> Can you simply define symbolic version as a normal one? >> >> when I tried I got an error message. Metacello was trying to parse >> 'development' as a semantic version number > You can implement #versionNumberClass in your configuration or > baseline to switch version number parser to MetacelloVersionNumber > which is less picky:) > > versionNumberClass > ^ MetacelloVersionNumber So using MetacelloVersionNumber does look like you can define the following version: versionDev: spec <version: 'dev'> spec for: #'common' do: [ spec baseline: 'Jenkins' with: [ spec repository: 'github://DamienCassou/pharo-jenkins:master/src' ]; import: 'Jenkins' ] and then use a standard symbolic version definition: development: spec <symbolicVersion: #'development'> spec for: #'common' version: 'dev' Dale

Sept. 21, 2015

Re: [Pharo-users] Adding a #development version of a Git project in the catalog

by Dale Henrichs

On 09/21/2015 06:31 AM, Damien Cassou wrote: > Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: > >> Can you simply define symbolic version as a normal one? > > when I tried I got an error message. Metacello was trying to parse > 'development' as a semantic version number You can implement #versionNumberClass in your configuration or baseline to switch version number parser to MetacelloVersionNumber which is less picky:) versionNumberClass ^ MetacelloVersionNumber

Sept. 21, 2015

Re: [Pharo-users] Mathex first release is out.

by Ben Coman

I don't have a use right now, but this is really cool. Thanks for the announcement. cheers -ben On Mon, Sep 21, 2015 at 1:44 AM, Julien Delplanque <julien(a)tamere.eu> wrote: > Hi all, > > I'm sending this mail for those who are eventually interested in the Mathex > package > I announced in a precedent mail > (http://forum.world.st/Mathex-Generating-latex-math-from-Pharo-td4848409.html) > > Mathex has now its first release: 0.1 (the latest release will always be in > the same state > as master branch, new features will be on bleed till there is no new > release. So basically, > releases are not really usefull except for announcing them :) ). > > Here is a list of changes/additional features since the last mail: > ===================================== > > - Greek letters are defined as globals: Alpha, Beta, ... > > - Additional packages for more latex commands > (https://github.com/juliendelplanque/mathex#load-additional-package) > > - GT-Inspector extensions to: > * explore the tree formed by Mathex objects > * see the LaTeX code generated by a Mathex object > * Have a preview of the compiled LaTeX code using pdflatex > > - The possibility to define custom commands made of Mathex objects > composition using > blocks (see: https://github.com/juliendelplanque/mathex/wiki#advanced-uses) > > - Documentation available on the wiki (more to come) > > - A code rewriter and its GUI (not documented yet and still experimental) > that allows you > to write "Mathex Smalltalk" ie Smalltalk code where #asMathex message is > sent to all literals automatically. > This make the code lighter because in spite of '(1 asMathex + 2 asMathex) > equal: 3 asMathex.', you can write: > '(1 + 2) equal: 3' and get Mathex objects that are able to generate LaTeX. > > - The possibility to create Mathex objects using symbols. For example: > '#vdash asMathex' returns a MVdash object. > > - Added messages to do things like: > '$a asMathex ==> $b asMathex' and get the latex code 'a \Rightarrow b'. > > - Some refactoring > > And probably things I forgot > > Some links: > ======= > > Mathex github repository: https://github.com/juliendelplanque/mathex > Mathex 0.1 release: > https://github.com/juliendelplanque/mathex/releases/tag/0.1 (you can just > follow instructions in this mail or in the README to get it). > Mathex wiki: https://github.com/juliendelplanque/mathex/wiki. > > Install Mathex package: > ============== > > Metacello new > baseline: 'Mathex'; > repository: 'github://juliendelplanque/mathex/repository'; > load. > > Install Mathex extensions (after Mathex package installation): > ==================================== > > MLoader loadArrows. "Load Mathex-Arrows" > MLoader loadBinaryOperators. "Load Mathex-BinaryOperators" > MLoader loadLoglike. "Load Mathex-Loglike" > MLoader loadMisc. "Load Mathex-Misc" > MLoader loadRelations. "Load Mathex-Relations" > > Install GT-Inspector extensions (after Mathex package installation): > ======================================== > > MLoader loadGTInspectorExtensions. > > Add a preview of the LaTeX code compiled in GT-Inspector (only for linux > users from now, sorry for others) > ================================== > See: > https://github.com/juliendelplanque/mathex#add-a-preview-of-the-latex-code-… > > Comments, help and critics are welcome. > > Regards, > > Julien

Sept. 21, 2015

Displaying custom Magritte view on FAMIX model

by Peter UhnÃ¡k

Hi, I would like to build custom magritte view for a FAMIX model, however it seems that Fame/Metanool are somehow interfering with it.. Imagine a simple model (a class with an attribute): ~~~~~~~~~~~~~~~~~~~~~~~~~~~ cls := FAMIXClass new name: 'Something'. (attr := FAMIXAttribute new) name: 'myAttribute'; declaredType: (FAMIXClass new name: 'OtherThing'). cls addAttribute: attr. ~~~~~~~~~~~~~~~~~~~~~~~~~~~ now I can open the magritte description ~~~~~~~~~~~~~~~~~~~~~~~~~~~ attr mooseDescription asMagritteDescription asMagritteMorph openInWindow. ~~~~~~~~~~~~~~~~~~~~~~~~~~~ However this is a meta description, which I don't want... So second option was to build it manually; I extract descriptions that I am interested in.... ~~~~~~~~~~~~~~~~~~~~~~~~~~~ container := MAContainer new addAll: ({ attr mooseDescription at: 'name'. attr mooseDescription at: 'declaredType'. } collect: #asMagritteDescription). (container asMorphOn: attr) openInWindow. ~~~~~~~~~~~~~~~~~~~~~~~~~~~ However the problem with this is, that the declaredType is presented as TextField, which is not very useful. So I'm kind of lost... basically what I want to do is to have a MAContainer that contains both the Attribute's name and #declaredType's name. Is this possible? Thanks, Peter

Sept. 21, 2015

Re: [Pharo-users] DesktopManager in Pharo 5 - Video

by Alexandre Bergel

+1 Alexandre > On Sep 21, 2015, at 11:15 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > The Spotter integration is really cool. > > Cheers, > Doru > > On Mon, Sep 21, 2015 at 3:30 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > https://www.youtube.com/watch?t=118&v=zpLY7uQnPsg > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 21, 2015

Re: [Pharo-users] DesktopManager in Pharo 5 - Video

by Tudor Girba

The Spotter integration is really cool. Cheers, Doru On Mon, Sep 21, 2015 at 3:30 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > https://www.youtube.com/watch?t=118&v=zpLY7uQnPsg > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 21, 2015

Re: [Pharo-users] DesktopManager in Pharo 5 - Video

by Damien Cassou

Torsten Bergmann <astares(a)gmx.de> writes: > https://www.youtube.com/watch?t=118&v=zpLY7uQnPsg great!! Good job. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 21, 2015

[ANN] Jenkins: query Jenkins servers from Pharo

by Damien Cassou

Hi, just to let you know I extracted some code from the Launcher to query Jenkins servers from Pharo. With this project, you can write code like: | pillar zipArtifact | pillar := JenkinsServer pharoContributions jobs detect: [ :job | job name = 'Pillar' ]. zipArtifact := pillar lastSuccessfulBuild runs anyOne artifacts detect: [ :artifact | artifact name = 'Pillar.zip' ] ZnClient new url: zipArtifact url; downloadTo: 'Pillar.zip' The (very simple) code is on github: https://github.com/DamienCassou/pharo-jenkins -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 21, 2015

Re: [Pharo-users] Mathex first release is out.

by Damien Cassou

Julien Delplanque <julien(a)tamere.eu> writes: > - Greek letters are defined as globals: Alpha, Beta, ... instead of "polluting" the global namespace, you might want to let your users write: #alpha asMathex > * Have a preview of the compiled LaTeX code using pdflatex you launch pdflatex from Pharo? Does it work on Windows? How do you know when pdflatex is finished compiling? How do you get the exit status of pdflatex? Pillar wanted the same. But we only managed to let Pillar generate a bash script that must be executed to launch pdflatex. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 21, 2015

Re: [Pharo-users] Adding a #development version of a Git project in the catalog

by Damien Cassou

Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: > Can you simply define symbolic version as a normal one? when I tried I got an error message. Metacello was trying to parse 'development' as a semantic version number. > I think that you need a baseline with a code of your symbolic version, > then you reference this baseline with the #development version and in > v1_0_0 you override repository to ââ¦pharo-jenkins:v1.0.0/srcâ. I think > that for me that was the main reason why I was doing pre-release. > Because you cannot define any changes in symbolic versions, my > baseline is a separate class, and âConfigurationOfâ requires semantic > versioning. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 21, 2015