- Pharo-dev - lists.pharo.org

[Pharo-project] new unstable on gforge

by StÃ©phane Ducasse

https://gforge.inria.fr/frs/download.php/26970/PharoCore-1.1-11343-UNSTABLE…

May 8, 2010

Re: [Pharo-project] [vwnc] Survey: Changing method names in JNIPort?

by Tudor Girba

Hi Joachim, As far as I know, Pharo now supports underscores in method names. Am I wrong? Cheers, Doru On 8 May 2010, at 21:31, Joachim Geidel wrote: > Hello everybody! > > I am preparing to port JNIPort (the Smalltalk-to-Java interface) to > Squeak > and Pharo. However, there is a complication: Squeak and Pharo don't > accept > underscores in method names, while Dolphin and VisualWorks have no > problem > with underscores. JNIPort contains many methods with underscores. > > If you are a JNIPort user, I would like to hear what you think about > the > ways to solve this problem. Opinions from non-users are welcome, > too, of > course. > > I currently see two options: > > 1. I can keep the versions for all platforms in sync. Obviously, I > would > prefer this solution, as it is less work for me. On the other hand, > users of > JNIPort would have to get used to new naming conventions: > > - All underscores would be dropped from method names. As method > names for > generated methods include the type names of the arguments, this can > lead to > somewhat ugly looking names, as the usual camel case notation is not > necessarily respected. E.g., > get_int: would be replaced by getint: > get_Object:String: would be replaced by getObject:String: > In those simple cases, the new notation doesn't look much worse than > before. > > - Static fields in Java tend to have uppercase names with > underscores, which > I would have to drop, too: > get_MAX_VALUE -> getMAXVALUE > set_MAX_VALUE: -> setMAXVALUE: > This has a small potential for naming conflicts if two field names > in the > same class differ only by underscores. But you can always use lower > level > methods for accessing a field if the generated method is ambiguous. > > - For names of inner classes which contain a $ character, I can't > replace $ > by _ anymore, and would use 0 (zero) instead - it doesn't look much > worse > than the $ character in Java, and I can't come up with something > nicer which > is a legal character in a selector. > > 2. I could leave the VisualWorks version as it is, and maintain a > second > code branch for Squeak and Pharo. I don't like this solution, as it > means > more work for me. For JNIPort users, it would mean that their code > isn't > easily portable to Squeak. OTOH, it would preserve the current more- > or-less > nice-looking method names in generated classes. > > So, what do you think? > > Joachim Geidel > > > _______________________________________________ > vwnc mailing list > vwnc(a)cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

May 8, 2010

Re: [Pharo-project] Newbie: How to load and use HTTP parser

by Dennis Schetinin

You can try to ask (this or other questions) in Russian Smalltalk User Group also: http://groups.google.com/group/sugr/ :) 2010/5/7 Andrei Stebakov <lispercat(a)gmail.com> > Hi > > Sent this message to the Pharo-users group, but no response for a couple of > days, so trying it here ;) > > I have a simple task of parsing some html content in Pharo (loading an html > page using HTTPSocket and retrieving useful info from it). > Having browsed for an html parser in my current one-click Pharo 1.0 image, > I couldn't find one. > How do I find/download a (the) HTML parser? > > What's the general routine of discovering and installing packages in Pharo? > I believe in Squeak there was a menu to explore and download packages, I > couldn't find it in Pharo though. > > > Thank you, > Andrei > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Dennis Schetinin

May 8, 2010

Re: [Pharo-project] [Metacello] We need a UI for Metacello/Loader

by StÃ©phane Ducasse

+1 > I don't think a graphical user interface is what is important now. If you look at other package management systems, APT or RubyGems, they work very well just from the command line. With GoferProjectLoader we basically have this command line interface. > > What is much more important is a process. We need universes for the different Pharo versions and for the different maturity/compatibility states of packages (e.g., unstable, testing, and stable). We need somebody who sets up a process and keeps it running, and we also need package maintainers. > > We can list packages on a website (like packages.debian.org) This should make it possible for anybody to find the desired package and install it. > > Of course, a GUI would be nice to have. But without a high-quality package repository, it will be only of little use. > > I don't have much time left at the moment, but I can assist somebody who wants to get such a system up and running. I believe its going to be a very important step for Pharo.

May 8, 2010

Re: [Pharo-project] [Metacello] We need a UI for Metacello/Loader

by Adrian Lienhard

