- Pharo-users - lists.pharo.org

gitfiletree metadata
by Peter UhnÃ¡k July 24, 2015

July 24, 2015

Hi, it seems that I managed to completely fuck up my gitfiletree metadata... e.g.: Ancestors: DynaCASE-PeterUhnak.148, DynaCASE-PeterUhnak.93, DynaCASE-PeterUhnak.144, DynaCASE-PeterUhnak.146, DynaCASE-PeterUhnak.92, DynaCASE-PeterUhnak.142, DynaCASE-PeterUhnak.140, DynaCASE-PeterUhnak.138, DynaCASE-PeterUhnak.139, DynaCASE-bliznjan.127, DynaCASE-PeterUhnak.137, DynaCASE-PeterUhnak.125, DynaCASE-PeterUhnak.126, DynaCASE-bliznjan.123, DynaCASE-bliznjan.121, DynaCASE-bliznjan.120, DynaCASE-PeterUhnak.119, DynaCASE-PeterUhnak.117, DynaCASE-PeterUhnak.115, DynaCASE-bliznjan.113, DynaCASE-PeterUhnak.111, DynaCASE-PeterUhnak.110, DynaCASE-PeterUhnak.108, DynaCASE-PeterUhnak.102, DynaCASE-bliznjan.95, DynaCASE-bliznjan.98, DynaCASE-PeterUhnak.91 I am also starting to see a lot of ghost changes etc. Now, someone mentioned that it would be possible to delete all the .version and methodProperties.json and whatnot and generate it directly from git. So my question is, is this possible? If yes, how? If no, what would need to be done (implemented) to make it so? Or at least is it possible to completely regenerate all the metadata purely from git? (To clean up all the mess until.) Peter

5 20

Screamer for Smalltalk?
by Paul DeBruicker July 24, 2015

July 24, 2015

