- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Vm-dev] Re: issue with large file path on windows

by Eliot Miranda

Thanks Nicolai, that's great! I'll merge in your changes. Which files do I need to look at? On Sat, Sep 12, 2015 at 8:00 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-09-10 21:31 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> >> Hi Nicolai, >> >> I'm a bit concerned that this is creating drift with the "official" >> Cog source base at http://www.squeakvm.org/svn/squeak/branches/Cog. >> Long filename support for win32 was recently added by Marcel Taumel in May >> of this year. Are you tracking that? How can we keep the sources >> harmonized? >> > > Ok, I removed all of my code again and merged with sqWin32Directory.c and > sqWin32FilePrims.c from the official cog source. > I left only pharos additions for the fileattributes (posixpermissions) > this should make it easier to merge which the > squeak vm main branch (wrapped with pharo vm ifdefs). > > github branch: > https://github.com/nicolaihess/pharo-vm/tree/harmonize_win_file_plugin > I'll create a push request. > > > nicolai > > > >> >> On Sun, Aug 23, 2015 at 4:44 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> For those who had problems with pharo on windows and github based >>> repositories, >>> I built a windows vm with support for long paths: >>> >>> >>> https://drive.google.com/file/d/0B8yEahnuIem2bmxwdzJuUXFxVGM/view?usp=shari… >>> >>> >>> For browsing directories with large paths (FileList or Inspect), >>> you may need one additional change in the image (But I am not really >>> sure about that) : >>> >>> DiskStore>>initialize >>> super initialize. >>> maxFileNameLength := Smalltalk vm maxFilenameLength ifNil: [ 32767 ]. >>> >>> >>> please test and give feedback. >>> >>> This wasn't as easy as I thought, and I had to make some more changes >>> for the file permissions (the stat-functions don't work for files with >>> long paths). >>> Please test other file/folder operations. >>> >>> >>> nicolai >>> >>> >>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> >> > > -- _,,,^..^,,,_ best, Eliot

Sept. 14, 2015

Re: [Pharo-dev] Metacello load script won't update the configuration

by Dale Henrichs

Uko, The `get` command is used to load a fresh copy of the ConfigurationOf or BaselineOf so the following should do the trick: Metacello new smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo40'; configuration: 'QualityAssistant'; get; load I make the loading of the BaselineOf and ConfigurationOf explicit so that the developer can control when and if they want a new copy of the BaselineOf or ConfigurationOf. For github urls like github://project/user/project, the `get` command causes the system to invalidate the cache directory so that on the next load, the github cache for the project is freshly downloaded so that you get the latest version of the BaselineOf ... Dale On 09/14/2015 01:49 PM, Yuriy Tymchuk wrote: > Hi, > > when you use a script like > > Metacello new > smalltalkhubUser: 'Pharo' > project: 'MetaRepoForPharo40'; > configuration: 'QualityAssistant'; > load > > and you already have the configuration package loaded, the script is > not updating the configuration itself. As the result you cannot update > to a newer version. Is there a special expression that has to be used > to update the configuration package? If not, maybe it does make sense > to update the configuration before loading it? > > Cheers! > Uko

Sept. 14, 2015

Metacello load script won't update the configuration

by Yuriy Tymchuk

Hi, when you use a script like Metacello new smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo40'; configuration: 'QualityAssistant'; load and you already have the configuration package loaded, the script is not updating the configuration itself. As the result you cannot update to a newer version. Is there a special expression that has to be used to update the configuration package? If not, maybe it does make sense to update the configuration before loading it? Cheers! Uko

Sept. 14, 2015

Re: [Pharo-dev] PID of VM ?

by Sven Van Caekenberghe

> On 14 Sep 2015, at 18:46, David T. Lewis <lewis(a)mail.msen.com> wrote: > >> On Mon, Sep 14, 2015 at 8:25 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >>> >>>> On 14 Sep 2015, at 14:21, David T. Lewis <lewis(a)mail.msen.com> wrote: >>>> >>>> >>>> No, OSProcess should not be included in the image. It is intended to be >>>> an external package. >>> >>> mmmÃ¢ÂÂ¦ we want to include it as more and more people requires it and we >>> can profit from having it in the image (same as FFI). >>> why do you think it should be external? >> >> We should distinguish between having it traditionally-in-Image where >> that is the only place it exists and fixes are integrated, and the >> current trend (e.g. in-Image Glamorous Tools) where fixes are >> integrated "upstream" into an external package >> > > Yes, that is what I meant. > > Dave Several packages are in that situation: Zinc, STON, FUEL, ... it works quite well.

Sept. 14, 2015

Re: [Pharo-dev] PID of VM ?

by David T. Lewis

> On Mon, Sep 14, 2015 at 8:25 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >>> On 14 Sep 2015, at 14:21, David T. Lewis <lewis(a)mail.msen.com> wrote: >>> >>> >>> No, OSProcess should not be included in the image. It is intended to be >>> an external package. >> >> mmmÃ¢ÂÂ¦ we want to include it as more and more people requires it and we >> can profit from having it in the image (same as FFI). >> why do you think it should be external? > > We should distinguish between having it traditionally-in-Image where > that is the only place it exists and fixes are integrated, and the > current trend (e.g. in-Image Glamorous Tools) where fixes are > integrated "upstream" into an external package > Yes, that is what I meant. Dave

Sept. 14, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Martin Dias

