- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Komitter in 30852?

by Sean P. DeNigris

I think the issue got closed by mistake. I reopened, looks ready to integrate https://pharo.fogbugz.com/default.asp?13680 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Komitter-in-30852-tp4769794p4772557.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 8, 2014

Only one week left!! - ESUG 2014 REMINDER: 11th Innovation Technology Awards

by jdelgado＠lsi.upc.edu

ESUG 2014 REMINDER: 11th Innovation Technology Awards http://www.esug.org/Conferences/2014/Innovation-Technology-Awards Have you written innovative Smalltalk? The developers of any Smalltalk-based software can enter by submitting a 3-5min video of their software. Entrants demo their systems in a session at the end of Monday August 18th 2014, after which the conference attendees vote. (A vote consists in providing a sorted list of 3 preferred pieces of software.) The top 3 teams with the most innovative software will receive, respectively, 500 Euros, 300 Euros and 200 Euros. The results are announced in the Awards ceremony that is held during the social event. Applicants should provide the following information on the conference registration server. Once you have registered your personal info, an 'Awards' menu allows submitting your software. You can provide this information when you first register, or login again later and update your details. The registration server will open soon. You can start preparing your software right now though. Info to provide: Name of the software Licence information (free, shareware, or commercial) Name of the Smalltalk dialect used Name, Affiliation and Country of developers Besides, it would be great if the submission could include: URL for a video (3-5 min) showing a screencast / demo of the software URL for downloading the software or at least a runnable demo Deadline: August 15th Any Smalltalker can apply (students, companies, ...). The presented piece of code/software should be written in Smalltalk or directly support Smalltalk (e.g. Smalltalk VM). All Smalltalk dialects are accepted. The applicant should be "strongly related" to the presented code, be it as an author, as owner of the copyright/copyleft, or as an official representative of the copyright/copyleft owner. Bests, Jordi

Aug. 8, 2014

Re: [Pharo-dev] [Remainder] Call for participation to the Second Visualization Contest with Roassal

by Alexandre Bergel

Only a few days left before the deadline, which is Monday 11 august. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jun 6, 2014, at 9:57 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Dear colleagues and friends, > > We are happy to announce the Second Visualization Contest with Roassal. > > > What can I win? > - 150 euros, sponsored by ObjectProfile > > - a Ã¼ber-cool ObjectProfile T-shirt and some wonderful stickers > > - maximum publicity of your work > > - a nice award certificate, delivered during ESUG > > > How can I win? > - you have to produce a visualization with Roassal. You can use the Pharo, VisualWorks, Amber or VAST version of Roassal. Here is an example of what we expect > http://bit.ly/sunburstDemo > http://bit.ly/GraphET > https://vimeo.com/96091089 about smartbrowser > https://vimeo.com/94724841 about GraphBuilder > http://www.youtube.com/watch?v=uOmox7NgRAg&feature=youtu.be on AspectMaps, by Johan Fabry, the winner of the contest last year > > - making a video is mandatory. The video will weight the most in our decision. The video could be of any length and has to include your name and say that is was made (partly or completely) with Roassal. No need to talk, just show off! > > - making your code available and easy to install will help you get more points > > > How can I submit? > - send the links of your video and other material (if needed) to info(a)objectprofile.com Every email you will send to this email will be acknowledged. If you do not receive a 'Ok' from us, it means we haven't read it, in that case send your email again after a few days. > - the deadline for submitting is August 11, 2014 > > > Mini FAQ? > - Is the object-profile team allowed to participate? No > > - I know nothing about Roassal, how can I start? Roassal comes with a large set of examples. On Pharo, just use the example browser available from the world menu. The book http://www.deepintopharo.com also contains chapter on Roassal 1 and Mondrian. You are also very welcome to ask question to the Pharo or Moose mailing lists about Roassal. Or simply send email to info(a)objectprofile.com . We will help you. > > - Iâve heard about Roassal2, Roassal3d, Roassal1. I feel lost in all these keywords! Wellâ¦ Roassal1 is available on VisualWorks and VAST. Roassal2 works on Pharo and Amber. Roassal2 is a major revamp of Roassal1. The documentation on Roassal1 may be easily adapted to Roassal2. > > - Should my visualization or code be open source? No need for this, whatever license is fine. However your video has to be public. > > - How can I get more information? Just comment on the facebook https://www.facebook.com/ObjectProfile or using Twitter @ObjectProfile or send email to info(a)objectprofile.com or the pharo or moose mailing list > > - What I submit two different videos? Yes, no problem with that. As many as you are productive. > > - Who won last year? Johan Fabry with AspectMaps made a nice video about visualizing aspects. > > - How will judge the videos? both the esug community and the object profile team. The Esug community will have 30% of the final grade, object profile the remaining 70% > > > Cheers, > The profilers

Aug. 8, 2014

Re: [Pharo-dev] Does image build process check for halts?

by Tim Mackinnon

