- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Igor Stasenko

On 31 August 2011 23:28, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. >>>> >>> >>> sorry, but if during development you need to do 2 commits of 20 >>> packages , calculate how much time it would take for you to >>> manuallly update a configuration for each update. >>> it is time sink. >>> >>> if you do that once per day, its okay.. but for every commit . no. its >>> is absurd. >>> >> unless there is an automated tool which can generate new configuration >> automatically, hidden in your sleeve .. :) > > there is a metacello browser that do that for you. > Now I do not know if it handles subproject. > The browser supports the process and use the MetacelloToolbox API. > > I should have a look when I will redo a complete pass on the metacello chapter. > > I wrote a memento so that we do not have to learn 35 pages to get all the details, but one page with the essential. > i need it. because manually updating configs is pain in the ass, and more than that is is error prone. > Stef > -- Best regards, Igor Stasenko AKA sig.

Aug. 31, 2011

Re: [Pharo-project] opening a text in a window

by StÃ©phane Ducasse

In latest 1.4 wk := Workspace new. wk contents: 'lkhkhkjhkjh'. wk toggleStylingActive. wk open so I imagine easily that we can define a better creation method but this one is working well. Stef On Aug 31, 2011, at 6:04 PM, Alexandre Bergel wrote: > hi! > > Is there a way to open a text in a window in Pharo? > Doing: Workspace openContents: 'hello world' > shows > <Screen Shot 2011-08-31 at 13.03.06.png> > > Is there a way to remove the syntax highlighting? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

Aug. 31, 2011

Re: [Pharo-project] opening a text in a window

by Igor Stasenko

(Workspace new contents: 'hello world') open opens without style hilite (it took me several minutes to figure out) this thing still severly broken.. for instance, why there is #contents: and #setContent: ?? Initially i tried to do: (Workspace openContents: 'hello world' ) textMorph beUnStyled as well as variations like: (Workspace openContents: 'hello world' ) toggleStylingActive but it has to effect. Broken, broken , broken. P.S. could someone explain me, why on Earth, a PluggableTextMorph has so much instance variables dedicated to styler: - nullStyler - shoutedStyler - styler - styled ??? isn't it a responsibility of an owner of morph to set a styler and based on what it sets (nil, null, shout or whatever else value) consider text as styled or not? Why on Earth, a PluggableTextMorph needs to care about it more than just having a 'styler' ivar? -- Best regards, Igor Stasenko AKA sig.

Aug. 31, 2011

Re: [Pharo-project] Pharo 1.3 release

by Henrik Johansen

On Aug 31, 2011, at 9:08 07PM, Sven Van Caekenberghe wrote: > > On 31 Aug 2011, at 20:04, Marcus Denker wrote: > >> No, honestly I just want to be ablet to release at all... Perfection (TM) is for the next release. >> > > but it is no longer in the image (see WorldState class>>#otherToolsOn:) > >>> Also, I think that it would be very cool if a normal user like me can take the image and run all unit tests and be amazed that they all pass: that would really inspire new users and instill a quality feeling. >>> >> Known bug, has something to do with networking. >> >> http://code.google.com/p/pharo/issues/detail?id=4495 > > Yeah, this is really weird, without all Network and Zinc tests the TestRunner completes its run (with some failures/errors). But running the Network and/or Zinc tests afterwards seperately just works (they even all pass). It must have something to do with resource cleanup. We should go over all tests and check a bit (hmm ;-). Still on the CI servers it works. > > Sven I really don't think it's related to sockets not being released and/or never signalled, in that case you'd not see 100% CPU utilization... What I DO know though, is running : - TraitTest - ZnClientTest Throws the system into a jiffy. My guess would be TraitTest doing something iffy without cleaning up properly. Why that iffyness would lead the VM to go into a hot loop when ZnClientTest does it's thing, I have no idea. Cheers, Henry

Aug. 31, 2011

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by StÃ©phane Ducasse

>>> >>> I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. >>> >> >> sorry, but if during development you need to do 2 commits of 20 >> packages , calculate how much time it would take for you to >> manuallly update a configuration for each update. >> it is time sink. >> >> if you do that once per day, its okay.. but for every commit . no. its >> is absurd. >> > unless there is an automated tool which can generate new configuration > automatically, hidden in your sleeve .. :) there is a metacello browser that do that for you. Now I do not know if it handles subproject. The browser supports the process and use the MetacelloToolbox API. I should have a look when I will redo a complete pass on the metacello chapter. I wrote a memento so that we do not have to learn 35 pages to get all the details, but one page with the essential. Stef

