AltME groups: search

^e ^q and you are back to console

hmm... and to get this function available at startup? I remember 
a user.r file somewhere...

This is pretty cool! I added do-events at the end of the scratch 
script.


Now I'm running a GUI program, and I can exit to the console though 
a "halt" button in the GUI. I 'SCRATCH the function I need and CTRL-E 
the changes and I can continue working with the GUI program with 
the new changes without quitting the editor. :-)

what I want to is right click on an image, copy to clipboard, and 
then paste it into a rebol application.

depending on app you can also paste the filename/url instead? as 
workaround? But image-clipboard and drag/drop ae so comfortable.

oh... it's because text is bound to a string, where you can't bind 
to TRUE and FALSE...

:-)

You're dealing with objects. A face is an object. The WITH block 
assign values to the attributes within the object, or extend the 
object with new attributes. Just like:
o1: make object! [a: 0]

o2: make o1 [a: 1 b: 2]	; the attribute a gets the value 1, and a 
new attribute b is created and gets the value 2.


Some data types in REBOL are references, when used in objects, some 
are not. (Remember that data types are grouped as scalars, series, 
etc.)

The data types in REBOL are one major cornerstone and reason, why 
so much functionality can be written with such little code.
(As I see it.)

Maybe new release is near :-) I just noticed there is few of nice 
bugfixes with comment like: Fixed in Core/SDK 2.6.2 and View 1.3.2 
....

I could really use a method for slowing down mouse events globally. 
I have a rather complex GUI with about 50 buttons, 2 listviews, fields 
and whatnot. If I accidentally click'n'drag above an empty area of 
the GUI, the interface stops responding for several seconds. I wonder 
how this could be done...

I have a frustration about the View editor that I don't see in RAMBO. 
 When no text is selected and one hit's ctrl-C, then ctrl-V  it pasts 
the entire document wherever the caret is.  I'm not sure if this 
is supposed to be a feature, but does anyone else find it annoying?

And this fixes it:

it might not be a bug in the editor, but try to load a large file, 
and select text with the mouse. you can't push the text scrolling 
down, if you go beyond the upper or lower window edge

Why do you think so?   My natural reaction is to expect something 
blank, or at least not have to close a file that I don't want open. 
  While you don't "close" a document in editor, I have to sit and 
think, "is this something that I want to be open right now or not?" 
   I find it disruptive from a UI standpoint

It was something with offset-to-caret and parse string "^/" IIRC

If you have word wrap on you'll also have to calculate the width 
of the text field and find the wraps.

If it is caret, this (parsing could be improved to not copy, and 
polling dropped by patching feel or set-face)

edit-text binding : IIRC you have to bind it to ctx-text and maybe 
system/view too.


set in ctx-text 'edit-text func [args] bind bind [newfunc] ctx-text 
system/view
(or something of this kind)

Hi - could anyone try following? I wanted to try some demos at my 
work, so I wen ty Cyphre's rebsite - start desktop\public\sites\cyphre\ 
 and try Magic carpet ...at my work, with latest View, I could run 
the script and once I tried to close it, Rebol crashed, each time. 
I wanted to try it here at home, to eventually submit RAMBO ticket, 
but I am not able to even start the script - window shows, I can 
see black background, I can see rotating hours icon, then it silently 
disappears ... so - could anyone try it too?

Works fine for me -- and no crashes when closed.
But it fails to be minimized if I try that.

thanks - crashed on me at work, and script closes automatically here 
at home ...

whoo, so many lists now :-) btw I wonder why Carl did not include 
his newer version of list, which was imo bacwards compatible, improved, 
and was done at days of IOS 1.3 View initiative ...

maybe as we found AGG, some small and cute 3D one plus compositing 
one could be found and integrated too :-)

And can be easily guified with sdk..

question: I'm using a text-list, which I update with some data after 
the use selected an entry. I want the slider to go to the top and 
show the first entry in the list as well. Positioning only the slider 
leaves the entries somewhere in teh middle.

Sorry, Robert. There is something I want to announce. :-)


http://hmkdesign.dk/list-test.png<--- a picture of the list view 
I'm building.


