May 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Request write access to Pharo40Inbox

by Marcus Denker

On 29 May 2014, at 12:05, Attila Magyar <m.magyar3(a)gmail.com> wrote: > Sean P. DeNigris wrote >> what are the dependency mczs? > > SmartSuggestions. I'm still getting the Http 500 error. > The strange thing is that I checked again the settings, and the public wrote access is *disabled*. This means that there is a bug: I enabled it *twice* already.

May 29, 2014

Re: [Pharo-dev] Request write access to Pharo40Inbox

by Attila Magyar

Sean P. DeNigris wrote > what are the dependency mczs? SmartSuggestions. I'm still getting the Http 500 error. -- View this message in context: http://forum.world.st/Request-write-access-to-Pharo40Inbox-tp4760747p476082… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 29, 2014

Re: [Pharo-dev] we should add Pharo30 inbox

by Marcus Denker

On 29 May 2014, at 11:57, stepharo <stepharo(a)free.fr> wrote: > > On 29/5/14 09:45, Marcus Denker wrote: >> On 29 May 2014, at 08:42, stepharo <stepharo(a)free.fr> wrote: >> >>> Hi >>> >>> we should add Pharo 30 inbox because many changes for 40 have been published there. >>> >> Yes, for a whileâ¦ or we just copy over all the slices. >> >> We need to start again to systematically do issue tracker: >> >> e.g. on an issue like that: put a note that the slice is in the wrong repo and >> a note: Next Action: copy slice to Pharo4 inbox. > > I do not think that copying slice is a good idea. > And I would refrain to create bug entries because it takes so much time handling them. > It is either a bug entry or a entry in my private TODO list. To me the only difference is that in case b) I am the only one who will act, while the issue tracker more people can do things. Marcus

May 29, 2014

Re: [Pharo-dev] we should add Pharo30 inbox

by stepharo

On 29/5/14 09:45, Marcus Denker wrote: > On 29 May 2014, at 08:42, stepharo <stepharo(a)free.fr> wrote: > >> Hi >> >> we should add Pharo 30 inbox because many changes for 40 have been published there. >> > Yes, for a whileâ¦ or we just copy over all the slices. > > We need to start again to systematically do issue tracker: > > e.g. on an issue like that: put a note that the slice is in the wrong repo and > a note: Next Action: copy slice to Pharo4 inbox. I do not think that copying slice is a good idea. And I would refrain to create bug entries because it takes so much time handling them. > > This way all these things get to be tiny 10 second actions that we can step by > tiny step do efficiently. > > > Marcus >

May 29, 2014

Re: [Pharo-dev] Request write access to Pharo40Inbox

by Marcus Denker

I checked again and somehow the public write access was not enables. I enabled it and double checked: now it should work. On 29 May 2014, at 11:20, Pablo Herrero <pablodherrero(a)gmail.com> wrote: > BTW: I'm also getting 'Error: could not save version.' with response > '500 Internal Server Error'. Maybe's not the case but it was a > permissions problem the last time I stamble upon this. > > Also here: > > MCSmalltalkhubRepository > owner: 'Pharo' > project: 'Pharo40Inbox' > user: 'pabloh' > password: '*****' > > 2014-05-28 20:14 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> what are the dependency mczs? >> >> On May 28, 2014, at 4:40 PM, Attila Magyar [via Smalltalk] <[hidden email]> >> wrote: >>> What other details would you like to know? >> >> Cheers, >> Sean >> >> ________________________________ >> View this message in context: Re: Request write access to Pharo40Inbox >> >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 29, 2014

Re: [Pharo-dev] Request write access to Pharo40Inbox

by Pablo Herrero

BTW: I'm also getting 'Error: could not save version.' with response '500 Internal Server Error'. Maybe's not the case but it was a permissions problem the last time I stamble upon this. Also here: MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo40Inbox' user: 'pabloh' password: '*****' 2014-05-28 20:14 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > what are the dependency mczs? > > On May 28, 2014, at 4:40 PM, Attila Magyar [via Smalltalk] <[hidden email]> > wrote: >> What other details would you like to know? > > Cheers, > Sean > > ________________________________ > View this message in context: Re: Request write access to Pharo40Inbox > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 29, 2014