Aug. 31, 2011

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Igor Stasenko

On 31 August 2011 23:23, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> For development configuration is useless and just time sink. >> >> I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. >> > > sorry, but if during development you need to do 2 commits of 20 > packages , calculate how much time it would take for you to > manuallly update a configuration for each update. > it is time sink. > > if you do that once per day, its okay.. but for every commit . no. its > is absurd. > unless there is an automated tool which can generate new configuration automatically, hidden in your sleeve .. :) >> Alexandre >> >> >>> But for release it has completely different purpose: it helps us to >>> identify what exactly and what version of it will be put in final >>> version. And gives a simple and concrete answer how to reproduce it, >>> in case of need. >>> Since we're are Â talking about release, i don't see how we could do >>> that without configurations. >>> >>> Yes, sure it could be done manually to manifest all packages and their >>> version(s) included into release, but it still means that >>> someone has to do it one way or another. >>> >>> >>> On 31 August 2011 23:03, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> Marcus >>>> >>>> We only do what is possible :) >>>> >>>> Â Â Â Â - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. >>>> Â Â Â Â Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded. >>>> >>>> Â Â Â Â - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. >>>> Â Â Â Â Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress. >>>> >>>> So we will fix that either in 1.3 or in 1.4 as time allows it. >>>> And more more important: no stress we are payed enough to stress and do stuff that hurts us. >>>> >>>> Stef >>>> >>>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: >>>>> >>>>>> The image contains outdated versions of RB and OB that miss some >>>>>> critical fixes. >>>>> >>>>> How can I know? >>>>> >>>>> It is is build using the latest MetaCello config... if the config needs to be updated, >>>>> it needs to be updated. It does not happen by itself. >>>>> >>>>>> Also there some proposed fixes don't seem to be >>>>>> included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> >>>>>> yet? >>>>>> >>>>> No... I have not yet found the energy to do that. >>>>> >>>>> Â Â Â Marcus >>>>> >>>>> -- >>>>> Marcus Denker -- http://marcusdenker.de >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel Â http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

Aug. 31, 2011

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Igor Stasenko

On 31 August 2011 23:19, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> For development configuration is useless and just time sink. > > I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. > sorry, but if during development you need to do 2 commits of 20 packages , calculate how much time it would take for you to manuallly update a configuration for each update. it is time sink. if you do that once per day, its okay.. but for every commit . no. its is absurd. > Alexandre > > >> But for release it has completely different purpose: it helps us to >> identify what exactly and what version of it will be put in final >> version. And gives a simple and concrete answer how to reproduce it, >> in case of need. >> Since we're are Â talking about release, i don't see how we could do >> that without configurations. >> >> Yes, sure it could be done manually to manifest all packages and their >> version(s) included into release, but it still means that >> someone has to do it one way or another. >> >> >> On 31 August 2011 23:03, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Marcus >>> >>> We only do what is possible :) >>> >>> Â Â Â Â - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. >>> Â Â Â Â Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded. >>> >>> Â Â Â Â - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. >>> Â Â Â Â Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress. >>> >>> So we will fix that either in 1.3 or in 1.4 as time allows it. >>> And more more important: no stress we are payed enough to stress and do stuff that hurts us. >>> >>> Stef >>> >>>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: >>>> >>>>> The image contains outdated versions of RB and OB that miss some >>>>> critical fixes. >>>> >>>> How can I know? >>>> >>>> It is is build using the latest MetaCello config... if the config needs to be updated, >>>> it needs to be updated. It does not happen by itself. >>>> >>>>> Also there some proposed fixes don't seem to be >>>>> included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> >>>>> yet? >>>>> >>>> No... I have not yet found the energy to do that. >>>> >>>> Â Â Â Marcus >>>> >>>> -- >>>> Marcus Denker -- http://marcusdenker.de >>>> >>>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Best regards, Igor Stasenko AKA sig.

Aug. 31, 2011

Re: [Pharo-project] opening a text in a window

by Jimmie Houchin

