October 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] ProgressDisplay package released
by Ralph Boland March 29, 2011

March 29, 2011

I recently released the first draft of my package ProgressDisplay to SqueakSource. It is like SystemProgressMorph et. al. but with a lot of bells and whistles added. It is not a suitable replacement for SystemProgressMorph though because it is too large and specific for that. SystemProgressMorph could be made a subclass of one of its classes though. It is designed largely to meet my specific needs but since it's MIT anyone may use it, steal components, or move components of it to Squeak/Pharo. It has a utility class category with useful classes for things like array permutation generation and array multiset permutation generation, numeric partitioning of a number, and a class RangeList (which I will be expanding upon later). All of these classes will be removed when the package meant to contain them is ready (not soon). There are also a number of utility methods that could be stolen or put into Squeak/Pharo proper. It probably has lots of bugs, so bug reports appreciated. Comments on its function, design, and implementation most welcome. Proposals for improvements or extensions will be considered but no promises. If you need access to make changes let me know. If Levente Uzonyi likes it but feels compelled to rewrite it completely from scratch, thats okay too. :-) ONE OF MY REASONS FOR RELEASING IT IS BECAUSE OF A BUG I COULD NOT FIX. It is supposed to be possible to turn on the ability to catch user interrupts but when this feature is turned on and an interrupt generated while the progress bar is displayed the interrupt is caught but not processed until the progress bar closes. :-( Of course the interrupt was meant to be processed immediately. If anyone can tell me how to fix this bug (or better still send me the code or add the code to the package) that would be great! Regards, Ralph Boland -- Quantum Theory cannot save us from the tyranny of a deterministic universe but it does give God something to do

6 5

[Pharo-project] State of different projects for work with 3D
by nullPointer March 14, 2011

March 14, 2011

Regards; excuse me for my poor english. I want create a language similar to XAML for define UI interfaces. My doubt is the number and state of different projects for access to OpenGL. I need running on different OS without differences. Well, perhaps is a great question, but I havenÂ´t a global look of that in Pharo. Is possible implements something like that in Smalltalk? Thanks for the answers. -- View this message in context: http://forum.world.st/State-of-different-projects-for-work-with-3D-tp226825… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

7 10

[Pharo-project] serializing a class
by StÃ©phane Ducasse March 7, 2011

March 7, 2011

Hi I would like to do a little experiment. I need to save a class (not the instances) in a binary format and I was wondering if somebody got experience with that. Stef

8 15

[Pharo-project] Inspect it wrong shortcut
by Mariano Martinez Peck March 3, 2011

March 3, 2011

Hi! With latest pharo 304 in Linux the shortcut for inspect it (ctrl + i) doesn't work but alt + i. I have evaluated Preferences enable: #swapCOntrolAndAltKeys. Actually, all the other shortcuts (browse it, do it, explore it, and so on) works with ctrl + XXX but there is a problem with inspect it. Can someone confirm this ? Cheers, Mariano

7 15

[Pharo-project] Introducing smallUML: a little project to help us document :)
by Carla F. Griggio Jan. 30, 2011

Jan. 30, 2011

