January 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] RSA and cryptography

by Norbert Hartl

> Am 23.01.2019 um 13:58 schrieb Holger Freyther <holger(a)freyther.de>: > > > >> On 23. Jan 2019, at 12:55, Norbert Hartl <norbert(a)hartl.name> wrote: >> > > Hi! > >> Is there anyone having crypto algorithms implemented or used a native lib to do so. We are using the Cryptography package and have problems. The code is quite old so we wonât spend time fixing it. We rather interface with a native lib. So Iâm asking upfront > > > is https://download.libsodium.org/doc/quickstart providing the functions you require? In the past I have used some of the Pharo/Squeak bindings for it. > I donât think so. We use RSA public key validation. It does not seem that libsodium supports that. A binding to libcrypto would be best :) Norbert

Jan. 23, 2019

Re: [Pharo-users] Seaside or Iliad for business applications?

by Esteban Lorenzano

> On 23 Jan 2019, at 14:22, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Wed, Jan 23, 2019 at 2:13 PM Siemen Baader <siemenbaader(a)gmail.com> wrote: >> >> Hi, >> > > Hello, > >> Iâm a very happy Iliad user but Iâm wondering if it would make sense to switch to Seaside for commercial development since it has a larger user base. I have only used Seaside briefly to try it out and found I was more happy with Iliad back then, but now Iâd like to hear your input. Especially from those of you who use it for business applications with paying customers. My questions are: >> >> - does Seaside support partial updates of the DOM, like Iliad, or do I need to refresh the whole website for every interaction? >> > > You can use JQuery with ajax to refresh part of the page. > > You can check for example this component in MDL that is working with ajax: > > https://mdl.ferlicot.fr/mdl/Widgets/DatePicker <https://mdl.ferlicot.fr/mdl/Widgets/DatePicker> There is also Willow (a framework on top of Seaside): https://github.com/ba-st/Willow <https://github.com/ba-st/Willow> Esteban > >> - Iliad has REST-like URLS that look clean and can be shared, Seaside seems not to. Is this possible with Seaside? >> > > It is possible to have rest-like URLs sharable, but when using the > application you will still have the hash of the session and callback > key in the URL (It seems not clean but it's sharable). > > Example: > > https://mdl.ferlicot.fr/mdl/Components/Badges > > To do that you can, yourself, write part of your urls depending on the > state of your Seaside application. Then, when a user get an URL, you > can customize the state of your application from the user request > containing the URL with the sub paths and the fields. > > We talked with Johan not long ago about clean URLs. It's possible to > have them by storing the fields in cookies, but it mean that you can > only have one session by browser. > >> - directly writing javascript. I suppose there is a WAComponent that can emit raw JS? >> > > It is possible to ship the application with javascript files or to > directly inject javascript in the application. > >> - what is the status of Websocket / Comet in Seaside? >> > > I am using sucessfuly Zinc's Websockets in Seaside. > > It is used in this Seaside project: https://demos.ferlicot.fr/TelescopeDemo > > I don't know for Comet. > >> Is there anything else I should consider? >> >> thanks, >> Siemen > > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Jan. 23, 2019

Re: [Pharo-users] Seaside or Iliad for business applications?

by Cyril Ferlicot

On Wed, Jan 23, 2019 at 2:13 PM Siemen Baader <siemenbaader(a)gmail.com> wrote: > > Hi, > Hello, > Iâm a very happy Iliad user but Iâm wondering if it would make sense to switch to Seaside for commercial development since it has a larger user base. I have only used Seaside briefly to try it out and found I was more happy with Iliad back then, but now Iâd like to hear your input. Especially from those of you who use it for business applications with paying customers. My questions are: > > - does Seaside support partial updates of the DOM, like Iliad, or do I need to refresh the whole website for every interaction? > You can use JQuery with ajax to refresh part of the page. You can check for example this component in MDL that is working with ajax: https://mdl.ferlicot.fr/mdl/Widgets/DatePicker > - Iliad has REST-like URLS that look clean and can be shared, Seaside seems not to. Is this possible with Seaside? > It is possible to have rest-like URLs sharable, but when using the application you will still have the hash of the session and callback key in the URL (It seems not clean but it's sharable). Example: https://mdl.ferlicot.fr/mdl/Components/Badges To do that you can, yourself, write part of your urls depending on the state of your Seaside application. Then, when a user get an URL, you can customize the state of your application from the user request containing the URL with the sub paths and the fields. We talked with Johan not long ago about clean URLs. It's possible to have them by storing the fields in cookies, but it mean that you can only have one session by browser. > - directly writing javascript. I suppose there is a WAComponent that can emit raw JS? > It is possible to ship the application with javascript files or to directly inject javascript in the application. > - what is the status of Websocket / Comet in Seaside? > I am using sucessfuly Zinc's Websockets in Seaside. It is used in this Seaside project: https://demos.ferlicot.fr/TelescopeDemo I don't know for Comet. > Is there anything else I should consider? > > thanks, > Siemen -- Cyril Ferlicot https://ferlicot.fr

