World: r3wp

Hang on, I'm just about to publish what I have, which is working. 
 In Tortoise, do I use the Import... menu option or SVN Checkout 
?

Isn't it commit ?

Checkout is to grab a copy of the repository.

So, I think you just select the files you want to commit to the repository 
and commit them.

the SVN book can be downloaded from http://svnbook.red-bean.com/

Sorry, yes, that's ok, I just read some Tortoise help.

I need to "check out", then "commit" changes, and tell others to 
"update".

So just now I committed my changes.

The build script and tour.r should be placed in the repository as 
well.

Yes, once you do an "SVN Checkout" the folders and files are displayed 
with a green tick. Editing a file causes it (and the folder it appears 
in) to be displayed with a red changed icon. Right clicking the root 
folder, RebGUI in my case, and selecting "SVN Commit" prompts for 
which changed scripts (and a comment) you wish to save back. Pretty 
straight forward once you've done it.

Yes, pretty straightforward after I read the help :) I just needed 
to be clear on the definitions of import/export/check out.

Ashley, I didn't make a history entry in rebgui-widgets.r for my 
changes, which I have commented next to the changes - would you prefer 
I did make a history entry ?

The change comment (which appears under Last Change when doing a 
"Browse Source") is the more important thing.

Not sure whether putting %tour.r up is a good thing as it has dependencies 
on images, dat files and / or dictionaries that don't really belong 
in SVN. I sort of wanted the repository to only contain code needed 
to produce %rebgui.r, while the %get-rebgui.r process delivers an 
"end-user" bundle with %tour.r, demos, etc ready to run (i.e. the 
repository is for developers/documentors only).


Likewise the build script has dependencies on prebol.r and prerebol.r 
so I'll need to extract the bits it uses before I put it up. Any 
ideas on what this script should be called? build.r, merge.r, make.r, 
compile.r, other?

build.r is good.

tour.r is needed for quick testing.

Unfortunately I don't see these changes fixing the problem, and it 
seems to introduce odd cursor movements when moving at boundaries 
( vertical).

It's not perfect, but is it not better than what we had before?

Could you restate the problem with the cursor as you saw it ?

note: the cursor confining code in area.r requires the patch to rebgui-widgets.r 
to work properly.

I've got the patch that sets the indent to 0.

Ok...

when the cursor reaches the bottom of the area, it suddenly then 
jumps up about a third of the way of the area on the same line.

ok let me try that.  Just using the scroller ? arrows or drag bar 
?

just the cursor key

down arrow ..

then as you continue to move down, you don't.. the screen moves up 
instead.

just down arrow, ok trying that.

well, combination of both

Ah yes, that's a separate problem.

but the original problem is also there.

curiously scrolling upwards is fine.

Cursor movement causes scrolling unnecessarily. It should only scroll 
when the cursor moves beyond the top or bottom borders.

exactly what I was about to say

oh! I just re-read your original problem...

Were you attempting to fix another problem? ;)

Hmm.. yes, kind of. But I see the problem as you first described 
- or at least a variant of it. In my case it always jumps to the 
bottom.

Needs an overhaul.

The area widget seems to be the most difficult to fix.

In mine, the cursor also jumps to the bottom of the area, but the 
text is not showing the bottom of the text.

Basically the problem is unnecessary scrolling of the text is occuring.

Yes, it's a simple algorithm for determining the scroller position 
I think. It needs to have a "window".

I'll see what I can do with this a bit later.

I have uploaded the "create-distribution.r" script Ashley posted. 
Sorry, for being that fast. But this one is mandatory otherwise the 
repository doesn't make any sense to me.

Why not add prerebol.r etc. to the reposititory as well? Into an 
own folder: distribution. Those files belong to a good repository 
as well. Normaly you even add the interpreter version this one works 
with.

prerebol.r ... not going to change it.

so makes not that much sense to include it?

I don't already have prerebol.r. It's not for the user to care which 
dependencies are  needed.

Exactly, that's why I would like to include it. If you check out 
the files and read the docs, you should be able to create the latest 
release with on click.

I hate those projects, where you have to collect for weeks any tools, 
patches etc.