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

Re: [Pharo-project] Doing research with the iPad

by Marcus Denker

On Mar 3, 2011, at 3:03 PM, Alexandre Bergel wrote: > Hi Guys, > > I am conscious this email is a bit out of topic. But you may have a valuable experience to share > I am just wondering whether some of you tried to: > - do some latexing on iPad > http://www.vancapy.com/textouch/ He provides for free a latex compile server... so if you have network connection, this is a full Latex environment. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 3, 2011

Re: [Pharo-project] About RPackage

by Henrik Johansen

On Mar 3, 2011, at 2:01 52PM, Alexandre Bergel wrote: >>> This was the decisions that two of us (I mean me and you) took :). >>> >>> Categories are mapped one-to-one to RPackages. The reason is that this is the simplest path to replace categories in the system. >> >> >> Doru I'm afraid that it will not work because it means that suddenly people will have to change all the configurationOf. >> We should come up with a smooth transition phase (now this is true that if we could get rid of categories it would be good) > > PackageInfo and RPackage cannot coexist? It's been awhile since I looked at RPacakge, but... Not if you want a clean transition, you either use one, or the other. Trying to maintain the package structure in two systems at a time can only lead to trouble, especially when they do not have the same constraints. (RPackage is not tied/derived from to category classification like PackageInfo is) > > In any case, it will not be a problem for me to update all my config with this new schema. > > Alexandre I'm not sure what you mean by configs. The contents of a Monticello package is simply a collection of definitions, and will stay the same. The browser will probably need updating though, since extensions no longer necessarily have to be in a *packagename category . Loading a Monticello package stored from an RPackage-based system into a system still using PackageInfo might cause false dirties , for the same reason. As long as there is no package browser as standard (like there is in VW), and people still specify extensions by using * categories in a system browser, that's not likely to be a big issue though. RPackage does make it much easier to create a performant package browser though :) Cheers, Henry

March 3, 2011

[Pharo-project] Doing research with the iPad

by Alexandre Bergel

Hi Guys, I am conscious this email is a bit out of topic. But you may have a valuable experience to share I am just wondering whether some of you tried to: - do some latexing on iPad - run Pharo on it These are the two basic things that I constantly do with my laptop (including web browsing and mails). Can I throw my laptop for an ipad? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 3, 2011

Re: [Pharo-project] GUI ?

by Olivier Auverlot

Le 03/03/11 13:32, Schwab,Wilhelm K a Ã©crit : > Morphic is a long-standing UI framework for Squeak, taken from Self. Morphic was a nice simulation environment, but Squeak's GUI really needed someone to either replace Morphic entirely, or to at least use it to simulate a user interface consistent with the "feel" (what the GUI does in response to user input) users have learned to expect. The first attempt to do that was Jim Benson's Zurgle, which the Squeak community completely marginalized. If Zurgle had a failing, it was dependence on external files, but a simple theme could have addressed the concerns. > > Time passes. Gary Chambers of Pinesoft announced Polymorph, and offered to make it available if anyone were interested in using it. A repeat of Zurgle's trip to oblivion seemed likely, but fortunately Pharo had begun to take shape, and it was not long before Polymorph became its default user interface framework. > > In short, Polymorph is a collection of widgets built on top of Morphic. It provides some impressive graphics, but the "feel" is the critical feature. Bill, Thank youfor that explanation.Iunderstandthe situation better. Best regards Olivier ;-) www.auverlot.fr

March 3, 2011

Re: [Pharo-project] LDAPlayer

by StÃ©phane Ducasse

Olivier what is the difference with the package Fixes: - Remove undocumented, untested, and unnecessary class Ldap - Fix broken handling of exception codes - Simplify some needlessly complex code Read moreâ¦ Stef On Mar 3, 2011, at 11:34 AM, Olivier Auverlot wrote: > Hi, > > I have uploaded today an updated version of LDAPlayer with some minor corrections for Pharo 1.1.1. All seems work perfectly. If you need an LDAP connector for Pharo, it's a good solution. > > I will try to produce a tutorial in the next days. > > http://www.squeaksource.com/@I6MXr0KZ8IlD2Fnn/CKF0ucuM > > Best regards > Olivier ;-) > > www.auverlot.fr >

March 3, 2011

Re: [Pharo-project] GUI ?

by laurent laffont

IMHO actually the way to go (and document - I can help) is Polymorph. On Pharocasts http://www.pharocasts.com/search/label/gui Also look at UITheme class, examples protocol. Laurent. On Thu, Mar 3, 2011 at 1:32 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Olivier, > > There is a growing body of good information. You might start here: > > http://www.pharo-project.org/documentation/screencasts > http://book.pharo-project.org/ > > Morphic is a long-standing UI framework for Squeak, taken from Self. > Morphic was a nice simulation environment, but Squeak's GUI really needed > someone to either replace Morphic entirely, or to at least use it to > simulate a user interface consistent with the "feel" (what the GUI does in > response to user input) users have learned to expect. The first attempt to > do that was Jim Benson's Zurgle, which the Squeak community completely > marginalized. If Zurgle had a failing, it was dependence on external files, > but a simple theme could have addressed the concerns. > > Time passes. Gary Chambers of Pinesoft announced Polymorph, and offered to > make it available if anyone were interested in using it. A repeat of > Zurgle's trip to oblivion seemed likely, but fortunately Pharo had begun to > take shape, and it was not long before Polymorph became its default user > interface framework. > > In short, Polymorph is a collection of widgets built on top of Morphic. It > provides some impressive graphics, but the "feel" is the critical feature. > > Welcome aboard! > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Olivier Auverlot > [olivier.auverlot(a)gmail.com] > Sent: Thursday, March 03, 2011 5:43 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] GUI ? > > Hi, > > Someone have a good documentation or tutorial for learning how to create > GUI avec Pharo ? > > In particuliar, I search a description of the objects like buttons, > fields, treeview , radio buttons, checkbox and the events mechanism. > > On the ML, i can read messages about Morphic and Polymorph ? what is the > difference ? > > Best regards > Olivier ;-) > > www.auverlot.fr > > > > >

March 3, 2011

Re: [Pharo-project] About RPackage

by Alexandre Bergel

>> This was the decisions that two of us (I mean me and you) took :). >> >> Categories are mapped one-to-one to RPackages. The reason is that this is the simplest path to replace categories in the system. > > > Doru I'm afraid that it will not work because it means that suddenly people will have to change all the configurationOf. > We should come up with a smooth transition phase (now this is true that if we could get rid of categories it would be good) PackageInfo and RPackage cannot coexist? In any case, it will not be a problem for me to update all my config with this new schema. Alexandre > >> The second step is to map the current Monticello package to RPackages so that we can load existing Monticello packages. >> >> The third step is to provide saving only of individual RPackages. Thus, Monticello should not save multiple RPackages into one Monticello package, but only make it easy to store each one in a separate package. > > > the problem is that it implies that we will have to change all the configurationOfXXX (or we should shrink all the packages > >> >> Once this is achieved, we can merge an RPackage with a Monticello package, which means that the package that you see in the image is directly storable in a transparent way. >> >> Cheers, >> Doru >> >> >> >> On 1 Mar 2011, at 22:44, StÃ©phane Ducasse wrote: >> >>> Hi cyrille/doru and others. >>> >>> I do not understand why >>> RPackage organizer packages contains System? >>> >>> In fact all the categories are mapped to packages and I wonder why. >>> I imagine that this is to avoid to have mostSpecific* logic of packageInfo, >>> but it means that in such a case we should merge categories to get back the package we have right now >>> else we will end up with loading/saving problems. >>> >>> >>> Stef >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 3, 2011

Re: [Pharo-project] LDAPlayer

by Alexandre Bergel

Just in case it was not clear for some people (like me :-) "LDPA is an application protocol for reading and editing directories over an IP network.[1] Adirectory in this sense is an organized set of records: for example, a telephone directory is an alphabetical list of persons and organizations with an address and phone number in each "record"." Cheers, Alexandre On 3 Mar 2011, at 07:34, Olivier Auverlot wrote: > Hi, > > I have uploaded today an updated version of LDAPlayer with some minor corrections for Pharo 1.1.1. All seems work perfectly. If you need an LDAP connector for Pharo, it's a good solution. > > I will try to produce a tutorial in the next days. > > http://www.squeaksource.com/@I6MXr0KZ8IlD2Fnn/CKF0ucuM > > Best regards > Olivier ;-) > > www.auverlot.fr > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 3, 2011

[Pharo-project] Issue 3777 in pharo: Bring back Mocketry

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3777 by marcus.d...(a)gmail.com: Bring back Mocketry http://code.google.com/p/pharo/issues/detail?id=3777 I removed Mocketry because of failing tests.. according the the author, these have been fixed.

March 3, 2011

Re: [Pharo-project] Issue 3620 in pharo: Settings: OCompletion settings appear twice

by pharo＠googlecode.com

Comment #14 on issue 3620 by marcus.d...(a)gmail.com: Settings: OCompletion settings appear twice http://code.google.com/p/pharo/issues/detail?id=3620 Levente suggests to fork it for 1.2: The fork would be the same as the latest version without the selectors containting pragma preferences. Then open a new issue for 1.3 about the duplicates appearing in the Settings Browser.

March 3, 2011