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

[pharo-project/pharo-core] 364f4b: 40026

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 364f4b8d02889711941dcacbde2d7bd764f7a564 https://github.com/pharo-project/pharo-core/commit/364f4b8d02889711941dcacb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-06-20 (Fri, 20 Jun 2014) Changed paths: M OpalCompiler-Core.package/SyntaxErrorNotification.class/README.md M OpalCompiler-Core.package/SyntaxErrorNotification.class/definition.st M OpalCompiler-Core.package/SyntaxErrorNotification.class/instance/accessing/errorMessage.st R OpalCompiler-Core.package/SyntaxErrorNotification.class/instance/accessing/messageText.st M OpalCompiler-Core.package/SyntaxErrorNotification.class/instance/accessing/setClass_category_code_doitFlag_errorMessage_location_.st M ProfStef-Core.package/PharoSyntaxTutorial.class/instance/interactive/prepareDebuggerExample.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script26.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40026.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40026 11987 Launching ProfStef should now require initials https://pharo.fogbugz.com/f/cases/11987 12579 SyntaxErrorNotification>>messageText https://pharo.fogbugz.com/f/cases/12579 http://files.pharo.org/image/40/40026.zip

June 20, 2014

[pharo-project/pharo-core]

by GitHub

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

June 20, 2014

Re: [Pharo-dev] How to convert properyl an Athens Surface to a Form

by Igor Stasenko

the best way is to blit surface on the morphic canvas using displayOnMorphicCanvas: canvas at: aPoint method. On 19 June 2014 22:16, Nicolai Hess <nicolaihess(a)web.de> wrote: > I use asForm and it works for me. > can you create a screenshot with the odd result > it creates. > > > > > > > > > 2014-06-19 21:58 GMT+02:00 Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > : > > Hi, >> I can't find it. #asForm message produce odd result for me. >> >> Hilaire >> >> >> > -- Best regards, Igor Stasenko.

June 20, 2014

Re: [Pharo-dev] Athens and StrikeFont ( again )

by Igor Stasenko

