AltME groups: search

Of course, I prefer REBOL data, with makedoc being my preferred markup 
format. I don't know if Carl's WIP wiki is worth asking about, or 
another wiki engine or site would not lock us in too much. Some of 
us did some work on a wikimedia interface for R3 docs, which didn't 
get far. And I have a wikidot site we can play with if people want.

In any case, you might find my attempts at a CMake-based build useful, 
as I explicitly list the `make prep` scripts and their dependencies 
there:

https://github.com/earl/r3/blob/wip-cmake/CMakeLists.txt#L109

WIP

Well, WIP wiki is imo OK, that's all I say. You are wrong if you 
think there are no editors, etc. Those are just higher rank users 
of R3 Chat IIRC. We imo need some consensus on this - do we move 
everything to Github? What about prebuilt products, marketing, etc.? 
What remains on REBOL.com then?

I'd really like to see more about MML Ashley.
 ... http://www.dobeash.com/MML/mml.html


Note that this is still a WIP (it's evolving as my site requirements 
evolve).

wip ;)  http://rebol.mustard.co.nz/mockup-v1.pngdone with draw 
and a little bit of R3

WIP on a tiff viewer for r2 http://www.digicamsoft.com/cgi-bin/rebelBB.cgi?thread=%3C19Feb2010232555055824100%3E

sometimes doubling the number of elements makes the refresh 10 times 
slower, sometimes, there is no noticeable difference. I'm still trying 
to find the best way to render things.  my guess is the GC is constantly 
interfering since the draw blocks have to be rebuilt over and over. 
 which is still my main issue wrt using draw in R2 and even R3.


if i forego of rendering, there seems to be no noticeable effect 
of processing the collisions, so I hope, its not just "a trick of 
the light" and that my current wip (handling collisions between many 
polys) is going to work well.

I prefer R3 Chat (and WIP wiki) Carl did, because there is user ranking, 
and only users of certain ranking can do changes. Maybe it can be 
done with the MediaWiki too, I don't know ...

Pekr: It's all explained in http://www.dobeash.com/it/rebgui/locale.html


Brock: radio-group does this already (set of mutually exclusive choices) 
and I was contemplating a check-group widget which uses the data 
attribute to store a block containing state information for each 
check-box in the group.


shadwolf: menu and tabbing are still WIP. The arrow widget is integrated 
into %widgets.r, I just ran out of room (> 1024 pixel width) with 
the current %tour.r. Once the scroller and spinner widgets are complete 
I'll redo %tour.r breaking it down into sub-widget categories (the 
real solution is to enhance the tab-panel widget but one thing at 
a time).

do you have to be on the tab panel you are replacing to use tab-panel/replace-tab?
 ... No, see the following test case:

	t: tab-panel data [
		"A" [field]
		"B" [field]
	]
	button [t/replace-tab 2 [button]]

Click the button then tab "B".

... Was this related to the new look?

 ... yes, the new look is an extensive WIP that "breaks" build 112.

Are the function keys accessible under Linux?
 ... http://www.dobeash.com/RebGUI/user-guide.html#section-4.4

The tabing changes are still a WIP, it'll take a couple of builds 
to get 100% ... but at least I can grok it now!

RebGUI v2 RC1 (build 200) uploaded to SVN

Focus of this version has been:
	* Make it look good (color scheme based on Windows 7)

 * Take into account OS sensibilities (different corner rounding, 
 window colors, system fonts)

 * Get rid of the cruft (removal of little-used widgets and options)
	* Improve tabbing
	* Make it load and run faster



Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?



Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color



Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font



Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]


WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

hmm, SVN says:

RebGUI v2 RC1

Added
	icon
	get-fonts
	confirm
	request
	request-calc
	requesst-verify
	rebface/old-color
	rebface/over?

Reimplemented
	arrow
	calendar
	drop-list
	password
	slider
	tool-bar
	set-state
	set-color

Enhanced
	chat
	edit-list
	spinner
	table
	request-char
	request-font

Removed
	question
	request-ui
	pie-chart
	symbol
	options [info no-click]
	options [arrow options]

WIP
	A disable/enable function and layout option
	Rewrite of led widget
	Rewrite of tree widget

The "tab out of list" and "rate" bug fixes are still WIP.

why tree-view node icons (arrows) were removed?

 ... tree-view was reimplemented to face-iterator ... havn't got around 
 to adding arrows/icons for the nodes yet
