Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
Hi Christoph --
...the alternative would be an extra #asString? Hmm... for source code, it kind of bothers me to watch out for whether it is styled or not. And #lines is surely interesting for lines-of-code and maybe other metrics...
Hmm... I would say no. #findString: has several similar messages in String that would bloat up Text. Same for #lines (and #linesDo:, #lineIndicesDo:)...
I have some usecases for that [...]
An extra #asString would not hurt there, would it?
Could be a nice application for traits ...
Nope. :-)
Best, Marcel Am 19.05.2023 14:17:33 schrieb christoph.thiede@student.hpi.uni-potsdam.de christoph.thiede@student.hpi.uni-potsdam.de: Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
Hi Marcel,
An extra #asString would not hurt there, would it?
For #findString:, yes. For #lines, no. myText asString lines would contain strings, but myText lines would answer true Text instances instead.
Best, Christoph
On 2023-05-19T14:31:09+02:00, marcel.taeumel@hpi.de wrote:
Hi Christoph --
...the alternative would be an extra #asString? Hmm... for source code, it kind of bothers me to watch out for whether it is styled or not. And #lines is surely interesting for lines-of-code and maybe other metrics...
Hmm... I would say no. #findString: has several similar messages in String that would bloat up Text. Same for #lines (and #linesDo:, #lineIndicesDo:)...
I have some usecases for that [...]
An extra #asString would not hurt there, would it?
Could be a nice application for traits ...
Nope. :-)
Best, Marcel Am 19.05.2023 14:17:33 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de <christoph.thiede(a)student.hpi.uni-potsdam.de>: Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
Hi Christoph --
...and we already have some *lines* protocol in Text. So, yes, a formatting-aware #lines and #linesDo: would be a nice thing to have in Text.
And the complementary #findString: would be nice since Text already has #findStringStartingAt:(caseSensitive:).
Best, Marcel Am 19.05.2023 16:51:29 schrieb christoph.thiede@student.hpi.uni-potsdam.de christoph.thiede@student.hpi.uni-potsdam.de: Hi Marcel,
An extra #asString would not hurt there, would it?
For #findString:, yes. For #lines, no. myText asString lines would contain strings, but myText lines would answer true Text instances instead.
Best, Christoph
On 2023-05-19T14:31:09+02:00, marcel.taeumel@hpi.de wrote:
Hi Christoph --
...the alternative would be an extra #asString? Hmm... for source code, it kind of bothers me to watch out for whether it is styled or not. And #lines is surely interesting for lines-of-code and maybe other metrics...
Hmm... I would say no. #findString: has several similar messages in String that would bloat up Text. Same for #lines (and #linesDo:, #lineIndicesDo:)...
I have some usecases for that [...]
An extra #asString would not hurt there, would it?
Could be a nice application for traits ...
Nope. :-)
Best, Marcel Am 19.05.2023 14:17:33 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de : Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
Done via Collections-ct.1033 & CollectionsTests-ct.387. :-)
Best, Christoph
On 2023-05-19T17:03:34+02:00, marcel.taeumel@hpi.de wrote:
Hi Christoph --
...and we already have some *lines* protocol in Text. So, yes, a formatting-aware #lines and #linesDo: would be a nice thing to have in Text.
And the complementary #findString: would be nice since Text already has #findStringStartingAt:(caseSensitive:).
Best, Marcel Am 19.05.2023 16:51:29 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de <christoph.thiede(a)student.hpi.uni-potsdam.de>: Hi Marcel,
An extra #asString would not hurt there, would it?
For #findString:, yes. For #lines, no. myText asString lines would contain strings, but myText lines would answer true Text instances instead.
Best, Christoph
On 2023-05-19T14:31:09+02:00, marcel.taeumel(a)hpi.de wrote:
Hi Christoph --
...the alternative would be an extra #asString? Hmm... for source code, it kind of bothers me to watch out for whether it is styled or not. And #lines is surely interesting for lines-of-code and maybe other metrics...
Hmm... I would say no. #findString: has several similar messages in String that would bloat up Text. Same for #lines (and #linesDo:, #lineIndicesDo:)...
I have some usecases for that [...]
An extra #asString would not hurt there, would it?
Could be a nice application for traits ...
Nope. :-)
Best, Marcel Am 19.05.2023 14:17:33 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de : Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
Hi Marcel,
hm ... what about #truncate[WithEllipsis]To: on Text? I could need that, too. (And maybe I can make RxMatcher>>#copyStream:to:replacingMatchesWith: et al. capable of Texts too in the future ...) :-)
Best, Christoph
--- Sent from Squeak Inbox Talk
On 2023-05-20T13:07:16+02:00, christoph.thiede@student.hpi.uni-potsdam.de wrote:
Done via Collections-ct.1033 & CollectionsTests-ct.387. :-)
Best, Christoph
On 2023-05-19T17:03:34+02:00, marcel.taeumel(a)hpi.de wrote:
Hi Christoph --
...and we already have some *lines* protocol in Text. So, yes, a formatting-aware #lines and #linesDo: would be a nice thing to have in Text.
And the complementary #findString: would be nice since Text already has #findStringStartingAt:(caseSensitive:).
Best, Marcel Am 19.05.2023 16:51:29 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de <christoph.thiede(a)student.hpi.uni-potsdam.de>: Hi Marcel,
An extra #asString would not hurt there, would it?
For #findString:, yes. For #lines, no. myText asString lines would contain strings, but myText lines would answer true Text instances instead.
Best, Christoph
On 2023-05-19T14:31:09+02:00, marcel.taeumel(a)hpi.de wrote:
Hi Christoph --
...the alternative would be an extra #asString? Hmm... for source code, it kind of bothers me to watch out for whether it is styled or not. And #lines is surely interesting for lines-of-code and maybe other metrics...
Hmm... I would say no. #findString: has several similar messages in String that would bloat up Text. Same for #lines (and #linesDo:, #lineIndicesDo:)...
I have some usecases for that [...]
An extra #asString would not hurt there, would it?
Could be a nice application for traits ...
Nope. :-)
Best, Marcel Am 19.05.2023 14:17:33 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de : Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
Hi Christoph --
As long as there is an actual benefit of keeping the attributes after applying the operation, sure.
Best, Marcel Am 04.06.2023 15:25:23 schrieb christoph.thiede@student.hpi.uni-potsdam.de christoph.thiede@student.hpi.uni-potsdam.de: Hi Marcel,
hm ... what about #truncate[WithEllipsis]To: on Text? I could need that, too. (And maybe I can make RxMatcher>>#copyStream:to:replacingMatchesWith: et al. capable of Texts too in the future ...) :-)
Best, Christoph
--- Sent from Squeak Inbox Talk
On 2023-05-20T13:07:16+02:00, christoph.thiede@student.hpi.uni-potsdam.de wrote:
Done via Collections-ct.1033 & CollectionsTests-ct.387. :-)
Best, Christoph
On 2023-05-19T17:03:34+02:00, marcel.taeumel(a)hpi.de wrote:
Hi Christoph --
...and we already have some *lines* protocol in Text. So, yes, a formatting-aware #lines and #linesDo: would be a nice thing to have in Text.
And the complementary #findString: would be nice since Text already has #findStringStartingAt:(caseSensitive:).
Best, Marcel Am 19.05.2023 16:51:29 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de : Hi Marcel,
An extra #asString would not hurt there, would it?
For #findString:, yes. For #lines, no. myText asString lines would contain strings, but myText lines would answer true Text instances instead.
Best, Christoph
On 2023-05-19T14:31:09+02:00, marcel.taeumel(a)hpi.de wrote:
Hi Christoph --
...the alternative would be an extra #asString? Hmm... for source code, it kind of bothers me to watch out for whether it is styled or not. And #lines is surely interesting for lines-of-code and maybe other metrics...
Hmm... I would say no. #findString: has several similar messages in String that would bloat up Text. Same for #lines (and #linesDo:, #lineIndicesDo:)...
I have some usecases for that [...]
An extra #asString would not hurt there, would it?
Could be a nice application for traits ...
Nope. :-)
Best, Marcel Am 19.05.2023 14:17:33 schrieb christoph.thiede(a)student.hpi.uni-potsdam.de : Hi all,
quick question: Would you like/mind to see #lines and #findString: and their variants on Text? I have some usecases for that, but I don't know whether this would clutter the interface too much. (Could be a nice application for traits ... :-))
Best, Christoph
squeak-dev@lists.squeakfoundation.org