Re: What does embedding mean
- From: schlenk <schlenk@xxxxxxxxxxxxxxxx>
- Date: Tue, 12 May 2009 05:23:43 -0700 (PDT)
On May 12, 1:45 pm, Canol Gokel <ca...@xxxxxxxxxx> wrote:
On Sun, 10 May 2009 12:35:18 +0000, Cameron Laird wrote:
In article
<c9919eb7-61dc-46cd-8d17-0a9edbadc...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
<b...@xxxxxxxxxxxxxxx> wrote:
On May 9, 12:25 pm, ZuLuuuuuu <canol.go...@xxxxxxxxx> wrote:.
.
.
.interface. I was thinking about using C and GTK+ since my instructor
wants a program easily installable on Windows machines. We are
electronics engineerings so, you know, the people around me does not
know what interpreted languages etc. are. They want .exe files which
are easily installable and are working with just a double click.
.
.
look at tclkits and startpaks. You can create a single file (or two.
file) runnable program. This is how I run all my tcl code today. I
.
.
Let's make this painfully clear: Tcl can be the basis for any
installation regime that "C and GTK+" offer, and more. Although the
original questioner doesn't realize it, his description is ambiguous.
Let's distinguish these possibilities: A. A single-file executable:
Tcl's Starpacks make
this possible. We generally handle this simply by giving consumers
the .exe, and letting them copy it where they want.
B. More "normal" in a retail sense is a single-file
.exe or install.bat which expands into a mess of DLLs and registry
entries and other goop, spread out over who-knows-where. Tcl and
applications based on it can be installed this way, if one insists
on goop-spreading--and your consumers are likely to expect it,
because they've been trained to think that conflict-prone goop is
"normal" and "professional".
C. There are many, many other possibilities,
including the "amateurish" ones you already have in mind.
I repeat: if "C and GTK+" do it, Tcl can, too, although it's generally
a little more unusual for Tcl programs to create the version skew and
DLL conflict to which GTK+ has been prone.
Thanks for the answers.
I don't know if building the main app with Tcl and extend it using C
might work for me because the device I'm gonna interact might have a
driver written in C and in that case I have to write a Tcl binding for
that driver to use it in Tcl I guess? But I don't know how to write
bindings for a language yet :(
If you can write C its close to trivial in most cases.
Either use something like critcl to write C inline in a Tcl script, or
use SWIG to help generating a Tcl extension, or start from the
sampleextension and add your own code to it.
Have a look at the links at:
http://wiki.tcl.tk/9849
Michael
.
- References:
- What does embedding mean
- From: ZuLuuuuuu
- Re: What does embedding mean
- From: biz5
- What does embedding mean
- Prev by Date: Re: Strange error with globals and tk_messageBox (bug?)
- Next by Date: Re: ttk::entry widget styles or states
- Previous by thread: Re: What does embedding mean
- Next by thread: Re: What does embedding mean
- Index(es):
Relevant Pages
|
