- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to manage GitFileTree and being integrated in-image (QualityAssistant example?)

by Thierry Goubier

2016-01-22 17:22 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Fri, Jan 22, 2016 at 11:50 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> Hi Mariano, >> >> this is a common question for external projects integrated inside the >> Pharo image. And we have an issue with version numbers, but let's try to >> keep that separate. >> >> Fixes to the code of external projects integrated inside Pharo should be >> done upstream (on the external project itself), not in the Pharo image. >> This is what is currently happening with the GT tools, NeoJSON, Zinc, and >> probably a few more. So, as a maintainer of such a projects in github, say, >> you can ask people to create issues on your project, pull requests and the >> like, and this is the only way bugs found in Pharo in your release project >> should be corrected. Then, everytime a new version of the Pharo image is >> built, a version of your project is integrated; and you can add an issue to >> update your project to a newer version inside Pharo. >> > > Well, that covers A PART of the problem. If someone finds a bug or > whatever in MY project, then your workflow sounds perfect. > Now...consider internal refactors of Pharo that affects multiple projects. > For example few months ago, someone changes all senders of #instVarNames to > #instanceVariabls (or something like that...I don't remember the exact > change but something like that). As part of those senders, there was Fuel. > So when that SLICE was integrated (with multiple packages as dependencies > of the SLICE), Fuel package was one of them. > > So what should be the path in this case: > > 1) Ask the poor guy that make the slice to also do the fork, git clone, > install gitfiletree, commit, push and make PR ... > Hum, takes about: - 1 click or two on github for the fork - 1 click on the configuration manager for gitfiletree - 4 lines of metacello for remote clone + repository - 3 clicks and a bit of text for the commit in the fork - two clicks for the push to github - 2 or 3 clicks for the pull request Soon (or even already now?), Skip Github code would allow that without git/gitfiletree. But in github world, you would need a fork anyway. > 2) Myself (as the developer of the tool) get notified when my package gets > changed and then, I take care of doing a diff and manaully "port" the fix > to my upstream project? > Probably this one. Technically, it is easy to: get the latest image; get the gitfiletree repository; create a branch at the previous stable version of the project; save the changed packages into that branch; then decide (git merge?) those changes into either a new stable version or on a development branch. Git will take care of the difference between your new stuff and the stuff changed in Pharo, and merge properly unless both sides have changed the same method / line in a method. I don't expect this sort of changes to occur very often. As you say, this is a particular use case, with a large number of packages changed, so I would consider that a rare occurrence for which I don't have to specially optimize the process, just to have it possible. Smaller fixes should be done the 1) way. > In either case, just to confirm, we do NOT do fetch/push because of the > versions problem right? > I mean...it will be either me or another guy (the guy that created the > issue), but one of us will finally end up putting the "changes" (not a MC > version) in the upstream whatever ways are taking for that (via PR or > whatever) ? > Yes, but the push will be a MC version anyway? I don't understand; using git means that you can just save and push versions, and git will determine what the diff is... > (Was I clear with that description? Feel free to ask or correct me :)) >> >> Now, about the package versions. There is an issue with metadata-less >> mode and a few quirks about the way Metacello check versions to upgrade >> packages, and the issue is open. Two ways forward are possible: David >> Allouche pointed one by saying ordering between versions (without checking >> the numbers) can be resolved by checking if one is an ancestor of the >> other... and the other is that, with Skip work on the github api, it >> becomes possible(*) to retrieve the version info from github without git >> and avoid those -Cypress.1. >> >> > OK that would very cool. > Yes, I think so too. Thierry

Jan. 22, 2016

Re: [Pharo-dev] [ANN] Pharo bootstrap

by Eliot Miranda

