loading Shout into trunk?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

loading Shout into trunk?

Ken G. Brown
I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.

I successfully did the following from the Help/Extending the System:
"Omnibrowser, including Refactoring engine"
(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).

Anyone know what is required to load Shout?
I can doit
 (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.

to get ConfigurationOfShout into the image, but I'm unsure of what to do next.

Thx fr any tips,
Ken G. Brown
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Sean P. DeNigris
Administrator
Try installing OCompletion (see http://forum.world.st/OCompletion-for-Squeak-4-2-td3016472.html) or the OB changeset (which you may need anyway to use refactoring, see http://forum.world.st/refactoring-browser-in-Squeak-td3010490i20.html).

Sean
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
Into Squeak4.2-10732-alpha.image I've just done
"Omnibrowser, including Refactoring engine"
(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).

which I found from Help/Extend the System.

I see Ocompletion, and RoelTyper stuff etc. I'm thinking I already have what is necessary.
It does indeed look like the Workspaces are using coloring.

So does Ocompletion replace the previous Shout stuff?
Or what is the relationship?
Is Shout needed anymore?

Has anyone done a Configuration to load a bunch of dev tools like the Damien Squeak-dev images used to have?

Thx,
Ken
 

At 3:00 PM -0800 12/3/10, Sean P. DeNigris apparently wrote:

>Try installing OCompletion (see
>http://forum.world.st/OCompletion-for-Squeak-4-2-td3016472.html) or the OB
>changeset (which you may need anyway to use refactoring, see
>http://forum.world.st/refactoring-browser-in-Squeak-td3010490i20.html).
>
>Sean
>--
>View this message in context: http://forum.world.st/loading-Shout-into-trunk-tp3071889p3071897.html
>Sent from the Squeak - Beginners mailing list archive at Nabble.com.
>_______________________________________________
>Beginners mailing list
>[hidden email]
>http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Levente Uzonyi-2
In reply to this post by Ken G. Brown
On Fri, 3 Dec 2010, Ken G. Brown wrote:

> I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.

Since Squeak 4.1 Shout is part of the base image as ShoutCore, so every
workspace has syntax highlighting.


Levente

>
> I successfully did the following from the Help/Extending the System:
> "Omnibrowser, including Refactoring engine"
> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
> ((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).
>
> Anyone know what is required to load Shout?
> I can doit
> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.
>
> to get ConfigurationOfShout into the image, but I'm unsure of what to do next.
>
> Thx fr any tips,
> Ken G. Brown
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
Ah, great then.
Guess i had not looked closely enough, was used to seeing the SHWorkspace.

Thx,
Ken

At 12:50 AM +0100 12/4/10, Levente Uzonyi apparently wrote:

>On Fri, 3 Dec 2010, Ken G. Brown wrote:
>
>>I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.
>
>Since Squeak 4.1 Shout is part of the base image as ShoutCore, so every workspace has syntax highlighting.
>
>
>Levente
>
>>
>>I successfully did the following from the Help/Extending the System:
>>"Omnibrowser, including Refactoring engine"
>>(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
>>((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).
>>
>>Anyone know what is required to load Shout?
>>I can doit
>>(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.
>>
>>to get ConfigurationOfShout into the image, but I'm unsure of what to do next.
>>
>>Thx fr any tips,
>>Ken G. Brown
>>_______________________________________________
>>Beginners mailing list
>>[hidden email]
>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>
>_______________________________________________
>Beginners mailing list
>[hidden email]
>http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
Another reason I did not realize that Workspaces had syntax highlighting, is that adding comment quotes around some text in a Workspace does not change the color to indicate it is all a comment. Also I see that syntax highlighting can be turned off in the Workspace windowbar menu, although the default appears to be set to on, but there is a preference called Subdued syntax highlighting that is on as well.
Is the lack of quoted comment coloring in a Workspace a known problem?
Is there a way to make quoted comments colored in the Workspace?

Ken


At 5:14 PM -0700 12/3/10, Ken G. Brown apparently wrote:

>Ah, great then.
>Guess i had not looked closely enough, was used to seeing the SHWorkspace.
>
>Thx,
>Ken
>
>At 12:50 AM +0100 12/4/10, Levente Uzonyi apparently wrote:
>>On Fri, 3 Dec 2010, Ken G. Brown wrote:
>>
>>>I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.
>>
>>Since Squeak 4.1 Shout is part of the base image as ShoutCore, so every workspace has syntax highlighting.
>>
>>
>>Levente
>>
>>>
>>>I successfully did the following from the Help/Extending the System:
>>>"Omnibrowser, including Refactoring engine"
>>>(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
>>>((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).
>>>
>>>Anyone know what is required to load Shout?
>>>I can doit
>>>(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.
>>>
>>>to get ConfigurationOfShout into the image, but I'm unsure of what to do next.
>>>
>>>Thx fr any tips,
>>>Ken G. Brown
>>>_______________________________________________
>>>Beginners mailing list
>>>[hidden email]
>>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>
>>_______________________________________________
>>Beginners mailing list
>>[hidden email]
>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
>_______________________________________________
>Beginners mailing list
>[hidden email]
>http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Levente Uzonyi-2
On Sat, 4 Dec 2010, Ken G. Brown wrote:

> Another reason I did not realize that Workspaces had syntax highlighting, is that adding comment quotes around some text in a Workspace does not change the color to indicate it is all a comment. Also I see that syntax highlighting can be turned off in the Workspace windowbar menu, although the default appears to be set to on, but there is a preference called Subdued syntax highlighting that is on as well.

Comments do have their own color, but the default color scheme is
different from the old one. If you want the old color scheme, then turn
off the Subdued Syntax Highlighting preference.
Also note that, there's a global preference for syntax highlighting in
workspaces, look for "Shout styling in Workspace".


Levente

> Is the lack of quoted comment coloring in a Workspace a known problem?
> Is there a way to make quoted comments colored in the Workspace?
>
> Ken
>
>
> At 5:14 PM -0700 12/3/10, Ken G. Brown apparently wrote:
>> Ah, great then.
>> Guess i had not looked closely enough, was used to seeing the SHWorkspace.
>>
>> Thx,
>> Ken
>>
>> At 12:50 AM +0100 12/4/10, Levente Uzonyi apparently wrote:
>>> On Fri, 3 Dec 2010, Ken G. Brown wrote:
>>>
>>>> I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.
>>>
>>> Since Squeak 4.1 Shout is part of the base image as ShoutCore, so every workspace has syntax highlighting.
>>>
>>>
>>> Levente
>>>
>>>>
>>>> I successfully did the following from the Help/Extending the System:
>>>> "Omnibrowser, including Refactoring engine"
>>>> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
>>>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).
>>>>
>>>> Anyone know what is required to load Shout?
>>>> I can doit
>>>> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.
>>>>
>>>> to get ConfigurationOfShout into the image, but I'm unsure of what to do next.
>>>>
>>>> Thx fr any tips,
>>>> Ken G. Brown
>>>> _______________________________________________
>>>> Beginners mailing list
>>>> [hidden email]
>>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>>
>>> _______________________________________________
>>> Beginners mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>
>> _______________________________________________
>> Beginners mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
Well, comment highlighting doesn't seem to work for me, at least not reliably all the time.

Could someone please check out the image Squeak4.2-10740-alpha at:
<https://public.me.com/kbrown> in the Squeak4.2Test folder, and let me know if they are seeing the "commented out" in the two Workspaces, properly colored a shade of green like the two lines in the Workspace that has more text? At least I see those two lines properly colored as comment.

The image is a fresh Squeak4.2-10548-alpha which only has had 'Update Squeak' done to update 10740.

Thx,
Ken G. Brown




At 2:00 AM +0100 12/5/10, Levente Uzonyi apparently wrote:

>On Sat, 4 Dec 2010, Ken G. Brown wrote:
>
>>Another reason I did not realize that Workspaces had syntax highlighting, is that adding comment quotes around some text in a Workspace does not change the color to indicate it is all a comment. Also I see that syntax highlighting can be turned off in the Workspace windowbar menu, although the default appears to be set to on, but there is a preference called Subdued syntax highlighting that is on as well.
>
>Comments do have their own color, but the default color scheme is different from the old one. If you want the old color scheme, then turn off the Subdued Syntax Highlighting preference.
>Also note that, there's a global preference for syntax highlighting in workspaces, look for "Shout styling in Workspace".
>
>
>Levente
>
>>Is the lack of quoted comment coloring in a Workspace a known problem?
>>Is there a way to make quoted comments colored in the Workspace?
>>
>>Ken
>>
>>
>>At 5:14 PM -0700 12/3/10, Ken G. Brown apparently wrote:
>>>Ah, great then.
>>>Guess i had not looked closely enough, was used to seeing the SHWorkspace.
>>>
>>>Thx,
>>>Ken
>>>
>>>At 12:50 AM +0100 12/4/10, Levente Uzonyi apparently wrote:
>>>>On Fri, 3 Dec 2010, Ken G. Brown wrote:
>>>>
>>>>>I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.
>>>>
>>>>Since Squeak 4.1 Shout is part of the base image as ShoutCore, so every workspace has syntax highlighting.
>>>>
>>>>
>>>>Levente
>>>>
>>>>>
>>>>>I successfully did the following from the Help/Extending the System:
>>>>>"Omnibrowser, including Refactoring engine"
>>>>>(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
>>>>>((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).
>>>>>
>>>>>Anyone know what is required to load Shout?
>>>>>I can doit
>>>>>(Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.
>>>>>
>>>>>to get ConfigurationOfShout into the image, but I'm unsure of what to do next.
>>>>>
>>>>>Thx fr any tips,
>>>>>Ken G. Brown
>>>>>_______________________________________________
>>>>>Beginners mailing list
>>>>>[hidden email]
>>>>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>>>
>>>>_______________________________________________
>>>>Beginners mailing list
>>>>[hidden email]
>>>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>
>>>_______________________________________________
>>>Beginners mailing list
>>>[hidden email]
>>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>
>>_______________________________________________
>>Beginners mailing list
>>[hidden email]
>>http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>
>_______________________________________________
>Beginners mailing list
>[hidden email]
>http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Levente Uzonyi-2
On Sun, 5 Dec 2010, Ken G. Brown wrote:

> Well, comment highlighting doesn't seem to work for me, at least not reliably all the time.
>
> Could someone please check out the image Squeak4.2-10740-alpha at:
> <https://public.me.com/kbrown> in the Squeak4.2Test folder, and let me know if they are seeing the "commented out" in the two Workspaces, properly colored a shade of green like the two lines in the Workspace that has more text? At least I see those two lines properly colored as comment.

The reason why your text is not highlighted is that the first character in
your workspace has ascii value 16. That character is not visible, but it's
there and results in a syntax error during parsing. If you delete it, the
highlighing will be normal again (up to the next syntax error).


Levente

>
> The image is a fresh Squeak4.2-10548-alpha which only has had 'Update Squeak' done to update 10740.
>
> Thx,
> Ken G. Brown
>
>
>
>
> At 2:00 AM +0100 12/5/10, Levente Uzonyi apparently wrote:
>> On Sat, 4 Dec 2010, Ken G. Brown wrote:
>>
>>> Another reason I did not realize that Workspaces had syntax highlighting, is that adding comment quotes around some text in a Workspace does not change the color to indicate it is all a comment. Also I see that syntax highlighting can be turned off in the Workspace windowbar menu, although the default appears to be set to on, but there is a preference called Subdued syntax highlighting that is on as well.
>>
>> Comments do have their own color, but the default color scheme is different from the old one. If you want the old color scheme, then turn off the Subdued Syntax Highlighting preference.
>> Also note that, there's a global preference for syntax highlighting in workspaces, look for "Shout styling in Workspace".
>>
>>
>> Levente
>>
>>> Is the lack of quoted comment coloring in a Workspace a known problem?
>>> Is there a way to make quoted comments colored in the Workspace?
>>>
>>> Ken
>>>
>>>
>>> At 5:14 PM -0700 12/3/10, Ken G. Brown apparently wrote:
>>>> Ah, great then.
>>>> Guess i had not looked closely enough, was used to seeing the SHWorkspace.
>>>>
>>>> Thx,
>>>> Ken
>>>>
>>>> At 12:50 AM +0100 12/4/10, Levente Uzonyi apparently wrote:
>>>>> On Fri, 3 Dec 2010, Ken G. Brown wrote:
>>>>>
>>>>>> I'd like to see syntax coloring in my Workspaces in Squeak4.2-10732-alpha.image like used to be available with SHWorkspace.
>>>>>
>>>>> Since Squeak 4.1 Shout is part of the base image as ShoutCore, so every workspace has syntax highlighting.
>>>>>
>>>>>
>>>>> Levente
>>>>>
>>>>>>
>>>>>> I successfully did the following from the Help/Extending the System:
>>>>>> "Omnibrowser, including Refactoring engine"
>>>>>> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfOmniBrowser'.
>>>>>> ((Smalltalk at: #ConfigurationOfOmniBrowser) project perform: #lastVersion) load: #( Dev ).
>>>>>>
>>>>>> Anyone know what is required to load Shout?
>>>>>> I can doit
>>>>>> (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfShout'.
>>>>>>
>>>>>> to get ConfigurationOfShout into the image, but I'm unsure of what to do next.
>>>>>>
>>>>>> Thx fr any tips,
>>>>>> Ken G. Brown
>>>>>> _______________________________________________
>>>>>> Beginners mailing list
>>>>>> [hidden email]
>>>>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>>>>
>>>>> _______________________________________________
>>>>> Beginners mailing list
>>>>> [hidden email]
>>>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>>
>>>> _______________________________________________
>>>> Beginners mailing list
>>>> [hidden email]
>>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>
>>> _______________________________________________
>>> Beginners mailing list
>>> [hidden email]
>>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>>>
>> _______________________________________________
>> Beginners mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
At 2:45 AM +0100 12/6/10, Levente Uzonyi apparently wrote:
>On Sun, 5 Dec 2010, Ken G. Brown wrote:
>
>>Well, comment highlighting doesn't seem to work for me, at least not reliably all the time.
>>
>>Could someone please check out the image Squeak4.2-10740-alpha at:
>><https://public.me.com/kbrown> in the Squeak4.2Test folder, and let me know if they are seeing the "commented out" in the two Workspaces, properly colored a shade of green like the two lines in the Workspace that has more text? At least I see those two lines properly colored as comment.
>
>The reason why your text is not highlighted is that the first character in your workspace has ascii value 16. That character is not visible, but it's there and results in a syntax error during parsing. If you delete it, the highlighing will be normal again (up to the next syntax error).
>

Well that's very odd, wonder where that came from?
And the other odd thing that putting the insertion bar before the first character and pressing delete, does not delete the character. Only by putting the insertion bar after the first visible character and then pressing delete will do the deletion of the invisible character but leaves the character immediately to the left of the insertion bar that you would think would normally be deleted. Not intuitive at all.

I wonder if there is any way to enable display of invisible characters with a small box or similar so a person would have a chance of finding issues like this?
Or some way of otherwise detecting and flagging such errors.

Thx,
Ken

>Levente
>
>>
>>The image is a fresh Squeak4.2-10548-alpha which only has had 'Update Squeak' done to update 10740.
>>
>>Thx,
>>Ken G. Brown
>>
<snip>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
Further:
Where is the invisible character in the Workspace that has the more text, and how do you find it?
How do you get the "commented out" at the bottom to color properly?

Ken

At 10:10 PM -0700 12/5/10, Ken G. Brown apparently wrote:

>At 2:45 AM +0100 12/6/10, Levente Uzonyi apparently wrote:
>>On Sun, 5 Dec 2010, Ken G. Brown wrote:
>>
>>>Well, comment highlighting doesn't seem to work for me, at least not reliably all the time.
>>>
>>>Could someone please check out the image Squeak4.2-10740-alpha at:
>>><https://public.me.com/kbrown> in the Squeak4.2Test folder, and let me know if they are seeing the "commented out" in the two Workspaces, properly colored a shade of green like the two lines in the Workspace that has more text? At least I see those two lines properly colored as comment.
>>
>>The reason why your text is not highlighted is that the first character in your workspace has ascii value 16. That character is not visible, but it's there and results in a syntax error during parsing. If you delete it, the highlighing will be normal again (up to the next syntax error).
>>
>
>Well that's very odd, wonder where that came from?
>And the other odd thing that putting the insertion bar before the first character and pressing delete, does not delete the character. Only by putting the insertion bar after the first visible character and then pressing delete will do the deletion of the invisible character but leaves the character immediately to the left of the insertion bar that you would think would normally be deleted. Not intuitive at all.
>
>I wonder if there is any way to enable display of invisible characters with a small box or similar so a person would have a chance of finding issues like this?
>Or some way of otherwise detecting and flagging such errors.
>
>Thx,
>Ken
>
>>Levente
>>
>>>
>>>The image is a fresh Squeak4.2-10548-alpha which only has had 'Update Squeak' done to update 10740.
>>>
>>>Thx,
>>>Ken G. Brown
>>>
><snip>
>_______________________________________________
>Beginners mailing list
>[hidden email]
>http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Levente Uzonyi-2
On Sun, 5 Dec 2010, Ken G. Brown wrote:

> Further:
> Where is the invisible character in the Workspace that has the more text, and how do you find it?

You can find it out by exploring the morphs from the halos. When you find
the text, look for invisible characters in the string (typically
asciiValue < 33).

> How do you get the "commented out" at the bottom to color properly?

You don't, because there are several syntax errors before that comment.


Levente

>
> Ken
>
> At 10:10 PM -0700 12/5/10, Ken G. Brown apparently wrote:
>> At 2:45 AM +0100 12/6/10, Levente Uzonyi apparently wrote:
>>> On Sun, 5 Dec 2010, Ken G. Brown wrote:
>>>
>>>> Well, comment highlighting doesn't seem to work for me, at least not reliably all the time.
>>>>
>>>> Could someone please check out the image Squeak4.2-10740-alpha at:
>>>> <https://public.me.com/kbrown> in the Squeak4.2Test folder, and let me know if they are seeing the "commented out" in the two Workspaces, properly colored a shade of green like the two lines in the Workspace that has more text? At least I see those two lines properly colored as comment.
>>>
>>> The reason why your text is not highlighted is that the first character in your workspace has ascii value 16. That character is not visible, but it's there and results in a syntax error during parsing. If you delete it, the highlighing will be normal again (up to the next syntax error).
>>>
>>
>> Well that's very odd, wonder where that came from?
>> And the other odd thing that putting the insertion bar before the first character and pressing delete, does not delete the character. Only by putting the insertion bar after the first visible character and then pressing delete will do the deletion of the invisible character but leaves the character immediately to the left of the insertion bar that you would think would normally be deleted. Not intuitive at all.
>>
>> I wonder if there is any way to enable display of invisible characters with a small box or similar so a person would have a chance of finding issues like this?
>> Or some way of otherwise detecting and flagging such errors.
>>
>> Thx,
>> Ken
>>
>>> Levente
>>>
>>>>
>>>> The image is a fresh Squeak4.2-10548-alpha which only has had 'Update Squeak' done to update 10740.
>>>>
>>>> Thx,
>>>> Ken G. Brown
>>>>
>> <snip>
>> _______________________________________________
>> Beginners mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
Thx.
I'm wondering if there might be some way for the syntax highlighting to be made to reset itself instead of giving up completely after a syntax error and everything after that doesn't work at all?
eg. the quote character? The double quote character should either be the beginning or end of a comment.

I suppose it's more complicated than that.

Ken


At 10:36 PM +0100 12/8/10, Levente Uzonyi apparently wrote:

>On Sun, 5 Dec 2010, Ken G. Brown wrote:
>
>>Further:
>>Where is the invisible character in the Workspace that has the more text, and how do you find it?
>
>You can find it out by exploring the morphs from the halos. When you find the text, look for invisible characters in the string (typically asciiValue < 33).
>
>>How do you get the "commented out" at the bottom to color properly?
>
>You don't, because there are several syntax errors before that comment.
>
>
>Levente
>
>>
>>Ken
<snip>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Levente Uzonyi-2
On Wed, 8 Dec 2010, Ken G. Brown wrote:

> Thx.
> I'm wondering if there might be some way for the syntax highlighting to be made to reset itself instead of giving up completely after a syntax error and everything after that doesn't work at all?
> eg. the quote character? The double quote character should either be the beginning or end of a comment.
>
> I suppose it's more complicated than that.

It's more complicated. But why don't you put your text into a comment?
Actually that's what comments are for in the language.


Levente

>
> Ken
>
>
> At 10:36 PM +0100 12/8/10, Levente Uzonyi apparently wrote:
>> On Sun, 5 Dec 2010, Ken G. Brown wrote:
>>
>>> Further:
>>> Where is the invisible character in the Workspace that has the more text, and how do you find it?
>>
>> You can find it out by exploring the morphs from the halos. When you find the text, look for invisible characters in the string (typically asciiValue < 33).
>>
>>> How do you get the "commented out" at the bottom to color properly?
>>
>> You don't, because there are several syntax errors before that comment.
>>
>>
>> Levente
>>
>>>
>>> Ken
> <snip>
> _______________________________________________
> Beginners mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/beginners
>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
At 12:07 AM +0100 12/9/10, Levente Uzonyi apparently wrote:
>On Wed, 8 Dec 2010, Ken G. Brown wrote:
>
>>Thx.
>>I'm wondering if there might be some way for the syntax highlighting to be made to reset itself instead of giving up completely after a syntax error and everything after that doesn't work at all?
>>eg. the quote character? The double quote character should either be the beginning or end of a comment.
>>
>>I suppose it's more complicated than that.
>
>It's more complicated. But why don't you put your text into a comment? Actually that's what comments are for in the language.

Correct, however...
I'm thinking of the case where I have a bunch of snippets in a Workspace, some of which would not work as pasted and therefore cause a syntax error but I still want to leave them as code and maybe later fix the syntax, or use the coloring to see where the syntax error might be occurring in the snippet.
The first syntax error seems to mess syntax highlighting up forever more after the first error i the Workspace. I would like stuff that is actually commented out farther on to to keep showing as comments, even tho there is a syntax error in some code above on the page.

Or the case where there was that invisible char as first char on the page and the commented section immediately after did not show as a comment color.
It seems to me that the syntax checker could reset at the next double quote after a syntax error since that must be the start of an actual comment because there would never be an actual syntax error inside a quoted section... Yes?
 
Ken

>
>Levente
>
>>
>>Ken
>>
>>
>>At 10:36 PM +0100 12/8/10, Levente Uzonyi apparently wrote:
>>>On Sun, 5 Dec 2010, Ken G. Brown wrote:
>>>
>>>>Further:
>>>>Where is the invisible character in the Workspace that has the more text, and how do you find it?
>>>
>>>You can find it out by exploring the morphs from the halos. When you find the text, look for invisible characters in the string (typically asciiValue < 33).
>>>
>>>>How do you get the "commented out" at the bottom to color properly?
>>>
>>>You don't, because there are several syntax errors before that comment.
>>>
>>>
>>>Levente
>>>
>>>>
>>>>Ken
>><snip>
>>_______________________________________________
<snip>
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Edwin Castro-3
In reply to this post by Levente Uzonyi-2


On Wed, Dec 8, 2010 at 3:56 PM, Ken G. Brown <[hidden email]> wrote:
At 12:07 AM +0100 12/9/10, Levente Uzonyi apparently wrote:
>On Wed, 8 Dec 2010, Ken G. Brown wrote:
>
>>Thx.
>>I'm wondering if there might be some way for the syntax highlighting to be made to reset itself instead of giving up completely after a syntax error and everything after that doesn't work at all?
>>eg. the quote character? The double quote character should either be the beginning or end of a comment.
>>
>>I suppose it's more complicated than that.
>
>It's more complicated. But why don't you put your text into a comment? Actually that's what comments are for in the language.

Correct, however...
I'm thinking of the case where I have a bunch of snippets in a Workspace, some of which would not work as pasted and therefore cause a syntax error but I still want to leave them as code and maybe later fix the syntax, or use the coloring to see where the syntax error might be occurring in the snippet.
The first syntax error seems to mess syntax highlighting up forever more after the first error i the Workspace. I would like stuff that is actually commented out farther on to to keep showing as comments, even tho there is a syntax error in some code above on the page.

Or the case where there was that invisible char as first char on the page and the commented section immediately after did not show as a comment color.
It seems to me that the syntax checker could reset at the next double quote after a syntax error since that must be the start of an actual comment because there would never be an actual syntax error inside a quoted section... Yes?


What if the syntax error is a missing double quote? The next double quote would indicate the end of the real comment thus causing more syntax errors. I think perhaps you should keep broken code or general text in comments so you can keep the rest of the syntax coloring.

--
Edwin G. Castro


_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Reply | Threaded
Open this post in threaded view
|

Re: loading Shout into trunk?

Ken G. Brown
At 4:18 PM -0800 12/8/10, Edwin Castro apparently wrote:

>On Wed, Dec 8, 2010 at 3:56 PM, Ken G. Brown <<mailto:[hidden email]>[hidden email]> wrote:
>
>At 12:07 AM +0100 12/9/10, Levente Uzonyi apparently wrote:
>>On Wed, 8 Dec 2010, Ken G. Brown wrote:
>>
>>>Thx.
>>>I'm wondering if there might be some way for the syntax highlighting to be made to reset itself instead of giving up completely after a syntax error and everything after that doesn't work at all?
>>>eg. the quote character? The double quote character should either be the beginning or end of a comment.
>>>
>>>I suppose it's more complicated than that.
>>
>>It's more complicated. But why don't you put your text into a comment? Actually that's what comments are for in the language.
>
>Correct, however...
>I'm thinking of the case where I have a bunch of snippets in a Workspace, some of which would not work as pasted and therefore cause a syntax error but I still want to leave them as code and maybe later fix the syntax, or use the coloring to see where the syntax error might be occurring in the snippet.
>The first syntax error seems to mess syntax highlighting up forever more after the first error i the Workspace. I would like stuff that is actually commented out farther on to to keep showing as comments, even tho there is a syntax error in some code above on the page.
>
>Or the case where there was that invisible char as first char on the page and the commented section immediately after did not show as a comment color.
>It seems to me that the syntax checker could reset at the next double quote after a syntax error since that must be the start of an actual comment because there would never be an actual syntax error inside a quoted section... Yes?
>
>
>What if the syntax error is a missing double quote? The next double quote would indicate the end of the real comment thus causing more syntax errors. I think perhaps you should keep broken code or general text in comments so you can keep the rest of the syntax coloring.

Well, I don't suppose that would be an actual error to the syntax highlighter, at least not until it reached the end of the Workspace.
And it would be simple to see since no doubt everything would be comment colored after the first quote?

Ken

>--
>Edwin G. Castro
>
>
>_______________________________________________
>Beginners mailing list
>[hidden email]
>http://lists.squeakfoundation.org/mailman/listinfo/beginners

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners