smallwiki

smallwiki@list.inf.unibe.ch

2312 discussions

by FDominicus

Gehe ich auf Mateialien bekomme ich: QCPrice(Object)>>error: QCPrice(UnitValue)>>inconsistentUnits:selector: QCPrice(UnitValue)>>lessFromUnit: QCPrice(UnitValue)>>< QCPrice(Magnitude)>>> QCBuyPriceCalculation>>DoItIn: OpalCompiler>>evaluate SmalltalkEditor>>evaluateSelectionAndDo: SmalltalkEditor>>inspectIt SmalltalkEditor>>inspectIt: SmalltalkEditor(TextEditor)>>performCmdActionsWith:shifted:return: SmalltalkEditor(TextEditor)>>dispatchCommandOn:return: SmalltalkEditor(TextEditor)>>dispatchOn: [ self dispatchOn: aKeyboardEvent ] in SmalltalkEditor(TextEditor)>>keystroke: in Block: [ self dispatchOn: aKeyboardEvent ] SmalltalkEditor(TextEditor)>>handleKeystrokeAction: SmalltalkEditor(TextEditor)>>handleEditionAction:fromKeyboardEvent: SmalltalkEditor(TextEditor)>>keystroke: [ editor keystroke: evt ] in TextMorphForEditView(TextMorph)>>basicKeyStroke: in Block: [ editor keystroke: evt ] TextMorphForEditView(TextMorph)>>handleInteraction: TextMorphForEditView>>handleInteraction: TextMorphForEditView(TextMorph)>>basicKeyStroke: [ self basicKeyStroke: evt ] in TextMorphForEditView(TextMorph)>>keyStroke: in Block: [ self basicKeyStroke: evt ] NECController class>>codeCompletionAround:textMorph:keyStroke: PharoCommonTools(ToolRegistry)>>codeCompletionAround:textMorph:keyStroke: TextMorphForEditView(TextMorph)>>keyStroke: TextMorphForEditView>>keyStroke: TextMorphForEditView(TextMorph)>>handleKeystroke: KeyboardEvent>>sentTo: TextMorphForEditView(Morph)>>handleEvent: TextMorphForEditView(Morph)>>handleFocusEvent: Ok also darf ich jetzt woh ein neues Image anlegen. Ich habe keins mehr was funktioniert... Super -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus -- View this message in context: http://forum.world.st/Und-so-geht-es-weiter-tp4822724.html Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.

9 years, 7 months

Vielleicht ein Fehler

by FDominicus

Bin mir nicht sicher. Ich habe mir ein QCMagritte image geholt und WebContfakt darein geladen. Die Daten habe ich mit Fuel gedumpt und dann eingelesen. Dann fehlen noch die übersetzungen und die ergeben: GRPharoUtf8Codec>>invalidUtf8 Grüsse aus Bruchsal Friedrich -- Q-Software Solutions GmbH; Sitz: Bruchsal; Registergericht: Mannheim Registriernummer: HRB232138; Geschaeftsfuehrer: Friedrich Dominicus -- View this message in context: http://forum.world.st/Vielleicht-ein-Fehler-tp4822576.html Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.

9 years, 7 months

Replacing TimeStamp with DateAndTIme in Magritte3 for Pharo 4 & 5

by John Borden

With Pharo 4, DateAndTIme is being deprecated, and planned to be removed from Pharo 5. The attached has updates for GRPharoPlatform>>magritteTimeStampClass and magritteTimeStampIfAbsent:, does anyone have write access to publish this to the Magritte3 project? Thanks, John

9 years, 7 months

Aconcagua-Magritte

by Sean P. DeNigris

I pushed some Aconcagua extensions to http://smalltalkhub.com/mc/SeanDeNigris/AconcaguaAddOns/main/ The package relevant to Magritte specifically is . This gives you MAMeasureDescription, which represents an Aconcagua Measure. It mostly acts like a number field mapped to its amount. You just have to tell it which unit to use to convert the amount number into a Measure. Example usage: MAMeasureDescription new accessor: #replacementPrice; label: 'Replacement Price'; unit: AmDollar new; yourself Then, you can type 100 in a Magritte form and "100 dollars" will be saved to the model. Enjoy! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Aconcagua-Magritte-tp4820928.html Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.

9 years, 8 months

What's new on Pillar ?

by Cyril Ferlicot

