Ok, I did my experiment with slashdot first (a site I remembered looked terrible on Scamper, and didn't hold much hope for). Well, it still looked bad enough I couldn't figure out exactly what was going on, but it was in the right format, with errors, not strung out indeterminately, as is was before.
Anyway, switched over to lwn.net, and that is actually readable now! Two biggest problems I saw: 1. Frames sometimes overlap. If they're located wrong, I can deal with that, but if things are occluded, they're much harder to read ;-) 2. Frames (and maybe text?) sometimes seem to extend beyond the limits of their containing frames.
I tried to figure out why all the frames have borderWidth 2 (which is not critical, ), while the HTML specifies width 0, but couldn't find where that was set...
Any hints on that?
Daniel
Karl Ramberg karl.ramberg@chello.se wrote:
This is a multi-part message in MIME format.
--Boundary_(ID_Jb6/yWrlO4D2jr2KCxQFCg) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT
This is yet another version of my HTMLTableMorph. The design is the best yet :-)
Do not save in a image that requires Scamper to function unaltered. Some issus are not solved with HTMLSelector and HTMLInput :-(
Also the most notorious problem that is not solved is table in table renderering. Some invalidation of owners layout must be signaled and redone, a little tricky.
Most obviously the rendering is not yet doing the right thing with border width, inset etc. Shold be quite easy to add.
Test this out and report or better send some fixes back.
Karl
danielv@netvision.net.il wrote:
Ok, I did my experiment with slashdot first (a site I remembered looked terrible on Scamper, and didn't hold much hope for). Well, it still looked bad enough I couldn't figure out exactly what was going on, but it was in the right format, with errors, not strung out indeterminately, as is was before.
Anyway, switched over to lwn.net, and that is actually readable now! Two biggest problems I saw:
- Frames sometimes overlap. If they're located wrong, I can deal with
that, but if things are occluded, they're much harder to read ;-)
Thats the table in table bug.
- Frames (and maybe text?) sometimes seem to extend beyond the limits
of their containing frames.
I tried to figure out why all the frames have borderWidth 2 (which is not critical, ), while the HTML specifies width 0, but couldn't find where that was set...
It's just the default look for RectangleMorphs, wich table is a sub class off. The table has a border and the cell has a border. Seeing where the stuff is located makes it easier while figuring out what is going on during development.
If you look in HtmlTable>>addToFormatter: and HtmlTableDataItem>>addToFormatter: you can add stuff that set borderwidth quite easy in this form: width _ (self getAttribute: 'width'). Karl
squeak-dev@lists.squeakfoundation.org