January 2018 - Pharo-users - lists.pharo.org

Regex: copy with ignoreCase

by Herbert VojÄÃk

Hi! String >> #asRegex return an instance of RxMatcher, as I tried. Now, I would like to get an object that behaves exactly as the one I got from asRegex, just that it ignores case (regardless whether it did or didn't in the original object). I understand it is not possible to get that object with existing API, is it? Herby

Jan. 29, 2018

Re: [Pharo-users] Sending notifications from Pharo to your Mobile via Pushover.net

by Todd Blanchard

Based on the icon and my mobile dev experience ... Either you need the Pushover app (hence the 'P' icon) to get a push notification or you can make your mobile app the recipient of the push notification (like UrbanAirship does) by including a library in your mobile app. For SMS I generally use Twilio or Plivo - either is a perfectly decent SMS service. Twilio and Plivo have similar REST apis and would have similar looking calls. -Todd Blanchard > On Jan 29, 2018, at 12:34 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > What is the difference between Pushover and other similar services? Do you need a Pushover client in the phone to handle such notifications? > > Nonetheless, the conciseness of Pharo with Zinc never ceases to amaze me. > > > Regards! > > Esteban A. Maringolo > > 2018-01-29 16:40 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>>: > Hi, > > Just a little snippet I wanted to share. Pushover (https://pushover.net <https://pushover.net/>) is a general service that delivers notifications to iOS, Android and desktop devices via an API (and an email gateway as well). It is really easy to get started with. > > This is how you do it from Pharo: > > ZnClient new > systemPolicy; > url: 'https://api.pushover.net/1/messages.json <https://api.pushover.net/1/messages.json>'; > accept: ZnMimeType applicationJson; > contentReader: [ :entity | NeoJSONObject fromString: entity contents ]; > contentWriter: [ :object | ZnEntity json: object asString ]; > contents: (NeoJSONObject new > token: 'ax4o55o6g5imb1a6st3m9x34hqu44z'; > user: 'uv2fovx3f9sp3rgssrupvjgvdo8quw'; > title: 'Test 3'; > message: ('This is a test @ {1} by {2}.' format: { > DateAndTime now. SystemVersion current })); > post. > > It will look like this on your mobile device (just seconds later): > > <PastedGraphic-1.png> > > Nothing special, but pretty handy. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org <http://pharo.org/> > http://association.pharo.org <http://association.pharo.org/> > http://consortium.pharo.org <http://consortium.pharo.org/> > > > > >

Jan. 29, 2018

Re: [Pharo-users] Sending notifications from Pharo to your Mobile via Pushover.net

by Esteban A. Maringolo

What is the difference between Pushover and other similar services? Do you need a Pushover client in the phone to handle such notifications? Nonetheless, the conciseness of Pharo with Zinc never ceases to amaze me. Regards! Esteban A. Maringolo 2018-01-29 16:40 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi, > > Just a little snippet I wanted to share. Pushover (https://pushover.net) > is a general service that delivers notifications to iOS, Android and > desktop devices via an API (and an email gateway as well). It is really > easy to get started with. > > This is how you do it from Pharo: > > ZnClient new > systemPolicy; > url: 'https://api.pushover.net/1/messages.json'; > accept: ZnMimeType applicationJson; > contentReader: [ :entity | NeoJSONObject fromString: entity contents ]; > contentWriter: [ :object | ZnEntity json: object asString ]; > contents: (NeoJSONObject new > token: 'ax4o55o6g5imb1a6st3m9x34hqu44z'; > user: 'uv2fovx3f9sp3rgssrupvjgvdo8quw'; > title: 'Test 3'; > message: ('This is a test @ {1} by {2}.' format: { > DateAndTime now. SystemVersion current })); > post. > > It will look like this on your mobile device (just seconds later): > > > Nothing special, but pretty handy. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Jan. 29, 2018

Re: [Pharo-users] Pharo IDE - change mouse cursor color/size

by Stephane Ducasse

Hi phil Yes we want to kill all the VM logic related to events because IT GETS ON OUR NERVES. Kill them all. Esteban told me that he is super upset by all the event / screen logic and that he is looking at ronie' changes. Stef On Mon, Jan 29, 2018 at 8:10 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > If you are on Windows you can load Vista cursors from the catalog. Then you > will have settings for the size. > > Not all cursors are implemented but it is easy to do. > > On Linux I had VM crashes when doing #beCursor. Maybe is it fixed these > days. > > Phil > > > On Jan 29, 2018 06:22, "Animosity" <bogdan.radacina+pharo(a)gmail.com> wrote: >> >> Hi there, >> >> I'm not able to find any setting in the Pharo IDE related to changing the >> mouse cursor color or size? >> Can this be done at all? Thanks in advance. >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

Jan. 29, 2018

Re: [Pharo-users] Iceberg and resource files

by Stephane Ducasse

Guille shows me a filesystem git accessed and browsed from Pharo. Soon to be public. On Mon, Jan 29, 2018 at 10:14 AM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi Ken, > >> Le 27 janv. 2018 Ã 15:38, kmo <voxkmp(a)gmail.com> a Ã©crit : >> >> I don't understand how iceberg handles resource files that you might also >> like to version along with the pharo code. > > For now, Iceberg do not really handle these files but it is planned in a next future. > >> Say I have an CSV file and a text file that my pharo application uses. How >> do I include these in the iceberg commit/push? How do I see changes made in >> these files from version to version? > > Currently, you cannot do anything related to this through the UI. > What you could do is to call directly Iceberg API to commit ressources to the git repository: > 1/ write the resource content in git working copy (std file system). There is a utility method: IceRepository>>#saveContent: aString inWorkingCopyFile: aRelativePathString > 2/ add these files to git index through: IceRepository>>addFilesToIndex: aListOfPaths > 3/ commit : > iceRepository > commitIndexWithMessage: commitMessage > andParents: { iceRepository headCommit } > > You can also read ressources by suing IceRepository>>#contentOfFileNamed: aPathString commit: aCommitId > > Christophe. > >> Does iceberg only handle pharo code? Generally git clients don't care about >> the file type - and it it is any kind of text you can see the actual >> differences between each commit. >> >> Ken >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Jan. 29, 2018

Re: [Pharo-users] Sending notifications from Pharo to your Mobile via Pushover.net

by Stephane Ducasse

Cool sven Is is a problem that you send you token/user around? Can I publish it on pharo weekly like that? Stef On Mon, Jan 29, 2018 at 8:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Just a little snippet I wanted to share. Pushover (https://pushover.net) > is a general service that delivers notifications to iOS, Android and > desktop devices via an API (and an email gateway as well). It is really > easy to get started with. > > This is how you do it from Pharo: > > ZnClient new > systemPolicy; > url: 'https://api.pushover.net/1/messages.json'; > accept: ZnMimeType applicationJson; > contentReader: [ :entity | NeoJSONObject fromString: entity contents ]; > contentWriter: [ :object | ZnEntity json: object asString ]; > contents: (NeoJSONObject new > token: 'ax4o55o6g5imb1a6st3m9x34hqu44z'; > user: 'uv2fovx3f9sp3rgssrupvjgvdo8quw'; > title: 'Test 3'; > message: ('This is a test @ {1} by {2}.' format: { > DateAndTime now. SystemVersion current })); > post. > > It will look like this on your mobile device (just seconds later): > > > Nothing special, but pretty handy. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Jan. 29, 2018

Sending notifications from Pharo to your Mobile via Pushover.net

by Sven Van Caekenberghe

Hi, Just a little snippet I wanted to share. Pushover (https://pushover.net) is a general service that delivers notifications to iOS, Android and desktop devices via an API (and an email gateway as well). It is really easy to get started with. This is how you do it from Pharo: ZnClient new systemPolicy; url: 'https://api.pushover.net/1/messages.json'; accept: ZnMimeType applicationJson; contentReader: [ :entity | NeoJSONObject fromString: entity contents ]; contentWriter: [ :object | ZnEntity json: object asString ]; contents: (NeoJSONObject new token: 'ax4o55o6g5imb1a6st3m9x34hqu44z'; user: 'uv2fovx3f9sp3rgssrupvjgvdo8quw'; title: 'Test 3'; message: ('This is a test @ {1} by {2}.' format: { DateAndTime now. SystemVersion current })); post. It will look like this on your mobile device (just seconds later): Nothing special, but pretty handy. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Jan. 29, 2018

Re: [Pharo-users] Problem with Traditional and Simplified Chinese parsing in Pharo

by ClÃ©ment BÃ©ra

Thanks all, Sven solution works. Yes this is not JSON it's some kind of JSON-like format (Is it yml ? I don't know it might be proprietary). I was naive and thought there was some metadata in files precising the encoding used, and that #readStream on FileReference was able to pick automatically the correct decoder. Obviously it isn't the case. Thanks anyway. 2018-01-29 18:59 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Your file is not in UTF-8 but in UTF-16 ! > > This will do: > > (FileLocator desktop / 'schinese.txt') readStreamDo: [ :in | > (ZnCharacterReadStream on: in binary encoding: #utf16) upToEnd ]. > > BTW, this is not valid JSON. > > From Windows, for sure ... > > > On 29 Jan 2018, at 18:49, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > > Hi, > > > > I am currently parsing lua and JSON-like file in Pharo. They contain > both Simplified and Traditional Chinese characters for comments and for > strings displayed in the UI. Lua files are parsed correctly. However the > JSON-like files aren't. > > > > In attachment I put one of the problematic file with Simplified chinese > characters (I've also copied the file at the end of the mail). The problem > can be shown as follow in Pharo: > > > > 'schinese.txt' asFileReference readStream contents > > > > The contents function sends a UTF8InvalidText 'Invalid utf8 input > detected' error. > > However my text editor correctly displays the file and it is correctly > parsed by the Lua runtime (The program parsed has been deployed in > production for years and works fine). > > > > What can I do to parse this file correctly from Pharo ? > > > > Thanks, > > > > Below is the file content, non Chinese people may not have the font to > display the characters, note that I have no idea what is written in Chinese > (Please don't hold me responsible if there are offending contents): > > > > "lang" > > { > > "Language" "Schinese" > > "Tokens" > > { > > "text_store_cd" "è´å£³ååºçååä¼æ¯å¤©éæºå·æ°! ä¸æ¬¡å·æ°å·å´æ¶é´" > > "text_cannot_huidaoguoqu" "ç°å¨ä¸è½ä½¿ç¨åå°è¿å»~" > > "tips1" "å©ç¨é¼ æ æ»è½®å¯ä»¥è°èè§è§è·ç¦»ï¼æ¹ä¾¿ä½ æ¥çåºå°å¨è²~" > > "tips2" "éè¿å¨é¨50å³ä»¥åä½ è¿å¯ä»¥ç»§ç»æææ´å æé¾åº¦çæ å°½è¯ç¼æ¨¡å¼ï¼" > > "tips3" "æ¯å¤©æ©æ¨è´å£³ååºä¼éæºå·æ°åéæºææï¼çå¿ä½ æ³è¦çååï¼" > > "tips4" "æè¡æ¦çå25åå¯ä»¥è·å¾çå å¥ç« ï¼è±¡å¾çä½ å¨å¡é²æ¸¸æä¸çåè¶æç»©ï¼" > > "tips5" "æ¯10æ³¢æäººä¼æä¸ä¸ªBOSSå³å¡ï¼å®æ¯æ®éæäººæ´é¾å»æ~" > > "tips6" "é£è¡çæäººä¸ä¼è¢«ç³å¤´é»æ¡ï¼æä»¥ä¸è½å©ç¨è¿·å®«æ¥å¢é¿æªç©ççº¿è·¯~" > > "tips7" "å¼å±çæ¶åç¹å»å·¦ä¸æ¹çè±ééæ©å¾æ å¯ä»¥æ¥çå¹¶éæ©ä½ æ¥æçè±éï¼" > > "tips8" "éèº«çæäººå¿é¡»éè¿èç½ç³»åå¡çç§æåç¯æè½è¢«åç°ï¼" > > "tips9" "ç¹å»å³ä¾§çåæå¬å¼æé®å¯ä»¥æå¼åæé¢æ¿ï¼äºè§£é«çº§å¡çåæä»¥åå½åéä»¶ç¶æ~" > > "tips10" "éè¯·å¥½åä¸èµ·æ¸¸æï¼å¯ä»¥äºç¸åä½å±åå¯¹æå¼ºå¤§çæäººï¼" > > "tips11" "ç³æ¿ä¼å¯¹è¸©ä¸å»çæäººäº§çææï¼æä»¥æå¥½æ¾ç½®å¨æäººå¿ç»çè·¯çº¿ä¸~" > > "tips12" "ä¸ºè±éè´ä¹°ç¾ä¸½çç¹æï¼å½ä½ å¯ä»¥ä¸åååæçæ¶åææéä»¶é½ä¼æç¹ææç¤ºï¼" > > "tips13" "æ¯ååä¼¤å®³æé«çå¡å°ä¼è·å¾æå¤10å±çMVPåç¯ï¼å¢å ç©çåéæ³è¾åºï¼" > > "tips14" "æ¯ä¸ªæçæåä¸å¤©æ¯èµå£ç»ç®æ¥ï¼å°ä¼æ ¹æ®ä½ è¿èµå£çæåé¢åä¸°åçè´å£³å¥å±ï¼" > > "tips15" "å¦æä¸ç¥éææ ·é è¿·å®«ï¼ä½ å¯ä»¥ç¹å»å³ä¾§çè¿·å®«æåæé®æ¥çæèåäº«æ¨èçè¿·å®«~" > > } > > } > > > > > > > > -- > > ClÃ©ment BÃ©ra > > Pharo consortium engineer > > https://clementbera.wordpress.com/ > > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > > <schinese.txt> > > >

Jan. 29, 2018

Re: [Pharo-users] Problem with Traditional and Simplified Chinese parsing in Pharo

by Cyril Ferlicot D.

Le 29/01/2018 Ã 18:49, ClÃ©ment Bera a Ã©critÂ : > Hi, > > I am currently parsing lua and JSON-like file in Pharo. They contain > both Simplified and Traditional Chinese characters for comments and for > strings displayed in the UI. Lua files are parsed correctly. However the > JSON-like files aren't. > > In attachment I put one of the problematic file with Simplified chinese > characters (I've also copied the file at the end of the mail). The > problem can be shown as follow in Pharo: > > 'schinese.txt' asFileReference readStream contents > > The contents function sends aÂ UTF8InvalidText 'Invalid utf8 input > detected' error. > However my text editor correctly displays the file and it is correctly > parsed by the Lua runtime (The program parsed has been deployed in > production for years and works fine). > > What can I do to parse this file correctly from Pharo ? > Hi, Here is how we manage encoding in Moose following Sven's advices. We detect the encoding of a file with this code: [ self fileReference binaryReadStreamDo: [ :in | (ZnCharacterEncoder detectEncoding: in upToEnd) identifier ] ] on: ZnCharacterEncodingError do: [ nil ] It is not bullet proof but I never got a problem since we use it. Then to read a file we do this: self fileReference binaryReadStreamDo: [ :in | (ZnCharacterReadStream on: in encoding: self encoding) upToEnd ] Here, self encoding return the result of the previous snippet. Or you can use it this way: ZnCharacterEncoder detectEncoding: ((FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | in upToEnd ]). (FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | | bytes encoder | bytes := in upToEnd. encoder := ZnCharacterEncoder detectEncoding: bytes. encoder decodeBytes: bytes ]. > Thanks, > > Below is the file content, non Chinese people may not have the font to > display the characters, note that I have no idea what is written in > Chinese (Please don't hold me responsible if there are offending contents): > > "lang" > { > "Language""Schinese" > "Tokens" > { > "text_store_cd""è´å£³ååºçååä¼æ¯å¤©éæºå·æ°! ä¸æ¬¡å·æ°å·å´æ¶é´" > "text_cannot_huidaoguoqu""ç°å¨ä¸è½ä½¿ç¨åå°è¿å»~" > "tips1""å©ç¨é¼ æ æ»è½®å¯ä»¥è°èè§è§è·ç¦»ï¼æ¹ä¾¿ä½ æ¥çåºå°å¨è²~" > "tips2""éè¿å¨é¨50å³ä»¥åä½ è¿å¯ä»¥ç»§ç»æææ´å æé¾åº¦çæ å°½è¯ç¼æ¨¡å¼ï¼" > "tips3""æ¯å¤©æ©æ¨è´å£³ååºä¼éæºå·æ°åéæºææï¼çå¿ä½ æ³è¦çååï¼" > "tips4""æè¡æ¦çå25åå¯ä»¥è·å¾çå å¥ç« ï¼è±¡å¾çä½ å¨å¡é²æ¸¸æä¸çåè¶æç»©ï¼" > "tips5""æ¯10æ³¢æäººä¼æä¸ä¸ªBOSSå³å¡ï¼å®æ¯æ®éæäººæ´é¾å»æ~" > "tips6""é£è¡çæäººä¸ä¼è¢«ç³å¤´é»æ¡ï¼æä»¥ä¸è½å©ç¨è¿·å®«æ¥å¢é¿æªç©ççº¿è·¯~" > "tips7""å¼å±çæ¶åç¹å»å·¦ä¸æ¹çè±ééæ©å¾æ å¯ä»¥æ¥çå¹¶éæ©ä½ æ¥æçè±éï¼" > "tips8""éèº«çæäººå¿é¡»éè¿èç½ç³»åå¡çç§æåç¯æè½è¢«åç°ï¼" > "tips9""ç¹å»å³ä¾§çåæå¬å¼æé®å¯ä»¥æå¼åæé¢æ¿ï¼äºè§£é«çº§å¡çåæä»¥åå½å > éä»¶ç¶æ~" > "tips10""éè¯·å¥½åä¸èµ·æ¸¸æï¼å¯ä»¥äºç¸åä½å±åå¯¹æå¼ºå¤§çæäººï¼" > "tips11""ç³æ¿ä¼å¯¹è¸©ä¸å»çæäººäº§çææï¼æä»¥æå¥½æ¾ç½®å¨æäººå¿ç»çè·¯çº¿ä¸~" > "tips12""ä¸ºè±éè´ä¹°ç¾ä¸½çç¹æï¼å½ä½ å¯ä»¥ä¸åååæçæ¶åææéä»¶é½ä¼æç¹ > ææç¤ºï¼" > "tips13""æ¯ååä¼¤å®³æé«çå¡å°ä¼è·å¾æå¤10å±çMVPåç¯ï¼å¢å ç©çåéæ³è¾åºï¼" > "tips14""æ¯ä¸ªæçæåä¸å¤©æ¯èµå£ç»ç®æ¥ï¼å°ä¼æ ¹æ®ä½ è¿èµå£çæåé¢åä¸°åç > è´å£³å¥å±ï¼" > "tips15""å¦æä¸ç¥éææ ·é è¿·å®«ï¼ä½ å¯ä»¥ç¹å»å³ä¾§çè¿·å®«æåæé®æ¥çæèåäº« > æ¨èçè¿·å®«~" > } > } > > > > -- > ClÃ©ment BÃ©ra > Pharo consortium engineer > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650Â Villeneuve d'Ascq -- Cyril Ferlicot https://ferlicot.fr

Jan. 29, 2018

Re: [Pharo-users] Problem with Traditional and Simplified Chinese parsing in Pharo

by Sven Van Caekenberghe

Your file is not in UTF-8 but in UTF-16 ! This will do: (FileLocator desktop / 'schinese.txt') readStreamDo: [ :in | (ZnCharacterReadStream on: in binary encoding: #utf16) upToEnd ]. BTW, this is not valid JSON. >From Windows, for sure ... > On 29 Jan 2018, at 18:49, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Hi, > > I am currently parsing lua and JSON-like file in Pharo. They contain both Simplified and Traditional Chinese characters for comments and for strings displayed in the UI. Lua files are parsed correctly. However the JSON-like files aren't. > > In attachment I put one of the problematic file with Simplified chinese characters (I've also copied the file at the end of the mail). The problem can be shown as follow in Pharo: > > 'schinese.txt' asFileReference readStream contents > > The contents function sends a UTF8InvalidText 'Invalid utf8 input detected' error. > However my text editor correctly displays the file and it is correctly parsed by the Lua runtime (The program parsed has been deployed in production for years and works fine). > > What can I do to parse this file correctly from Pharo ? > > Thanks, > > Below is the file content, non Chinese people may not have the font to display the characters, note that I have no idea what is written in Chinese (Please don't hold me responsible if there are offending contents): > > "lang" > { > "Language" "Schinese" > "Tokens" > { > "text_store_cd" "è´å£³ååºçååä¼æ¯å¤©éæºå·æ°! ä¸æ¬¡å·æ°å·å´æ¶é´" > "text_cannot_huidaoguoqu" "ç°å¨ä¸è½ä½¿ç¨åå°è¿å»~" > "tips1" "å©ç¨é¼ æ æ»è½®å¯ä»¥è°èè§è§è·ç¦»ï¼æ¹ä¾¿ä½ æ¥çåºå°å¨è²~" > "tips2" "éè¿å¨é¨50å³ä»¥åä½ è¿å¯ä»¥ç»§ç»æææ´å æé¾åº¦çæ å°½è¯ç¼æ¨¡å¼ï¼" > "tips3" "æ¯å¤©æ©æ¨è´å£³ååºä¼éæºå·æ°åéæºææï¼çå¿ä½ æ³è¦çååï¼" > "tips4" "æè¡æ¦çå25åå¯ä»¥è·å¾çå å¥ç« ï¼è±¡å¾çä½ å¨å¡é²æ¸¸æä¸çåè¶æç»©ï¼" > "tips5" "æ¯10æ³¢æäººä¼æä¸ä¸ªBOSSå³å¡ï¼å®æ¯æ®éæäººæ´é¾å»æ~" > "tips6" "é£è¡çæäººä¸ä¼è¢«ç³å¤´é»æ¡ï¼æä»¥ä¸è½å©ç¨è¿·å®«æ¥å¢é¿æªç©ççº¿è·¯~" > "tips7" "å¼å±çæ¶åç¹å»å·¦ä¸æ¹çè±ééæ©å¾æ å¯ä»¥æ¥çå¹¶éæ©ä½ æ¥æçè±éï¼" > "tips8" "éèº«çæäººå¿é¡»éè¿èç½ç³»åå¡çç§æåç¯æè½è¢«åç°ï¼" > "tips9" "ç¹å»å³ä¾§çåæå¬å¼æé®å¯ä»¥æå¼åæé¢æ¿ï¼äºè§£é«çº§å¡çåæä»¥åå½åéä»¶ç¶æ~" > "tips10" "éè¯·å¥½åä¸èµ·æ¸¸æï¼å¯ä»¥äºç¸åä½å±åå¯¹æå¼ºå¤§çæäººï¼" > "tips11" "ç³æ¿ä¼å¯¹è¸©ä¸å»çæäººäº§çææï¼æä»¥æå¥½æ¾ç½®å¨æäººå¿ç»çè·¯çº¿ä¸~" > "tips12" "ä¸ºè±éè´ä¹°ç¾ä¸½çç¹æï¼å½ä½ å¯ä»¥ä¸åååæçæ¶åææéä»¶é½ä¼æç¹ææç¤ºï¼" > "tips13" "æ¯ååä¼¤å®³æé«çå¡å°ä¼è·å¾æå¤10å±çMVPåç¯ï¼å¢å ç©çåéæ³è¾åºï¼" > "tips14" "æ¯ä¸ªæçæåä¸å¤©æ¯èµå£ç»ç®æ¥ï¼å°ä¼æ ¹æ®ä½ è¿èµå£çæåé¢åä¸°åçè´å£³å¥å±ï¼" > "tips15" "å¦æä¸ç¥éææ ·é è¿·å®«ï¼ä½ å¯ä»¥ç¹å»å³ä¾§çè¿·å®«æåæé®æ¥çæèåäº«æ¨èçè¿·å®«~" > } > } > > > > -- > ClÃ©ment BÃ©ra > Pharo consortium engineer > https://clementbera.wordpress.com/ > BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq > <schinese.txt>

Jan. 29, 2018