September 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Migrated Artefact to GitHub

by Peter Uhnak

Hi Stef, I understand that everyone is short on time, but I consider not preserving the history problematic for two reasons * it is appropriating someone else's work as one's own -- this seems borderline illegal, or at the very least in violation of MIT license * it is sending bad signals to potential contributors that we can scrub them anytime we want as you yourself have said: > @People try to avoid to piss on good will of others. Yet this is what it feels like to some when traces of their contributions are voided. I've invested a ton of time to alleviate this process as much as possible, and I can tell you for a fact that people are _really_ happy that the authorship is preserved. Not to mention that the history itself is valuable if you know how to use it (and I very regularly look when a particular piece of code was written when debugging issues). That being said, if you have issues with migrating or think that it can be streamlined even further, please let me know and I'd be happy to help you or streamline the tool even further. Peter On Sat, Sep 29, 2018 at 10:23 AM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi guille > > I deeply appreciated that you spent your time to bring Artefact to Pharo 70 > and in general all the positive energy you put around Pharo. > I love Iceberg! and more! > > I quit these mailing-lists in the past because of these little > aggressions, the "You should do that" > I registered today again to this mailing list just to publicly talk to > you, while I could come to your office (I will do it too). > > I did a port of Artefact to Pharo 60 a while ago and started to fix > Artefact aspects I did not like and I would like to integrate my fixes > to yours. Please let me know where it is. :) > > I do not care of the history because I prefer the future. If people > care then this is their duties. Easy. If they are not happy. This is > THEIR PROBLEM. You see people often tells me that I cannot control and > that github is decentralised. It is! So enjoy but @People try to avoid > to piss on good will of others. > > Now sorry Norbert your point that Guillemo would be rude because he spent > his time to help Milton and made sure that Artefact in Pharo 70 is clearly > out of context and misplaced. You see I did the same in > github.com/olivierauverlot because I needed it. And this is like that. > Period. > You are not happy. This is ok. You do not like it. This is ok too. > > This is several times that I noticed that your are not nice with > emails so do the same than me: think about the impact on others. You > have no idea about what guille is doing and what it is paid for and > this is certainly not to fix Artefact. And you may notice that we know > what is to work on others unmaintained code because we do it all the > time, we even create documentation on systems we do not understand > because some people are too busy to write method and class comments so > imagine documentation. > > So I would like to thanks again guille and I would like to have > artefact on Pharo 70. > > Stef > >

Sept. 29, 2018

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Peter Uhnak

