- Pharo-users - lists.pharo.org

How do I display a text in a text window?

by H. Hirzel

Hello I want to display a string (no code) in a text window. What is the equivalent of the Squeak expression StringHolder new textContents: (MyTextCollection at: 101); openLabel: 'theText 101' in Pharo 5.0? Regards Hannes

Sept. 1, 2016

Re: [Pharo-users] No right-button menu in Inspector on a ByteString

by H. Hirzel

However the text is incomplete there. No possibility to get it into the clip board. Question still open .... On 9/1/16, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Found the answer: > > the right-mouse button menu is only available in the 'raw' tab ... > > --H. > > On 9/1/16, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Hello >> >> I have an Inspector on n a ByteString open and would like to copy out >> the string into the clipboard. >> >> I can select the text but there is no right-mouse button menu to copy it. >> >> ALT-C just replaces the text with a c >> CTRL-C the same. >> >> I am using Pharo 5.0 on Linux Mint. >> >> In the preferences I found nothing how to activate a right mouse >> button menu nor something about activating an edit menu. >> >> What am I missing? >> >> Kind regards >> >> Hannes >> >

Sept. 1, 2016

Re: [Pharo-users] No right-button menu in Inspector on a ByteString

by H. Hirzel

Found the answer: the right-mouse button menu is only available in the 'raw' tab ... --H. On 9/1/16, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hello > > I have an Inspector on n a ByteString open and would like to copy out > the string into the clipboard. > > I can select the text but there is no right-mouse button menu to copy it. > > ALT-C just replaces the text with a c > CTRL-C the same. > > I am using Pharo 5.0 on Linux Mint. > > In the preferences I found nothing how to activate a right mouse > button menu nor something about activating an edit menu. > > What am I missing? > > Kind regards > > Hannes >

Sept. 1, 2016

No right-button menu in Inspector on a ByteString

by H. Hirzel

Hello I have an Inspector on n a ByteString open and would like to copy out the string into the clipboard. I can select the text but there is no right-mouse button menu to copy it. ALT-C just replaces the text with a c CTRL-C the same. I am using Pharo 5.0 on Linux Mint. In the preferences I found nothing how to activate a right mouse button menu nor something about activating an edit menu. What am I missing? Kind regards Hannes

Sept. 1, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by HernÃ¡n Morales Durand

Hi Peter, 2016-09-01 10:26 GMT-03:00 PBKResearch <peter(a)pbkresearch.co.uk>: > Hello > > > > I am using XPath as a way of dissecting web pages, especially from > Wiktionary. > Any specific reason to not use the SPARQL endpoint? > Generally I get good results, but I could get useful extra flexibility by > using the binary Smalltalk operators to represent XPath, as mentioned at > the end of the class comment for XPath. However, the description there is > very terse, and I am having difficulty seeing how to include more complex > expressions, especially attribute tests. > Which XPath version are you using? How did you installed it? > I have put some of my XPath expressions through the XPath compiler and > looked at the output, and out of that I have found expressions which work > but look very clumsy. As an example, I have used the fragment: > > > > document xPath: '//div[@id=''catlinks'']//li//text()' > > > > and found that an equivalent is: > > > > document //'div' ?? [:node :x :y|(node attributeAt: 'id') = > 'catlinks']//'li'//[:n| n isStringNode]]. > > (I had to put two dummy arguments in the three-argument block to get it to > work.) > > > > Is there a more extensive explanation of the use of these binary > operators? If not, could some kind person show me the most concise > translation of the sample XPath above, to give me a start in working out > more complex cases? > > > > Many thanks for any help. > > > > Peter Kenny > > >

Sept. 1, 2016

Re: [Pharo-users] Spec / GT Inspector integration

by Alistair Grant

Hi Nicolai, On Thu, Sep 01, 2016 at 11:00:29AM +0200, Nicolai Hess wrote: > > ... > > Here is an example how you can create a spec based presentation (an > IconListModel) ). > Add this method to the other gtInspectorMethods for class Morph (instance > side): > > gtInspectorSubmorphs2In: composite > Â Â Â <gtInspectorPresentationOrder: 80>Â > Â Â Â composite spec > Â Â Â Â Â Â title: 'Submorphs2'; > Â Â Â Â Â Â display: [:each ||lm| > Â Â Â Â Â Â Â Â Â lm:= IconListModel new. > Â Â Â Â Â Â Â Â Â lm items: each submorphs. > Â Â Â Â Â Â Â Â Â lm icons:[:item | item taskThumbnailOfSize: (16@16) ]. > Â Â Â Â Â Â Â Â Â lm displayBlock:[:item | item printString -> item class name]. > Â Â Â Â Â Â Â Â Â lm buildWithSpec. > Â Â Â Â Â Â Â Â Â lm > Â Â Â Â Â Â Â Â Â ] Perfect, thank you! I've made a note to create an example, either as a comment or using GT Examples, and submit it back for inclusion in the core image. Thanks again, Alistair

Sept. 1, 2016

Re: [Pharo-users] UFFI const, unsigned, opaque-ish types

by Esteban Lorenzano

