- Pharo-dev - lists.pharo.org

[Pharo-project] So...we freeze 1.1 ? (next steps?)
by Mariano Martinez Peck May 18, 2010

May 18, 2010

We said that for middle May we were going to freeze 1.1. This means, no more new features or refactors. Just bug fixes. So, the next steps can be: - Release a PharoCore1.1 with the last version we have so far tagged as alpha1 (please, put this tag in the zip, .image and .changes). This may be, for example: Pharo-1.1-11360-alpha1.image - Build and release a Pharo 1.1 alpha1 based on such core (now we have almost all dev tools working well in 1.1) - Make publish all new VMs (for each OS) Then the idea is that people/developers start to play with Pharo 1.1. It may be quite unstable as this is the first release for 1.1. People should try to load their own packages, adapt them (if necessary) to 1.1, and report all issues they find (and fixes!!). But they should keep in mind this the first alpha ;) With these, we will be testing: new VMs, PharoCore, PharoDev tools, and external packages (from other people). Pharo team at the same time, continues to work, fixing and integrating. We make new versions as we have been doing so far. When we consider, we release an alpha2....then beta, then RC and finally Pharo 1.1. now...do you think there is an issue that is so important to be fixed/included in the first Pharo1.1 even being a first alpha ? Cheers Mariano

8 28

[Pharo-project] Community Supported Packages
by Torsten Bergmann May 18, 2010

May 18, 2010

Hi, I tried to follow the discussion on both lists regarding supported packages and how/where to manage them by using Metacello. I can not give complete feedback since I go with GÃ¶ran here who said "I need to read your thoughts once more before giving proper feedback." and I think we all should take the time to think about all the implications the different approaches have. With this discussion we set up the base for the future of package maintenance but also for collaboration amongst the communities, how images are built, ...! I'm sure we all want to blur the line between in and out of the (whatever) image and share/reuse as many code/packages as possible within the broader community (Squeak, Pharo, Cuis, Gemstone, ...). So: Goal Nr. 1 is: if it is not in my environment then just load it. Goal Nr. 2 is: if it is loaded it should work in my environment since it brings in anything it needs to work Currently the discussion and actions seem to focus on where to put the configurations (into the image vs. in repositories per version). I'm in favour of the latter since that is easier to handle and share between platforms while having them in the image would limit people who work on various platforms, it would not scale and eat more resources for maintenance. My fear is also that if you have the configurations within the image then we all will end up with something similar to the unmaintained SqueakMap registrations. With external repos we can also feed CI-Tools (Hudson build server, ...) The only benefit from the "maintining configs in-image" would be that it would be easy to build a UI similar to SqueakMap/Universe Browser. This is something that has to be solved - especially for Pharo since loading/browsing it is not very "user friendly" today, but AFAIK work already started with the "Loader" project. Agree with Andreas that Metacello needs more work and a good browser of available configs would be a plus. But thats not the main question. Even if Squeak decides to have the configurations "in-image" and Pharo decides for external configs one can mix them: An in-image ConfigurationOfMyApp just loads the ConfigurationOfMyAppExternal where the last one is maintained in an external repo and the internal config is for convenience to just load it. However - I have to reread all the arguments and think about all this. <warning> But with a better acceptance of Metacello there will be more to come and to discuss! </warning> Lets think about the implications for anything above the virtual machine: Squeak is currently maintained as a "full image" using the trunk process while Pharo already switched to a "small core + external packages" model. The "pharo core" image (which is not Pharo!) is getting stable and hopefully smaller and one can already create a Pharo image right from the "ConfigurationOfPharo". That is there and working. I'm not saying that Squeak is not getting stable (I'm still a Squeak AND Pharo guy) but it is a different approach to build the end result that we later announce on our websites. If Squeak jumps on the Metacello config bandwagon it may also have to think about jumping onto the "small core + external packages" model. At least to me this would be the next logical step. This leads to several questions: - could this small core could be the same for all of us - especially since we currently fix stuff in Cuis, Squeak and Pharo mostly the same way - could this small core be reduced to a minimum set of objects and a loader that is able just suck in the things defined in package configurations of packages that work together - would any specific assembled/deployed image not just be a special distro of the "small kernel" + selected packages (similar to the linux world) So "Squeak" may later be the distro with media/fun/experimental packages or etoys and "Pharo" may later be the distro with packages oriented towards commercial development. However then the lines are blurred then and if you have the common core on your disk you can even create your own distro with Seaside and Etoys ... Pharo will follow the path "kernel" + selected packages" and external config path anyway since this is already discusssed and prepared. >From what I understand so far a repo for Pharo 1.1. will appear soon with freezed/working configs and a build structure will be set up. So lets see how this works out and if successfull if Squeak will adapt it too. Just my 2 cents. Expect additionally cents after getting more time to think about all this ... Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

4 3

[Pharo-project] HTTP Proxy server ...
by Geert Claes May 18, 2010

May 18, 2010

I can't seem to connect using a proxy server with network authentication. I have now successfully saved the HTTP proxy server and port number as well as the user name and password. I am using 1.1 using the new Settings browser and successfully updated the settings in "MyOwn" settings style. Also, how can I set the "use automatic configuration script"? Is there maybe a way for the VM to detect the proxy settings somehow just like a web browser detects the network/proxy settings from the host OS? http://n4.nabble.com/file/n2220967/Network_Settings.png -- View this message in context: http://forum.world.st/HTTP-Proxy-server-tp2220967p2220967.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] Decoding bug with XMLParser ?
by Damien Pollet May 18, 2010