Currently about half done and quite usable at this time: It's resizable. 
Values are stored as blocks of blocks. All columns can be sorted. 
Input columns can be filtered so you can show only some columns. 
Columns can be freely reordered (but not in the GUI yet). One arbitrary 
column can be resized.

It has the normal range of series manipulation functions available 
in REBOL. There is also possibility for inline editing, by doubleclicking 
a line. Changed values are automatically stored in the list. All 
such operations are "bundled" in the list view VID code and you only 
need to provide whatever functions needed to store the list data 
in an external place. If a text entry is too wide, it'll be neatly 
cut with ellipsis (...).

Filtering function, to filter input by rows. Also has a scroll-to-selected-line 
function.

It's about as fast as the current LIST in VID, since it really is 
LIST with just a whole bunch of extra functions to make general list 
views easy. There are functions possible for clicking and double 
clicking and functions for retrieving rows and columns.


Current limitations: No mouse over indication (can't make it fast 
enough). Only one resizable column. No keyboard navigation. No horizontal 
scrolling. No scroll-wheel support. It doesn't integrate 100% with 
VID yet. I'm using some of my own widgets and bitmap graphics from 
a pretty big GUI library. Stripe look, font and coloring is locked. 
No standard settings yet for the list view.

All code is about 250 lines.


Planning: Reordering columns via drag'n'drop. Column resizing, if 
I can figure it out. Format the font object conditionally from list 
input (make this line bold if the age column is > 45 years, etc.). 
Grid drawing. Images in list rows. And if I can get around to it: 
Single cell in-line editing ala spreadsheets. :-)

Yes, you can freely do that in runtime, although there is no method 
for doing that within the list. All viewing and filtering operations 
are non-destructive.

columns have input and output description blocks. so if you have 
a dataset with [name height weight age sex] you can select to output 
[name age] and also rearrange that to [age name] and simply refresh 
the list. also adding and removing columns can be done on the fly.

I prefer having grid with nice and open/extensible functionality, 
than with knowing it is based upon 'list or other style - make it 
from scratch, if necessary :-)

And nice announcement. Be sure to integrate it into RebGUI as well.

The caching stuff you mentioned is something I partially did for 
my old listview. Correctly the listview was very fast, but also very 
memory hungry, took a long time to initialize and the code was 5 
times bigger and a lot harder to maintain.


This one simply doesn't paint anything other than what is seen, so 
if you have a million rows, only 15 will be painted, if you have 
15 visible rows on screen. The backside to the LIST which this one 
is based on is that it uses iterated faces. This means that if I 
only do a small change to one face, it has to repaint the entire 
list view with all rows. That's why mouse over became too slow to 
be practically useful. I'm not sure yet how to fix this problem.

And please, add auto-filter functionality a la Excel to the columns. 
Very handy for most programs as it frees you from having to develop 
a query-dialect.

Henrik, I advise building this style from FACE (ie. not an existing 
style, like LIST). Makes it less dependant on other code, more portable 
(ie. to RebGUI), and you will be forced to write your own pane function, 
which you will need to do anyway . :)

I based a lot of styles on existing styles, and this is a great way 
to learn, but I found as existing styles were changed (bugs fixed 
or ottherwise), my styles would break. Then it's a run-around to 
do a version-dependant fix for the problems.

I just unzipped it, hit enter on .r file, and using View 1.3.2 I 
got nice, full-screen presentation ... you use right-arrow to move 
to next slide ...

Pekr: NUBUNK is nice and has only 27 hits on Google. You should use 
it as some product name :))

ok, I've been experimenting with it a bit, and I must say, it's harder 
than I thought. I think I'll give up on it for now. too many things 
don't fit together...

I've got an area field and am using ^S to send text in my chat client. 

I clear the field with face/line-list: none, and face/text: copy 
""

but the cursor ends up not at the left edge.  How does one fix that?

Mmm. FIELD access functions do not take into account whether the 
face has the focus or not. I think they should check that and set 
the caret to the field's new text facet (if it is new).

anton, I read it (great stuff), but I currently have problems with 
which method to correctly group faces in the main pane (header, scroller 
and list), and get each face properly initalized. I know LAYOUT does 
this, but I can't use this with already made faces.

ok, haven't gotten very far yet, but http://hmkdesign.dk/rebol/list-view3.r

