From: Bob D. <bd...@si...> - 2003-12-04 19:44:24
|
Hi, @ SICOM we agree we want to have this type of feature in RLIB.. more in the PDF for us.. but we always do the other formats to be consistent. Everton pointed out that RLIB doesn't span memo fields correctly yet... so I need to make that happen before I can start to worry about "boxing" stuff.... so give us a little time.. but expect it to be in before the 1.2 release - Bob On Thu, 2003-12-04 at 11:18, Jeff Kowalczyk wrote: > Bob Doan wrote: > > Right now rlib has a concept of "Output".. which contains "Images", > > "HorizontalLines", and "Lines".. "Lines" in turn contain "Text" and > > "Data".. Its as simple as that at the moment... You are asking for the > > ability to "Box" items... mainly "Text" and "Data" in lines.. so the > > "Line" we would add a property box="..some style..".. > > To implement this we would have to first settle in on what exactly the > > properties of boxing would be.. Chet.. Bob Kratz... any suggestions? > > I see. Looking at > http://docutils.sourceforge.net/spec/rst/reStructuredText.html#tables > > +------------------------+------------+----------+----------+ > | Header row, column 1 | Header 2 | Header 3 | Header 4 | > | (header rows optional) | | | | > +========================+============+==========+==========+ > | body row 1, column 1 | column 2 | column 3 | column 4 | > +------------------------+------------+----------+----------+ > | body row 2 | Cells may span columns. | > +------------------------+------------+---------------------+ > | body row 3 | Cells may | - Table cells | > +------------------------+ span rows. | - contain | > | body row 4 | | - body elements. | > +------------------------+------------+---------------------+ > > Perhaps auto wrapping and spanning aren't necessary in the > context of precision layout like rlib uses. After all, the > objective is only to make certain rlib text output optionally > reST compatible. This way, each line wouldn't grow a dependency > on previous and subsequent lines for floating bordering. Note > that the exterior borders have no difference to internal > borders, which is convenient for the implementation. > > - normal specification of column widths should result in good > alignment, user can tweak alignment if reST column spanning is > desired. Row spanning wouldn't be as simple. > - header property, affects lower border style. > - line may need a height (in lines) property, user is > responsible for specifying height, truncate overflow? > - specifying text/data cell width to align in a reSt compatible > fashion is probably OK to ask the user to handle in the > report definition. > - default single space side margin property for cell? Reports > that are tight on space may wish to omit margin space. > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Rlib-users mailing list > Rli...@li... > https://lists.sourceforge.net/lists/listinfo/rlib-users |