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 <tinchod...@gmail.com
<mailto:tinchod...@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
