October 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] GUI Frameworks Choice

by Pavel Krivanek

Hi Craig, try to look at Phobos frmework: https://code.google.com/p/phobos-framework/ Cheers, -- Pavel Dne pÃ¡tek 17. ÅÃjna 2014 Craig <craig(a)hivemind.net> napsal(a): > Hi All, > > I'm new to Pharo although not to Smalltalk. I did dabble with Dolphin > about 20 years ago, when it was first being developed, and did some quite > cool stuff. > > This time around I chose Pharo because I feel that Dolphin has strayed > from the pure OO model that I enjoyed back then. > > I've chosen a fairly ambitious GUI project as my Pharo primer. The > problem is - which GUI framework to use. The GUI that I want to build will > be static but complex with a menu, 2 toolbars, 20 odd toolbar buttons, and > 3 (dockable?) windows, containing Trees, lists and text editors. > > Any suggestions on which GUI framework would suit? > > I thought about using PolyMorph, but I cannot find the examples in my > Pharo 3 image. > > Craig > > > > > > > > >

Oct. 17, 2014

Re: [Pharo-users] GUI Frameworks Choice

by stepharo

Hi craig The examples are in the class WidgetExample or ExampleWidget. Now we are not happy from a design point of view of having all these widgets creation on UITheme. You can also use Spec. There is a draft of chapters on https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/838/artifa… Stef On 17/10/14 09:11, Craig wrote: > Hi All, > > I'm new to Pharo although not to Smalltalk. I did dabble with Dolphin about 20 years ago, when it was first being developed, and did some quite cool stuff. > > This time around I chose Pharo because I feel that Dolphin has strayed from the pure OO model that I enjoyed back then. > > I've chosen a fairly ambitious GUI project as my Pharo primer. The problem is - which GUI framework to use. The GUI that I want to build will be static but complex with a menu, 2 toolbars, 20 odd toolbar buttons, and 3 (dockable?) windows, containing Trees, lists and text editors. > > Any suggestions on which GUI framework would suit? > > I thought about using PolyMorph, but I cannot find the examples in my Pharo 3 image. > > Craig > > > > > > > > >

Oct. 17, 2014

Re: [Pharo-users] UDP example

by Annick Fron

Thank you, but I am confused. I have checked your NTP code, and it uses sendUDPData and not sendData. Same for receiveUDPData. Besides how is it possible to know where the message comes from in a broadcast mode ?? Annick Le 17 oct. 2014 Ã 17:35, Sven Van Caekenberghe <sven(a)stfx.eu> a Ã©crit : > UDP is pretty easy, just send and receive byte arrays basically, mostly non-blocking. > > http://forum.world.st/UDP-Listener-example-td4362851.html > http://forum.world.st/SysLogSender-UDP-td4745862.html > > The API is all in Socket. > > On 17 Oct 2014, at 17:09, Annick Fron <list(a)afceurope.com> wrote: > >> Hi, >> >> I was not able to find a UDP example in pharo. >> >> There are only TCP examples. >> >> Any pointer ? >> >> Annick >> > >

Oct. 17, 2014

Re: [Pharo-users] Client cerificate authentication with ZnClient?

by Attila Magyar

wow, thanks. I will test it on Monday. -- View this message in context: http://forum.world.st/Client-cerificate-authentication-with-ZnClient-tp4784… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Oct. 17, 2014

Re: [Pharo-users] [Pharo-dev] [ANN] New Gold Member LabWare

by Sven Van Caekenberghe

This is excellent news. On 15 Oct 2014, at 14:00, Marcus Denker <marcus.denker(a)inria.fr> wrote: > The Pharo Consortium is very happy to announce that LabWare has joined the Consortium as a Gold Industrial Member. > > About LabWare: > "LabWare is recognized as the global leader in providing enterprise scale laboratory automation solutions. > Our Enterprise Laboratory Platform combines the award-winning LabWare LIMSâ¢ and LabWare ELNâ¢, a > comprehensive and fully integrated Electronic Laboratory Notebook application, which enables companies > to optimize compliance, improve quality, increase productivity and reduce costs. LabWare is a full service > provider offering software, professional implementation services and validation assistance, training, and > world class technical support to ensure our customers get the maximum value from their LabWare products." > > - LabWare: http://www.labware.com > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies to support the ongoing development and future of Pharo. > Individuals can support Pharo via the Pharo Association: http://association.pharo.org

Oct. 17, 2014

Re: [Pharo-users] UDP example

by Sven Van Caekenberghe

UDP is pretty easy, just send and receive byte arrays basically, mostly non-blocking. http://forum.world.st/UDP-Listener-example-td4362851.html http://forum.world.st/SysLogSender-UDP-td4745862.html The API is all in Socket. On 17 Oct 2014, at 17:09, Annick Fron <list(a)afceurope.com> wrote: > Hi, > > I was not able to find a UDP example in pharo. > > There are only TCP examples. > > Any pointer ? > > Annick >

Oct. 17, 2014

Re: [Pharo-users] FFI on Linux again

