head	1.3;
access;
symbols
	v2_0_0beta3:1.3
	v2_0_0beta2:1.3
	v2_0_0beta1:1.3
	v1_5_0:1.3
	v1_4_0:1.3
	gaim-doodle:1.3.0.6
	v1_3_1:1.3
	v1_3_0:1.3
	v1_2_1:1.3
	v1_2_0:1.3
	v1_1_4:1.3
	v1_1_3:1.3
	v1_1_2:1.3
	v1_1_1:1.3
	v1_1_0:1.3
	v1_0_3:1.3
	v1_0_2:1.3
	v1_0_1:1.3
	v1_0_0:1.3
	oldstatus:1.3.0.4
	v0_82:1.3
	v0_81:1.3
	v0_80:1.3
	v0_79:1.3
	v0_78:1.3
	v0_77:1.3
	v0_76:1.3
	v0_75:1.3
	v0_74:1.3
	v0_74-branch:1.3.0.2
	v0_73:1.3
	v0_72:1.3
	v0_62:1.3
	v0_71:1.3
	v0_70:1.3
	v0_69:1.3
	v0_68:1.2
	v0_67:1.1
	v0_65:1.1
	v0_64:1.1
	v0_63:1.1;
locks; strict;
comment	@# @;


1.3
date	2003.09.12.19.04.52;	author hermanator;	state Exp;
branches;
next	1.2;

1.2
date	2003.08.19.21.47.36;	author chipx86;	state Exp;
branches;
next	1.1;

1.1
date	2003.04.25.06.47.17;	author chipx86;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Perl plugins for Win Gaim.
@
text
@Makefile
Makefile.in
.deps
.libs
*.dll
*.lib
*.la
*.lo
*.a
@


1.2
log
@Okay, ready for some breakage again? I rewrote the perl loader plugin. All
old scripts are broken, but the new API will be much better. Currently, you
can access accounts and do debug output, and that's it, but adding support
for new things is much easier. Please don't come after me with pitchforks.
@
text
@d6 1
@


1.1
log
@I had a damn good commit message, but it was eaten. Let's try it again.

Announcing, Gaim Plugin API version 2.0, or GPAPIV2.0 for short.

There are lots'a cool thingies here.

Okay now, this isn't as cool as the previous message, but:

1) There's now a single entry function for all plugin types. It returns a
   detailed information structure on the plugin. This removes a lot of the
   ugliness from old plugins. Oh yeah, libicq wasn't converted to this, so
   if you use it, well, you shouldn't have used it anyway, but now you
   can't! bwahahaha. Use AIM/ICQ.

2) There are now 3 types of plugins: Standard, Loader, and Protocol
   plugins.

   Standard plugins are, well, standard, compiled plugins.

   Loader plugins load other plugins. For example, the perl support is now
   a loader plugin. It loads perl scripts. In the future, we'll have
   Ruby and Python loader plugins.

   Protocol plugins are, well, protocol plugins... yeah...

3) Plugins have unique IDs, so they can be referred to or automatically
   updated from a plugin database in the future. Neat, huh?

4) Plugins will have dependency support in the future, and can be hidden,
   so if you have, say, a logging core plugin, it won't have to show up,
   but then you load the GTK+ logging plugin and it'll auto-load the core
   plugin. Core/UI split plugins!

5) There will eventually be custom plugin signals and RPC of some sort, for
   the core/ui split plugins.

So, okay, back up .gaimrc.

I'd like to thank my parents for their support, javabsp for helping convert
a bunch of protocol plugins, and Etan for helping convert a bunch of
standard plugins.

Have fun. If you have any problems, please let me know, but you probably
won't have anything major happen. You will have to convert your plugins,
though, and I'm not guaranteeing that all perl scripts will still work.
I'll end up changing the perl script API eventually, so I know they won't
down the road. Don't worry, though. It'll be mass cool.

faceprint wants me to just commit the damn code already. So, here we go!!!

..

..

I need a massage. From a young, cute girl. Are there any young, cute girls
in the audience? IM me plz k thx.
@
text
@d8 1
@

