August 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Question about MD5

by Henrik Johansen

Please also use (String new: (self size * 2)) writeStream instead of '' writeStream. In this case it won't lead to any noticeable performance increases, but it's good practice anyways :) I'd also argue the expected returnvalue of "hex" might not be clear as something like "asHexString" when applied to a collection (hex previously only implemented on single values), but that's a minor issue. When looking around, I also noticed WriteStream nextPut: does an unnecessary check for ByteStrings which is pretty ugly (plus, it decreases nextPut: performance for all ByteString writeStreams), filed as Issue 1065. Cheers, Henry Issue 1065 On Aug 13, 2009, at 10:32 19AM, StÃ©phane Ducasse wrote: > add a nice method comment and a couple of tests! > > Stef > > On Aug 13, 2009, at 1:26 AM, Mariano Martinez Peck wrote: > >> Hi folks: Me and the rest of the team is developing SqueakDBX which >> is a driver to talk with major databases. However, I think the most >> persistence alternatives pharo has, the best. There is no better >> solution for every escenario. So, I am also trying to get the >> PostgreSQL native driver to work in Pharo. This package depends on >> Cryptography because of MD5. I know that there were added to Pharo >> packages like System-Hashing-core, System-Hashing-SHA1 and System- >> Hashing-MD5. However, the driver doesn't work yet. But adding this >> single method: >> >> ByteArray>>hex >> | stream | >> stream _ '' writeStream. >> self do: [ :each | >> stream >> nextPut: ('0123456789ABCDEF' at: each // 16 + 1); >> nextPut: ('0123456789ABCDEF' at: each \\ 16 + 1)]. >> ^ stream contents >> >> The driver works like a charm in Pharo without needing Cryptography >> package. As far as I remember there were no MIT problem with this >> package. Because of this those packages ( System-Hashing-core, >> System-Hashing-SHA1 and System-Hashing-MD5) were integrated in Pharo. >> >> So, can I add it? >> >> Thanks >> >> Mariano >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 13, 2009

Re: [Pharo-project] Help on Polymorph [was How to build a GUI]

by StÃ©phane Ducasse

On Aug 13, 2009, at 11:41 AM, laurent laffont wrote: > > > So far we should invent it. > And I totally agree with you. If people do not see the good doc they > will not write good comment. > I started to work on DrDoc a kind of package meta data to add > documentation to a package but it got stole > I should push that again. What would be nice is to take one package > and do it well as an example. > > > It think it should be possible to write documentation at the package > level. So developpers have a place where they can write an overview > of their package. When we click on a package, documentation should > be displayed by default or easily. Yes this is exactly the idea behind DrDoc The browser or another tools could show us that You can have a look at DrDoc and we could pair code more on it. > In the rubygems world, it is a common practice to write > documentation in a README file which is displayed by RDoc on startup > page (github works the same way). It seems to me that there's the > same level of comment between Ruby class/methods and Pharo. The > documentation at the package level may be the difference. Yes > Python has a real documentation effort.Each release come with its up > to date documentation. It's a release criteria. Python shares some > similarities with Pharo as they both have "batteries included". May > be there should have a process to contribute to a centralized Pharo > documentation which can be accessed within the IDE. Yes I think that pushing a bit more DrDoc is the way to go. I'm just flooded by work. > > Laurent. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 13, 2009

Re: [Pharo-project] Help on Polymorph [was How to build a GUI]

by laurent laffont

> > So far we should invent it. > And I totally agree with you. If people do not see the good doc they > will not write good comment. > I started to work on DrDoc a kind of package meta data to add > documentation to a package but it got stole > I should push that again. What would be nice is to take one package > and do it well as an example. > > It think it should be possible to write documentation at the package level. So developpers have a place where they can write an overview of their package. When we click on a package, documentation should be displayed by default or easily. In the rubygems world, it is a common practice to write documentation in a README file which is displayed by RDoc on startup page (github works the same way). It seems to me that there's the same level of comment between Ruby class/methods and Pharo. The documentation at the package level may be the difference. Python has a real documentation effort.Each release come with its up to date documentation. It's a release criteria. Python shares some similarities with Pharo as they both have "batteries included". May be there should have a process to contribute to a centralized Pharo documentation which can be accessed within the IDE. Laurent.

Aug. 13, 2009

Re: [Pharo-project] Problem with new Inspector

by Frederic Pluquet