Hi everyone ! I'm currently working on Pillar ! It's been a little while now so I wanted to share what's new. --> First of all, with Stephane we created a new project, Cocoon, based on the configuration system of Pillar. And now Pillar uses Cocoon for his configurations. http://smalltalkhub.com/#!/~PharoExtras/Cocoon --> Pillar unit tests weren't working on Windows before --> With Damien we also added two new abstractions: --> The transformers: They take the Pillar tree and modify it. For exemple we have a transformer which evaluates the scripts with a "eval=true" parameter. --> The annotations: They let the writer specify many different things in their document using just 1 syntax (see below for an example) --> We now have our first annotation tag: the inclusion tag ! If you add this: ${inputFile:test.pillar}$ or ${inputFile:folder/test.pillar}$ into your Pillar file, that will include the content of test.pillar. I recommend for now to use it at the root of the pillar file and not inside a paragraph. That still needs some improvement. --> We now have a transformer which adds an anchor after each title. The anchor will have the text of the title. This still needs some improvement, it's really simple for now. For exemple we need to consider the case where we have 2 titles with the same text (like 'introduction'). --> Now you can add 'lineNumber=true' as parameter for a Script. This will add a numerotation at your script, usefull if we want to explain a long code. --> I did some refactorisation on the parameters used by pillar to clean the code. --> I did some refactorisation of the template system, the old one was really ugly and changed the baseDirectory. Now template are managed by a stream and not a file. --> I improved a little the configuration --> Now if you want to change the baseDirectory you can pass a FileReference, a relative path or an absolute path. --> Now we look for the inputFiles from the baseDirectory and not the working directory like before. You can also pass a FileReference, a relative path or an absolute path. --> I added some tests to Pillar. --> I added some doc to EnterprisePharo https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… --> To help the users I improved the error reports. Before we had really few errors specific to Pillar. For this one you can help me ! If you found a weird error or something really not easy to deal with, send me your problem ! -- Cheers Cyril Ferlicot

9 years, 8 months

Magritte-Model changes .455, .456

by stephan

I'm not sure the replacement of visitNumberDescription: aDescription | contents | contents := self contents. contents isEmpty ifTrue: [ MAReadError signal ]. (contents occurrencesOf: $-) > 1 ifTrue: [ MAReadError signal ]. (contents indexOf: $-) > 1 ifTrue: [ MAReadError signal ]. (contents occurrencesOf: $.) > 1 ifTrue: [ MAReadError signal ]. (contents allSatisfy: [ :each | '+-0123456789.eE' includes: each ]) ifFalse: [ MAReadError signal ]. super visitNumberDescription: aDescription by visitNumberDescription: aDescription | isContentsValid | isContentsValid := NumberParser isNumber: self contents. isContentsValid ifFalse: [ MAReadError signal ]. super visitNumberDescription: aDescription works cross-platform. There are two 455s, and 456 misses changes from both. Merged in 457 Stephan

9 years, 8 months

Re: [Pharo-users] [Esug-list] [ANN] Pharo 4.0 is released!

by Mariano Martinez Peck

Super good news! thank you all! On Thu, Apr 16, 2015 at 1:08 PM, Richard Wettel <wettel(a)gmail.com> wrote: > Great! And thank you all! > Ricky > > — > Sent from Mailbox <https://www.dropbox.com/mailbox> > > > On Thu, Apr 16, 2015 at 5:24 PM, Serge Stinckwich < > serge.stinckwich(a)gmail.com> wrote: > >> Thank you all ! >> >> On Thu, Apr 16, 2015 at 11:29 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> Please spread widely. >>> Sorry for multiple posts. >>> >>> (this post can be see here: http://pharo.org/news/pharo-4.0-released) >>> >>> Dear World, >>> >>> Pharo 4.0 (http://www.pharo.org) is here. >>> >>> Pharo is a pure object-oriented programming language and a powerful >>> environment, focused on simplicity and immediate feedback. >>> >>> Many things have changed in Pharo. Here are some highlights: >>> - Inspector/Playground/Spotter are new moldable development tools for >>> inspecting, coding and searching objects. >>> - Slots model instance variables as first class entities and enable >>> meta-programming on this level. >>> - ShoreLine reporter introduces a way to report system errors and >>> collect statistics, that we will use for future improvements >>> - Dark theme. >>> >>> These are just the more prominent highlights, but the details are just >>> as important. We have closed 1697 issues in Pharo 4. Take a moment to go >>> through a more detailed recount of the progress: >>> >>> >>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md >>> >>> Pharo is improving on many fronts, but one of the most prominent changes >>> is the addition of moldable tools for inspection and search. These tools >>> provide extension mechanisms that allow every object to define ways in >>> which it can be understood effectively. To provide an idea of the impact of >>> the already existing extensions, the map below shows the Pharo classes >>> grouped in packages, highlighting in red those parts of the system that >>> have at least one such custom view coming with the main distribution. The >>> spread of these extensions shows that moldability is powerful mechanism >>> that can be used in many contexts. >>> >>> >>> Remember that Pharo is your platform. We thank all the contributors of >>> this release: >>> >>> Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe >>> Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, >>> Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, >>> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei >>> Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, >>> Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane >>> Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, >>> Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, >>> Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, >>> Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max >>> Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila >>> Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot >>> Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, >>> Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, >>> Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian >>> Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, >>> Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin >>> >>> And all those who contributed indirectly, by reporting bugs, >>> participating in discussion threads, providing feedback... >>> >>> Pharo 4.0 is another big step. And, the best is yet to come. >>> >>> Enjoy! >>> The Pharo Team >>> >>> >>> _______________________________________________ >>> Esug-list mailing list >>> Esug-list(a)lists.esug.org >>> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >>> >>> >> >> >> -- >> Serge Stinckwich >> UCBN & UMI UMMISCO 209 (IRD/UPMC) >> Every DSL ends up being Smalltalk >> http://www.doesnotunderstand.org/ >> > > -- Mariano http://marianopeck.wordpress.com

