World: r3wp

synapse chat 0.0.16 at http://www.compkarori.com/reb/pluginchat9.r

the background slows everything down so as per Allen's suggestion, 
I have set saved-area: true for all the buttons.  I did the same 
for the main message area which fixes up the slow scrolling issue, 
but causes a resize error sometimes.  Not sure how to fix this as 
resetting the saved-area to true after a resize doesn't fix it.

If the background is calculated, saved-area: true on background?

try pasting the below in

layout [text "Hello world"]
 or 
effect [grid 10x10]
or
effect [gradient 0x1 255.20.20 20.20.255]

0.0.15 uploaded

Changes:
      New: Updated documentation with images
      New: DATA can now also be a single block of values
      Fix: IN-COLS is no longer mandatory
      Fix: MAIN-COL is no longer mandatory
      New: Default WIDTHS now a fraction value.
      New: Fractional widths of the list width as decimals
      Fix: List size calculation optimizations

      Fix: Scroller width is now always equal to the corner reset button 
      width
      New: SCR-WIDTH lets you set the scroller width
      Fix: AGG is no longer a requirement
      New: CLEAR to quickly clear the list

The files have moved again:
    http://www.hmkdesign.dk/rebol/list-view/list-view.r

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

Seems to be a missing graphic for the docs

ie broken link.

yes, some graphics are still missing. there is a bug in the width 
calculation code, which I want to fix for 0.0.16, so I thought that 
would have a higher priority

what does the corner reset button do ?

resets the sorting mode to 'nosort

Any plans on adding drag and drop on to the list ?

eg. moving elements from one list-view to another?

maybe if I get time, but it will not be added until after inline 
editing and most bugs have been fixed...

we'll try and give you more feedback about bugs then :)

thanks... 0.0.16 and forward will provide some testcases and new 
demos, so it's going to be easier to test.

Graham - please slow down with new features, unless basic ones do 
work :-) I would like to ask you, if you or your users do really 
heavy drag and drop and what is more, even in between several grids?

but I can tell you what our 300 users are used to, working with 3 
grids we introduced within last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. How cbut I can tell you what our 
300 users are used to, working with 3 grids we introduced within 
last 10 years, what they valued most - 


- column resizing was not an issue at all - proper grid can calculate 
size to set it automatically - we had two modes, auto column-width 
adjust, or static, set in config

- drag and drop was rarely used for columns. You can do it othe way 
around - let users to choose which columns they want to see, in what 
order. Let them save the config!!! Without it, forget about your 
grid being powerfull - what ppl are looking for is comfortable view 
of their data. Each person is used to slightly different view

- horizontal scrolling is a must. It is so basic feature, I wonder 
why noone is requesting it? grids based upon list show its main flaw 
- non ability to scroll horizontally. Real life apps do consist of 
more fields usually then you can fit into your screen ;-)

- sometimes users requested split-view, so that few left columns 
got locked and did not scroll horizontally ....

- proper keyboard handling is a must - enter=edit, ins=insert record, 
del=delete record, move by arrows, pgdn, pgup, end home, ctrl plus 
pgdn, pgup, home, end, left, righ ....

Eliza is a hotty!!!

ah damned, I should request new notebook, sorry, my keyboard is so 
broken - few keys don't work and I have to keep "a" in clipboard, 
making wrong presses with ctrl plus c which is near ctrl plus v

pekr, config saving will come, but I'm not sure yet how to do it. 
maybe an object or something.


Horizontal scrolling, I need to figure out. It will be an additional 
mode that can be activated by setting FIT-WIDTH to FALSE. By then, 
a scroller will appear along the bottom and different policies regarding 
column drawing need to be made. A little complex to figure out, but 
it will come.

in honor of good UI design, the horizontal scroller will always be 
visible. I hate the scroll-views that jump around, because of appearing/disappearing 
scrollers

with text-list - does scroller updates automatically when I reassign 
text-list/data to newly formed data block?

No. There is text-list/update. Partially broken. I have a fix somewhere, 
but not used for some month.

still broken even in 1.3.2?

Did not check. Try it :)

:-)

Henrik.........looking good!

Glad you like Eliza Ryan!  :)

Yeah putting Eliza in was funny, might as well add jivespeak : )

LIST-VIEW version 0.0.16 uploaded.

