On 8/25/05, Leon Brooks [EMAIL PROTECTED] wrote:
You can build PPC and PPC64 binaries. I think you'd need eitehr a real
machine or a good emulator to actually thest them.
I think I agree (with an added caveat that cross compiling environments
are not always trivial to work with).
Thanks!
On Friday 26 August 2005 03:36, woc wrote:
On 8/25/05, Leon Brooks [EMAIL PROTECTED] wrote:
You can build PPC and PPC64 binaries. I think you'd need eitehr a
real machine or a good emulator to actually thest them.
I think I agree (with an added caveat that cross compiling
environments are
Hi,
woc [EMAIL PROTECTED] writes:
Can someone point me at:
* gimp 2.2 load/save support for some type of file written in
script-fu? Or,
* a concise reference work describing the data types I'd need to deal
with and their fundamental support routines? Or,
* a faq which is specific to
On 8/23/05, woc [EMAIL PROTECTED] wrote:
I do not want to write a .c plugin, because portability is more
important to me than speed.
Gimp itself is written in some variant of C, isn't it?
The only portability issue here is that you'd need to compile it on
all target OS's. No big deal --
On Wednesday 24 August 2005 15:48, michael chang wrote:
On 8/23/05, woc [EMAIL PROTECTED] wrote:
I do not want to write a .c plugin, because portability is more
important to me than speed.
Gimp itself is written in some variant of C, isn't it?
Right. ANSI C 89' with some extensions that
On 8/24/05, michael chang [EMAIL PROTECTED] wrote:
The only portability issue here is that you'd need to compile it on
all target OS's. No big deal -- that's how GIMP is made anyways. Use
MinGW for Windows, and Linux uses the GCC and related tools. Easy
enough.
Which means I'd have to mess
On 8/24/05, Shlomi Fish [EMAIL PROTECTED] wrote:
While Perl has many facilities for handling text very well, it does not have
any limitations with handling binary data. It can easily segment such data,
convert it from ASCII to binary, generate it, etc. Perl strings can contain
\0 characters,
On Wed, Aug 24, 2005 at 12:58:35PM -0400, woc wrote:
On 8/24/05, michael chang [EMAIL PROTECTED] wrote:
Perl probably has similar limitations, to a certain extent. Perl
handles text best -- binary data, it's best at simply passing... I
believe the term is ad verbatim or something.
So it
On 8/24/05, Manish Singh [EMAIL PROTECTED] wrote:
You can use Perl or Python to write a file format plugin. Script-fu is a
nonstarter, there's no way to register a load/save handler from a script
(though there could be in the future). Script-fu sucks for this for
other reasons, as others have
On Wed, Aug 24, 2005 at 01:49:50PM -0400, woc wrote:
On 8/24/05, Manish Singh [EMAIL PROTECTED] wrote:
You can use Perl or Python to write a file format plugin. Script-fu is a
nonstarter, there's no way to register a load/save handler from a script
(though there could be in the future).
On Wed, Aug 24, 2005 at 02:34:28PM -0400, woc wrote:
On 8/24/05, Manish Singh [EMAIL PROTECTED] wrote:
Well, the python bindings are disted with GIMP, though not on Windows.
This will change with GIMP 2.4 though.
If you care about Windows, you should've said so from the beginning. ;)
On 8/24/05, Manish Singh [EMAIL PROTECTED] wrote:
Yeah, and you contradicted this statement when you said that C wasn't
portable enough for you. There are differing definitions of what
portability means.
C is definitely less portable than I'd like.
Unfortunately, it looks like it's as
On 8/24/05, Manish Singh [EMAIL PROTECTED] wrote:
Well, the python bindings are disted with GIMP, though not on Windows.
This will change with GIMP 2.4 though.
If you care about Windows, you should've said so from the beginning. ;)
You're basically stuck with C for 2.2, script-fu won't cut
On 8/24/05, woc [EMAIL PROTECTED] wrote:
On 8/24/05, Manish Singh [EMAIL PROTECTED] wrote:
Yeah, and you contradicted this statement when you said that C wasn't
portable enough for you. There are differing definitions of what
portability means.
C is definitely less portable than I'd
On 8/24/05, michael chang [EMAIL PROTECTED] wrote:
I presume you mean this in the sense that you'd want to write it and
distribute it as-is for your users in this cases?
Yep -- plain text is ideal, but I can deal with other formats if
I have to.
If you want, you can always cross compile for
On Thursday 25 August 2005 00:58, woc wrote:
I'd have to mess around with getting access to the right
development environment every time I needed to make a change.
(And I do anticipate needing to make changes.)
Shouldn't be a big issue.
For MS-Windows, go to CygWin.com and click on the
woc wrote:
On 8/24/05, michael chang [EMAIL PROTECTED] wrote:
The only portability issue here is that you'd need to compile it
on all target OS's. No big deal -- that's how GIMP is made
anyways. Use MinGW for Windows, and Linux uses the GCC and related
tools. Easy enough.
Which means
On 8/24/05, Michael Schumacher [EMAIL PROTECTED] wrote:
If you make sure that GCC can build it, use stuff that'savailable on any
platform (Hint: make heavy use of glib functions), make the plug-in
available at http://registry.gimp.org and announce new releases on the
gimp mailinglists, you
(This is a nearly verbatim copy of a message I sent to gimp-user.
After posting it, I belatedly realized that this is probably more of
a developer question than a user question. Or, if not, just ignore
me and I'll go on and bug other people.)
I want to write gimp support for an obscure file
19 matches
Mail list logo
