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

Re: mapping CamelCase to <custom-tag-name>

by Kasper Osterbye

> > What's wrong with > > $- join: (s cutCamelCase collect: [ :each | each asLowercase]) There is no method called cutCamelCase in Pharo. If there was, this was exactly the right solution to use something existing. Best, Kasper

Oct. 26, 2022

Re: mapping CamelCase to <custom-tag-name>

by Richard O'Keefe

The important thing is that there is no NEED to write a new method to split a Smalltalk identifier into pieces, because there already *IS* such a method. Only write a new method if the existing one doesn't actually work for you. For example, what do you want to be done with strings or symbols that contain non-alphanumeric characters, like #== ? What do you want done with underscores and digits in strings like 'INTL_61_123_456'? On Wed, 26 Oct 2022 at 22:41, Richard O'Keefe <raoknz(a)gmail.com> wrote: > What's wrong with > > $- join: (s cutCamelCase collect: [ :each | each asLowercase]) > > where s is the string you want to transform? > I'm sure you're aware of the proverb: > You have a problem and you decide to solve it with > a regular expression. Now you have TWO problems. > > MYWeirdName and MyWeirdName both map to my-weird-name, > but perhaps you are happy with that. > > On Sat, 22 Oct 2022 at 21:57, Siemen Baader <siemenbaader(a)gmail.com> > wrote: > >> Hi, >> >> I'm looking for an elegant way to convert class names with optional >> namespace prefixes to names for custom html elements. >> >> MYCustomElement and CustomElement >> >> to >> <my-custom-element> and <custom-element> >> >> There must be an elegant way to do it with regex or inject, but I'm >> embarrassed to say I can't get my head around it. I can get it to match the >> regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall >> correctly) but can't get a collection of the individual elements 'MY' >> 'Custom" 'Element' to lowercase and join. >> >> Thanks for any hints! >> >> cheers >> Siemen >> >

Oct. 26, 2022

Re: mapping CamelCase to <custom-tag-name>

by Richard O'Keefe

What's wrong with $- join: (s cutCamelCase collect: [ :each | each asLowercase]) where s is the string you want to transform? I'm sure you're aware of the proverb: You have a problem and you decide to solve it with a regular expression. Now you have TWO problems. MYWeirdName and MyWeirdName both map to my-weird-name, but perhaps you are happy with that. On Sat, 22 Oct 2022 at 21:57, Siemen Baader <siemenbaader(a)gmail.com> wrote: > Hi, > > I'm looking for an elegant way to convert class names with optional > namespace prefixes to names for custom html elements. > > MYCustomElement and CustomElement > > to > <my-custom-element> and <custom-element> > > There must be an elegant way to do it with regex or inject, but I'm > embarrassed to say I can't get my head around it. I can get it to match the > regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall > correctly) but can't get a collection of the individual elements 'MY' > 'Custom" 'Element' to lowercase and join. > > Thanks for any hints! > > cheers > Siemen >

Oct. 26, 2022

UK Smalltalk User Group Meeting - 26 October 2022

by Giovanni Corriga

For this month's meeting, we'll take it easy and have an online social! Bring your favourite drinks - beer, coffee, or whatever you prefer! This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/289339721/ ) to receive the meeting details.

Oct. 25, 2022

Looking for an engineer position to work on Virtual Machines

by Pierre Misse-Chanabier