9 years, 8 months

[ANN] Pharo 4.0 is released!

by Esteban Lorenzano

Please spread widely. Sorry for multiple posts. (this post can be see here: http://pharo.org/news/pharo-4.0-released <http://pharo.org/news/pharo-4.0-released>) Dear World, Pharo 4.0 (http://www.pharo.org) is here. Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Many things have changed in Pharo. Here are some highlights: - Inspector/Playground/Spotter are new moldable development tools for inspecting, coding and searching objects. - Slots model instance variables as first class entities and enable meta-programming on this level. - ShoreLine reporter introduces a way to report system errors and collect statistics, that we will use for future improvements - Dark theme. These are just the more prominent highlights, but the details are just as important. We have closed 1697 issues in Pharo 4. Take a moment to go through a more detailed recount of the progress: https://github.com/pharo-project/ChangeLogs/blob/master/Pharo40ChangeLogs.md Pharo is improving on many fronts, but one of the most prominent changes is the addition of moldable tools for inspection and search. These tools provide extension mechanisms that allow every object to define ways in which it can be understood effectively. To provide an idea of the impact of the already existing extensions, the map below shows the Pharo classes grouped in packages, highlighting in red those parts of the system that have at least one such custom view coming with the main distribution. The spread of these extensions shows that moldability is powerful mechanism that can be used in many contexts. Remember that Pharo is your platform. We thank all the contributors of this release: Clara Allende, Jean-Baptiste Arnaud, Jean-Christophe Bach, Philippe Back, Clement Bera, Alexandre Bergel, Torsten Bergmann, Vincent Blondeau, Noury Bouraqadi, Santiago Bragagnolo, Johan Brichau, Sven Van Caekenberghe, Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Andrei Chis, Ben Coman, Bernardo Contreras, Tommaso Dal Sasso, Jan Van De Sandt, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Stephane Ducasse, Stephan Eggermont, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Jerome Garcia, Tudor Girba, Thierry Goubier, Jigyasa Grover, Kris Gybels, Norbert Hartl, Dale Henrichs, Pablo Herrero, Nicolai Hess, Pavel Krivanek, Juraj Kubelka, Jan Kurs, Laurent Laffont, Jannik Laval, Kevin Lanvin, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Tim Mackinnon, Attila Magyar, Esteban Maringolo, Stefan Marr, Max Mattone, Martin Mc Clure, Eliot Miranda, Alain Plantec, Guillermo Polito, Damien Pollet, Stefan Reichhart, Mark Rizun, Udo Schneider, Ignacio Sniechowski, Henrik Sperre Johansen, Igor Stasenko, Aliaksei Syrel, Ciprian Teodorov, Camille Teruel, Sebastian Tleye, Yuriy Tymchuk, Peter Uhnak, Andres Valloud, Sven Van Caekenberghe, Thomas Vincent, Jan Vrany, Martin Walk, Richard Wettel, Dmitri Zagidulin And all those who contributed indirectly, by reporting bugs, participating in discussion threads, providing feedback... Pharo 4.0 is another big step. And, the best is yet to come. Enjoy! The Pharo Team

9 years, 8 months

Pillar package dependency

by Johan Brichau

Hi all, Can someone give me access to the Pillar repository or fix the issue below? I was trying to play around with Pier3 (which uses Pillar) but immediately hit an issue. When loading: Metacello new configuration: 'Pier3'; version: #'release3.1'; load. And then opening localhost:8080 pier gives you a DNU on MacOSXPlatform>>pillarLineEnding The issue is that the code of Pillar-Model (which is loaded by Pier) is dependent on Pillar-ExporterCore (which contains the method above). I think two things need to be done: - move the #pillarLineEnding method to the Pillar-Model - move the #pillarLineEnding method from Platform class to GRPlatform class to ease porting to other Smalltalks thanks Johan

9 years, 8 months

Issue Tracker

by Sean P. DeNigris

Now that Google Code is shutting down, what shall be done about Magritte's issue tracker? The standard move seems to be to export to GitHub, a painless process I just undertook for a personal project. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-Tracker-tp4814743.html Sent from the Magritte, Pier and Related Tools mailing list archive at Nabble.com.

9 years, 8 months

← Newer
1
...
5
6
7
8
9
10
11
...
232
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki