work
VA stuck an SMP server with a gig of ram in my cubicle for
me to play with. How nice of them. As if the 100mbit
internet connection wasn't enough to keep me happy ;-). Did
I mention that they pay me too, in addition to all of this?
:) It's so hard to believe that you would be payed to sit at
a desk with a superfast internet connection and amazing
computers, but I guess that's what VA is about.
play
I worked some more on the normal mode patch for AbiWord.
After fixing up some annoying conflicts caused by the huge
commit today for lists, I tried to make it hide the left
ruler in normal mode. It's not easy. First, the view isn't
created when the rulers are being created, so I guess I have
to go with rulers on until the view comes to life and
decides otherwise. The modification to the code is pretty
simple. I wouldn't mind doing it once but due to the
braindead Abi hierarchy each platform has pasted code for
doing that same thing the same way with
s/oldplatform/newplatform/g. So once I DO get it working on
Unix I'll have to do it for windows, mac, qnx, beos, etc,
and I'll have no way to test it on any other platforms. And
hinding the left ruler is the easiest of it all, here's my
TODO list as designed by Paul Rohr for the normal mode code:
Done:
- don't draw borders or background
- easy toggling between modes
Not sure:
- still print like the existing "page layout" view
TODO:
- no left ruler; top ruler starts at the left margin, not
the left of the page
- format all content as inline blocks in series
- labelled dotted or dashed lines for section / column
breaks (page breaks completed)
It's not going to be easy. Left ruler stuff is a
nice
challenge but nothing compared to doing the kind of hacks in
the formater required to make it work right. Right now it is
a tiny hack as hacks go and it does not work right: there
are columns and several major bugs that don't let you move
the cursor up or keep a huge margin at the bottom of the
page when there should be none. And once the behavior is
more correct, printing will probably be broken becuase it
should use the current WYSIWYG behavior, so I will have to
support both modes at the same time for different devices.