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

Re: [Pharo-project] [squeak-dev] The SmalltalkHub demo is online!

by StÃ©phane Ducasse

mariano I know you are on holidays, but what is finally the solution to support migration of fuel serialized objects to new format (the discussion with philippe). Stef On Nov 15, 2011, at 9:56 PM, Mariano Martinez Peck wrote: > > > On Tue, Nov 15, 2011 at 4:18 PM, Nicolas Petton <petton.nicolas(a)gmail.com> wrote: > Hi guys, > > I'm glad to tell you that the demo of SmalltalkHub is online. > http://www.smalltalkhub.com > > Note that this is a demo only (all projects will be deleted at some > point). > > You can follow the SmalltalkHub project here: > http://smalltalkhub.com/user/NicolasPetton/SmalltalkHub > > You can report bugs you encounter on the issue tracker there. > > This demo is running on Pharo (the next one will be on GemStone). > > The changelog is quite big, but here's some important changes: > > - The clone feature has been removed in favor of an inbox per project. > (later the inbox repository url will be visible in the project overview) > - RSS feeds for project timelines and user activity > - Persistency is now pluggable (the current demo uses Fuel to serialize > the repository) > > Nice to hear that. Let us know if we can improve something. > > BTW.... one thing I would love but I think you already answered to me that yes, is the ability to have a ConfigurationOfSmalltalkHub which let me take a standard Pharo image and execute: ConfigurationOfSmalltalkHab loadWithFuelPresistency. > and I can have my own/company/whatever repo running :) > > > - New help system > - New chronological view of packages > - More useful commit view > - The issue tracker has received some love some bugs has been fixed > - new statistics view > - Email notifications > - And of course, many bug and UX fixes > > Some features that will appear soon (in random order): > - Scripting engine to perform actions on projects > - A diff browser > - the ability to accept/decline packages committed to the inbox, and > move/delete packages/versions. > > Cheers, > Nicolas > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Nov. 16, 2011

Re: [Pharo-project] SystemChangeNotifier and Traits

by StÃ©phane Ducasse

+ 1 and we should remove the old ones and a lot of old abstraction MethodReference, PseudoClass, FilePackage, and a lot more I hope that we will get into that mode soon. Stef On Nov 16, 2011, at 3:55 PM, Fernando Olivero wrote: > Please note that eventually the system is going to be using solely > System announcements, instead of the old mechanism in place right now. > > Did you try hooking up to the SystemAnnouncements? > > For examples, check out Nautius. > > Fernando > > > > On Tue, Nov 15, 2011 at 9:02 PM, ezequiel lamonica > <lamonicaezequiel(a)gmail.com> wrote: >> Hello again, >> >> Now the problem is when I create a class that use Traits, >> SystemChangeNotifier sends two messages to report this creation: 1st for >> class added without traits, and 2nd for class modified to use this trait. >> And this last message has Object as old class instead of ClassForTesting >> without traits. >> >> For example: >> >> Object subclass: #ClassForTesting >> uses: TSortable >> instanceVariableNames: 'a' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'OOSCM-ClientImageTest' >> >> >> Can I change those messages to use only one message that includes traits? Is >> not this better? >> >> What do you suggest? >> >> >> >> ----- >> eze >> -- >> View this message in context: http://forum.world.st/SystemChangeNotifier-and-Traits-tp4073962p4073962.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> >

Nov. 16, 2011

Re: [Pharo-project] [Progress Report] Zn+Zdc=HTTPS (Zodiac)

by StÃ©phane Ducasse

