[Cuis-dev] Fix for VectorCanvas>>#image:at:
Juan Vuletich
juan at cuis.st
Wed Jun 21 05:55:12 PDT 2023
Hi Luciano,
I just removed the double quotes, but kept the additional dot at the
end, as it helps proper shouting in the next line (in case there's not
an empty line).
Cheers,
Juan Vuletich
On 6/17/2023 2:07 PM, Luciano Notarfrancesco via Cuis-dev wrote:
> Great, thank you.
> I removed the double quotes from printIt (see attached method) and
> have been using it like that for two days, seems to work fine, shout
> doesn't get confused. IMO without the double quotes the output looks
> cleaner, but it's up to you how you want it in the core image.
> Cheers,
> Luciano
>
> On Sat, Jun 17, 2023 at 2:47 AM Juan Vuletich <juan at cuis.st
> <mailto:juan at cuis.st>> wrote:
>
> Hi Luciano,
>
> On 6/16/2023 2:37 PM, Luciano Notarfrancesco via Cuis-dev wrote:
>> Hi Juan,
>> Your last changes seem to work great so far.
>> However I found another little issue that maybe we can fix: copy
>> and pasting looses text attributes, so subscripts and
>> superscripts get lost.
>
> Right. I was thinking on code browsers (code is plain text by
> definition), but pasting Text makes sense in Workspaces.
>
>> I think we can fix this by just removing the two methods in the
>> ‘clipboard’ category in SmalltalkEditor. I’m not sure if there’s
>> still a need to replace underscores with arrows like you do in
>> those methods. I just removed those two methods and the
>> underscore is still converted to arrow on paste, and subscripts
>> and superscripts now are pasted correctly.
>
> Those methods are there just in case you paste code with Unicode
> Arrows (not underscores!). We do that to have good looking and
> functional code in The Cuis Book. So I kept them, but keeping Text
> Attributes.
>
> Fix is now at github.
>
> Thanks!
>
>>
>> On Thu, 15 Jun 2023 at 22:43 Luciano Notarfrancesco
>> <luchiano at gmail.com <mailto:luchiano at gmail.com>> wrote:
>>
>> That’s fantastic, thank you! I just updated a fresh image and
>> seems to work well. I’ll continue using it and let you know
>> if I find any problems.
>> Thanks for taking the time to do this!
>> Luciano
>>
>> On Thu, 15 Jun 2023 at 22:09 Juan Vuletich <juan at cuis.st
>> <mailto:juan at cuis.st>> wrote:
>>
>> Hi Luciano,
>>
>> On 6/15/2023 3:23 PM, Luciano Notarfrancesco via Cuis-dev
>> wrote:
>>> Hi Juan,
>>>
>>> On Thu, 15 Jun 2023 at 19:43 Juan Vuletich <juan at cuis.st
>>> <mailto:juan at cuis.st>> wrote:
>>>
>>>
>>> I guess the name is not clear. It just avoids Shout
>>> Attirbutes, but not Shout analizing the text as if
>>> it was source code and getting confused. That's why
>>> we need the double quotes and final $.
>>>
>>>
>>> Oh, I see. It seems to me that it would be more useful
>>> to tag printIt text as “not code” instead, and make
>>> Shout ignore it completely. It could also function as
>>> “separator” between fragments of code to be syntax
>>> highlighted, just like leaving two empty lines. And it
>>> would make the double quotes and final dot unnecessary.
>>
>> I agree. Currently the parsers take String, not Text, so
>> I'm not sure if doing as you suggest is complicated or not.
>>
>> As a start, I just commited a few updates that make
>> Workspace Shout parsing start fresh after any empty line
>> (i.e. a sequence of two LFs). Maybe this is enough. Maybe
>> the double quotes are no longer needed. We'll see.
>>
>>>
>>> > I’m still having troubles with := and _ not being
>>> shown as arrows, leaving empty
>>>
>>> > lines between fragments of code doesn’t seem to help.
>>>
>>> Does adding $. after the "offending code" help?
>>> Double quoting it?
>>>
>>>
>>> Adding $. doesn’t help, but commenting out big portions
>>> of text does (it’s hard to find the exact offending text
>>> and fix it). Ideally, it would be nice if syntax
>>> highlighting worked properly in workspaces without
>>> requiring the user to make sure that all the text in
>>> workspace compiles correctly. I’d turn off syntax
>>> highlighting in workspaces if that helped, but if I do
>>> that underscores are not converted to arrows anymore…
>>
>> If I got right the stuff I just pushed, just an empty
>> line should be enough to get left arrows for assignment
>> and Shout attributes right. Please test.
>>
>> BTW, You all folks telling these kinds of things out loud
>> is extremely important. I have a tendency to get used to,
>> and ignore these small annoyances. You all pointing at
>> them makes me try to fix them!
>>
>> Thanks,--
>>
>> Juan Vuletich
>> cuis.st <http://cuis.st>
>> github.com/jvuletich <http://github.com/jvuletich>
>> researchgate.net/profile/Juan-Vuletich <http://researchgate.net/profile/Juan-Vuletich>
>> independent.academia.edu/JuanVuletich <http://independent.academia.edu/JuanVuletich>
>> patents.justia.com/inventor/juan-manuel-vuletich <http://patents.justia.com/inventor/juan-manuel-vuletich>
>> linkedin.com/in/juan-vuletich-75611b3 <http://linkedin.com/in/juan-vuletich-75611b3>
>> twitter.com/JuanVuletich <http://twitter.com/JuanVuletich>
>>
>
>
> --
> Juan Vuletich
> cuis.st <http://cuis.st>
> github.com/jvuletich <http://github.com/jvuletich>
> researchgate.net/profile/Juan-Vuletich <http://researchgate.net/profile/Juan-Vuletich>
> independent.academia.edu/JuanVuletich <http://independent.academia.edu/JuanVuletich>
> patents.justia.com/inventor/juan-manuel-vuletich <http://patents.justia.com/inventor/juan-manuel-vuletich>
> linkedin.com/in/juan-vuletich-75611b3 <http://linkedin.com/in/juan-vuletich-75611b3>
> twitter.com/JuanVuletich <http://twitter.com/JuanVuletich>
>
--
Juan Vuletich
cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
linkedin.com/in/juan-vuletich-75611b3
twitter.com/JuanVuletich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20230621/39ae5024/attachment-0001.htm>
More information about the Cuis-dev
mailing list