[news.eclipse.tools.gef] Re: draw2d.text indent strategy

["Randy Hudson" <none@xxxxxxxxxx>]

> Code.  (No, I haven't gone loco =D)

Funny, if you look at our text example in CVS, you'll see that we've modeled
import statements and javadoc regions.  I'm just making up test cases, but I
believe code should be edited wysiwyg-style.  Instead of typing "{", then
indenting a bunch of lines, then typing "}", why not just select the code
and invoke "block" command.  I don't think I should ever have to type or
delete a single TAB.  And of course, JavaDoc should be edited as HTML.
Another benefit of using figures would be that "code-folding" could be more
flexible.  You could reformat other peoples code as you are viewing it, or
change sorting of members, etc.

>
> > I think that LineBox and boxes in general need to support "padding" and
> > "insets".  For first line indentation, the LineBox would have left
insets
> >  >
> > 0.
>
> We're on the same page here.  I'll tinker and see what develops.

If you would like to contribute to GEF, our goals would be to conform to
CSS2 definitions of boxes, padding, insets, borders, etc.

>
> Are you blue-skying at this point or is this something in the works?  I
only
> ask to determine my own level of effort.  I'm more than happy to help with
> this but I don't want to noodle through something that's already been
> noodled through.

If you want to track these items and/or contribute, open bugzillas to avoid
both of us working on the same thing.  For now there is not a bugzilla open
for inline borders, nor for padding.

>
>
> --
> Rob Grzywinski
>
>