This is a really exciting news! Stef On Nov 15, 2011, at 3:06 PM, Sven Van Caekenberghe wrote: > Hi, > > Since the first Zodiac code became available last May and since the two Alpha releases in June and September I think there has been some progress. I know of at least two projects that independently have put Zn+Zdc (Zinc HTTP Components & Zodiac) to successful use for doing HTTPS: > > - Paul DeBruicker's stripe.com credit card payment gateway integration > - Guillermo Polito's google.com account authentication and API access (Ulysse the Monkey) > > That is why in the last Zn release, HTTPS will work out of the box, provided you load Zdc and install the necessary plugin. > > So the following should just work: > > ZnClient new > https; > host: 'www.google.com'; > addPath: 'search'; > queryAt: 'q' put: 'Pharo Project'; > get > > ZnClient new > get: 'https://www.google.com/search?q=Pharo Project' > > To verify that the query actually worked, you can do a > > self includesSubString: 'www.pharo-project.org' > > on the resulting byte string. > > There is now a new webpage dedicated to Zodiac: > > http://zdc.stfx.eu > > Currently, it is quite minimal, but it will grow when needed. > > Although the project is far from finished, I think it is safe to move it from Alpha to Beta. > > Sven > >

Nov. 16, 2011

Re: [Pharo-project] Status of ToolBuilder

by StÃ©phane Ducasse

On Nov 15, 2011, at 8:47 PM, Lukas Renggli wrote: > I was kind of surprised that ToolBuilder is still part of Pharo. where? Because we removed it. > Are there any users? Are there any plans to update it to match the > version of Squeak? Is it encouraged to build UIs with ToolBuilder? no :) We were brainstorming on valueHolder, Spec and UIBuilder a la VW with Benjamin and we got the conclusions: Specs are cool because the same application Model can propose multiple spec valueHolder are the building brick to be able to reuse the application model UI logic (and not just the UI widgets). placing widgets on the screen is just a part of the story but the least interesting one because point 2 is more important. Now This is a brainstorming > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Nov. 16, 2011

Re: [Pharo-project] Thank you

by StÃ©phane Ducasse

thanks for the update Hilaire. Right now time is quite scarce for me but we will come back :) On Nov 15, 2011, at 5:23 PM, Hilaire Fernandes wrote: > Hello people, > > A small note to say DrGeo is doing great progresses in term of features, > usability and fun. I am working regularly with teachers from my school > and elsewhere to develop new features based on their needs. > The next release will be in December with a lot of new cool small features. > > This is nice for Pharo and Smalltalk as well. > > To document DrGeo, I am doing regularly screencast (now in Enlgish) in > the DrGeo channel at Dailymotion http://www.dailymotion.com/group/drgeo > > Thanks for your helps. > > Hilaire > > PS: I really have fun programming DrGeo with Pharo Smalltalk > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > >

Nov. 16, 2011

Re: [Pharo-project] could you test the attached?

by StÃ©phane Ducasse

Thanks eliot Issue 4998: ContextPart>>#runUntilErrorOrReturnFrom: Definitively the kind of methods I want to understand. On Nov 16, 2011, at 8:58 PM, Eliot Miranda wrote: > Hi All, > > I've found a bug in ContextPart>>#runUntilErrorOrReturnFrom: that in a certain rare circumstance causes the method to peel back too much of the stack. This method is used in the debugger (e.g. completeStep: et al) but also in Process termination. So it is right at the heart of the system. I'm loath to simply commit it I'd really appreciate y'all testing with the fix and reporting any changes you see. It does not affect the trunk test suite (there is a test, WeakSetInspectorTest, which is unreliable, but apart form that no observed effects). So, brave souls, please try with the attached and see if you come to grief or not. > -- > thanks, > Eliot > > <ContextPart-runUntilErrorOrReturnFrom.st>

Nov. 16, 2011

Re: [Pharo-project] pharo-xmlrpc samples fail in Pharo 1.3

by StÃ©phane Ducasse

