Re: [Pharo-dev] Debugging in Production Servers

The good developers / expert users will not do what you state. The eclipse debug, inspector, watches are very much part of a normal dev cycle in our place with around 100 devs. Even in Smalltalk I have seen less capable developers not exploiting even a fraction of the capability Smalltalk has and

Re: [Pharo-dev] Debugging in Production Servers

I am sorry, but I disagree. Yes, technically, much of what we take for granted is partially possible in most other languages, but it is often hard to use, an add-on, an afterthought. But more important, Java developers even do not use debuggers/inspectors/browsers during development, let alone

Re: [Pharo-dev] Debugging in Production Servers

The capability exists, any dev team can take advantage if reqd of it, I am sure many may have in rare occassions. On the remote on the same LAN it will not be any different than debug is for eclipse / VisualStudio in dev. In Insurance, Banking in my experience, it will be the last resort, unless i

Re: [Pharo-dev] Debugging in Production Servers

Thanks for reply. Are there cases of Java/Eclipse running in Production? Similarly with VC++ / Visual Studio? They would be very very slow wouldn't they? I am referring to real use case of live debugging in Production servers. I agree that this capability might not be attractive from point of view

Re: [Pharo-dev] Debugging in Production Servers

One can easily do that with Java / Eclipse or for VC++ / Visual Studio with attach to process. Probably I would reckon these to be more "secure" as industry prefers rather than having live debug capabilities built in to the code delivered or somehow "in-process". I am sure all others as in python,

Re: [Pharo-dev] [Pharo CI] Linux slave problem solved

Pharo and MOOSE CI seems to be in good condition now, but pharo-contribution still broken apparently. On Wed, Apr 23, 2014 at 3:28 PM, Marcus Denker wrote: > Hi, > > The problem with the linux slaves is fixed… things should get normal again. > > " there was an inconsistency between libvirt (used

[Pharo-dev] Debugging in Production Servers

Smalltalk has the capability of allowing live debugging in production servers. How unique is this capability? What other systems allow that? Is there a name for such capability? Can we coin one and market it? What are the pros and cons of having such a capability? All the best, Aik-Siong Koh

[Pharo-dev] Pharo Inbox now Public Writable

IIRC you still need to be logged in... - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-Inbox-now-Public-Writable-tp4756131.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Phexample: API Change Proposal (was Phexample: Image Destroying Bug)

Stefan Marr-3 wrote > First of all, I enabled public write access on the repository. It doesn't look like it has public write access. Notice the difference compared to the Pharo Inbox: vs.

Re: [Pharo-dev] Verifying Ubuntu downloads

