December 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Calendrical capabilities

by publius789＠gmail.com

This is very helpful. Nice holiday weekend reading! Sure, if its not too much trouble you can send it to me. Thanks. Regards, Jim -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Stephane Ducasse Sent: Saturday, December 23, 2017 5:02 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] Calendrical capabilities Aconcagua is available via the catalog. Here is what I found in my harddisc about chronos. I can send you the zipped file with old code (probably should be ported to Pharo). On Sat, Dec 23, 2017 at 10:32 PM, <publius789(a)gmail.com> wrote: > I am new to the Pharo world and looking at capabilities for potential > applications. > > > > One of the first things I am interested in is Calendar processing > capabilities. I havenât had a chance to look at the code yet, but > specifically how much does Pharoâs Date/Calendar capabilities match > that in the java.util package for Java 9? Additionally, is there any > way to give the number of business days between two dates for a > particular local calendar? If so, whatâs the format for a local calendar? > > > > Iâm going to take a look at the code shortly, but if anyone can shed a > general light what currently exists it would be greatly appreciated. > > > > Regards, > > Jim

Dec. 23, 2017

Re: [Pharo-dev] Calendrical capabilities

by Stephane Ducasse

Aconcagua is available via the catalog. Here is what I found in my harddisc about chronos. I can send you the zipped file with old code (probably should be ported to Pharo). On Sat, Dec 23, 2017 at 10:32 PM, <publius789(a)gmail.com> wrote: > I am new to the Pharo world and looking at capabilities for potential > applications. > > > > One of the first things I am interested in is Calendar processing > capabilities. I havenât had a chance to look at the code yet, but > specifically how much does Pharoâs Date/Calendar capabilities match that in > the java.util package for Java 9? Additionally, is there any way to give > the number of business days between two dates for a particular local > calendar? If so, whatâs the format for a local calendar? > > > > Iâm going to take a look at the code shortly, but if anyone can shed a > general light what currently exists it would be greatly appreciated. > > > > Regards, > > Jim

Dec. 23, 2017

Re: [Pharo-dev] Calendrical capabilities

by Stephane Ducasse

Hi Jim you should have a look at the Aconcagua library. It has been designed by people making business in stock management. You can find two pdfs here: http://sdmeta.gforge.inria.fr/Teaching/CoursAnnecy/0506-M1-COO/ And their authors are still around in this mailing-list. Now it may means that you have to extend it to fit your need. I like what they did. There was also a library called chronos but I do not know its status it was supporting many different calendars. Finally I think the core library should deserve some love because sometimes I see it limited but when I compare with the java counterpart I saw, it is good :). Stef On Sat, Dec 23, 2017 at 10:32 PM, <publius789(a)gmail.com> wrote: > I am new to the Pharo world and looking at capabilities for potential > applications. > > > > One of the first things I am interested in is Calendar processing > capabilities. I havenât had a chance to look at the code yet, but > specifically how much does Pharoâs Date/Calendar capabilities match that in > the java.util package for Java 9? Additionally, is there any way to give > the number of business days between two dates for a particular local > calendar? If so, whatâs the format for a local calendar? > > > > Iâm going to take a look at the code shortly, but if anyone can shed a > general light what currently exists it would be greatly appreciated. > > > > Regards, > > Jim

Dec. 23, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Sean P. DeNigris

