September 2015 - Pharo-dev - lists.pharo.org

System announcements fixed?

by Stephan Eggermont

What is the planning for getting updates again? Nautilus and Monticello don't update anymore in lots of cases. Stephan

Sept. 4, 2015

Re: [Pharo-dev] rb highlighting is not up to the task yet

by Nicolai Hess

This depends on the kind of error. For example, a missing open or closed parenthesis will most likely mark the whole (following) code. But it should still highlight the preceding code. Can you give an example. nicolai 2015-09-04 23:10 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > I think it's nice that we are going towards consolidating our tools around > RB. > > However, the highlighting logic is not quite enough because if I have an > error anywhere in the code, the whole highlighting disappears. In contrast, > Shout manages to limit the problem only to the surrounding code. > > Is anyone working on this part of the highlighting? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Sept. 4, 2015

Re: [Pharo-dev] To Detent Or Not To Detentâ¦

by Nicolai Hess

2015-09-02 17:42 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Can anyone explain the purpose of sending #detentBy:atMultiplesOf:snap: in > the method below? The problem is that, if you resize programatically below > a > factor of 0.1, you enter a black hole from which many scale attempts become > effectively ignored. If the send is removed, everything works for my use > case, but I don't understand its purpose and so don't know if it's a bug or > feature! > TransformationMorph>>#extent: newExtent > self adjustAfter: > [ | scaleFactor |scaleFactor := (self scale * newExtent r > / self > fullBounds extent r) max: 0.1. > self scale: (scaleFactor detentBy: 0.1 atMultiplesOf: 1.0 > snap: false)] > > > Maybe it is not needed for the #extent method. It is used for rotation and scaling with the halos. For example, if you remove that call in #scaleToMatch:, it may be difficult (or impossible, due to rounding errors) to scale a Morph back to scale factor 1.0. But I think it is enough to use this in #scaleToMatch: , no need to have it in #extent: too. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/To-Detent-Or-Not-To-Detent-tp4847682.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Sept. 4, 2015

Re: [Pharo-dev] [Moose-dev] Equivalent class for Pharo

by milton mamani

Hi Vincent I am trying to export code from VisualWork to pharo using the bundle( FileOut30) Cheers, Milton 2015-09-04 17:29 GMT-04:00 Vincent BLONDEAU < vincent.blondeau(a)polytech-lille.net>: > Hi Milton, > > > > You should ask to the Pharo mailing list (in copy). > > > > But what is the purpose of the BinaryStorageBytes class? > > > > Cheers, > > Vincent > > > > *De :* moose-dev-bounces(a)iam.unibe.ch [mailto: > moose-dev-bounces(a)iam.unibe.ch] *De la part de* milton mamani > *EnvoyÃ© :* vendredi 4 septembre 2015 23:23 > *Ã :* Moose-related development; Vwnc (vwnc(a)cs.uiuc.edu) > *Objet :* [Moose-dev] Equivalent class for Pharo > > > > Hi to all > > > > Can someone please tell me the equivalent class for BinaryStorageBytes(a > VW class) for Pharo > > > > Cheers, > > Milton >

Sept. 4, 2015

Re: [Pharo-dev] [Moose-dev] Equivalent class for Pharo

by Vincent BLONDEAU

Hi Milton, You should ask to the Pharo mailing list (in copy). But what is the purpose of the BinaryStorageBytes class? Cheers, Vincent De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de milton mamani EnvoyÃ© : vendredi 4 septembre 2015 23:23 Ã : Moose-related development; Vwnc (vwnc(a)cs.uiuc.edu) Objet : [Moose-dev] Equivalent class for Pharo Hi to all Can someone please tell me the equivalent class for BinaryStorageBytes(a VW class) for Pharo Cheers, Milton

Sept. 4, 2015

rb highlighting is not up to the task yet

by Tudor Girba

Hi, I think it's nice that we are going towards consolidating our tools around RB. However, the highlighting logic is not quite enough because if I have an error anywhere in the code, the whole highlighting disappears. In contrast, Shout manages to limit the problem only to the surrounding code. Is anyone working on this part of the highlighting? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Sept. 4, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Nicolai Hess

