June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] What happened to smallharbour ?

by garduino

Sorry, this means that the problems I reported in February are solved? I don't tried, honestly I remainded awaiting your comments. Cheers. -- View this message in context: http://forum.world.st/What-happened-to-smallharbour-tp4635752p4635787.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 20, 2012

Re: [Pharo-project] How to correctly remove a package for everywhere?

by Chris Cunningham

In Monitcello days (and browser), there is Delete working package, and Unload package. I suspect deletePackageNamed: is all about removing the idea of the package, but not the code (as you found) - just making the code part of the image and not a package. You want something like unloadPackage: or #unloadPackage to remove the code (and package) from the system. Assuming that is still there, that is (I don't have a version 2.0 yet). Wouldn't your drive to package everything make you want to guard against the deletePackageNamed: behaviour? Only delete it if there is no code associated to the package, otherwise complain somehow. -Chris

June 20, 2012

Re: [Pharo-project] How to correctly remove a package for everywhere?

by Fernando Olivero

Seems that removing a package does not imply removing the included classes?Maybe this should be changed? With RPackage is understandable, since its just a layer on top of the system.You have to explicitly register/deregister packages. Fernando On Wed, Jun 20, 2012 at 10:24 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > well, I don't know what the hell happened, but a workaround I think it is > > DataStream removeFromSystem. > RPackageOrganizer Â default unregisterPackageNamed: #'System-Object Storage'. > > On Wed, Jun 20, 2012 at 10:19 PM, Mariano Martinez Peck <marianopeck(a)gmail.com<mailto:marianopeck@gmail.com>> wrote: > So removing 'System-Object Storage' didn't work. I did: > > ScriptLoader new deletePackageNamed: 'System-Object Storage'. > > Now the MCWorkingCopy is removed (I don't see the package in Monticello Browser), but I can still browse the class DataStream, and the package is available from Nautilus. > > Now if I do: > > RPackageOrganizer Â default unregisterPackageNamed: #'System-Object Storage' > > I don't see the package in Nautilus, but the class "DataStream" is still alive. I can do "DataStream name -> #DataStream" ..et...when I browse it with Nautilus I don't see the class but the category _UnpackagedPackage.. > > so...how the hell can I remove this package and class from everywhere in the system? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 20, 2012

Re: [Pharo-project] How to correctly remove a package for everywhere?

by Mariano Martinez Peck

well, I don't know what the hell happened, but a workaround I think it is DataStream removeFromSystem. RPackageOrganizer default unregisterPackageNamed: #'System-Object Storage'. On Wed, Jun 20, 2012 at 10:19 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > So removing 'System-Object Storage' didn't work. I did: > > ScriptLoader new deletePackageNamed: 'System-Object Storage'. > > Now the MCWorkingCopy is removed (I don't see the package in Monticello > Browser), but I can still browse the class DataStream, and the package is > available from Nautilus. > > Now if I do: > > RPackageOrganizer default unregisterPackageNamed: #'System-Object Storage' > > I don't see the package in Nautilus, but the class "DataStream" is still > alive. I can do "DataStream name -> #DataStream" ..et...when I browse it > with Nautilus I don't see the class but the category _UnpackagedPackage.. > > so...how the hell can I remove this package and class from everywhere in > the system? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

June 20, 2012

[Pharo-project] How to correctly remove a package for everywhere?

by Mariano Martinez Peck

So removing 'System-Object Storage' didn't work. I did: ScriptLoader new deletePackageNamed: 'System-Object Storage'. Now the MCWorkingCopy is removed (I don't see the package in Monticello Browser), but I can still browse the class DataStream, and the package is available from Nautilus. Now if I do: RPackageOrganizer default unregisterPackageNamed: #'System-Object Storage' I don't see the package in Nautilus, but the class "DataStream" is still alive. I can do "DataStream name -> #DataStream" ..et...when I browse it with Nautilus I don't see the class but the category _UnpackagedPackage.. so...how the hell can I remove this package and class from everywhere in the system? thanks -- Mariano http://marianopeck.wordpress.com

June 20, 2012

Re: [Pharo-project] What happened to smallharbour ?

by laurent laffont

Hi Mariano, it's running at least and I have a few websites deployed :) But no development for months and time/motivation/whatever to continue development. Documentation / project: http://www.smallharbour.org/ A test server: http://alpha.smallharbour.org/ A site in production: http://www.cara74.org/ If you want to dig into it I will help (and I think Romain too) Laurent On Wed, Jun 20, 2012 at 9:08 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Is it alive? was it abandoned? does it work? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > >

June 20, 2012

[Pharo-project] What happened to smallharbour ?

by Mariano Martinez Peck

Is it alive? was it abandoned? does it work? thanks -- Mariano http://marianopeck.wordpress.com

June 20, 2012

[Pharo-project] red cross during updates

by StÃ©phane Ducasse

I identified the causes now I do not know the solution http://code.google.com/p/pharo/issues/detail?id=6099 Stef

June 20, 2012

Re: [Pharo-project] StartupPreferences hardcoded again :(

by Camillo Bruni

On 2012-06-20, at 18:10, Mariano Martinez Peck wrote: > Hi. As part of my changes (and Ben Coman) we removed the hardcoded > preferences directory. > Previously we had: > > preferencesRootFolder > > ^ (self default ascendingSearchForDirectory: self > configFolderLocalName) directoryNamed: 'pharo'. > > Now it is hardcoded again: > > FileLocator preferences / 'pharo' / 'general'. > > meaning I have an error because Path / 'Users' / 'mariano' / 'Library' / > 'Preferences' / 'pharo' / 'general' > does not exist.. I don't have that folder either and it works :) so I assume that you're not running under the latest VM :) Actually we just rewrote it to use the new filesystem, maybe I accidentally reset your changes. :)

June 20, 2012

[Pharo-project] [update 2.0] #20145

by Esteban Lorenzano

20145 ----- Issue 5945: Nice packaging for Text stuff http://code.google.com/p/pharo/issues/detail?can=2&q=5945

June 20, 2012