Hello, Thank you for your feedback :) It is a good idea. I fixed it in the last version on SqueakSource. I hope it fit better for you now. FrÃ©d ---- FrÃ©dÃ©ric Pluquet UniversitÃ© Libre de Bruxelles (ULB) Assistant http://www.ulb.ac.be/di/fpluquet 2009/8/13 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2009/8/12 <csrabak(a)bol.com.br> > >> Oh well :-| I understand your gripe now, you resent the yellow button does >> not bring a menu on this pane, right!? >> >> If this is considered a bug, then yes, a BT must be opened... >> > that's exactly what I want :) Not only for people who don't use or don't > know about shortcuts but also because not all the commands are accessible by > shortcuts. > > Bye > > Mariano > > >> >> Em 12/08/2009 22:59, *Mariano Martinez Peck < marianopeck(a)gmail.com >*escreveu: >> >> >> >> >> 2009/8/12 <csrabak(a)bol.com.br<http://mce_host/compose?to=csrabak@bol.com.br> >> > >> >>> In the Inspector you have three panes, the bottom right is a small one >>> and it receives messages when I type, for example, self class, or self >>> allInstances, I can print the results or even inspect the result, is that >>> you want to do? >>> >> But HOW do you print the results? using ctrl + p or ctrl + i ? >> I want (actually I use shortcuts, but for others) to be able yo use the >> right button for this. >> >> Cheers, >> >> mariano >> >>> >>> >>> Em 12/08/2009 22:02, *Mariano Martinez Peck < marianopeck(a)gmail.com<http://mce_host/compose?to=marianopeck@gmail.com>> >>> * escreveu: >>> >>> >>> Hi folks: I have a problem with the new inspector. To reproduce: >>> >>> 1) Go to a workspace. >>> 2) Type ScriptLoader or any other class and inspect it. >>> 3) If I want to sends messages to THAT object, it seems the place to do >>> it is in the pane that is above on the right. Is this correct? >>> The problem is that there the right button doesn't work. So, I can only >>> use shortcuts. >>> >>> This is not good for newbie people. In addition, not all the commands are >>> accessible by a shortcut. >>> >>> Any has the same problem? If so, I will open a bug ticket. >>> >>> Best, >>> >>> Mariano >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr<http://../../../undefined/compose?to=Pharo> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 13, 2009

Re: [Pharo-project] Question about MD5

by StÃ©phane Ducasse

add a nice method comment and a couple of tests! Stef On Aug 13, 2009, at 1:26 AM, Mariano Martinez Peck wrote: > Hi folks: Me and the rest of the team is developing SqueakDBX which > is a driver to talk with major databases. However, I think the most > persistence alternatives pharo has, the best. There is no better > solution for every escenario. So, I am also trying to get the > PostgreSQL native driver to work in Pharo. This package depends on > Cryptography because of MD5. I know that there were added to Pharo > packages like System-Hashing-core, System-Hashing-SHA1 and System- > Hashing-MD5. However, the driver doesn't work yet. But adding this > single method: > > ByteArray>>hex > | stream | > stream _ '' writeStream. > self do: [ :each | > stream > nextPut: ('0123456789ABCDEF' at: each // 16 + 1); > nextPut: ('0123456789ABCDEF' at: each \\ 16 + 1)]. > ^ stream contents > > The driver works like a charm in Pharo without needing Cryptography > package. As far as I remember there were no MIT problem with this > package. Because of this those packages ( System-Hashing-core, > System-Hashing-SHA1 and System-Hashing-MD5) were integrated in Pharo. > > So, can I add it? > > Thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 13, 2009

Re: [Pharo-project] OBDependencyWalker for Pharo

by StÃ©phane Ducasse

Mariano and everybody when you open a ticket please - make sure that we know if this is for the OB version of a tools or not - send a clear mail to the list Stef On Aug 13, 2009, at 3:11 AM, Mariano Martinez Peck wrote: > > > 2009/8/12 <csrabak(a)bol.com.br> > In my attempt to install OBDependencyWalker in Pharo beta #10413, I > discovered that it triggers DNUs because #theClass is no longer > available in this image version. > > I could not find easily the rationale for stripping the method. > > Is this a known fact and OBDependencyWalker should be modified, or > #theClass needs to be reinstated? > > > > Hi have also opened a ticket a couple of days ago about a DNU > theClass. > > See http://code.google.com/p/pharo/issues/detail?id=1059 > > Best, > > Mariano > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 13, 2009

Re: [Pharo-project] [Ann] RFB/VNC fully configurable by code.

by StÃ©phane Ducasse

yes yes yes On Aug 12, 2009, at 10:32 PM, Miguel Enrique CobÃ¡ Martinez wrote: > El miÃ©, 12-08-2009 a las 18:18 -0100, Mariano Martinez Peck escribiÃ³: > >> >> >> What sort of packages should be put there? For example, I am woring >> in >> SqueakDBX and Glorp and both of them work there. However, they are >> not >> dev tools or something like. Thus, I don't understand which type or >> packages should be added. > > Every package that loads and runs ok on pharo. > This will motivate to port even more packages. I hope it will be a > catalyzer because if we can show that a lot of packages are already > running ok on pharo, the stability and maturity of pharo will make > it a > good platform to base new software and to port software from other > smalltalk versions. > So, if you have a package that load/runs, please by any means add it. > > > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 13, 2009

