AltME groups: search

Depend on what you mean by "debug version" and what debugging tools 
you're thinking about. My plan for Red is to deeply integrate it 
with the IDE, so that you'll be able to have advanced debugging capabilities, 
like step-by-step debugging. Such feature could maybe also be ported 
to the console version, so you'll be able to use it even without 
the IDE installed.


Also, I have thought the Red execution architecture to be as reflective 
as possible in order to try to support memory image loading/saving 
and stopping/resuming (think Smalltalk). It's very tricky (not sure 
we'll have it in the end), but if we can achieve it, you'll be able 
to get a snapshot of a running Red program on file, transfer it and 
resume it somewhere else....ideal for reproducing exact bugs occuring 
conditions. EDIT: the right expression for that is "Image-based persistence".


In the meantime, we already have some "debug mode": -d switch for 
Red and -g switch for Red/System (we'll probably adopt -d for both, 
-g will be reserved for gdb support). It's mainly intended for internal 
usage for now, the Red/System one can be useful to locate runtime 
errors in source code (usable, but still needs some fixes though).

Well I changed some text in this file, I changed it online in a black 
background box where I could not see my cursor nor the arrow pointer, 
so it sucked :( 

I thought it would be possible to edit the file offline but that 
is something to find out how to do next time ;)

Now I added a comment and it says I want to commit 182 changes into 
the master branch, which is not what I want, but Github says I want 
that. Including my comments it could be I typed in total 182 characters 
including the ones I deleted (?) but the 182 are the commits from 
the 0.3.0 branche I think. 

Me and my friend Github >:|

My own website is done with Cheyenne and the HTML dialect and is 
very easy for me to maintain: Makedoc files are rendered on the fly 
to each webpage. I can SSH to the server and edit files as I please 
and there is nearly zero HTML involved.


Granted, there is no blog or comments section, but is another example 
of how a small toolchain (one Cheyenne executable and a few script 
files) can be used to build a good website.

Oh forgot it, I can edit it directly.

If you are not sure of your english being good enough, well go ahead 
and just do edit the site and we will tell you what can be approved. 
Nothing held against you! Happy to see a little more life (or is 
it live) on the site. together we can do more than on our own. It 
takes just some initiative now and then.

No, that's another way to prove the point. You can just edit the 
time of your message. Do you want me to answer before the previous 
post? :-)

No, I can't edit previous messages. Maybe the troll can

They are very rough.  Feel free to redo or edit.

Hello MaxV: Congrats to your first R3GUI app! ;-) I have some questions/notes 
though:

1. Why one needs to download the two DLL files to get R3B running?? 
(not much user friendly IMO)


2. On your Blog page you say: "First of all there are some bugs, 
most of them depends on R3GUI, for example this one: https://github.com/angerangel/r3bazaar/issues/8"

I bet this is not related to R3GUI at all but more to your R3B build. 
The REQUEST-FILE works without any problems in our Saphirion build 
(and I think also the "official" Carl's build works well but haven't 
tried it). I tried to download and run your R3B binary and I can 
confirm the bug is related only to this version so it would be fair 
enough if you remove your R3GUI blaming from the blog entry if possible. 
I know R3GUi is not perfect so maybe you can just change the blame 
for some other which is really related to the framework. Or better 
feel free to ask any questions in RgGUI group here!

3. I've looked into the EDITOR function code and comparing to the 
R3 editor code (which is still twice as big as the R3GUI version 
- but I don't know if they match the features though) the R3GUI code 
looks much cleaner and abstracted that the R2 style even if you are 
not expereienced writing R3GUI apps. Some notes:


3.1 I'm curious why are you accessing the internal AREA style value 
like face/names/tb or aa/names/tb/state/value? Is that for some reason? 
Why you don't use the AREA directly like:
do-actor/style face 'on-key arg 'area
instead of
do-actor/style face/names/tb 'on-key arg 'text-box

or

write (to-file AA-INFO/OPTIONS/text-edit) get-face aa


write (to-file AA-INFO/OPTIONS/text-edit) aa/names/tb/state/value 


3.2 There is "classic" but anoying bug. If you open file requester 
and close it without selecting a file the editor errors out. (but 
you probably already noticed)


3.3 Would be great if you add keyboard shortcuts. It's easy to add 
them. See the layouts-15.r3 file in R3GUI Saphirion package as an 
example.


3.4 Maybe you could try to write your first R3GUI style - MENU It 
would be handy in the editor(and also in other apps) instead of the 
buttons on top.


Anyway, thanks for promoting R3 and R3GUI. I appreciate all your 
efforts!

#include %gfx-colors.r
#include %gfx-funcs.r

#include %view-funcs.r
#include %view-vid.r
#include %view-edit.r
#include %view-feel.r
#include %view-images.r
#include %view-styles.r
#include %view-request.r


;-- Must be done prior to loading anything that requires fonts on 
Linux.

layout [text "imanXwin kludge"] ;-throw this one away soon-- okay?

open-events

Same as yours only with prot-setnet.r added.

#include %gfx-colors.r
#include %gfx-funcs.r

#include %view-funcs.r
#include %view-vid.r
#include %view-edit.r
#include %view-feel.r
#include %view-images.r
#include %view-styles.r
#include %view-request.r

#include %prot-setnet.r


;-- Must be done prior to loading anything that requires fonts on 
Linux.

layout [text "imanXwin kludge"] ;-throw this one away soon-- okay?

open-events

no, I think I just shared it with the option to edit

Yes, it's obvius. Frankly it depends on what data you want to "share". 
I like google documents for storing files to edit when I travel ,not 
very important documents. For example: if you would plan a kamikaze 
attack or write a personal diary on your sexual orientation, I didn't 
suggest you to use google documents.

The best way for documentation is a wiki, where people can easily 
ragiter, log in and edit.

I think that something like http://en.wikibooks.org/wiki/REBOL_Programming
is the best thing. You may organize topics, correct, edit and add 
pages

Doc, for implementation details, you and a few others who know will 
have to provide the basic information. If there is cleanup and wordsmithing 
to be done, as long as others can edit it easily, I would leave that 
to someone else. Write the best doc you can, of course, but don't 
worry if it's not perfect. Your time should be spent doing things 
nobody else can do as well, using what you know, and what you know 
is planned.


For friendly user reference, do you have a style of docs you want 
to mimic, or an idea of how you want the doc data managed? e.g., 
do you want to use a wiki, so that infrastructure is all there?

The http://www.rebol.com/r3/docs/index.htmlwiki is not good, you 
can't register or edit.... :-(

MaxV: I think you can edit. I would definitely not replace it with 
the Github one, at least not for docs, which are quite extensive. 
IIRC, you had to be registered on R3 Chat, and then when you got 
some level of access, you could edit docs. There is more to the R3 
Chat, than might be seen from the mostly ugly surface ...

Sorry, but I don't think so. 

A good wiki is a wiki where is easy to register and edit. The one 
on the Rebol.com is not a good wiki.

People will register and use GitHub, so a wiki must be on GitHub. 

If youlike, you may have an "offical" wiki in Rebol, but a living 
wiki is the GitHub.

I can copy all rebol wiki on GitHub, you you want; but please reactivate 
the GitHub wiki!

Don't do the same errors of Rebol 2, where there was a wall between 
people and reboltech.

MaxV: "The http://www.rebol.com/r3/docs/index.htmlwiki is not good, 
you can't register or edit.... :-( " - that is actually not true. 
You *can* register if you want, just say so in here.

Do you want me to edit my answer to include the exporting stuff? 
I can't really do it in a comment since it would be in the same scale 
as the original answer.

Edit the answer would be better

And edit, because SO is much better for this kind of thing. And maybe 
provide a little context for why the function exists at all.

Crap, I hate not being able to edit what I just posted. Used to being 
sloppy on the SO chat. I see that I managed two typos above...

(Sorry, can't edit here) millions -> many tens of thousands

aren't -> are
I hate not being able to edit my posts.

I had to get rid of [catch] in my first edit. And [catch] is a bad 
idea for loops because it hides where the real error is being triggered.

I want to use Worldmaster dividers with some slight changes... SO, 
a way to choose Worldmaster dividers, then edit them for a custom 
one, would be nice

OK, so let me recap, you want to be able to re-edit something that 
was posted?

I like the edit/publish methodology inside the filesharing area

Actually, this looks like a WindowsXP or NTFS problem, not a problem 
of rebol at all, because I can "Run D:\Anton\Dev\Rebol\View\rebol.r...." 
and my text editor (associated with .R files) pops up to edit rebol.r

View 1.2.109 and 1.2.110   no longer have CTX-EDIT, where did that 
code go ?

anton: ctx-viewtop/ctx-edit. but, this will be fixed.

Ryan Cole had done hex-edit.r  found on my hard drive...wasn't in 
Library when I searched on hex and editor

aha, it was from IOS Developer/Users/Ryan-Cole/Utilities folder...where 
hex-edit.r was from...rather than the library.

I thought it might be version related, but one of the VID versions 
I have exhibit the problem:
** Script Error: Cannot use multiply on none! value
** Where: edit-text
** Near: 2 * face/edge/size

http://www.rebol.org/cgi-bin/cgiwrap/rebol/discussion.r?script=calendar.r

How easy is it to edit your scripts after they have been submitted? 
Do you feel comfortable adding the appropriate needs header where 
needed, provided you know enough about REBOL versions to determine? 
Can you flag the appropriate files as problematic?

Thanks Graham.

Paging for AltME archive.....We only put the basics in place. It 
is certainly improvable.

Meanwhile, you can make great leaps if you are happy to edit the 
end of the URL ....

... eg 16273 is the post number for group 453 of world R3WP. Change 
the 16273 to move quickly:
http://www.rebol.org/aga-display-posts.r?post=r3wp453x16273

Anyone can add any tag to scripts....Click the [edit tags] link when 
logged on and looking at a script.
   http://www.rebol.org/boiler.r?display=st-edit-tags-help

If you add a new script, yoy can add a (say)
  library: [r3: 'tested]
tag, and that will be picked up and used in the tag index.


The problem with updating the tags in the headers of existing scripts 
is that it is long-winded: you need to physically upload a new version.

Better just to retag via the [edit tags] link.

Just lookin at the source......We do edit line ending to try to get 
them consistent.
Perhaps consistent, but wrong!

You should be good now......but using the updater to download 169+ 
scripts wlll trigger the problem again.

(Another quick fix is to edit the script to put a wait 10 between 
each read of the library)

enable-fields: func [pane][

    foreach face pane [if face/style = 'field [face/feel: ctx-text/edit]]
]
disable-fields: func [pane][
    unfocus
    foreach face pane [if face/style = 'field [face/feel: none]]
]
view lay: layout [
    field field field guide
    btn "Enable" [enable-fields lay/pane] return
    btn "Disable" [disable-fields lay/pane]
]

the flag is set by each function that modified the series. It's in 
ctx-text (insert-char, edit-text for the most).

Dont know, I figured it out largely by examining the ctx-edit object 
(view editor)

Thanks for all those suggestions.   I was out for quite a while and 
am very happy of all those remarks. It will help orient my trials&errs. 
 About  objects, dynamic versus static, If I understand it, in Rebol 
it is static?  I never had to use them except to encapsulate the 
whole of an app.  Is there a trick to mimick something dynamic to 
hold changing values?  Maybee a copied block is enough?  I wonder 
because I regularly try to add code to a bibliographic database, 
a kind of a variation on bibtex (never ended, allways in progress), 
And I am not too far from aiming the storage mechanism and wonder 
what I should use to hold something like from 5 to 10 thousand references 
(my actual need is 3.5K)  I used endnotes in the past, but dreamed 
about my own.  It is a lot of work (more than I expected as it is 
my first app).   Up to now I think I will use simply name-value pairs, 
like Carl's cardex.  This kind of data is more like a ragged array, 
the fields and their numbers allways vary, and I may amend their 
list with time.  The idea of using an object would be nice but need 
something where I may add or retract variable names and change their 
values.  By the way, I thank Volker for his edit-tools, that may 
help to add a writing pad.  And his double slider is refreshingly 
new for such and old paradigm as an editor.

Hello everyone,

I have an EditME me that I'm using to manage a project this summer. 
I would like to use Rebol to logon to my wiki, edit some pages and 
attach files to pages.

Are their any code exemples that I could use to understand how to 
go about this. I need to be able to fill in forms and send them in 
to my wiki. 
many thanks

Alternatively. try to upload without a Library header.....One'll 
get added, and you can then edit it.


[It'd be good to get one more script in the Library. Right now we 
have 666, and that's an iconic number for some people :-)]

One of the goals with the MakeDoc format is, that it's possible to 
easily read with a normal text window, and some people may want to 
edit it with a normal text editor and write the formatting chars 
themselves. XML is not suited for that. XML also has the same start- 
and end-tag problem (that I mentioned above) as HTML.

Ah..  I was just ready to give my user feedback on that. :) No matter, 
I still think the install was pretty easy. The only thing was not 
knowing how to edit menu.lst (I found AEDIT, but that was not obvious, 
eg. I tried "ed" "edit" etc first.) But you're going to fix the whole 
issue anyway.

I give up, I will edit sqlite driver and disable loging at all ....

I'll have a blog running on peoplecards.ca...and it's blog.r based. 
 I'm just a little confused by 

blog-active: true/false  and the [edit] sequence doesn't seem quite 
right yet. 

This code snippet doesn't seem to redisplay things properly...
	if cgi/save [
		show-blog save-blog cgi/save cgi/date cgi/title cgi/text
	]

Graham,have you tried Mandriva ? I just installed VMPlayer on it 
but still need to edit a pl config to get it to work Altme/View install 
fine on the x386 version but the 64 bit version does not

sorry, you mean edit the mime type configuration file in gnome?

Most of what I do could in theory be done from the command line (I 
don't edit images much), but the gain or loss in productivity varies.

well, but as for 3) if I only edit my script, overwrite it, the permission 
(after copying it back to ftp) will be preserved. But if I add script, 
it has insufficient permission once again ...

system/options/cgi/remote-addr is not registered, apparently, so 
I can't edit pages.

Found a tool for css and firefox. Opens an editor in the sidebar 
with css for the main-page. and updates main-page on the fly on edit. 
https://addons.update.mozilla.org/extensions/moreinfo.php?application=firefox&version=1.0&os=MacOSX&category=DeveloperTools&numpg=10&id=179>EditCSS

mod_rewrite? Never used something like that ... so shold I edit httpd.conf?

Definitions of widget on the Web:


    A standardized on-screen representation of a control that may be 
    manipulated by the user. Scroll bars, buttons, and text boxes are 
    all examples of widgets.
    www.redhat.com/docs/glossary/


    A set of clickable, graphical element in a user interface. This includes 
    buttons, radios, checkboxes, and scroll bars. Widgets vary in appearance 
    and dimension from platform to platform.
    www.gerbilbox.com/newzilla/glossary.php


    n. 1. A meta-thing. Used to stand for a real object in didactic examples 
    (especially database tutorials). Legend has it that the original 
    widgets were holders for buggy whips. "But suppose the parts list 
    for a widget has 52 entries...." 2. [poss. evoking `window gadget'] 
    A user interface object in {X} graphical user interfaces.

    www.worldwideschool.org/library/books/tech/computers/TheHackersDictionaryofComputerJargon/chap55.html


    (n.) In a window system, a reusable user interface component such 
    as a button, scrollbar, control area, text edit area, and so on. 
    When an X Toolkit Intrinsics function creates a widget, it is returned 
    as an opaque data handle and assigned to a variable called a widget 
    identifier. See also OLIT.
    docs.sun.com/db/doc/805-4368/6j450e610


    – A graphical user interface programming object (button, scrollbar, 
    radio button, etc.) for the X Window System. (Also, see X Window 
    System.)
    www.newtolinux.org.uk/glossary.shtml

First stab at a list of required base widgets

	area
	bar
	box
	button
	check
	droplist - text display + drop-down list
	editlist - edit box + drop-down list
	field
	groupbox - encloses a group of gadgets in a titled border
	icon
	image
	list – single column
	listview – multi-column
	progress
	radio
	scrollbar

 spliter – a “spliter window” which affects the width / height and 
 position of other gadgets
	tab -  arranges multiple gadgets into logical groups
	text
	slider
	treeview

 updown – scrollbar minus the bar (used with a field to increment 
 / decrement numbers, etc)
	menu
	popup-menu - context menu
	status – status bar with one or more “segments”
	toolbar


The aim is to have as few widgets as neccessary to build the majority 
of required GUI's. Take a look at the applications you use on a day 
to day basis, what widgets do they use? Are they in the list above? 
How are they named? Are there any widgets in the above list we can 
do without? (not that *someone* won't need it, just that it isn't 
common enough to be part of the base widget set).

for droplist the edit field must have an auto completion according 
to entries in the dropped list

Latest release available at: http://www.dobeash.com/files/RebGUI-015.zip

Highlights include:

	- New LED widget
	- Tweaked check, splitter and tab-panel widgets
	- Basic edit feel added to area and field widgets
	- Resizing is now fully recursive
	- Added a light-weight request-file function for Win32/SDK use
	- Numerous minor improvements and fixes
	- Documentation update (the Display User's Guide in particular)

Less than a dozen widgets to go!

	droplist	edit box / text display + drop-down list
	list		single column
	listview	multi-column
	radio
	treeview

 updown	scrollbar minus the bar (used with a field to increment / 
 decrement numbers, etc)
	menu
	popup-menu	context menu
	status		status bar with one or more “segments”


If you're working on any of these, drop a message here so we don't 
double up on efforts. ;)

Pekr: the edit feel is pretty basic at the moment (doesn't support 
highlighting or cut / paste). The Ctrl+BackSpace and Ctrl+Del are 
"delete to end" and "delete to beginning" respectively, which almost 
all editors support without the need for highlighting ... now the 
key mappings are another issue. ;)

Graham: You need to add the following to %tour.r:

	#include %gfx-colors.r
	#include %request-file.r
	#include %gui.r
	#include %widgets.r
	#include %display.r


and comment out the "do %gui.r" in %tour.r and the "do %widgets.r" 
and "do %display.r" lines in %gui.r. I'll make this less painful 
in the next release.


Brian: See Sunanda's response or just comment out the redefine of 
'show in %gui.r

Latest build available at: http://www.dobeash.com/files/RebGUI-018.zip

Highlights include:

	- New pwd-field widget
	- Updated tab-panel & radio-group widgets
	- Timer widget removed
	- Added Ctrl+Left & Ctrl+Right (word left / right) to edit feel
	- Display User's Guide updated to reflect previous changes
	- Menu widget and tabbing deferred until 0.1.9


Note that face edge, font, para and feel now default to none. Use 
default-* objects if your widgets need these attributes (this brings 
these attributes in line with the RebGUI philosophy of "absent unless 
specified"; and removes all the attribute: none assignments).

that's why I have made logging in obligatory to edit pages

sunanda: they are not meant to be published on my site, I simply 
wanted to approve them here before handing them to Carl (which I 
actually have, but he hasn't responded other than "Cool!", but hasn't 
done anything :-)).


I was thinking about a very simple extension to webserv.r which simply 
submits a form to a modified makedoc2.r processor, which generates 
a page, sectioned so that you can edit small parts of it.

Is that fast enough to edit video?

Even a slow computer can edit video just fine.  It depends on what 
medium you work on.  For example, if work in Raw, everything is really 
fast.  When you finally move to a format (AVI, .MOV, .MPG, etc.) 
that is when stuff takes a LONG time.  You need lots of video space.

I would like to have answered:


1) what technique to use for "timestamping" - do we continue with 
timestamps against one central time, or do we use hashes, or sequencing 
numbers, or mixture of mentioned techniqueues? We might look how 
others do it ...


2) better support for possible conflicts - imagine following scenario 
- you have some reblet, e.g. Contacts - one person starts editing 
it, then another person starts editing it too. First one syncs (saves 
changes), then second one does the same - changes of first ones are 
lost. How to aproach this - introduce some kind of resources locking? 
(not real locking, but we are message based, so could be queued)


It could work as follows - person 1 wants to edit some record. Edit 
button posts request-for-lock. Lock is assigned. I other person tries 
to edit, it will not obtain lock. We could even introduce protocol 
level support, so that the person is informed, who has the lock, 
and how long. The trouble usually comes, when person goes off-line 
after the edit started - we need to remove dead-locks, so by default, 
I would lock for 20 minutes e.g. and the lock would have to be renewed, 
if person 1 wants to work longer with the given document ...


another scenario is, when you actually start editing something which 
might require locking, but you start already being off-line. We could 
create lock-request, just not synced yet. Once you go on-line, you 
simply check seqno, if the lock is possible, and the given record 
not modified. But what if it was modified in the meantime? e.g. you 
might be working with stock system and someone else in the office 
sells few units, for which you may start writing offer for to another 
customer. Tough scenario - would like to know your opinion. Maybe 
some things simply need to be done on-line only?


3) I needed small file-sync scenario - could use IOS, but IOS can't 
sync and "forget". Simply idea is to have different kind of syncing 
techniques, so e.g. for file transfer you have dir to sync, if correctly 
synced, log it, forget it, delete it on client and or server (or 
not, it depends)


as for IOS, local storage could be encrypted (or not), imported into 
RebDB (no single better solution so far introduced for rebol), sync-per-record 
or record-set could remain (record=document). RebDB on Serve would 
speed things up significantly too ...


another possibility is to think outside the IOS terms, in more general 
way - simply thinking about world of objects, being in various states, 
with various life-time around internet and on-line or off-line devices. 
I think that maybe we could find some simpler solution than SyncML 
and the likes ...


another point - such techniques should be transport independent, 
so I would not like to hear that it needs this or that ;-)

So, anyone?

but at least you could use Ultra edit on the mac to code it  ;-)

I also want to save the data so I can edit it and fill out the form 
again later.

openoffice 2.0 has a free XForms implementation. it can save PDF's 
like this so you can edit them like a real form. I haven't worked 
with it deeply, but I think you can save data from them in a database.

edit them like a real form
 => edit them like a real form in adobe reader

Yes.  I posted the complete contents of my edit buffer (Word), and 
deleted it and restarted.  Not that anything was important, but it 
may have read oddly (even for my posts).

 wtcSQLite allows you to add/edit/delete indexes, fields, tables, 
 triggers, views, data, and manage multiple database aliases without 
 knowing any SQL at all. 
http://www.zend.com/php5/contest/contest.php?id=74&single=1

(it's phpmyadmin for sqlite)

What am I doing wrong here:

rebol []
do %sqlite.r
do %rebgui.r

if not exists? %id.txt [write %id.txt 1]

db: %indodex.db
either not exists? db [
    CONNECT/create/flat/direct/format db

    SQL "create table base (id, Nama, Alamat, Telefon, Handfon, Fax, 
    Email, Tgl_Nikah, Nota)"

    SQL "create table birthdays (id, Nama, Jenis, Hubungan, Tgl_Lahir, 
    Agama, Nota)"
][
    CONNECT/flat/direct/format db
]
unless value? 'ctx-rebgui [
	either exists? %rebgui-ctx.r [do %rebgui-ctx.r] [do %rebgui.r]
]
set-colors
tab-size: 120x55
fonts: reduce [font-sans-serif font-fixed font-serif "verdana"]
do show-cc: make function! [] [
display "IndoDex Ver. 1.0.1" [
    tab-panel #HW data [
        "Add" [

            label "Title:" priority: drop-list 30 #W "Pak" data ["Pak" "Ibu" 
            "Sdr." "Sdri." "Drs." "Dr." "Tuan" "Nyonya"] 20x5
            return
            label "Nama:" nama: field 
            return
            label "Alamat:" alamat: area 50x30
            return
            label "Telefon" telefon: field
            return
            label "Handfon" handfon: field
            return
            label "Fax:" fax: field
            return
            label "E-Mail:" email: field
            return
            label "Nota:" nota: area 50x30
            return
            button "Save" [
                (id: to-integer read %id.txt)

                SQL/flat/direct {insert into base values (id, Nama, Alamat, Telefon, 
                Handfon, Fax, Email, Tgl_Nikah, Nota)}
                (write %id.txt id)
                show-text ex-status "Saved"]
        ]
        "Edit" [
            
	]
	"Search" [
	]
    ]
]
]
do-events