Hi Gille, I'll respond to the two object spaces message next, but saw the point about AST interprretation and I have a suggestion On Wed, Jan 20, 2016 at 4:29 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > On 20 ene 2016, at 9:08 a.m., Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > > Hi Pavel, > > Le 19 janv. 2016 Ã 19:53, Pavel Krivanek a Ã©crit : > > Hi, > > amazing! Do you have any idea how to speed up it? The bootstrap process is > now running on my machine about one and half hour and it is still far from > finish. > > > The process is indeed far too long (takes around 10 hours) on the CI > server. > Reasons are: > - we use a stack interpreter VM > - we modified it and is a bit slower than a classical stack VM > > > Not quite so. My measurements did not show thatâ¦ But I can understand the > feeling as the StackVM is in general half as fast as the CogVM, which is > the VM we are used to use since years. > > - we use AST interpretation to build the bootstrap and it is very slow. > Guille already did some speed improvements by avoiding to interpret loops > by example. > > I did not yet spend time on this point because I first wanted to have > something working. > Definitely, this problem will be tackled when we will put in production > the bootstrap. > > > We should really measure because I see three main aspects: > > 1) class creation (executes the class builder using AST interpretation) > 2) method compilation > 3) method installation (using AST interpretation to respect trait copying) > > My feeling (from what I observe only) is that most of the time is consumed > in 2) and 3), and that specially it is in 3). > The AST interpretation seems to me easily replaced by bytecode interpretation that should be much faster. If you added a subclass of Context, say OzInstallationInterpreter, this could override all methods that make direct inst var access, such as Context methods for instruction decoding pushReceiverVariable: offset "Simulate the action of bytecode that pushes the contents of the receiver's instance variable whose index is the argument, index, on the top of the stack." self push: (self object: self receiver instVarAt: offset + 1) with ones that map back from inst var offsets to inst var names, e.g. OzInstallationInterpreter methods for instruction decoding pushReceiverVariable: offset "Simulate the action of bytecode that pushes the contents of the receiver's instance variable whose index is the argument, index, on the top of the stack. Override to ensure that the offset of the named inst var is used." self push: (self object: self receiver instVarNamed: (self mapInstVarOffsetToName: offset + 1)) You might even be able to do this just in object:instVarAt:. But if you move away from AST interpretation you save both the overhead of interpreting the AST /and/ the cost of parsing the method to the AST, which I presume is significant, and can simply use the methods extant in the system. > And I particularly want to see how the growing of collections perform. > > > Cheers, > Christophe > > > Cheers, > -- Pavel > > 2016-01-19 15:29 GMT+01:00 Christophe Demarey <christophe.demarey(a)inria.fr > >: > >> Hi all, >> >> In case you do not know, we work on bootstrapping Pharo, i.e. create a >> Pharo image from sources, not based on a previous image (well, we use a >> pharo image to produce it but no code / state from it). >> >> This process will allow to define a minimal Pharo kernel (currently 52 >> packages but we could have it far smaller) and to modularize the whole >> image (currently packages have too much dependencies on packages already >> loaded into the image). >> The bootstrap process also allows to write down the recipe to initialize >> a new image from scratch (some code is missing in the image or is wrong). >> In addition, I think we will clean a lot of historical objects that are not >> used anymore. >> >> With the amazing work done by Guillermo Polito during his Phd (around >> Espell, Oz): >> https://guillep.github.io/files/publications/Poli15Thesis.pdf, *we >> succeeded to get a first prototype of a bootstraped Pharo 5 image (from >> 5.392)*. >> This prototype is able to run an eval command line handler and to log >> output / errors. Not all classes are yet initialized and you cannot yet >> save / restart this image but it is a big step forward. >> It is a 4 mb image (could be half the size without unicode data). You can >> download it at: >> http://chercheurs.lille.inria.fr/~demarey/pmwiki/pub/pharo-bootstrap/pharo-… >> . >> >> Next steps are to have a bootstrapped image fully working, then to load >> packages on top of it (like network, sunit) to produce a minimal image. >> Then, we need to implement an Oz VM on top of Spur. >> After that, we need to work on a reliable way to build the bootstrap (not >> too sensitive to changes in the image). >> >> Christophe. >> >> ------- >> demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ >> ../pharo bootstrap.image --no-default-preferences eval "1 + 1" >> 2 >> demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ >> ../pharo bootstrap.image --no-default-preferences eval "'a' , 'b'" >> 'ab' >> demarey@193-51-236-143:~/dev/rmod/bootstrap/bootstrap-2016-01-19$ >> ../pharo bootstrap.image --no-default-preferences eval "1 / 0" >> ZeroDivide >> SmallInteger>>/ >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> OpalCompiler(AbstractCompiler)>>evaluate: >> SmalltalkImage>>evaluate: >> >> EvaluateCommandLineHandler>>no (source is Undeclared) >> no source in EvaluateCommandLineHandler>>evaluate: in Block: no source >> BlockClosure>>on:do: >> EvaluateCommandLineHandler>>evaluate: >> EvaluateCommandLineHandler>>evaluateArguments >> EvaluateCommandLineHandler>>activate >> EvaluateCommandLineHandler class(CommandLineHandler class)>>activateWith: >> >> BasicCommandLineHandler>>no (source is Undeclared) >> no source in >> PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: in >> Block: no source >> BlockClosure>>on:do: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand: >> PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand >> PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument: >> >> BasicCommandLineHandler>>no (source is Undeclared) >> no source in PharoCommandLineHandler(BasicCommandLineHandler)>>activate >> in Block: no source >> BlockClosure>>on:do: >> PharoCommandLineHandler(BasicCommandLineHandler)>>activate >> PharoCommandLineHandler>>activate >> PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: >> >> PharoCommandLineHandler class>>no (source is Undeclared) >> no source in PharoCommandLineHandler class>>activateWith: in Block: no >> source >> NonInteractiveUIManager(UIManager)>>defer: >> PharoCommandLineHandler class>>activateWith: >> no source in BasicCommandLineHandler>>activateSubCommand: in Block: no >> source >> BlockClosure>>on:do: >> BasicCommandLineHandler>>activateSubCommand: >> BasicCommandLineHandler>>handleSubcommand >> BasicCommandLineHandler>>handleArgument: >> no source in BasicCommandLineHandler>>activate in Block: no source >> >> SmallInteger>>no (source is Undeclared) >> >> UndefinedObject>>no (source is Undeclared) >> >> AbstractCompiler>>no (source is Undeclared) >> >> SmalltalkImage>>no (source is Undeclared) >> >> BlockClosure>>no (source is Undeclared) >> >> EvaluateCommandLineHandler>>no (source is Undeclared) >> >> EvaluateCommandLineHandler>>no (source is Undeclared) >> >> CommandLineHandler class>>no (source is Undeclared) >> >> BasicCommandLineHandler>>no (source is Undeclared) >> >> BasicCommandLineHandler>>no (source is Undeclared) >> >> PharoCommandLineHandler>>no (source is Undeclared) >> >> UIManager>>no (source is Undeclared) >> >> UndefinedObject>>no (source is Undeclared) >> >> CommandLineUIManager>>no (source is Undeclared) >> >> SmalltalkImage>>no (source is Undeclared) >> >> DelayMicrosecondScheduler>>no (source is Undeclared) >> >> BlockClosure>>no (source is Undeclared) >> >> SmalltalkImage>>no (source is Undeclared) >> >> WeakArray class>>no (source is Undeclared) >> >> >> ps: source cannot be displayed because there is no formatter available in >> the bootstrap >> >> > > > -- _,,,^..^,,,_ best, Eliot

Jan. 22, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] fef09a: 50540

by Christophe Demarey

Le 22 janv. 2016 Ã 17:08, Ben Coman a Ã©crit : > On Fri, Jan 22, 2016 at 11:26 PM, GitHub <noreply(a)github.com> wrote: >> Branch: refs/heads/5.0 >> Home: https://github.com/pharo-project/pharo-core >> Commit: fef09a7c252f92e255c5053927295a61d16b8395 >> https://github.com/pharo-project/pharo-core/commit/fef09a7c252f92e255c50539… >> Author: Jenkins Build Server <board(a)pharo-project.org> >> Date: 2016-01-22 (Fri, 22 Jan 2016) > >> Log Message: >> ----------- >> 50540 >> Pharo >> >> http://files.pharo.org/image/50/50540.zip > > What are the issue numbers associated with this integration?? Case 17446: Add registration/unregistration to/from session manager

Jan. 22, 2016

Re: [Pharo-dev] How to manage GitFileTree and being integrated in-image (QualityAssistant example?)

by Mariano Martinez Peck

On Fri, Jan 22, 2016 at 11:50 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Hi Mariano, > > this is a common question for external projects integrated inside the > Pharo image. And we have an issue with version numbers, but let's try to > keep that separate. > > Fixes to the code of external projects integrated inside Pharo should be > done upstream (on the external project itself), not in the Pharo image. > This is what is currently happening with the GT tools, NeoJSON, Zinc, and > probably a few more. So, as a maintainer of such a projects in github, say, > you can ask people to create issues on your project, pull requests and the > like, and this is the only way bugs found in Pharo in your release project > should be corrected. Then, everytime a new version of the Pharo image is > built, a version of your project is integrated; and you can add an issue to > update your project to a newer version inside Pharo. > Well, that covers A PART of the problem. If someone finds a bug or whatever in MY project, then your workflow sounds perfect. Now...consider internal refactors of Pharo that affects multiple projects. For example few months ago, someone changes all senders of #instVarNames to #instanceVariabls (or something like that...I don't remember the exact change but something like that). As part of those senders, there was Fuel. So when that SLICE was integrated (with multiple packages as dependencies of the SLICE), Fuel package was one of them. So what should be the path in this case: 1) Ask the poor guy that make the slice to also do the fork, git clone, install gitfiletree, commit, push and make PR ... 2) Myself (as the developer of the tool) get notified when my package gets changed and then, I take care of doing a diff and manaully "port" the fix to my upstream project? In either case, just to confirm, we do NOT do fetch/push because of the versions problem right? I mean...it will be either me or another guy (the guy that created the issue), but one of us will finally end up putting the "changes" (not a MC version) in the upstream whatever ways are taking for that (via PR or whatever) ? > > (Was I clear with that description? Feel free to ask or correct me :)) > > Now, about the package versions. There is an issue with metadata-less mode > and a few quirks about the way Metacello check versions to upgrade > packages, and the issue is open. Two ways forward are possible: David > Allouche pointed one by saying ordering between versions (without checking > the numbers) can be resolved by checking if one is an ancestor of the > other... and the other is that, with Skip work on the github api, it > becomes possible(*) to retrieve the version info from github without git > and avoid those -Cypress.1. > > OK that would very cool. > Thierry > > * There is a bit of code to write, of course, but most of it is reusing > what already exists inside Skip github and GitFileTree. > > 2016-01-22 14:33 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> Hi guys, >> >> Let's say there is a project which is being build with metadata-less >> GitFileTree. There is a BaselineOf and a ConfigurationOf which work >> correctly. And ConfigurationOf can perfectly have fixed "versions" that >> could be, at some point, integrated in Pharo. >> >> Let's say I release version 1.0 which is INTEGRATED inside Pharo. When >> Pharo image is build, it uses ConfigurationOfMyApp to load the code and so >> there will be NO history of versions (cypress.1). >> >> Now, as Pharo goes on, there may be changes to that project as part of >> refactors or whatever that happens in-image. So in one months from now, >> Pharo may have a "newer" code than the originally released 1.0. Let's say >> that for the package MyAppPackage were only 3 commits in those 2 months. >> >> At the same time, I have continue working with my project, and I am ready >> to publish 1.1. >> >> Question is.... how do I bring Pharo changes to my own place? >> >> 1) Fetching (from Pharo repo) and pushing to my GitFileTree only the >> versions during those 2 months? I doubt this will work as crappy >> Monticello numbers could have collisions, right? >> >> 2) Doing a poor man diff and cherry picking changes from Pharo repo and >> manually apply them to my own repo? In this case, the "3 commits" of those >> 2 months will be lost as from git history version. >> >> Is there a project doing this?? I know QualityAssistant is close, but he >> does not use metadata-less GitFileTree I think...so I am not sure. >> >> Thoughts? >> >> Thanks! >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