Hello, My name is Pierre Misse-Chanabier. I'm finishing my PhD in the RMOD team on testing Virtual Machines in about two months. I am therefore looking for a Job, hopefully in the Pharo community ! Ideally, I'm looking to work in the domains of Virtual Machines or Language Tooling, or Meta-programing, but I'm open to other opportunities. See my CV attached. I have to stay in Lille for at least the next year, therefore, I am looking to work remotely. Here are my most important projects and publications about them: Illicium : a framework to generate C code from Pharo code. Github repository: [ https://github.com/hogoww/Illicium | https://github.com/hogoww/Illicium ] IWST'19 Illicium: A modular transpilation toolchain from Pharo to C [ https://hal.archives-ouvertes.fr/hal-02297860/ | https://hal.archives-ouvertes.fr/hal-02297860/ ] version poster SAC'22 & full ICSR'22: Differential testing of simulation-based VM generators: automatic detection of VM generator semantic gaps between simulation and generated VMs [ https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 | https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 ] [ https://dl.acm.org/doi/abs/10.1145/3477314.3507171 | https://dl.acm.org/doi/abs/10.1145/3477314.3507171 ] Polyphemus: Retro engineering of the Pharo Image, and ease of VM tooling Github Repository: [ https://github.com/hogoww/Polyphemus/ | https://github.com/hogoww/Polyphemus/ ] Video Presentation for Esug Innovation award (I was unable to present it myself): [ https://www.youtube.com/watch?v=zf3cCtNW830 | https://www.youtube.com/watch?v=zf3cCtNW830 ] VMIL'22: Ease VM Level Tooling with Language Level Ordinary Object Pointers [ https://hal.inria.fr/hal-03827632 | https://hal.inria.fr/hal-03827632 ] (preprint) I am particularly interested in my latest work: Polyphemus. I have also worked on many part of the Pharo ecosystem. The Pharo VM, The Pharo bootstrap, Calypso, Debugger, selector extraction, Iceberg scripting, SUnit ... Let me know if you have openings or questions ! Pierre

Oct. 25, 2022

How to handle conflict resolution in baselines?

by Eric Merritt

Everyone, In a baseline in a project I am working on I have a dependency on both Magritte and Seaside. Magritte loads fine, but when Seaside loads, Monticello declares a conflict on the Grease package. You can see the WIP baseline here: https://github.com/ericbmerritt/profeos/tree/feat/working-goals/BaselineOfP… . So far, I haven't found a solution to resolve conflicts in the spec. The closest solution I have found is here: https://github.com/CCMi-FIT/kendrick-modeller/blob/9c76ff8170c67d5472cc1e1b… It works but seems to be stepping out of the declarative form of baseline definition. Is there another solution? Thanks, Eric

Oct. 24, 2022

Re: mapping CamelCase to <custom-tag-name>

by Siemen Baader

Thank you very much, Kasper! Even with an implementation, wow.. I will use your solution. cheers Siemen On Sat, Oct 22, 2022 at 4:08 PM Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > I took this a my afternoon code-quiz, so here is a solution if you want it: > splitCamelCase > | str split word| > "Split an expanded camelcase word into constituents. Extened camel > case allow some words to be fully uppercase" > "'ZAPMeToo' splitCamelCase >>> #('ZAP' 'Me' 'Too')" > str := ReadStream on: self. > split := OrderedCollection new. > word := WriteStream on: ''. > [ str atEnd ] whileFalse: [ | char | > char := str next. > (char isUppercase and: [str atEnd or: [str peek > isLowercase]]) > ifTrue: [ split add: word contents. word := > WriteStream on: '' ]. > word nextPut: char ]. > split add: word contents. > ^ split asArray > > You should then use cute join and asLowercase to go rest of the way. > > Best, > > Kasper > > > > > On 22 Oct 2022, at 14.53, Kasper Osterbye <kasper.osterbye(a)gmail.com> > wrote: > > > > My feeling is that it cannot be solved by regular expressions. The > reason it that there is the regular expressions in smalltalk/pharo does not > have look-ahead or backtracking. In your example the capital Y is part of > MY, but C starts a new word. I do not know of anyway to express that in > smalltalk regular expressions. > > > > So I believe this is one of the cases where you add an extension method > to string which does the job using plain coding. > > > > Best, > > > > Kasper > > > >> On 22 Oct 2022, at 10.56, Siemen Baader <siemenbaader(a)gmail.com> wrote: > >> > >> Hi, > >> > >> I'm looking for an elegant way to convert class names with optional > namespace prefixes to names for custom html elements. > >> > >> MYCustomElement and CustomElement > >> > >> to > >> <my-custom-element> and <custom-element> > >> > >> There must be an elegant way to do it with regex or inject, but I'm > embarrassed to say I can't get my head around it. I can get it to match the > regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall > correctly) but can't get a collection of the individual elements 'MY' > 'Custom" 'Element' to lowercase and join. > >> > >> Thanks for any hints! > >> > >> cheers > >> Siemen > > >

Oct. 24, 2022

Re: mapping CamelCase to <custom-tag-name>

by Kasper Osterbye

I took this a my afternoon code-quiz, so here is a solution if you want it: splitCamelCase | str split word| "Split an expanded camelcase word into constituents. Extened camel case allow some words to be fully uppercase" "'ZAPMeToo' splitCamelCase >>> #('ZAP' 'Me' 'Too')" str := ReadStream on: self. split := OrderedCollection new. word := WriteStream on: ''. [ str atEnd ] whileFalse: [ | char | char := str next. (char isUppercase and: [str atEnd or: [str peek isLowercase]]) ifTrue: [ split add: word contents. word := WriteStream on: '' ]. word nextPut: char ]. split add: word contents. ^ split asArray You should then use cute join and asLowercase to go rest of the way. Best, Kasper > On 22 Oct 2022, at 14.53, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > > My feeling is that it cannot be solved by regular expressions. The reason it that there is the regular expressions in smalltalk/pharo does not have look-ahead or backtracking. In your example the capital Y is part of MY, but C starts a new word. I do not know of anyway to express that in smalltalk regular expressions. > > So I believe this is one of the cases where you add an extension method to string which does the job using plain coding. > > Best, > > Kasper > >> On 22 Oct 2022, at 10.56, Siemen Baader <siemenbaader(a)gmail.com> wrote: >> >> Hi, >> >> I'm looking for an elegant way to convert class names with optional namespace prefixes to names for custom html elements. >> >> MYCustomElement and CustomElement >> >> to >> <my-custom-element> and <custom-element> >> >> There must be an elegant way to do it with regex or inject, but I'm embarrassed to say I can't get my head around it. I can get it to match the regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall correctly) but can't get a collection of the individual elements 'MY' 'Custom" 'Element' to lowercase and join. >> >> Thanks for any hints! >> >> cheers >> Siemen >

Oct. 22, 2022

Re: mapping CamelCase to <custom-tag-name>

by Kasper Osterbye

My feeling is that it cannot be solved by regular expressions. The reason it that there is the regular expressions in smalltalk/pharo does not have look-ahead or backtracking. In your example the capital Y is part of MY, but C starts a new word. I do not know of anyway to express that in smalltalk regular expressions. So I believe this is one of the cases where you add an extension method to string which does the job using plain coding. Best, Kasper > On 22 Oct 2022, at 10.56, Siemen Baader <siemenbaader(a)gmail.com> wrote: > > Hi, > > I'm looking for an elegant way to convert class names with optional namespace prefixes to names for custom html elements. > > MYCustomElement and CustomElement > > to > <my-custom-element> and <custom-element> > > There must be an elegant way to do it with regex or inject, but I'm embarrassed to say I can't get my head around it. I can get it to match the regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall correctly) but can't get a collection of the individual elements 'MY' 'Custom" 'Element' to lowercase and join. > > Thanks for any hints! > > cheers > Siemen

Oct. 22, 2022

mapping CamelCase to <custom-tag-name>

by Siemen Baader

Hi, I'm looking for an elegant way to convert class names with optional namespace prefixes to names for custom html elements. MYCustomElement and CustomElement to <my-custom-element> and <custom-element> There must be an elegant way to do it with regex or inject, but I'm embarrassed to say I can't get my head around it. I can get it to match the regex '((:isUppercase:+)*)((:isUppercase::isLowercase:+)*)', (if I recall correctly) but can't get a collection of the individual elements 'MY' 'Custom" 'Element' to lowercase and join. Thanks for any hints! cheers Siemen

Oct. 22, 2022