Hi Keiron etc, I'm really happy to see all this movement going on and folks from the "maintenance" branch getting into the redesign to help you out. I'm hoping to be able to start contributing again too, perhaps not right away, but hopefully in September. There may even be some possibility of getting to work on FOP as part of my "real" work, though it might be hard to work on the new layout in that context. I'll keep the group posted.
I'll start by looking at the latest and then maybe cogitating on list or table layout, depending on the timing and what others are interested in doing. It looks like status.xml is the sign-up sheet for the tasks; is that right? With regard to the line-height calculations, is anybody in the group interested in getting into the gory details of the baseline stuff for different scripts? I spent some time poring over the spec and trying to get a handle on this, but maybe it's too much detail for now. On the other hand, I'd really like to make sure that this version of FOP handles that stuff correctly as well as being able to do the various kinds of line-stacking strategies defined by the XSL-FO spec. Regards, Karen Keiron Liddle wrote: > Now that we have some pagination there are lots of areas that people can > work on. > If you want to implement any of these and have any questions then just > ask. > > Once we can get a few of these done then we could do a developers > release. > > > - Add static areas to page > The static areas will need to be handled in a similar way to the flow > except the bpd is unlimited and it will need to reset and repeat for > each page. > > > - Add id areas to page when area added > When the layout managers add an area to the page it can also add the id > information. > > > - Resolve id references on other pages, extensions > When an id is added to a page this will allow id references to be > resolved. > > > - Add markers to page when areas added > When an area is added that is created by an FO that contains markers > then the markers can also be added. There are four types of positions > for markers. > > > - Retrieve markers from page > When doing the static areas the markers wil need to be available for > retrieving. The marker can then be layed out as normal. > > > - calculate line height > The line height needs to be calculated while finding breaks. This needs > to include all the alignment and height details of the inline areas. > > > - Various inline objects > Page number, page number citation etc. need to be implemented. > > > - Implement page caching > If a page need to be stored for the store pages or waiting to resolve > forward references then we need a cache mechanism to save the page > somewhere. > > > - Implement table layout > The table layout will use the same technique as the block layout. It > will locate suitable breaks between rows or inside rows until table > finished or end of bpd reached. > > > - Implement list layout > The list layout like the table layout will be looking for suitable > breaks from the child objects. The it will add the appropriate areas to > the area tree. > > > - Get bookmark extension working > Make sure the extension id references are resolved. Once the data is > fully resolved then implement a way for the pdf renderer to add the > bookmarks. See branch for code how to add bookmarks. > > > These are just some of the things, I will add them to the todo list. > If there is a decent response then there are more that can be added. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