Jan. 23, 2019

Seaside or Iliad for business applications?

by Siemen Baader

Hi, Iâm a very happy Iliad user but Iâm wondering if it would make sense to switch to Seaside for commercial development since it has a larger user base. I have only used Seaside briefly to try it out and found I was more happy with Iliad back then, but now Iâd like to hear your input. Especially from those of you who use it for business applications with paying customers. My questions are: - does Seaside support partial updates of the DOM, like Iliad, or do I need to refresh the whole website for every interaction? - Iliad has REST-like URLS that look clean and can be shared, Seaside seems not to. Is this possible with Seaside? - directly writing javascript. I suppose there is a WAComponent that can emit raw JS? - what is the status of Websocket / Comet in Seaside? Is there anything else I should consider? thanks, Siemen

Jan. 23, 2019

Re: [Pharo-users] RSA and cryptography

by CÃ©drick BÃ©ler

Have you tried ParrotTalk ? But I think it depends on cryptography (?). Maybe better would be NaCl bindings but havent tried and it seems quite old: - https://www.samadhiweb.com/blog/2013.11.13.crypto.html Hth, CÃ©drick > Le 23 janv. 2019 Ã 13:55, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > Is there anyone having crypto algorithms implemented or used a native lib to do so. We are using the Cryptography package and have problems. The code is quite old so we wonât spend time fixing it. We rather interface with a native lib. So Iâm asking upfront > > thanks, > > Norbert > >

Jan. 23, 2019

Re: [Pharo-users] RSA and cryptography

by Holger Freyther

> On 23. Jan 2019, at 12:55, Norbert Hartl <norbert(a)hartl.name> wrote: > Hi! > Is there anyone having crypto algorithms implemented or used a native lib to do so. We are using the Cryptography package and have problems. The code is quite old so we wonât spend time fixing it. We rather interface with a native lib. So Iâm asking upfront is https://download.libsodium.org/doc/quickstart providing the functions you require? In the past I have used some of the Pharo/Squeak bindings for it. holger

Jan. 23, 2019

RSA and cryptography

by Norbert Hartl

Is there anyone having crypto algorithms implemented or used a native lib to do so. We are using the Cryptography package and have problems. The code is quite old so we wonât spend time fixing it. We rather interface with a native lib. So Iâm asking upfront thanks, Norbert

Jan. 23, 2019

Re: [Pharo-users] [ANN] Next Pharo Sprint: Jan 25

by Marcus Denker

Jan 25 if course (changed Subject was wrong) > On 23 Jan 2019, at 10:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > (sorry, a bit late this mail): > > We will organize a Pharo sprint / Moose dojo Jan 25, starting at > > 10:00am. (Local Time Paris). > > Goals of this sprint: > > â¢ Pharo 8 > > Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: > > http://pharo.org/contribute-events <http://pharo.org/contribute-events> > > Known Local Sprint meetings > > Lille/France: > > It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

Jan. 23, 2019

[ANN] Next Pharo Sprint: Dec 21

by Marcus Denker

(sorry, a bit late this mail): We will organize a Pharo sprint / Moose dojo Jan 25, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 8 Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

Jan. 23, 2019

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo 7.0 released!

by Norbert Hartl

Congratulations to you all! It has been a hard piece of work which was postponed 9 months. But the changes to collaboration process, build process, 64 bit maturing and huge list of things was worth it. Hopefully the next version is less huge. Happy to be able to take part!!! Norbert > Am 22.01.2019 um 14:36 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Pharo 7.0 released! > =============== > > Dear World and dynamic language lovers: > > The time has come for Pharo 7.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > > <pastedGraphic.png> > > > This is our most significant release yet. Here are the key highlights of this release: > > â¢ Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. > â¢ Pharo comes with a new version of the PharoLauncher (https://pharo.org/download) THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). > â¢ Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. > â¢ Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. > â¢ Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. > â¢ IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. > â¢ The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit. > > Pharo 70âs new infrastructure and process set the stage for a new generation of version. > The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off. > > These are just the more prominent highlights, but the details are just as important. > > We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70Change…) > > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, StÃ©phane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, ClÃ©ment BÃ©ra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, BenoÃ®t Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, HernÃ¡n Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, SÃ©bastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. > (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation >

Jan. 23, 2019