Hi Tobias, Tim,


On Tue, Oct 8, 2013 at 1:58 PM, Tobias Pape <Das.Linux at gmx.de> wrote:

> Am 08.10.2013 um 22:49 schrieb tim Rowledge <tim at rowledge.org>:
>
> > On 08-10-2013, at 12:58 PM, Eliot Miranda <eliot.miranda at gmail.com>
> wrote:
> >>
> >> If it weren't for comments (and comments are /really/ important) we'd
> have implemented a parameterised formatted by now that auto-formatted code
> to the preferences of the reader and this would all be moot.  But without a
> good AI I don't see how to spot and preserve while reformatting multi-line
> comments, comments with diagrams in them, etc, etc, etc.
> >> --
> >
> > One possible thing we could do with comments is make them act like
> comments to annotated Word/Pages documents. Select the section of code, hit
> MagicKey-comment, enter comment in balloon. Comments get to live in their
> own private formatting space, unaffected by whatever happens to the code
> layout. Possibly, they could be handled so that the code differ doesn't
> have to get confused by them, potentially simplifying that important job.
> >
>
> CodeTalk.
> https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/codetalk
> Yours truly had been involved with this in his bachelor's project[1]
> which then was done in cooperation with Andreas and Qwaq.
>
> There is a Paper[2] with screenshots also, an Marcel[3] wrote his
> Bachelor's Thesis
> about this[4].
>
> You get pop-out chats on your code that get sync-ed via a monticello
> extension.
>

So what does a file-out look like?  What's the textual/interchange format
e.g. in a Monticello package?


> > once you have them separated, you can display them according to whatever
> algorithm you like. Inline them, have them float at the side, have them
> only pop-up when pointer is in the relevant region, list them at the end
> like footnotes, whatever. Or even invert the view - have the comments
> appear as the main text with the code off to the side.
> >
> > tim
>
> Best
>         -Tobias
>
>
> [1] Our Univerisities way to get your fingers dirty in order to be able to
>     write your thesis.
> [2] http://www.taeumel.eu/pdf/codetalk-ieee.pdf
> [3] The guy who also did the Morpic designer:
> https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/designer
> [4] http://www.taeumel.eu/pdf/bachelors-thesis.pdf
>
>
>
>


-- 
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131008/a61ff1e5/attachment.htm