[Phpwebsite-developers] Module design concept brainstorming

[Verdon V. <ve...@ve...>]

Hi :)

I'm just thinking out loud and looking for opinions here. Would welcome 
any...

I've been doing preliminary work re-writing my phpwsbusiness mod as 
rolodex, for fallout. While I've been doing that and asking questions 
here, discussion has come up about the demographics mod. I'd definitely 
like to hook into this, but there are usage scenarios where this would 
not be good, as one phpws user will be managing/owning many or all 
rolodex cards.

So, what I've been thinking is that it would be good if the site admin 
using my rolodex mod could decide whether to hook into the demographics 
mod, or use the rolodex internal tables instead. My first thoughts 
being that there could be a switch in rolodex settings that would tell 
the card class' init() function where to look for data for all cards. I 
then thought, would it be better if an individual card record could 
somehow be flagged to use demographics data or rolodex data. That would 
allow the real world scenarios I currently have where one user is 
owning/managing 700 or so phpwsbusiness records on a site while the 
other 200 or so records are owned/managed by individual phpws users.

Now, I'm only thinking in the broadest terms here and haven't worked 
out any of the logistics involved. I am curious as to what others might 
think would be useful. I'm also unsure of (and concerned about) what 
kind of performance hit / overhead I might introduce. If you remember 
phpwslistings, it used extended user_vars to store demographic info for 
agents for listings. I always wondered if that had anything to do with 
some of it's performance issues.

Anywise, any thoughts?

Thanks,
verdon