Re: gimp-help: markup conventions

2000-08-07 Thread egger

On  6 Aug, Kevin Turner wrote:

 gimp-help/whysgml.txt states that we are going to go through all the
 bother of writing well-formed XML files (e.g. being strict about
 always using closing tags, etc), but that we won't be actually marking
 the files as XML.  If you have a grudge against xml, why bother being 
 half-compatible?  I'm a bit puzzled by this fence-sitting stance.  If 
 anyone is afraid that the XML tools are Not There Yet, remember that
 the tools that work with DocBook in its SGML form work with
 DocBook/XML too.

 However the DTD you were using for the maze plugin is more like a
 experimental hack. I you like to have the real XML DocBook you might
 consider using the version 4.0. I personally have no problem using 
 DocBook/XML 4.0 versus using DocBook/SGML 4.0, however we should consider
 using ONE of them for the whole project because everything else is a mess.

 And the conversion from one to another is pretty simple as (like you
 stated) we already conform to most of the xml conventions.

 Please note, that I took notice of DocBook/XML just 5 days ago and that
 it's not really advertised on www.docbook.org, thus I didn't really know
 that Jade really works fine with that.

 I feel the on-line help is a reference, with distinct entries for
 specific parts of the application.  A help entry for a filter is like 
 a man page for that filter.  I feel DocBook's "refentry" is the best 
 fit for this.

 Hm, I'll have a look whether that can be integrated in a seamless
 fashion. If yes, why not

 To address or link to some part of the document, that part needs to be
 tagged with an ID.  How shall we organize that namespace?  For
 filters, I might use their PDB name, but some filters may have more
 than one PDB entry.  And much of the help system is going to be
 describing user interface elements with no PDB name, so that's
 probably not a good plan.

 You normally shouldn't give subparts of your document id's and the
 naming for the mainpart of it should be pretty obvious, it's the
 name of the dialog or the plugin you're describing. However if you
 like to link to subparts of your document give it an id like:
 maze-001, maze-002 and so on... that should solve the problem. Of course
 if we have a plugin with the same name like an internal function we have
 to choose a different name, but that really shouldn't happen.

 There needs to be a regular way to construct a refentry's ID, and also
 a way to ensure all ID's inside that refentry are unique to that part
 of the document (so my "width" section doesn't end up pointing to
 something about cropping without meaning to).

 See above. Of course you also may name this section (applied to the
 maze example): maze-width. 

 A man page usually has a "Credits" and/or "Authors" section.  Do these
 belong in the help page?  I'm guessing not, but it's not like plug-ins
 have About boxes or anything.

 Are you asking about the Authors of the document or the plugin?

 BTW: Please Kevin consider making a ChangeLog entry when you check
 something into gimp-help, thanks

-- 

Servus,
   Daniel




script fu: writing to a text file.

2000-08-07 Thread JB

Hi
I want to make an export plugin from a multilayer gimp image to my game.
My idea is to separate each layers as pngs files (to use transparency and
compression) and then to write a text file like this:
layer1 : image1.png
layer2 : image2.png
layer3 : image3.png
...
I manage to export each layers on separate layers, but not to find the
function to write to a text file..
For the moment, this is a script fu, but I don't know scheme... So, I
would prefer C, but I didn't find any example of C plugin doing this kind
of stuff...

Any help would be welcom...

Mandor 

[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org





Re: Gimp to MacOS

2000-08-07 Thread Arnaud Masson


- Original Message -
From: Michael Natterer [EMAIL PROTECTED]
To: Jason T. Slack [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, July 21, 2000 12:26 AM
Subject: Re: Gimp to MacOS


 On Thu, 20 Jul 2000, Jason T. Slack wrote:

  Hello All,
 
  I am interested in doing a port of GTK+ and GIMP to MacOS.
 
  Has anybody started this?
 
  Should I go full speed ahead?

 Hi,

 I guess that Gtk+ and Gimp will run more or less automatically
 on MacOS X' BSD API once there is an X server, so there should
 be no need to "port" it.

 If you mean to port it to MacOS X' native windowing system, then
 it sould be mostly a matter of porting Gtk+. You should ask on
 the Gtk+ developer list if there are alrady efforts to port
 the upcoming version 2.0 to MacOS X.

 Porting them to the classic or carbon APIs may be not really
 fun because they lack stuff like processes and pipes.


Hi !

I have ported a big part of gtk+  to MacOS 9, it's on mac-gtk at
SourceForge.
IT'S ALIVE ! ;-)
The GDK port is based on QuickDraw+WindowMgr, and Justin Armstrong has made
changes for carbon support.
Of course, on MacOS X, he uses a standard unix glib (I must use the GUSI
posix emulation on the classic MacOS which is not easy for the process
stuff).

AND... I have a minimal version of Gimp running on MacOS 9 !
There are still a lot of bugs but at least I can paint some flowers with the
brush tool...

Currently I don't have much time for GTK because I am on holidays (far away
from my G4) so you should contact Justin for the MacOS X port.

Arnaud









Gimp-filters

2000-08-07 Thread Fethi BELGHAOUTI

hi to all !
can you tell mes where can i found the list of all the
recensement filters of Gimp ?

thank you.

Fethi.

___
Do You Yahoo!?
Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr



animated-Gif

2000-08-07 Thread Fethi BELGHAOUTI

hi to all !


can you tell how can i savec an animated Gif whith a
script in Perl-fu ?

thank you!

Fethi.

___
Do You Yahoo!?
Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr