- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PetitParser in 3.0?

by Stephan Eggermont

Esteban wrote >This is a question for the moosers :) >Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella? That's a question of effort vs results. Moose builds on top of Pharo, which has no stable. There are newer builds of Pharo 3 containing bug-fixes. Moose has no Metacello way to identify which build it is running on so no way to create a stable. Moose is a large framework exercising large parts of the Pharo code base so almost all bug-fix releases impact Moose. The test suite of Pharo contains non-green tests so there is no easy way to track issues. In addition there are of course the issues in Moose development itself. Stephan

July 18, 2014

Re: [Pharo-dev] Fun With Pharo on ci

by stepharo

Super! I should migrate and revisit also some of my chapters. Stef On 17/7/14 22:01, Stephan Eggermont wrote: > Thanks to some help by Damien, we now have FunWithPharo > on ci. It generates the whole book and separate chapters. > > Stephan > >

July 18, 2014

Re: [Pharo-dev] Pharo Not For The Enterprise

by stepharo

>> I started Fun With Pharo :) >> >> https://github.com/SquareBracketAssociates/FunWithPharo > Good. I've added the chapter. Can I just copy the ci config from > PharoForTheEnterprise to generate book & chapters? > Anything else to do than change urls? adding chapters I will have a look now. I thought that I added a conf already. > > Stephan > >

July 18, 2014

Re: [Pharo-dev] Current maintainer of PharoExtras/LDAP?

by stepharo

Excellent! We loved such enhancements. I did not check but I imagine you can commit now to the repo? Stef On 17/7/14 12:08, Udo Schneider wrote: > > What are the changes ? > SSL: > * Addition of LDAPSConnection/LDAPSWorker and instance generation > methods (e.g. LDAPSConnection>>#to:port:ssl:) to use Zodiac Sockets > instead of regular sockets. Both classes support SSL and non-SSL > connection. So it might be worth rolling them into the regular > LDAPConnection/LDAPWorker > AD: > * Addition of LDAPSearchResultReference to handle ReferenceResults. > W/o this even something simple like searching the RootDSE fails. > * Addition of LDAP URLs (not working yet) to parse ReferenceResults > * Some convenience methods to search/create/delete AD Users and > Groups. Support for (Re)Setting Passwords ... this was quite PITA to > figure out BTW ... > Misc: > * Spec based LDAP Browser (http://udos.s3.amazonaws.com/LDAPBrowser.png) > > Just a summary (omitting some bits and pieces like fetching RootDSEs, > namingContexts ...) > > CU, > > Udo > > > On 17.07.2014 09:30, Olivier Auverlot wrote: >> LDAP is so important. Improving support for Active Directory and SSL >> is really a good idea. >> >> I used the framework in many projects with Pharo 1.3 and 2.0. It >> works very well. >> >>>> But I'm hitting a few issues now which would change the base packages. >> >> What are the changes ? >> >> Best regards >> Olivier :-) >> >> Le 16 juil. 2014 Ã 19:47, stepharo a Ã©crit : >> >>> >>> On 16/7/14 19:02, Udo Schneider wrote: >>>> All, >>>> >>>> I'm currently making some changes to the LDAP package to make it >>>> play nicer with ActiveDirectory and SSL. Up to now all those >>>> changes were non-intrusive to the current packages. But I'm hitting >>>> a few issues now which would change the base packages. >>>> >>>> What's the policy on this? >>> Improving :) >>> We need stronger and better libraries. >>>> Keeping those changes in my own fork or submitting them to a >>>> maintainer (who?). >>> >>> I gave you access to the PharoExtras repo. >>> Just add tests and build the best LDAP you want :) >>> Make sure that everything work well and suits your needs. >>> I'm not sure that current design is good. At least when olivier >>> auverlot showed to me I was skeptical about the chapter we/he wrote >>> on it. >>>> In addition ... as far as I can see the current package is Pharo >>>> only (was Squeak). >>>> If "Pharo-only" is o.k. I could for instance integrate my stuff for >>>> LDAP-over-SSL in there directly (based on Zodiac). >>> Excellent idea. >>> Our goal is to make sure that people can make business. >>>> >>>> Thanks, >>>> >>>> Udo >>>> >>>> >>>> >>> >>> >> >> >> > > > >

July 18, 2014

Re: [Pharo-dev] RFB broken

by stepharo

Damien what is this looking bad selector? #wordingProvider:wordingSelector: and who is invoking it? because we should simply use a default menu. Stef On 18/7/14 13:24, Damien Cassou wrote: > On Thu, Jul 17, 2014 at 8:49 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> http://www.samadhiweb.com/blog/2014.05.01.rfb.pharo3.html > > thank you very much, I pushed the fix to the RFB repository >

July 18, 2014

Re: [Pharo-dev] RFB broken

by Damien Cassou

On Thu, Jul 17, 2014 at 8:49 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > http://www.samadhiweb.com/blog/2014.05.01.rfb.pharo3.html thank you very much, I pushed the fix to the RFB repository -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Tudor Girba

Because nobody did it. Doru On Fri, Jul 18, 2014 at 12:04 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > This is a question for the moosers :) > Why there is no copy (with stable version) in metarepo of ll > configurations that are under the moose umbrella? > > cheers, > Esteban > > On 18 Jul 2014, at 10:00, phil(a)highoctane.be wrote: > > I load it from the moose team on sth. Works for me, browser included. > Le 18 juil. 2014 09:24, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > >> In the case of Moose, #development and #bleedingEdge are the same. >> >> Doru >> >> >> On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert(a)hartl.name> >> wrote: >> >>> I think what is loaded by CI is dependent on the workflow of the >>> project. IMHO for most projects loading #bleedingEdge is the best thing to >>> do. >>> >>> Norbert >>> >>> Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>> >>> It loads #development as any CI job should do. >>> >>> Doru >>> >>> >>> On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com >>> > wrote: >>> >>>> Stephan Eggermont wrote >>>> > And there is a image build at >>>> > https://ci.inria.fr/pharo-contribution/job/PetitParser/ >>>> >>>> Interesting. I wonder what the ci is loading, because if I try to load >>>> the >>>> default group in Pharo 3.0, I get an error (hence I load 'Core' and >>>> have no >>>> problems) >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> View this message in context: >>>> http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html >>>> Sent from the Pharo Smalltalk Developers mailing list archive at >>>> Nabble.com <http://nabble.com/>. >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Esteban Lorenzano

