March 2022 - Pharo-users - lists.pharo.org

Re: How to unsubscribe?

by Marcus Denker

> On 1 Mar 2022, at 12:50, contactme(a)kathe.in wrote: > > Hello, > > I tried issuing the "unsubscribe" and "help" commands to the mailing list management system but didn't get any response. > > May I know how to go about "unsubscribing" from this mailing list? > Hello, you can send a mail to pharo-users-leave(a)lists.pharo.org this should remove you. If this does not work, I can remove you using the admin tools Marcus

March 2, 2022

Re: ByteString asDate

by Robert Briggs

Thanks Bernardo That construct works as required, however Iâm not sure what the semantic difference is to my original.Â I seems counterintuitive.Â Could you expand on what is going on for my benefit (if you have time). Again thanks. Also do you have a view on my description of the asDate result, and whether it should self-validate the receiver and raise an exception? Regards R From: Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Tuesday, 1 March 2022 at 15:05 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: ByteString asDate try to send the #on:do: message to a block. try this ^ [ (Date readFrom: self pattern: âdd/mm/yyyyâ). true ] on: DateError do: [ false]. On Tue, Mar 1, 2022 at 11:52 AM Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: I may be being stupid but the current Date Class does not appear to protect itself against a ByteString that is not in valid date format, e.g. by raising an Error. e.g. the code âABCâ asDate opens the Debugger on #isLetter was sent to nil because it appears to expect more letters after $C but the peek returns nil instead. This seems to me to require a more defensive programming approach. I would like to validate a user input as a valid date in a number of different formats before converting it to a Date and storing it in my model. Iâve tried using the Date parser, e.g. Date readFrom: '04/02/2013' readStream pattern: 'dd/mm/yyyy'. This is fine for simply parsing a valid string but rates a DateError if it doesnât match the . So entering â04/13/2013â cleverly raises âDateError: There is no 13th monthâ. My thought was I could use this to return a simple true/false result in a ByteString extension in my application for example as follows: ByteString >> isValdiDate (Date readFrom: self pattern: âdd/mm/yyyyâ) on: DateError do: [^ false]. ^ true However this doesnât intercept the DateError which is simply reported in the Debugger as before. This may be my lack of uncderstaning of the Exception handling in Pharo. Any and all thoughts welcome. R -- Bernardo E.C. Sent from a cheap desktop computer in South America.

March 2, 2022

Re: [Esug-list] Re: [PDFtalk] Porting to non-namespace Smalltalks

by James Foster

