- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Instruments for headless images

by Sven Van Caekenberghe

On 21 Jan 2011, at 11:19, Igor Stasenko wrote: >> What is interesting (and we might make that an option) is that the 'no display' error results in the image being saved 'headfull' so that you can start it up using a display to debug it (suspended process/debugger). > > That could be done.. but not as userful as simply report an error. > Usually we (developers) knowing what we want to do, > and what i don't want to see in my headless image is any attempts to > access display/ui. Yeah, that's why I said it would better be an option. The first thing to do is simply report the error (and quit, or maybe that should be an option too). But many people playing with headless images (myself included) have had blocking/locked up images: having a log would be great, but adding this option to debug the cause further would be great. Sven

Jan. 21, 2011

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

by pharo＠googlecode.com

Updates: Status: Accepted Comment #7 on issue 3419 by marcus.d...(a)gmail.com: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing http://code.google.com/p/pharo/issues/detail?id=3419 (No comment was entered for this change.)

Jan. 21, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Comment #8 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 12316 TODO: 1.3

Jan. 21, 2011

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

by pharo＠googlecode.com

Updates: Status: Closed Labels: -Milestone-1.2 Comment #6 on issue 3419 by marcus.d...(a)gmail.com: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing http://code.google.com/p/pharo/issues/detail?id=3419 Workaround 12316. Not to be appled to 1.3

Jan. 21, 2011

Re: [Pharo-project] Instruments for headless images

by Igor Stasenko

On 21 January 2011 11:04, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Igor, > > Headless support is an important feature. > It should be something simple so that it can be used in many ways. > I would suggest to read chapter 20 of the VW Application Developers Guide (it is only 10 pages). > > They basically have the option to toggle between headless and headfull. > This is not detected automatically, but a global switch (with a test method). > > In headless mode all display access results in an error. yes. > In headless mode all Transcript output (can/is) also sent to a file (stdout would be another option). > yes > What is interesting (and we might make that an option) is that the 'no display' error results in the image being saved 'headfull' so that you can start it up using a display to debug it (suspended process/debugger). That could be done.. but not as userful as simply report an error. Usually we (developers) knowing what we want to do, and what i don't want to see in my headless image is any attempts to access display/ui. > Saving a headless image headfull can also be done programmatically. > > I don't think more than that is needed. There are many options to interact with headless images, forcing one on people would not be good, the same goes for command line parsing, preferences, startup files, ... These other options could become separate projects. > well, again, when people running image(s) in headless mode, they are know what they doing, and i think their default expectation is that image(s) should be aware that it runs headless and do not try to invoke anything which requires user interaction (like yes/no dialog) , because this does not makes any sense. > I would be an interested user and if I can will try to help. > > Regards, > > Sven > -- Best regards, Igor Stasenko AKA sig.

Jan. 21, 2011

Re: [Pharo-project] Issue 3465 in pharo: Hundson OneClick: Does not show Mac menues

by pharo＠googlecode.com

Comment #1 on issue 3465 by marianopeck: Hundson OneClick: Does not show Mac menues http://code.google.com/p/pharo/issues/detail?id=3465 This is related with Cog. The same image works perfectly with a Standard VM. ------- Hi. I am testing a Pharo image from here: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/lastSuccessfulBuild/… and the Mac host menu doesn't appear at all. I checked with SmalltalkImage current listLoadedModules SmalltalkImage current listBuiltinModules and MacMenubarPlugin is included. However, evaluating "HostSystemMenusMacOSX new " will throw a 'primDeleteMenu: failed' Why the image doesn't throw any error??? Look in HostSystemMenus >> startUp: resuming resuming ifFalse: [^self]. self clearDefault. [self setDefaultMenuProxyClass] ifError: []. So....indeed, setDefaultMenuProxyClass is throwing an error...but we are puting it under the carpet. Anyway, does someone know why this is not working in Cog? because In the standard VM in works perfect. Cheers Mariano

Jan. 21, 2011

Re: [Pharo-project] Issue 3520 in pharo: Workspaces do not recognize previously evaluated temps

by pharo＠googlecode.com

Updates: Status: Fixed Comment #7 on issue 3520 by marcus.d...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 (No comment was entered for this change.)

Jan. 21, 2011

[Pharo-project] [update 1.3] #13007

by Marcus Denker

13007 ----- Issue 3520: Workspaces do not recognize previously evaluated temps -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 21, 2011

[Pharo-project] Gofer issue

by Torsten Bergmann

Lukas wrote: >Looks good, but instead of duplicating the documentation I would >rather just return the class comment from the help method. Feel free to do so. I just wanted to point you to the fact that you can already use the pier style notation to document stuff. Hope we will now see more docu popping up. And it is now possible to easily extend the help system with other pragma/non pragma based help types. We could have others like <rssHelp: 'url'> and the like in the future. Some more notes on WikiStyleHelp: Currently it uses pier in <wikiStyleHelp:> as default since Alain provided the code for that but in the future I would like to see more syntaxes. Thats already prepared since you can also write <wikiStyleHelp: 'bookName' syntax: #pier Bye T. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

Jan. 21, 2011

Re: [Pharo-project] Issue 3419 in pharo: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing

by pharo＠googlecode.com

Updates: Status: Fixed Comment #5 on issue 3419 by jannik.l...(a)gmail.com: TraitCompositionTest>>testProvidedMethodBindingsWithConflicts is failing http://code.google.com/p/pharo/issues/detail?id=3419 Fixed for Pharo1.2 We remove the test In SLICE-Issue-3419-TraitCompositionFail-janniklaval.1

Jan. 21, 2011