I realize it'll take a huge effort.
I don't believe making the "framework" is consulting work. I don't mind giving the framework away for free with some common/possibly popular workflow schemes, showing it's potential and then whoever wants to can be hired for developing schemes for those who can't make them themselves. Or another more likely scenario, people could make their own schemes fitted for themselves, giving them the option to share it with others if they want to.
The framework would be modular. Sure, no two projects are actually exactly the same but there is a whole lot of overlapping, repetitive, unnecessary, tasks.
I'm not saying you lock into forever using whatever name convention you're using.
It's my first time ever proposing to work with strangers on the internet. I don't have a whole lot of experience with it so I can't really come out with every angle of the final product before anyone asks. (You might think you're asking but you're not, you're saying "You are an incompetent "idea man" who just came up with something you assume is unique and now you want a developer as your pet slave". Instead of saying things like "Nor have you outlined...", you could say "But how do you plan to deal with...").
I imagine folder structure being defined in Finder, the whole concept of the framework is based on the idea that all apps are great at their own thing, so Finder being the core of navigating through folders and finding files it would be logical. While the framework running in the background, Finder could get some extra toggle buttons or drop down menu in the toolbar to let you select what the folder should have of attributes "Like this should be where the XX of the project goes". Could use color labels to make it faster to distinguis between the different folders if one didn't find them hideous.
Depending on what'd you were developing cache flushing would obviously be handled different, who ever developed the scheme for that workflow would decide how it should be done. Someone likes to do it with changing filenames of the files you've edited. The workflow application would handle this, make sure where ever those files where included in the rest of your project their reference would be updated, and the browser you were using would be redirected to the new url. This would mean that your source files would have to be copied into a the deployment folder.
People are creative and resourceful and if you let them taste something great you should expect some of them to crave for more. I'm not saying the framework should have schemes (one computer is not limited to having a single scheme either) that fit perfectly for everyone but if you'd provide a few and show how smooth it can be I don't doubt that some people will want to roll their own.
Yep, I'm old and jaded. You see me as negative? _shrugs_ . I never said it was impossible, only that it's hard, tedious, boring, and that it goes through well-trodden areas with lots of competition so revenue generation will be hard. Pick one of the sub-tasks and work on it. You'll be happier and with a larger chance of success. Or think of that as a stepping stone to learn more about what's needed for the larger project.
Personally, I think the directory structure layout validation is the most interesting, especially if you can tell it to build your final structure layout. This could include minimization tasks, or automatic image format conversions. Another direction that could go is towards a static site generation tool. But then, I'm a developer.
Your rhetorical style needs work. It's ludicrous to assume that I or anyone else would expect you to have all the details planned beforehand. Neither did I say that you are incompetent. I pointed to that URL for a reason - it's hard to come up with an idea and get developers involved, and that essay gives some of the reasons. Instead, I am pointing out your inexperience and giving advice for the some things you need to distinguish yourself from an "incompetent 'idea man'."
You should also talk a lot less about yourself. Most people don't care enough to read through several paragraphs defending your inexperience to figure out what your point is, the title had little to do with what you wanted from people, and the self-described term "Problem Solver" is another suspicious flag which falls into the "Idea Person" category.
I really appreciate you taking the time to help me on my way.
I will work on some proof-of-concept apps that can help illustrate the approach I wish to take. Starting with the folder structure layout builder, image format conversion and layout/format validation. Then I'll see if it has something to it.
Comments
I realize it'll take a huge effort. I don't believe making the "framework" is consulting work. I don't mind giving the framework away for free with some common/possibly popular workflow schemes, showing it's potential and then whoever wants to can be hired for developing schemes for those who can't make them themselves. Or another more likely scenario, people could make their own schemes fitted for themselves, giving them the option to share it with others if they want to.
The framework would be modular. Sure, no two projects are actually exactly the same but there is a whole lot of overlapping, repetitive, unnecessary, tasks.
I'm not saying you lock into forever using whatever name convention you're using.
It's my first time ever proposing to work with strangers on the internet. I don't have a whole lot of experience with it so I can't really come out with every angle of the final product before anyone asks. (You might think you're asking but you're not, you're saying "You are an incompetent "idea man" who just came up with something you assume is unique and now you want a developer as your pet slave". Instead of saying things like "Nor have you outlined...", you could say "But how do you plan to deal with...").
I imagine folder structure being defined in Finder, the whole concept of the framework is based on the idea that all apps are great at their own thing, so Finder being the core of navigating through folders and finding files it would be logical. While the framework running in the background, Finder could get some extra toggle buttons or drop down menu in the toolbar to let you select what the folder should have of attributes "Like this should be where the XX of the project goes". Could use color labels to make it faster to distinguis between the different folders if one didn't find them hideous. Depending on what'd you were developing cache flushing would obviously be handled different, who ever developed the scheme for that workflow would decide how it should be done. Someone likes to do it with changing filenames of the files you've edited. The workflow application would handle this, make sure where ever those files where included in the rest of your project their reference would be updated, and the browser you were using would be redirected to the new url. This would mean that your source files would have to be copied into a the deployment folder.
People are creative and resourceful and if you let them taste something great you should expect some of them to crave for more. I'm not saying the framework should have schemes (one computer is not limited to having a single scheme either) that fit perfectly for everyone but if you'd provide a few and show how smooth it can be I don't doubt that some people will want to roll their own.
Yep, I'm old and jaded. You see me as negative? _shrugs_ . I never said it was impossible, only that it's hard, tedious, boring, and that it goes through well-trodden areas with lots of competition so revenue generation will be hard. Pick one of the sub-tasks and work on it. You'll be happier and with a larger chance of success. Or think of that as a stepping stone to learn more about what's needed for the larger project.
Personally, I think the directory structure layout validation is the most interesting, especially if you can tell it to build your final structure layout. This could include minimization tasks, or automatic image format conversions. Another direction that could go is towards a static site generation tool. But then, I'm a developer.
Your rhetorical style needs work. It's ludicrous to assume that I or anyone else would expect you to have all the details planned beforehand. Neither did I say that you are incompetent. I pointed to that URL for a reason - it's hard to come up with an idea and get developers involved, and that essay gives some of the reasons. Instead, I am pointing out your inexperience and giving advice for the some things you need to distinguish yourself from an "incompetent 'idea man'."
You should also talk a lot less about yourself. Most people don't care enough to read through several paragraphs defending your inexperience to figure out what your point is, the title had little to do with what you wanted from people, and the self-described term "Problem Solver" is another suspicious flag which falls into the "Idea Person" category.
You're right, my rhetorical style is rubbish. :)
I really appreciate you taking the time to help me on my way. I will work on some proof-of-concept apps that can help illustrate the approach I wish to take. Starting with the folder structure layout builder, image format conversion and layout/format validation. Then I'll see if it has something to it.
I'll post when I have some updates. Gotta go.