Re: [Pharo-project] Help on Polymorph [was How to build a GUI]

by StÃ©phane Ducasse

On Aug 12, 2009, at 10:32 PM, laurent laffont wrote: > Not exactly a compreensive documentation but rather a quick start: > > In a workspace evaluate: > > UITheme exampleBasicControls. > UITheme exampleColorControls. > UITheme exampleDialogs. > UITheme exampleGroups. > UITheme exampleOtherControls. > UITheme exampleWindowWithToolbars. > > > Hi > > In fact I've managed to build some windows with controls but I feel > missing several concepts on how to use Polymorph the right way > ( funny, I've built Gtk, Qt, Swing, ... GUI quite easily ... ). this is normal Morphic has not evolved since years. Now I hope that with the UI builder NullPointer is doing it will change a lot. > - What is the idea behind the word "Pluggable" (PluggableButton, > PluggableDialogWindow, ....) ? Normally you pass a symbol or a block and it will be executed (I think that any GUI should be like that :)). > - It seems that many (all ?) UI in Pharo use the builder pattern. > Great, but that's a lot of stuff for me while trying to learn (with > almost no time, I had forgotten that a new child take soooo much > time). Do you know a package/class with simpler UI to study ? > > - In Toolbuilder, what the word "Spec" means ? > > Some thoughts: > > - Toolbuilder-Examples package is great to study how to use > Toolbuilder. I think it should be included in Pharo with some other > XXX-Examples packages that might exists. thanks. Where is the ToolBuilder-Examples in the Squeak trunk? > - Is there a somewhat easier way to navigate through class and > methods documentation than in System Browser ? I think that > documentation is not easily seen, so it doesn't push developers to > write documentation, so there's not a lot of documentation, so > people don't write tools to read documentation, ... There should be > a system / tool to reward developpers that write good class / > package documentation with examples. So far we should invent it. And I totally agree with you. If people do not see the good doc they will not write good comment. I started to work on DrDoc a kind of package meta data to add documentation to a package but it got stole I should push that again. What would be nice is to take one package and do it well as an example. > > > Regards, > > Laurent > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 13, 2009

Re: [Pharo-project] Question about MD5

by Adrian Lienhard

Yes, please create an entry in the bug tracker (just copy paste the mail below should be sufficient). Cheers, Adrian On Aug 13, 2009, at 01:29 , Mariano Martinez Peck wrote: > Sorry, I forgot to say that others classes like Integer, Float and > Character > are already implementing the message hex. > > Best, > > Mariano > > On Wed, Aug 12, 2009 at 8:26 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Hi folks: Me and the rest of the team is developing SqueakDBX which >> is a >> driver to talk with major databases. However, I think the most >> persistence >> alternatives pharo has, the best. There is no better solution for >> every >> escenario. So, I am also trying to get the PostgreSQL native driver >> to work >> in Pharo. This package depends on Cryptography because of MD5. I >> know that >> there were added to Pharo packages like System-Hashing-core, >> System-Hashing-SHA1 and System-Hashing-MD5. However, the driver >> doesn't work >> yet. But adding this single method: >> >> ByteArray>>hex >> | stream | >> stream _ '' writeStream. >> self do: [ :each | >> stream >> nextPut: ('0123456789ABCDEF' at: each // 16 + 1); >> nextPut: ('0123456789ABCDEF' at: each \\ 16 + 1)]. >> ^ stream contents >> >> The driver works like a charm in Pharo without needing Cryptography >> package. As far as I remember there were no MIT problem with this >> package. >> Because of this those packages ( System-Hashing-core, System- >> Hashing-SHA1 >> and System-Hashing-MD5) were integrated in Pharo. >> >> So, can I add it? >> >> Thanks >> >> Mariano >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 13, 2009

Re: [Pharo-project] Socket>>connectTo:port: fail

by Serge Stinckwich

On Thu, Aug 13, 2009 at 11:40 AM, HernÃ¡n Morales Durand<hernan.morales(a)gmail.com> wrote: > Hi Serge, > Â This works for me: > > | socket1 socket2 | > > socket1 := Socket newTCP. > socket2 := Socket newTCP. > socket1 listenOn: 6665. > address := NetNameResolver addressForName: '127.0.0.1' timeout: 20. > socket2 connectTo: address port:6665. Ok works better now ;-) Thank you HernÃ¡n. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Aug. 13, 2009