Navigation

The question of why we should add supportsFeature in a plugin is first saw here.

more...

So often a plugin need to track information in variables, I'm talking about data that is persistent through out the life of the plugin. This allow data to be passed from event to event, for example.

more...

Feature discussion can go to: here

Follow what hcgtv did in his site, now I added news feed as well.

[update]
Now using nudn/rss skin for output.
[/update]

Added Atom 0.3 feed.

Good stuff.

Finally find some time to get this going.... really getting sick of screwed up HTML ul, ol, table and such in a post.

see here

Now, one can read my NUDM site from RSS.

In the plugin API, there is a getMinNucleusVersion function that helps a plugin to report to Nucleus that the minimum Nucleus version it supports. This is a way to ensure a plugin is not install on a old Nucleus setup that certain support is missing. ie user defined table prefix

more...

I saw it sometimes when a plugin writer directly construct a permalink (also called item link) by doing this:

...
...
echo "<a href=\"index.php?itemid=".$itemid."\">".$title."</a>";

...
...

more...

Today, I learnt about a trick how to put a 2nd blog on its own dirs.

see here

Some links still broken because nudn/nudn is in the link instead of nudn/... still working on it. Now, all is working.

Here's a list of item to discuss:

1. walk through the feature list, discuss the roadmap for next release: timeframe, required features. I don't know we want a roadmap that look too far into future. I'd suggest a roadmap of 2 releases in the roadmap: up-coming release, future releases, and no interest.
2. discussion on the synergy with BlogCMS, how to best collabrate ie plugin/bugs/feature backport. Update: There seem to be more and more posts from radek on the forum about "new" BLOG:CMS plugins that does not work directly on Nucleus, and causing users to puzzle... is this a issue that we need to talk to him?
3. karma said in last meeting: "I did have an idea about plugin interoperability with BlogCMS. It's a thing to do on Radek's side, though. Here goes: instead of having BlogCMS-specific plugins inherit from NucleusPlugin, have them inherit BlogCMSPlugin. Then create BlogCMSPlugin as a class that inherits from NucleusPlugin. BlogCMS-specific plugins will then simply fail to install on Nucleus core, since no BlogCMSPlugin class is available." Progress on this?
4. plugin license, do we want to stay GPL or allow LGPL to allow commerical plugin?

Since Nucleus 2.5, sql_table() is introduced to construct the name of table name.

ie. sql_table('item') yields nucleus_item in a normal setup.

So, why a plugin should use this function to determine the table name, you ask?

I say, simple.

more...

- fixed right menu
- use extended body
- fixed my info on top left

Here's a list of features being discussed in the forum for the next release, with URL/description/spec. This is intended for developer discussion in next IRC session (in 2 weeks?) and for tracking purposes.

more...

Here's my current to-do and watch list. Please give me a shout if you work on any of the following.

In-progress:

more...

With all these threads on the forum with many good idea, I just getting dizzle and need a summary and tracker. Here's a list of threads from the past 2 months or so that I found might be interesting for 3.5.

more...