Sure, if you want. I'll edit the security entry I already put there.

If we could configure plug-in some-way, those behind proxy would 
at least normally edit their user.r and do some tweakings, not so 
with proxy ....

Have you noted there are two tags, and you have to edit both? or 
does not eventhe install-page work?

.r files are treated as CGI script by default in Cheyenne. To change 
that, you have to edit the httpd.cfg file and change the following 
line :

what we can do is manage code and edit the code on the fly... which 
is what I will be doing as my first liquidator module.

elixir, itself is about 90% done.  file i/o is done, GUI framework 
finiwhed,  CLI 100% operational, all I needed was to finish the data 
query language to be able to create/list/edit/delete stuff in the 
data cloud more easily...

I put 0% of time on site layout, once its done.  I just edit content 
and make the page.  its like editing make doc, but in html format... 
also, the tags are not standard html type tags  they nest directely 
 <p! text <b! is bold <i! and italic>>>

easier to edit, since I don't have to track the damned end tag all 
the time... this being said, normal html is still valid within the 
files... so its a 1/2 way between html and rebol code.

they are all part of the standard apache distro... but you have so 
edit the config file to enable them

I just intalled the windows version, it works very well. I just had 
to edit the stunnel.conf file to uncomment the HTTPS config options.

Then Start => Programs => STunnel => Edit stunnel.conf : uncomment 
the [https] section, then save it.

