Module or Snippet?

Quick question: while trying to get my custom scripts to work with MODx, I’ve been wondering whether it would be better to make something a module or a snippet. I have a script which allows certain trusted people (site admins) to add and edit records in a database which is searchable by all users. Because it’s only meant for specific members to use, should I make it a module or wold a snippet be ok? Is giving a page with the snippet call to the script and adding permissions to the page allowing a "database editors" web group to view it secure enough? I wanted to add some features to the public part, where if you were logged into the frontend as a db editor, there would be links to edit the current record, add a new one and other things to make the admin part easier. So that’s why I was thinking about making it a snippet, but I could really use some advice on whether one would be better than the other. Thanks!

Does anybody know? Sorry for bumping this, but I was reading the "future proofing" article in the WIKI and read this about modules:

"Modules" will no longer exist in their current form. The new Manager will itself be powered by MODx, so any extra Manager facilities will need to be snippets, just like they would be a front-end app. You may therefore wish to develop a front-end application and restrict who can use it.

What exactly does it mean by "The new Manager will itself be powered by MODx, so any extra Manager facilities will need to be snippets"?

The MODx Manager in a future release will be built on top of the MODx API itself, just like any other "normal" front-end site.

So does that mean that the manager will be integrated into the frontend, unlike now where you need to log into the backend to do manager-like stuff (like add new docs, edit snippets etc)? Sorry if it’s a stupid question, I’m still sorta new to this stuff.

No... it will be a separate "context". Quick Edit will likely remain integrated into the front end as it is now.

Bah, I still don’t get it... what do you mean by "separate context"? I’m really interested in the new innovations coming into MODx... needless to say some of it seems confusing to me

Please wait until the relevant demo is available.

"correct me if I’m wrong"

He’s saying basically that the modx manager will (in a future release) run on top of the modx API instead of being built into it. This will offer the ability to fully integrate your applications with the manager because they will exist on the same tier.

Quote from: rthrash at Feb 12, 2007, 11:40 AM

Please wait until the relevant demo is available.

I was waiting for you to say that!

Ok, after reading Seventhapex’s reply and re-reading Ryan’s I think I get it... so basically, modules get the ax, but at the same time it becomes possible to fully integrate apps into the manager, like a snippet in the frontend. Sounds sweet!

And don’t get me wrong... usually I’m a pretty technically oriented person... I’m the guy that everyone goes to for computer help when the network goes down or a hdd needs a good refomat. I love OO too (CS major!), but sometimes it takes me awhile to "get it". Thanks for putting up with my stupid questions.

I just got into OO myself you should check out this blog entry, it’ll wet your geek and get you pumped about the future of modx.