Maybe this is a good moment to review what checks are run on every build and ensure that they are working? Itâs easy to leave in something like self halt - it would be nice to have the CI system do its stuff and send you an email that you forget (this is where CI is awesome). Iâm also assuming in the CI process we check logs for âundefinedâ and âerrorâ msgs that would appear in the transcript right? Tim On 8 Aug 2014, at 13:56, stepharo <stepharo(a)free.fr> wrote: > > On 8/8/14 09:50, Tim Mackinnon wrote: >> Guys - I noticed that the pharo build 40152 - has a halt when you press ALT-Tab (I assume this was accidentally left in by someone?). > probably me in my chase to understand widgets are used >> >> But this got me thinking - doesnât the CI process check for this and just fail the build? > Normally we run a set of rules and one should be looking for halt and other debugging messages but I do not know if we are doing it or not. > >> Maybe legitimate halts should be tagged specially somehow so they pass through - but accidental ones get noted? >> >> Tim >> >> > >

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Tim Mackinnon

I can see how that makes sense for now - we will continue to make suggestions and then over time maybe we can help curate it it becomes too much. Although I am worried that this can create a lot of work - both to report and fix? In the meantime how do you prefer we submit changes, in Markdown format (does that help?) - or is RTF better? OR - is there any way we can commit proposed changes - which you can review and publish (e.g. could we use a Git Repo?). I'm not familiar with the underlying technology of Pharo.org - but could we modify it so there is a discussion page like on Wikipedia where changes can be proposed and applied by you? This sounds like a great BOF topic at ESUG - and maybe we should follow up on that? At the moment I can see numerous tiny fixes (grammatical and formatting - that are more time consuming to report than just fix). For now, can you apply the newer fixes I proposed (to undo Stef's misunderstanding for my "use link" suggestion). I also think on the http://pharo.org/download page we should mention the PharoLauncher project (http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher) - its really handy for managing multiple images (and getting the latest image). tim On Fri, 8 Aug 2014, at 01:14 PM, Esteban Lorenzano wrote: > Hi, > > We love to have contributions, but for the moment being (to try to keep the design, etc. and prevent too much disorderâ¦ which was a problem in the previous site). > I would prefer you to send me your contributions (or post it here), and I will upload them to the site. > > cheers, > Esteban > > On 08 Aug 2014, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > >> >> Yes - it would be better to link to the YouTube version in the text. >> >> So how is the Pharo.org site generated? Is this what Pillar is? (Is it a pier wiki?) and could we easily help with editing a subsection of it to help out? >> >> Tim >> >> Sent from my iPhone >> >> On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: >> >>> I've uploaded the video on my channel as well. >>> >>> https://www.youtube.com/watch?v=iFomI-7h4qQ >>> >>> Phil > >

Aug. 8, 2014

Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal

by Alexandre Bergel

Your version had been merged. But your .mcz was not in the repo. Now it is. Sorry about that. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Aug 7, 2014, at 9:31 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Hi Alexandre, > > The patch doesnât seems to be commited in Roassal2 repoâ¦ > > Vincent > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Alexandre Bergel > EnvoyÃ© : mercredi 6 aoÃ»t 2014 21:44 > Ã : Moose-related development > Cc : Pharo Development List > Objet : Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal > > Thanks Vincent! > It seems to work well. > > Included in Roassal! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > On Aug 6, 2014, at 12:29 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > > Solved ! > > You will found the changes in the attached .mcz. > > I added some sessions guards where some Athens external objects are used. Stef you were right ;) > Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path that relies on Athens external objects. > > It seems to works for me. If it is the case for you, it we be nice to integrate it quickly to be able to work fine :) > > Thanks > > Vincent > > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de stepharo > EnvoyÃ© : jeudi 31 juillet 2014 22:58 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM error with Roassal > > Alexandre > > may be you should try to understand what is a session. > Because this is about 2 lines of code. > > When you open an image you save 2 min ago or 2 years ago, how the system knows that an OS ressources is valid? > By checking the session id... > > Stef > > On 31/7/14 16:09, Alexandre Bergel wrote: > > Yes, and this is a mess. > I've spent quite some time in getting the session working with Roassal2 and it still does not work. I would appreciate help on this. > > Alexandre > > > On Jul 31, 2014, at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > It looks like Trachel does not recreate athens external resources. > There is an example in AthensSceneView, on how to check and reload an > AthensSurface. > > > 2014-07-31 12:51 GMT+02:00 Usman Bhatti <usman.bhatti(a)gmail.com>: > > > > On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > Yes it is. But I will not do > > TRMorph allInstances do: #delete > > In command line every day... > > > It is only intended to recover your lost work in the image not for everyday use :). > > > > > Vincent > > > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > de Usman Bhatti EnvoyÃ© : jeudi 31 juillet 2014 10:59 Ã : Pharo > Development List Cc : Moose-related development > > > Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error > with Roassal > > > > This may be related to this known issue reported a few days back. > > https://code.google.com/p/moose-technology/issues/detail?id=1084 > > > > And there is a possible solution to recover your image. > > > > usman > > > > On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Hi, > > > > Yesterday, I was using GraphET (a part of Roassal) to do some charts and, today, when I wanted to reopen the image. > > And I got that : > > <image001.png> > > It is *very* unpleasant... > > > > To reproduce the bug: > > 1 - You can do either: > > | builder | > > builder := GET2Line data: (0 to: 100) . > > builder > > y: [ :x | x*x ]. > > > > builder open. > > Or > > WorldMenu -> Roassal examples -> choose an item -> click on a graph . A TRMorph should be opened. > > 2 - don't close the graph and save the pharo image. > > 3 - Close the pharo image > > 4 - Reopen it > > > > I am under W7 x64 with the latest moose image and the VM available on the pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from the 10 july. > > You will find the crash dump attached. > > > > > > Thankfully, I managed to open the image with a latest VM (http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip) > > Thanks a lot Eliot ! :) > > > > And I got this: > > <image002.png> > > > > Thanks in advance > > > > Cheers, > > Vincent BLONDEAU > > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. > <Trachel-VincentBlondeau.180.mcz>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Aug. 8, 2014