On 20 June 2014 02:01, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Times to times, font are displayed in a very weir fashion: small and big > letter. Width is not properly computed in addition. > > that should be fixed already.. i will check. > Alexandre > > > Le 19-06-2014 Ã 18:26, Nicolai Hess <nicolaihess(a)web.de> a Ã©crit : > > > > > > If I take a fresh pharo image I always have to reenable FT fonts before > > doing any athens rendering with text > > (RMOD StrikeFont(Object)>>doesNotUnderstand: #getPreciseHeight). > > > > Ok, I know I have to > > open settings > > disable then > > enable FreeType > > and choose a FreeType font. > > > > But what exactly is the problem with Athens rendering and non FT fonts? > > > > > > Nicolai > > -- Best regards, Igor Stasenko.

June 20, 2014

Re: [Pharo-dev] The importance of Class Comments

by Sven Van Caekenberghe

You are not targeting me, you are targeting everybody, that is why I, as a member of this community trying to improve things, feel offended. By saying 'the class comments are not good', you imply all of them. If I say 'people from country X are lazy' or even 'many/most of them are lazy', most people of that country, especially those who are definitively not will be rightfully offended. It is a generalisation that creates a bad reputation which is unfair. Of course you don't have to call out individual people, but if there are large packages out there (inside Pharo even) with 10s or 100s of classes with zero comments, then we as users have every right to say WTF !? And for me, those are terrible parts (with respects to documentation), because it is very hard to even start looking at the code and find your way. Spec _is_ partially documented - the website www.spec.org and the papers are pretty good - it took Ben and Johan lots of time and I appreciate that a lot. The problem of Spec is that it is a bit strange, hard to get your finger on (it is a UI specification, abstraction and composition layer, not a GUI toolkit as such). It confuses people (things are called model, but these are UI models, not domain models). Furthermore, it evolved a lot so that there are historic inconsistencies between current code, examples and documentation. But I know you are helping to improve Pharo, especially around documentation, so I am not angry at all - I know for a fact that the situation around documentation has been improving a lot, and improvements accelerated in the last year. On 20 Jun 2014, at 12:17, kilon alios <kilon.alios(a)gmail.com> wrote: > " It sounds a bit like there is no documentation at all" > > Î never implied this, and I refuse to believe that my wording can sound like that. I just say that the class comments are usually too small and many important classes are not documented at all. I don't know why you think I targeted you specifically with my comments. > > "terrible parts" is not the word I will use. I find the lack of documentation frustrating but that does not make the classes themselves "terrible". Pharo has its fair share of messy code but I have failed to see something I would call terrible. > > Its awesome that you spent large amount of time documenting, but all I said is that documenting key classes in the range of 10-15 lines each should not take a lot of time and pharo developers should do it. Thats my opinion, you are more than welcome to disagree or ignore it. > > I am willing to help any way I can. I am not willing to put blame on people. > > I do feel however because I believe I am a logical person that people that are introduced to Pharo will be disappointed in this department as I am. I think this is unfair to Pharo, because you guys have put a lot of effort in it that partly goes to waste. Imagine what would happen if people had easy access to the libraries , how many more would contribute and help pharo. > > I cannot imagine where I would be if there was no PBE or PFTE or the class comments that already are in there. For me any form of documentation is like bread and butter. > > Am I unreasonable ? > > I hope not. > > > > > On Fri, Jun 20, 2014 at 11:45 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I am a bit offended by the generalisations in your remarks, Kilon. It sounds a bit like there is no documentation at all. > > There are several books, covering many of the high level aspects. > > There is lots of documentation in the image, many class comments are pretty good, as are many method comments - even quite a lot of implementation comments can be found. > > OK, there are some terrible parts as well, and some people seems to make a sport out of _not_ writing any comments at all - please call them out specifically, but don't generalise. > > I have spent a large amount of time documenting all code that I published as well as writing separate high level documentation and tutorials for most of it as well as for Pharo in general. I know many others who did the same. > > On 20 Jun 2014, at 10:10, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > I have not worked with spec a lot, but I think that itâs nice in terms of comments, they are very helpful. Also lately Iâve worked with Roassal2 - no comments at all, but you can ask Alex for help :) > > > > Uko > > > > On 20 Jun 2014, at 10:06, kilon alios <kilon.alios(a)gmail.com> wrote: > > > >> yes good idea Damien , thank you. Right now I am working with Rubric building a new workspace tool basing it on the rubric example. Spec and Morphic are on my list too. > >> > >> Should I open also an issue on the bug tracker with a slice of my class comment ? Or is posting it here enough ? > >> > >> > >> On Fri, Jun 20, 2014 at 10:47 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> > >> On Fri, Jun 20, 2014 at 9:10 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> Saying that I will start adding class comments wherever I can but obviously the people that have created the code are far more qualified than me . > >> > >> > >> I suggest that you ask on this mailing list when you would like to have documentation on a class and you can't write it yourself. That way, we all will read the answer. Hopefully, someone, will merge this and write a class comment. > >> > >> > >> -- > >> Damien Cassou > >> http://damiencassou.seasidehosting.st > >> > >> "Success is the ability to go from one failure to another without losing enthusiasm." > >> Winston Churchill > >> > > > > >

June 20, 2014

Linking to online documentation

by kilon alios

Hello guys I want to create a small documentation tool that will display my own documentation for classes and methods and then have a more info button for linking to existing documentation online. Any quick pointers how I do that, creating the button should be no problem but I don't know how to trigger an internet browser and send it to a specific web address. Any ideas ?

June 20, 2014

Re: [Pharo-dev] The importance of Class Comments

by kilon alios

I think some Spec class comments could be bigger maybe with a couple of sort examples. Now that we have an online reference for Pharo it would be important if class comments are lengthier even if the information is covered in the PFTE Spec tutorial. But I will investigate further to see what I can propose in terms of actual comments. On Fri, Jun 20, 2014 at 11:10 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > I have not worked with spec a lot, but I think that itâs nice in terms of > comments, they are very helpful. Also lately Iâve worked with Roassal2 - no > comments at all, but you can ask Alex for help :) > > Uko > > > On 20 Jun 2014, at 10:06, kilon alios <kilon.alios(a)gmail.com> wrote: > > yes good idea Damien , thank you. Right now I am working with Rubric > building a new workspace tool basing it on the rubric example. Spec and > Morphic are on my list too. > > Should I open also an issue on the bug tracker with a slice of my class > comment ? Or is posting it here enough ? > > > On Fri, Jun 20, 2014 at 10:47 AM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: > >> >> On Fri, Jun 20, 2014 at 9:10 AM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> Saying that I will start adding class comments wherever I can but >>> obviously the people that have created the code are far more qualified than >>> me . >>> >> >> >> I suggest that you ask on this mailing list when you would like to have >> documentation on a class and you can't write it yourself. That way, we all >> will read the answer. Hopefully, someone, will merge this and write a class >> comment. >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without losing >> enthusiasm." >> Winston Churchill >> > > >

June 20, 2014

Re: [Pharo-dev] The importance of Class Comments

by kilon alios

