OpenEuphoria

RE: fixed windows

• Posted by gertie at visionsix.com Aug 05, 2003
• 411 views

On 5 Aug 2003, at 18:12, Peter Willems wrote:

> 
> 
> gertie at visionsix.com wrote:
> 
> > So the mirc nicklist and channel window are just fixed (but changeable 
> > and 
> > detachable) child windows in the parent ! That explains how it is 
> > possible to 
> > move each channel out of the mirc application screen and out onto the 
> > desktop. Just think where Eu would be now if RobC had merged Eu and mirc 
> > 
> > functionality way back when i first suggested it. Eu would look like 
> > Bach/Bliss/OpenEu/mIRC now. And beat the pants off everything out there.
> 
>     Kat, I've seen your remarks about mIRC before and I don't get it.
> 
>     As far as I can see mIRC is an application that handles the
>     IRC protocol. It has a build in interpreter to handle scripting
>     inside mIRC so all kind of stuff can be automated.
> 
>     mIRC is definitely NOT a multi-purpose programming environment.

Want a list of the language words and variables of mirc? Want a list of what 
it can do that Eu can't? 

>     Having said that, I think it is very much possible to implement
>     IRC functionality with Euphoria, and creating a library that can
>     understand mIRC commands and run them as a Eu program should be
>     possible also (although I think it's a serious undertaking).

Not terribly serious, other than the string execution mirc has. And being able 
to override it's built-in commands. I wrote a 100% Eu bot, and you can find 
the mirc-eu bot in the archives. The 100% Eu bot has no gui. The mirc-eu bot 
has access to mirc's script engine and gui.


>     One thing should be clear: the functionality of mIRC (like what
>     can be done with it's windows) has nothing to do with mIRC's
>     scripting language. I'm not sure in what programming language
>     mIRC has been developed, but it is definitely not written in it's
>     own scripting language 
> 
>     So I really don't understand what you mean by "merging Eu and
>     mIRC" ?! They are two completely different things. It's like
>     asking to merge Visual Basic (a language) with OpenOffice (as
>     a scriptable application).

In a word(s):

mirc:
1) executing strings
2) goto
3) threads (including threaded timers)
4) event handling
5) native socks support (you can http/telnet/pop3 with mirc too)
6) easy as heck gui support
7) no var instanciation required
8) no crash if a var has no contents in a boolean test

Bach:
9) classes
10) crash catching
11) gui support
12) block comments
13) slicing shorthands
14) better include paths 

These 14 items are things BobC has said will not appear in Eu. The closest 
app i have seen coded in Eu that might enable all the above is AGetz's 
window server and Jiri's associated lists. And several string libs are required 
in my opinion, string.e and strtok.e, and the file manipulation libs like
file.e,,
and for any windows gui, you must have win32lib. If RobC can't handle the 
full developement of Eu, i refer you to my suggestion he hire Jiri, Cuny, and 
Parnell (maybe paying them in futures, like stock).

Kat