- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] missing updates: 30503 30504

by StÃ©phane Ducasse

On Oct 23, 2013, at 10:52 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-10-22, at 10:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> For retracting files you need access to files.pharo.org. >>> >>> This is what should be written in the readme. >> >> BTW have you tried that you actually have access to the machine? >> Because I remember that it didn't work for you nor Esteban... > > > So stef, did you check that you can actually edit the file? I cannot access it but I least I know that I should not look for it. And next time if there is a problem I just stop integrated and continue hacking on my cool stuff and look smart. Stef > Otherwise you will run into exactly the same trouble the next time...

Oct. 23, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by StÃ©phane Ducasse

On Oct 22, 2013, at 9:34 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I'll remove the script again, this is silly duplication that is going to be > outdated very quickly. It points already to the jenkins job, this is where > everything happens. so I will readd it. Camillo can you respect people that do not think like you? Stef > > On 2013-10-22, at 08:38, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> I changed the readme to be >> >> Pharo 3.0 Update Files >> ====================== >> >> This repository contains a collection of the updates files used for the system-updates of Pharo 3.0. >> The files are made available on the [file server](http://files.pharo.org/updates/pharo3.0/). >> The [updates30.list](updates30.list) is contains a list of all update files and is generated by a [jenkins job](https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-3-Release/). >> >> Do not touch these files manually if you do not know what you are doing. >> Read the class comments of the `ScriptLoader` class for a complete description of the Pharo integration process. >> >> >> Here is a bit of an explanation of how the staged and update.list are merged: this is the script of the jenkins job >> https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-3-Release/ >> >> >> ./pharo Pharo.image eval " >> updates := (ZnEasy get: 'http://files.pharo.org/updates/pharo3.0/updates30.list') contents lines. >> updates := updates reject: [ :each | each beginsWith: '#' ]. >> >> staged := 'updates30.staged' asFileReference readStream contents asString lines. >> staged := staged reject: [ :each | each beginsWith: '#' ]. >> >> updates := (updates, staged) asSet asArray sorted. >> >> 'updates30.list' asFileReference ensureDeleted writeStreamDo: [ :output | >> >> output nextPutAll: '#Pharo3.0'; cr. >> updates do: [ :each | >> output nextPutAll: each; cr ]]. >> >> Smalltalk snapshot: false andQuit: true." >> >> >> The update30.list file is generated on the server and in case of emergency this is the way to modify it. >> >> ssh file-pharo.inria.fr >> sudo su - filepharosync >> cd /appli/files.pharo.org/updates/pharo3.0/ >> vi updates30.list >> >> Good luck because you should not need it at all. >> >> >

Oct. 23, 2013

Re: [Pharo-dev] The new fogbugz mails look nice :)

by StÃ©phane Ducasse

where? I want to see it and get brainwashed and start fixing bugs :) Stef On Oct 22, 2013, at 3:17 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > that would be cool ;) > > Ben > > On Oct 22, 2013, at 3:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> One would almost start fixing things, just to see them ;-) >> >> On 22 Oct 2013, at 15:08, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> Just to say :P >>> >>> Ben >>> >> >> >

Oct. 23, 2013

Re: [Pharo-dev] VM for Athens Graphics

by Igor Stasenko

On 23 October 2013 08:12, J.F. Rick <self(a)je77.com> wrote: > On Tue, Oct 22, 2013 at 7:37 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> The latest Pharo vms for all 3 major platforms support Athens with Cairo >> as backend. >> It is our starting point, one day we might choose to have different >> backend(s), like opengl etc. >> > > Excellent. I'm mainly using Linux. > > >> For the ipad , best would be to implement a quartz backend for athens. >> As a temporary solution we could try to compile cairo library for it, but >> i am not expert in iOS >> to say if it can be done without much fuss. >> Also, since iOS is famous for banning any applications which using >> generated code, >> that means it should be done by writing a VM plugin and then adopting new >> primitives to >> work with Athens API. >> > > While I would love to use such a thing on iOS, I'm afraid that VM making > is beyond me. That said, if somebody does it, I do have a few multi-touch > tools, such as a keyboard, that I'd be willing to port to it. > > Increasingly, touch based machines are going to replace mouse based > machines as the dominant paradigm. > Mouse i much more precise than fingers. I doubt it going to be replaced. I think it will stay. > If we can create a great development environment for touch, we'd have a > good chance to really invent the future. Graphic processor accelerated > graphics are part of that. A rewrite of the events infrastructure, both to > simply the current mess and to add touch support, is part of that. > > Yes, what interesting that morphic from the very beginning supports multiple hands concept, which fits well with multitouch. Of course you need to handle things a bit different, but still it is good basement. > Cheers, > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick > -- Best regards, Igor Stasenko.

