- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Mariano Martinez Peck

On Fri, May 21, 2010 at 6:35 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > There is no warning when you try to access a monticello repository > with a password and you enter the wrong password. > The repository just look empty. > > This this is wrong from my point of view. Anyway, wasn't it like that also in 1.0 ? can you check ? Thanks Mariano > 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi Pharaoers. I am pleased to announce the first Pharo 1.1 beta based on > > PharoCore-1.1-11367-Beta. It is the first time we build a Pharo 1.1 dev > > image with PharoCore 1.1 so the image may be not 100% stable. However, we > > think it is good to release it so that people can start to test it, load > > their own packages, adapt them, etc. We would like to receive feedback > about > > it. It (yet) has failing and error tests. > > > > The main changes with Pharo 1.0 is that of course, it is based on a > > PharoCore 1.1 with all that it means. We started to write down some of > the > > actions done in PharoCore 1.1. The list so far can be found here: > > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotOne > > Of course, for the stable releae of Pharo 1.1 we will do a clear list in > the > > website as we did for 1.0. > > > > Regarding the included packages in 1.1 we added ScriptManager (a tool to > > manage and persist workspaces), ProfStefBrowser, ArchiveViewer, > > MethodWrappers and ObjectMetaTools (which includes things like > > ProtocolCatcher, ObjectTracer, ObjectViewer, etc). > > > > Another difference is the font. In Pharo 1.0 we used TrueType fonts by > > default. In Pharo 1.1 we use StrikeFonts (no need of TrueType plugin, > > netiher to have the fonts). However, of course, you can disable > StrikeFonts > > and put TrueType like in 1.0. > > > > That's all. We would really appreciate you use it, test it, report > issues, > > provide fixes, etc. It is important also that you start to use your own > > packages/applications. There have been several changes in 1.1 that may > > require change in your code. > > > > Ahh if you want to create the image yourself, check as usually the > > installScript.st file to see how to do it. Actually, you can just take a > > PharoCore-1.1-11367-Beta image and evaluate (the same procedure as 1.0): > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfPharo'; > > load. > > > > ((Smalltalk at: #ConfigurationOfPharo) project version: > '1.1-beta1.10517') > > load. > > > > Here is the link to the image: > > > > > https://gforge.inria.fr/frs/download.php/27025/Pharo-1.1-11367-Betadev10.05… > > > > Cheers > > > > Mariano > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2010

Re: [Pharo-project] Pier Book tool

by Geert Claes

Tudor Girba wrote: > > Now, when you are logged in as an editor, you should see the tree in the > footer, with the children of the current structure expanded. > I just logged in but I am still not sure where this tree is. The footer does have the commands toolbar (see attachement) http://n4.nabble.com/file/n2225761/Editor_Commands.png -- View this message in context: http://forum.world.st/Re-Pier-Book-tool-tp2225737p2225761.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

[Pharo-project] VM Preferences > System Configuration > Network Configuration...

by Geert Claes

I am just wondering whether the Network - HTTP proxy and network authentication - settings (from the much improved new Settings Browser by the way) should actually be moved to the VM Preferences under System Configuration just like the Printer Configuration. At home I use the Mac VM and I tend to take my image on a USB key and use the same image (how great is that) with the windows VM at work. I reckon the Network Settings are just like the Print Setup and depend on the environment where the VM is running and not necessarily the image. I assume the same goes for a developer who develops an app on one machine and deploys the image on a server? Anyway, just a thought :) -- View this message in context: http://forum.world.st/VM-Preferences-System-Configuration-Network-Configura… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

Re: [Pharo-project] Pier Book tool

by Tudor Girba

Hi, Indeed, the Sitemap was only accessible for admins. It was my mistake. I fixed it. Now, when you are logged in as an editor, you should see the tree in the footer, with the children of the current structure expanded. Cheers, Doru On 20 May 2010, at 13:44, Lukas Renggli wrote: >>>>> The toolbar icon above the edit area lists the embeddable items. >>>> >>>> Listing the embeddable items would be good, how do you list the >>>> embeddable >>>> items? The link or embed buttons above the edit area don't do >>>> anything? >>> >>> Any structure (page, figure, component, ...) is embeddable. I guess >>> that when you log-in you get some kind of a navigation tree that >>> shows >>> the structure, no? >> >> There the TOC, and the TOC has a Table of Figures showing the >> images and >> their title but no way to find out the name, which you need to >> embed the >> image no? I would also like to remove images but I have no idea >> where I can >> do that. > > That has nothing to do with the TOC and TOF. There should be a tree > with the complete structure of the book after you login. Maybe you > don't see it because you don't have the access rights, I don't know. > Please ask your administrator. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

May 21, 2010

Re: [Pharo-project] Where should I put ConfigurationOfGLMorphic

by Igor Stasenko

2010/5/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com>: > Hi, I made a very basic ConfigurationOfGLMorphic that manages it's > dependency on FFI. Where should I upload this configuration now? > Feel free to upload it into GLMorphic repository. > Regards, > Â Â Â Â Â Â Â Â Â Â Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 21, 2010

[Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Torsten Bergmann

>Thanks Torsten. I wasn't aware of such package. So..for next release I will >add a project reference from ConfigurationOfPharo to >ConfigurationOfHelpSystem No, please just add the package I've mentioned since the ConfigurationOfHelpSystem was before the integration into Squeak/Pharo and would load old code. Meanwhile we had adaptions (we dont have the Squeak support code in Pharo for instance and vice versa). Maybe we should remove ConfigurationOfHelpSystem since it now adds more confusion. >It is not clear for me where Help packages should be hosted. For >example, ScriptManager host its own Help package in its own repository. >But Metacello is in the HelpSystem repository. The book for Metacello was just a demo - typically I would expect them to be in the same repo as the code. I dont want a "docu only" repo - if it is close to the code it will be easier to know and maintain it. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 21, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Serge Stinckwich

There is no warning when you try to access a monticello repository with a password and you enter the wrong password. The repository just look empty. 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi Pharaoers. I am pleased to announce the first Pharo 1.1 beta based on > PharoCore-1.1-11367-Beta. It is the first time we build a Pharo 1.1 dev > image with PharoCore 1.1 so the image may be not 100% stable. However, we > think it is good to release it so that people can start to test it, load > their own packages, adapt them, etc. We would like to receive feedback about > it. It (yet) has failing and error tests. > > The main changes with Pharo 1.0 is that of course, it is based on a > PharoCore 1.1 with all that it means. We started to write down some of the > actions done in PharoCore 1.1. The list so far can be found here: > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotOne > Of course, for the stable releae of Pharo 1.1 we will do a clear list in the > website as we did for 1.0. > > Regarding the included packages in 1.1 we added ScriptManager (a tool to > manage and persist workspaces), ProfStefBrowser, ArchiveViewer, > MethodWrappers and ObjectMetaTools (which includes things like > ProtocolCatcher, ObjectTracer, ObjectViewer, etc). > > Another difference is the font. In Pharo 1.0 we used TrueType fonts by > default. In Pharo 1.1 we use StrikeFonts (no need of TrueType plugin, > netiher to have the fonts). However, of course, you can disable StrikeFonts > and put TrueType like in 1.0. > > That's all. We would really appreciate you use it, test it, report issues, > provide fixes, etc. It is important also that you start to use your own > packages/applications. There have been several changes in 1.1 that may > require change in your code. > > Ahh if you want to create the image yourself, check as usually the > installScript.st file to see how to do it. Actually, you can just take a > PharoCore-1.1-11367-Beta image and evaluate (the same procedure as 1.0): > > Gofer new > Â Â Â squeaksource: 'MetacelloRepository'; > Â Â Â package: 'ConfigurationOfPharo'; > Â Â Â load. > > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.1-beta1.10517') > load. > > Here is the link to the image: > > https://gforge.inria.fr/frs/download.php/27025/Pharo-1.1-11367-Betadev10.05… > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 21, 2010

Re: [Pharo-project] MetaSource demo app working again

by Sean P. DeNigris

Torsten Bergmann wrote: > > It should be no problem when you put the ExternalBrowser code > package into another repo until you can copy it to the > original repo. > > But the ConfigurationOfXXX should be continued on > squeaksource/MetacelloRepository which is read/write. > > So the configuration can point to the temporary location until the > package moves to the original one - but others can still > use the newer versions in ConfigurationOfXXX since they dont > care where the loaded packages are hosted... > Perfect, that's what I wanted to know. Sean -- View this message in context: http://forum.world.st/MetaSource-demo-app-working-again-tp2225100p2225586.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

Re: [Pharo-project] FFI Documentation

by Sean P. DeNigris

Igor Stasenko wrote: > > NB Pros: > * as well as for plugin, you can create new > functionality that doesn't exist in any library > * no need to recompile plugin/VM when you making a changes > * all your code is distributed with the Smalltalk code, > but there can be > complications with platforms > * fast - faster than any FFI implementation written in > C, and as fast as plugin primitive or even faster > > Cons: > * ?unsafe? - you have to provide a safety layers > (But hey, you have to deal with same sorts of stuff, > when writing plugin. No magician workers there) > > * harder to write > Yes, its harder than plain smalltalk - true. > But i can't say, that writing an assembler is harder than writing a > plugin's slang code. > If you writing a plugin, you should have an expertise, in VM internals > and how to build VM , etc etc > and if you writing an native code, you should have an expertise in > assembler as well as VM internals. > > So, they are different, and definitely much harder comparing to plain > smalltalk code, > but which one is easier is hard to tell. > Cool, I'm glad you wrote that. I've been following your posts about NB, and from that quick summary, I already have a much better understanding of where it fits into the "external code" picture. Sean -- View this message in context: http://forum.world.st/FFI-Documentation-tp2225148p2225585.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

[Pharo-project] Where should I put ConfigurationOfGLMorphic

by Javier PimÃ¡s

Hi, I made a very basic ConfigurationOfGLMorphic that manages it's dependency on FFI. Where should I upload this configuration now? Regards, Javier. -- Javier PimÃ¡s Ciudad de Buenos Aires

May 21, 2010