Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm looking to evaluate a few opensource e-commerce solutions. Are there any good alternatives to OSCommerce out there ?
I've looked at Thelia and Magento so far, are there any others that are worth looking at ?
They should be :
Free as in freedom
Easy to maintain / extend
Coded in PHP or Python (ideally, but I'm open-minded)
There are forks of OSCommerce such as CRELoaded, although that doesn't change much in terms of the basic calculus, it just may have some additional features that you care about.
I had experience with CRELoaded/OSCommerce. I found the code base pretty bad, with UI and logic mixed in everywhere, with no good control over the architecture and what code goes where.
You said free as in freedom, so I'm going to throw this out (although I think the technology is Java). Fry is not at all free as in beer (several hundred thousand short of free), but whatever they implement you get full source code (at least according to their sales pitch when I was looking at them). I suspected that this was because they used GPL stuff in their stack, but I don't know.
Another good one is Magento, I have heard good things about both. I also in the past used ClickCart Pro and it was nice a couple of years ago.
For those who may be interested, I ended up discovering and selecting PrestaShop.
It is coded in PHP/MySQL, highly configurable, very modular by design and the codebase is really clean and well-organized. A crapload of opensource and paying modules are available to extend the functionnality if needed.
zen cart
Very vague. Alternative in what way, in that they can also host products? Hav a CMS? Built in features? Configurable? Themable? What are you looking for?
Isn't this more of a google query?
How about using opencart ? It is released under GNU GPL
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I'm a React Native Developer from the past 7 months. And this is my first technology I'm working on. So, I recently got to know that there are certain coding rules which I wasn't following and was unaware of. I have two general programming questions.
So I just got to know from an inteview that one should create wrapper functions in their code, by which I can just call a single function which points to a module or a API.
Like wrapper functions, what else is a good practice in programming?
Since I never worked on Android/iOS before and directly jumped to React Native. I often find myself doing trial and erros when it comes to do styling in my application.
Or what is the right way to style an element without giving too much margin/padding, which I assume is wrong. Or what is the right way to style where the styling works the same in all devices. Can someone recommend me a right article or video or something for this styling issue?
This may well be the broadest question(s) on StackOverflow :-). Just a few suggestions for the first question.
1. Read :
Many books have been written, some down-to-earth (Clean Code, The Pragmatic Programmer, Code Complete, Refactoring, ...), some more theoretical (Structure and Interpretation of Computer Programs, ...).
2. Collaborate :
You can sollicit code reviews from colleagues, have pair-programming sessions with them, attend coding dojos or hackathons. All of these are ways to share and transfer knowledge among peers, are very helpful, and almost always fun, too.
3. Play :
Sites like codewars.com are great to let you experiment with huge numbers of coding challenges, risk-free, and with the bonus benefit of seeing the solutions of others (once you're done :-)).
Maybe it's worth posting the second question separately, with the appropriate title. Good luck!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Can anyone give advice, or point to any guides, on how to manage a community of open source software developers in writing api documentation?
A typical, unmanaged, starting point for most projects is to have a project wiki where anyone can freely create pages, add content to existing pages, edit existing content etc. The problem is that, despite people's best intentions, the wiki can easily end up being a disorganised, poorly written, incomplete, written in disparate voices etc etc.
So, what to do to improve the quality of the documentation?
I suspect a key ingredient is clear editorial/style guidelines, something similar to http://en.wikipedia.org/wiki/Wikipedia:Encyclopedic_style#Information_style_and_tone. Can anyone point to an example of such a guide tailored specifically to software apis?
Are there any other practices that people have found useful? E.g. form a core team of editors and accept that most documentation that gets added by the community will most likely need to be 'strongly edited'?
The short answer, that the solution is social/human and not technical. The way to get good documentation for any project is to have someone with time, in charge of doing high level organization for the documentation, and then being involved in the development and user communities to ensure that the documentation remains up to date and continues to address the problems and confusions that users typically have.
Community projects have accepted that you need point people (i.e. "managers," for aspects of the project like "translation," and "release," and for various components. The same thing needs to happen for documentation.
As for tools, Sphinx is really great though it's not "wiki like," exactly you can use whatever version control system your project is comfortable with to store documentation and configure your web server to rebuild the documentation following commits/updates/pushes. Which has always worked just fine for any project I've worked on/with.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I need to help a human rights organisation to setup a donation page at their website. They have tried PayPal and GlobalGiving and they found some glitches with these services like ceiling, transaction fees, etc. They want to setup their own mechanism. So what are the possible options and how much programming is needed? Is there any free-open source e-commerce or charity modules available?
Sounds like you are looking for something very customizable here, what I would recommend you is to do some custom coding or leverage solution like wufoo. You can build as simple as a form that whole bunch of fields and sends all these result to paypal or other payment gateways. Leveraging pre-built solution like wufoo is often recommended for non-technical people and/or simple, quick tasks like this.
(Alternatively) Most well-known applications like drupal, Joomal, wordpress (you name the rest) have fairly good support/module on this area, however, most of them require some degree of customizations and often become an overkill solution (mainly because of the learning curve).
You might look into Google Checkout. It's not free, but they do have an option tailored to non-profits (link).
The main benefit of going with them is that you won't need to set up a direct relationship with a CC merchant gateway, which can be a good sized hassle, especially for a smaller nonprofit. To me, the other benefit is that it keeps you far away from Raiser's Edge / Blackbaud, purveyors of some of the most awful donation pages I've ever had the misfortune to see or use.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I want to make a technical documentation of an existing web site for developers so that new developers can continue to work with it. In existing codes, little (or not at all) in-code comments or doc-strings are available (bad practice, I know). Yeah, I have seen some posts related to these. But those were not that detailed. Here are all my questions:
What to include?
How to organize? I mean, can you suggest some hierarchy so that new developers can easily get onto the track?
What are the best practices?
Can you show some samples?
How can it be made easy? Some ppl suggests wiki tool but I know nothing about it, will it be useful? Can you suggest any tool with some quick starting tutorial?
I have never made one. So I appreciate any kind of answer. Thanks in advance.
(Links will be helpful but please give a quick and lucid summary of it)
Quick and lucid:
Think of it like any paper.
What is the goal of the app (website)? [why?]
How does it achieve this goal?
What problems have arisen?
What problems could arise?
What could be expanded upon? [why?]
What problems could expansion cause? [why?]
What naming/formatting conventions should continue to be followed?
Outline format is great.
In addition to Nona's suggestion I would also say that it is important to break down the code and explain any conventions and intentions of the code so that there is uniformity between developers for things like ID values, CSS classes, and JavaScript function names. Be as specific as you determine necessary to prevent a new person to the team from reinventing work.
If you're looking for a quick way to get through your code, try .NET Reflector. It gives you a broad overview of all your classes, methods, properties, etc. so that you can write all the technical documentation you need without actually going through the files. It's super easy to browse through and it will even show you the code itself.
Have you thought about representing what is there with some UML notation? That's what UML is for! If the new developers are good then they should be able to understand it.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am developing an application that can be extended using "plug-ins". The plug-ins will be pretty basic, allowing developers to add new "actions" to my application.
What documentation/information do I need to provide so that developers can do what they need to?
I was thinking a short example and a general overview of how the application/plug-ins work?
You need to foster a sense of community. Things like:
sample code for more than one real plugin;
a getting started guide for plugin writers;
details on how to deploy a plugin and on how they are discovered by your application;
a wiki so that plugin writers can collaborate, and
an easy way for plugin authors to contribute their plugin
might help.
You also have to decide how detailed your API is going to be. IF you are offering a rich API, make sure to document it well, and to explicitly highlight directives (explicit "do" or "don't do" instructions).
Most users will not bother to read the documentation and figure out things from the name, or skim your docs. So it is best if you can avoid "surprising them", and if not, at least offer them a chance to find the problems.
Finally, err on the side of caution with checking correct use and send exceptions rather than counting on users meeting your instructions.
Also, think very well in advance on whether you truly expect anyone to use your plug-ins because the core product becomes a "hit".
It is very common to err on the side of optimism, and think that when you are writing a plug-in infrastructure that somebody will actually use it.
However, nobody is likely to write plugins before the core out-of-the-box offering is successful and popular. You may be better off publishing and distributing your own plugins before worrying about extensions by others.