Hi Screamer (https://nikodemus.github.io/screamer/) is a Lisp library that: "Screamer provides a nondeterministic choice-point operator, a backtracking mechanism, and a forward propagation facility." Is there an equivalent library available in Smalltalk? Thanks Paul

2 1

deprecating classes
by Peter UhnÃ¡k July 24, 2015

July 24, 2015

Hi, is there a mechanism for deprecating whole classes? For example there's class RTResizEable that has been replaced by RTResizable (without extra "e") class. But if I don't want to break people's code I would like to tell them that they should use something else. I could mark every method with "self deprecated:" but that's a bit tedious... And doing it with a script (rewritting all methods to add the statement) is dangerous, because it can be part of UI loop, so it will blow up the image with warnings. An idea might be to instead of opening Warning dialog with debug... to create a "Deprecations Browser" (which has only one instance so if you attempt to open it again while it is still opened nothing will happen). And in the Deprecations Browser would be list of triggered deprecations... maybe something like "Announcements tab" in Announcer inspector... That way even deprecations in UI loops will just add a hundred rows to a single window instead of opening hundred windows. (And there would be also opportunity for not showing duplicates.) Thanks, Peter

2 1

Re: [Pharo-users] Semantics of #resignalAs:
by Norbert Hartl July 24, 2015

July 24, 2015

You get a debugger at the position if the halt in the code. Meaning the exception block run more than once. And it would run forever. Norbert > Am 23.07.2015 um 18:46 schrieb Joachim Tuchel <jtuchel(a)objektfabrik.de>: > > Norbert, > > Sorry if this is a stupid question: what does the debugger say? > > I mean, assuming NotFound is an Exception, I'd expect a debugger showing a NotFound Error... > > Joachim > > Am 23.07.2015 18:34 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >> >>> Am 23.07.2015 um 17:54 schrieb Joachim Tuchel <jtuchel(a)objektfabrik.de>: >>> >>> Norbert, >>> >>> I'd say you get a NotFound Exception. >> In pharo you get a debugger. Meaning this piece of code is actively an endless loop. >> >> Norbert >> >>> Joachim >>> >>> >>> >>>> Am 23.07.2015 um 16:20 schrieb Norbert Hartl <norbert(a)hartl.name>: >>>> >>>> What are the semantics of Exception>>#resignalAs: regarding active exception handler? Isn't the active exception handler excluded from being treated again? Taking the example >>>> >>>> | counter | >>>> counter := 0. >>>> [ 1/0 ] >>>> on: Error >>>> do: [ :e | >>>> counter := counter + 1. >>>> counter > 1 ifTrue: [ self halt ]. >>>> e resignalAs: NotFound new ]. >>>> >>>> should it just run and end? Or should the debugger pop up? >>>> >>>> thanks, >>>> >>>> Norbert >> >> >>

2 3

Re: [Pharo-users] Semantics of #resignalAs:
by Joachim Tuchel July 23, 2015

July 23, 2015

Norbert, Sorry if this is a stupid question: what does the debugger say? I mean, assuming NotFound is an Exception, I'd expect a debugger showing a NotFound Error... Joachim Am 23.07.2015 18:34 schrieb Norbert Hartl <norbert(a)hartl.name>: > > > > Am 23.07.2015 um 17:54 schrieb Joachim Tuchel <jtuchel(a)objektfabrik.de>: > > > > Norbert, > > > > I'd say you get a NotFound Exception. > > > In pharo you get a debugger. Meaning this piece of code is actively an endless loop. > > Norbert > > > Joachim > > > > > > > >> Am 23.07.2015 um 16:20 schrieb Norbert Hartl <norbert(a)hartl.name>: > >> > >> What are the semantics of Exception>>#resignalAs: regarding active exception handler? Isn't the active exception handler excluded from being treated again? Taking the example > >> > >> | counter | > >> counter := 0. > >> [ 1/0 ] > >>Â Â on: Error > >>Â Â do: [ :e | > >>Â Â Â Â Â Â counter := counter + 1. > >>Â Â Â Â Â Â counter > 1 ifTrue: [ self halt ]. > >>Â Â Â Â Â Â e resignalAs: NotFound new ]. > >> > >> should it just run and end? Or should the debugger pop up? > >> > >> thanks, > >> > >> Norbert > >> > >> > >> > > > > >

1 0

Semantics of #resignalAs:
by Norbert Hartl July 23, 2015

July 23, 2015

What are the semantics of Exception>>#resignalAs: regarding active exception handler? Isn't the active exception handler excluded from being treated again? Taking the example | counter | counter := 0. [ 1/0 ] on: Error do: [ :e | counter := counter + 1. counter > 1 ifTrue: [ self halt ]. e resignalAs: NotFound new ]. should it just run and end? Or should the debugger pop up? thanks, Norbert

2 2

Spec with Roassal
by Mark Rizun July 23, 2015

July 23, 2015

Hi everyone! I'm building a ui with Spec and using Roassal view inside of my window. To embed the view I use Roassal2Spec package (RoassalModel class). When I click on element of view I want to change its color. The problem is that color changes only after you move a winodw or open another window etc. Here is an example code. Just try to click on elements and than move the window. ********************************************** ui := DynamicComposableModel new. ui instantiateModels: #( button ButtonModel view RoassalModel ). ui button label: 'I am a button'. ui extent: 600 @ 480. ui view script: [ :view :canvas | |es| es := RTEllipse new size: 20; elementsOn: (1 to: 6). view addAll: es. RTCircleLayout on: es. RTEdgeBuilder new view: view; elements: es; connectToAll: [ :value | { value + 1. (value + 1) % 6 } ]. view elements when: TRMouseClick do: [ :e | e element trachelShape color: Color red. World displayWorld. World doOneCycleNow ]. canvas camera focusOnCenter. ]. layout := SpecLayout composed newColumn: [ :col | col add: #button height: ComposableModel toolbarHeight; add: #view. ]; yourself. ui openWithSpecLayout: layout. ********************************************** Thanks Mark -- View this message in context: http://forum.world.st/Spec-with-Roassal-tp4838854.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 2

Seeking help to resolve startup error on CI automated build
by Jigyasa Grover July 23, 2015

July 23, 2015

HiI am trying to build my first application in Pharo i.e. an offline text search application namely *searchQuick* which returns the list of file titles from the pre-loaded text files present in the resource folder when a string is searched for. You all are welcome to fork the code (https://github.com/jig08/sQuick_new) , try the infancy application and send in suggestions. Currently, I have put my application up on CI for automated build. I am currently getting a StartUp error on VERSION=development (40) The error is as follows: *The symbolic version '0.1-baseline' is not defined in ConfigurationOfsQuick_new for the current platform. Possible symbolic version values include: #(#bleedingEdge #development #stable)* I have checked ConfigurationOfsQuick_new and the corresponding method reads as follows:*------------------------------------------------------ development: spec <symbolicVersion: #'development'> spec for: #'common' version: '0.1-baseline'*.*------------------------------------------------------* It would be great if my mistake is pin-pointed and I could resolve it. Thanks and Regards Jigyasa

1 0

[MCGitHubRepository] Seeking better options to access resources folder from github repo
by Jigyasa Grover July 23, 2015

July 23, 2015

Hi I am trying to build my first application in Pharo i.e. an offline text search application namely *searchQuick* which returns the list of file titles from the pre-loaded text files present in the resource folder when a string is searched for. You all are welcome to fork the code (https://github.com/jig08/sQuick_new) , try the infancy application and send in suggestions. So far, to access the resources folder from my github repo, I have been using the following code snippet: *----------------------------------------------------------------------------------------------------------------* *| resourceFolder resourcePath|* *MCGitHubRepository allSubInstancesDo: * * [ :repo |* * repo projectPath = 'jig08/sQuick_new' * * ifTrue: [ resourcePath := repo directory ] * * ]. * *resourceFolder := resourcePath / 'sQuick_new/resources'.* *----------------------------------------------------------------------------------------------------------------* I wanted to know a better option that could be used to access it, without checking all the entries present for a correct match i.e. not use *"**MCGitHubRepository allSubInstancesDo:"* Help Appreciated Thanks Jigyasa

1 0

New pretty printer Blue Ink
by Franck Warlouzet July 22, 2015

July 22, 2015

Hello everyone, We just integrated Blue Ink, the new pretty printer, in the latest Pharo 5 image ! Basically what was working still is and what was not well now is. It is not yet enabled by default, we will wait for feedbacks first. If you want to try it, just type : RBProgramNode formatterClass: BIConfigurableFormatter. BIConfigurableFormatter formatAsYouReadPolicy: true Feel free to contact me via the mailing list or personnal mail if you experience a strange behavior. I tried to improve all of them but with you I am sure all the cases will be treated in an exhaustive way. Thanks for testing it, I hope it will convince you to use format as you read in Nautilus or just automatically format your code. Franck

4 4