As luck would have it, I just finished writing a set of unit tests to verify filein and fileout capability of text attributes. This is included in CollectionsTests-dtl.209 in the inbox. I think this may make it somewhat easier to understand and maintain the support for styled text in code.
http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-January/175795.h...
As a matter of policy, it seems to me that since source code can be (and sometimes is) in the form of styled text, and given that various people have found interesting uses for this over the years, we should not do something to make that impossible.
I also agree that it is preferable to store source code as plain text wherever possible. I just would not want to make it impossible to store styled text in the cases where someone has a good reason to do so.
Dave
On Fri, Jan 3, 2014 at 12:03 PM, Frank Shearar frank.shearar@gmail.comwrote:
OK, so that's you & I in agreement. I think Colin's happy for it to go. Any ol' timers out there with warnings of doom, before I rip this out?
No, I certainly wouldn't miss it.
I will say this, however. I don't know if it goes all the way back to ST-80, but I do remember that styled code was considered important in the early days of Squeak. I seem to remember some tweaks to Monticello when it first came out that would allow it to store styled code the same way it's stored in the changes file. IIRC we even supported hyperlinks in code, although I don't remember actually seeing one in the wild.
Therefore, we ought to decide if this is a change in policyi.e., we're going to support plain-text source code onlyor if we're just rejiggering preferences for better modularity. If it's a policy change, we have a free hand simplify the codebase accordingly, take styling commands out of code editors and so on. It doesn't have to be done right away, but let's consider that on the agenda for 4.6.
On the other hand, if we consider styled source code important, we should figure out how to change the preferences to play nicely with Shout for those who use it, while still retaining the ability to manually style code and persist those styles along with the content of the code.
Personally, I'd vote for plain-text only code. I can see the value of styled code, but that's not the way the world went, and it's no longer worth the complexity or friction when dealing with the world outside of the image.
Colin