Hi Christian, I think you are right; I just was curious. Thanks, James > On Mar 1, 2022, at 10:40 AM, <christian.haider(a)smalltalked-visuals.com> <christian.haider(a)smalltalked-visuals.com> wrote: > > Hi James, > > I am not aware that I override any system methods. That would change the behavior of the base system and that is not ok. > I do extend system classes though. > But maybe I donât understand your questionâ¦ > > Christian > > > Von: James Foster <smalltalk(a)jgfoster.net> > Gesendet: Dienstag, 1. MÃ¤rz 2022 19:23 > An: Pharo Mailing List <pharo-users(a)lists.pharo.org> > Cc: ESUG Mailing list <esug-list(a)lists.esug.org> > Betreff: [Pharo-users] Re: [PDFtalk] Porting to non-namespace Smalltalks > > Hi Christian, > > Iâm glad to hear that PDFtalk is getting such good exposure! I have a brief question about the VW port: Did you need to replace any base methods (using package overrides, not subclass overrides)? > > James > > >> On Mar 1, 2022, at 10:08 AM, christian.haider(a)smalltalked-visuals.com <mailto:christian.haider@smalltalked-visuals.com> wrote: >> >> Hi all, >> >> PDFtalk is a PDF library for VisualWorks[1]. The library has been ported successfully to Gemstone[2]. >> Now, there is interest from companies in a port to Squeak and VA Smalltalk. >> >> The project[3] has started and we are making good progress. >> The first step: porting the Values package. >> This is easy, because there are no namespace issues. >> >> The next step is to implement class renamings so that namespaced classes can be renamed to global prefixed names. >> >> Then PDFtalk with all its components, except for the UI, can be ported. >> >> The porting approach is different to the traditional way of loading and fixing. >> The import files for other Smalltalks are generated from VisualWorks where the code is transformed by declarative rules. >> The approach is documented in [4]. >> >> I set up a GitHub organization for this project[5]. There, the fileouts for each dialect are published (Gemstone, Squeak and VA Smalltalk so far), so that people without VisualWorks can work with the code in their Smalltalk. >> >> Also, I record and explain all steps of the porting process for Squeak in great detail[6], so that people can follow it. >> >> I would like to invite Smalltalkers from all dialects to take part in this project. >> The code transformations for Squeak will be quite similar to the ones needed for Pharo and Cuis. >> Therefore, each port to one Smalltalk will help the port to other Smalltalks. >> >> Any takers? >> >> Happy hacking, >> Christian >> >> >> [1] https://wiki.pdftalk.de/doku.php?id=start <https://wiki.pdftalk.de/doku.php?id=start> >> [2] https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone <https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone> >> [3] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout <https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout> >> [4] https://wiki.pdftalk.de/doku.php?id=smalltalktransform <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> >> [5] https://github.com/PortingPDFtalk <https://github.com/PortingPDFtalk> >> [6] https://wiki.pdftalk.de/doku.php?id=valuesportinglog <https://wiki.pdftalk.de/doku.php?id=valuesportinglog> > > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org

March 1, 2022

Re: [PDFtalk] Porting to non-namespace Smalltalks

by christian.haider＠smalltalked-visuals.com

Hi James, I am not aware that I override any system methods. That would change the behavior of the base system and that is not ok. I do extend system classes though. But maybe I donât understand your questionâ¦ Christian Von: James Foster <smalltalk(a)jgfoster.net> Gesendet: Dienstag, 1. MÃ¤rz 2022 19:23 An: Pharo Mailing List <pharo-users(a)lists.pharo.org> Cc: ESUG Mailing list <esug-list(a)lists.esug.org> Betreff: [Pharo-users] Re: [PDFtalk] Porting to non-namespace Smalltalks Hi Christian, Iâm glad to hear that PDFtalk is getting such good exposure! I have a brief question about the VW port: Did you need to replace any base methods (using package overrides, not subclass overrides)? James On Mar 1, 2022, at 10:08 AM, christian.haider(a)smalltalked-visuals.com <mailto:christian.haider@smalltalked-visuals.com> wrote: Hi all, PDFtalk is a PDF library for VisualWorks[1]. The library has been ported successfully to Gemstone[2]. Now, there is interest from companies in a port to Squeak and VA Smalltalk. The project[3] has started and we are making good progress. The first step: porting the Values package. This is easy, because there are no namespace issues. The next step is to implement class renamings so that namespaced classes can be renamed to global prefixed names. Then PDFtalk with all its components, except for the UI, can be ported. The porting approach is different to the traditional way of loading and fixing. The import files for other Smalltalks are generated from VisualWorks where the code is transformed by declarative rules. The approach is documented in [4]. I set up a GitHub organization for this project[5]. There, the fileouts for each dialect are published (Gemstone, Squeak and VA Smalltalk so far), so that people without VisualWorks can work with the code in their Smalltalk. Also, I record and explain all steps of the porting process for Squeak in great detail[6], so that people can follow it. I would like to invite Smalltalkers from all dialects to take part in this project. The code transformations for Squeak will be quite similar to the ones needed for Pharo and Cuis. Therefore, each port to one Smalltalk will help the port to other Smalltalks. Any takers? Happy hacking, Christian [1] https://wiki.pdftalk.de/doku.php?id=start [2] https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone [3] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout [4] https://wiki.pdftalk.de/doku.php?id=smalltalktransform [5] https://github.com/PortingPDFtalk [6] https://wiki.pdftalk.de/doku.php?id=valuesportinglog