On Tue, Sep 8, 2015 at 12:29 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > >> On 08 Sep 2015, at 11:03 , Martin Dias <tinchodias(a)gmail.com> wrote: >> >> On Sat, Sep 5, 2015 at 1:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> The same for the ]lang[ tag (see issue 15750) >> >> Ok. But I still don't know how to add a url to a method's source code >> or comment from the UI. >> >> I mean, people with a non-English keyboard can produce source code >> with ]lang[, but how can I produce a ]style[ ? >> >> MartÃn > > The whole mechanism is quite broken in Pharo4 upwards: Not sure what to do in Pharo: parse the Text or just ignore the ]style[, but at least file-in should not raise an error. I reported it: https://pharo.fogbugz.com/f/cases/16575/CodeImporter-doesn-t-parse-style-ch… MartÃn

Sept. 14, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50323 Home: https://github.com/pharo-project/pharo-core

Sept. 14, 2015

[pharo-project/pharo-core] 309117: 50323

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 30911717587a2fa15bc22339ddd55620746dbbdc https://github.com/pharo-project/pharo-core/commit/30911717587a2fa15bc22339… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-14 (Mon, 14 Sep 2015) Changed paths: M AST-Core.package/BISimpleFormatter.class/instance/initialization/initialize.st M AST-Core.package/RBMethodNode.class/instance/private/reformatSource.st M AST-Core.package/RBParseTreeSearcher.class/class/private/buildSelectorString_.st M AST-Core.package/RBParser.class/instance/accessing/parseLiterals_.st M AST-Core.package/RBParser.class/instance/private-parsing/parseLiteralArray.st M AST-Core.package/RBParser.class/instance/private-parsing/parseLiteralByteArray.st M AST-Core.package/RBScanner.class/instance/accessing/contents.st M AST-Core.package/RBScanner.class/instance/initialize-release/on_.st M NautilusCommon.package/NautilusClassSelected.class/definition.st R NautilusCommon.package/NautilusClassSelected.class/instance/accessing/selectedClass.st R NautilusCommon.package/NautilusClassSelected.class/instance/accessing/selectedClass_.st R NautilusCommon.package/NautilusClassSelected.class/instance/compatibility/itemClass.st M NautilusCommon.package/NautilusMethodSelected.class/definition.st R NautilusCommon.package/NautilusMethodSelected.class/instance/accessing/selectedMethod.st R NautilusCommon.package/NautilusMethodSelected.class/instance/accessing/selectedMethod_.st R NautilusCommon.package/NautilusMethodSelected.class/instance/compatibility/method.st M NautilusCommon.package/NautilusPackageSelected.class/definition.st R NautilusCommon.package/NautilusPackageSelected.class/instance/accessing/selectedPackage.st R NautilusCommon.package/NautilusPackageSelected.class/instance/accessing/selectedPackage_.st R NautilusCommon.package/NautilusPackageSelected.class/instance/compatibility/package.st M NautilusCommon.package/NautilusProtocolSelected.class/definition.st R NautilusCommon.package/NautilusProtocolSelected.class/instance/accessing/selectedProtocol.st R NautilusCommon.package/NautilusProtocolSelected.class/instance/accessing/selectedProtocol_.st R NautilusCommon.package/NautilusProtocolSelected.class/instance/compatibility/category.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/README.md A NautilusCommon.package/NautilusSelectionAnnouncement.class/definition.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedClass.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedClass_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedMethod.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedMethod_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedPackage.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedPackage_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedProtocol.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedProtocol_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/category.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/itemClass.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/method.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/package.st A Polymorph-Widgets.package/MorphicUIManager.class/instance/display/showWaitCursorWhile_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50322.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50323.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50322.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50323.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Changes.package/ChangeRecord.class/instance/initialization/fileIn.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOut.st A UIManager.package/UIManager.class/instance/display/showWaitCursorWhile_.st Log Message: ----------- 50323 16566 Replace WriteStream with writeStream message send in AST-Core https://pharo.fogbugz.com/f/cases/16566 16556 Nautilus selection announcements intersect as they are in a hierarchy https://pharo.fogbugz.com/f/cases/16556 16539 System-Changes and Compression should not depend on Graphics-Display Objects https://pharo.fogbugz.com/f/cases/16539 http://files.pharo.org/image/50/50323.zip

Sept. 14, 2015

Re: [Pharo-dev] Querying hierarchical entities in Voyage

by Yuriy Tymchuk

Thanks Norbert! > On 14 Sep 2015, at 17:31, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 14.09.2015 um 15:41 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >> Hi, >> >> how can I query all the objects from a hierarchy? Should a do separate query for each subclass and then concatenate the results? Is there a more efficient solution? >> > You can put something like that in your base class > > mongoContainer > <mongoContainer> > ^ VOMongoContainer new > collectionName: 'user'; > yourself > > So every subclass will be stored in the user collection as well. If you query on the base class you will get all subclasses as well. > > Norbert > >> Also what is the place to read about Voyage? >> > > >

Sept. 14, 2015

Re: [Pharo-dev] Querying hierarchical entities in Voyage

by Norbert Hartl

> Am 14.09.2015 um 15:41 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > Hi, > > how can I query all the objects from a hierarchy? Should a do separate query for each subclass and then concatenate the results? Is there a more efficient solution? > You can put something like that in your base class mongoContainer <mongoContainer> ^ VOMongoContainer new collectionName: 'user'; yourself So every subclass will be stored in the user collection as well. If you query on the base class you will get all subclasses as well. Norbert > Also what is the place to read about Voyage? >

Sept. 14, 2015