__________________

SVN Repo set up at http://code.google.com/p/talkphp/ you need to create a google account, then I can add people so that they can have commit permissions.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

Could you please join me on, my account is village.idiot@sbcglobal.net , please make me admin.

__________________

There you go m8, I've added you as a project owner.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

Here is a quick mockup of what the database could look like (there is no perticular reason that one is highlighted)
http://www.imagewasp.com/uploads/8052.png

__________________

My thread got jacked!


(edited out the rest...)

__________________
Signatures are nothing but incriminating.

admin or member?

That DB design seems good.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

djm53@kent.ac.uk - is currently my main one so feel free to add me also :P

__________________
www.jooney.co.uk - the online portfolio

It says that user doesn't exist, you will need to register it with google:
http://www.google.com/accounts/NewAccount

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

A few features that could be added to the list!
How about subscriptions?

Friendslist which would be catagolized like:
The member can create "groups" where they can put different friends in, for example some might want a "Family" or "Business" or "Design", etc.
Also allow them to "subscribe" to their friends' which would basicly make a subscriptions for new images added by that friend. Meaning that you can have someone on your friendslist without having to be subscribed to him/her.

How does that sound?

__________________

I'd love to help it in some way, but my PHP skills are greatly lacking.
Hope to see something awesome come out of this!

dalejamesmooney@gmail.com

Use this email then :P

__________________
www.jooney.co.uk - the online portfolio

consider yourself added sir!

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

I don't understand the first part. But I like subscribing to a user.

I am getting a more accurate database design up.

__________________

Do we have a project directory structure in mind?

Looking forward to the improved DB design .

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

Not at the moment, no. But if you have one I would love to see it.

__________________

Items:


Users:


Gallery:

__________________

Items:




Users:




Gallery:


Options/Templates:


Configs I can name off the top of my head (will be a place to add more):
ActiveTemplate
ImageDir
ResLimitX
ResLimitY
SizeLimit
AllowUnregInIndex
AllowUnregInSearch
AllowUnregInGallery
AllowUnregInItem
AllowUnregToComment
AllowUnregToRate

__________________

Well i usually use a structure loosly based round the zend framework structure:

How well it will translate to this project I dunno, think it may be alittle too complex for a relatively simple project.

__________________
mysql> SELECT * FROM `users` WHERE `users`.`clue` > 0;
Empty set (0.00 sec)

That is probably going to be too complex, we are not using most of the things provided in that structure. I was thinking something more like this:
-Core is our class functions and deeper logic. Absolutely no implementation or design elements are to be here.
-Src is our script related images, javascript, ect.
-Templates is our templates, each one will have a sub directory.
-Implementation is where the stuff actually happens, where the commands are actually called and ran on the server. This is almost exclusively inline code.
-Main Dir is where our front pages are called which call the templates.
-Images is where we store the images for the users, we will mod_rewrite a file to load and process them. It might be ideal to put it below the webroot. This filename would be a config.

Lets say a user submits an image. He is taken to main/submit.php. This file loads its implementation file which actually submits the image. The implementation files deal with the classes to utilize them, they almost completely inline code. The main file after getting the response from its implementation file then displays the template and all the effects it needs to.

This gives good abscraction from the classes, implementation, and displaying. It is also fairly simple and straight forward.

I would like this confirmed with other programmers before I actually do it though.

__________________