CyrilFerlicot wrote > - To be able to depend on a git project from a private server/ * > repo * > in > BaselineOf/ConfigurationOf * > and automatically clone using SSH keys if needed * (Additions to above in bold) > STABILITY Of course! I've been dreaming of most of the rest of my wishlist since 1.1, and it seems we've been creeping closer and closer: - Clean, stable low-level UI framework preserving the liveness and directness of Morphic, which also is infinitely zoomable and supports multiple (potentially simultaneously-running) worlds - 100% customizable (per instance) keybindings - Clean, customizable text editor with intuitive text model (sad to see Tx disappear, but we seem to have a replacement brewing) - Multi OS window support (not sure how close we are here) - Versionner (or its replacement) support for Baselines - hand editing is a draaaag Overall, I'm very thankful for all the progress we've made so far. Many of my wishlist items have been crossed off. Some bigger ones were: - Intuitive file library (FS) - Easy (low-barrier) contribution to other people's projects (via git/GH support) - Image management (Launcher) - Image auto-customization (startup scripts) - Single FFI library with must-have features from different existing (e.g. async callbacks) (almost there?) - Lots of integration with standard formats (NeoCSV/JSON, Pillar for MD) - Massive CI, including issue tracker integration - Cherry pick commits (Iceberg and Komitter before) - Real package model, with meta-data (RPackage and manifests) - In-editor critics with auto-transformations I can't wait to see what 2018 brings! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 23, 2017

Calendrical capabilities

by publius789＠gmail.com

I am new to the Pharo world and looking at capabilities for potential applications. One of the first things I am interested in is Calendar processing capabilities. I haven't had a chance to look at the code yet, but specifically how much does Pharo's Date/Calendar capabilities match that in the java.util package for Java 9? Additionally, is there any way to give the number of business days between two dates for a particular local calendar? If so, what's the format for a local calendar? I'm going to take a look at the code shortly, but if anyone can shed a general light what currently exists it would be greatly appreciated. Regards, Jim

Dec. 23, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by StÃ©phane Ducasse

Sounds like a good wish list! > On 23 Dec 2017, at 20:33, Robert Pergl <robert.pergl(a)fit.cvut.cz> wrote: > > Dear Santa, > > this is what I wish for Pharo in 2018: > > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > - STABILITY > > Thanks a lot! > > Your Robert > > -- > Ing. Robert Pergl, Ph.D. > Assistant Professor at Department of Software Engineering > Head of Centre for Conceptual Modelling and Implementation > ELIXIR CZ representative in the Interoperability Platform > > Czech Technical University in Prague, Faculty of Information Technology > ThÃ¡kurova 9, 160 00 Praha 6, Czech Republic > room: A-935 > http://ccmi.fit.cvut.cz <http://ccmi.fit.cvut.cz/> > http://www.fit.cvut.cz/en <http://www.fit.cvut.cz/en> > e-mail: robert.pergl(a)fit.cvut.cz <mailto:robert.pergl@fit.cvut.cz> > tel.: +420 777 042 249 > > On 23 December 2017 at 17:58, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 23, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Cyril Ferlicot D.

On 12/23/2017 05:58 PM, Esteban Lorenzano wrote: > Hi everybody, > Hi :) > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > I'll list the things I wanted the most those last months :) - To be able to load a private git project from a private server via Metacello API - To be able to depend on a git project from a private server in BaselineOf/ConfigurationOf - 64bits vm more recent that does not crash 1/4 of the time (It would help to deploy apps for some customers with older linux distributions) - 64bits Windows vm (But as far as I know, there is progress on this side already) - Continue to push Iceberg (I am not really specific because I want a lot on that part. For more details, I open issues on Iceberg repository often :) ) All those points are in the optic to make business with Pharo easier. > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > Of course :) > So, letâs those wishes come! > Also, I would like to thanks everyone because I really like my Pharo journey and it would not be possible without you! :) > cheers, > Esteban > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 23, 2017

New Year Wishlist (2018) ?

by Esteban Lorenzano

Hi everybody, This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. Features, improvements, radical changes, etcâ¦. whatever you want. Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) So, letâs those wishes come! cheers, Esteban

Dec. 23, 2017

[Pharo 7.0-dev] Build #398: SUCCESS

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

There is a new Pharo build available! The status of the build #398 was: SUCCESS. Could not extract further issue information from commit message: Looks ok and simple Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 23, 2017

Re: [Pharo-dev] TLS Version supported by Zinc/Pharo

