From: Sebastian G. <S.G...@pi...> - 2000-07-11 15:32:30
|
Hi! I'm currently working on anchors (to get URL's like "foo#bar" rendered correctly, bug #10), and I have two questions: 1. Does anyone do anything on tables? It's because I will change the DwPage widget, and this is probably also necessary for tables; so we should avoid to get problems patching both togeher. 2. My basic idea is: o Extend the DwPage widget: add a new DW_PAGE_CONTENT_ANCHOR, which has zero size and is not drawn in any way. o The point to start is Nav_open_url. This function should get the requested anchor after the "#" and store it somewhere. Probably, the page should not be loaded when the href points to an anchor in the same file. Later, the pixel position should be calculated. "Later" means: - when the page has already been loaded: immediatly, or - otherwise: when the lines in the page are wrapped, or, perhaps, already when the correct <a name="..."> is read (probably not). The last problem does not seem too hard. My question is: where to store the requested anchor? BrowserWindow would be simple, but when frames are implemented later, the requested anchor should belong to a frame. DwPage would be better, but when I follow all the created structures, there is a break in the IO/Mime module where the anchor gets lost (?). What about DwBorder becoming a base Widget for a frame? Any suggestions? Sebastian. |