Jan. 22, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] fef09a: 50540

by Ben Coman

On Fri, Jan 22, 2016 at 11:26 PM, GitHub <noreply(a)github.com> wrote: > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: fef09a7c252f92e255c5053927295a61d16b8395 > https://github.com/pharo-project/pharo-core/commit/fef09a7c252f92e255c50539… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2016-01-22 (Fri, 22 Jan 2016) > Log Message: > ----------- > 50540 > Pharo > > http://files.pharo.org/image/50/50540.zip What are the issue numbers associated with this integration?? cheers -ben

Jan. 22, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 22, 2016

[pharo-project/pharo-core] fef09a: 50540

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: fef09a7c252f92e255c5053927295a61d16b8395 https://github.com/pharo-project/pharo-core/commit/fef09a7c252f92e255c50539… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-22 (Fri, 22 Jan 2016) Changed paths: M AST-Core.package/ASTCache.class/class/class initialization/initialize.st A AST-Core.package/ASTCache.class/class/class initialization/release.st R Balloon.package/ShortIntegerArray.class/class/initialization/initialize.st R Balloon.package/ShortIntegerArray.class/class/initialization/startUp.st R Balloon.package/ShortIntegerArray.class/class/initialization/swapShortObjects.st A Balloon.package/ShortIntegerArray.class/class/initialize-release/initialize.st A Balloon.package/ShortIntegerArray.class/class/initialize-release/release.st A Balloon.package/ShortIntegerArray.class/class/initialize-release/swapShortObjects.st A Balloon.package/ShortIntegerArray.class/class/system startup/startUp.st R Collections-Strings.package/Symbol.class/class/access/allSymbols.st R Collections-Strings.package/Symbol.class/class/access/selectorsContaining_.st R Collections-Strings.package/Symbol.class/class/access/thatStartsCaseSensitive_skipping_.st R Collections-Strings.package/Symbol.class/class/access/thatStarts_skipping_.st A Collections-Strings.package/Symbol.class/class/accessing/allSymbols.st A Collections-Strings.package/Symbol.class/class/accessing/selectorsContaining_.st A Collections-Strings.package/Symbol.class/class/accessing/thatStartsCaseSensitive_skipping_.st A Collections-Strings.package/Symbol.class/class/accessing/thatStarts_skipping_.st A Collections-Strings.package/Symbol.class/class/cleanup/compactSymbolTable.st R Collections-Strings.package/Symbol.class/class/initialization/allSymbolTablesDo_.st R Collections-Strings.package/Symbol.class/class/initialization/allSymbolTablesDo_after_.st R Collections-Strings.package/Symbol.class/class/initialization/compactSymbolTable.st R Collections-Strings.package/Symbol.class/class/initialization/initialize.st A Collections-Strings.package/Symbol.class/class/initialize-release/initialize.st A Collections-Strings.package/Symbol.class/class/initialize-release/release.st A Collections-Strings.package/Symbol.class/class/iterating/allSymbolTablesDo_.st A Collections-Strings.package/Symbol.class/class/iterating/allSymbolTablesDo_after_.st R Collections-Strings.package/Symbol.class/class/private/shutDown_.st A Collections-Strings.package/Symbol.class/class/system startup/shutDown_.st M Collections-Weak.package/WeakArray.class/class/initialization/initialize.st A Collections-Weak.package/WeakArray.class/class/initialization/release.st A FileSystem-Core.package/FileLocator.class/class/adding/addResolver_.st R FileSystem-Core.package/FileLocator.class/class/class initialization/addResolver_.st R FileSystem-Core.package/FileLocator.class/class/class initialization/flushCaches.st M FileSystem-Core.package/FileLocator.class/class/class initialization/initialize.st A FileSystem-Core.package/FileLocator.class/class/class initialization/release.st R FileSystem-Core.package/FileLocator.class/class/class initialization/startUp_.st A FileSystem-Core.package/FileLocator.class/class/flushing/flushCaches.st A FileSystem-Core.package/FileLocator.class/class/system startup/startUp_.st R FileSystem-Disk.package/DiskStore.class/class/class initialization/checkVMVersion.st M FileSystem-Disk.package/DiskStore.class/class/class initialization/initialize.st A FileSystem-Disk.package/DiskStore.class/class/class initialization/release.st R FileSystem-Disk.package/DiskStore.class/class/class initialization/shutDown_.st R FileSystem-Disk.package/DiskStore.class/class/class initialization/startUp_.st A FileSystem-Disk.package/DiskStore.class/class/system startup/checkVMVersion.st A FileSystem-Disk.package/DiskStore.class/class/system startup/shutDown_.st A FileSystem-Disk.package/DiskStore.class/class/system startup/startUp_.st M Files.package/FileStream.class/class/initialize-release/initialize.st A Files.package/FileStream.class/class/initialize-release/release.st M Files.package/FileStream.class/class/system startup/shutDown_.st M Files.package/FileStream.class/class/system startup/startUp_.st R Files.package/MultiByteFileStream.class/class/class initialization/defaultToCR.st R Files.package/MultiByteFileStream.class/class/class initialization/defaultToCRLF.st R Files.package/MultiByteFileStream.class/class/class initialization/defaultToLF.st R Files.package/MultiByteFileStream.class/class/class initialization/guessDefaultLineEndConvention.st M Files.package/MultiByteFileStream.class/class/class initialization/initialize.st R Files.package/MultiByteFileStream.class/class/class initialization/startUp.st A Files.package/MultiByteFileStream.class/class/defaults/defaultToCR.st A Files.package/MultiByteFileStream.class/class/defaults/defaultToCRLF.st A Files.package/MultiByteFileStream.class/class/defaults/defaultToLF.st A Files.package/MultiByteFileStream.class/class/defaults/guessDefaultLineEndConvention.st A Files.package/MultiByteFileStream.class/class/system startup/startUp.st R Files.package/Stdio.class/class/class initialization/initialize.st A Files.package/Stdio.class/class/initialize-release/initialize.st A Files.package/Stdio.class/class/initialize-release/release.st M FontInfrastructure.package/LogicalFont.class/class/class initialization/initialize.st A FontInfrastructure.package/LogicalFont.class/class/class initialization/release.st R FreeType.package/FT2Handle.class/class/class initialization/initialize.st A FreeType.package/FT2Handle.class/class/initialize-release/initialize.st A FreeType.package/FT2Handle.class/class/initialize-release/release.st R FreeType.package/FT2Handle.class/class/initialize-release/unload.st M FreeType.package/FT2Handle.class/class/system startup/startUp_.st R FreeType.package/FreeTypeCache.class/class/accessing/clearCurrent.st R FreeType.package/FreeTypeCache.class/class/accessing/initialize.st A FreeType.package/FreeTypeCache.class/class/cleanup/clearCurrent.st A FreeType.package/FreeTypeCache.class/class/initialize-release/initialize.st A FreeType.package/FreeTypeCache.class/class/initialize-release/release.st M FreeType.package/FreeTypeCache.class/class/system startup/shutDown_.st M FreeType.package/FreeTypeSettings.class/class/class initialization/initialize.st A FreeType.package/FreeTypeSettings.class/class/class initialization/release.st M FreeType.package/FreeTypeSettings.class/class/system startup/shutDown_.st R Graphics-Display Objects.package/Cursor.class/class/class initialization/initBottomLeft.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initBottomLeft.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initBottomRight.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initCorner.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initCrossHair.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initDown.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initMarker.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initMenu.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initMove.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initNormal.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initNormalWithMask.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initOrigin.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initOverEditableText.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initRead.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initResizeLeft.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initResizeTop.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initResizeTopLeft.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initResizeTopRight.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initRightArrow.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initSquare.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initTarget.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initTopLeft.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initTopRight.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initUp.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initWait.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initWrite.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/initXeq.st A Graphics-Display Objects.package/Cursor.class/class/initialization - private/makeCursorsWithMask.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initBottomRight.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initCorner.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initCrossHair.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initDown.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initMarker.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initMenu.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initMove.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initNormal.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initNormalWithMask.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initOrigin.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initOverEditableText.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initRead.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initResizeLeft.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initResizeTop.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initResizeTopLeft.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initResizeTopRight.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initRightArrow.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initSquare.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initTarget.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initTopLeft.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initTopRight.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initUp.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initWait.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initWrite.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initXeq.st R Graphics-Display Objects.package/Cursor.class/class/initialization/initialize.st R Graphics-Display Objects.package/Cursor.class/class/initialization/makeCursorsWithMask.st R Graphics-Display Objects.package/Cursor.class/class/initialization/startUp.st A Graphics-Display Objects.package/Cursor.class/class/initialize-release/createStandardCursors.st A Graphics-Display Objects.package/Cursor.class/class/initialize-release/initialize.st A Graphics-Display Objects.package/Cursor.class/class/system startup/startUp.st A Graphics-Display Objects.package/DisplayScreen.class/class/accessing/actualScreenDepth.st A Graphics-Display Objects.package/DisplayScreen.class/class/accessing/actualScreenSize.st R Graphics-Display Objects.package/DisplayScreen.class/class/class initialization/initialize.st A Graphics-Display Objects.package/DisplayScreen.class/class/initialize-release/initialize.st R Graphics-Display Objects.package/DisplayScreen.class/class/snapshots/actualScreenDepth.st R Graphics-Display Objects.package/DisplayScreen.class/class/snapshots/actualScreenSize.st R Graphics-Display Objects.package/DisplayScreen.class/class/snapshots/shutDown.st R Graphics-Display Objects.package/DisplayScreen.class/class/snapshots/startUp.st A Graphics-Display Objects.package/DisplayScreen.class/class/system startup/shutDown.st A Graphics-Display Objects.package/DisplayScreen.class/class/system startup/startUp.st A Graphics-Display Objects.package/Form.class/class/initialize-release/initialize.st A Graphics-Display Objects.package/Form.class/class/initialize-release/release.st R Graphics-Display Objects.package/Form.class/class/shut down/shutDown.st A Graphics-Display Objects.package/Form.class/class/system startup/shutDown.st R Graphics-Files.package/extension/Form/class/initialize.st R Graphics-Fonts.package/StrikeFont.class/class/derivative font caching/shutDown.st A Graphics-Fonts.package/StrikeFont.class/class/initialize-release/initialize.st A Graphics-Fonts.package/StrikeFont.class/class/initialize-release/release.st A Graphics-Fonts.package/StrikeFont.class/class/system startup/shutDown.st R Graphics-Primitives.package/Color.class/class/initialization/initialize.st R Graphics-Primitives.package/Color.class/class/initialization/initializeColorRegistry.st R Graphics-Primitives.package/Color.class/class/initialization/initializeGrayToIndexMap.st R Graphics-Primitives.package/Color.class/class/initialization/initializeIndexedColors.st R Graphics-Primitives.package/Color.class/class/initialization/registerColor_named_.st A Graphics-Primitives.package/Color.class/class/initialize-release/initialize.st A Graphics-Primitives.package/Color.class/class/initialize-release/initializeColorRegistry.st A Graphics-Primitives.package/Color.class/class/initialize-release/initializeGrayToIndexMap.st A Graphics-Primitives.package/Color.class/class/initialize-release/initializeIndexedColors.st A Graphics-Primitives.package/Color.class/class/initialize-release/registerColor_named_.st A Graphics-Primitives.package/Color.class/class/initialize-release/release.st R Graphics-Primitives.package/Color.class/class/other/shutDown.st A Graphics-Primitives.package/Color.class/class/system startup/shutDown.st A Kernel.package/Class.class/instance/initialize-release/release.st R Kernel.package/Delay.class/class/class initialization/initialize.st A Kernel.package/Delay.class/class/initialize-release/initialize.st A Kernel.package/Delay.class/class/initialize-release/release.st M Kernel.package/PharoKernelAssembly.class/class/meta-data/parts.st M Kernel.package/ProcessorScheduler.class/class/background process/startUp.st M Kernel.package/ProcessorScheduler.class/class/class initialization/initialize.st A Kernel.package/ProcessorScheduler.class/class/class initialization/release.st R Kernel.package/SmallInteger.class/class/class initialization/initialize.st R Kernel.package/SmallInteger.class/class/class initialization/startUp_.st A Kernel.package/SmallInteger.class/class/initialize-release/initialize.st A Kernel.package/SmallInteger.class/class/initialize-release/release.st A Kernel.package/SmallInteger.class/class/system startup/startUp_.st A Metacello-GitHub.package/MCGitHubRepository.class/class/flushing/flushDownloadCache.st R Metacello-GitHub.package/MCGitHubRepository.class/class/initialization/flushDownloadCache.st A Metacello-GitHub.package/MCGitHubRepository.class/class/initialize-release/initialize.st A Metacello-GitHub.package/MCGitHubRepository.class/class/initialize-release/release.st A Metacello-GitHub.package/MCGitHubRepository.class/class/system startup/startUp_.st M Monticello.package/MCMethodDefinition.class/class/initialization/cachedDefinitions.st M Monticello.package/MCMethodDefinition.class/class/initialization/flushMethodCache.st M Monticello.package/MCMethodDefinition.class/class/initialization/initialize.st A Monticello.package/MCMethodDefinition.class/class/initialization/release.st R Monticello.package/MCMethodDefinition.class/class/initialization/shutDown.st A Monticello.package/MCMethodDefinition.class/class/system startup/shutDown.st A Morphic-Core.package/WorldMorph.class/class/initialize-release/initialize.st A Morphic-Core.package/WorldMorph.class/class/initialize-release/release.st R Multilingual-Languages.package/LanguageEnvironment.class/class/class initialization/localeChanged.st R Multilingual-Languages.package/LanguageEnvironment.class/class/class initialization/startUp.st M Multilingual-Languages.package/LanguageEnvironment.class/class/initialization/initialize.st A Multilingual-Languages.package/LanguageEnvironment.class/class/initialization/release.st A Multilingual-Languages.package/LanguageEnvironment.class/class/system startup/localeChanged.st A Multilingual-Languages.package/LanguageEnvironment.class/class/system startup/startUp.st M NECompletion.package/NOCCompletionTable.class/class/class initialization/initialize.st A NECompletion.package/NOCCompletionTable.class/class/class initialization/release.st R Nautilus.package/Nautilus.class/class/class initialization/registerToolsOn_.st A Nautilus.package/Nautilus.class/class/initialize-release/initialize.st A Nautilus.package/Nautilus.class/class/initialize-release/release.st A Nautilus.package/Nautilus.class/class/tool - registration/registerToolsOn_.st M Network-Kernel.package/InternetConfiguration.class/class/initialization/initialize.st A Network-Kernel.package/InternetConfiguration.class/class/initialization/release.st M Network-UUID.package/UUIDGenerator.class/class/initialization/initialize.st A Network-UUID.package/UUIDGenerator.class/class/initialization/release.st R Network-UUID.package/UUIDGenerator.class/class/initialization/startUp.st A Network-UUID.package/UUIDGenerator.class/class/system startup/startUp.st M NonInteractiveTranscript.package/NonInteractiveTranscript.class/class/class initialization/initialize.st A NonInteractiveTranscript.package/NonInteractiveTranscript.class/class/class initialization/release.st M NonInteractiveTranscript.package/NonInteractiveTranscript.class/class/system startup/shutDown.st A Polymorph-Widgets.package/MorphicUIManager.class/class/testing/isValidForCurrentSystemConfiguration.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50539.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50540.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50539.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50540.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-BasicCommandLineHandler.package/BasicCommandLineHandler.class/class/class initialization/initialize.st A System-BasicCommandLineHandler.package/BasicCommandLineHandler.class/class/class initialization/release.st R System-BasicCommandLineHandler.package/BasicCommandLineHandler.class/class/class initialization/startUp_.st A System-BasicCommandLineHandler.package/BasicCommandLineHandler.class/class/system startup/startUp_.st M System-Clipboard.package/Clipboard.class/class/initialization/initialize.st A System-Clipboard.package/Clipboard.class/class/initialization/release.st R System-Clipboard.package/Clipboard.class/class/initialization/shutDown_.st R System-Clipboard.package/Clipboard.class/class/initialization/startUp_.st A System-Clipboard.package/Clipboard.class/class/system startup/shutDown_.st A System-Clipboard.package/Clipboard.class/class/system startup/startUp_.st M System-Finalization.package/WeakFinalizationList.class/class/class initialization/initialize.st A System-Finalization.package/WeakFinalizationList.class/class/class initialization/release.st A System-Localization.package/Locale.class/class/accessing/platformEncodings.st M System-Localization.package/Locale.class/class/initialization/initialize.st R System-Localization.package/Locale.class/class/initialization/platformEncodings.st A System-Localization.package/Locale.class/class/initialization/release.st A System-OSEnvironments.package/OSEnvironment.class/class/initialize-release/initialize.st A System-OSEnvironments.package/OSEnvironment.class/class/initialize-release/release.st A System-OSEnvironments.package/OSEnvironment.class/class/system startup/shutDown_.st R System-OSEnvironments.package/OSEnvironment.class/class/testing/initialize.st R System-OSEnvironments.package/OSEnvironment.class/class/testing/shutDown_.st R System-Platforms.package/OSPlatform.class/class/class initialization/initialize.st R System-Platforms.package/OSPlatform.class/class/class initialization/shutDown_.st R System-Platforms.package/OSPlatform.class/class/class initialization/startUp_.st A System-Platforms.package/OSPlatform.class/class/initialize-release/initialize.st A System-Platforms.package/OSPlatform.class/class/initialize-release/release.st A System-Platforms.package/OSPlatform.class/class/system startup/shutDown_.st A System-Platforms.package/OSPlatform.class/class/system startup/startUp_.st A System-Support.package/EndianDetector.class/class/class initialization/release.st M System-Support.package/EndianDetector.class/class/system startup/startUp_.st A System-Support.package/SmalltalkImage.class/class/image/wordSize.st M System-Support.package/SmalltalkImage.class/class/initialization/initialize.st A System-Support.package/SmalltalkImage.class/class/initialization/release.st M System-Support.package/SmalltalkImage.class/class/initialization/startUp_.st R System-Support.package/SmalltalkImage.class/class/initialize-release/wordSize.st M System-Support.package/SmalltalkImage.class/instance/snapshot and quit/snapshotPrimitive.st M System-VMEvents.package/InputEventFetcher.class/class/class initialization/deinstall.st M System-VMEvents.package/InputEventFetcher.class/class/class initialization/install.st M System-VMEvents.package/InputEventFetcher.class/instance/initialize-release/installEventLoop.st M System-VMEvents.package/InputEventFetcher.class/instance/initialize-release/terminateEventLoop.st M System-VMEvents.package/InputEventSensor.class/class/class initialization/installEventSensorFramework_.st M System-VMEvents.package/InputEventSensor.class/class/class initialization/installMouseDecodeTable.st M System-VMEvents.package/InputEventSensor.class/class/system startup/startUp.st R System-VMEvents.package/InputEventSensor.class/instance/initialize-release/shutDown.st R System-VMEvents.package/InputEventSensor.class/instance/initialize-release/startUp.st A System-VMEvents.package/InputEventSensor.class/instance/system startup/shutDown.st A System-VMEvents.package/InputEventSensor.class/instance/system startup/startUp.st R Tool-Base.package/PharoCommonTools.class/class/cleanUp/shutDown_.st M Tool-Base.package/PharoCommonTools.class/class/initialization/initialize.st A Tool-Base.package/PharoCommonTools.class/class/initialization/release.st A Tool-Base.package/PharoCommonTools.class/class/system startup/shutDown_.st M Tool-ProcessBrowser.package/CPUWatcher.class/class/class initialization/initialize.st M Traits.package/TClass.class/instance/initialize-release/removeFromSystem_.st Log Message: ----------- 50540 Pharo http://files.pharo.org/image/50/50540.zip

