OpenEuphoria

1. generic coding problem

• Posted by ChrisBurch2 <crylex at freeuk.co.uk> Aug 07, 2006
• 578 views

Hi

As much to write this down, as to ask for help.

I create a 2d table, with an unknown number of columns, and an unknown number
of rows

Each of the columns has an unknown, but uniform number of characters (ie each
cell in the column has the same length)

I want to print the table on a printer using fixed fonts.

The printer can either support 80 or 124 characters. Printing switches from
80 to 124 if the total character count (with spaces) is greater than 80.

When printing the row title must always be shown, but the column title does
not need to be shown, except as a first row

All the data must be printed, word wrapping is not allowed.

I started with the concept of a 'page' onto which I place the characters of
each  cell, but my brain is exploding.

Has anyone done anything like this before. BTW this is not windows or 
wxEuphoria programming, just raw stuff.

Cheers in advance

Chris

3. Re: generic coding problem

• Posted by Chris Burch <chriscrylex at aol.com> Aug 07, 2006
• 534 views

Hi

All the columns can have different lengths, but all the cells in the same
column have the same length.

Chris

http://members.aol.com/chriscrylex/euphoria.htm
http://uboard.proboards32.com/
http://members.aol.com/chriscrylex/EUSQLite/eusql.html

5. Re: generic coding problem

• Posted by ChrisBurch2 <crylex at freeuk.co.uk> Aug 08, 2006
• 538 views

Pete Lomax wrote:
> 
> On Mon, 07 Aug 2006 11:46:54 -0700, ChrisBurch2
> <guest at RapidEuphoria.com> wrote:
> 
> >As much to write this down, as to ask for help.
> Understood.
> >
> >I create a 2d table, with an unknown number of columns, and an unknown number
> >of rows
> >
> >Each of the columns has an unknown, but uniform number of characters (ie each
> >cell in the column has the same length)
> So during/after creation of the 2d table are you checking down every
> column in the table to get the maxwidth?

Thats not requirement, but yes it could be an optional extra. One of the
function defs was for the table to have been preformatted so that the title
lengths were the same as the rest of each of the column for each column title

> >
> >I want to print the table on a printer using fixed fonts.
> >
> >The printer can either support 80 or 124 characters. Printing switches from
> >80 to 124 if the total character count (with spaces) is greater than 80.
> >
> >When printing the row title must always be shown, but the column title does
> >not need to be shown, except as a first row
> >
> >All the data must be printed, word wrapping is not allowed.
> So after adding all the column maxwidths and finding it greater than
> 124, what are you doing? Do you want to find the column(s) which
> mini-wrap to give shortest overall report, eg:
> 
> kernel32.dll OpenFile Some fairly long description which is probably 
> 			the best thing to wordwrap...
> kernel32.dll ReadFile
> kernel32.dll WriteFile
> kernel32.dll CloseFile
> 
> rather than:
> 
> kernel32 Open Some fairly long description which is ...
> .dll	File
> kernel32 Read
> .dll	File
> kernel32 Write
> .dll	File
> kernel32 Close
> .dll	File
> 
> Or is >124 an error, or just truncated?

No wrapping. The columns left over would be printed on the next page, as would
columns left over from that. Imagine a very large spreadsheet, printed over
several pages.


> >
> >I started with the concept of a 'page' onto which I place the characters of
> >each  cell, but my brain is exploding.
> I'd analyse everything, then build a format string (or two), then
> print in one pass at the end, possibly under control of some table I
> built in the analysis phase.
> 
> >Has anyone done anything like this before. BTW this is not windows or 
> >wxEuphoria programming, just raw stuff.
> 
> The only thing which springs to mind for me is my common code analysis
> routine (now part of edita [eacca.e]) which outputs eg:
> 
> -- 9095  9105                               styleMask = xor_bits...
> -- 9096    |                                style = and_bits( style...
> -- 9097  9107  9159  9168                   if style != curStyle then
> -- 9098        9160                             VOID = w32Func...
> 

ooh, windows, and way too complicated for me brine.

> Now I know this is probably not relevant, but 9105..9107 (length 3) as
> the longest matching group gets prime position in column 1, then
> 9159..1960 (length 2) is next but since it can't all go in column 1 it
> all goes in column 2, and lastly 9168 (length 1) goes in the next
> available column, 3. So it is playing with columns, first calculating
> what needs to be printed, then where, but is unlikely to be the sort
> of thing you mean.

Actually not that far off. When I conceptualise it, I see a rectangular window
no bigger than the printable page, which takes data from the table, puts it into
a file to print, and then moves the window to the next spot. The columns need
to remain in order presented to the function.

Note the length of the table doesn't matter, because enscript takes care of
that. Enscript will also split large files, but not cleanly on spaces, and
you have to specify the section.

> 
> Regards,
> Pete
> PS thanks for the startup monitor link.

Mike Lin was 16 when he wrote that several years. He will go far.
> 
>

7. Re: generic coding problem

• Posted by Chris Burch <chriscrylex at aol.com> Aug 08, 2006
• 540 views
• Last edited Aug 09, 2006

Hi

Thats very good. You type faster than I think. Definitely given me some more
clarifying ideas.

Cheers

Chris

http://members.aol.com/chriscrylex/euphoria.htm
http://uboard.proboards32.com/
http://members.aol.com/chriscrylex/EUSQLite/eusql.html

9. Re: generic coding problem

• Posted by ChrisBurch2 <crylex at freeuk.co.uk> Aug 11, 2006
• 559 views

Pete Lomax wrote:
> 
> On Tue, 08 Aug 2006 17:16:49 -0700, Chris Burch
> <guest at RapidEuphoria.com> wrote:
> 
> >Hi
> >
> >Thats very good. You type faster than I think. Definitely given me some more
> clarifying ideas.</font></i>
> btw, that demo is much better with
> }}}
<eucode>
> constant maxwid=79,         -- characters across page
>          split_text_cols=0  -- 0 to stop text splits
>  ...
>     colwidths = repeat(0,10+rand(20))
>  ...
> --  k = rand(3)
>     for i=1 to length(colfmts) do
>         k = rand(3)
> </eucode>
{{{

> 
> Regards,
> Pete
> 
> 
Hi Pete, this is what I came up with (debugging stops still present)

------------------------------------------------------------------------------------------------------------------
global function printers_reports_table(sequence tbl, sequence tbl_title)
--takes a formatted table of strings, and works out the best way of printing it
on paper.
--Rules
--      cells must be pre formatted strings
--      cells in each column must all have same width, but
--      different columns do not need to be same width
--      table must be uniform - eg, 3 * 9, all rows and columns must be the same
count
--paper rows and columns for printers hard coded here, but may not apply to all
printers

--seem we can use the enscript slice function for this!
------------------------------------------------------------------------------------------------------------------
sequence orientation
integer row, col, max_row, max_col
integer landscape_cols, portrait_cols, char_cols, char_count, r_loc
sequence print_command, line, line_new
integer fp
integer col_start, col_end, cur_column, cur_row, cur_char_pos

portrait_cols = 79      --actually 80
landscape_cols = 124    --125

--define maximumum row and column numbers
max_row = length(tbl)
max_col = length(tbl[1])

review_data(tbl)

--find the length of characters required to print one row
char_count = 0
for i = 1 to max_col do
        char_count += length(tbl[1][i]) + 1
end for

--can only really do this if using enscript to process the text files, so check
this
if match("enscript", printers[PR_REPORTS]) = 0 then
        VOID = get_yn_box("No enscript match")
        return 0
end if

--decide on orientation, and create page to print on
if char_count <= portrait_cols then
        orientation = "-R"
        char_cols = portrait_cols
        --line = repeat(' ', 80)
else 
        orientation = "-r"       
        char_cols = landscape_cols 
        --line = repeat(' ', 125)
end if
--paper = line


--find the position of the "-r" or "-R" in the printer string,
--and replace it with the above one
--if not present, just add it.
r_loc = find("-R", upper(printers[PR_REPORTS]))

if r_loc = 0 then
        print_command = printers[PR_REPORTS] & " " & orientation
else
print_command = printers[PR_REPORTS][1..r_loc-1] & " " & orientation &
        printers[PR_REPORTS][r_loc+3..$]
end if

VOID = get_yn_box(print_command)

--first copy as much of the row across onto the paper,
--marking where have to stop - next one for next 'sheet'


--now create the file to print
cur_column = 2          --header count
col_start = 2
cur_row = 1
cur_char_pos = 1

line = ""
line_new = ""

fp = open("report.txt", "w")
puts(fp, tbl_title & "\n")
for i = 1 to length(tbl_title) do
        puts(fp, "=")
end for
puts(fp, "\n\n")

while 1 do
        line_new = ""
        while 1 do
                if cur_column = col_start then
                        --put the row title on
                        line_new = tbl[cur_row][1] & " "
                        line = line_new
                        if length(line) > char_cols then
VOID = get_yn_box("The row title is wider than
                                the page!")
                                return 0
                        end if
                end if

                --line_new = append(line_new, tbl[cur_row][cur_column] & " ")
                line_new = line_new & tbl[cur_row][cur_column] & " "

                if length(line_new) < char_cols then
                        line = line_new
                        cur_column += 1
                        if cur_column > length(tbl[1]) then
                                --have we gone past the end of the table?
                                exit
                        end if
                else
                        --line_new is of greater length than the page
                        --write out the line, exit from this loop
                        puts(fp, line & "\n")
                        exit
                end if
        end while

        --advance the row
        cur_row += 1

        --have we gone past the end of the table?
        if cur_row > length(tbl) then
                --restart table, with new start of column chunk
                cur_row = 1
                col_start = cur_column + 1
                puts(fp, "\n\n")
        else
                --otherwise just put it back to the start of the chunk
                cur_column = col_start
        end if

        if col_start > length(tbl[1]) then
                --have gone past col count
                exit
        end if
                      
end while
close(fp)

system_view_file("report.txt")

return 1
end function

It took me a lot longer to get here, than you did, 
but you cleared things in my head, as much as anything else, and its mostly,
but not fully, tested yet.

Cheers, 

Chris