Hi, This is a question for the moosers :) Why there is no copy (with stable version) in metarepo of ll configurations that are under the moose umbrella? cheers, Esteban On 18 Jul 2014, at 10:00, phil(a)highoctane.be wrote: > I load it from the moose team on sth. Works for me, browser included. > > Le 18 juil. 2014 09:24, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > In the case of Moose, #development and #bleedingEdge are the same. > > Doru > > > On Fri, Jul 18, 2014 at 9:18 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I think what is loaded by CI is dependent on the workflow of the project. IMHO for most projects loading #bleedingEdge is the best thing to do. > > Norbert > > Am 18.07.2014 um 05:21 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > >> It loads #development as any CI job should do. >> >> Doru >> >> >> On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Stephan Eggermont wrote >> > And there is a image build at >> > https://ci.inria.fr/pharo-contribution/job/PetitParser/ >> >> Interesting. I wonder what the ci is loading, because if I try to load the >> default group in Pharo 3.0, I get an error (hence I load 'Core' and have no >> problems) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

July 18, 2014

Re: [Pharo-dev] Association dnu emitValue:

by Yuriy Tymchuk

Thank you! On 18 Jul 2014, at 11:01, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> I added tests in 099 to check that all binding are correct in Smalltalk globals and all classPools. >>> >>> It seems that someone is adding global somehow with the wrong class (Association instead of >>> GlobalVar (a subclass of Association). >>> >>> But #at:put: should do the right thing in SystemDictionaryâ¦ >>> >>> The most likely candidate is Undeclared handlingâ¦ yes, that has to be it. The unknown binding is >>> put into Undeclared as an association and then just moved over, while it should switch the type >>> (depending on if it is a global or a class var). >>> >>> I will fix that. >>> >>> as a workaround, you can add the method >>> >>> emitValue: methodBuilder >>> methodBuilder pushLiteralVariable: self. >>> >> I will add for now the workaroundâ¦ I found the place where to fix it, too, but that needs then some testing. >> >> > > This is now in update #100 > > Marcus

July 18, 2014

[pharo-project/pharo-core]

by GitHub

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

July 18, 2014