Oct. 23, 2013

[pharo-project/pharo-core]

by GitHub

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

Oct. 23, 2013

[pharo-project/pharo-core] 97519b: 30517

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 97519bf22e86a3b42c647e4b4fe44a30921d2ec0 https://github.com/pharo-project/pharo-core/commit/97519bf22e86a3b42c647e4b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-23 (Wed, 23 Oct 2013) Changed paths: M OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitArrayNode_.st M OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitBlockNode_.st M OpalCompiler-Core.package/OCAbstractLocalVariable.class/instance/read%2Fwrite usage/isUninitialized.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/isRead.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/isUnused.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/markRead.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/markWrite.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script172.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30517.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30517 11975 Sync with Opal Repository https://pharo.fogbugz.com/f/cases/11975 http://files.pharo.org/image/30/30517.zip

Oct. 23, 2013

Re: [Pharo-dev] Release mails and update summary

by Torsten Bergmann

> because it's duplicate information. Makes sense > I don't understand, we send github mails since a while and they include all the information > you need, diffs + commit log. Yes - really a step forward! > smalltalkhub has never update it's search functionality, so yes you are lost. > Again, a result of limited resources, but you find it under the Pharo project: > > http://smalltalkhub.com/#!/~Pharo/ci Thanks - I will look into it. Thanks T.

Oct. 23, 2013

Re: [Pharo-dev] Release mails and update summary

by Camillo Bruni

On 2013-10-23, at 12:17, "Torsten Bergmann" <astares(a)gmx.de> wrote: > Marcus wrote: >> do it. The problem is that not everything that would be nice can be done just because the day >> has just 24 hours. > > No need to say this. We know that each others plate if full - but we all try to move Pharo forward. > We all did in the past and hopefully will be able to continue to do so. > > But currently I'm completely LOST to even know in which direction the release management moves, > its current state and what is planned for it. > > Just for demonstration: > > I only stumbled by accident on your mail regarding the release mails and that they > will not be sent anymore. > > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085… > > Is it because you have no time to write them, is it because there is a "grand plan" > to switch to a different process to make the updates reproducible? I dont know. because it's duplicate information. > Anything I know now from the mail is that I should now have to watch out for Github > mails and need to find out more out the current github activities - before getting even > a glue on whats going on or how to help. I don't understand, we send github mails since a while and they include all the information you need, diffs + commit log. > another example: > > Camillo talkes about "a complete fogbugz api written in pharo" - I can not find it when > searching "fogbugz" on SmalltalkHub => I'm LOST again smalltalkhub has never update it's search functionality, so yes you are lost. Again, a result of limited resources, but you find it under the Pharo project: http://smalltalkhub.com/#!/~Pharo/ci

Oct. 23, 2013

Release mails and update summary

by Torsten Bergmann

Marcus wrote: >do it. The problem is that not everything that would be nice can be done just because the day >has just 24 hours. No need to say this. We know that each others plate if full - but we all try to move Pharo forward. We all did in the past and hopefully will be able to continue to do so. But currently I'm completely LOST to even know in which direction the release management moves, its current state and what is planned for it. Just for demonstration: I only stumbled by accident on your mail regarding the release mails and that they will not be sent anymore. http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085… Is it because you have no time to write them, is it because there is a "grand plan" to switch to a different process to make the updates reproducible? I dont know. Anything I know now from the mail is that I should now have to watch out for Github mails and need to find out more out the current github activities - before getting even a glue on whats going on or how to help. another example: Camillo talkes about "a complete fogbugz api written in pharo" - I can not find it when searching "fogbugz" on SmalltalkHub => I'm LOST again It's really hard to follow all the activities ...

Oct. 23, 2013

Re: [Pharo-dev] Pharo-project.org success stories link to be revised a bit...

by phil＠highoctane.be

Sure, please do. --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Wed, Oct 23, 2013 at 8:46 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Oct 22, 2013, at 6:41 PM, phil(a)highoctane.be wrote: > > As Doru mentioned, marketing of Pharo should be improved to get more > traction. > > Now, on http://www.pharo-project.org/about/success-stories > > a serious bunch of links are not working, point to projects that are > abandoning Smalltalk for Javascript (Language of Languages) - link goes to > a page saying so -- bad karma. > > Even Esteban's Lawsuit Tracker is not the right URL (right one is * > http://smallworks.com.ar/web/projects/lawsuitTracker)*. > > Looks like other projects are not there anymore, click on the links for > issys or Ilon SA and end up waiting with nothing showing up. > > 2denker's http://taskfor.us/ is dead: 404 > > > So, some fixing needed. > > > -> the bug tracker can be good for thsese things, too. > > -> I can add you as someone who can change the website if you want. > > Marcus > >

Oct. 23, 2013