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

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

by Esteban Lorenzano

On 29 May 2014, at 09:01, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: > 2014-05-29 9:11 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > 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 ? > > (just noticed it right now): Try to revert to a "regular" theme and tell me what color is the text cursor, that should partially answer your question :D no, it is not a hack. Dark theme is a combination of two things: a refactor to move out hardcoded colors (they are everywhere) and the theme itself. the cursor color is also a hardcoded value someplace there (not the fault of the theme :P). but... #installFullTheme should be used between dark and lighter themes to restore all values. If you choose dark theme, to go back you should first execute: Pharo3Theme installFullTheme. that should restore everything as before. so wellâ¦ I do not like the theme design, but the dark theme is following its guidelines. Then is not a hack, but it has some limitations :) also, thatâs why it is integrated in Pharo4 and not in Pharo3â¦ most probably it need some iterations until is ready. Esteban > > Cheers, > Sergi

May 29, 2014

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

by Sergi Reyner

2014-05-29 9:11 GMT+01:00 kilon alios <kilon.alios(a)gmail.com>: > 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 ? > (just noticed it right now): Try to revert to a "regular" theme and tell me what color is the text cursor, that should partially answer your question :D Cheers, Sergi

May 29, 2014

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

by Nicolas Petton

I will have a look at it next monday. Cheers, Nico Marcus Denker <marcus.denker(a)inria.fr> writes: > 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. -- Nicolas Petton http://nicolas-petton.fr

May 29, 2014

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

by Attila Magyar

Now, it works for me too. -- View this message in context: http://forum.world.st/Request-write-access-to-Pharo40Inbox-tp4760747p476083… 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

> I added Sean, zeroflag and Pablo as contributors the the inbox > (as a workaround) FWIW I could upload to the Inbox right after you enabled the public write access for the second time (and before you add me as a contributor)

May 29, 2014

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

by Marcus Denker

On 29 May 2014, at 12:25, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 29 May 2014, at 12:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> 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. > > So, yes, it seems to be not saved, the public status flag. > > I added Sean, zeroflag and Pablo as contributors the the inbox (as a workaround) Marcus

May 29, 2014

[pharo-project/pharo-core]

by GitHub

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

May 29, 2014

[pharo-project/pharo-core] 860433: 40007

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 8604330899a4bc97d906b4a79687f913321a55a5 https://github.com/pharo-project/pharo-core/commit/8604330899a4bc97d906b4a7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-05-29 (Thu, 29 May 2014) Changed paths: M Nautilus.package/AbstractNautilusUI.class/class/menu/classesFixMenu_.st R Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/addFullClass.st A ScriptLoader40.package/ScriptLoader.class/instance/accessing/inboxRepository30.st M ScriptLoader40.package/ScriptLoader.class/instance/mc related utils/addHomeRepositoryToAllPackages.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script6.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40007.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Tools.package/AbstractTool.class/class/private/defineFullClassTemplate.st R Tools.package/AbstractTool.class/instance/class/addFullClassIn_.st Log Message: ----------- 40007 13257 Pointless class creation menu in Nautilus https://pharo.fogbugz.com/f/cases/13257 - add 30Inbox (to be removed later) http://files.pharo.org/image/40/40007.zip

May 29, 2014

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

by Marcus Denker

On 29 May 2014, at 12:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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. So, yes, it seems to be not saved, the public status flag. Marcus

May 29, 2014

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

by Marcus Denker

On 29 May 2014, at 12:01, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 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. I added the inbox. But this is not enoughâ¦ we would need to add the main repo, too, as for merging it needs the latest common ancestor (or maybe because we killed the 6MB of MC meta dataâ¦) Marcus

May 29, 2014