my attempt at a list view based on custom faces. more will come during 
the day... basically only fills out values and the sort buttons react 
visibly, but no sorting happens yet.

text filtering works now. by entering a string in the field, the 
string will be searched through all values in all columns and only 
display rows with the string in it. currently only searches all columns.

There should be at least three states for sort  [ascending, descending 
and unsorted]

Nice! Maybe it would be better to have situation similar to Lotus 
Notes grid? They show thin arrow, if the column is sortable (not 
all are). Then you can sort it up and down and third click deactivates 
sorting. It is kind of natural ...

back again.... fixed a bug where resize didn't work during filtering 
and incorrect amount of results when filtering and turning off sorting

the filter works on multiple strings and is case insensitive. the 
purpose is to let you very quickly search for things without resorting 
to regular expressions or wildcards, with as few keypunches as possible. 
try entering "shoe" first. then "shoe very". "shoevery" won't produce 
a result

new version 0.0.5 uploaded.

single selecting works now.
standard font made a bit smaller.

selecting requires the use of a new face called LIST-TEXT with a 
FEEL that allows for mouse over and single/double clicking in the 
list.
single-click action is stored as a block in LST-ACT
double-click action is stored as a block in DBL-LST-ACT

Demo can be found at http://hmkdesign.dk/rebol/list-view3.r

0.0.6 uploaded... minor bugfix to keep the selected persistent even 
when sorting and filtered.

I tried it, but there are problems with focusing. Keyboard nav, requires 
focusing on the right face, and when I try that, selecting goes haywire. 
It's the same with mousewheel. Suggestions are welcome.

unsort: please put this on the right-click. Cycling through unsorted 
isn't standard and doens't make sense.

Robert: I will look at right click unsorting.


Realtime filtering is really up to the field that provides the string 
and updates the list, not the list itself (more flexible that way). 
I've done it before, where realtime performance could be achieved 
with more than 30000 entries in the list, so it's not a problem to 
do.

pekr: I've tried focusing a single cell, and I can get key and mousewheel 
feedback, but selecting is ruined by it.

robert, BTW tri-state sorting can be turned off with the TRI-STATE-SORT 
variable. then it only switches between ascending and descending.

sorry for the wait... Version 0.0.8 uploaded

Changes:

      New: Functions to select next, previous, next page, previous page, 
      first and last. Uses FOLLOW.

      New: FOLLOW. Automatically follows the selected entry so it's always 
      in view. Requires FOLLOW? set to TRUE

      New: SCROLL-HERE. Scrolls automatically to the selected entry.
      Fix: Filter result was lost after resize.
      Fix: Sorting was lost after resize.
      Fix: Sorting indication is now persistent after resize.
      Fix: Dual state sorting was accidentally broken.
      New: Initial sorting can now be set before first view
      New: Right-click on header unsorts the list

Demo can be found at http://hmkdesign.dk/rebol/list-view3.r

Version 0.0.9 uploaded

Changes:

      New: GET-BLOCK retrieved the selected data as a block. Only works 
      with shift for now under multi and multi-row.

      New: Using the shift key, you can select multiple cells in multi 
      and multi-row mode.

      New: Five different select modes now: Single, multi, row, multi-row 
      and column.

      Fix: SCROLL-HERE only works with select modes 'single and 'row

      Fix: FOLLOW didn't work when selecting a row and then sorting


The different select modes might be interesting for a future spreadsheet 
face.

The list uses some standard values that are not correct right now, 
but I'll move those values into the correct place soon. If you for 
example set HDR-COLS to [], the header won't be shown.


The idea is that you have IN-COLS, which is based on the data you 
have in DATA. It's just a block of any words to tell each column 
apart. Then you will have OUT-COLS, which are the columns shown in 
the list view. The ordering of OUT-COLS determines the order that 
the columns are displayed in. HDR-COLS is for now a separate block, 
but it will be combined with OUT-COLS later. This ordering mechanism 
doesn't work yet, but it'll come in very soon.

Example of intended functionality:


in-cols: [person-id age sex height weight name address city country 
phone]
out-cols: [name age city]

Then you could reorder:

out-cols: [age city name]


