Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I was wondering which php based carts will be the easiest to integrate with cakephp.
I've heard about bakesale but I have no info on it whether is up to par with magento, cubecart or other carts out there. It's been a while since they have updated info on bakesale (August 2008). So if anyone has any info how reliable and secure bakesale is or is it better to use other php carts any info wil be appreciated.
That depends on how tightly you want the cart integrated with the rest of your Cakephp app.
I have tried Bakesale for online store, and I ended up dumping it for ZenCart after too many complaints from the client. I tried bakesale because it seemed simple, but it was too simple. It is does not have all of the features of a Magento or ZenCart. Some parts of it are unfinished or just plain broken.
Bakesale is a nice Cakephp app but really misses the mark as an ecommerce solution.
The development on both bakesale and phpshop seem pretty dead. I would suggest building your cake app separate and then setting up something like store.mydomain.com using magento. There are still ways of getting them to talk to one another.
Recent, I've released a shopping cart plugin for CakePHP called Kaching found at http://code.google.com/p/kaching-php/. It's a middle ground between Magento and Bakesale. I found Magento tried to make every store fit into the same mold and Bakesale lacked features.
With Kaching you create the store's look and feel by interacting with Kaching's controllers. There is no need to build a store administration because one is provided.
I heard phpshop was being re-written as a Cake app - not sure how far along they are... or why they aren't writing it as a plugin!
Given that Magento is written in Zend, which like CakePHP is MVC framework, you might be better off writing the site in Zend. I've coded in both frameworks and they have a lot in common due to the MVC nature, though CakePHP certainly has more automagic functionality.
Cart plugin for CakePHP 2.0. Still in development but already useable, it follows coding standards and has unit tests. https://github.com/burzum/cart
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
can somebody suggest real world tutorials / example on react.js vue.js applications. The ones I find on youtube are too basic and lack logic. A real-world application consists of an admin dashboard and frontend. The tutorials you find on youtube are just basic crud applications.
is it just me or the kind of tutorials you find youtube are too basic and they lack logic ? because of this I find it really hard to learn and master new technologies. I struggled to learn and master web development even, coz there was too much basic tutorials out there but none of them were based on real world applications. It took me some time, and combining information from different sources to be able to build real world applications in php and be job ready.
Like when you work as a web developer you won't be building crud applications. You'll be building real applications with admin backend and frontend with business logic. I'm not roasting what programming channels do though. I think they they are doing a wonderful job and they still help us in a way. But I feel like there're few tutorials online that are based on real world projects. I'd like to hear somebody's opinion on this.
I'm even thinking of starting my own youtube channel that will strictly be based on real world applications like e-commerce stores, Item ordering sites, classifieds sites, property listing sites etc
The React website has a few good examples listed, the University of Helsinki also released a pretty solid introduction to web development website.
However, with those two basic examples listed, that's exactly what they are: basic. They're very simple examples to get people started with React (there are a ton of equivalents for Vue as well) and React alone. I think the issue you may be facing here is that the scope of the projects you're looking to see is a bit out of scale for what a basic React or Vue tutorial would have. This could even just be a problem with the specific wording that you're using, as there are a ton of great full stack projects utilizing React or Vue that you can find online. Examples of that may include looking through resources like Awesome Open Source's full stack open source projects list or some projects like Free Code Camp's full stack blog may be up your alley if you're looking for something to take you through piece by piece.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
New to front end development here. Discovered Yeoman, seems like a great tool. I worked through a tutorial and then completed a small project using Angular JS with a Node JS backend. To assist in looking at things from my perspective: at this point I don't know enough web development to abstract my approach, I just know the set of tools I can use to get something working. I know if I want to make a new web site I can generate a project using Yeoman, fiddle with the HTML/CSS, and make the content dynamic with Angular. It actually works pretty well.
However, I am curious as to what the other approaches to web development are. What are the alternatives to Angular JS? Is Angular.js the standard/common approach?
There are tons of Javascript frameworks out there. AngularJS is quite popular, but by no means the standard or common practice. Other popular frameworks you may want to look into are Meteor for full stack apps, ReactJS, Backbone, Ember, and many many more for front-end Javascript frameworks. Also, taking a step back, there are tons of other approaches to web development other than just considering what's on the front end (HTML, CSS and JS). For example, you can build whole websites without even touching javascript using Ruby on Rails. Other big frameworks are Python's Django, PHP with Drupal, Wordpress, Joomla, etc., and .NET / C# just to mention a few. Hope that gets your research started.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
We are a team of developers that have been doing web application programming for a few years. We are now starting over with a new project and we are aiming at making it a single page application. For the front end we are using angular. We are relatively familiar with angular, we know how to create services, directives, controllers ect. We know how to use built in services like $http and $resource and how to user routes (or states with ui-router) but we are stuck at a pretty early state on how to structure the application.
We are having a hard time finding good resources (blogs, videos, books) that tackle this general issue. Many posts have a very simple approach like:
"To build a SPA you need to use $http, this is how you do it, easy isn't it?"
They can be very good to understand the basics of each component but they do not explain hos to couple it all together. Questions we have are of the following type:
Do we build a central js object to represent the application state? If the application would be a back end for a web shop then the central object would probably be a company which has a list of products, each having a list of orders and each of them has a reference to the customer. Or do we split the representation of the application state in different objects? If so, how do we keep them in sync?
To display a form which edits an entity we create a route that loads a partial into a view and we populate the scope with the entity to edit. Do we fetch the entity from the back end? Or if we already have it in our js model, do we simply fetch it from there so that we don't need to make an http request?
There is a lot more that is unclear and I realize that there will not be a simple answer to any question, rather it is likely to be different design patterns with pros and cons. I do not expect the answers to all my questions as a response to this post, but rather I'd like to find some resource (like I said blog, video, book) that discuss these issues on an application-wide level. Some questions are angular-specific and some are more general around single page applications. Are there such resources?
I am relatively new to AngularJS myself, and I agree it is hard to find info that goes beyond the basics. So far, the most useful tutorials I have found are from Dan Wahlin.
http://weblogs.asp.net/dwahlin/archive/2013/04/12/video-tutorial-angularjs-fundamentals-in-60-ish-minutes.aspx
http://weblogs.asp.net/dwahlin/archive/2013/05/22/dynamically-loading-controllers-and-views-with-angularjs-and-requirejs.aspx
http://blogs.interfacett.com/getting-started-with-angularjs-video-series
The 60-ish minute tutorial was excellent, and his other stuff is good for getting you past the Hello World stage. I've also watch a couple presentations from Misko Hevery, the creator of Angular, and he is very good too.
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 7 years ago.
Improve this question
I'm almost finished working on a useful (at least, in my opinion) JavaScript plugin. Having seen and used many JavaScript packages, both freely licensed (JQuery, YUI, etc) and partly or fully commercially licensed I'm not sure what other factors dictate which license I should release my own under and how to support the plugin.
Some background information on my JavaScript plugin:
Similar audience and plugin size/impact to addthis.com, although slightly more niche. My plugin doesn't provide any analytics though.
Uses JQueryUI for user interface, can be expanded upon with there themeing components, etc.
No other similar tool out there (at least that has become popular).
Can be easily integrated in to a website.
Questions I have:
Should I launch a dedicated website for the plugin, or use something similar to Google Groups? Would a dedicated website bring more kudos perhaps?
Would a Creative Commons Non-Commercial license be a suitable license considering I'm a young developer and perhaps reputation building is more important than my bank managers happiness?
These are the 2 big questions that have been puzzling me for a while now, and I don't know anyone who has been in a similar situation :(
Thanks for any advice.
Considering you seem community, rather than cash driven .. the community will hold the key to what they find best, simplest and acceptable (and what works)
What do other plugin developers do? Take their lead. They set the convention and it determines how other people find your plugin. If a Firefox extension only had it's own site then I probably wouldn't find it.
What do others use? GPL? LGPL? What does jQuery use? Ask them why?
It might be worth using an online revision control tool like github or launchpad so people can contribute bug reports and help your development.
If I were you I would definitely use something like launchpad or google code.
You get integrated (community enabled):
source version control
bug tracking
...
for free.
Considering this library is aimed at other (web) developers a shiny website seems a lot less important then the convenient features above (in a known format).
And: congratulations on your first release, of course ;-)
About running site:
For me running dedicated website gives your product more professional look. Hosting on Google groups isn't good choice for all products: you can't build screenshots gallery, own blog, etc. You can build forum by youself if you need 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 4 years ago.
Improve this question
I'm evaluating DotNetNuke for a project in which an offshore team is going to be doing the development. In short, the application will be a community blogging platform with many similarities to stackoverflow except no questions, just posts. Posts may include an image or video, tags, use info, title, body, community vote (up or down) comments, hotness, and a few other details. They should be taggable, sortable, categorizeable (beyond what a single set of tags provide) In the future the site will carry forums, a calendar, and a couple of other features for which there are modules available for DotNetNuke. Additionally, this site will incorporate a user experience that will include a lot of custom skinning.
Thoughts?
Using a web application framework (such as DotNetNuke) has a ton of benefits to help you get up and running faster and do less work when creating custom functionality.
However, you have to realize that you're basically incorporating tons of code into your project that you may not be familiar with. No matter how good the code is and how easy the framework is to learn, there's still going to be a significant learning curve for you and your team.
Your decision making process (if you're still deciding whether or not to use DotNetNuke), should include (in addition to reading, talking and other general investigation):
Downloading the application from Codeplex and checking out the source.
Investigating the third party modules that are out there.
Downloading a free module or two that comes with source, and try to reverse engineer the creator's development process. How did she integrate with the framework, what features did she take advantage of, what was written from scratch?
One place where DotNetNuke (or any other framework with tons of extensions) available can really shine is taking existing extensions that are available and customize them. If you need to implement a given feature, check out the solutions in the third party extension community first. You can probably find one that gets you a good percentage of the way there and use it as a foundation for your feature.
For example, if you want a photo gallery on your site, you probably don't want to write it from scratch. There are three major photo galleries out there that sell the source code. The core gallery module is free, simple gallery is cheap, and the source for ultra media gallery is available for a reasonable amount compared to writing it yourself. Any of these could give you a good head start in implementing your features.