well, I accept contributions :) I was thinking about enhance the parser too (but for allowing array declarations, not for unsigned)â¦ anyway, as soon as tests passes and backward compatibility is there, I would like to have a better parser, yes. cheers, Esteban > On 01 Sep 2016, at 18:40, Ben Coman <btc(a)openInWorld.com> wrote: > > Thanks Esteban. That worked. > > However it may be good to be more permissive about allowing const to > reduce the surprises for FFI users. Same for unsigned. > > Reviewing FFIExternalStructureFIeldParser>>praseFields:structure: > I see declarations are parsed simply left-to-right, which okay as the > simplest-thing-that-would-work. However (in case I get inspired...), > would this benefit from more complex parsing like described at [1] and > [2]? Or is this unlikely to be a concern in prcatice, and/or the rest > of FFI not ready receive such complex declarations from the parser? > > [1] http://www.geeksforgeeks.org/complicated-declarations-in-c/ > [2] http://unixwiz.net/techtips/reading-cdecl.html > > cheers -ben > > On Thu, Sep 1, 2016 at 2:01 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> (Short because I'm by phone) >> >> Const should be ignored so you can keep it (if not is a bug) >> Unsigned does not exist :) >> You can always put an alias, but the type you are looking for is "uint" >> >> Cheers, >> Esteban >> >>> On 31 Aug 2016, at 18:59, Ben Coman <btc(a)openinworld.com> wrote: >>> >>> For this definition pulled from a library header file... >>> typedef struct { >>> const void *data; >>> unsigned private_flags; >>> } CXString; >>> >>> which is used with a helper function to get a usable string like... >>> void show_clang_version(void) >>> { CXString version = clang_getClangVersion(); >>> printf("%s\n", clang_getCString(version)); >>> clang_disposeString(version); >>> } >>> >>> ==> 'Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on >>> LLVM 3.5.0)' >>> >>> >>> So I defined... >>> FFIExternalStructure subclass: #CXString >>> instanceVariableNames: '' >>> classVariableNames: '' >>> package: 'LibCLang' >>> >>> and ignoring the const as advised in the manual [1], I try... >>> CXString class >> fieldsDesc >>> ^ #( >>> void *data; >>> unsigned private_flags; >>> ) >>> >>> but... >>> CXString rebuildFieldAccessors. >>> ==>Error: Unable to resolve external type: unsigned >>> >>> I also tried "unsigned int private_flags;" >>> but get the same error. Any ideas what is wrong? >>> >>> >>> Actually I can kind of ignore creating accessors since this is like an >>> opaque type where I'm not expected to access its internals, but I do >>> need CXString as a return value like this... >>> >>> LibCLang class >> getClangVersion >>> ^ self ffiCall: #( CXString clang_getClangVersion () ) module: LibCLang >>> >>> which needs to be passed to this function to get a workable string.... >>> >>> LibCLang class >> getString: aCXString >>> ^ self ffiCall: #( String clang_getCString ( CXString aCXString ) >>> ) module: LibCLang >>> >>> However this doesn't work if I use FFIOpaqueObject instead of >>> FFIExternalStructure. >>> I guess the difference is opaque objects are normally pointers to a >>> type, whereas here that pointer is contained in a struct. >>> >>> What I've done at the moment to push ahead with experimenting is avoid >>> needing to generate accessors by adding... >>> >>> CXString >> printOn: asStream >>> self getString printOn: aStream >>> >>> CXString >> getString >>> ^ self ffiCall: #( String clang_getCString ( CXString self ) ) >>> module: LibCLang >>> >>> such that... >>> LibCLang getClangVersion "<Print It>" >>> ==> 'Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based >>> on LLVM 3.5.0)' >>> >>> >>> Is there a better way to approach this? >>> >>> cheers -ben >>> >>> btw, this is in Pharo 5 (Moose 6). >>> >>> [1] https://ci.inria.fr/pharo-contribution/view/Books/job/PharoBookWorkInProgre… >>> >> >

Sept. 1, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Alexandre Bergel

