- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Question on KmGlobalDispatcher

by Ben Coman

Hi David, I invite you to consider this an opportunity to submit a PR to fix it. I'm happy to walk you though the process if you ping me on Discord chat. I remember it felt cool to have my first code integrated. Pharo is yours. cheers -ben On Wed, 20 Feb 2019 at 02:16, ducasse <stepharo(a)netcourrier.com> wrote: > Hello David > > Indeed this is a good catch. > Can you open a bug entry on github? > Else I will do it but this is cool to get involved that way > > On 19 Feb 2019, at 17:37, David Richards <david.i.richards.iii(a)gmail.com> > wrote: > > Why does the class name KmGlobalDispatcher have a small 'm'? > > Should it be more consistently named KMGlobalDispatcher, as all other > classes in package: 'Keymapping-Core'? > > Object subclass: #KmGlobalDispatcher > instanceVariableNames: 'dispatcher' > classVariableNames: '' > package: 'Keymapping-Core' > > Just curious why this name seems inconsistent. I don't recall seeing an > inconsistency with class name prefixes in any other package group. Is this > just a mistake, or rather an opportunity to learn something interesting > about how classes should be named in Pharo? As a beginner, I'm not sure > which. > > Thanks > David > > >

Feb. 20, 2019

Re: [Pharo-dev] [Vm-dev] VMMaker in Pharo [Was: Squeak and Tonel]

by David T. Lewis

