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

Re: [Pharo-dev] Touch Events VM changes

by Alexandre Bergel

Thanks Jeff for this analysis. This is instructing. Cheers, Alexandre > On 11 Mar 2014, at 08:54, "J.F. Rick" <self(a)je77.com> wrote: > > Hi Sergi, > > Based on my experience developing touch interfaces since 2007, I believe in touch. I believe it will be the future of interfaces and I believe it can be better than mouse-keyboard interfaces. That said, it is not there yet. Now is the time to innovate and get it there so that touch interfaces won't be poor replicas of their desktop forebears. Currently, text entry is a real problem for touch exclusive devices, but there is progress being made on that front. We don't have the answer yet but I think it will be a significantly different landscape in five years. In regards to touch vs physical pointers, this is not as large of a problem as people make it out to be. It is just that our widgets tend to be created for mouse-based interfaces and therefore don't transition well to touch. Interfaces designed with touch in mind can be just as smooth (if not smoother) as mouse-based interfaces. You just have to take advantage of what touch does well (faster, more precise routes; multi-touch gestures; bimanual interaction) and stay clear of things it does poorly (precise touch down, covering the target with the finger). > > Cheers, > > Jeff > > >> On Tue, Mar 11, 2014 at 12:34 PM, Sergi Reyner <sergi.reyner(a)gmail.com> wrote: >> 2014-03-11 10:37 GMT+00:00 J.F. Rick <self(a)je77.com>: >> >>> As we move from mouse-keyboard devices to touch-based ones >> >> I certainly hope that "we" refers to a small group of people, unless we get onscreen keyboards as good as physical ones, feedback included. The same goes for touch versus physical pointer :) >> >> Cheers, >> Sergi > > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

March 12, 2014

Re: [Pharo-dev] Status of the VM?

by Jan Vrany

Hi Eliot, >> Anyway, the interesting question to me is what are the advantages >> of your approach? > > One is interactivity. The tool supports drilling down to instruction > level, which is good for critical code sequences such as method > prolog. > > Another is comprehensibility. Because it can distinguish between > generated machine code (specific methods and runtime routines), > functions in the VM and other support code (including stuff like > Linux on stack system call entry) one sees all activities in the VM > presented meaningfully. > That's of course important, I agree. But if one uses out-of-image tools, this could be seen too, couldn't it? If one uses tools like OProfile or cachegrind, all this data are collected and available for analysis. > Another is evolvability. Because it's written in smalltalk I can > develop the tool quickly and do so while I'm using it. > But this is because it's written in Smalltalk rather than because it runs within the debugee/profilee, no? Jan

March 12, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30794 Home: https://github.com/pharo-project/pharo-core

March 12, 2014

