- Pharo-users - lists.pharo.org

Re: The orange 'content modified' indicator

by Robert Briggs

Hi Esteban Thankyou for responding. You say itâs a very bad way to show something is âdirtyâ yet Pharo continues to use it in the System Browser and elsewhere.Â Also from my researching It was used in Spec but has been deprecated in Spec2. I think It is also used in VisualWorks and earlier SmallTalk systems. Personally I find it very useful when editing code across a number of different objects as it reminds me that Iâve not saved the edits (which has caught me out when subsequently running a test for example.Â What is considered to be a better way to show that something is âdirtyâ, and is anything planned for Spec2 in the future in this respect? Regards R From: Esteban Lorenzano <estebanlm(a)netc.eu> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Thursday, 3 March 2022 at 15:16 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Robert Briggs <rbriggs2009(a)me.com> Subject: [Pharo-users] Re: The orange 'content modified' indicator Hi, No, this is not possible. Main reason is because that little triangle is a very bad way to show something is "dirty", but also because Spec itself does not has the concept of "dirty". If you want such mechanism you need to implement it yourself (you can listen when content changes and add/remove a style, for example). Esteban On Mar 3 2022, at 3:28 pm, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: Hi Pharo browserâs show a little triangular orange triangle in the top right corner when code is edited by the user but not yet Accepted. Is there a mechanism for doing the same, e.g. in an editable SpTextPresenter? Iâve looked around related Spec2 Classes but unable to find a method to do this. Advice please. Regards R

March 3, 2022

Re: The orange 'content modified' indicator

by Esteban Lorenzano

Hi, No, this is not possible. Main reason is because that little triangle is a very bad way to show something is "dirty", but also because Spec itself does not has the concept of "dirty". If you want such mechanism you need to implement it yourself (you can listen when content changes and add/remove a style, for example). Esteban On Mar 3 2022, at 3:28 pm, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > Hi > > > Pharo browserâs show a little triangular orange triangle in the top right corner when code is edited by the user but not yet Accepted. > > Is there a mechanism for doing the same, e.g. in an editable SpTextPresenter? > > Iâve looked around related Spec2 Classes but unable to find a method to do this. > > Advice please. > > Regards > R

March 3, 2022

The orange 'content modified' indicator

by Robert Briggs

Hi Pharo browserâs show a little triangular orange triangle in the top right corner when code is edited by the user but not yet Accepted. Is there a mechanism for doing the same, e.g. in an editable SpTextPresenter? Iâve looked around related Spec2 Classes but unable to find a method to do this. Advice please. Regards R

March 3, 2022

Dragging objects with restrictions

by Eduardo Ochs

Hi people, I am a beginner with SmallTalks. At the moment I understand the basics about the language but very little about the graphical interface... Can you recommend me docs and tutorials on how to do something like this in Pharo? http://angg.twu.net/eev-videos/2022dragABC.mp4 The link above is to a video that is 20 seconds long. In the first 15 seconds (suggestion: ignore them!) I use weird Emacs tricks to draw three objects in a Tcl/Tk canvas - the letters A, B, and C - and to bind "mousebutton1 motion" to different actions in each of them... ...and in the last 5 seconds of the video I draw the letters A, B and C with the mouse to show what are these actions. In short: the letter A moves freely, the letter B moves in the same horizontal line as A, and when I drag C around it moves B horizontally to force B to be in the same horizontal line as C. Thanks in advance! =) Eduardo Ochs http://angg.twu.net/#eev

March 2, 2022

Re: ByteString asDate

by Robert Briggs

Thanks Bernardo. Seems your suggestion creates a Protected Block which I understand.Â I will read the document some more a necessary.Â Thank you for taking time to respond. From: Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Wednesday, 2 March 2022 at 14:19 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: ByteString asDate see chapter 13 in http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf it's a chapter dedicated to exceptions. the #on:do: message is in section 13.4. regarding the asDate message, i really don't know. you need a kind of validator. sorry, if i'm not much help. On Wed, Mar 2, 2022 at 7:35 AM Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: 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. -- Bernardo E.C. Sent from a cheap desktop computer in South America.

March 2, 2022

Re: ByteString asDate

by Bernardo Ezequiel Contreras

see chapter 13 in http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf it's a chapter dedicated to exceptions. the #on:do: message is in section 13.4. regarding the asDate message, i really don't know. you need a kind of validator. sorry, if i'm not much help. On Wed, Mar 2, 2022 at 7:35 AM Robert Briggs via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > 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. > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

March 2, 2022

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