2015-09-04 21:27 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Martin, > > On Fri, Sep 4, 2015 at 8:13 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Hi all, >> >> The source code of a method could be a Text, with TextAttributes. In such >> case, it will be written down to a stream with a "]style[" suffix. Through >> a special parsing, the system can reconstruct the original Text. I think >> the use of Text in source code or class comments is discouraged, but I >> understand we kept support for some backward compatibility. Now, may be >> it's time to remove this feature. >> >> With Pablo, we looked for uses of ]style[ in the .sources and .changes >> files of a new Pharo 5.0, and there are no real uses. It appears in some >> comments only, as examples. >> >> We tried to find past discussions about this feature, because we're sure >> there were, but we couldn't. >> >> So, the questions is: >> >> Can we remove support for text in source code or class comments in >> Pharo 5.0? >> > > IIUC, ]style[ also supports things like embedding URL links and method > references in class comments. So I would request that it /not/ be > removed. It is very useful to put clickable links in class comments. > I missed that too, why did we remove that? > > >> >> I think I can propose a slice. >> >> Regards, >> MartÃn >> PS: I was trying to cut dependencies of Text-Core with System-Changes and >> System-Changes. >> > > > > -- > _,,,^..^,,,_ > best, Eliot >

Sept. 4, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Eliot Miranda

Sent from my iPhone > On Sep 4, 2015, at 1:33 PM, stepharo <stepharo(a)free.fr> wrote: > > eliot > > Nobody defines urls in method comment anymore. I do. Several places in the Cog JIT contain irks to specification documents. I don't care how its implemented (providing it's preserved in text, or maybe have the pretty-printer scan comments for http://. But it is sad that we can't have hyperlinks in text. Look I know the implementation stinks, but it can be fixed. But if the functionality is lost the system is weakened. Instead of asking what you can get rid if why not ask what you can reimplement or enhance more elegantly. Christ you're even using minis paced fonts. It's like the dark ages in there ;-) > In addition would prefer to have an explicit syntax as in Pillar or html to represent > an hyperlink. We could have > *Class>>#method* when pillar is not loaded and else a nicer representation. > ctrl-click on a class should jump on it already and we could map it to *Class>>#method* > > In class comments we should use pillar and get a real text renderer. > > >> Hi Martin, >> >>> On Fri, Sep 4, 2015 at 8:13 AM, Martin Dias <tinchodias(a)gmail.com> wrote: >>> Hi all, >>> >>> The source code of a method could be a Text, with TextAttributes. In such case, it will be written down to a stream with a "]style[" suffix. Through a special parsing, the system can reconstruct the original Text. I think the use of Text in source code or class comments is discouraged, but I understand we kept support for some backward compatibility. Now, may be it's time to remove this feature. >>> >>> With Pablo, we looked for uses of ]style[ in the .sources and .changes files of a new Pharo 5.0, and there are no real uses. It appears in some comments only, as examples. >>> >>> We tried to find past discussions about this feature, because we're sure there were, but we couldn't. >>> >>> So, the questions is: >>> >>> Can we remove support for text in source code or class comments in Pharo 5.0? >> >> IIUC, ]style[ also supports things like embedding URL links and method references in class comments. So I would request that it /not/ be removed. It is very useful to put clickable links in class comments. >> >>> >>> >>> I think I can propose a slice. >>> >>> Regards, >>> MartÃn >>> PS: I was trying to cut dependencies of Text-Core with System-Changes and System-Changes. >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >

Sept. 4, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by stepharo

eliot Nobody defines urls in method comment anymore. In addition would prefer to have an explicit syntax as in Pillar or html to represent an hyperlink. We could have *Class>>#method* when pillar is not loaded and else a nicer representation. ctrl-click on a class should jump on it already and we could map it to *Class>>#method* In class comments we should use pillar and get a real text renderer. > Hi Martin, > > On Fri, Sep 4, 2015 at 8:13 AM, Martin Dias <tinchodias(a)gmail.com > <mailto:tinchodias@gmail.com>> wrote: > > Hi all, > > The source code of a method could be a Text, with TextAttributes. > In such case, it will be written down to a stream with a "]style[" > suffix. Through a special parsing, the system can reconstruct the > original Text. I think the use of Text in source code or class > comments is discouraged, but I understand we kept support for some > backward compatibility. Now, may be it's time to remove this feature. > > With Pablo, we looked for uses of ]style[ in the .sources and > .changes files of a new Pharo 5.0, and there are no real uses. It > appears in some comments only, as examples. > > We tried to find past discussions about this feature, because > we're sure there were, but we couldn't. > > So, the questions is: > > Can we remove support for text in source code or class comments > in Pharo 5.0? > > > IIUC, ]style[ also supports things like embedding URL links and method > references in class comments. So I would request that it /not/ be > removed. It is very useful to put clickable links in class comments. > > > > I think I can propose a slice. > > Regards, > MartÃn > PS: I was trying to cut dependencies of Text-Core with > System-Changes and System-Changes. > > > > > -- > _,,,^..^,,,_ > best, Eliot

Sept. 4, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 4, 2015