" It sounds a bit like there is no documentation at all" Î never implied this, and I refuse to believe that my wording can sound like that. I just say that the class comments are usually too small and many important classes are not documented at all. I don't know why you think I targeted you specifically with my comments. "terrible parts" is not the word I will use. I find the lack of documentation frustrating but that does not make the classes themselves "terrible". Pharo has its fair share of messy code but I have failed to see something I would call terrible. Its awesome that you spent large amount of time documenting, but all I said is that documenting key classes in the range of 10-15 lines each should not take a lot of time and pharo developers should do it. Thats my opinion, you are more than welcome to disagree or ignore it. I am willing to help any way I can. I am not willing to put blame on people. I do feel however because I believe I am a logical person that people that are introduced to Pharo will be disappointed in this department as I am. I think this is unfair to Pharo, because you guys have put a lot of effort in it that partly goes to waste. Imagine what would happen if people had easy access to the libraries , how many more would contribute and help pharo. I cannot imagine where I would be if there was no PBE or PFTE or the class comments that already are in there. For me any form of documentation is like bread and butter. Am I unreasonable ? I hope not. On Fri, Jun 20, 2014 at 11:45 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I am a bit offended by the generalisations in your remarks, Kilon. It > sounds a bit like there is no documentation at all. > > There are several books, covering many of the high level aspects. > > There is lots of documentation in the image, many class comments are > pretty good, as are many method comments - even quite a lot of > implementation comments can be found. > > OK, there are some terrible parts as well, and some people seems to make a > sport out of _not_ writing any comments at all - please call them out > specifically, but don't generalise. > > I have spent a large amount of time documenting all code that I published > as well as writing separate high level documentation and tutorials for most > of it as well as for Pharo in general. I know many others who did the same. > > On 20 Jun 2014, at 10:10, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > > I have not worked with spec a lot, but I think that itâs nice in terms > of comments, they are very helpful. Also lately Iâve worked with Roassal2 - > no comments at all, but you can ask Alex for help :) > > > > Uko > > > > On 20 Jun 2014, at 10:06, kilon alios <kilon.alios(a)gmail.com> wrote: > > > >> yes good idea Damien , thank you. Right now I am working with Rubric > building a new workspace tool basing it on the rubric example. Spec and > Morphic are on my list too. > >> > >> Should I open also an issue on the bug tracker with a slice of my class > comment ? Or is posting it here enough ? > >> > >> > >> On Fri, Jun 20, 2014 at 10:47 AM, Damien Cassou < > damien.cassou(a)gmail.com> wrote: > >> > >> On Fri, Jun 20, 2014 at 9:10 AM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> Saying that I will start adding class comments wherever I can but > obviously the people that have created the code are far more qualified than > me . > >> > >> > >> I suggest that you ask on this mailing list when you would like to have > documentation on a class and you can't write it yourself. That way, we all > will read the answer. Hopefully, someone, will merge this and write a class > comment. > >> > >> > >> -- > >> Damien Cassou > >> http://damiencassou.seasidehosting.st > >> > >> "Success is the ability to go from one failure to another without > losing enthusiasm." > >> Winston Churchill > >> > > > > >

June 20, 2014

Re: [Pharo-dev] vm over android

by ClÃ©ment Bera

2014-06-20 10:16 GMT+02:00 Jan Vrany <jan.vrany(a)fit.cvut.cz>: > Hi, > > > Yes there is a business interest of running on ARM processors. Some of >> the big companies use smalltalk on their own hardware for very specific >> tasks, and they are now constraint to use x86 processor due to smalltalk. >> >> There are other smalltalks that run on non-x86 && non-amd64 machines. > Smalltalk ~~ Pharo :-) Yes, yes sorry. I wrote it the right way in the mail before this one. "Pharo can run on ARM processor on the contrary to several other smalltalks" Some smalltalks cannot run on ARM, but some can. Squeak, Pharo and GNU Smalltalk can run on ARM for example. I don't know about Smalltalk/X. > > > Jan > >

June 20, 2014

Re: [Pharo-dev] Cloudfork HMAC-SHA256 in System-Hashing

by Sven Van Caekenberghe

OK, thanks, I will have a look. On 20 Jun 2014, at 10:56, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > Max, > > Yes, it's usable as the SHA1 package already there (without HMAC so). I'm no expert in those stuff but I don't get "SHA256 base implementation". Someone with more knowledge can probably tell ;) > > Sven, > > The bare minimum to load it is: > > Gofer it > smalltalkhubUser: 'JanVanDeSandt' project: 'Cloudfork'; > package: 'Cloudfork-Common'; > package: 'Cloudfork-Pharo-Platform'; > load. > > The implementation is in Cloudfork-Pharo-Platform. > > > > On Thu, Jun 19, 2014 at 6:20 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I want to have a look, if you tell me where to look... > > On 19 Jun 2014, at 18:03, Max Leske <maxleske(a)gmail.com> wrote: > > > > > On 19.06.2014, at 17:59, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > > >> Does it make sense from a license point of view and practical point of view to include the CloudFork HMAC-SHA256 implementation (CFSH256 class) in the System-Hashing package (in where there's already SHA1 and MD5) ? > > > > Can Cloudfork HMAC-SHA256 be easily parameterized with, say, an SHA256 base implementation? Or does it require extra stuff? In the former case I probably wouldnât add it. In the latter case itâs open for discussion. Personally, I think it belongs into a separate package, not into System-Hashing. > > > > Cheers, > > Max > > >

June 20, 2014