- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] xml-oo mapper?

by Tudor Girba

Hi, Thanks. I guess it is probably what I need. I will look at it more closely. I want to be able to map an XML structure on objects and support read/write at the object level. Cheers, Doru On Wed, Aug 6, 2014 at 11:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > There is Magritte-XML. Or do you mean something different? It is in > Magritte3Addons on smallttalkhub > > Norbert > > > Am 06.08.2014 um 09:29 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > Does anyone know if there exists an XO mapper available in the Pharo? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 7, 2014

New CogVMs available

by Eliot Miranda

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3060/. CogVM binaries as per VMMaker.oscog-eem.844/r3060 Fix bad bug in interpreter to machine code frame conversion on backward branch. Old code would decrement branch even if backward branch checked for events and did a process switch, potentially converting frames at arbitrary unmappable pcs, not just backward branches. Neaten and comment the code. Neaten and update the pc mapping tests for multiple bytecode sets and for sets with extensions. Change default count to 40 from 10 to reduce number of startup methods jitted. Allow warnings to be treated as errors, adding -blockonwarn flag on Mac & Unix. -- best, Eliot

Aug. 7, 2014

Re: [Pharo-dev] No projects on StHub?

by Alexandre Bergel

I did not known neither. I will have a serious look at GitHub. Alexandre > Le 05-08-2014 Ã 11:13, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> a Ã©crit : > > Wow, I didnât know that. Nice > > >> On 05 Aug 2014, at 17:01, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >> >> >> KIlon, >> >> If you use a a github reference in your configuration: >> >> github://username/projectname:commitish/repositoryDir >> >> Git is not required. Metacello will download a zipped version of the commitish referenced (a commitish is a branch name, SHA or tag name) and a read only filetree repository is created .... >> >> So folks should be able to use your project without installing git on their machine. >> >> Dale >> >> >>> On Mon, Aug 4, 2014 at 2:17 AM, kilon alios <kilon.alios(a)gmail.com> wrote: >>> yeah I will also move my latest project to github. I am already more active with github than I am in SThub anyway. The one thing that stopped me so far is that I don't want to force people to install git to get the latest version of my project. SThub is great for this. >>> >>> >>>> On Mon, Aug 4, 2014 at 12:03 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> Well, thankfully I keep all my latest projects on github, and I have configurations of them in the image. But CI is not working and anyway itâs a strange situation. Is there any other service where I can keep my configurations? Because thatâs the only thing I version with monticello are configurations as I want to use gofer to load my projects. And here reliability is much more important then other features. >>>> >>>> Uko >>>> >>>> >>>>> On 04 Aug 2014, at 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>> oh boy thats looks nasty bug, hope its not permanent. >>>>> >>>>> >>>>>> On Mon, Aug 4, 2014 at 11:44 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>>> Hi, >>>>>> >>>>>> I was on vacation last weak, have I missed anything? Because my SmaltalkHub user does not have any projects http://smalltalkhub.com/#!/~YuriyTymchuk (and I had a bunch of them). >>>>>> >>>>>> Uko >

Aug. 6, 2014

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

by Nicolai Hess

In the solution I posted on the list, only TRCanvas holds the session and if it changes all attached Shapes resets its path. 2014-08-06 21:43 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > 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 > <pharo-dev-bounces(a)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 > <pharo-dev-bounces(a)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 > > >

Aug. 6, 2014

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

by Alexandre Bergel

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

Aug. 6, 2014

Fwd: [squeak-dev] Float parsed as a Fraction bug

by Eliot Miranda

oops; meant to include Pharo in the discussion ---------- Forwarded message ---------- From: Eliot Miranda <eliot.miranda(a)gmail.com> Date: Wed, Aug 6, 2014 at 12:42 PM Subject: Re: [squeak-dev] Float parsed as a Fraction bug To: The general-purpose Squeak developers list < squeak-dev(a)lists.squeakfoundation.org> Hi Levente, On Wed, Aug 6, 2014 at 11:43 AM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Wed, 6 Aug 2014, Eliot Miranda wrote: > > Hi All, >> Squeak trunk also suffers from the Float parsed as a Fraction bug: >> >> 1e-8 class Fraction >> 1.0e8 class Float >> > > I'm not entirely sure about it being a bug. I've checked Squeak 3.8 > (pre-SqNumberParser), and it also parsed that literal as a Fraction. If I > want a Float, I can be explicit and use 1.0e-8. > IMO it very much *is* a bug. Smalltalk-80 has never supported Fraction literals. They're always written as division expressions. Fraction answers false to isLiteral. Just because it worked that way doesn't mean it was right. I suspect no one noticed. Allowing Fraction literals feels like a big change to me. I made a modified version of Fraction >> #printOn:base: which outputs the > literal format if possible. The change "fixes" the debugger (note that itw > was way less broken in Squeak than in Pharo anyway). > The only drawback I found is that some fractions become a bit more > "complex" when printed, e.g. 3/4 => 75e-2 OK, but is this the right fix? What does everybody think? Keep the language unchanged or add Fraction literals and add another incompatibility with other dialects? If Fractions are literals - what is the semantics of 1/0 (easy, it is not a literal, but needs to be stated)? - what is [1/0.1] on: ZeroDivide do: [:ex| #error] ? Is it 10.0 or #error, i.e. is 1/0.1 10.0 or 1 / 0 followed by the Integer 1? > Levente > >> -- >> eek! Eliot > > -- best, Eliot -- best, Eliot

