World: r3wp

looking at current description of Rebbrowser I am far from satisfied. 
I can already imagine how ugly the default interface is going to 
be. It seems to me like a concept without deeper thought. Buttons 
as forward, back, are the most flawed concept of the web, with very 
negative effect for the web apps ...

Why don't we just use Tortoise SVN? Some ppl know it from RebGUI 
project. Is SVN any less functional?

Not distributed

Why do we need distributed?

IMO rebrowse should be far away in our todo list. So much core capabilities 
was missing in the first R3 released.

When i read that for Carl, [parse] evolutions must be downsized the 
most as possible (while I believe this is one of the most important 
functions 

in Rebol), i have still some doubts how priorities are well defined.

It has been said by many rebolers all over the past, the Killer app 
should be an IDE (including code editor, screen designer and other 
wizards).

It the only manner to encourage new groups of developper in starting 
huge projets with Rebol.

Distributed version control is far superior over the classic schemes

SVN is hardly an upgrade over CVS

TortoiseSVN on Windows XP has been a nightmare: the more you checkou, 
the slower XP Explorer runs until you uninstall.

RapidSVN has worked flawlessly for anything that was not convenient 
on a command line

TortoiseSVN: Good name then. :-)

There are many advantages to using a distributed vcs, all variants 
on a theme. For example:

- You can track changes within your own code without submitting it 
until it is ready.

- It is easier to collaborate with other people without having to 
put your changes into the central repository.

This makes it easier to make large changes with the help of other 
people, and is why I suggested Mercurial over CVS.


The problem with all of this is that the main purpose of DevBase 
isn't source control, it is managing development workflow. No other 
vcs handles the workflow management function of DevBase. Without 
the workflow management Carl can't manage contributions.

Yesterday I came up with a way to change the DevBase model so that 
it would keep (and enhance) the workflow management functions and 
still get most of the benefits of a distributed vcs. Yes, it would 
depend on making the DevBase client a reblet run by the browser above, 
but that would be a bonus for R3 anyways.

Pekr, the navigational functions of web browsers are what makes the 
web work so well. You shouldn't misjudge them by the way that some 
badly designed web apps don't take them into account. We will still 
have the ability to create regular aplications in R3 when the browser 
model doesn't work for you.

Steeve, the reasons for minimizing the parse proposals are given 
in the proposal doc, but they boil down to these:

- Clean, simple and powerful is not only the REBOL way, but more 
efficient at runtime. It's the greatest strength of PARSE.

- PARSE is only one dialect of many in REBOL, and they are designed 
to be used together.

If anyone wants to discuss the source control and workflow management 
of the R3 project, mention it in the !DevBase group here.

BrianH: so which of parse proposals will make it into?

Don't know yet. I know my preferences - should I put an Editor's 
Note in the Priorities section?

Don't know - it makes sense, only if Carl takes the list of priorities 
seriously. Maybe he has his own opinion and will choose to implement 
according to his own priorities ...

I haven't edited the priorities section at all - I figured that was 
Carl's job. I should take a look at it. The trouble is, I don't know 
whether Carl has already started work or whether he has put it on 
hold in order to get a developers' release out ASAP.

Henrik claimed Carl is working on parser for one week or so :-) But 
maybe he just guessed?

I would prefer public relese, and continuous, incremental releases. 
But - can it happen without CVS?

Is there any conclusion to it? Will it be Mercurial? Hg? DevBase?

No conclusion yet, discussion continues in the DevBase groups.

Mercurial = Hg

If you don't want TortoiseXXX to slow down your explorer, turn off 
overlay icons. That is what slows them down. If you decide to turn 
them on, set the settings so it is only on for specific folders where 
you need the overlay icons.

New bug tracker is now online http://curecode.org/rebol3/

No screenshots for a bit. My server is going down for a few days.

(office is being repainted)

Carl wants to stick to devbase instead of using Hg

and he can't decide on whether to use a BBS or not.

We are using a BBS, just not a web-based one.

I mean now. We don't know yet whether we will be switching from the 
AltME BBS to another one.

The problem with AltME is not that it is not a BBS, but that it isn't 
a very good one for our purposes.

BBS's predate the web, so you can't just assume that a BBS would 
be web-based.

I recall zmodem protocols :)

acoustic coupled modems

good old fido net

Those were the days :)

Nice - screenshots there - http://www.rebol.net/wiki/GUI_Panels- 
they are nicely self-explanatory addition to source codes ...

I have deleted the REBOL Developer's Networking Group on Linkedin 
due to lack of participation.

Has anyone involved with VID3.4 development looked at MigLayout, 
the Java layout manager (http://www.miglaout.com), for inspiration? 
I've recently started using MigLayout with Groovy and this manager 
is great for intuitive programmatic control placement. I'm guessing 
that whomever is doing all the hard work in R3 has really thought 
about the problem and will provide smilar functionality and ease 
of use, but just in case, it might be worth a look.

The Java WebStart Swing demo on the page allows you to see the source 
as well as the individual constraints by right-clicking on a control.

are u sure for the link ?

add a 'y"

looking for screenshots...

I don't think there are screenshots - the live swing demo app is 
probably the best way to see/experience how the manager works - you 
don't need to install anything (you do need a Java VM, though)

Short VID3.4 status:

- Some extra formatting options in the DOC style.

- I added a numeric field today similar to the one on my old blog 
site for VID, except that this one took half a day to do instead 
of a week and was way easier to implement.

- Skin is changing appearance a bit, both to simplify and to extend 
its possibilities. This made it possible to build pixel-perfect text 
areas, lists and other combined faces, finally.

- Some bugs remain in the layout engine which make certain layouts 
look a little messy. Still not sure that MAX-SIZE is the right approach.

- Added CONTAINER to help produce aforementioned pixel perfect styles. 
As a bonus, such styles will have a common border, which we then 
can change in a simple way.

- Looked a bit at a CALENDAR style for a date picker, but decided 
that it is better to wait a bit with that to finish some other base 
styles first.

Any word on the updated alpha release timing yet?

I think we have moved into a time dilation field