developer docs? (and OC x CrC)
Posted: Mon Jul 13, 2009 2:17 pm
I'm having a tough time deciding between OC and CrC. I'm a developer and whichever I pick I'm going to have to work on a lot.
I looked at the documentation for OC, but it's really only a definition list. The quirks about any particular settings aren't even noted. I would have like to have seen a 'Common issues getting started' section at least. Searching through the forum I saw quite the number of people asking about the friendly URL aliases and although it's usually a missing "seo keyword" setting, there's not a faq mentioning it. The definition list only says "SEO Keyword: Keyword used for SEO". How about a 'duhhhh'. Stating the same thing back to you... in reverse? How about "This is the word that is placed in the url when the SEO Friendly URLs are enabled" with a hyperlink on "SEO Friendly URLs".
CrC's wiki is more developer oriented and goes into a little detail beyond "the folder named controller is the controller folder".
Neither OC and CrC's code has much (any) comments so looking at it is a mystery unless every line is analyzed. I'd like to see a definition list for all the functions, that would be usefull. PHPDoctor is pretty nice, but that's probably asking way to much.
OC is also EU centric. It's find that it's developed in the EU and everything is set to pounds and kilograms, but it would be nice if dollars and pounds (and maybe oz) were at least entered into the back end by default, so the starting user doesn't need to go figure out how to add that which could take a while and they would only need to do once. If it was already there, chances are the majority would never need to even bother figuring out how to add a new unit.
This is an open source project, but are there a lot of active developers? With the lack of any info for developers to use this, it doesn't seem very inviting. If there's only a couple [developers], how open are they to outside development and integrating good clean code into the core? How rapid is new development? I can understand that if there's only a couple people new feature requests could take a while, but if the code is just given to them, it should be rather quick to just integrate it.
I had already made a template for CrC and then I looked at the code and it doesn't use PHP5's class access specifiers or the Model piece of MVC. Then I looked at OC's code and found it cleaner, using models and class specifiers.
They both have a few features the other doesn't; all of which are usefull. I'd want to port whichever features over to whichever one I picked. Though they each do somethings in incompatable manners. For ex in OC, it has a beautiful page to add product options, yet it's hampered because options have to be created individually for all products. If there are 20 products all with the same options, like, clothing (sm/med/lg), they need to be entered over and over and over again.
I'm not sure how willing the developers of either cart would be to fix some of the issues. They might not see them as such, as they must have picked their methods in those directions at some point.
Both OC and CrC are significantly faster than what's out there and have much better code with the MVC. ZenCart and Magneto are so slow I want to shoot myself. And ZenCart's code makes me sick to my stomach. They also said the beta would be release soon... 8 months ago, and then said yeah, its ready now.. 2 months ago. They didn't do a 100% rewrite so it's still going to be crap.
Well, I've rambled on enough. Both carts are good, but they both need work.
I was just looking for other peoples opinions.
Thanks,
Adam
I looked at the documentation for OC, but it's really only a definition list. The quirks about any particular settings aren't even noted. I would have like to have seen a 'Common issues getting started' section at least. Searching through the forum I saw quite the number of people asking about the friendly URL aliases and although it's usually a missing "seo keyword" setting, there's not a faq mentioning it. The definition list only says "SEO Keyword: Keyword used for SEO". How about a 'duhhhh'. Stating the same thing back to you... in reverse? How about "This is the word that is placed in the url when the SEO Friendly URLs are enabled" with a hyperlink on "SEO Friendly URLs".
CrC's wiki is more developer oriented and goes into a little detail beyond "the folder named controller is the controller folder".
Neither OC and CrC's code has much (any) comments so looking at it is a mystery unless every line is analyzed. I'd like to see a definition list for all the functions, that would be usefull. PHPDoctor is pretty nice, but that's probably asking way to much.
OC is also EU centric. It's find that it's developed in the EU and everything is set to pounds and kilograms, but it would be nice if dollars and pounds (and maybe oz) were at least entered into the back end by default, so the starting user doesn't need to go figure out how to add that which could take a while and they would only need to do once. If it was already there, chances are the majority would never need to even bother figuring out how to add a new unit.
This is an open source project, but are there a lot of active developers? With the lack of any info for developers to use this, it doesn't seem very inviting. If there's only a couple [developers], how open are they to outside development and integrating good clean code into the core? How rapid is new development? I can understand that if there's only a couple people new feature requests could take a while, but if the code is just given to them, it should be rather quick to just integrate it.
I had already made a template for CrC and then I looked at the code and it doesn't use PHP5's class access specifiers or the Model piece of MVC. Then I looked at OC's code and found it cleaner, using models and class specifiers.
They both have a few features the other doesn't; all of which are usefull. I'd want to port whichever features over to whichever one I picked. Though they each do somethings in incompatable manners. For ex in OC, it has a beautiful page to add product options, yet it's hampered because options have to be created individually for all products. If there are 20 products all with the same options, like, clothing (sm/med/lg), they need to be entered over and over and over again.
I'm not sure how willing the developers of either cart would be to fix some of the issues. They might not see them as such, as they must have picked their methods in those directions at some point.
Both OC and CrC are significantly faster than what's out there and have much better code with the MVC. ZenCart and Magneto are so slow I want to shoot myself. And ZenCart's code makes me sick to my stomach. They also said the beta would be release soon... 8 months ago, and then said yeah, its ready now.. 2 months ago. They didn't do a 100% rewrite so it's still going to be crap.
Well, I've rambled on enough. Both carts are good, but they both need work.
I was just looking for other peoples opinions.
Thanks,
Adam