![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
nemesis <nam### [at] gmail com> wrote:
> [-- text/plain, encoding 8bit, charset: iso-8859-1, 16 lines --]
> Warp <war### [at] tag povray org> wrote:
> > Darren New <dne### [at] san rr com> wrote:
> > > Warp wrote:
> > > > (Besides, what is *your* definition of "IDE", if CMake isn't one?)
> >
> > > CMake is just a new version of make, or a makefile generator, I forget
> > > which. It's not integrated, and it's not an environment, any more than make
> > > itself is.
> >
> > You said what CMake is/isn't, not what an "IDE" is...
> bash is a pretty good IDE to me. It integrates/glues all other dev tools
> needed. :)
I wouldn't call that integration. It just launches the independent apps.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> bash is a pretty good IDE to me. It integrates/glues all other dev tools
>> needed. :)
>
> I wouldn't call that integration. It just launches the independent apps.
I think to be integrated, the tools actually have to talk to each other
while running. :-)
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New wrote:
>>> bash is a pretty good IDE to me. It integrates/glues all other dev
>>> tools needed. :)
>>
>> I wouldn't call that integration. It just launches the independent
>> apps.
>
> I think to be integrated, the tools actually have to talk to each other
> while running. :-)
There are pipes :)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nicolas Alvarez <nic### [at] gmail com> wrote:
> Darren New wrote:
> >>> bash is a pretty good IDE to me. It integrates/glues all other dev
> >>> tools needed. :)
> >>
> >> I wouldn't call that integration. It just launches the independent
> >> apps.
> >
> > I think to be integrated, the tools actually have to talk to each other
> > while running. :-)
>
> There are pipes :)
Excellent punchline! :)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> JavaScript is the only language I know which might conceivably be able
>> to do COM stuff. (If it can, I don't know how yet.)
>
> Out of curiousity, what languages *do* you know? I thought you'd worked
> in Tcl before.
Yeah, I've done some stuff with Tcl. But I didn't see anything in the
documentation about COM. (I gather you can add extension to Tcl to do
just about anything - but I'm not sure exactly how you link the
necessary C code into the interpretter...)
I have written some trivial VB code before now, but it's so absurdly
difficult to find out how to do stuff with VB. Anyway, I'm sure VB has
ways to do stuff with COM.
And I've written a tiny amount of C++ code. (More than VB, but still not
much.) C++ surely has a way to do this. Whether you'll survive to live
to tell the tale is another matter.
Also, I can probably do IA32 assembly.
(But The Real WTF is that there's a Haskell package for doing COM stuff,
and - get this - it doesn't compile on Windows...)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
>>> JavaScript is the only language I know which might conceivably be
>>> able to do COM stuff. (If it can, I don't know how yet.)
>>
>> Out of curiousity, what languages *do* you know? I thought you'd
>> worked in Tcl before.
>
> Yeah, I've done some stuff with Tcl. But I didn't see anything in the
> documentation about COM.
It's an extension called tcom.
http://www.vex.net/~cthuang/tcom/
I'll grant you it took two googlings to find it. ;-)
> (I gather you can add extension to Tcl to do
> just about anything - but I'm not sure exactly how you link the
> necessary C code into the interpretter...)
You say "package require tcom"
> (But The Real WTF is that there's a Haskell package for doing COM stuff,
> and - get this - it doesn't compile on Windows...)
Heh.
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> Yeah, I've done some stuff with Tcl. But I didn't see anything in the
>> documentation about COM.
>
> It's an extension called tcom.
>
> http://www.vex.net/~cthuang/tcom/
>
> I'll grant you it took two googlings to find it. ;-)
If I can't figure out how to add extensions, knowing which extension it
is doesn't help. So why bother looking it up?
>> (I gather you can add extension to Tcl to do just about anything - but
>> I'm not sure exactly how you link the necessary C code into the
>> interpretter...)
>
> You say "package require tcom"
That's very nice, but how do I get freewrap.exe to recognise this?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> That's very nice, but how do I get freewrap.exe to recognise this?
You find the package path out of freewrap, then put the package there. In
other words, you read the instructions on how Tcl finds packages.
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
> That's very nice, but how do I get freewrap.exe to recognise this?
FWIW, I'll be happy to answer "I tried this and that, and couldn't figure
out this other". The "I haven't even tried to answer my own question that's
well-documented in the obvious places" kinds of questions tho... :-)
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
A new kind of IDE interface:
http://www.youtube.com/watch?v=PsPX0nElJ0k
--
FE
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |