- Pharo-users - lists.pharo.org

configurable space in XML Writer tag

by Peter UhnÃ¡k

Hi, what would be the best approach to not generate space at the end of single tag? Right now it generates <item /> but I would like <item/> The space is added in XMLTagWriter>>writeEpilogue, but to "cleanly" change it I would need to * subclass tag writer * subclass xml writer * figure out how to provide different writer so it plays with XMLDocument>>printOn: and that certainly doesn't feel like a nice approach. Maybe this can be made configurable in similar fashion to indentation? Thanks, Peter

April 3, 2018

Re: [Pharo-users] Calypso error after clean up

by Denis Kudriashov

Also you can completely disable critiques: ClyCriticBrowserPlugin disable.ClyCriticEnvironmentPlugin disable.ClyNavigationEnvironment reset. And reopen browser. 2018-04-03 17:53 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > Try clean Calypso with "ClyNavigationEnvironment reset" and then reopen > browser. > If error will not disappear then problem could be related to the state of > RPackageOrganizer in your image. Do you see from debugger what is missing > in the package? > > 2018-04-03 16:59 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > >> Hello, >> >> I have this error when opening calypso on a P7 image, likely the critic >> stuff. The image was tightly cleaned. Likely one package was removed and it >> should not. Any idea which package family to look at >> >> Thanks >> >> Hilaire >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >

April 3, 2018

Re: [Pharo-users] Calypso error after clean up

by Denis Kudriashov

Hi. Try clean Calypso with "ClyNavigationEnvironment reset" and then reopen browser. If error will not disappear then problem could be related to the state of RPackageOrganizer in your image. Do you see from debugger what is missing in the package? 2018-04-03 16:59 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Hello, > > I have this error when opening calypso on a P7 image, likely the critic > stuff. The image was tightly cleaned. Likely one package was removed and it > should not. Any idea which package family to look at > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > >

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

I think doing something Ã la M4, to process macro in the BaselineOf files, but it will add confusion to the confusion. Now, in the bazaar repo I don't have release version number either. Le 03/04/2018 Ã 16:57, Thierry Goubier a Ã©critÂ : > Mine as well:( > > I still believe a "release" kind of script could help, associated with > a project: update the baselineOf, save everything with a nice commit, > tag the commit, done. > > I would need one for OSProcess, and for the GitFileTree-MergeDriver. > > But it's kind of specific to the way you package DrGeo, so no single > command would fit. > > Thierry -- Dr. Geo http://drgeo.eu

April 3, 2018

Calypso error after clean up

by Hilaire

Hello, I have this error when opening calypso on a P7 image, likely the critic stuff. The image was tightly cleaned. Likely one package was removed and it should not. Any idea which package family to look at Thanks Hilaire -- Dr. Geo http://drgeo.eu

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Thierry Goubier

2018-04-03 16:31 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Probably, but my hands are already full. Mine as well :( I still believe a "release" kind of script could help, associated with a project: update the baselineOf, save everything with a nice commit, tag the commit, done. I would need one for OSProcess, and for the GitFileTree-MergeDriver. But it's kind of specific to the way you package DrGeo, so no single command would fit. Thierry > > > > Le 03/04/2018 Ã 15:52, Thierry Goubier a Ã©crit : >> >> Couldn't you call a bazaar routine to get that information? >> >> Writing a specific method with the version number on each release is a >> bit of a pain, to have practised that before. >> Unless you write a release command that adds the code and do the >> necessary stuff to package the release. >> >> Thierry > > > -- > Dr. Geo > http://drgeo.eu > > >

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

Probably, but my hands are already full. Le 03/04/2018 Ã 15:52, Thierry Goubier a Ã©critÂ : > Couldn't you call a bazaar routine to get that information? > > Writing a specific method with the version number on each release is a > bit of a pain, to have practised that before. > Unless you write a release command that adds the code and do the > necessary stuff to package the release. > > Thierry -- Dr. Geo http://drgeo.eu

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Thierry Goubier

2018-04-03 15:25 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > I don't use github. I will just use a class method returning a version > number. Couldn't you call a bazaar routine to get that information? Writing a specific method with the version number on each release is a bit of a pain, to have practised that before. Unless you write a release command that adds the code and do the necessary stuff to package the release. Thierry > > Le 03/04/2018 Ã 14:14, Thierry Goubier a Ã©crit : >> >> Normally, you should do it via the repository url. If you use tags in >> your repository management and integration >> into Monticello (like filetree and gitfiletree), you can retrieve a >> branch or tag name by scanning the repository >> url: for example, github://XX/DrGeo:18.06/src. > > > -- > Dr. Geo > http://drgeo.eu > > >

April 3, 2018

Re: [Pharo-users] Howto BaselineOf

by Hilaire

I don't use github. I will just use a class method returning a version number. Le 03/04/2018 Ã 14:14, Thierry Goubier a Ã©critÂ : > Normally, you should do it via the repository url. If you use tags in > your repository management and integration > into Monticello (like filetree and gitfiletree), you can retrieve a > branch or tag name by scanning the repository > url: for example, github://XX/DrGeo:18.06/src. -- Dr. Geo http://drgeo.eu

April 3, 2018

Proper Monticello (with Iceberg integration) update

by Juraj Kubelka

Hi! What is the proper updated mechanism on projects stored on GitHub? To be more explicit, the script: Metacello new baseline: #DiscordSt; repository: 'github://JurajKubelka/DiscordSt/src'; load. With the Iceberg integration, it does not work if an older version is already in a Pharo image. Doing pull from the Iceberg UI neither works as the new version may have new packages and new external dependencies. Actually it is also tricky if the Iceberg integration is not involved. I use this script in such scenario: ``` UIManager default informUserDuring: [ :bar | bar label: 'Removing cached DiscordSt repository from github-cache'. bar current: 0. (FileLocator workingDirectory / 'github-cache' / 'JurajKubelka' / 'DiscordSt') ensureDeleteAll. bar label: 'Updating DiscordSt baseline definition'. bar current: 0.33. Iceberg enableMetacelloIntegration ifFalse: [ Gofer new url: 'github://JurajKubelka/DiscordSt/src' asZnUrl; package: 'BaselineOfDiscordSt'; load ]. bar label: 'Updating DiscordSt source files'. bar current: 0.66. Metacello new baseline: #DiscordSt; repository: 'github://JurajKubelka/DiscordSt/src'; onConflict: [:ex | ex allow]; load: #default. bar current: 1 ]. ``` I think I need a script that: 1. updates a local Iceberg repository (if exists) 2. loads new BaselineOfDiscordSt package version to a Pharo image 3. executes the Metacello script. How can I do properly the first two steps when Iceberg is involved? Thanks! Juraj

April 3, 2018