Damien Cassou wrote > nope, still same problem Of course because I forgot to push the new config :/ Thanks for beta testing! Now, with Dale's advice on how to disable the package cache when simulating a load from the user's perspective before publishing a config (http://forum.world.st/Disabling-pa

Re: [Pharo-dev] GUI TestRunner failures not found by CI (was Re: [pharo-project/pharo-core] 1953a9: 30829)

Sven Van Caekenberghe wrote: On 23 Apr 2014, at 19:55, Ben Coman wrote: Sven Van Caekenberghe wrote: And we're all GREEN, great work ! Let's keep it that way until release. Everything that breaks a test should now be reverted. Thats great news

Re: [Pharo-dev] Hijri calendar

Hi, You could try Chalten, it also has support for the Islamic Calendar. Take a look here: https://github.com/mtaborda/chalten. Regards. Maxi 2014-04-23 17:26 GMT-03:00 Paul DeBruicker : > Torsten Bergmann wrote > > Paul DeBruicker wrote > >> Chronos has: > >> ... > >> Is that what you want? >

Re: [Pharo-dev] Hijri calendar

Torsten Bergmann wrote > Paul DeBruicker wrote >> Chronos has: >> ... >> Is that what you want? > > The www.chronos-st.org seems to be gone. But there is > http://smalltalkhub.com/#!/~Chronos/Chronos/ > > Thanks - I will have a look. Is it known to work in Pharo 3.0? > > Thx > T. Eh it will pr

Re: [Pharo-dev] Lost in spec

On 22 April 2014 21:02, Nicolai Hess wrote: > 2014-04-22 13:56 GMT+02:00 Igor Stasenko : > > i want to use different adaptor for TextModel, when opening my UI >> so that when widget is built for it, it will be my own widget, >> not PluggableTextMorph.. >> >> but i found it hard to do.. here what

Re: [Pharo-dev] Hijri calendar

Paul DeBruicker wrote > Chronos has: > ... > Is that what you want? The www.chronos-st.org seems to be gone. But there is http://smalltalkhub.com/#!/~Chronos/Chronos/ Thanks - I will have a look. Is it known to work in Pharo 3.0? Thx T.

Re: [Pharo-dev] GUI TestRunner failures not found by CI (was Re: [pharo-project/pharo-core] 1953a9: 30829)

On 23 Apr 2014, at 19:55, Ben Coman wrote: > Sven Van Caekenberghe wrote: >> And we're all GREEN, great work ! >> Let's keep it that way until release. >> Everything that breaks a test should now be reverted. >> >> > Thats great news. However while the CI monkey is great, there are still

Re: [Pharo-dev] Hijri calendar

Chronos has: "IslamicFatimidCalendar Concept: IslamicFatimidCalendar implements the Islamic Fatimid Calendar. The Islamic Fatimid Calendar (also called the Tabular Islamic Calendar) is an arithmetical variation of the Astronomical Islamic Calendar (the one most Muslims

[Pharo-dev] GUI TestRunner failures not found by CI (was Re: [pharo-project/pharo-core] 1953a9: 30829)

Sven Van Caekenberghe wrote: And we're all GREEN, great work ! Let's keep it that way until release. Everything that breaks a test should now be reverted. Thats great news. However while the CI monkey is great, there are still a few tests (at least in Windows) that fail in a fresh image

[Pharo-dev] Hijri calendar

Do we have support/code for that somewhere? Thx T.

Re: [Pharo-dev] [pharo-project/pharo-core] 1953a9: 30829

On 23 Apr 2014, at 19:21, Camille Teruel wrote: > > On 23 avr. 2014, at 19:00, Marcus Denker wrote: > >> >> On 23 Apr 2014, at 18:34, Marcus Denker wrote: >> >>> >>> On 23 Apr 2014, at 18:18, Sven Van Caekenberghe wrote: >>> And we're all GREEN, great work ! Let's keep it that

Re: [Pharo-dev] [pharo-project/pharo-core] 1953a9: 30829

On 23 avr. 2014, at 19:00, Marcus Denker wrote: > > On 23 Apr 2014, at 18:34, Marcus Denker wrote: > >> >> On 23 Apr 2014, at 18:18, Sven Van Caekenberghe wrote: >> >>> And we're all GREEN, great work ! >>> Let's keep it that way until release. >>> Everything that breaks a test should now

Re: [Pharo-dev] [pharo-project/pharo-core] 1953a9: 30829

On 23 Apr 2014, at 18:34, Marcus Denker wrote: > > On 23 Apr 2014, at 18:18, Sven Van Caekenberghe wrote: > >> And we're all GREEN, great work ! >> Let's keep it that way until release. >> Everything that breaks a test should now be reverted. >> > Yes! > > there are just two issues that are

Re: [Pharo-dev] [pharo-project/pharo-core] 1953a9: 30829

On 23 Apr 2014, at 18:18, Sven Van Caekenberghe wrote: > And we're all GREEN, great work ! > Let's keep it that way until release. > Everything that breaks a test should now be reverted. > Yes! there are just two issues that are for pharo3 with fixes: https://pharo.fogbugz.com/f/case

Re: [Pharo-dev] [pharo-project/pharo-core] 1953a9: 30829

And we're all GREEN, great work ! Let's keep it that way until release. Everything that breaks a test should now be reverted. On 23 Apr 2014, at 17:55, GitHub wrote: > Branch: refs/heads/3.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 1953a92ba18a036b8f469a69840f0597468abf

[Pharo-dev] [pharo-project/pharo-core]

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

[Pharo-dev] [pharo-project/pharo-core] 1953a9: 30829

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 1953a92ba18a036b8f469a69840f0597468abf32 https://github.com/pharo-project/pharo-core/commit/1953a92ba18a036b8f469a69840f0597468abf32 Author: Jenkins Build Server Date: 2014-04-23 (Wed, 23 Apr 2014

[Pharo-dev] [pharo-project/pharo-core] d208bb: 30828

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d208bbfc3a68d186259ec8baf2d5fafed3bbcce7 https://github.com/pharo-project/pharo-core/commit/d208bbfc3a68d186259ec8baf2d5fafed3bbcce7 Author: Jenkins Build Server Date: 2014-04-23 (Wed, 23 Apr 2014

[Pharo-dev] [pharo-project/pharo-core]

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

[Pharo-dev] [pharo-project/pharo-core] 67a6c7: 30827

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 67a6c79966cd1d06dfaac2d8192fdccaef2ab3d8 https://github.com/pharo-project/pharo-core/commit/67a6c79966cd1d06dfaac2d8192fdccaef2ab3d8 Author: Jenkins Build Server Date: 2014-04-23 (Wed, 23 Apr 2014

[Pharo-dev] [pharo-project/pharo-core]

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

Re: [Pharo-dev] Verifying Ubuntu downloads

On Tue, Apr 22, 2014 at 2:04 AM, Sean P. DeNigris wrote: > Arg... forgot to specify a dependent package. Uploading a new config now... > should work... nope, still same problem -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another wit

Re: [Pharo-dev] Confused by NewListExample

Ben wrote >What do you think is the reaction people have reading this mail? I expected something like: - looks like it needs some cleaning up, please go ahead; or - is no longer needed, should be removed; or - where are the issue numbers? Stephan

Re: [Pharo-dev] Confused by NewListExample

2014-04-23 11:01 GMT+01:00 Benjamin : > What do you think is the reaction people have reading this mail? > "NewList is awful, terrible, and eats babies"? Cheers, Sergi

Re: [Pharo-dev] Confused by NewListExample

What do you think is the reaction people have reading this mail? Ben On 22 Apr 2014, at 20:53, Stephan Eggermont wrote: > - title toggling doesn’t work > - doesn’t have a usable size > - window title not set > - dragging doesn’t work > - disallows selection in one place, > allows it somewhere

Re: [Pharo-dev] [Pharo CI] Linux slave problem solved

Thank you marcus ! On Wed, Apr 23, 2014 at 3:28 PM, Marcus Denker wrote: > Hi, > > The problem with the linux slaves is fixed… things should get normal again. > > " there was an inconsistency between libvirt (used on CloudStack's hypervisor > nodes) > and the configuration of system's locale. A

Re: [Pharo-dev] [Pharo CI] Linux slave problem solved

Thanks Marcus On 23.04.2014, at 10:28, Marcus Denker wrote: > Hi, > > The problem with the linux slaves is fixed… things should get normal again. > > " there was an inconsistency between libvirt (used on CloudStack's hypervisor > nodes) > and the configuration of system's locale. As a conseq

[Pharo-dev] [Pharo CI] Linux slave problem solved

Hi, The problem with the linux slaves is fixed… things should get normal again. " there was an inconsistency between libvirt (used on CloudStack's hypervisor nodes) and the configuration of system's locale. As a consequence, a CloudStack test was failing sometimes, leading to the removal of a