March 1, 2022

Re: [PDFtalk] Porting to non-namespace Smalltalks

by James Foster

Hi Christian, Iâm glad to hear that PDFtalk is getting such good exposure! I have a brief question about the VW port: Did you need to replace any base methods (using package overrides, not subclass overrides)? James > On Mar 1, 2022, at 10:08 AM, christian.haider(a)smalltalked-visuals.com wrote: > > Hi all, > > PDFtalk is a PDF library for VisualWorks[1]. The library has been ported successfully to Gemstone[2]. > Now, there is interest from companies in a port to Squeak and VA Smalltalk. > > The project[3] has started and we are making good progress. > The first step: porting the Values package. > This is easy, because there are no namespace issues. > > The next step is to implement class renamings so that namespaced classes can be renamed to global prefixed names. > > Then PDFtalk with all its components, except for the UI, can be ported. > > The porting approach is different to the traditional way of loading and fixing. > The import files for other Smalltalks are generated from VisualWorks where the code is transformed by declarative rules. > The approach is documented in [4]. > > I set up a GitHub organization for this project[5]. There, the fileouts for each dialect are published (Gemstone, Squeak and VA Smalltalk so far), so that people without VisualWorks can work with the code in their Smalltalk. > > Also, I record and explain all steps of the porting process for Squeak in great detail[6], so that people can follow it. > > I would like to invite Smalltalkers from all dialects to take part in this project. > The code transformations for Squeak will be quite similar to the ones needed for Pharo and Cuis. > Therefore, each port to one Smalltalk will help the port to other Smalltalks. > > Any takers? > > Happy hacking, > Christian > > > [1] https://wiki.pdftalk.de/doku.php?id=start <https://wiki.pdftalk.de/doku.php?id=start> > [2] https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone <https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone> > [3] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout <https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout> > [4] https://wiki.pdftalk.de/doku.php?id=smalltalktransform <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> > [5] https://github.com/PortingPDFtalk <https://github.com/PortingPDFtalk> > [6] https://wiki.pdftalk.de/doku.php?id=valuesportinglog <https://wiki.pdftalk.de/doku.php?id=valuesportinglog>

March 1, 2022

[PDFtalk] Porting to non-namespace Smalltalks

by christian.haider＠smalltalked-visuals.com

Hi all, PDFtalk is a PDF library for VisualWorks[1]. The library has been ported successfully to Gemstone[2]. Now, there is interest from companies in a port to Squeak and VA Smalltalk. The project[3] has started and we are making good progress. The first step: porting the Values package. This is easy, because there are no namespace issues. The next step is to implement class renamings so that namespaced classes can be renamed to global prefixed names. Then PDFtalk with all its components, except for the UI, can be ported. The porting approach is different to the traditional way of loading and fixing. The import files for other Smalltalks are generated from VisualWorks where the code is transformed by declarative rules. The approach is documented in [4]. I set up a GitHub organization for this project[5]. There, the fileouts for each dialect are published (Gemstone, Squeak and VA Smalltalk so far), so that people without VisualWorks can work with the code in their Smalltalk. Also, I record and explain all steps of the porting process for Squeak in great detail[6], so that people can follow it. I would like to invite Smalltalkers from all dialects to take part in this project. The code transformations for Squeak will be quite similar to the ones needed for Pharo and Cuis. Therefore, each port to one Smalltalk will help the port to other Smalltalks. Any takers? Happy hacking, Christian [1] https://wiki.pdftalk.de/doku.php?id=start [2] https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone [3] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout [4] https://wiki.pdftalk.de/doku.php?id=smalltalktransform [5] https://github.com/PortingPDFtalk [6] https://wiki.pdftalk.de/doku.php?id=valuesportinglog

March 1, 2022

Re: ByteString asDate

