World: r3wp

others do both and don't get the time to release  them  ;-)

so you're looking for post mortem fame?

isn't that when things get valued to millions  ;-)

pesos

notice that I've recently released a few things quickly and this 
thread is just going to continue  :-)

thread=trend

Wow, Christian took my advice, and redo ODBC extension into .DLL 
form, and now it uses ports! That is cool. Should be imo reported 
to rebolweek :-) 

http://www.diefettenjahresindvorbei.de/odbc/odbc-docs.html

And I've taken your advice to publish a .dll, too. Somestimes, yeah, 
sometimes, I take advice ...

:-) thanks anyway!

funny, it didn't register in my brain that the ODBC driver was for 
R3 and that it meant I could actually use it for work in a little 
while.. hehehe.   thanks !

Just posted a bunch of new CC tickets that explain a lot of the new 
or changed features in A108 and A109.
- New features in A108: 1682 1683 1684 1687 1690 1691 1692 1693

- New features in A108 that don't work yet: 1685 1686 (because of 
1685) 1688 1689 1696 (because of 1697)

- New features for A109 that I've already written: 1680 1681 1685 
1689 1694 1695 1696 (workaround)

(!REBOL3 Modules is probably a better place to discuss those.)

BrianH: when you finish protect/unprotect etc. security tickets? 
Shouldn't that be a priority ... at some point? :-)

Just a little tidbit I thought might be good for others still resisting 
the dark side of the force (R3 :-)


I'm at a point where I'm 50:50 in my time spend on R2 and R3 overall. 
which is a nice observation.

ATM, I much prefer R3 for many reasons.

-binding control and dynamic code building is soooo much better.
-embeded modules
-extensions which can (at last) almost do anything with REBOL.

-being able to fix/understand some limitations myself by "looking 
under the hood".

-it really is much better designed, scalable, fast, consistent and 
more.

why is R3 the dark-side?
-it constantly tempts you, 

-promises power (which it ultimately delivers, after kicking you 
in the nuts a few times), 

-allows much easier access to evil dlls (dark lawless libraries) 
than R2, 

-can be a lot more harsh finding your errors, but then removes guilt 
by disarming them 
-some unexpected issues still make it highly temperamental. 
-it will actually KILL your app with mush less discrimination 

-DOS shell makes it a trial by pain experience (and no, making its 
bg color white doesn't changes this ;-)

And this had to be bold why exactly?

damn, where is my BAN button? :-)

:)

I forgive max for his last bullet point: "DOS shell makes it a trial 
by pain experience (and no, making its bg color white doesn't changes 
this ;-) " - hehe, made my day :-)

if with there where an easier way to indicate discussion threads 
"beginings"  just did that so it does stand out from all the other 
discussions of which it really isn't related.

maybe you should use color next time ... e.g. pink one - in love 
:-)

I really love my R3 :-)

You can already build a better shell with the hostkit :) Until someone 
actually gets annoyed enough to do this, it's probably easiest to 
just install a "proper" shell, maybe along with rlwrap.

hehehe

one thing I would really like (now that its possible) is to have 
context/block browsing in the CLI .

this would make the console 50% more usefull.

Andreas - we can't have R3 linked to proper shell!

Carl requested some info on it, I tried to help with some lookup, 
not much ppl commented. I don't remember the blog article, but I 
might try to find it ...

so as for me - f*ck off MS shell crap, this is absolutly devastating 
experience for me, and they should fire someone in MS for that rude 
experience :-)))

dataset browsing example : 

>>my-ctx: context [ a: 22 c: context [ b: 33]]
>>using my-ctx
>>current-words
== [a c]

>> using c
>> current-words
== [c]

>> using none
>> current-words
== [... list of current user context words ...]

Pekr, we can write an R2-style console app with the hostkit. It's 
just that someone needs to actually do it :)

But you said - "it's probably easiest to just install a "proper" 
shell, maybe along with rlwrap." , which I think is not possible.

yeah, the command-line is a program like any other.. its just the 
I/O from the shell which is really complex in MS... 


the actual text user interactive session is totally controlable... 
just look at python's IDLE which is basically an example of R2's 
console but in DOS console.

Well, it will be possible, once R3 is not going to be a GUI app.

IDLE is not a DOS console.

Pekr, by that I meant something like rxvt from Cygwin. Or powercmd 
or console2 or ...

Combine this with rlwrap, and you should have a usable environment.

pekr, its a console application, just like our current R3 CLI.   
a console is simply a place which accepts lines of input interactively 
and spawns processing upon hitting a complete command.

a shell is a different thing entirely.  though the shell usually 
has access to the same input stream which is re-directed to/from 
the console.

But you'll probably need some hostkit hacking in any case.

http://www.rebol.net/cgi-bin/r3blog.r?view=0282#comments

Andreas - power console can't work. I tried Console2. The outcome 
is, you can't have both the true console mode and the GUI app. Look 
at the above link. Or simply Carl was not able to achieve that. Some 
ppl said, that is the reason why Python has two executables - one 
for plain console mode, and the other for GUI mode. But I might not 
interpret it correctly ...

Max - sorry for mispelling console for shell ...

Fortunately, with the hostkit you have the power to compile either 
as console or windows app.

IIRC, R3 is currently compiled as console app per default.

So currently "installing a proper shell" should work.

coundn't we just use their better console handling code and use it 
within R3's input loop?  or is that part of what you really meant?

yes? then we should take car to make it work with real console. I 
don't need power-shell. Shell2 is nice and sufficient. Simply - anything 
better than MS default console, is a win ...

http://sourceforge.net/projects/console/

What I mean is, two options:

- Short term: use a third-party shell replacement (like rxvt, console2, 
...)
- Long term: let someone write a nice R2-style console

recently even the short-term is not done ...