Keeping TP Organized.

[Xarcell]

I'm good at time management and keeping things organized, which is why I'm so good at my job at work. So I just wanted to pass on some ideas to Bloc...

1.) One of the things I noticed about TP is the button issues which have already been discussed. Sooner or later there are going to be too many buttons to fit in a theme. So here are a few suggestions...

Make the TPAdmin link appear in the "user Info" block if the user has permission to use TPAdmin. If the User isn't a administrator or moderator, the TPAdmin link doesn't appear.

I think you should let people add buttons manually. You also gotta remember that there are other mod's added to SMF in general that add buttons, aside from any buttons that  user might want to add manually like "stats", "gallery", "osstore" or "smfshop", etc.


2.) I'm really big on termnology when must people aren't, but I really hate to see alotta confusion in the future to appear with TP & SMF with the word "Mod" or "module". Especially to those that don't know english very well.

Why not call a TP module a "plugin" or something other than "module" or "mod". TP is already mod itself.

3.) I was thinking about how TP is being updated and how much time it takes. I understand that Bloc has actually updated TP and done many other things in a very timely fashion. However, most of the "mob" don't understand the time it takes to do such things. So I thought of an idea to make TP seem as though it always having updates, etc etc...

Seperate TP from the extended modules except for "content" and "userinfo". Update TP and release it.

Then update and release the the extended modules as you finish them. Such as "shoutbox", "downloads", "theme selection", any future blocks like, "random game", "adblock" "calendar", poll", "random member", etc. This way it seems you have continued progress, and if if doesn't need to be updated, or you've already updated it, you can still release it the same day no problem.

Then do the same with your themes. It's less stressful this way, and for those that can't wait will feel as though things are moving more quickly.

Also keep in mind if there is a needed "bugfix" to a module, it can be done without having to release an updated TP. You can just release the updated module...

4.) I'm not sure how you have this planned, what about moving "module" to the TPAdmin settings, rather than having it as a selected block. Then have the name of the module installed appear inside in the "create block" list along with phpbox, newsbox, rssbox, etc.

5.) It was suggested by Nok, that allow permissions by membergroup to make a block upshrinkable or not. At first it seemed pointless, but then I thought if your putting ad's in your blocks, you don't want your user's to be able to upshrink them. However, if a user is donater, you can place him/her in a membergroup that would allow you to upshrink the blocks with ad's in them. I think that's something serious to consider...

6.) Probably the biggest issue us "noobs" with portals is getting a module that actually works with the version of the portal we are using. For example:

Say you update TP to .9 and you have 2 modules with one of them working with version .9 and the other one doesn't. The one that doesn't is updated and put in the .9 modules, but the other module that works with .8 & .9 is only listed in .8 module list. So then you get people asking all the time " is it compatiable with .9?" repeatedly. We already see this at the SMF boards.

I think everytime TP is updated, the modules that are already compatiable should be resubmitted to a .9 modules list with the version # of the module. Even if the author is absent, and the module seems to be working fine with no erros on the new .9, a adminstrator or moderater can submit it in the .9 module listing.

This version .9 listing can be viewed in the SMF package manager when browsing "TP" Modules". However, if the user hasn't updated to version .9 of TP yet, they cannot see the module list of .9, only the module list of .8. They should only be able to view the list of compatiable modules that work with the version of TP they are using.

I hope I didn't confuse, there are probably easier ways of keeping it organized...

[Xarcell]

I would rather have an admin link in the userinfo block along with tpadmin also.

Just an idea...

[borgBOB]

I do believe the "Mod" that TP is for SMF, is not 'module', but rather 'modification'.

To me, the 'Mods' board at SMF, is a list of 'modifications' to SMF, not a list of 'modules' to add on.

While the 'modules' in TP are actually modules, or configurable, functional areas. For example, Downloads and Gallery are modules for TP.

The button problem should go away as we move to more themes based on the NDT for SMF RC2+.

The TPadmin added as a link or 'button' in the user block is a great idea, and I believe Bloc is working on that.  One problem I see, is if an admin does not activate a 'user block', then the only other way to see it, is to direct link, or change themes.  And many of blocks themes incorporate a way to add buttons, although this feature may not be fully explained.

Remembering that this is still a 'beta' modification, not a final gold release, explains the path Bloc has taken on the developement of this project. He is following the path SMF has taken.
Just my humble opinion.