API questions

[Philip Olson]

Hello all,

A couple of questions:

1. Is there a list of API changes with 0.6->0.7? Like for plugins, no
more info() and the XML file changed but I'm assuming more. I'm mainly
concerned with plugins. And I ran into one API break from (I assume
0.5) in FormUI, like add()->append().

2. Is there a requirements API? Like, if a plugin requires a PHP
version or PHP extension or PHP directive value... or are these checks
custom per plugin? And, for example, I suppose a plugin may require
another plugin.

Basically, I'm mostly looking for a list of known breaks while
cleaning up the plugins, and being new here my brain lacks the history
of knowledge.

Regards,
Philip

[luke]

Phillip,

Can i just say a big thankyou for taking the time to clean up the -
extras plugin repo. I really appreciate it :)

Sorry i can't really answer your questions, but if it's not in the
wiki, it probably doesn't exist. If you can catch michaeltwofish, he's
often working on documentation.

Cheers,

[Ali B.]

On Sun, Nov 22, 2009 at 9:32 AM, Philip Olson <phi...@roshambo.org> wrote:

Hello all,

A couple of questions:

1. Is there a list of API changes with 0.6->0.7? Like for plugins, no
more info() and the XML file changed but I'm assuming more. I'm mainly
concerned with plugins. And I ran into one API break from (I assume
0.5) in FormUI, like add()->append().

Hi Philip,

There's no such list yet to my knowledge. Hopefully we'll be able to compile such list at or close to release. And there would be more than the plugin change in the API. If we are to include taxonomy in 0.7, that's a brand new sub-API added. Not to mention that the tags part of the API will likely disappear if we end up reimplementing them from the taxonomy system.
One change worth mentioning in addition to the changes in the plugins (the xml and the omittion of info()) is the change in how the front-end comment form is implemented. Themers can (should?) now use FormUI to build the themes' comment forms instead writing the form markup from scratch.
 

2. Is there a requirements API? Like, if a plugin requires a PHP
version or PHP extension or PHP directive value... or are these checks
custom per plugin? And, for example, I suppose a plugin may require
another plugin.

The concept of requirements has been suggested in more than one occasion and as part of several discussion topics. I am not sure if there are any plans to implement such system in the upcoming release though. I could be wrong.

--
Ali B./dmondark
http://awhitebox.com

[Philip Olson]

> There's no such list yet to my knowledge. Hopefully we'll be able to
> compile such list at or close to release. And there would be more
> than the plugin change in the API. If we are to include taxonomy in
> 0.7, that's a brand new sub-API added. Not to mention that the tags
> part of the API will likely disappear if we end up reimplementing
> them from the taxonomy system.
> One change worth mentioning in addition to the changes in the
> plugins (the xml and the omittion of info()) is the change in how
> the front-end comment form is implemented. Themers can (should?) now
> use FormUI to build the themes' comment forms instead writing the
> form markup from scratch.

I'm not familiar with taxonomy but it sounds like it'll make it into
0.7.

Could you offer a specific example regarding a FormUI update like
this? Maybe using one of the current plugins?

> The concept of requirements has been suggested in more than one
> occasion and as part of several discussion topics. I am not sure if
> there are any plans to implement such system in the upcoming release
> though. I could be wrong.

Okay thanks, we'll see what happens.

Regards,
Philip

[Sean Coates]

> Could you offer a specific example regarding a FormUI update like
> this?

Here's the FormUI for Comments Form change in K2. I think this is what you're asking about:
https://trac.habariproject.org/habari/changeset/3691/trunk/htdocs/system/themes/k2/comments.php

S