Hi everyone! Well, here I am announcing the resulting project of my GSoC experience during the [your] summer: smallUML, a project to help us building diagrams and sharing them with any package of code. My mentor was Stephane Ducasse and my co-mentor Geert Claes, so thanks to them for the guidance up to now, and also to Fernando Olivero who helped me a lot (hope to do some coding with you at ESUG! :P). You can gofer it: Gofer it > squeaksource: 'smallUML'; > package: 'ConfigurationOfSmallUML'; > load. > (Smalltalk at: #ConfigurationOfSmallUML) project latestVersion load. > And then open the Diagram Browser of the current little examples evaluating: DiagramDrawingDocumentation openDiagramBrowser . > This is beta and I'm still working on it, my work will continue after GSoC's deadline, so of course your welcome to give some feedback and think about what features would you like it to have and if you're confortable with the current features. It would be really nice if this helped to get all Pharo projects more documented, with visual diagrams that help understanding them at a glance. Talking about that... the current features are: - Open a *Diagram Browser* for an existing Category Diagrams Holder (this is a class ment to hold the created diagrams and there should be one per category, for now; you can browse DiagramDrawingDocumentation to see an example) - *Create and edit diagrams* programatically describing them with "diagram code" (the diagram code it's just a protocol of methods meant to describe diagrams, you can see some diagram code browsing DiagramDrawingDocumentation methods or each Class Box in the Diagram Browser) - Every diagram you build through the Diagram Browser it's saved as "diagram code", so you can *share it as code* that will reproduce your diagram :) That means that diagrams can 'travel' along it's package when you commit your changes with Monticello! And then they can be edited by anybody, they're not just a pretty picture. - You can *export* your diagram as a *PNG* picture or you can export it's "diagram code" as a *workspace*. - Only *Class Diagrams* can be built for now. - Class Boxes of a class diagram can be *dragged* to be easily positioned. Some details that are missing: - It's funny, but I can't center the class boxes title! :P - I tried adding some scrollbars to the "whiteboard" where you can view your diagrams in the Diagram Browser, but if I did that the drag & drop of the class boxes worked funny :( I'll ask about that to you later. On the way: - Tests and documentation, and a screencast showing every feature. - Lots of refactors: as I'm adding more kind of diagrams right now, so I'm doing a lot of refactors to make everything more flexible and improving all the messy code there. - A version of Minimal Connectors for anybody to use if they feel like connecting morphs for another project. - Some usability improvements. - Object diagrams - Sequence diagrams - Your feedback :D So I'd really appreciate if you can give it a try and tell me how you feel about it, I'd like it to be very usable. Cheers! Carla

7 14

[Pharo-project] CommandShell
by laurent laffont Jan. 28, 2011

Jan. 28, 2011

Hi, I'm trying to load CommandShell into Pharo. I have the error: This package depends on the following classes: PluggableTextController PluggableTextView You must resolve these dependencies before you will be able to load these definitions: ShellWindowView ...... Do you know where I can find PluggableTextController and PluggableTextView ? Or maybe we can use other classes to make it compatible with Pharo Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

5 12

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?
by Simon Denier Dec. 30, 2010

Dec. 30, 2010

Uhuh, that's indeed the old theme, but as said before I now prefer the current theme with some adaptations: it's less aggressive to the eye. To apply, call SHTextStylerST80 initialize after changing the style table SHTextStylerST80 styleTable: #( "(symbol color [emphasisSymbolOrArray [textStyleName [pixelHeight]]])" (default ( black ) ) (invalid ( red ) ) (excessCode ( red ) ) (comment ( green muchDarker ) ) (unfinishedComment ( green muchDarker ) ) (#'$' ( magenta muchDarker) ) (character ( magenta muchDarker) ) (integer ( magenta muchDarker) ) (number ( magenta muchDarker) ) (#- ( magenta muchDarker) ) (symbol ( magenta muchDarker) ) (stringSymbol ( magenta muchDarker) ) (literalArray ( magenta muchDarker) ) (string ( magenta muchDarker) ) (unfinishedString ( magenta muchDarker) ) (assignment ( black ) ) (ansiAssignment ( black ) ) (literal ( black ) ) (keyword ( black ) ) (binary ( black ) ) (unary ( black ) ) (incompleteKeyword ( red ) ) (incompleteBinary ( red ) ) (incompleteUnary ( red ) ) (undefinedKeyword ( red ) ) (undefinedBinary ( red ) ) (undefinedUnary ( red ) ) (patternKeyword ( black ) bold ) (patternBinary ( black ) bold ) (patternUnary ( black ) bold ) (#self ( cyan muchDarker ) ) (#super ( cyan muchDarker ) ) (#true ( cyan muchDarker ) ) (#false ( cyan muchDarker ) ) (#nil ( cyan muchDarker ) ) (#thisContext ( cyan muchDarker ) ) (#return ( black ) ) (patternArg ( blue muchDarker ) ) (methodArg ( blue muchDarker ) ) (blockPatternArg ( blue muchDarker ) ) (blockArg ( blue muchDarker ) ) (argument ( blue muchDarker ) ) (blockArgColon black ) (leftParenthesis black ) (rightParenthesis black ) (leftParenthesis1 black ) (rightParenthesis1 black ) (leftParenthesis2 black ) (rightParenthesis2 black ) (leftParenthesis3 black ) (rightParenthesis3 black ) (leftParenthesis4 black ) (rightParenthesis4 black ) (leftParenthesis5 black ) (rightParenthesis5 black ) (leftParenthesis6 black ) (rightParenthesis6 black ) (leftParenthesis7 black ) (rightParenthesis7 black ) (blockStart black ) (blockEnd black ) (blockStart1 black ) (blockEnd1 black ) (blockStart2 black ) (blockEnd2 black ) (blockStart3 black ) (blockEnd3 black ) (blockStart4 black ) (blockEnd4 black ) (blockStart5 black ) (blockEnd5 black ) (blockStart6 black ) (blockEnd6 black ) (blockStart7 black ) (blockEnd7 black ) (arrayStart black ) (arrayEnd black ) (arrayStart1 black ) (arrayEnd1 black ) (byteArrayStart black ) (byteArrayEnd black ) (byteArrayStart1 black ) (byteArrayEnd1 black ) (leftBrace black ) (rightBrace black ) (cascadeSeparator black ) (statementSeparator black ) (externalCallType black ) (externalCallTypePointerIndicator black ) (primitiveOrExternalCallStart black ) (primitiveOrExternalCallEnd black ) (methodTempBar black ) (blockTempBar black ) (blockArgsBar black ) (primitive gray ) (externalFunctionCallingConvention gray ) (module gray ) (blockTempVar ( blue muchDarker ) ) (blockPatternTempVar ( blue muchDarker ) ) (instVar ( brown darker) ) (workspaceVar ( blue muchDarker ) ) (undefinedIdentifier ( red ) ) (incompleteIdentifier ( red ) ) (tempVar ( blue muchDarker ) ) (patternTempVar ( blue muchDarker ) ) (poolConstant ( black ) bold ) (classVar ( brown darker ) ) (globalVar ( black ) bold ) ) On 25 oct. 2010, at 19:36, Mariano Martinez Peck wrote: > Thanks Ramon. So, we have to options. > > 1) We commit this change to Shout repository > 2) We add this method in ConfigurationOfPharo and we call it while building the dev image. > > opinions? > > cheers > > mariano > > On Mon, Oct 25, 2010 at 7:12 PM, Ramon Leon <ramon.leon(a)allresnet.com> wrote: > On 10/23/2010 10:11 AM, Mariano Martinez Peck wrote: > Exactly. > > Can you or Simon provide a script to set back the original colors?? So > that we can apply this for next PharoDev images? (or at least for my > own images) > > Thanks > > Mariano > > I just went back in the package history and found the point where Damien changed the colors and grabbed the previous version. I have a ConfigurationOfDevelopment class that loads all my local packages, so I just added a method to it to reload the old colors. Here it is... > > -- Simon

5 11

[Pharo-project] ConfigurationOfCitezen
by Schwab,Wilhelm K Dec. 23, 2010

Dec. 23, 2010

Hello all, Maybe I am simply getting confused by reading code from an "old" image, but I am trying to install Citezen. As I read the configuration, it was written in terms of Seaside 2.8, but it looks like 3.0 is being installed. Any ideas? I am open to thinking about Seaside 3, but my packages will fail to load due to the configuration changes. So far, all I have found is that I need to "change to the new system" but not much more than that. Perhaps the answer is to comment out the offending #initialize code, load everything, and then worry about how to get them registered. As slick as it is to be able to use Seaside to configure my Seaside apps, I do not want to trust myself on that front; I want them to be secured from the beginning, and temporarily re-configured for development as needed, and then programmatically switched back to secure-or-nothing. Semi-rhetorical question: should Citezen be loading Seaside? Could/should there be a Citezen-base or something that just reads BibTeX, and then other things that do all of the web-enabled work? All I do with it is parse entries, for which is very valuable. Bill

4 6

[Pharo-project] SmaCC
by Ross Boylan Dec. 12, 2010

Dec. 12, 2010

I'm using the Pharo 1.0 image and have loaded the configuration for SmaCC. It doesn't seem to come with any instruction or examples about how to use it, and I seem to have only the SmaCC-Runtime package group. I think I need SmaCCDev, but can't figure out how to load it. I opened up the monticello browser, but when I try to add a repository it asks me for an email address. I would appreciate help on any or all of figuring out how to use SmaCC, loading SmaCCDev (or any other packages) and info about package management in Pharo. Thanks. Ross Boylan

5 10

[Pharo-project] Using Pharo from the command-line
by Stefan Marr Dec. 2, 2010

Dec. 2, 2010

Hello: I just try to get started with Pharo to experiment with some benchmarks and would be grateful for some basic hints, since the documentation on pharo-project.org is not to excessive. As far as I read in the documentation of the language shootout[1], I will need the OSProcess package. How can I load this package into the image downloaded from p-p.org? My second problem is to execute code from the command line. I tried a simple example file $ cat test.sq Transcript open; cr; show: 'Hello, world'. $ Squeak\ 4.2.1beta1U.app/Contents/MacOS/Squeak\ VM\ Opt pharo1.0-10418-BETAdev09.08.3.image test.sq But this only leads to a debugger popping up in installSourceFile saying "No content to install". Looks like aStream is nil which should have the data loaded from file:test.sq Any pointers to documentation which might discusses command line related features are very welcome. I actually just need a way to choose a benchmark to be executed from the commandline. The actual code could already be in the image. Many thanks and best regards Stefan [1] http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=squeak&la… -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525 -- Stefan Marr Software Languages Lab Former Programming Technology Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://prog.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525

9 12