Changes:

      Fix: LAST-CNT crashed on empty SORT-INDEX after filtering

      New: FILL flag to set whether or not to paint all rows in the list 
      view

      New: COLORS/4 contains the color of the background behind the rows.

      New: When resizing OUT-COLS in runtime, WIDTHS is reset to default 
      values

      Fix: Columns can now be appended or removed to OUT-COLS in runtime
      Fix: Changed behaviour so that DATA is always treated as
        a block of blocks if manipulated by LIST-VIEW itself.

        Only external input of a single block value can change this.
      Fix: INSERT-ROW-HERE, REMOVE-ROW-HERE, CHANGE-ROW-HERE
        failed on empty DATA
      New: Stricter typechecks on manipulation functions
      Fix: Values are now copied into DATA
      Fix: Sorting did not work, when using only one DATA column

      New: Allows using keyed blocks as input for manipulating functions.

      Fix: Header size now calculated with OUT-COLS also, which removes 
      a crash
      New: Created a test suite in file list-demo.r
      New: Moved demo code out of this file

    Main file is available at:
    http://www.hmkdesign.dk/rebol/list-view/list-view.r
    Demo and testcases available at:
    http://www.hmkdesign.dk/rebol/list-view/list-demo.r
    Docs are available in makedoc2 format at:
    http://www.hmkdesign.dk/rebol/list-view/list-view.txtand
    http://www.hmkdesign.dk/rebol/list-view/list-view.html

can anybody answer this, or at least provide some hints: I heard 
something about the viewtop becoming open source, did this come to 
pass? can I modify it to suit my own needs (commercially).

Viewtop is currently open source.  NOt sure where the official source 
is located though...

you can modify it, but you have to submit the changes back to RT.

I downloaded it when they released it. Filename is viewtop1200.zip

thanks all!

i think the version in the sdk is more recent.

even better, thanks!

LIST-VIEW 0.0.17 uploaded.

Changes:

      Fix: FILTER was broken. Seems to be a bug in clearing bitsets.

      New: EDT-FLD-ACT and EDT-LST-ACT to let you perform functions when 
      tabbing out of an inline editing field

      Fix: Column selecting marked columns beyond the end of DATA.

      Fix: Fractional widths are now properly resized, when resizing the 
      list

      New: Inline Editing! Can be activated with the EDITABLE? flag (default 
      on)

Henrik - it does not work easily - you can't do list-view and then 
list-demo.r, as it seeks list-view.r on your hd ... that should be 
stated ...

as for demo, I am somehow confused .... your naming conventions seem 
quite strange. Naming something "here" is imo not good. in-cols, 
out-cols, main-col ... what shoul one think of it? why not simply 
all-cols, or visible-colls, etc.?

another things - why main-col is resizable? I saw no desings as such 
yet .... every column should be resizable, or not ...

guys, don't get me wrong, but imo first design should be decided, 
then implementation done, or you will end-up patching your initial 
solution ...

pekr: Listview file searching noted...

pekr, well, I find the names to be logical, but if we can agree on 
better names, it's only a matter of search/replace

I know :-), but e.g. in-cols description in table, I can't even properly 
translate it ..... but then - I am not native englishman, so my problem 
:-)

pekr, MAIN-COL is resizable, because that was easy to do and I use 
that in my design. It works very well in my older implementation.that's 
why I continued using it.

it is just that I don't recognieze main-col functionality with grids 
I worked with so far ... once you allow your users to freely adapt 
your grid (order of columns), which one is main col?

if you don't want any auto resizability, then MAIN-COL should be 
set to NONE, but this isn't tested thoroughly yet. The point is that 
in my lists, I mostly have some data columns that need to be short 
and then one long description column. It fits very well to have only 
that column to be resizable, plus the rows always neatly fits horizontally 
to the list view size.


Later I'll implement your much wanted system for horizontal scrolling 
and in that mode, MAIN-COL won't be needed as the list will take 
up the amount of width that it needs. Then it'll work more like a 
standard list.

list-demo.r quickfix. now always downloads latest list-view.r

0.0.18 uploaded. Only small changes:

      Fix: SCR initialization bug
      Fix: Demo Lab now always downloads the latest list-view.r

      Fix: If MAIN-COL is NONE, then the first column will be resized.
      New: Decoration in the upper right corner button

No new docs today.