Jan. 22, 2016

Re: [Pharo-dev] How to manage GitFileTree and being integrated in-image (QualityAssistant example?)

by Thierry Goubier

Hi Mariano, this is a common question for external projects integrated inside the Pharo image. And we have an issue with version numbers, but let's try to keep that separate. Fixes to the code of external projects integrated inside Pharo should be done upstream (on the external project itself), not in the Pharo image. This is what is currently happening with the GT tools, NeoJSON, Zinc, and probably a few more. So, as a maintainer of such a projects in github, say, you can ask people to create issues on your project, pull requests and the like, and this is the only way bugs found in Pharo in your release project should be corrected. Then, everytime a new version of the Pharo image is built, a version of your project is integrated; and you can add an issue to update your project to a newer version inside Pharo. (Was I clear with that description? Feel free to ask or correct me :)) Now, about the package versions. There is an issue with metadata-less mode and a few quirks about the way Metacello check versions to upgrade packages, and the issue is open. Two ways forward are possible: David Allouche pointed one by saying ordering between versions (without checking the numbers) can be resolved by checking if one is an ancestor of the other... and the other is that, with Skip work on the github api, it becomes possible(*) to retrieve the version info from github without git and avoid those -Cypress.1. Thierry * There is a bit of code to write, of course, but most of it is reusing what already exists inside Skip github and GitFileTree. 2016-01-22 14:33 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi guys, > > Let's say there is a project which is being build with metadata-less > GitFileTree. There is a BaselineOf and a ConfigurationOf which work > correctly. And ConfigurationOf can perfectly have fixed "versions" that > could be, at some point, integrated in Pharo. > > Let's say I release version 1.0 which is INTEGRATED inside Pharo. When > Pharo image is build, it uses ConfigurationOfMyApp to load the code and so > there will be NO history of versions (cypress.1). > > Now, as Pharo goes on, there may be changes to that project as part of > refactors or whatever that happens in-image. So in one months from now, > Pharo may have a "newer" code than the originally released 1.0. Let's say > that for the package MyAppPackage were only 3 commits in those 2 months. > > At the same time, I have continue working with my project, and I am ready > to publish 1.1. > > Question is.... how do I bring Pharo changes to my own place? > > 1) Fetching (from Pharo repo) and pushing to my GitFileTree only the > versions during those 2 months? I doubt this will work as crappy > Monticello numbers could have collisions, right? > > 2) Doing a poor man diff and cherry picking changes from Pharo repo and > manually apply them to my own repo? In this case, the "3 commits" of those > 2 months will be lost as from git history version. > > Is there a project doing this?? I know QualityAssistant is close, but he > does not use metadata-less GitFileTree I think...so I am not sure. > > Thoughts? > > Thanks! > > > > -- > Mariano > http://marianopeck.wordpress.com >