[pharo-project/pharo-core] f2fdea: 30794

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: f2fdeae83a7dc59af7365161da3ecdec7b01a0e9 https://github.com/pharo-project/pharo-core/commit/f2fdeae83a7dc59af7365161… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-03-12 (Wed, 12 Mar 2014) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script447.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30794.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/AbstractEyeElement.class/instance/accessing/longLabel.st M Spec-Inspector.package/EyeTreeInspector.class/instance/api/childrenForObject_.st A Zinc-Character-Encoding-Core.package/ZnByteEncoder.class/class/convenience/iso88591.st A Zinc-Character-Encoding-Core.package/ZnByteEncoder.class/class/convenience/latin1.st A Zinc-Character-Encoding-Core.package/ZnByteEncoder.class/instance/converting/backOnStream_.st M Zinc-Character-Encoding-Core.package/ZnCharacterEncoder.class/README.md A Zinc-Character-Encoding-Core.package/ZnCharacterEncoder.class/instance/converting/backOnStream_.st A Zinc-Character-Encoding-Core.package/ZnNullEncoder.class/instance/converting/backOnStream_.st M Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/README.md M Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/definition.st A Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/accessing/decodePlusAsSpace.st M Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/converting/decode_.st M Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/converting/decode_to_.st M Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/converting/encode_.st A Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/converting/errorAsciiCharacterExpected.st A Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/error handling/errorHexDigitExpected.st A Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/initialize-release/decodePlusAsSpace_.st M Zinc-Character-Encoding-Core.package/ZnPercentEncoder.class/instance/private/readHexFrom_.st A Zinc-Character-Encoding-Core.package/ZnUTF16Encoder.class/instance/converting/backOnStream_.st A Zinc-Character-Encoding-Core.package/ZnUTF16Encoder.class/instance/private/back16BitWordOnStream_.st A Zinc-Character-Encoding-Core.package/ZnUTF8Encoder.class/instance/converting/backOnStream_.st A Zinc-Character-Encoding-Tests.package/ZnCharacterEncoderTests.class/instance/testing/testUTF16Back.st A Zinc-Character-Encoding-Tests.package/ZnCharacterEncoderTests.class/instance/testing/testUTF8Back.st A Zinc-Character-Encoding-Tests.package/ZnPercentEncoderTests.class/instance/testing/testDecodePlusAsSpace.st R Zinc-HTTP.package/ZnBivalentWriteStream.class/instance/accessing/print_.st M Zinc-HTTP.package/ZnChunkedWriteStream.class/instance/accessing/extraHeaders.st M Zinc-HTTP.package/ZnClient.class/instance/accessing request/accept_.st M Zinc-HTTP.package/ZnClient.class/instance/accessing request/headerAddAll_.st M Zinc-HTTP.package/ZnClient.class/instance/accessing request/method_.st M Zinc-HTTP.package/ZnClient.class/instance/accessing request/resetEntity.st M Zinc-HTTP.package/ZnClient.class/instance/accessing request/setBasicAuthenticationUsername_password_.st A Zinc-HTTP.package/ZnClient.class/instance/options/autoResetEntityMethods.st A Zinc-HTTP.package/ZnClient.class/instance/options/autoResetEntityMethods_.st M Zinc-HTTP.package/ZnDefaultServerDelegate.class/instance/initialization/initialize.st A Zinc-HTTP.package/ZnDefaultServerDelegate.class/instance/responses/formTest1_.st M Zinc-HTTP.package/ZnNetworkingUtils.class/class/constants/socketStreamTimeout.st M Zinc-HTTP.package/ZnReadEvalPrintDelegate.class/instance/private/evaluate_.st R Zinc-HTTP.package/ZnStandardOutputLogger.class/instance/initialization/initialize.st M Zinc-HTTP.package/ZnUtils.class/class/conversions/decodeBase64_.st M Zinc-HTTP.package/ZnUtils.class/class/conversions/encodeBase64_.st M Zinc-HTTP.package/ZnUtils.class/class/conversions/httpDate_.st M Zinc-HTTP.package/ZnValueDelegate.class/class/instance creation/with_.st M Zinc-Resource-Meta-Core.package/ZnMimeType.class/instance/testing/isBinary.st A Zinc-Resource-Meta-Core.package/ZnResourceMetaUtils.class/class/accessing/queryKeyValueSafeSet.st A Zinc-Resource-Meta-Core.package/ZnResourceMetaUtils.class/class/conversions/decodePercentForQuery_.st M Zinc-Resource-Meta-Core.package/ZnResourceMetaUtils.class/class/conversions/decodePercent_.st M Zinc-Resource-Meta-Core.package/ZnResourceMetaUtils.class/class/conversions/parseQueryFrom_.st M Zinc-Resource-Meta-Core.package/ZnResourceMetaUtils.class/class/conversions/writeQueryFields_withTextEncoding_on_.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/parsing/parseFrom_defaultScheme_.st M Zinc-Resource-Meta-Tests.package/ZnMimeTypeTests.class/instance/testing/testIsBinary.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testNoSchemeColonInPath.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testPlusHandling.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testQueryEncodingExtended.st M Zinc-Tests.package/ZnClientTests.class/instance/private/withServerDo_.st M Zinc-Tests.package/ZnClientTests.class/instance/testing/testGetAfterPost.st A Zinc-Tests.package/ZnClientTests.class/instance/testing/testGetForm.st M Zinc-Tests.package/ZnClientTests.class/instance/testing/testProgress.st M Zinc-Tests.package/ZnDispatcherDelegateTest.class/instance/private/withServerDo_.st M Zinc-Tests.package/ZnEasyTests.class/instance/private/withServerDo_.st M Zinc-Tests.package/ZnImageExampleDelegateTests.class/instance/private/withServerDo_.st M Zinc-Tests.package/ZnServerTests.class/instance/private/port.st A Zinc-Tests.package/ZnServerTests.class/instance/private/runningOnWindows.st M Zinc-Tests.package/ZnServerTests.class/instance/private/usingClassicSocketStreamsOnWindowsDo_.st M Zinc-Tests.package/ZnServerTests.class/instance/private/withServerDo_.st M Zinc-Tests.package/ZnServerTests.class/instance/testing/testEchoLocalInterface.st A Zinc-Tests.package/ZnServerTests.class/instance/testing/testFormTest1.st M Zinc-Tests.package/ZnStaticFileServerDelegateTests.class/instance/private/withServerDo_.st M Zinc-Tests.package/ZnStaticFileServerDelegateTests.class/instance/tests/testBasicGet.st M Zinc-Tests.package/ZnStaticFileServerDelegateTests.class/instance/tests/testBasicGetLarge.st M Zinc-Tests.package/ZnStaticFileServerDelegateTests.class/instance/tests/testBasicGetWide.st M Zinc-Tests.package/ZnStaticFileServerDelegateTests.class/instance/tests/testBasicHead.st A Zinc-Zodiac.package/ZnHTTPSTests.class/instance/private/runningOnWindows.st M Zinc-Zodiac.package/ZnHTTPSTests.class/instance/private/runningOnWindowsInriaCI.st R Zodiac-Core.package/ZdcAbstractSocketStream.class/instance/initialization/initialize.st A Zodiac-Core.package/ZdcAbstractSocketStream.class/instance/initialize-release/initialize.st R Zodiac-Core.package/ZdcPluginSSLSession.class/instance/initialization/initialize.st A Zodiac-Core.package/ZdcPluginSSLSession.class/instance/initialize/initialize.st R Zodiac-Core.package/ZdcSecureSocketStream.class/instance/initialization/initialize.st A Zodiac-Core.package/ZdcSecureSocketStream.class/instance/initialize-release/initialize.st Log Message: ----------- 30794 13052 EyeTreeInspector does not respect the description of EyeDynamicElement https://pharo.fogbugz.com/f/cases/13052 13058 Smalltalk tools explore does not work where Smalltalk tools inspect does. https://pharo.fogbugz.com/f/cases/13058 12989 Zn Update https://pharo.fogbugz.com/f/cases/12989/ http://files.pharo.org/image/30/30794.zip