Hi Stef, XMLParser is maintained by monty (I've CCed him). > Now the question still remains: who is planning to migrate the XML packages. I'd be happy to do that (including preserving the history), unless monty wants to do it themselves. Peter On Sat, Sep 29, 2018 at 10:39 AM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > I contacted the maintainer (but I'm not sure in fact who it is :) ) > about the XML related packages in Pharo extras. > > XMLParser > XMLParserHTML > XMLParserStAX > XMLSupport > XMLWriter > XPath > > I did not get any answer so may be I sent a mail to the wrong email > address. > Probably. > Now the question still remains: who is planning to migrate the XML > packages. > I was planning to do it but I will not consider history because I do > not know how to do it and I do not have the time to do it (sorry). And > yes I work the weekends and this is bad and this is not even on Pharo. > > I was planning to spend some time on the baseline and making sure that > we can load everything and run the tests. > So let me know. > > Stef > >

Sept. 29, 2018

[Pharo 7.0-dev] Build #1278: 22397-Add-executable-comments-to-Date-classes

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1278 was: SUCCESS. The Pull Request #1832 was integrated: "22397-Add-executable-comments-to-Date-classes" Pull request url: https://github.com/pharo-project/pharo/pull/1832 Issue Url: https://pharo.fogbugz.com/f/cases/22397 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 29, 2018

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Sven Van Caekenberghe

I think that would be monty, email addresses (CC-ed) monty2(a)programmer.net montykamath(a)gmail.com I should note that he has been very good at maintaining the XML packages (the specs of which are super complex), and as far as I know, the code works under Pharo 7 ... What does not work for you ? Sven > On 29 Sep 2018, at 10:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > I contacted the maintainer (but I'm not sure in fact who it is :) ) > about the XML related packages in Pharo extras. > > XMLParser > XMLParserHTML > XMLParserStAX > XMLSupport > XMLWriter > XPath > > I did not get any answer so may be I sent a mail to the wrong email address. > Probably. > Now the question still remains: who is planning to migrate the XML packages. > I was planning to do it but I will not consider history because I do > not know how to do it and I do not have the time to do it (sorry). And > yes I work the weekends and this is bad and this is not even on Pharo. > > I was planning to spend some time on the baseline and making sure that > we can load everything and run the tests. > So let me know. > > Stef >

Sept. 29, 2018

[Pharo 7.0-dev] Build #1277: 22497-MIMEDocumentsaveToFile-should-not-use-FileStream

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1277 was: SUCCESS. The Pull Request #1838 was integrated: "22497-MIMEDocumentsaveToFile-should-not-use-FileStream" Pull request url: https://github.com/pharo-project/pharo/pull/1838 Issue Url: https://pharo.fogbugz.com/f/cases/22497 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 29, 2018

Migrating XML support to github/PharoContributions/

by Stephane Ducasse

Hi I contacted the maintainer (but I'm not sure in fact who it is :) ) about the XML related packages in Pharo extras. XMLParser XMLParserHTML XMLParserStAX XMLSupport XMLWriter XPath I did not get any answer so may be I sent a mail to the wrong email address. Probably. Now the question still remains: who is planning to migrate the XML packages. I was planning to do it but I will not consider history because I do not know how to do it and I do not have the time to do it (sorry). And yes I work the weekends and this is bad and this is not even on Pharo. I was planning to spend some time on the baseline and making sure that we can load everything and run the tests. So let me know. Stef

Sept. 29, 2018

[ANN] Migrated Artefact to GitHub

by Stephane Ducasse

Hi guille I deeply appreciated that you spent your time to bring Artefact to Pharo 70 and in general all the positive energy you put around Pharo. I love Iceberg! and more! I quit these mailing-lists in the past because of these little aggressions, the "You should do that" I registered today again to this mailing list just to publicly talk to you, while I could come to your office (I will do it too). I did a port of Artefact to Pharo 60 a while ago and started to fix Artefact aspects I did not like and I would like to integrate my fixes to yours. Please let me know where it is. :) I do not care of the history because I prefer the future. If people care then this is their duties. Easy. If they are not happy. This is THEIR PROBLEM. You see people often tells me that I cannot control and that github is decentralised. It is! So enjoy but @People try to avoid to piss on good will of others. Now sorry Norbert your point that Guillemo would be rude because he spent his time to help Milton and made sure that Artefact in Pharo 70 is clearly out of context and misplaced. You see I did the same in github.com/olivierauverlot because I needed it. And this is like that. Period. You are not happy. This is ok. You do not like it. This is ok too. This is several times that I noticed that your are not nice with emails so do the same than me: think about the impact on others. You have no idea about what guille is doing and what it is paid for and this is certainly not to fix Artefact. And you may notice that we know what is to work on others unmaintained code because we do it all the time, we even create documentation on systems we do not understand because some people are too busy to write method and class comments so imagine documentation. So I would like to thanks again guille and I would like to have artefact on Pharo 70. Stef

Sept. 29, 2018

Re: [Pharo-dev] Artifact and PDFExporter for Roassal

by Alexandre Bergel

Thanks Guille! Alexandre > On Sep 27, 2018, at 7:27 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Milton, > > I've taken 1 hour to migrate Artefact to Github, create a baseline, fix your issue and make a new release. > Can you test? > > https://github.com/pharo-contributions/Artefact > > Guille > > On Thu, Sep 13, 2018 at 4:40 PM milton mamani <akevalion(a)gmail.com> wrote: > > > El jue., 13 sept. 2018 a las 14:06, milton mamani (<akevalion(a)gmail.com>) escribiÃ³: > Hi! > > I am Milton Mamani I work with Roassal2, and now I am in ESUG-Cagliari, and I have tried to load Artefact with the next piece of code, in the last Pharo7 image. > > Metacello new > configuration: 'Artefact'; > smalltalkhubUser: 'RMoD' project: 'Artefact'; > version: #stable; > load. > > "To load roassal and pdf roassal exporter" > Metacello new > > > configuration: 'GraphQLBeta' > ; > > smalltalkhubUser: 'ObjectProfile' project: 'GraphQL' > ; > > version: #development > ; > load. > > Gofer new > smalltalkhubUser: 'azazael' project: 'RTPDFExporter'; > package: 'ConfigurationOfRTPDFExporter'; load. > (Smalltalk at: #ConfigurationOfRTPDFExporter) loadDevelopment > > I have a problem, when I tried to export my Roassal-Visualization to pdf file with for example this piece of code: > > view := RTBoxPlotExample new exampleBoxPlot5 build view. > stream := 'foo.pdf' asFileReference writeStream. > > [RTPDFExporter new > stream: stream; > exportView: view ] ensure: [ stream close ] > > I get a lot of kind exceptions related with the class: PDFStreamPrinter > > In the method visitPDFDataXRefEntry: > And in the logic of the new Stream classes of Pharo7. > > Could you please review Artifact in Pharo7 with this roassal2 implementation > > Cheers, > Milton > > > > -- > > Guille Polito > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13

Sept. 28, 2018

[Pharo 7.0-dev] Build #1276: 22482-AutoCompletion-preview-breaks-code-navigation

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1276 was: SUCCESS. The Pull Request #1831 was integrated: "22482-AutoCompletion-preview-breaks-code-navigation" Pull request url: https://github.com/pharo-project/pharo/pull/1831 Issue Url: https://pharo.fogbugz.com/f/cases/22482 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 28, 2018

[Pharo 7.0-dev] Build #1275: 22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1275 was: FAILURE. The Pull Request #1829 was integrated: "22480-ClassTestCase--testClassComment-depends-on-the-environment-configuration" Pull request url: https://github.com/pharo-project/pharo/pull/1829 Issue Url: https://pharo.fogbugz.com/f/cases/22480 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 28, 2018