World: r3wp

uploaded 0.0.11

Changes:

      New: Header can now be defined from the words in OUT-COLS or IN-COLS

      New: No longer need to manually create the subface for the list
      Fix: DATA was not properly initialized

      Fix: List was updated twice during all manipulation functions added 
      in 0.0.10

      New: Added /no-show refinement to FLT-LIST to speed up certain updates 
      that require setting the selected row before showing

oops... the example code has been commented out, but the example 
line at the bottom should be fairly easy to figure out :-)

hm... still a bug when initializing the header... hang on

there... new 0.0.11 uploaded

seems to work now

I should start working on the docs now, so people can test it out 
a bit...

How to set the column sizes ?

by making a layout manually :-) seriously I need to make that a bit 
easier...

MAIN-COL sets the column that should be resizable

I could make a block of widths, but somehow it'll get less than managable 
when OUT-COLS will start to get dynamic. I'm not sure yet how to 
do it easily, so all columns simply have a standard width of 100 
pixels.

repeat i length? out-cols [
          insert tail lo [list-text 100]
        ]

except the first column is 4x the size of the second column.

u must resize it somewhere.

it does, because MAIN-COL is normally set to the first column

how about using a block of widths first off ? Then optimise later 
on.

and it automatically expands it to the total width of the list

and the width of the list is determined by what ?

SIZE

you could: view layout [list-view 600x200]

I'll give it a go with a width block... hopefully it won't come back 
and take revenge later :-)

try using a height of 350

the last row is higher then the others

BTW, I'm trying to make it blend in as good as I can with the rest 
of VID by using the same keywords and functions.

no, the bottom portion happens to be in the same color as the last 
row, which isn't entirely at the bottom. that was an easy/quick fix 
at lists that don't add up height wise.

We don't have a resizable bsd licensed multicolumn list ... so carry 
on :)

so the background behind the list rows is simply 240.240.240

I made it BSD licensed, because maybe someday a thousand years into 
the future, when the code is good enough, it could be included officially 
in VID

are the row heights adjustable ... or do I have to hard code them 
?

manual layout again, yes... do you need variable height like in AltME 
so it fits the text?

No, don't need variable height.

where to change the row height and font size for the rows ?

also by manual layout... I think it's actually easier to create the 
manual layout if you want to set a lot of parameters such as:

list-text 75 right bold font-size 17

which is standard LAYOUT dialect

then you can set all parameters of the list-text face

this is also how LIST in VID works

I'll have to read the wikibook again :)

luckily I managed to write a section on LIST in the wikibook :-)

LIST is grossly underdocumented in the original VID docs... If I 
had found it sooner, I could have saved 3-4 weeks of work this summer 
:-(

I've got a new version (0.0.9) version of the chat client at http://www.compkarori.com/reb/

which incorporates Henrik's list ( not used yet though ), and Allen 
has added his link parser :)

http://www.compkarori.com/reb/pluginchat.rfor those not using IE.

version 0.0.12 uploaded.

Changes:
      New: Documentation!

      New: WIDTHS block to let you determine the widths of the columns

    Docs are available in makedoc2 format at:
    http://www.hmkdesign.dk/rebol/list-view.txtand
    http://www.hmkdesign.dk/rebol/list-view.html


Note the new url for the source code for LIST-VIEW is http://www.hmkdesign.dk/rebol/list-view.r

In the coming versions, I will remove the original demo and rely 
more on the docs. I might provide an updated demo later when the 
list view is in a more reliable state.

Henrik it will be cool if you can make list view model independant.

What I mean by this is that list could request a model to give the 
data to display for the specific row. Instead of enforcing a particular 
model for the data representation.

hmm... could you give an example? my brain is a bit fried right now 
:-)

Right now all *data model* is a block. But you may want to be able 
to access a file of bytes and some particular fields in that stream.

So, instead of forcing the conversion of the bytes stream in the 
block data model. The list view could interrogate the controller 
to extract the data from the base model.

So list-view will say to an intermediary function give me the first 
row of values. This intermediary function ask the conversion func 
aka the controller to extract and conver the data from the reall 
*data model*. The controller returns this to the list-view list-view 
displays the row of data.

So LIST-VIEW will use the MVC paradigm. (Model-View-Controler http://en.wikipedia.org/wiki/Model-view-controller)

This way LIST-VIEW is *data-model* independant. Programmer doesn't 
waste ram or cpu cycles converting all data to from *real data model* 
to LIST-VIEW expected *data model*. The programmer only need to write 
the controler part. Which is taylor for efficiency. You only need 
to extract the values that are visible by the LIST-VIEW at any given 
moment from the *real data model*.

The current list-view is quite nice. ;-)