January 2011 - Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] Gofer issue

by Igor Stasenko

On 21 January 2011 10:16, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Igor, > > 2011/1/21 Igor Stasenko <siguctua(a)gmail.com>: >> On 20 January 2011 22:52, Lukas Renggli <renggli(a)gmail.com> wrote: >>>>> Following the coventions your name is 'Igor' and the package is on the >>>>> branch 'Stasenko'. Gofer proritizes the main branch. >>>> >>>> how about retrieving the latest version regardless of branch? >>>> Can you provide an example how to tell Gofer to load it? >>> >>> There is no such thing as the latest version in Monticello, unless you >>> download all versions and compare the timestamps. >>> >> >> why you saying like that? If i open this repo in monticello browser, i >> can clearly see what is the latest >> uploaded version. And i sure that MC browser does not downloads all >> versions from repository. > > I didn't checked the source code but it seems MC repository inspector > always sort the package list by version number and when you save a > package in the Monticello Browser you can edit the version number and > write a lower number, then you cannot concede the first in the list is > the latest cronologically. I don't know why the version number is > editable though. > Okay, i found the solution. Use Installer ! Installer monticello http: 'http://www.squeaksource.com'; project: 'VMMaker'; install: 'CMakeVMMaker' works well for me and loads correct *latest* version. > HernÃ¡n > > -- Best regards, Igor Stasenko AKA sig.

Jan. 21, 2011

Re: [Pharo-project] Instruments for headless images

by Sven Van Caekenberghe

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. In headless mode all Transcript output (can/is) also sent to a file (stdout would be another option). 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). 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. I would be an interested user and if I can will try to help. Regards, Sven On 20 Jan 2011, at 21:39, Igor Stasenko wrote: > Hello folks. > > I'd like to ask, if there any 'standartized' instruments for headless > images (or alike). > > I need a simple things: > - redirect all ToolSet/UIManager messages to Transcript > - redirect Transcript logging to file or stdout > > in short, these tools should serve a simple, yet important purpose: > - if image runs in headless mode, it should suppress anything which > expecting user interaction (like showing warnings with 'continue' > button) and either log such messages to file > or simply quit image with error message. > > Without such tool it is quite difficult to monitor, what happens with > your headless image.. unless you have RFB installed.. but that is > different and unrelated story. > > > I did a prototype once for Hydra (you can check it at > SqS/HydraVM/HydraVM.mcz package) > there are two subclasses: > - MorphicUIManager subclass: #HydraUIManager > - StandardToolSet subclass: #HydraDebugToolSet > > and > - WriteStream subclass: #HydraTranscript > > which can be installed as a Transcript. > > And in order to prepare image to run in headless mode, i issued: > ToolSet unregister: StandardToolSet. > ToolSet register: HydraDebugToolSet. > UIManager default: HydraUIManager new. > > Also, HydraTranscript > startUp does something like: > > TranscriptStream > newTranscript: (self basicNew initialize > on: (String new: 1000)) > > > With that i could run the image in headless mode, knowing that in case > of error or warning etc, all will be redirected to transcript, > moreover i even stopped the UI process, so it never run on headless images. > > I wonder if there are other work, which can offer similar, > and is there any way to detect that image are running in headless mode? > > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 21, 2011

Re: [Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by pharo＠googlecode.com

Updates: Status: Closed Comment #5 on issue 3556 by marcus.d...(a)gmail.com: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: http://code.google.com/p/pharo/issues/detail?id=3556 in 13006 and 12315

Jan. 21, 2011

Re: [Pharo-project] New chapter on OpenGL in Pharo

by HernÃ¡n Morales Durand

2011/1/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com>: > Hi! I just gathered many of my previous experiences trying to use opengl and > uploaded it to the pharo book. It would be nice if someone could check the > info, try to add more and mainly test the tips to see if they are working. Link? > With FFI OpenGL I'm getting an error while compiling a test method in Pharo which error? > 1.2 and some problems with underscore assignments and deprecations, we which problems? Menu -> System -> Settings Write underscore, hit Enter Check "Allow underscore as assignment" To change all underscores _ to := install AST and RB and evaluate: | environment change rule | environment := BrowserEnvironment new forPackageNames: #('YourPackageName'). rule := RBUnderscoreAssignmentRule new. SmalllintChecker runRule: rule onEnvironment: environment. change := CompositeRefactoryChange new. change changes: rule changes. change execute > should fix them but I don't think I have access to that repo. Also, loading > it involves many steps, having a ConfigurationOfFFIOpenGL would be awsome. > Please add anything you consider useful. > Regards, > Â Â Â Â Â Â Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires >

Jan. 21, 2011

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

by pharo＠googlecode.com

Comment #6 on issue 3520 by siguc...(a)gmail.com: Workspaces do not recognize previously evaluated temps http://code.google.com/p/pharo/issues/detail?id=3520 - this should fix the issue Attachments: workspace-bindings-fix.1.cs 869 bytes

Jan. 21, 2011