March 12, 2014

Re: [Pharo-dev] Sort by property

by Nicolas Cellier

I presume you all know about Griggs work on the subject http://stackoverflow.com/questions/8204826/smalltalk-sort-a-collection-by-t… http://objology.blogspot.com/2010/11/tag-sortfunctions.html 2014-03-12 11:23 GMT+01:00 carlo.t <snoobabk(a)yahoo.ie>: > Hi Otto > > I think the main reason is to support the second usage scenario: > SequenceableCollection withAllSubclasses sortedAs: [:class | class > methodDict size]. > We could try and unify the sort: method to take only blocks while sortedAs: > a symbol but then at the same time we could just put everything into one > method and use cull: perhaps to handle all the scenarios. > > Personally I don't feel too comfortable with the code below, apart from the > performance penalties it also feels like code that is too 'clever' for > itself which obviously makes it complicated to understand and modify. I > wrote it mainly for people to voice opinions and get ideas flowing. I'd > have > 2 separate sort methods so that users can choose if they want the runtime > characteristics of either. > > Example which can handle all current scenarios i.e. symbol or block taking > 1 > or 2 arguments: > SequenceableCollection>>sort: aSortBlock > self > mergeSortFrom: 1 > to: self size > by: (self createSortBlock: aSortBlock) > > > SequenceableCollection>>createSortBlock: aSortBlockOrSymbol > ^ aSortBlockOrSymbol numArgs < 2 > ifTrue: [[ :a :b | (#(true false ) > includes: (aSortBlockOrSymbol > value: a)) > ifTrue: [ aSortBlockOrSymbol value: a] > ifFalse: [(aSortBlockOrSymbol value: a) < > (aSortBlockOrSymbol value: > b)]]] > ifFalse: [[:a :b | aSortBlockOrSymbol cull: a cull: b]] > > > BTW the previous versions had a bug where it fails when called on an empty > collection as the true/false check is done eagerly. > > Cheers > Carlo > > > > -- > View this message in context: > http://forum.world.st/Sort-by-property-tp4748500p4748757.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