Welcome norizzk.com

by Johan Brichau

Hi all, Yesterday, a new web application built with Seaside in Pharo and deployed with GLASS in Gemstone/S was launched to the world: www.norizzk.com Norizzk.com is an innovative platform for risk-based test management. Watch the trailer on https://www.youtube.com/watch?v=MMqMwl6C-lk Once again, the use of Smalltalk, Pharo, Seaside and Gemstone has proven to be a competitive advantage in the development of a stunning innovative product. Some of you may well know the lead developer of this project, Veronica, who did her Phd as part of the RMoD team in Lille and the SOFT lab in Brussels. Over the past year, Veronica worked with Inceptive on this project and is now continuing the lead and development at the customer. The inceptive.be team wishes them good luck and we look forward to continue the development collaboration. http://jbrichau.github.io Johan

May 29, 2014

Re: [Pharo-dev] Dark Theme in Pharo 4

by kilon alios

I would also like to take a deep look and see if with your help can document the theming. You think that themes now are more coder friendly or is Dark theme still a hack ? On Thu, May 29, 2014 at 2:02 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > wellâ¦ we have to decide that (is trivial to implement, but it was not > working like that until now, soâ¦ maybe we need to rethink it :) ) > > Esteban > > > On 28 May 2014, at 19:59, kilon alios <kilon.alios(a)gmail.com> wrote: > > Ah ok . But why ? I assumed that a theme would take care of these things. > Especially the color of the font. > Î£ÏÎ¹Ï 29 ÎÎ±Ï 2014 1:54 Ï.Î¼., Î¿ ÏÏÎ®ÏÏÎ·Ï "Esteban Lorenzano" < > estebanlm(a)gmail.com> ÎÎ³ÏÎ±ÏÎµ: > >> wellâ¦ I just tried with #installFullTheme and it works fine. >> you are probably trying to do it trough settings browserâ¦ there, you need >> to chose the background, the completion background and the colorisation by >> yourself. >> >> Esteban >> >> On 28 May 2014, at 19:36, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> > using #installFullTheme? >> > thatâs super weirdâ¦ after all, Pharo4 is almost Pharo3 now, and I just >> merged inâ¦ >> > >> > Esteban >> > >> > On 28 May 2014, at 19:01, kilon alios <kilon.alios(a)gmail.com> wrote: >> > >> >> I don't know if you are aware of this, even though dark theme is >> integrated in Pharo 4 I see several problems that I dont have with my Pharo >> 3 install of Dark theme. >> >> >> >> 1) Pharo background appears still white >> >> >> >> 2) Code completion has also white background >> >> >> >> 3) fonts appear black in workspace and inside methods code. >> >> >> >> >> >> Most likely you are aware of this and I realise that Pharo 4 just >> started but I decided to report just in case. >> >> >> >> Just for the record Rubric workspace also has issues with Dark Theme. >> > >> >> >> >

May 29, 2014

Re: [Pharo-dev] we should add Pharo30 inbox

by Marcus Denker

On 29 May 2014, at 08:42, stepharo <stepharo(a)free.fr> wrote: > Hi > > we should add Pharo 30 inbox because many changes for 40 have been published there. > Yes, for a whileâ¦ or we just copy over all the slices. We need to start again to systematically do issue tracker: e.g. on an issue like that: put a note that the slice is in the wrong repo and a note: Next Action: copy slice to Pharo4 inbox. This way all these things get to be tiny 10 second actions that we can step by tiny step do efficiently. Marcus

May 29, 2014

Re: [Pharo-dev] is ClassOrganization>>#categories right?

by stepharo

Thanks nicolas it sounds like a good strategy. BTW: we will need help because now 40 is starting (and I have to handle a totally new house too so starting to paint paint fix paint and paint a bit more, sawing, drilling, .... :)) Stef > +1, that sounds better, then #protocols is not just another rename but > a value change. > > In that case, first revert #categories (remove --all--), > - #categories -> #categoriesAndPseudoCategories > - #realCategories -> #categories > backport to Pharo 3.1, deprecate it in 4.0 (grace period for package > maintenance...) > > One can allways arrange to add #categories later in a compatibility layer. > > Nicolas >

May 29, 2014