Re: [Pharo-dev] Metacello Projects: one canonical config/repo for all platforms

by Dale Henrichs

On Fri, Aug 8, 2014 at 3:54 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 08 Aug 2014, at 06:16, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> > wrote: > > > Ben and Sean, > > > > After a bit more thought, I believe that it should be okay to make > copies, but there does need to be a single primary repository where the > correct and latest configuration can be found. > > > > Putting copies of configurations into repositories to make project > discovery easier is a good use of copies. Copies are also useful when > creating mirror repos.... > > > > But one must be able to determine the location of the canonical > repository for the configuration. > > > > If the configuration were always co-located with the packages then it > would relatively easy to figure out where to find the newest and > 'correctest' configuration. > > > > The canonical location should ALWAYS be used in project references. > > But can't Metacello help there ? > > I mean, each configuration, no matter where it is copied/located is the > same and knows its canonical repository, right ? > So all that is needed is a kind of double-check, or following the > reference. > > BTW, doesn't Metacello not do some latest version checking already ? > > Sven, In a project reference, the developer specifies the repository from which the configuration should be loaded: spec project: 'Zinc Project' with: [ spec versionString: #'stable'; className: 'ConfigurationOfZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents' ]. In the above case, the canonical repository for Zinc is being used, but a developer can use a different repository like http://squeaksource.com/MetacelloRepository. Metacello's job is to do what the developer specifies. The developer may have perfectly good reasons for specifying a different location than the canonical repository: - critical bug fix to configuration, but no write access to canonical repo - private fork of project ... - etc. Metacello cannot second guess the developer when it comes to loading packages:) Sean is referring to the fact that some configurations are not present in the repository where the packages are located and they should be. Also there are cases where the generic *MetacelloRepository* is used in a project reference when the canonical location should be. Dale

Aug. 8, 2014

Re: [Pharo-dev] Does image build process check for halts?

by stepharo

On 8/8/14 09:50, Tim Mackinnon wrote: > Guys - I noticed that the pharo build 40152 - has a halt when you press ALT-Tab (I assume this was accidentally left in by someone?). probably me in my chase to understand widgets are used > > But this got me thinking - doesnât the CI process check for this and just fail the build? Normally we run a set of rules and one should be looking for halt and other debugging messages but I do not know if we are doing it or not. > Maybe legitimate halts should be tagged specially somehow so they pass through - but accidental ones get noted? > > Tim > >

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Esteban Lorenzano

Hi, We love to have contributions, but for the moment being (to try to keep the design, etc. and prevent too much disorderâ¦ which was a problem in the previous site). I would prefer you to send me your contributions (or post it here), and I will upload them to the site. cheers, Esteban On 08 Aug 2014, at 12:11, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes - it would be better to link to the YouTube version in the text. > > So how is the Pharo.org site generated? Is this what Pillar is? (Is it a pier wiki?) and could we easily help with editing a subsection of it to help out? > > Tim > > Sent from my iPhone > > On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > >> I've uploaded the video on my channel as well. >> >> https://www.youtube.com/watch?v=iFomI-7h4qQ >> â >> Phil

Aug. 8, 2014

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by phil＠highoctane.be

AFAIK it is a Marina based CMS. http://astares.blogspot.be/2014/04/marina.html Now, I knew how to get in the older system but no info on how to do this in the new one. Phil On Fri, Aug 8, 2014 at 12:11 PM, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes - it would be better to link to the YouTube version in the text. > > So how is the Pharo.org site generated? Is this what Pillar is? (Is it a > pier wiki?) and could we easily help with editing a subsection of it to > help out? > > Tim > > Sent from my iPhone > > On 8 Aug 2014, at 10:52 am, "phil(a)highoctane.be" <phil(a)highoctane.be> > wrote: > > I've uploaded the video on my channel as well. > > https://www.youtube.com/watch?v=iFomI-7h4qQ > â > Phil > >

Aug. 8, 2014