I do not see any apparent libraries on OSX. I am inspecting the content of the R application Package and it only contains images and some executables. Alexandre > On Sep 1, 2016, at 1:55 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com> wrote: > > Sorry, I havenât a Mac. > > First, you have to install R. > Then, I think you should only have to copy the R libraries (somewhere in the disk^^) to the Pharo VM folder. > > Tell me if it works ;) > > Vincent > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org <mailto:pharo-dev-bounces@lists.pharo.org>] De la part de Alexandre Bergel > EnvoyÃ© : jeudi 1 septembre 2016 17:49 > Ã : Any question about pharo is welcome > Cc : scismalltalk(a)googlegroups.com <mailto:scismalltalk@googlegroups.com>; Pharo Development List > Objet : Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1 > > I wanted to try, but there is no installation instruction for OS X :-( > Can you produce some on OS X? It would be great > > Anyway, this is great Vincent! Keep pushing! > > Alexandre > > > On Sep 1, 2016, at 12:42 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com <mailto:vincent.blondeau@worldline.com>> wrote: > > Hello everyone, > > I am glad to announce the release of version 2.1 of the RProjectConnector. > The binding between Pharo and R (https://www.r-project.org/ <https://www.r-project.org/>) is now translated to UFFI and so to Pharo 6.0. > > You can call directly your R methods from Pharo. For example, with the famous iris clustering example: > > iris := 'eval' asREval: {RObject findVar: 'iris'}. > 'plot' > asREval: > {(iris at: 'Petal.Length'). > (iris at: 'Petal.Width'). > (#pch -> 21). > (#xlab -> 'length'). > (#ylab -> 'Width'). > (#bg ->((iris at: 'Species') collect: [ :value | {'red'. 'green3'. 'blue'} at: value ])). > (#main -> 'Edgar Anderson''s Iris Data')}. > iris inspect. > > To use it, you should install R and copy the R libraries near the Pharo VM (see the documentation on SmalltalkHub (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector <http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector>) for how to proceed). > > Donât forget to relaunch Pharo after the installation to be able to use the connector. > > Only basic features are implemented yet, but you can participate to its extension! > > Cheers, > Vincent Blondeau > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" > > > !!!************************************************************************************* > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Sept. 1, 2016

Re: [Pharo-users] Coding XPath as Smalltalk

by PBKResearch

Hi CÃ©drik I started out using Soup, but I found out that it does what its name suggests, and jumbles up the contents of the pages. I now parse the pages with XMLHTMLParser, which preserves the original structure exactly. The point of XPath is that it is a convenient way of specifying a route through the structure to the desired information. So the XPath I cited says âfind a DIV node, at any depth, which has id=âcatlinksâ, then find a descendant which is a LI node, then find the text of any descendants.â Peter Hi Peter, Never used Path so I cannot help there. I just wander if you connote use Soup to Â« dissect Â» your webpages ? http://www.smalltalkhub.com/#!/~PharoExtras/Soup HTH, CÃ©drik Le 1 sept. 2016 Ã 15:26, PBKResearch <peter(a)pbkresearch.co.uk <mailto:peter@pbkresearch.co.uk> > a Ã©crit : Hello I am using XPath as a way of dissecting web pages, especially from Wiktionary. Generally I get good results, but I could get useful extra flexibility by using the binary Smalltalk operators to represent XPath, as mentioned at the end of the class comment for XPath. However, the description there is very terse, and I am having difficulty seeing how to include more complex expressions, especially attribute tests. I have put some of my XPath expressions through the XPath compiler and looked at the output, and out of that I have found expressions which work but look very clumsy. As an example, I have used the fragment: document xPath: '//div[@id=''catlinks'']//li//text()' and found that an equivalent is: document //'div' ?? [:node :x :y|(node attributeAt: 'id') = 'catlinks']//'li'//[:n| n isStringNode]]. (I had to put two dummy arguments in the three-argument block to get it to work.) Is there a more extensive explanation of the use of these binary operators? If not, could some kind person show me the most concise translation of the sample XPath above, to give me a start in working out more complex cases? Many thanks for any help. Peter Kenny

Sept. 1, 2016

Re: [Pharo-users] [Pharo-dev] [ANN] RProjectConnector V2.1

by Blondeau Vincent

Sorry, I havenât a Mac. First, you have to install R. Then, I think you should only have to copy the R libraries (somewhere in the disk^^) to the Pharo VM folder. Tell me if it works ;) Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Alexandre Bergel EnvoyÃ© : jeudi 1 septembre 2016 17:49 Ã : Any question about pharo is welcome Cc : scismalltalk(a)googlegroups.com; Pharo Development List Objet : Re: [Pharo-dev] [Pharo-users] [ANN] RProjectConnector V2.1 I wanted to try, but there is no installation instruction for OS X :-( Can you produce some on OS X? It would be great Anyway, this is great Vincent! Keep pushing! Alexandre On Sep 1, 2016, at 12:42 PM, Blondeau Vincent <vincent.blondeau(a)worldline.com<mailto:vincent.blondeau@worldline.com>> wrote: Hello everyone, I am glad to announce the release of version 2.1 of the RProjectConnector. The binding between Pharo and R (https://www.r-project.org/) is now translated to UFFI and so to Pharo 6.0. You can call directly your R methods from Pharo. For example, with the famous iris clustering example: iris := 'eval' asREval: {RObject findVar: 'iris'}. 'plot' asREval: {(iris at: 'Petal.Length'). (iris at: 'Petal.Width'). (#pch -> 21). (#xlab -> 'length'). (#ylab -> 'Width'). (#bg ->((iris at: 'Species') collect: [ :value | {'red'. 'green3'. 'blue'} at: value ])). (#main -> 'Edgar Anderson''s Iris Data')}. iris inspect. To use it, you should install R and copy the R libraries near the Pharo VM (see the documentation on SmalltalkHub (http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector) for how to proceed). Donât forget to relaunch Pharo after the installation to be able to use the connector. Only basic features are implemented yet, but you can participate to its extension! Cheers, Vincent Blondeau !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!" !!!************************************************************************************* "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.!!!"

Sept. 1, 2016