by Annick Fron

I have the same problem with myWindow xid. Â« bad argument Â». Yet I have used all the other methods which also use myWindow xid and display as arguments. I think the problem is from the other arguments passed by reference, not by value. I have seen a new version of Alien from Sept 30, but I donât know if it works in pharo. Annick Le 25 sept. 2014 Ã 18:56, Nicolai Hess <nicolaihess(a)web.de> a Ã©crit : > > Am 25.09.2014 17:25 schrieb "Annick Fron" <list(a)afceurope.com>: > > > > Hi, > > > > I Have tried the following code on Linux , but the call breaks. Is it because of the X11Window structure missing or else ? > > > > Annick > > ==== > > testGetOurWindowLocation > > "self new testGetOurWindowLocation" > > > > | display ourWindow aParent anX anY aWidth aHeight aBorderWidth aDepth | > > display := X11Display XOpenDisplay: nil. > > ourWindow := display ourWindow. > > (Alien lookup: 'XGetGeometry' inLibrary: 'X11') > > primFFICallResult: nil > > withArguments: > > {display. > > ourWindow. > > (aParent := Alien new: 4). > > (anX := Alien new: 4). > > (anY := Alien new: 4). > > (aWidth := Alien new: 4). > > (aHeight := Alien new: 4). > > (aBorderWidth := Alien new: 4). > > (aDepth := Alien new: 4)}. > > (anX unsignedLongAt: 1) inspect > > withArguments ... > ourWindow xid > ... > ? >

Oct. 17, 2014

Re: [Pharo-users] Spur images

by Alexandre Bergel

Interesting. When working on AstroCloud (http://astrocloudy.wordpress.com) we find out that Bitmap and FormCanvas were way too slow. Performing a global modification (e.g., changing a red for a blue) took long long time for very large images (2000 x 2000 pixels). We did some intensive profiling and aggressive optimizations until the points we could not optimize anymore. We then tried to avoid manipulating objects in some very specific part of the code. For example, instead of having instance of the class Color, we have an array (unique and preallocated) that contains the red, green, and blue values. Having these âprimitivesâ values was convenient to call either a C function or very low level functions with native boost. We got a ~ x 30 speed up. I do not know much about wide strings, but I suspect you can do something like that. So, my advice is: identify the method that cost you a lot, and write it natively. This has worked for us, in a non-trivial setting. Let us know Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Oct 3, 2014, at 5:07 PM, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > My apologies if this is already spelled out somewhere and I simply can't > find it, but are there any Spur images for Pharo yet? I can only find > Squeak ones. It's not a big deal either way; I was just playing with an > algorithm that, after very heavy optimization, I was able to get down to > about 278ms per pass (from ~700ms initially from a naive > implementation). For contrast, the equivalent Python runs in ~80ms. > Looking at MessageTally, it seems at least half of that 278ms is spent > noodling around in WideStrings and other small things that the Spur > object format ought to help with, so it'd be interesting to see how much > of a speed boost that gives without any further work. >

Oct. 17, 2014

UDP example

by Annick Fron

Hi, I was not able to find a UDP example in pharo. There are only TCP examples. Any pointer ? Annick

Oct. 17, 2014

Re: [Pharo-users] Spur images

by Sven Van Caekenberghe

On 10 Oct 2014, at 03:40, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > On Sun, 05 Oct 2014 16:51:25 -0400, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > [snip] >> Apart from that, the tokenisation is not very efficient, #lines is a copy of your whole contents, so is the #split: and #trimmed. The algorithm sounds a bit lazy as well, writing it 'on purpose' with an eye for performance might yield better results. > > So I was reflecting on this more. If String and WideString were immutable, then it'd be easy to avoid all of these copies; you could instead pass around very tiny objects that had only three members (a String, a start position, a stop position), and avoid copying very much data. It's that String and WideString are mutable that preclude that. For fun, since I know I won't mutate the stringsin this example, I actually did a quick spike where I replaced #copyFrom:to: with a new method I introduced called #viewFrom:to: that returned a StringView. I'll post the code when I have a chance to clean it up if there's interest, but it looks like it pretty handedly chops off 120-150ms from that runtime (i.e., double the speed). > > Has there been any thought to introducing some immutable collections? Or maybe I'm just missing them? They'd be useful not just for String and WideString, but really for basically any of the collection types. The implementation in most cases would be as simple as overriding #at:put: and friends to throw "self shouldNotImplement", and then providing methods/classes like the one I introduced to allow taking advantage of the newfound immutability. > > If there's interest, I'd be happy to submit a Slice we could use as a concrete RFC of what this could look like. > > --Benjamin I think it is interesting that you get real measurable improvements with user defined string views. I have always felt that a problem for going in that direction is that most primitives (which are important to get good basic string performance) are not flexible enough to be used really efficiently. More concretely, they should take start/stop indexes on all string arguments. For example, ByteString class>>#compare:with:collated: or #stringHash:initialHash: - it should be possible to do these operations on substrings *without creating the substrings*. Sven

Oct. 17, 2014