German Can you have a look? Stef On Nov 15, 2011, at 1:16 PM, seamus wrote: > Hi all > > Just wondering what to do next. > I need a working xmlrpc library for a project I am working on but the latest > version of pharo-xmlrpc fails due to a DoesNotUnderstand #contentString > error. This is just testing the samples provided as below: > > | url proxy r | > > url := Url absoluteFromText: 'http://snipplr.com/xml-rpc.php'. > proxy := XMLRPCProxy new url: url. > > r := proxy invokeMethod: 'languages.list' withArgs: #('Your snipplr key'). > > r := proxy invokeMethod: 'user.checkkey' withArgs: #('Your snipplr key'). > r := proxy invokeMethod: 'snippet.list' withArgs: #('Your snipplr key' > 'pharo'). > > "To get a snippet you don't need key, but the Snippet ID" > r := proxy invokeMethod: 'snippet.get' withArgs: #('41365'). > > Any ideas to get this working? I see that someone mentioned that this may be > a missing method in the Dictionary object. > > Regards > > Seamus > > -- > View this message in context: http://forum.world.st/pharo-xmlrpc-samples-fail-in-Pharo-1-3-tp4042738p4042… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 16, 2011

Re: [Pharo-project] WideString performance

by Nicolas Cellier

I think that there are several issues: 1) Character with codePoint < 256 are unique, but Wider are not. The characters are not stored in the WideString (which instead stores the code points), but any enumeration using at: rather than wordAt: will create an overhead. I presume that it would be better to have a #codePointAt: defined as #byteAt: in ByteString and #wordAt: in WideString, so we could still define generic methods in String. 2) A lot of ByteString methods are optimized with ad hoc optional primitives, but very few WideString methods are. 3) Some of these optimized operations work with 256 element masks and cannot be generalized to WideString that easily 4) Some Stream operations that copy one Collection to the stream buffer or vice versa are also not optimized for mixed byte/word collections 5) UTF8 is optimized for ASCII anyway... And Squeak/Pharo converters also are (because they can use more primitives in this case) 6) Pharo ripped #squeakToUtf8 and #utf8ToSqueak which were maybe questionable from quality POV, but were not replaced from efficiency POV. I would say that a new VM with immediate Character values might help, but that won't be enough. Nicolas 2011/11/16 Sven Van Caekenberghe <sven(a)beta9.be>: > Dennis, > > On 16 Nov 2011, at 19:30, Dennis Schetinin wrote: > >> Hi! >> >> Parsing a UTF-8 CSV file with Russian symbols (using CSVParser), I found it really slow. It takes about 5 seconds to read a 53Kb file (136 lines) and several minutes to parse a 3.4Mb file (about 8K lines). >> >> Profiler shows that nearly all the time is eaten by WideString >> at:put: which is invoked from WriteStream>>nextPut:. If I'm not mistaken, this means that <primitive: 66> there does not work in this caseâ¦ So, to be short: is there a simple way to improve the performance? TIA >> >> -- >> Dennis Schetinin > > I am interested in this problem. > > Would it be possible to provide a test file (not that I can read Russian) and your test code ? > > I would like to try this myself. > > Sven >

Nov. 16, 2011

[Pharo-project] [update 1.4] #14227

by Marcus Denker

14227 ----- Issue 4976: MessageNotUnderstood: SolidFillStyle>>addFillStyleMenuItems:hand:from: http://code.google.com/p/pharo/issues/detail?id=4976 Issue 4972: NullStream breaks the debugger http://code.google.com/p/pharo/issues/detail?id=4972 -- Marcus Denker -- http://marcusdenker.de

Nov. 16, 2011

Re: [Pharo-project] Can we display and input chinese?

by Igor Stasenko

On 16 November 2011 09:30, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Hello > > A friend of me in Taiwan ask me about that because previous version of > DrGeo used to work with Chinese display and input. > Well, a more general question is does pharo supports unicode input/output: in general yes, but there could be some tweaks needed. For displaying chinese glyphs, first thing you need is to have a font with them, obviously. So, i would try first with changing font, and then see if there are more problems. > Hilaire > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > -- Best regards, Igor Stasenko.

Nov. 16, 2011