I don't think a graphical user interface is what is important now. If you look at other package management systems, APT or RubyGems, they work very well just from the command line. With GoferProjectLoader we basically have this command line interface. What is much more important is a process. We need universes for the different Pharo versions and for the different maturity/compatibility states of packages (e.g., unstable, testing, and stable). We need somebody who sets up a process and keeps it running, and we also need package maintainers. We can list packages on a website (like packages.debian.org) This should make it possible for anybody to find the desired package and install it. Of course, a GUI would be nice to have. But without a high-quality package repository, it will be only of little use. I don't have much time left at the moment, but I can assist somebody who wants to get such a system up and running. I believe its going to be a very important step for Pharo. Cheers, Adrian On May 8, 2010, at 18:54 , Mariano Martinez Peck wrote: > On Sat, May 8, 2010 at 5:48 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > >> Hi, >> >> Could you detail a bit the requirements? >> > > Hi Doru. Basically, you should be able to use the GoferProjectLoader actions > from a UI. In this link you can see all the actions: > > http://www.smallworks.com.ar/en/community/GoferProjectLoader > > Look where it says "Usage". I past here them just in case: > > list Answers a collection with all available projects on configured > repositories > search: Answers a collection of projects matching the string > managed Answers a collection of currently managed project names > availableVersionsOf:Answers a collection of available versions of project. > WARNING: this command actually installs the configuration package if not > present > versionOf: Answer current version of project > attributesOf: Answer current attributes of project. The answer is a > Dictionary with following keys: Author, Timestamp, Description > repository: Adds a repository to current list of repositories, this > repostory works just for this instance of GoferProjectLoader > repository:username:password: Same to #repository:, but also adds user > identification > rememberRepository: Adds a persistent repository to current list of > repositories > rememberRepository:username:password: Same to #rememberRepository:, but also > adds user identification > removeRepository: Removes a persistent repository > load: load a project > load:group: load latest stable version of project, just the selected groups. > A group can be a string (e.g. âdefaultâ) or a collection of strings (e.g. > #(âCoreâ âTestâ) > load:version: load a specified version of project > load:version:group: load a specified version and group(s) of project > update Updates all configuration files for managed projects, and answers a > list of new versions available for each project (if there is new versions) > update: Update the configuration for specified project > upgrade Upgrade all managed projects with new versions if any available. *Be > careful, this option can lead to a unusable image* > upgrade: Upgrade specified project with latest stable version if it is newer > than the version installed > upgrade:version: Upgrade specified project with specified version > upgrade:version:group: Upgrade specified project with specified version and > group(s) > > Of course, we can release a first version with the most important actions > and then a second or third with the rest. > > Cheers > > Mariano > > > > >> Cheers, >> Doru >> >> >> >> On 8 May 2010, at 16:53, Mariano Martinez Peck wrote: >> >> Hi folks. First of all let me clarify that all this email is though for >>> new comers. >>> >>> I think Metacello is a wonderful project and that's why we are adopting it >>> in Pharo. I know Metacello has it's own UI: >>> >>> http://code.google.com/p/metacello/wiki/MetacelloTools >>> >>> I also know there is Metaceller done by Doru. >>> >>> But I think that the features Esteban Lorenzano implemented in >>> GoferProjectLoader are a MUST for a new comer. You can read them here: >>> >>> http://www.smallworks.com.ar/en/community/GoferProjectLoader >>> >>> Now...he doesn't plan to do a UI for that. My question if it would be a >>> good idea to "extend" Metaceller or Metacello-OB so that to uses >>> GoferProjectLoader features. Not necessary for Metacello 1.0 but maybe for >>> 1.1. I think this is important, at least for Pharo. We don't have Universe >>> neither SqueakMap anymore. >>> >>> Cheers >>> >>> Mariano >>> >> >> -- >> www.tudorgirba.com >> >> "The coherence of a trip is given by the clearness of the goal." >> >> >> >> >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 8, 2010

[Pharo-project] [update 1.1] #11343

by StÃ©phane Ducasse

11343 ----- - nextPut: returns its argument. rewrote all implementors of #nextPut: and #nextPutAll: to return their argument. Thanks lukas. Stef

May 8, 2010

Re: [Pharo-project] [Metacello] We need a UI for Metacello/Loader

by Mariano Martinez Peck

