As some may already be familiar with, I'm re-styling my website. I plan to include a user system where I can add photos, tweak portfolios, water-marks and what not. And eventually branch out to user registration so clients can book sessions over the web. Then I wondered, could I make the user backend computer based? So, primarily myself, can log in from my computer and upload photos.
I'd be able to add features to watch folders for new photos, and basically alleviate server load. My initial goal for the online script was to take an uploaded photo (of any-size) and resize it, watermark it and move it to a directory where it'll be found by the portfolio script. Then I read that some servers (I believe here in a post by Ben) restrict the amount of RAM a script can use and that an 8MP (give or take a 2MP's) picture took 32MB's to process.
The Desktop App would be able to save the locations of multiple photos (kind of like upload boxes) and resize them, watermark them and place them in their respective directories all in one fell swoop. Opposed to the web, where I'd need to upload the photos (whether from FTP or through the script) then resize, watermark and relocate them. It's really no different, but the web process seems much slower and cumbersome.
My primary camera right now is 15MP's. I could output smaller photos (4MP's) to the server and have the script do it's thing but why not cover two bases: Export the full-sized JPEG's and let a computer application resize the photos and upload the photos to their appropriate destination and back up the full sized JPEG's to a folder on the server so I can fetch them at any time if I need to resize the images or re-watermark them if I no longer have the originals or I'm away from the drive that stores them.
To do this, I'd need to learn Objective-C (C++?) for OS X. I'd prefer to use a library that supports Windows & Mac - for when or if - I release a version with client support. A version for clients to log in, browse their sessions (past & scheduled), create & edit/cancel sessions and view all uploaded photos from previous sessions where they can order prints.
Of course, the client support (Web or Computer) is a long ways down even after I make the user/login system. So Windows support isn't a main concern at the moment, but something to factor in. I've searched for Desktop based apps for Joomla! & Drupal and both are nonexistent. I'm not opposed to an entirely online UI, I think it'd be convenient to have a desktop application. I'd also like to create a mobile application but that's even more iffy than the desktop application.
Whether I choose a Web & Computer User Backend, it'll be a huge undertaking for me. I have no idea what's involved to implement what I want in both environments. This will not make it into the February update of my website, but likely an incremental update if not a future version. Obviously, regardless of which option I choose I'll need to use a web database (MySQL) to store client information.
As an inexperienced developer, what seems logical? The Web UI or a desktop UI? I won't need to cross develop on the web, but I feel like I'd have more creative freedom (and memory) on the computer.
I'd be able to add features to watch folders for new photos, and basically alleviate server load. My initial goal for the online script was to take an uploaded photo (of any-size) and resize it, watermark it and move it to a directory where it'll be found by the portfolio script. Then I read that some servers (I believe here in a post by Ben) restrict the amount of RAM a script can use and that an 8MP (give or take a 2MP's) picture took 32MB's to process.
The Desktop App would be able to save the locations of multiple photos (kind of like upload boxes) and resize them, watermark them and place them in their respective directories all in one fell swoop. Opposed to the web, where I'd need to upload the photos (whether from FTP or through the script) then resize, watermark and relocate them. It's really no different, but the web process seems much slower and cumbersome.
My primary camera right now is 15MP's. I could output smaller photos (4MP's) to the server and have the script do it's thing but why not cover two bases: Export the full-sized JPEG's and let a computer application resize the photos and upload the photos to their appropriate destination and back up the full sized JPEG's to a folder on the server so I can fetch them at any time if I need to resize the images or re-watermark them if I no longer have the originals or I'm away from the drive that stores them.
To do this, I'd need to learn Objective-C (C++?) for OS X. I'd prefer to use a library that supports Windows & Mac - for when or if - I release a version with client support. A version for clients to log in, browse their sessions (past & scheduled), create & edit/cancel sessions and view all uploaded photos from previous sessions where they can order prints.
Of course, the client support (Web or Computer) is a long ways down even after I make the user/login system. So Windows support isn't a main concern at the moment, but something to factor in. I've searched for Desktop based apps for Joomla! & Drupal and both are nonexistent. I'm not opposed to an entirely online UI, I think it'd be convenient to have a desktop application. I'd also like to create a mobile application but that's even more iffy than the desktop application.
Whether I choose a Web & Computer User Backend, it'll be a huge undertaking for me. I have no idea what's involved to implement what I want in both environments. This will not make it into the February update of my website, but likely an incremental update if not a future version. Obviously, regardless of which option I choose I'll need to use a web database (MySQL) to store client information.
As an inexperienced developer, what seems logical? The Web UI or a desktop UI? I won't need to cross develop on the web, but I feel like I'd have more creative freedom (and memory) on the computer.