Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy. This forum is not for asking programming related questions.
I think we should do a group thing, like the phpthrowdown team did. I didn't get to participate but I wanted to.
Being a third of that team I'm all too aware of the potential problems involved in Internet collaboration. The primary reason for working with others over the internet is probably to learn from the experience and, sadly, I just need to get the job done. I'm employed now, I have to be able to justify my actions.
As I compromise I could set up a thread documenting my actions as I develop my solution. Would that interest anyone?
ole wrote:As I compromise I could set up a thread documenting my actions as I develop my solution. Would that interest anyone?
I'd be interested -- especially if up-front we came up with a quick list of requirements and optional 'would be nice' features. Without that is not that easy to discuss the design issues and different design options available, or what building blocks are necessary.
Agreed with NSG, as long as I'd be able to rip it to shreds, and piece it back together, I'll be fine with following your progress/being a guinea pig (tester)...
arborint wrote:Since Ninja and nick are a couple of bastard(izer)s then maybe you can throw out some requirements.
I took ever so minor offense to that comment due to the lack of a smiley indicating sarcasm (assuming there was some, and it was not intended as an insult)
nickvd wrote:I took ever so minor offense to that comment due to the lack of a smiley indicating sarcasm (assuming there was some, and it was not intended as an insult)
Usually if I put a smiley I am being sarcastic, without one simply attempting to be clever. I can't really imagine myself (or anyone else around here) using the word bastard seriously here. It's just not a programmer term. No insult intended, just playing off Ninja's use of the word.
However, if you don't post those requirements I'll think you are a ... <-----
I think we should do a group thing, like the phpthrowdown team did. I didn't get to participate but I wanted to.
Being a third of that team I'm all too aware of the potential problems involved in Internet collaboration. The primary reason for working with others over the internet is probably to learn from the experience and, sadly, I just need to get the job done. I'm employed now, I have to be able to justify my actions.
As I compromise I could set up a thread documenting my actions as I develop my solution. Would that interest anyone?
That sounds fantastic! Will we be allowed to take it and suite it to our own needs? I understand if not.
I'm trying to get into the habit of not working over weekends now I actually have a proper routine - ish.
I'll give you my requirements and some background but no code is going to be written for one to two weeks probably because I've got a production server migration to do and no desktop machine or development server yet.
Background
A frequent occurrence is that of the "approval". This is where a video or part of a video has been created and needs to be approved by the client. At this stage it is important that the video and related sources are password protected and not public because it has not yet been approved. Once it is approved the video can be made public and needs to be available via GET request so that it can be embedded in a web page.
In addition to this some videos are sensitive and are intended for the eyes of maybe only a select group of individuals working for the client. And in this case both the approvals and the approved versions need to be password protected. The approved version still, however, needs to be embedded in a web page and therefore be available via GET request.
Finally we also need to share files such as images or articles with our clients and vice versa (a drop-box). Email is inadequate large files are restricted by some clients and they are disorganised, all the resources end up scattered about in people's inboxes, making the resources difficult to get hold of. Centralization is what we are after.
Proposed Solution - Requirements
Store all videos/resources outside of the document root on the server
PHP provides an interface by which this files can be retrieved via GET and is able to make any necessary password prompts; sessions will help here.
Drop-box: Clients need a simple (possibly like explorer) interface for uploading and downloading files
We should be able to create user accounts so that our clients can get access to the drop-box. This user accounts should be chroot'd and optionally have expiration dates.
The drop-box should have our company branding.
Drop-box should be written using web standards and be fully functional without JavaScript.
JavaScript should be used to enhance the interface of the drop-box (right-click menus etc.)
Flash has a feature where multiple files can be uploaded as once using the Windows drag selection via an Open File dialog. It would be nice to implement this.
In future I may need to interact with an external file system over FTP or something else.
- when a file is uploaded, the user should be able to select people to notify (if any) on successful upload.
- users should of course have adjustable privileges - upload / download / edit text files / etc.
- just to extend on your "connect to external ftp server" - I'd say give the admins the ability to go into a "connect to remote server" page and type in their credentials and then they could surf that server just as if it was their own
- possibly the ability "save" connection settings to remote servers - although this may not be a good idea due to security issues
That's all I can think of for now. If you aren't interested in these don't worry about it, I'm just throwing out suggestions.