i think i will be bringing my camera, and i can shoot some videos, 
not sure i'll have the time to edit and publish them immediately 
though. i hope the organization didn't forget about creating videos 
:)

just edit the tileset :)

Hi Doc,    Very nice. And fast!        From first look here are some 
questions:

1. Is it possible that an option is don't allow comment editting 
or delete since this is the full audit path for resolution?

2. Can it add journal items to record who changed what when they 
use "Edit Ticket"?

Hi MikeL, thanks for your feedback.


1: Only the author of a comment can edit/delete its comment, no one 
else can. See http://softinnov.org:8000/curecode/ticket.rsp?id=10005#comments


2: Definitely a useful feature that I would like to add asap. (added 
as a feature request in CureCode project).

Not even that. It would be sufficient to do two things:

- Do a server-side redirect to a get page when you go into edit mode 
on a ticket or comment update.

- If doing a post and the session has timed out, create a new session 
and save the data to it temporarily and take the person to a login 
page. After the relogin, take them back to the page with their edits 
prefilled in. Then let them save (or perhaps save on the way).

Getting the redirect loop on edit bug again. Clicking on a ticket 
from the View Tickets list takes me to:
- http://curecode.org/rebol3/edit-ticket.rsp?id=607&cursor=1
which takes me to

- http://curecode.org/rebol3/set-project.rsp?prj-id=2&ref=edit-ticket.rsp%3Fid%3D607%26cursor%3D1
and back again, endlessly.