And after using UPDATE, the list would update on the fly. DATA is 
not manipulated at all.

the existing hardware columns appear and not the new named ones, 
and they are added to the existing ones.

the existing hardcoded columns still appear.  Then a large gray box, 
and then the scoller.

the layout is for one row and it must be horizontal. you should also 
use the LIST-TEXT widget.

example:

layout/tight [across space 0 list-text 100 list-text 50]


but.. when I get this done right, it shouldn't be necessary to define 
the layout

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

and the width of the list is determined by what ?

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

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.

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

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 :)

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.

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 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.

Nope. One of my problems with VID and RebGUI is that the gfx are 
to tightly couple with the data representation. So a change in data 
representation implies a change in the gfx code.

what it can do right now is append, change, remove and insert rows. 
so this would be kind of an ACQUIRE function that calls a controller 
function that returns a value that can be inserted into DATA with 
insert-row or append-row?

with the point being, that you call your data source and insert the 
data into the list using a single function

Henrik, just looking at your list-view, and noticed a little thing 
that can be optimized:
b: []  insert tail insert tail b 1 2
b ;== [1 2]
b: []  insert insert tail b 1 2
b ;== [1 2]

I see you are successfully basing on FACE. Just a point about placement 
of custom facets; I would put all the facets that already exist in 
face at the top, then follow with all your custom ones. That way, 
someone who reads your code can see which is which. Furthermore, 
if by some chance the FACE definition ever changes (adding or removing 
a facet), it will be easier to see where the fault lies. Eg:
	list-view: face with [
		size: 500x300
		edge: make edge [...]
		
		; my custom facets

  colors: [...]  ; <--- this is the same name and I suppose the same 
  concept as used in VID 
				; (but it's still custom from list-view's point of view)
		select-modes: [single multi row multi-row column]
		; etc...
	]

What I meant to say about the face definition changing - say for 
instance a COLORS facet was added to FACE. Then, you would be unintentionally 
overriding the View system's one and probably introducing bugs, because 
the View system would expect it to be used a particular way and might 
render the face incorrectly given the data you've put into it. It 
might also change that data when you expect it to remain, etc etc.

anton:

First one: Alright. :-)

Second one: All that code will be thrown out and there will be a 
different demo later

Third one: You have a point. I'll look at the issue of sorting standard 
vs. custom facets.

version 0.0.14 uploaded

Changes:
      Fix: Documentation updates
      Fix: Multiple lists accidentally shared the LIST-SIZE value
      New: Custom layout block can now have multiple rows
        at the cost of horizontal resizability
      New: Now using ROW-FACE to store the custom layout block
      New: If HDR-COLS is set to a single word in a block,
        it will take the width of the list view.
      Fix: Code size optimization of navigation functions

      Info: The version between 0.0.12 and 0.0.14 is mysteriously missing... 
      :-)


The demo has been changed a bit to test custom layouts and multiple 
lists.

http://www.hmkdesign.dk/rebol/list-view.r
http://www.hmkdesign.dk/rebol/list-view.html

http://www.compkarori.com/reb/if you have IE and plugin.

is something supposed to happen when you select a user from the list? 
It reacts very slowly and sometime require multiple clicks before 
it responds

Just playing with it .. I've only got two list entries, and the top 
one responds each time.  It's the bottom one that is resistant.

the AGG part... right. the sort button uses AGG to display the sorting 
arrow. I could make that into an image and do some tests on an older 
View and see if it can run there...

I think I've gotten rid of the AGG dependency and that will be part 
of 0.0.15, but there are many other dependencies, so I don't know 
whether it'll work with the plugin.

list/update resets all the row heights, and scroller width

Henrik - can I set-row somehow? I mean I can 'get-row, but would 
like to set particular row hilighted and if not in view, it should 
be scrolled to have it in view ....

graham: 0 width columns seems to work fine in 0.0.14 here, but you 
may not need it once column filtering is properly implemented. then 
you determine which columns need to be displayed with OUT-COLS and 
in which order

And when I use /update, it restores the scroller width to the original 
and not my changed version.

and the header is HDR, list is LST, edit is EDT

when you click on a name in the list, ip and port information is 
given.

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

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

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 ....

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.

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

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 ...

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.