On Sat, May 8, 2010 at 5:48 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > Could you detail a bit the requirements? > Hi Doru. Basically, you should be able to use the GoferProjectLoader actions from a UI. In this link you can see all the actions: http://www.smallworks.com.ar/en/community/GoferProjectLoader Look where it says "Usage". I past here them just in case: list Answers a collection with all available projects on configured repositories search: Answers a collection of projects matching the string managed Answers a collection of currently managed project names availableVersionsOf:Answers a collection of available versions of project. WARNING: this command actually installs the configuration package if not present versionOf: Answer current version of project attributesOf: Answer current attributes of project. The answer is a Dictionary with following keys: Author, Timestamp, Description repository: Adds a repository to current list of repositories, this repostory works just for this instance of GoferProjectLoader repository:username:password: Same to #repository:, but also adds user identification rememberRepository: Adds a persistent repository to current list of repositories rememberRepository:username:password: Same to #rememberRepository:, but also adds user identification removeRepository: Removes a persistent repository load: load a project load:group: load latest stable version of project, just the selected groups. A group can be a string (e.g. âdefaultâ) or a collection of strings (e.g. #(âCoreâ âTestâ) load:version: load a specified version of project load:version:group: load a specified version and group(s) of project update Updates all configuration files for managed projects, and answers a list of new versions available for each project (if there is new versions) update: Update the configuration for specified project upgrade Upgrade all managed projects with new versions if any available. *Be careful, this option can lead to a unusable image* upgrade: Upgrade specified project with latest stable version if it is newer than the version installed upgrade:version: Upgrade specified project with specified version upgrade:version:group: Upgrade specified project with specified version and group(s) Of course, we can release a first version with the most important actions and then a second or third with the rest. Cheers Mariano > Cheers, > Doru > > > > On 8 May 2010, at 16:53, Mariano Martinez Peck wrote: > > Hi folks. First of all let me clarify that all this email is though for >> new comers. >> >> I think Metacello is a wonderful project and that's why we are adopting it >> in Pharo. I know Metacello has it's own UI: >> >> http://code.google.com/p/metacello/wiki/MetacelloTools >> >> I also know there is Metaceller done by Doru. >> >> But I think that the features Esteban Lorenzano implemented in >> GoferProjectLoader are a MUST for a new comer. You can read them here: >> >> http://www.smallworks.com.ar/en/community/GoferProjectLoader >> >> Now...he doesn't plan to do a UI for that. My question if it would be a >> good idea to "extend" Metaceller or Metacello-OB so that to uses >> GoferProjectLoader features. Not necessary for Metacello 1.0 but maybe for >> 1.1. I think this is important, at least for Pharo. We don't have Universe >> neither SqueakMap anymore. >> >> Cheers >> >> Mariano >> > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > > > > >

May 8, 2010

[Pharo-project] [update 1.1] #11341

by StÃ©phane Ducasse

11341 ----- - Issue 2171: add consistency in MC, Exception and other and a lot more like at:put: Stef and Lukas eating black chocolate in the cold spring (WTF with the weather..... no sunny seaside trip today)

May 8, 2010

[Pharo-project] [update 1.1] #11340

by StÃ©phane Ducasse

11340 ----- - Issue 2393: SocketStream changes from Trunk. Thanks lukas and Squeak :) Stef

May 8, 2010

Re: [Pharo-project] [Metacello] We need a UI for Metacello/Loader

by Schwab,Wilhelm K

A GUI is fine, but Esteban appears (IMHO - only he can speak for himself and his plans) to be tackling the void of a scriptable package system. By analogy to my evolving home away from Redmond, a graphical package manager is great when I want one thing; it starts to break down when somebody is telling me how to install all the packages I need to compile something from source, in which case I want a shell script with a bunch of apt-get lines. Esteban's code is probably going to be of greatest value to someone who begins to use Pharo and then is faced with the need to load many external packages into future images. One of the few things that Microsoft has gotten right over the years is COM versioning; it supports versioning by pointedly not supporting it. Want a new version? Make a new interface. That is exactly how I approach my own code. The only time I ever have to mess with it is to periodically make sure I have a loadable copy of my work, and (the big one) when it comes time to build a new image. The things that need to be done are: (1) find all code that I appear to have touched, so I won't loose work; (2) save all of my work in ONE STEP (maybe fewer<g>) (3) provide ONE THING that I load into my next image, and it loads everything else in ONE STEP, with the ability to break it down if things go wrong. I don't care about version of my code; I just need to save its current state and load that into the next image. For external packages, I hope not to care much about versions. I might want to specify a given verion of Seaside, and after that, I will typically want the latest of a given list of packages. When somebody lets me down, I will want to override that version in specific cases. My evolving solution is in the form of Migrate, which I hope to be able to simplify over time thanks to Loader. GUI tools usually make it easy to spend a long time doing a bunch of small steps, such that what could be a simple task turns into an error prone nightmare. In general, GUIs are great for tinkering, and command lines and scripting are good for automation. We can have all the GUIs we want, but please note the importance of scripting. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Tudor Girba Sent: Saturday, May 08, 2010 10:48 AM To: metacello(a)googlegroups.com Cc: Pharo Development Subject: Re: [Pharo-project] [Metacello] We need a UI for Metacello/Loader Hi, Could you detail a bit the requirements? Cheers, Doru On 8 May 2010, at 16:53, Mariano Martinez Peck wrote: > Hi folks. First of all let me clarify that all this email is though > for new comers. > > I think Metacello is a wonderful project and that's why we are > adopting it in Pharo. I know Metacello has it's own UI: > > http://code.google.com/p/metacello/wiki/MetacelloTools > > I also know there is Metaceller done by Doru. > > But I think that the features Esteban Lorenzano implemented in > GoferProjectLoader are a MUST for a new comer. You can read them here: > > http://www.smallworks.com.ar/en/community/GoferProjectLoader > > Now...he doesn't plan to do a UI for that. My question if it would be > a good idea to "extend" Metaceller or Metacello-OB so that to uses > GoferProjectLoader features. Not necessary for Metacello 1.0 but maybe > for 1.1. I think this is important, at least for Pharo. We don't have > Universe neither SqueakMap anymore. > > Cheers > > Mariano -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal." _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 8, 2010