Help Rebuild OsCommerce
Moderator: General Moderators
Heh.. nice diagram. The wiki is down at the moment (or just going slowly) so I'll post a few comments here:
1. Why does the admin need to see the same "Welcome Page" as the user?
2. Why does the admin need to see the same product catalogue as the user? (I imagine admin would prefer to see a more compact version without marketing fluff) (thinking about it, your diagram just says admin access the same data, so this point might be moot)
3. Ideally admin shouldn't have to approve orders, this should be done automagically on a successful return from the payment gateway. This could well be an option though.
4. Should admin be able to change the billing modular? I'd have thought that should be something for a developer/maintainer/installer of the application. (Unless that's who you mean by 'admin').
1. Why does the admin need to see the same "Welcome Page" as the user?
2. Why does the admin need to see the same product catalogue as the user? (I imagine admin would prefer to see a more compact version without marketing fluff) (thinking about it, your diagram just says admin access the same data, so this point might be moot)
3. Ideally admin shouldn't have to approve orders, this should be done automagically on a successful return from the payment gateway. This could well be an option though.
4. Should admin be able to change the billing modular? I'd have thought that should be something for a developer/maintainer/installer of the application. (Unless that's who you mean by 'admin').
I've made a "gantt chart" (sort, it's not really a proper one) outlining approximately the way I see the project going (click to enlarge):

Each box is 1 week .. so to get to a project release is 40 weeks in total. This is quite high pressure though .. if people want to work slower then now is really the time to say so. Clearly there's several things being written at once .. we'll need to divide up sections of the project.
Each box is 1 week .. so to get to a project release is 40 weeks in total. This is quite high pressure though .. if people want to work slower then now is really the time to say so. Clearly there's several things being written at once .. we'll need to divide up sections of the project.
1. 'Welcome Page' just means base index (i.e. docroot/index.php) it's kind of a superflous addition to the chart, I added only because the admin will need to access something before getting authenticated (thinking too far ahead!)onion2k wrote:Heh.. nice diagram. The wiki is down at the moment (or just going slowly) so I'll post a few comments here:
1. Why does the admin need to see the same "Welcome Page" as the user?
2. Why does the admin need to see the same product catalogue as the user? (I imagine admin would prefer to see a more compact version without marketing fluff) (thinking about it, your diagram just says admin access the same data, so this point might be moot)
3. Ideally admin shouldn't have to approve orders, this should be done automagically on a successful return from the payment gateway. This could well be an option though.
4. Should admin be able to change the billing modular? I'd have thought that should be something for a developer/maintainer/installer of the application. (Unless that's who you mean by 'admin').
2. Yeah, more of a 'check catalog is displaying correctly' than to actually view it as a user.
3. Optional is what I had in mind
4. I thought it might be worthwhile investigating if the client (shop owner) had the ability to change the billing module themselves, all of course via a nice easy to follow process via the site. The options will be limited to what modules they have installed, and any extras they will need assistance?
N.B. Administrator == Shop Owner.
I'm sorry about the problems with the WIKI. Dreamhost says they are having some network issues that neither they nor CISCO can solve so they are going to install a new core router that is 8 times more powerful tonight at 12CST. If this doesn't fix it I'll look into migrating all my sites to another host as these problems are not acceptable to me.
If you all want to pick out a domain name for this project I'll go ahead and buy it and host it, other wise we can continue to use a subfolder on Astions, it doesn't matter to me either way.
I still am unable to access devnetwork.net without using a proxy. It's rather annoying and I'm not sure that I 100% believe that it's my router blocking it. Other than the router control panel crashing I don't have any problems with it.
If you all want to pick out a domain name for this project I'll go ahead and buy it and host it, other wise we can continue to use a subfolder on Astions, it doesn't matter to me either way.
I still am unable to access devnetwork.net without using a proxy. It's rather annoying and I'm not sure that I 100% believe that it's my router blocking it. Other than the router control panel crashing I don't have any problems with it.
Onion: if I understand the chart correctly the skinning block is when the html/css skin-system is implemented? From the point of view as a html/css maintainer (volunteer) I would like to suggest that just as there are standards to follow in backend programming, standards on the front-end are important as well. That would mean absolutely perfectly clean output from the backend - if any html at all. Maybe some lean but semantic markup here and there, but nothing else.
That would assure the skinning part is loosely coupled (ha!) to the rest of the application. Which would make a big difference with a lot of existing software packages, as most of them are quite hard to change/modify design wise.
But I quess a lot depends also on the quality of the template system. I could assist in that part as well to make sure the front-end seperation and quality is assured.
That would assure the skinning part is loosely coupled (ha!) to the rest of the application. Which would make a big difference with a lot of existing software packages, as most of them are quite hard to change/modify design wise.
But I quess a lot depends also on the quality of the template system. I could assist in that part as well to make sure the front-end seperation and quality is assured.
Absolutely, the HTML team should have input to all of the other modules that output any HTML or CSS content. By "Skinning system" I meant the system to add new skins to the software, and the production of a few different demo skins to really show off how nice the application can look. This evening I'll write up exactly what I meant by each of the elements on the chart. And I'll add a couple that I've missed (store admin, and user management).matthijs wrote:Onion: if I understand the chart correctly the skinning block is when the html/css skin-system is implemented? From the point of view as a html/css maintainer (volunteer) I would like to suggest that just as there are standards to follow in backend programming, standards on the front-end are important as well. That would mean absolutely perfectly clean output from the backend - if any html at all. Maybe some lean but semantic markup here and there, but nothing else.
That would assure the skinning part is loosely coupled (ha!) to the rest of the application. Which would make a big difference with a lot of existing software packages, as most of them are quite hard to change/modify design wise.
But I quess a lot depends also on the quality of the template system. I could assist in that part as well to make sure the front-end seperation and quality is assured.
A kind offer, but I think we're better off using DevNetwork/Google/Sourceforge/etc where possible, and Astions has very kindly already set up the Wiki for us all. Having worked on a couple of open source projects in the past I've found that trusting anything to a single point of contact can be a bit unreliable. I'm not suggesting you would be, just learning from past experience.ok wrote:I can host the project on my server (and provide a *.1.vg domain).
I intend to start tracking activity on Monday next week (Sept 18th). I'm toying with the idea of writing a little app over the weekend to help.ok wrote:Your plan starts from this week? if not, when?
EDIT: I was bored.. http://www.ooer.com/onion/gantt.jpg .. made with .. http://www.ooer.com/onion/gantt.phps