Jan. 22, 2016

Re: [Pharo-dev] [ANN] GitHub API Bindings: new version

by Skip Lentz

Hi, thanks a lot for your feedback. > On Jan 22, 2016, at 2:25 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Yes, now it works. Thank you. > > May I suggest a couple of UI tips? > > - Please don't use input boxes without label. Yes I chose to use a ghost text inside the input boxes instead of labels. I thought labels would take too much space.. > - In the same row it would be better a Login button. > - A button to logout? Sure, the login button could turn into a logout button after logging in :P. Or it can be an option when you click on your username in the top right.. I think that is better actually. > - A progress bar or clock while logging and/or switching repositories/branches? Yes I was thinking about the same. What I would like most is a spinner of some sort, however I donât know if any of this is supported by Pharoâs UI framework > - I clicked "Checkout" button but what happened? After a wait clock, I don't know, there is no feedback at all. A pane at bottom would be awesome :) A progress/status pane at the bottom is not a bad idea at all! > Cheers, > > HernÃ¡n > > > 2016-01-22 9:11 GMT-03:00 Skip Lentz <skip.lentz(a)inria.fr <mailto:skip.lentz@inria.fr>>: > That sounds like the most probable source of the problem. > > Thanks Sven for the new version, I will update my configuration (or âBaselineOfâ). > HernÃ¡n, maybe you can try loading it in a new image to see if you get the same problem? > >> On Jan 22, 2016, at 12:42 PM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >> >> Hi, >> If there is already a version of NeoJSON in the image the new version can be skip (ahah!) during the loading. I had this problem before, I had to load the bleeding edge in a new image. >> >> >> >> On Friday, January 22, 2016, Skip Lentz <skip.lentz(a)inria.fr <mailto:skip.lentz@inria.fr>> wrote: >> Thanks HernÃ¡n for your report. >> As Sven said, it is not yet present in the stable version of NeoJSON. >> But it should not matter as I load the bleeding-edge version. >> >> I will look into this. >> Can you tell me which script you used to load the tool? Is it the one in the first e-mail? >> >> >> -- >> Cheers >> Cyril Ferlicot >> > >

Jan. 22, 2016

Re: [Pharo-dev] Pharo bootstrap

by Christophe Demarey

Hi Brad, Envy is a package manager. It does not define the minimal kernel you need to install packages needed for your application. The goal of a bootstrap is to set up an environment from a know state. In the same time, this exercise forces us to define the minimal kernel needed to run Pharo (because you do not want to bootstrap the full system). Currently, we miss both the minimal kernel and a bootstrapped image of Pharo. Le 20 janv. 2016 Ã 20:17, Brad Selfridge a Ã©crit : > Has anyone looked at the VASmalltalk Envy Packager. It let's one decide > whether you want to package a headless or UI image. It then allows one to > define packaging instructions, that are saved with the new application), > that get fed into the packager. The instructions define prerequisite apps, > un-referenced methods, etc. When one defines a new application (package), > one can define prerequisite applications that have to be installed before > the current application is installed. This prerequisite chain is used in > loading the application from Envy and in packaging. Seems to work fairly > well. Doesn't take too long to package an app and give the developer pretty > fine control over the packaging and loading process. > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/ANN-Pharo-bootstrap-tp4872633p4872989.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 22, 2016