[Pharo-users] Proper Monticello (with Iceberg integration) update

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

Re: [Pharo-users] Howto BaselineOf

Hi Thierry, Does not work either. PharoDebug.log is not updated with this error. I paste bellow the stack from the debugger (but there is a no attribute values). Hilaire MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: [ | references

Re: [Pharo-users] Howto BaselineOf

Hi Hilaire, try Metacello new baseline: 'DrGeo'; repository: 'tonel://', SmalltalkImage current imageDirectory pathString, '/src'; load Thierry 2018-04-03 10:34 GMT+02:00 Hilaire : > Hi, > > I have this enclosed BaselineOfDrGeo which I think contains mostly all I

Re: [Pharo-users] Howto BaselineOf

Ok, adding the package names was needed in the baseline and resolved the remaining errors: spec package: 'DrGeoII-core'; package: 'DrGeoII-Polymorph'; etc. Now I would like to insert in the BaselineOf a version number more meaningfull than I want to extract from 'BaselineOfDrGeo project

Re: [Pharo-users] Howto BaselineOf

Hi Hilaire, 2018-04-03 12:40 GMT+02:00 Hilaire : > Ok, adding the package names was needed in the baseline and resolved the > remaining errors: > > spec package: 'DrGeoII-core'; package: 'DrGeoII-Polymorph'; etc. > > Now I would like to insert in the BaselineOf a version number

Re: [Pharo-users] Howto BaselineOf

Moving the BaselineOfDrGeo out of the ConfigurationOfDrGeo package in the file based tonel helps to get over this error. More error followed but need to be examined. Le 03/04/2018 à 11:42, Hilaire a écrit : Does not work either. PharoDebug.log is not updated with this error. I paste bellow

Re: [Pharo-users] unsolicited package-cache use

Thanks for the update. I will see, I don't use GIT and will not as drgeo code is on Launchpad and the CVS is Bazaar. Launchpad comes with handing tooling to ease the work of translators. Hilaire Le 03/04/2018 à 00:01, Thierry Goubier a écrit : Hi Hilaire, a BaselineOf is the same as a

Re: [Pharo-users] Howto BaselineOf

2018-04-03 15:25 GMT+02:00 Hilaire : > 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

Re: [Pharo-users] Howto BaselineOf

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

Re: [Pharo-users] Howto BaselineOf

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

Re: [Pharo-users] Howto BaselineOf

2018-04-03 16:31 GMT+02:00 Hilaire : > 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

Re: [Pharo-users] Howto BaselineOf

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

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

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

Re: [Pharo-users] Is Tonel known to eat code?

hi, I think Tonel will not process correctly a method name with a dot at the end (which is not valid smalltalk, just a glich in the compiler ;) if you remove it, it will be fine. Esteban > On 3 Apr 2018, at 18:13, Hilaire wrote: > > I have method disappearing in my tonel

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

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 : > Hi. > > Try clean Calypso with "ClyNavigationEnvironment

[Pharo-users] configurable space in XML Writer tag

Hi, what would be the best approach to not generate space at the end of single tag? Right now it generates but I would like 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

Re: [Pharo-users] Is Tonel known to eat code?

Oh man I prefer this :) But it is strange because I have been doing build since weeks from tonel repo, and this point seems to have been there since years, or maybe some mix up with the package cache, oh but I was paying attention to empty it before... Lost in confusion. Any way now using the

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

The Manifest- packages were missing. It resolves the problem. Le 03/04/2018 à 17:53, Denis Kudriashov a écrit : 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

Re: [Pharo-users] Black screen on Mac OSX

No I am not defining such extra method. I more or less packaged blindly a modified universal VMs for P4. I was able to test it on linux and windows (throught wine), but not on Mac osx. I am doing right now the same for P7 based image, but not there yet. Le 03/04/2018 à 22:39, Stephane

Re: [Pharo-users] Black screen on Mac OSX

Hilaire I looked at the other bug. And I would like to know if you are defining extra methods on SQSurfaceDispatch class. I do not get why I got an error (may be this is related to the source management. Stef On Tue, Apr 3, 2018 at 9:56 PM, Stephane Ducasse wrote: > Hi

Re: [Pharo-users] To be there or not to be there

On 4 April 2018 at 05:06, Hilaire wrote: > Hello, > > I have re-organized the packages and classes in DrGeo with Calypso. An now > I come to a situation where methods seems to be there without been there. > > For example DrGeoWindow>>newTable: methods, > > - Calypso can browse

[Pharo-users] Howto BaselineOf

Hi, I have this enclosed BaselineOfDrGeo which I think contains mostly all I need. How should I load it? This code bellow does not work: (BaselineOfDrGeo project version: #development) load. By the way the PharoDebug log file is not recorded along the image, but at the user root directory.