Aug. 6, 2014

Re: [Pharo-dev] review issue 13767 packagetree changes visible selection even if okToChange is false

by stepharo

Thanks Nicolai I will have a look. I was dead today ... Stef On 6/8/14 14:08, Nicolai Hess wrote: > please, can someone test and review issue 13767. > Integrating this change is helpful for the next > nautilus refactoring steps. > > nicolai >

Aug. 6, 2014

Re: [Pharo-dev] About Smalltalkhub

by stepharo

Thanks nico. Stef On 6/8/14 17:38, Nicolas Petton wrote: > Hi guys, > > I'm just back from 2 weeks offline, and I just saw that SmalltalkHub has > some issues. I just restarted everything as packets were dropped, and > I'll have a deeper look tomorrow to see why it's behaving that > strangely. > > Cheers, > Nico > > >

Aug. 6, 2014

Jobs and Internships

by stepharo

HRworks: Get on board as graduate HRworks is the pioneer in software for service solutions in Germany. As early as 1998, HRworks developed a web-based business software for the cloud. With this software solution, companies can bill travel expenses and manage absences and equipment. More than 800 customers such as McDonaldâs, Tom Tailor, Lexmark or the Warner Music Group rely on HRworks every day. Have you already completed your studies and are looking for your first professional experience? After our âboot campâ you will take responsibility for minor components and tasks. You will gain experience and gradually you will be entrusted with more demanding tasks, depending upon your abilities. What do we expect from you? â¢ That you enjoy programming â¢ Smalltalk is your passion â¢ Good spoken English What does HRworks offer you? â¢ An open, motivated & efficient team that enjoy working together â¢ Working on a unique application architecture â¢ Optimum working conditions, such as the open-space concept â¢ Fruit & drinks; in particular, as much coffee as you need â¢ Above-average pay What next? Are you interested? Then we look forward to receiving your application by email to job(a)hrworks.de. More information: www.hrworks.de/career/ Any questions? JosÃ©-SimÃ³n GerÃ³nimo, +49 761 47954-12, job(a)hrworks.de ---------------------------------------------------------------------------------------------------- Hi guys HRWorks is a consortium member since the beginning and they are looking for Smalltalkers. Pass the message around. Stef HRworks: Internship HRworks is the pioneer in software for service solutions in Germany. As early as 1998, HRworks developed a web-based business software for the cloud. With this software solution, companies can bill travel expenses and manage absences and equipment. More than 800 customers such as McDonaldâs, Tom Tailor, Lexmark or the Warner Music Group rely on HRworks every day. Are you a student looking for an internship from 5 to 6 months? What do we expect from you? â¢ That you enjoy programming â¢ Smalltalk is your passion â¢ Good spoken English What tasks will you be given? You will develop new features and functions and improve our internal components and development processes. All features that you subsequently implement will be used by hundred thousand employees in prestigious companies. What does HRworks offer you? â¢ An open, motivated & efficient team that enjoy working together â¢ Working on a unique application architecture â¢ Optimum working conditions, such as the open-space concept â¢ Fruit & drinks; in particular, as much coffee as you need â¢ Above-average pay â¢ A student room What next? Are you interested? Then we look forward to receiving your application by email to job(a)hrworks.de. More information: www.hrworks.de/career/ Any questions? JosÃ©-SimÃ³n GerÃ³nimo, +49 761 47954-12, job(a)hrworks.de

Aug. 6, 2014

Re: [Pharo-dev] First commit with Git-Filetree

by kilon alios

no rush at all. I was off to the beach, I am also on vacations and plus its not really a problem all I had to do was to git add the folder. So no big deal for me, commits work just fine. But I thought it was better to report it. I have not tried to reproduce the error again. On Wed, Aug 6, 2014 at 8:16 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 04/08/2014 15:48, kilon alios a Ã©crit : > > So I have started using gitfiletree and the first commit seems to commit >> only .filetree file and not my package folder. I had to add the package >> folder with a "git add" and of course make a commit of it .Is this normal ? >> > No, it's not :( > > > >> the process I have followed is this >> >> 1) Create a github repo intialized with a readme and license file >> 2) git clone the repo to my hd >> 3) in a clean pharo image install gitfiletree as described in Git and >> Pharo chapter in Pharo for the Enterprise >> 4) in monticello add repository +gitfiletree and then choose the git >> folder >> 5) select a package and click save >> 6) add the commit info >> >> My other commits dont need any extra step just a simple "git push". >> > All the steps look fine. I'm off the internet most of the time until next > week (camping time), are you ok waiting until then? > > Thierry > >

Aug. 6, 2014