... dobeash.com is still down

 ... getting the domain transferred is taking much longer than expected, 
 hope to have it back up within 3-5 days
... stops working with buid 208 ...

 thanks marek, most of those issues are due to the major tabbing changes 
 that occurred in 208. Fixing them is still a WIP.

hum I get an R3 error when I save the document on wip

Yes, unit tests are very good for pure functionality (functions that 
don't affect the state) ... this is strictly for webapps, webapps 
is basically based on some state so unit test don't make sense except 
for the algoritmic part of webapp ... you can see sometning about 
this testing engine here .. http://itmmetelko.com/blog/2009/04/24/a-peek-into-wip-trail-testing-engine/

As I wrap up WIP3 for the current website redo, it seems a bit odd 
that each time, the WIP system gets smaller and better.

This may be of interest to those of you who need to [quickly] create 
hexagonal game maps ... but don't want to master a complex CAD program. 
My QAD attempt at a declarative solution yields results like this:

	http://dl.dropbox.com/u/8269768/ACW.png

The prototype code can be found here:

	http://dl.dropbox.com/u/8269768/MapMaker.zip


No documentation, but the sample map file (ACW.r) shows how the PNG 
above was generated. Note you can drag the map around by click-moving 
it. Map, game and software still WIP.

I doubt that would save him time - all of rebol.com is generated 
from scripts, mostly WIP in the new site.

I realize the GUI is still a WIP ... but is the underlying [native] 
gob! system settled? (i.e. is it likely that the details of http://www.rebol.net/wiki/GOB
will change?).

WIP wiki is better - only ranked persons can contribute ....

Carl, the wiki should be downgraded to simply a repository of documents 
to be collected later for permanent storage in the WIP wiki.

hum ..; can i crack the wip too ? it seems fun !!!

therefore as you have the wip in the hand robert i think richtext 
dialect will go the way of a realtime wisiwyg  system able to be 
applyed over all the wigets we want... (like draw basically)

Does this still apply to the WIP ? http://www.rebol.com/r3/docs/gui/gui.html

It's possible that these are done with Carl's WIP document generator. 
I'm not sure if that works with MDP.

we want to ask Carl to free the WIP script.

it doesn't help, when we don't have the WIP script to parse the text.

Oldes, you have to reload, for new stuff to appear on the website. 
I noticed also some docs are released (resizing). What about publishing 
even doc, which is in WIP format included in the archive? Well, but 
that would probably mean maintaining two versions - MDP one, plus 
WIP for rebol.com ...

no, I don't ... just the general doc for the WIP, plus your resizing 
docs ...

Just making few notes:

1. we don't push anyone to use/accept R3GUI from RMA


2. anyone who is missing "Carl's GUI" can download it at http://www.rebol.com/r3/gui.r
and happily use and enhance it. (It really works much better than 
RMA version...especially with A111 :-))


3. Having 'good looking' demo doesn't mean anything when the system 
cannot be used in real application. (That was the first thing we 
realized when checking the "Carl's GUI" and that's why we continued 
to improve our own version based on Carl's design)

4. It has been said by defferent RMA-members:

-this project is still in 'alpha', we are working frequently on it 
to be better
-we are publishing/sharing our work-in-progress code
-we invite any good contribution to the wip code

So far the major reaction to our effort is none,negative or contra-productive 
here even from some people who have experiences with mangement of 
larger projects(*sigh*). I don't understand why.

This has of course nothing to do with constructive critics which 
we hear, discuss and think about every useful comment (even if it 
is not accepted in the end). Unfortunately we could count 'useful 
comments' in this group on fingers on both hands max.


5. even with all the negative energy that is 'pumped' on us from 
Rebol3 we will continue with releasing our work and inform people 
here about the progress etc.

otoh I found it out myself ... just clicking small WIP wiki icons, 
which are publicly available :-)

Added it as a codec so you can access it:

>> ml: decode 'markup read http://www.rebol.com
>> foreach tag ml [probe tag]
<!doctype html>
^/
<html>
<head>
^/
<meta name="generator" content="REBOL WIP Wiki"/>
^/
<meta name="date" content="10-Aug-2010/12:18:33-7:00"/>
^/
<meta name="rebol-version" content="2.100.97.4.2"/>
^/

<meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/>

my webapps (latest one is wip timetracking) code is getting cleaner 
and shows more benefits with every itteration. And all in direction 
only rebol-like langs (not even lisps) can provide AFAIK. And ages 
away from classical / python / ruby code.