I entered a bug report into the Rebol3 tracker and it got duplicated 
- #645 & #646. I don't think I clicked "submit ticket" twice though 
I may have accidentally double-clicked on it.


I tried to delete #645 and followed the sequence "edit ticket"->"delete 
ticket"->"confirm ticket" but it wasn't deleted.

BrianH, on 21-Jan 11:16 PM you said : "Do a server-side redirect 
to a get page when you go into edit mode on a ticket or comment update."


I'm not sure to understand the "server-side redirect to a get page" 
part. When you click on a ticket ID or comment [Edit] button, you 
enter in edit mode using a GET request. What would a redirect improve 
here? Is it related to the browser Back button and client cache management?

Currently the changelog for the new version is :

	o FEAT: "User" column added to tickets list page.
	o FEAT: Search text feature extended to comments.	
	o FIX:	"By Submitter" filter now working correctly.	
	o LOOK: Textarea edit fields enlarged to maximum width.

Nick, I'm throwing my questions into a wiki, which will eventually 
become the Wiki to tell people everything they need to know to jump 
into the DevCon.

This is a public syndicated version of the Wiki


https://www.qtask.com/qwiki.cgi?mode=previewSynd&uuid=89Q6MQ8PFN5YU27HNSV87LWB22QT


If you want to edit the Wiki, you simply need to be a member of the 
REBOL SIG project in Qtask.


If anyone wants in, just shoot me a message with the email address 
you want me to use.  There are already about 70+ people in the project.


Here is the link to the editable Wiki  https://www.qtask.com/quilt.fcgi#qwiki-8382?project=198

We really need a place we can send everyone.  I'm going to vote a 
public Wiki, but if no one steps forward with that...then I will 
simply take the art I made, make a Wik on Qtask out of that, and 
sydicate it (make it public).

Anyone in the REBOL DevCon project in Qtask can edit it...