May 18, 2010

Hi, I have a failing test to show the problem, but I can't commit to the XMLSupport squeaksource, so I attach the MCZ here. Basically, if I parse an UTF-8 document with an entity like … (ellipsis), I don't get a Character with the correct #codePoint. Cheers, -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 3

[Pharo-project] Pharo1.1 alpha image?
by Fernando olivero May 18, 2010

May 18, 2010

Clicking on download does not work, and i cant find the Pharo1.1 alpha image. http://www.pharo-project.org/home Version 1.1 alpha (unstable) If you want to use all the new features and improvements (e.g., performance) that have been added to Pharo lately, and you don't mind living on the bleeding edge, then download the current Pharo 1.1 alpha.

2 1

[Pharo-project] Fwd: [squeak-dev] I really miss a binary bitOr: selector for integers
by StÃ©phane Ducasse May 18, 2010

May 18, 2010

> > > send code with a nice comments and a test and it will be in 1.1 :) > > Stef > > On May 18, 2010, at 3:26 AM, Igor Stasenko wrote: > >> Hello, >> C world using bitor-s extensively for passing various flags and options. >> >> And porting the code looks really awful with #bitOr: , because it >> requires braces when you combining more than 2 flags. >> >> Can we , please , please, include #| as an alternative selector for >> bitor-ing integers into a kernel? >> >> Btw, Alien alredy adds it as extension. But i would really like to get >> it into the core, so any other may use it. >> >> Meanwhile, i defined own awfull extension selector - #++ >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > >

1 0

[Pharo-project] condensing changes file
by laurent laffont May 18, 2010

May 18, 2010

Hi, I've just started playing with ConfigurationOfPharo 1.1 and I'm currently experiencing the looooong "condensing changes file". I have currently troubles trying to follow all the traffic of this mailing-list :) but is there some work to make it far less longer ? or optional ? Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

3 5

[Pharo-project] Decoupling Shout and Styler
by Fernando olivero May 18, 2010

May 18, 2010

I would like to decouple the Styler Object ( For example SHTextStyler) from the Shout packages. Since Shout purpose it to add: 'Syntax Highlighting that updates after each key stroke so that the highlighting remains correct during the editing of a method'. I think it would be beneficial to style any piece of text, independently from the editing of a method. For example, when working on the NewTextMorph i do not need any functionality of the TextMorphForShout or TextMorphForShoutEditor classes, but only the Styler related classes. And in its current state, these two are coupled in the same package. I propose Shout could be spitted into 2 packages, that better reflect the classes intentions. 1. Code Styler: which would include Shout-Parsing, and Shout-Styling. 2. TextMorphShout: Shout-TextSupport, Shout-Windows. What do you think? Fernando

4 4

[Pharo-project] I really miss a binary bitOr: selector for integers
by Igor Stasenko May 18, 2010

May 18, 2010

Hello, C world using bitor-s extensively for passing various flags and options. And porting the code looks really awful with #bitOr: , because it requires braces when you combining more than 2 flags. Can we , please , please, include #| as an alternative selector for bitor-ing integers into a kernel? Btw, Alien alredy adds it as extension. But i would really like to get it into the core, so any other may use it. Meanwhile, i defined own awfull extension selector - #++ -- Best regards, Igor Stasenko AKA sig.

2 1

[Pharo-project] [Bug] Refactoring does not respect formatting
by Sean P. DeNigris May 18, 2010

May 18, 2010

http://code.google.com/p/pharo/issues/detail?id=2439 We are currently working on version 1.1, so please verify your issue with the latest 1.1 Unstable version before reporting it - we improved a lot the system. Pharo image: Pharo-core Pharo core version: 1.1 #11364 Virtual machine used: Squeak 4.2.4beta1U (mac) Class browser used (if applicable): OBSystemBrowserAdaptor Steps to reproduce: 1. Start with clean image 2. Install OB with: 3. Select line "(MCPackage named: 'ProjectNotNamedForRepo') unload." from following method: testFromSqueakSourse "" ImageSetup new installProject: 'ProjectNotNamedForRepo' fromRepository: 'ProjectNamedForRepo'. (MCPackage named: 'ProjectNotNamedForRepo') unload. SystemOrganization removeCategory: 'ProjectNotNamedForRepo'. 4. Extract method via refactor source->extract method 5. Result does not respect whitespace and formatting: testFromSqueakSourse "" ImageSetup new installProject: 'ProjectNotNamedForRepo' fromRepository: 'ProjectNamedForRepo'. self projectShouldBeInstalled. self shouldnt: [ Smalltalk at: #ClassInProjectNotNamedForRepo ] raise: Error. self extracted. SystemOrganization removeCategory: 'ProjectNotNamedForRepo' Issue was discussed in 9/09 at: http://forum.world.st/Is-there-a-way-to-use-rename- refactor-while-preserving-whitespace-formatting-in-refactored-methods- td1302148.html#a1302148 Ideas were: * write your own formatter that formats as you like * implement Gwenael's changes to the RBParser and AST, which preserve code formatting * use tools implemented in OB-Regex Sean -- View this message in context: http://forum.world.st/Bug-Refactoring-does-not-respect-formatting-tp2220567… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1