On Wed, Feb 20, 2019 at 09:23:55AM +0100, Tudor Girba wrote: > > Hi, > > I have seen that code, and the issue I wanted to address is to have the > decision about which dialect a piece of code is ran on in one single place. > This should make it easier to find statically. > > Indeed, this will not necessarily be guaranteed to work when moving from > one version of Pharo to another. But, that problem can be addressed by > tracing releases in a reproducible fashion. And in the VMMaker case, the > scenario is about a development environment not a production system. So, > it should be reasonable to point developers to a working configuration > that pairs the Pharo/Squeak version and the VMMaker version. > > What do you think? > > Cheers, > Doru > Hi Doru and Eliiot, The approach that I have been using to address this in OSProcess is to put the compatibility methods in one place, in the 'compatibility' category in class OSProcess. This allows support for the different file system interfaces in Cuis, Pharo and Squeak. For example, one of the compatibility methods is: OSProcess class>>directoryExists: path "Answer true if a directory of the given name exists. The given name may be either a full path name or a local directory within this directory." ^ self useFileMan ifTrue: [((Smalltalk at: #DirectoryEntry) perform: #withPathName: with: path) exists] ifFalse: [self useFileSystem ifTrue: [ (path perform: #asFileReference) exists ] ifFalse: [ (Smalltalk at: #FileDirectory) default directoryExists: path ]] And the tests for Cuis/Pharo/Squeak are in these two methods: OSProcess class>>useFileSystem "If true use FileSystem, otherwise use traditional FileDirectory. See senders for methods with file system dependencies." ^ Smalltalk hasClassNamed: #FileReference OSProcess class>>useFileMan "If true use FileMan for directory and file access. See senders for methods with file system dependencies." ^ Smalltalk hasClassNamed: #FileIOAccessor This is ugly but it does work, and I been able to maintain OSProcess and CommandShell for the Squeak diaspora over a number of years in this manner. It also means that I do not need to worry if Squeak moves to FileMan(*) or FileSystem at some point in the future. I don't think that VMMaker should have a hard dependency on OSProcess, but as a practical matter you probably have OSProcess loaded in the VM development image anyway, so you could try using these methods directly and see how ugly things get. HTH, Dave * Personally I like the FileMan approach in Cuis best, but that is another topic entirely ;-)

Feb. 20, 2019

Re: [Pharo-dev] VMMaker in Pharo [Was: Squeak and Tonel]

by Tudor Girba

Hi, I have seen that code, and the issue I wanted to address is to have the decision about which dialect a piece of code is ran on in one single place. This should make it easier to find statically. Indeed, this will not necessarily be guaranteed to work when moving from one version of Pharo to another. But, that problem can be addressed by tracing releases in a reproducible fashion. And in the VMMaker case, the scenario is about a development environment not a production system. So, it should be reasonable to point developers to a working configuration that pairs the Pharo/Squeak version and the VMMaker version. What do you think? Cheers, Doru > On Feb 20, 2019, at 4:39 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Doru, > > On Mon, Feb 18, 2019 at 8:14 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Eliot, > > Please, let me clarify the current direction: I am not trying to get you to Pharo at this point. I only want to reach a point where the VMMaker code runs in Pharo. This will allow us to bootstrap an environment that can later be evaluated. > > Having the sources in Git is secondary at this point. With the current infrastructure, we get those sources in Git while preserving the history from the Squeaksource repo automatically. The code will be loadable from either Git or Squeaksource, but the commit repository is still the Squeaksource one. So, nothing would change from the workflow of the current committers. What we gain with the Git repository is a test ground and an easier ability to load the code in Pharo, all at no extra cost and without affecting your flow. > > Let me emphasize this again: the Git support should not be the main issue at this point. Now we would only need to get the code to run in Pharo. For this, we would need to introduce a few support methods. One key method that Andrei and I would like to propose, and that we used before in other porting projects, is: > Object>>vmMakerForSqueak: aBlockToBeExecutedOnlyInSqueak forPharo: aBlockToBeExecutedOnlyInPharo > > I am doing things on a case-by-case basis. Currently I use classNamed:, e.g. > > (Smalltalk classNamed: #FileSystem) > ifNotNil: [:fileSystem| fileSystem disk delimiter asInteger] > ifNil: [FileDirectory pathNameDelimiter asInteger] > > (Smalltalk classNamed: #CurrentReadOnlySourceFiles) > ifNil: syncAction > ifNotNil: [:crosf| crosf cacheDuring: syncAction] > > (Smalltalk classNamed: #Project) > ifNotNil: [:project| Project uiProcess] "Squeak" > ifNil: [UIManager default uiProcess] "Pharo" > > ((Smalltalk classNamed: #FillInTheBlankMorph) > ifNotNil: "Squeak" > [:fITBM| > fITBM > request: 'Input please!' > initialAnswer: '' > centerAt: ActiveHand cursorPoint > inWorld: ActiveWorld > onCancelReturn: nil > acceptOnCR: true] > ifNil: "Pharo; onCancelReturn: nil is the default here" > [UIManager default > request: 'Input please!' > initialAnswer: '']). > > this at least allows Squeak to migrate to FileSystem without having to rewrite. Using the above I was already able to get most of VMMaker working in Pharo6. Things broke for Pharo7, which indicates that the vmMakerForSqueak:forPharo: approach has vulnerabilities. > > > Andrei will propose a commit in VMMaker Inbox this week. > > What do you say? > > Cheers, > Doru > > > > On Feb 18, 2019, at 7:55 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Doru, > > > > On Sun, Feb 17, 2019 at 10:33 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi Eliot, > > > > You raise a few technical concerns related to VMMaker that seem addressable: > > > > 1. Rendering technology: Both in Pharo and in GT, there exist in-image canvases, Athens and Sparta respectively, that are backend independent. This allows us to have image-based drawing logic, like BitBlt or even better, the drawing capabilities that Juan Vuletich built in Morphic 3, transparently. In fact, we even started to look at the code from Morphic 3 and we think itâs not much effort to make it work behind Sparta. This would provide a complete solution that would not rely on any external libraries. > > > > 2. Git history. We used to have the author and timestamp in the metadata of Tonel but because it generated unwanted conflicts it was decided to remove it. I think this is a good decision and one based on the experience of using it. But, why do you think the algorithm of retrieving Git could not be made to work in Squeak? Is there a specific technical reason, or is it more that you do not see the effort being spent in this direction? I am asking to understand what could a possible solution be. > > > > > > But, letâs take a step back. George and Andrei did move the VMMaker code, including all its history, into Git using (and enhancing) https://github.com/peteruhnak/git-migration. > > > > The code is here: > > https://github.com/feenkcom/opensmalltalk-vm/tree/pullrequest5/vmmaker > > > > Our goal was to make the code loadable and runnable in Pharo through Git. We have a reproducible process to produce this history, and this means that we can also synchronize all changes from the Monticello VMMaker repository and produce a history-preserving Git repository. > > > > The current code comes with a BaselineOfVMMaker that loads in Pharo, and the code generation seems to work to a good extent without much effort. There is still work that needs to be done especially on the simulation part, but we think most of it can be addressed through a Pharo-specific package that provides compatibility logic. > > > > I see two benefits for doing this: > > 1. It allows people in Pharo to play with the VM within the Pharo context and consequently contribute. > > 2. It allows us to build an environment dedicated for VM development without affecting the current contribution process. We can judge later whether this is useful. > > > > All this is great work. But I cannot use it until I can also function in Squeak. I know you want me to move to Pharo, but I am not convinced that it is a safe place for me to land. I have voiced my concerns before (stability, moving away from support I need (e.g. Pharo dropping read./write file streams is the latest example). Let me simply restate that "t6he devil you know is better than the devil you don't", and that I know I am productive with VMMaker in Squeak, but I *do not* know that I can be productive in Pharo (in fact, I have lots of experience of the contrary). So I will not move to Pharo any time soon and so, until there is a solution to git/tonel/squeak integration I cannot join the unified repository, must as I would like to. > > > > I'm sorry for the frustration this causes other. I am radical in some things, but deeply conservative in others. And my ability to be productive is obviously foundational. > > > > > > Cheers, > > Doru > > > > > > > On Feb 17, 2019, at 9:27 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > > > Hi All, Hi Torsten, Hi Jakob, > > > > > > On Thu, Feb 14, 2019 at 6:17 AM Torsten Bergmann <astares(a)gmx.de> wrote: > > > Hi, > > > > > > as some of you might already know "Tonel" is a file-per-class format for monticello repositories [1]. > > > > > > In Pharo land many projects are already converted to it - as regular "file tree" solution faces issues > > > with git handling due to very long file names / deep file hierarchy (often leading to trouble on Windows). > > > > > > Dales's Rowan (a new project/package manager for Smalltalk) supports FileTree and also Tonel > > > repositories [2]. There is also a tool to convert from STORE (VisualWorks Source-Code Versioning System) > > > to Tonel format [3]. > > > > > > So I wonder about adoption of Tonel in Squeak land. > > > > > > Any status/comments? > > > > > > Last year I was given contract employment by Tudor Girba's feenk which in part was to involve me porting VMMaker.oscog to Pharo in order to reap the productivity benefits of the Glamorous Toolkit when applied to VMMaker. The major direction was to unify the opensmalltalk-vm repository with a Toned-Format repository holding the Smalltalk code. > > > > > > This project, though no fault of feenk's did not go well. A big part of it was my own emotional attachment to Squeak, my "muscle memory" with Squeak and my long experience with Smalltalk-80 derived meta programming which I make extensive use of in VMMaker.oscog. But a key issue was that I was not prepared to *move* VMMaker.oscog to Pharo; for me it is key that it can live in both places. In particular I will not risk VMMaker.oscog being stranded on Pharo as it moves away from the "image-based rendering model". This is not because I don't believe in pixel-independent rendering models, but because productivity in VMMaker depends much more than on GToolkit inspection on the key architectural feature of being completely, safely simulateable (not a real English word; but meaning capable of being simulated). As Pharo moves towards external libraries to implement its UI so the degree to which VMMaker is simulated is reduced. Thus crashes in external code cannot be handled with the same power as with errors presented within the Smalltalk environment itself, and this (as harsh experience over thirty five years has taught me) is far more important for overall productivity than having powerful tailorable inspectors. > > > > > > I therefore wanted a Tonel that could both function for Squeak's Monticello and for Pharo's Iceberg. I had modified the Tonel serialization a little to provide well-formatted support for method timestamps, which are still a key and extremely useful part of Squeak Monticello's "blame" equivalent. Until git author attribution can be imported into Squeak's Monticello (something I don't see happening) I wanted merely to be able to have a variant of Tonel, enabled for example by a class variable, and hence /not/ present in Pharo, that would allow VMMaker.oscog to use Tonel but still be functional inside Squeak. I asked Esteban and was met by a flat no. Not "OK, but this is an option only you will use", but a flat "not under any circumstance". > > > > > > So here I am joining in this thread reluctantly. I'm extremely frustrated by the state of Tonel in Squeak and between the two dialects. ClÃ©ment had moved his Scorch optimizer to Tonel/git and I tried to use Metacello and Jakob's Tonel code to at least allow me to load that code and try and push forward on Sista/Scorch. The port *does not work*. Metacello fails to load Scorch. Neither Jakob nor Fabio, after putting in some effort, were able to fix the problem, and it is well beyond me. So I have accepted the fact that I will have to use the Monticello repository for Scorch/Sista. > > > > > > I had deep concerns that the pursuit of git integration would end up splitting the Pharo and Squeak communities and indeed this is now in progress. I am utterly unmotivated by the lack of cooperation, the sheer arrogance and bullying of those that say "you will move to git/tonel or else", and considering leaving VMMaker altogether. The only things that are keeping me interested are Ron Teitelbaum's Terf and me pursuing a PhD on register allocation in the context of Sista/Scorch with Robert Hirshfeld's group at HPI. > > > > > > Here's the kind of crap people like Ducasse throw at me: > > > > > > "Eliot > > > > > > At the end of the day I will probably ask the two phds that should work on language design to use truffle or pypy > > > because let us face it we cannot work with the Pharo VM. Else we will simply have to fork it (because we do not want to have > > > to jump over cuis, newspeak, squeak code constraints and I do not what) and it will be another drama is in the pico world > > > of the âopenâ smalltalk VM. " > > > > > > I am so over this crap. > > > _,,,^..^,,,_ > > > best, Eliot > > > > -- > > www.feenk.com > > > > âSoftware has no shape. Actually, it has no one shape. It has many." > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > -- > www.feenk.com > > "Sometimes the best solution is not the best solution." > > > > -- > _,,,^..^,,,_ > best, Eliot -- www.feenk.com "Beauty is where we see it."

Feb. 20, 2019

Re: [Pharo-dev] VMMaker in Pharo [Was: Squeak and Tonel]

by Eliot Miranda

Hi Doru, On Mon, Feb 18, 2019 at 8:14 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Eliot, > > Please, let me clarify the current direction: I am not trying to get you > to Pharo at this point. I only want to reach a point where the VMMaker code > runs in Pharo. This will allow us to bootstrap an environment that can > later be evaluated. > > Having the sources in Git is secondary at this point. With the current > infrastructure, we get those sources in Git while preserving the history > from the Squeaksource repo automatically. The code will be loadable from > either Git or Squeaksource, but the commit repository is still the > Squeaksource one. So, nothing would change from the workflow of the > current committers. What we gain with the Git repository is a test ground > and an easier ability to load the code in Pharo, all at no extra cost and > without affecting your flow. > > Let me emphasize this again: the Git support should not be the main issue > at this point. Now we would only need to get the code to run in Pharo. For > this, we would need to introduce a few support methods. One key method that > Andrei and I would like to propose, and that we used before in other > porting projects, is: > Object>>vmMakerForSqueak: aBlockToBeExecutedOnlyInSqueak forPharo: > aBlockToBeExecutedOnlyInPharo > I am doing things on a case-by-case basis. Currently I use classNamed:, e.g. (Smalltalk classNamed: #FileSystem) ifNotNil: [:fileSystem| fileSystem disk delimiter asInteger] ifNil: [FileDirectory pathNameDelimiter asInteger] (Smalltalk classNamed: #CurrentReadOnlySourceFiles) ifNil: syncAction ifNotNil: [:crosf| crosf cacheDuring: syncAction] (Smalltalk classNamed: #Project) ifNotNil: [:project| Project uiProcess] "Squeak" ifNil: [UIManager default uiProcess] "Pharo" ((Smalltalk classNamed: #FillInTheBlankMorph) ifNotNil: "Squeak" [:fITBM| fITBM request: 'Input please!' initialAnswer: '' centerAt: ActiveHand cursorPoint inWorld: ActiveWorld onCancelReturn: nil acceptOnCR: true] ifNil: "Pharo; onCancelReturn: nil is the default here" [UIManager default request: 'Input please!' initialAnswer: '']). this at least allows Squeak to migrate to FileSystem without having to rewrite. Using the above I was already able to get most of VMMaker working in Pharo6. Things broke for Pharo7, which indicates that the vmMakerForSqueak:forPharo: approach has vulnerabilities. > Andrei will propose a commit in VMMaker Inbox this week. > > What do you say? > > Cheers, > Doru > > > > On Feb 18, 2019, at 7:55 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > Doru, > > > > On Sun, Feb 17, 2019 at 10:33 PM Tudor Girba <tudor(a)tudorgirba.com> > wrote: > > Hi Eliot, > > > > You raise a few technical concerns related to VMMaker that seem > addressable: > > > > 1. Rendering technology: Both in Pharo and in GT, there exist in-image > canvases, Athens and Sparta respectively, that are backend independent. > This allows us to have image-based drawing logic, like BitBlt or even > better, the drawing capabilities that Juan Vuletich built in Morphic 3, > transparently. In fact, we even started to look at the code from Morphic 3 > and we think itâs not much effort to make it work behind Sparta. This would > provide a complete solution that would not rely on any external libraries. > > > > 2. Git history. We used to have the author and timestamp in the metadata > of Tonel but because it generated unwanted conflicts it was decided to > remove it. I think this is a good decision and one based on the experience > of using it. But, why do you think the algorithm of retrieving Git could > not be made to work in Squeak? Is there a specific technical reason, or is > it more that you do not see the effort being spent in this direction? I am > asking to understand what could a possible solution be. > > > > > > But, letâs take a step back. George and Andrei did move the VMMaker > code, including all its history, into Git using (and enhancing) > https://github.com/peteruhnak/git-migration. > > > > The code is here: > > https://github.com/feenkcom/opensmalltalk-vm/tree/pullrequest5/vmmaker > > > > Our goal was to make the code loadable and runnable in Pharo through > Git. We have a reproducible process to produce this history, and this means > that we can also synchronize all changes from the Monticello VMMaker > repository and produce a history-preserving Git repository. > > > > The current code comes with a BaselineOfVMMaker that loads in Pharo, and > the code generation seems to work to a good extent without much effort. > There is still work that needs to be done especially on the simulation > part, but we think most of it can be addressed through a Pharo-specific > package that provides compatibility logic. > > > > I see two benefits for doing this: > > 1. It allows people in Pharo to play with the VM within the Pharo > context and consequently contribute. > > 2. It allows us to build an environment dedicated for VM development > without affecting the current contribution process. We can judge later > whether this is useful. > > > > All this is great work. But I cannot use it until I can also function > in Squeak. I know you want me to move to Pharo, but I am not convinced > that it is a safe place for me to land. I have voiced my concerns before > (stability, moving away from support I need (e.g. Pharo dropping > read./write file streams is the latest example). Let me simply restate > that "t6he devil you know is better than the devil you don't", and that I > know I am productive with VMMaker in Squeak, but I *do not* know that I can > be productive in Pharo (in fact, I have lots of experience of the > contrary). So I will not move to Pharo any time soon and so, until there > is a solution to git/tonel/squeak integration I cannot join the unified > repository, must as I would like to. > > > > I'm sorry for the frustration this causes other. I am radical in some > things, but deeply conservative in others. And my ability to be productive > is obviously foundational. > > > > > > Cheers, > > Doru > > > > > > > On Feb 17, 2019, at 9:27 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > > > > > > Hi All, Hi Torsten, Hi Jakob, > > > > > > On Thu, Feb 14, 2019 at 6:17 AM Torsten Bergmann <astares(a)gmx.de> > wrote: > > > Hi, > > > > > > as some of you might already know "Tonel" is a file-per-class format > for monticello repositories [1]. > > > > > > In Pharo land many projects are already converted to it - as regular > "file tree" solution faces issues > > > with git handling due to very long file names / deep file hierarchy > (often leading to trouble on Windows). > > > > > > Dales's Rowan (a new project/package manager for Smalltalk) supports > FileTree and also Tonel > > > repositories [2]. There is also a tool to convert from STORE > (VisualWorks Source-Code Versioning System) > > > to Tonel format [3]. > > > > > > So I wonder about adoption of Tonel in Squeak land. > > > > > > Any status/comments? > > > > > > Last year I was given contract employment by Tudor Girba's feenk which > in part was to involve me porting VMMaker.oscog to Pharo in order to reap > the productivity benefits of the Glamorous Toolkit when applied to > VMMaker. The major direction was to unify the opensmalltalk-vm repository > with a Toned-Format repository holding the Smalltalk code. > > > > > > This project, though no fault of feenk's did not go well. A big part > of it was my own emotional attachment to Squeak, my "muscle memory" with > Squeak and my long experience with Smalltalk-80 derived meta programming > which I make extensive use of in VMMaker.oscog. But a key issue was that I > was not prepared to *move* VMMaker.oscog to Pharo; for me it is key that it > can live in both places. In particular I will not risk VMMaker.oscog being > stranded on Pharo as it moves away from the "image-based rendering model". > This is not because I don't believe in pixel-independent rendering models, > but because productivity in VMMaker depends much more than on GToolkit > inspection on the key architectural feature of being completely, safely > simulateable (not a real English word; but meaning capable of being > simulated). As Pharo moves towards external libraries to implement its UI > so the degree to which VMMaker is simulated is reduced. Thus crashes in > external code cannot be handled with the same power as with errors > presented within the Smalltalk environment itself, and this (as harsh > experience over thirty five years has taught me) is far more important for > overall productivity than having powerful tailorable inspectors. > > > > > > I therefore wanted a Tonel that could both function for Squeak's > Monticello and for Pharo's Iceberg. I had modified the Tonel serialization > a little to provide well-formatted support for method timestamps, which are > still a key and extremely useful part of Squeak Monticello's "blame" > equivalent. Until git author attribution can be imported into Squeak's > Monticello (something I don't see happening) I wanted merely to be able to > have a variant of Tonel, enabled for example by a class variable, and hence > /not/ present in Pharo, that would allow VMMaker.oscog to use Tonel but > still be functional inside Squeak. I asked Esteban and was met by a flat > no. Not "OK, but this is an option only you will use", but a flat "not > under any circumstance". > > > > > > So here I am joining in this thread reluctantly. I'm extremely > frustrated by the state of Tonel in Squeak and between the two dialects. > ClÃ©ment had moved his Scorch optimizer to Tonel/git and I tried to use > Metacello and Jakob's Tonel code to at least allow me to load that code and > try and push forward on Sista/Scorch. The port *does not work*. Metacello > fails to load Scorch. Neither Jakob nor Fabio, after putting in some > effort, were able to fix the problem, and it is well beyond me. So I have > accepted the fact that I will have to use the Monticello repository for > Scorch/Sista. > > > > > > I had deep concerns that the pursuit of git integration would end up > splitting the Pharo and Squeak communities and indeed this is now in > progress. I am utterly unmotivated by the lack of cooperation, the sheer > arrogance and bullying of those that say "you will move to git/tonel or > else", and considering leaving VMMaker altogether. The only things that > are keeping me interested are Ron Teitelbaum's Terf and me pursuing a PhD > on register allocation in the context of Sista/Scorch with Robert > Hirshfeld's group at HPI. > > > > > > Here's the kind of crap people like Ducasse throw at me: > > > > > > "Eliot > > > > > > At the end of the day I will probably ask the two phds that should > work on language design to use truffle or pypy > > > because let us face it we cannot work with the Pharo VM. Else we will > simply have to fork it (because we do not want to have > > > to jump over cuis, newspeak, squeak code constraints and I do not > what) and it will be another drama is in the pico world > > > of the âopenâ smalltalk VM. " > > > > > > I am so over this crap. > > > _,,,^..^,,,_ > > > best, Eliot > > > > -- > > www.feenk.com > > > > âSoftware has no shape. Actually, it has no one shape. It has many." > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > -- > www.feenk.com > > "Sometimes the best solution is not the best solution." > > -- _,,,^..^,,,_ best, Eliot

Feb. 20, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Paul DeBruicker

Oh. Hmm. Seems like the url for Metacello should point right to the "repository" directory in the git repo. so ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo/repository but when I use scp to copy a file over ssh I always have to add an extra colon (:) before the path, after the domain/port combo. So maybe its ssh://git@bitbucket.somehost.be:8899:/xxx/t3-pharo/repository Sven Van Caekenberghe-2 wrote > But it is not just private, it runs on our own servers. > > Maybe MCBitbucketRepository has to be extended like the MCGitlabRepository > as Cyril suggested ... > >> On 19 Feb 2019, at 19:08, Paul DeBruicker < > pdebruic@ > > wrote: >> >> Does >> >> Metacello>>#bitbucketUser:project:commitish: path: >> >> do what you want? >> >> >> You can set your bitbucket username/password with >> >> MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword >> >> Which should let you access your private repo >> >> >> >> >> >> Sven Van Caekenberghe-2 wrote >>> Hi, >>> >>> My code lives in a private bitbucket git repo, how can I use this with >>> the >>> Metacello scripting API ? >>> >>> Metacello new >>> repository: 'ssh:// >> >>> git@.somehost >> >>> :8899/xxx/t3-pharo.git'; >>> baseline: 'BetaNineT3'; >>> load: #('core' 'gb'). >>> >>> IOW, what is the correct URL ? >>> >>> Is that even possible, if not what is the alternative ? >>> >>> I created/used this repo before, using keys as authentication. >>> >>> Could one also use username/password authentication, like when deploying >>> ? >>> >>> Sven >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Sven Van Caekenberghe

But it is not just private, it runs on our own servers. Maybe MCBitbucketRepository has to be extended like the MCGitlabRepository as Cyril suggested ... > On 19 Feb 2019, at 19:08, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Does > > Metacello>>#bitbucketUser:project:commitish: path: > > do what you want? > > > You can set your bitbucket username/password with > > MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword > > Which should let you access your private repo > > > > > > Sven Van Caekenberghe-2 wrote >> Hi, >> >> My code lives in a private bitbucket git repo, how can I use this with the >> Metacello scripting API ? >> >> Metacello new >> repository: 'ssh:// > >> git@.somehost > >> :8899/xxx/t3-pharo.git'; >> baseline: 'BetaNineT3'; >> load: #('core' 'gb'). >> >> IOW, what is the correct URL ? >> >> Is that even possible, if not what is the alternative ? >> >> I created/used this repo before, using keys as authentication. >> >> Could one also use username/password authentication, like when deploying ? >> >> Sven > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2019

Re: [Pharo-dev] Question on KmGlobalDispatcher

by ducasse

Hello David Indeed this is a good catch. Can you open a bug entry on github? Else I will do it but this is cool to get involved that way > On 19 Feb 2019, at 17:37, David Richards <david.i.richards.iii(a)gmail.com> wrote: > > Why does the class name KmGlobalDispatcher have a small 'm'? > > Should it be more consistently named KMGlobalDispatcher, as all other classes in package: 'Keymapping-Core'? > > Object subclass: #KmGlobalDispatcher > instanceVariableNames: 'dispatcher' > classVariableNames: '' > package: 'Keymapping-Core' > > Just curious why this name seems inconsistent. I don't recall seeing an inconsistency with class name prefixes in any other package group. Is this just a mistake, or rather an opportunity to learn something interesting about how classes should be named in Pharo? As a beginner, I'm not sure which. > > Thanks > David

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Paul DeBruicker

Does Metacello>>#bitbucketUser:project:commitish: path: do what you want? You can set your bitbucket username/password with MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword Which should let you access your private repo Sven Van Caekenberghe-2 wrote > Hi, > > My code lives in a private bitbucket git repo, how can I use this with the > Metacello scripting API ? > > Metacello new > repository: 'ssh:// > git@.somehost > :8899/xxx/t3-pharo.git'; > baseline: 'BetaNineT3'; > load: #('core' 'gb'). > > IOW, what is the correct URL ? > > Is that even possible, if not what is the alternative ? > > I created/used this repo before, using keys as authentication. > > Could one also use username/password authentication, like when deploying ? > > Sven -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2019

Question on KmGlobalDispatcher

by David Richards

Why does the class name KmGlobalDispatcher have a small 'm'? Should it be more consistently named KMGlobalDispatcher, as all other classes in package: 'Keymapping-Core'? Object subclass: #KmGlobalDispatcher instanceVariableNames: 'dispatcher' classVariableNames: '' package: 'Keymapping-Core' Just curious why this name seems inconsistent. I don't recall seeing an inconsistency with class name prefixes in any other package group. Is this just a mistake, or rather an opportunity to learn something interesting about how classes should be named in Pharo? As a beginner, I'm not sure which. Thanks David

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Cyril Ferlicot

On Tue, Feb 19, 2019 at 2:57 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > My code lives in a private bitbucket git repo, how can I use this with the Metacello scripting API ? > > Metacello new > repository: 'ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo.git'; > baseline: 'BetaNineT3'; > load: #('core' 'gb'). > > IOW, what is the correct URL ? > > Is that even possible, if not what is the alternative ? > > I created/used this repo before, using keys as authentication. > > Could one also use username/password authentication, like when deploying ? Hi, I think non default ssh port will not be supported by Metacello. I had to add it for gitlab to be able to reference repositories from a self hosted gitlab with non default ssh port. I guess the same can be done for bitbucket but it I doub it's already done. For Gitlab I added it in MCGitlabRepository for the Metacello part and in the Iceberg extensions of this class to use the new infos in Iceberg. (Method scpUrl) > > Sven > > > -- Cyril Ferlicot https://ferlicot.fr

Feb. 19, 2019