Your welcome. I also just explored and learned this. I can also do this. tt := ThreadSafeTranscript new. tt openAsMorphLabel: 'My Transcript'. tt show: 'my content';cr. tt clear. tt show: 'my new content';cr. Seems to work as what I was originally hoping for. No syntax highlighting and no quoting as a comment required. Thought maybe this would be helpful to anyone in like situation. This is in a Pharo 1.3 image. Thanks. Jimmie On 8/31/2011 12:42 PM, Alexandre Bergel wrote: > Thanks for your help. > > Alexandre > > > On 31 Aug 2011, at 14:15, Jimmie Houchin wrote: > >> On 8/31/2011 11:04 AM, Alexandre Bergel wrote: >>> hi! >>> >>> Is there a way to open a text in a window in Pharo? >>> Doing: Workspace openContents: 'hello world' >>> shows >>> <Mail Attachment.png> >>> >>> Is there a way to remove the syntax highlighting? >> I have recently been using >> ws := Workspace openLabel: 'A Nice Label'. >> ws contents: '"', 'my contents', '"'. >> >> ie: wrapping the contents with doubles quotes which simply make the contents a comment in the workspace. >> >> This is what I noticed was being used for the workspaces opened in in new image. >> >> I do wish we had a simple text box to receive such content which was not necessarily meant for syntax highlighting. >> >> I am using Workspace in my situation to provide progress updates on background processes which take hours to accomplish their task. >> >> I don't know if any of the recent work towards improving Transcript helps here. For me I would want an independent Transcript which I label and control. Not the general Transcript. >> >> Hope this helps. >> >> Jimmie

Aug. 31, 2011

Re: [Pharo-project] [Pharo-users] PLEASE HELP testing Pharo 1.3 One Click [WAS] Pharo 1.3 release

by Alexandre Bergel

> For development configuration is useless and just time sink. I strongly disagree. Metacello was sold to please users. Actually, I use it for me, the developper. I create a new version at each commit. It works wonderfully. Alexandre > But for release it has completely different purpose: it helps us to > identify what exactly and what version of it will be put in final > version. And gives a simple and concrete answer how to reproduce it, > in case of need. > Since we're are talking about release, i don't see how we could do > that without configurations. > > Yes, sure it could be done manually to manifest all packages and their > version(s) included into release, but it still means that > someone has to do it one way or another. > > > On 31 August 2011 23:03, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Marcus >> >> We only do what is possible :) >> >> - for the configurations of let us take what exist. We cannot control everything. I do not have the time and knowledge for that. >> Lukas decided that configurations are evil. Ok perfect now we fix them when we know what should be loaded. >> >> - Then for example to integrate the broken highlight I need the code first. I still do not know which slice to load in 1.3. >> Two days ago I spent time on it loading the wrong slice. So I decided that I will not stress. >> >> So we will fix that either in 1.3 or in 1.4 as time allows it. >> And more more important: no stress we are payed enough to stress and do stuff that hurts us. >> >> Stef >> >>> On Aug 31, 2011, at 8:22 PM, Lukas Renggli wrote: >>> >>>> The image contains outdated versions of RB and OB that miss some >>>> critical fixes. >>> >>> How can I know? >>> >>> It is is build using the latest MetaCello config... if the config needs to be updated, >>> it needs to be updated. It does not happen by itself. >>> >>>> Also there some proposed fixes don't seem to be >>>> included <http://code.google.com/p/pharo/issues/list?q=milestone%3D1.3> >>>> yet? >>>> >>> No... I have not yet found the energy to do that. >>> >>> Marcus >>> >>> -- >>> Marcus Denker -- http://marcusdenker.de >>> >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 31, 2011

Re: [Pharo-project] RB API

by StÃ©phane Ducasse

>> > > I think it is a very bad idea to integrate the refactoring engine into > the system, but I guess we don't have to discuss that again. This is simple. If nobody maintains the Configuration then it means that this is impossible to load it automatically We do not want a script we want a metacello spec for obvious reason. And it means that we are always confused and we do not know what is the latest version and on which repository it is. Then we do not want it to take 20 min to load because in that case it means that we will never be able to load it to integrate and work on core. Because when we work on core and integrate and fix things we generate images sometimes every 5 minutes so a jenkins server does not help at all. We want powerful tools to work on core so the only solution is to load it in core for now. The situation could be better if everybody would help but this is not the case so we will live with that and see if fuel can help us speeding up all the process. But right now we should close other efforts. Stef >> because you know, for you , as an author (and/or maintainer) of it >> things look pretty straightforward, but for people who only get >> started they apparently not. > > No, the refactoring engine is not an easy piece of software. It took > me many years to fully understand it before I could start to fix and > improve it. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 31, 2011