May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New Versionner Tool and Authentication

by Sean P. DeNigris

EstebanLM wrote > should be fixed if you install bleedingEdgeâ¦ I installed #bleedingEdge but it is still happening :/ ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032p4824… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 4, 2015

WhatsUp from: 2015-05-04 until: 2015-05-17

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-05-17 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

May 4, 2015

TxSpan>>#isAtEnd

by Sean P. DeNigris

Right now, there is: TxBasicSpan>>#isAtEnd ^ false and TxEndSpan>>#isAtEnd ^ true However, there are cases were a list of spans has no end marker e.g. the argument to #insert: I'm thinking of changing to: TxBasicSpan>>#isAtEnd ^ self next == self. This will allow changing e.g. the following slightly opaque loop condition: [ span next == span ] whileFalse: [ span := span next ]. to: [ span isAtEnd ] whileFalse: [ span := span next ]. All tests pass with this change, but I'm still very much beginning learning Tx, so I wanted to run it by everyone to see if I'm missing something... ----- Cheers, Sean -- View this message in context: http://forum.world.st/TxSpan-isAtEnd-tp4824134.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sean P. DeNigris

Sean P. DeNigris wrote > We have two kinds of external projects in Pharo: After reviewing your fix, your case is especially complicated - you have edited one of each type of project! Spec, which has been forked, and Versionner, which is externally maintained. You may have to open another issue for the Spec changes. In fact, I think we should have a discussion because you extended the extremely ugly SystemWindow logic (not blaming you, you didn't create it!) into Spec: (self model respondsTo: #aboutTitle) ifTrue: [^self model aboutTitle]. ^(self model respondsTo: #toolName) ifTrue: [self model toolName] ifFalse: [self model class name]. The Versionner about text proposal is more straightforward. I copied your package into the PharoExtras/Versionner repo (I actually made some edits to the text as I think that Metacello and Monticello should be described elsewhere in their own context). The next step would be to create a configuration to pick up these changes, but I guess the Spec question would have to be resolved first... Please don't be discouraged! By chance, you stepped into the absolute the worst-case scenario. Thankfully, many issues are much easier to integrate :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Improving-the-About-Text-of-Versionner-tp4823759p4824… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sean P. DeNigris

Sergio Fedi wrote >> There is ConfigurationOfVersionner in the image... > What does it mean? Is there something wrong I did? It was in response to Ben's question: "is Versioneer Slice based or Configuration based?". We have two kinds of external projects in Pharo: - Traditional model: projects that, while technically external, have been adopted (cough... forked) by Pharo core so that we were free to evolve. This seemed to be the only way before we had really good tools because trying to keep everything in sync required massive effort. These can be considered core packages and are committed via the slice process. The projects are sometimes synced with the main project at irregular intervals. - Shiny new model: we have been starting to experiment with keeping projects (e.g. Rubric, TxText) in their own repos and loading improvements via Metacello configurations. While historically this was impractical, now fogbugz issues can specify configurations and their versions to be picked up by CI, and Esteban has just made a tool [1] to create those versions easily (i.e. almost automatically). Writing this, it seems a bit complicated, but actually it seems we are moving toward a very streamlined place. It's just that this moment is the transition. [1] http://forum.world.st/ANN-Screencast-on-Versionner-Part-2-td4823221.html ----- Cheers, Sean -- View this message in context: http://forum.world.st/Improving-the-About-Text-of-Versionner-tp4823759p4824… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sergio Fedi

> > There is ConfigurationOfVersionner in the image... > Sorry, I don't understand. What does it mean? Is there something wrong I did?

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sean P. DeNigris

There is ConfigurationOfVersionner in the image... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Improving-the-About-Text-of-Versionner-tp4823759p4824… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 4, 2015

Re: [Pharo-dev] Where to start contributing

by Sergio Fedi

I saw that discussion, but I didn't know how I could (if I could) contribute to that problem. â

May 4, 2015

Re: [Pharo-dev] Where to start contributing

by Cyril Ferlicot

Marcus opened a discussion last time and the result is that he'll maybe close all the bugs and ask to people to reopen only the one we really want. http://forum.world.st/Issue-tracker-what-about-old-issues-td4822552.html On 4 May 2015 at 02:27, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > @Cyril > I tried to do what you suggested, but the amount of cases to resolve is > huge, I'm quite lost on where to begin, and most of them I don't understand > how to solve them > > @Ben > How do I do that reviewing you suggest? > Which ones do you suggest I should begin reviewing? > If anyone else have more comments or suggestions on where and how I can > contribute, please chime in. > -- Cheers Cyril Ferlicot

May 4, 2015

Re: [Pharo-dev] Beyond resolving a case

by Sergio Fedi

I understand, thanks for the answer.â

May 4, 2015