Official MOD creation instructions

[Randem]

Colin,

Thanks for your help. My issue is that if I have to start at scratch I might as well convert my current system from Perl to php and use that. This would be a better use of my time. But since I was going to use SMF, I thought that maybe what I use may be useful to others. My current tool still runs on Perl on a different platform/host than SMF. I could just as easy just keep the same system that is working quite well. I thought I would ask to see if my work could be cut short in converting to SMF (hense the cheat sheet). If it cannot then I have other options.

[Colin]

Ah I see, no problem.

Unfortunately we don't have anything specifically created for how to develop the features that you requested. There is most definitely a bit of a learning curve in terms of becoming familiar with how SMF works. However once you get past that, SMF is efficient and powerful to develop for. I certainly would encourage you to stick it out and give it a try, but I suppose I have a bias .

[Burke ♞ Knight]

You could still convert, then make a mod.
That is basically what I thought would be done.

There are some sites out there, that have very good quick reference guides for PHP.
Look, I did not mean to be so harsh, and the ignorant remark was not meant to be directed at "you" but at people in general who seem to come to places to have everything hand delivered to them on a platter. As you can see when look through the forum, that does happen a lot.

Package SDK: package-info.xml
Package SDK: modification.xml
[WIP] Modding Documentation: Adding Permissions to 2.0
Integration hooks
[README] SSI FAQ's

[Randem]

Suki,

Thanks, that is the most helpful link that has been given. At least I know what to look for and where to start. Basically what I was looking for and it would have been a lot simplier if there were one location to see all this information as well as the where the software to change was. I am imagining that all the source in the downloaded SMF install package and no triggers and code are in the actual database?

[Randem]

BurkeKnight,

I currently have two host/platforms. The Perl Platform with my Discus Support Board that has been converted and redirected to SMF and my converted SMF support board on a php platform. Now my tracking and reporting (Realtime) is still on the Perl platform and still works quite well giving me the information that I need to progress and tune. However I wanted to move to only one platform/host so as not to have to support two host/platforms. this is where the MODS come in. If it were simple to create MODS to get what I need into SMF it would be a cleaner solution to support. Hoever if it is not an easy solution I will either keep two platforms (easiest) or convert the tracking/reporting system to php (still easier than creating an SMF MOD at this point it seems).

Just checking my options. It will get done either way.

[Burke ♞ Knight]

Now, I'm going to ask something, since I'm not familiar with Perl...
Can Perl be integrated into regular php code?

Yes, I admit it, I have no knowledge about Perl. Never used it, see it in my cPanel and stay as far away from it as I can. LOL

[Arantor]

Perl can't be integrated into PHP directly, just as PHP can't directly be integrated into Perl. It's a scripting language, much like PHP, but with some very serious differences.

Thing is, if you're porting it to PHP, you already have 75% of an SMF mod right there... the only 'moddy' bits are the bits where you alter SMF code directly to splice in whatever you need during SMF's execution.

Disclaimer: I haven't looked at any of the 'help' around here in years, not even the stuff I originally wrote, because there is only one definitive source for information about what works, where and how: the SMF source itself. And since you have to modify that anyway, why not just use that?

[Randem]

Arantor Beeblebrox the First,

Actually, I don't have to modify anything. The systems are separated systems that are connected with data only. I can use the Perl system as is as I have been. I just thought that if were easy enough and I did not have to spend much time learning and creating things I would integrate it into SMF for a cleaner solution. I really don't have to; it was just an idea... Things are fine just the way they are.

[Kindred]

you know, all of that information actually **IS** in one place -- it's called the online manual for a reason.

http://wiki.simplemachines.org/smf/Category:Package_SDK
http://wiki.simplemachines.org/smf/Category:Developing_SMF