by Bernardo Ezequiel Contreras

try to send the #on:do: message to a block. try this ^ [ (Date readFrom: self pattern: âdd/mm/yyyyâ). true ] on: DateError do: [ false]. On Tue, Mar 1, 2022 at 11:52 AM Robert Briggs via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > I may be being stupid but the current Date Class does not appear to > protect itself against a ByteString that is not in valid date format, e.g. > by raising an Error. > > > > e.g. the code âABCâ asDate opens the Debugger on #isLetter was sent to > nil because it appears to expect more letters after $C but the peek > returns nil instead. > > This seems to me to require a more defensive programming approach. > > > > I would like to validate a user input as a valid date in a number of > different formats before converting it to a Date and storing it in my model. > > > > Iâve tried using the Date parser, e.g. > > > > Date readFrom: '04/02/2013' readStream pattern: 'dd/mm/yyyy'. > > > > > > This is fine for simply parsing a valid string but rates a DateError if it > doesnât match the . So entering â04/13/2013â cleverly raises âDateError: > There is no 13th monthâ. > > > > My thought was I could use this to return a simple true/false result in a > ByteString extension in my application for example as follows: > > > > ByteString >> isValdiDate > > > > (Date readFrom: self pattern: âdd/mm/yyyyâ) on: DateError do: [^ false]. > > ^ true > > > > However this doesnât intercept the DateError which is simply reported in > the Debugger as before. This may be my lack of uncderstaning of the > Exception handling in Pharo. > > > > Any and all thoughts welcome. > > > > R > > > > > > > > > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

March 1, 2022

ByteString asDate

by Robert Briggs

I may be being stupid but the current Date Class does not appear to protect itself against a ByteString that is not in valid date format, e.g. by raising an Error. e.g. the code Â âABCâ asDate opens the Debugger on #isLetter was sent to nil because it appears to expect more letters after $C but the peek returns nil instead. This seems to me to require a more defensive programming approach. I would like to validate a user input as a valid date in a number of different formats before converting it to a Date and storing it in my model. Iâve tried using the Date parser, e.g. Date readFrom: '04/02/2013' readStream pattern: 'dd/mm/yyyy'. This is fine for simply parsing a valid string but rates a DateError if it doesnât match the .Â So entering â04/13/2013â cleverly raises âDateError: There is no 13th monthâ. My thought was I could use this to return a simple true/false result in a ByteString extension in my application for example as follows: ByteString >> isValdiDate (Date readFrom: self pattern: âdd/mm/yyyyâ) on: DateError do: [^ false]. ^ true However this doesnât intercept the DateError which is simply reported in the Debugger as before.Â Â This may be my lack of uncderstaning of the Exception handling in Pharo. Any and all thoughts welcome. R

March 1, 2022

Re: Wanted: Backend + Database project

by Santiago Bragagnolo

Wikimedia? What do you mean? do they have some pharo application on the context? El mar, 1 mar 2022 a las 12:21, gettimothy via Pharo-users (< pharo-users(a)lists.pharo.org>) escribiÃ³: > Wikimedia > > > > ---- On Tue, 01 Mar 2022 05:21:15 -0500 *Santiago Bragagnolo > <santiagobragagnolo(a)gmail.com <santiagobragagnolo(a)gmail.com>>* wrote ---- > > Hello everybody! > In my company we are working on an approach to migrate from monolithic > applications to microservices. > The approach has been tested on a java project, we are looking now to test > it in pharo. > > For doing so we are looking for a monolithic backend project that proposes > some kind of API and uses a database. > > Does anybody knows about a project that complies to this restrictions? > > Thanks a lot in advance! > > Santiago > > >

March 1, 2022

How to unsubscribe?

by contactme＠kathe.in

Hello, I tried issuing the "unsubscribe" and "help" commands to the mailing list management system but didn't get any response. May I know how to go about "unsubscribing" from this mailing list? Thank you. Â

March 1, 2022