by Nicolas Cellier

2017-12-22 21:07 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi nicolas > > May be I'm naive and dull but indeed using branches is the way to go. > We used that for Pillar. > I can integrate fixes for the current stable in master and we are > coding in a dedicated branch. > > I imagine that you know it, else you would not wish to use it. > Hi steph, If I had the dictatorship, I would not only wish ;) Git supports branches and usually good processes are > - dev in local branches until it is ready and stable to merge in master > - master is always the stable version > and different builds can trigger and test different branches. > > So do I guess correctly that the VM code is not managed that way? > This is surprising because all complex projects are managed that way with > git. > In fact good branching is one of the best features of git. > > > The problem is partly cultural, but not exclusively. Main specificity to take into account is that most part of development does not happen in github. It happens in VMMaker and VM simulation, ask Clement or Eliot. That explains why the github part can be seen as secondary... and why adoption of better practices is slow. And don't forget that code generation is not yet reproducible. Type inference vary from one invocation to another (due to unordered methodDictionary probably). Until we fix that, we cannot really profit by full github features and increased automation. Branches should be as short as possible, or they get impracticle. We cannot reasonnably use separate branches for sista nor lowcode for example. I mean we could, but would have to merge frequently in trunk (cog). Look how difficult it is to merge classic VMMaker and oscog branches already. Branches are easy to use for modification of platform specific source code, but they are not so much for VMMaker generated code. Concurrent modification of generated code often create many conflicts that cannot reasonnably nor safely be merged. That means that github PR does not really work for VMMaker work (unless non-concurrent). Nevertheless we should use branches and PR for small changes... Before giving lessons, I have to discipline myself. I still commit in trunk too often just because I can. You know, do what I say, not what I do ;) Stef > > > On Fri, Dec 22, 2017 at 5:35 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi Norbert, > > having something integrated into the VM is not necessarily hard. > > The pull request of Holger has been accepted fast enough. > > So your point is maybe more about delivery of the binary artefacts. > > > > The pharo builds have been broken for some time but are now fixed, > thanks to > > Fabio/Christophe/Clement/Esteban! > > I wish we can preserve the green status longer this time. > > > > The question is then about the release cycle which is well too > loooonnng... > > Continuous integration require GREEN builds, I wish we start using > feature > > branchs and reject half-ready PR > > Then stability of head revision (cog) also matters. > > Automated tests don't catch all problems. > > Changing the garbage collector for example may trigger rare bugs... > > > > Maybe some essential (and limited) patch could be back-ported to well > known > > stable point. > > But this can't happen with current ressources... > > IOW help is welcome! > > > > Nicolas > > > > > > 2017-12-22 16:31 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> > >> the week I return from holidays Iâm planing to get all that done (vm > >> stuff). > >> > >> Esteban > >> > >> > On 22 Dec 2017, at 16:17, Norbert Hartl <norbert(a)hartl.name> wrote: > >> > > >> > I had that problem when openssl 1.1x library was present and SqueakSSL > >> > uses 1.0.2 library. The patch is done by Holger and ready to be > integrated. > >> > But as always it is close to impossible to having something > integrated in > >> > the vm. > >> > > >> > Norbert > >> > > >> > > >> >> Am 22.12.2017 um 16:12 schrieb Torsten Bergmann <astares(a)gmx.de>: > >> >> > >> >> Hi, > >> >> > >> >> I used ZnClient to call an HTTPS URL and while it worked well in the > >> >> past > >> >> I now receive an "SSL Exception: connect failed [code:-5]". > >> >> > >> >> I guess the reason is an update of the URLs site to a server with > newer > >> >> TLS > >> >> protocol (TLS 1.2 instead of TLS 1.0). > >> >> > >> >> Do we support that already in Pharo? > >> >> > >> >> Thx > >> >> T. > >> > > >> > >> > > > >

Dec. 22, 2017