March 12, 2014

Re: [Pharo-dev] ****REALLY IMPORTANT**** the Pharo market place NEEDS YOU

by Esteban Lorenzano

+1 (but AFAIK, versionner can do that) Esteban On 12 Mar 2014, at 11:37, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 12 Mar 2014, at 11:28, jannik laval <jannik.laval(a)gmail.com> wrote: > >> At least, what could be really great is to have the MetaRepo inside the monticello browser, Like that I don't loose time to retrieve the correct url on smalltalkhub and/or ss3. > > +1 > >

March 12, 2014

Re: [Pharo-dev] ****REALLY IMPORTANT**** the Pharo market place NEEDS YOU

by Pharo4Stef

> >> At least, what could be really great is to have the MetaRepo inside the monticello browser, Like that I don't loose time to retrieve the correct url on smalltalkhub and/or ss3. > > +1 I need people to help :)

March 12, 2014

Re: [Pharo-dev] ****REALLY IMPORTANT**** the Pharo market place NEEDS YOU

by Sven Van Caekenberghe

On 12 Mar 2014, at 11:28, jannik laval <jannik.laval(a)gmail.com> wrote: > At least, what could be really great is to have the MetaRepo inside the monticello browser, Like that I don't loose time to retrieve the correct url on smalltalkhub and/or ss3. +1

March 12, 2014

Re: [Pharo-dev] ****REALLY IMPORTANT**** the Pharo market place NEEDS YOU

by jannik laval

Dears, I am using the Catalog for Pharo 2 and 3 for Phratch. My main problem is that when I update my configuration, I have to save it in my repository but also in the MetaRepo. I don't know if an automatic process can be made ? At least, what could be really great is to have the MetaRepo inside the monticello browser, Like that I don't loose time to retrieve the correct url on smalltalkhub and/or ss3. I love this catalog, and I would like to see it always up to date. Cheers, Jannik 2014-03-12 8:29 GMT+01:00 Pharo4Stef <pharo4Stef(a)free.fr>: > Hi guys > > We would like to improve the visibility of Pharo by > - renaming the catalog of published package to marketPlace :) > > - have many more projects decently documented > > Yes click that link: > > https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/ > ? > > So I imagine that you are all like me: you are too busy to add the correct > information > because you do not know what/how/. So I created a little class: called > CatalogAdder for you and me :P > It is available in last version of Versionner but > > I'm a simple utility class that add methods to ConfigurationOf class to > declare catalog metadata. > > Gofer new > smalltalkhubUser: 'DamienCassou' project: 'Pier-Gutemberg'; > package: 'CatalogAdder'; > load. > > (CatalogAdder on: ConfigurationOfXXX) > defineCatalogMetadata > > and it creates all the methods with dummy template for you :) > > Check the catalog* methods and fill them up. > > Stef > > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://car.mines-douai.fr/

March 12, 2014

Re: [Pharo-dev] Making Git and Pharo More Accessible

by Goubier Thierry

Le 12/03/2014 11:18, Max Leske a Ã©crit : > > Will do. Thanks, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

March 12, 2014