World: r3wp

I'm changing my mind on not needing math and it not being a series. 
Sorry, if that seemed confusing.

Don't worry, it seems confusing only because i'm stupid :)

I just have a very clear example in MAKE-TICKS, where it would reduce 
about 10 hard to understand lines of code to 1 or 2 very clear lines 
of code.

Just to replace 10 lines of code in one usecase ? You're assuming 
Rebol should behave as your own or what ? :-)

I have encountered this problem before, where I just had to give 
up, because the problem became too complex to solve in a hurry. With 
the counter! datatype, it would not be a problem.

If it can be used to maintain large index on any data structure efficiently, 
it could be usefull. I'm waiting for your code

It'll be a while. Some things to think through first.

there is actually a built-in similarity to counter:

to-time 78
== 0:01:18

Just imagine any base instead of just !24.60.60

I don't understand the meaning of the tuple. Is that just an indentifier 
?

it's not a tuple. each number is a separate full integer.

This proposed datatype looks quite complex. Are you sure it's wise 
to add it to Rebol? Doesn't this just feed into lobbying for the 
user datatype? I might first implement your counter as mezzanine, 
solve the problem you have at hand, then maybe try to imagine how 
it could be specified using a user datatype...

yes, Anton, I agree it's complex, but I'm not sure it's any more 
complex than object! or port!. A mezzanine would only partially solve 
the problem, but it would allow similar behavior.

btw, i assume, it could be implemented as a scheme

it probably can

Where is the current MAKE-TICKS source, by the way?

Posting to you privately.

I was looking for it too. What is this function supposed to do?

Is it timer related?

no, it simply makes a shape block with tick lines for sliders, gradient 
bars and the rgb spectrum viewer. it will be used in more places 
than it currently is in use.

Yes, fairly recently we saw those slider demos with ruler marks on 
them.

.. which is where make-ticks was used.

essentially MAKE-TICKS [3 1 2] would draw something like:

| . . : . . | . . : . . |

Woooh, it means..., nothing to me :-)

your clock on the wall probably has something similar. (if it's an 
analog clock) :-)

Anton, the --do bug is known, cross-platform (not just Linux), and 
part of a half-dozen bugs that can be fixed by rewriting one function. 
It's the next R3 thing on my todo list, when I get the chance. I'm 
swamped with work at the moment.

:-) I thought it is Braile letters :-)

BrianH, cool, that it's next on your todo list - glad you've noticed.

User datatypes can't add new syntax.

http://rebol.hmkdesign.dk/files/r3/gui/106.png

Make-ticks was used in the 5 sliders at the top.

I've just been busy lately. Carl fixed/documented a lot of things 
in alpha 37 for me, but I'm in crunch time at work now. Soon.

Henrik, I advise not spending the energy lobbying for the new datatype. 
Just implement the "counter" algorithm as optimally as you can and 
move on.

Sorry, I think there's too much in this to pass it up. I think this 
would be very useful.

Ok, sliders, rulers, analog clocks... anything else?

Aside from the syntax, this could be done as a user-defined datatype. 
Or it could be done as an API.

Anywhere you want to count with varying base on multiple numbers 
and act on it. I've run into this numerous times.

BrianH, are there docs anywhere on user defined datatypes yet? Limitations?

Just discussions, but I know what the limitations are.

Henrik, I'll have to think more on it.

Steeve, where was your disk-block scheme source?

http://sites.google.com/site/rebolish/

thanks. maybe it's better to implement it as a scheme anyway.

I'm confused on your proposal as wel Henrik. A concrete example would 
really help, since it's a complex concept.

I think I'll wait. I've discovered some problems with the idea, which 
makes it less useful than I thought it would be.

There is new blog about small change to modules - http://www.rebol.net/r3blogs/0179.html

Eh Ammon ! how do you manage selection over several text gobs ?

I'm trying to do it currently, but i'm not sure to have the best 
design

I haven't gotten that far yet.  I recently had to rewrite my parser 
from the ground up, mostly due to the fact that NOT isn't implemented 
yet and I want to be able to handle unicode without too much trouble. 
 I think I'm going to have to handle a lot events like text selection 
by passing them through the text faces to the main scrollable area 
and let it handle them.  I expect I'll be rewriting the highlighting 
from the ground up.

i'm rewritting completly the key handler with my own cursor (a gob). 
I don't like the default handler

I like the design of the default handler.  =D  I'll need to modify 
or extend it before I'm through though.

too much ovverrides have to be done, redoing it from the scratch 
is simpler

You know that you can get the source from DevBase, right?