- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GraphViz - renggli repo down

by StÃ©phane Ducasse

there are MIT because lukas did all his public code under MIT. On Nov 16, 2013, at 3:22 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Phil, > I have the packages somewhat adapted to Pharo 2.0 > I can upload it to SmalltalkHub but I don't know the license. > > HernÃ¡n > > El 15/11/2013 17:39, phil(a)highoctane.be escribiÃ³: >> Hello >> >> Is there someone having a copy of that package? I cannot load it from >> Lukas repo. >> >> Gofer new >> renggli: 'packaging'; >> package: 'GraphViz'; >> package: 'Package-Dependencies'; >> load >> >> TIA >> >> --- >> Phil >> > >

Nov. 16, 2013

Re: [Pharo-dev] A thought about backporting

by kilon alios

Yeap definetly I have my bad days too like everyone so its ok btc. :) On Sat, Nov 16, 2013 at 6:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Nov 15, 2013, at 7:05 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > btc wrote > >> My apologies for how badly that poured out of me. > > > > We all have bad days :) > > oh yes > What is strange is that I did not see the original mail.I wonder if I lose > mails. > > > > > Actually, your passion may have awakened interest in this important > topic. I > > agree with you - I've been pushing semantic versioning since Dale (IIRC) > > explained it to me. At the time, I think the barrier was adding to the > > burden of our poor integrators. But now that our CI process has become so > > automated, maybe this is the perfect time to revisit... > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/A-thought-about-backporting-tp4722224p4722533.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > >

Nov. 16, 2013

Re: [Pharo-dev] SVG in Cairo

by StÃ©phane Ducasse

Alexandre There is an SVG importer in the athens repo. Now it is not complete but you can load many file already - it is better than the cade svg importer according to the CADE guys. Some GSOC students tried to improve it but they duplicate it entirely so it is not easy to see what has been added. Now what was missing is elliptical curve and if I remember correclty igor was doing them at the image level because cairo did not support them (from memory). Stef > Hi! > > Just wondering whether there is a way to represent SVG within Athens, in Pharo. > There is a great deal of SVG description on the web. Using them in Athens would be great. > > Any hint where to start? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Nov. 16, 2013

Re: [Pharo-dev] A thought about backporting

by StÃ©phane Ducasse

On Nov 15, 2013, at 7:05 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > btc wrote >> My apologies for how badly that poured out of me. > > We all have bad days :) oh yes What is strange is that I did not see the original mail.I wonder if I lose mails. > > Actually, your passion may have awakened interest in this important topic. I > agree with you - I've been pushing semantic versioning since Dale (IIRC) > explained it to me. At the time, I think the barrier was adding to the > burden of our poor integrators. But now that our CI process has become so > automated, maybe this is the perfect time to revisit... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/A-thought-about-backporting-tp4722224p4722533.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Nov. 16, 2013

Would love to have chuck in Pharo

by StÃ©phane Ducasse

http://lexspoon.org/chuck/ I want to read the PhD. Stef

Nov. 16, 2013

Re: [Pharo-dev] Spotlight discussion

by btc＠openinworld.com

Nov. 16, 2013

Re: [Pharo-dev] Spotlight discussion

by kilon alios

I wonder if it would be better to integrate Finder and Spotlight together. Do we need two tools that do similar things ? On Sat, Nov 16, 2013 at 6:10 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com>wrote: > > El 16-11-2013, a las 12:30, Alexandre Bergel <alexandre.bergel(a)me.com> > escribiÃ³: > > > I think it would be great to always have it apparent. > > Could be. The advantage is developers know it is here. Disadvantage it > occupy space which may most of the time is not used. > > Cheers, > Jura > > > Using keys to select the item we want. Maybe right and left key to move > implementors / senders. > > > > Alexandre > > > > > > On Nov 16, 2013, at 12:28 PM, Juraj Kubelka <juraj.kubelka(a)gmail.com> > wrote: > > > >> Hi Esteban, > >> > >> StÃ©phane mentioned that you have some ideas how to improve Spotlight. I > am interested to participate on it. Can we have a discussion about it? > >> > >> Thanks, > >> Jura > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > >

Nov. 16, 2013

Re: [Pharo-dev] [issue tracker] Please review "fix review needed" issues

by kilon alios

A bit more details would help. For example I certainly dont mind testing fixes and marking them as resolved. My problem is that I am not an experienced smalltalker so I cant be sure what the expected behavior is. Is there a guideline, criteria , principles a fix should follow, or is it just a matter "if it works, its ok" ? Also I was curious what happens to a fix after its marked as resolved, how exactly the slice is integrated ? On Sat, Nov 16, 2013 at 6:32 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > So we now have an automatic system to check that a change does not break > tests and even passes Code Critique. > > Nevertheless, this does *not* mean that any change that passes is good. > (e.g. a change that just deletes all tests is fine for > the monkey). > > So we *need* people to look at proposed changes! > > Right now I feel that I decide far too many things. It would be very nice > to have the input of more people. > > Marcus >

Nov. 16, 2013

[issue tracker] Please review "fix review needed" issues

by Marcus Denker

So we now have an automatic system to check that a change does not break tests and even passes Code Critique. Nevertheless, this does *not* mean that any change that passes is good. (e.g. a change that just deletes all tests is fine for the monkey). So we *need* people to look at proposed changes! Right now I feel that I decide far too many things. It would be very nice to have the input of more people. Marcus

Nov. 16, 2013

Re: [Pharo-dev] Critics Browser - behaviour with extensions

by Marcus Denker

On 16 Nov 2013, at 17:20, btc(a)openinworld.com wrote: > > I thought for my first use of Critics Browser I would try it out on PharoLauncher project. I am not familiar with the expected behaviour some I wanted to clarify something related to extensions before opening a Case. > > Running Critics Browser restricted to packages PharoLauncher-Core (BenComan.12) & PharoLauncher-Spec (DamienCassou.11) > I get: > Coding Idiom Violation > Sends "questionable" message > for method > SettingTreeBuilder>>#systemSettings > but actually that method is not part of either of the two PharoLauncher packages selected above. > However PharoLauncher-Spec does define an extension method SettingTreeBuilder>>pharoLauncherSettings. It seems this causes the whole SettingTreeBuilder class to be processed. Whereas I would have thought that only the single #pharoLauncherSettings method of SettingTreeBuilder should be processed, not the whole class. Renaming the protocol of SettingTreeBuilder>>pharoLauncherSettings from *pharoLauncher-Spec to *xx causes the Critic to go away. > > What is the expected behaviour? > > There was a fix, hum, yesterday, to fix this. So which version are you using? Marcus

Nov. 16, 2013