Hi, I wanna know What happened with this project. Are you still
working on it?? Did you decided to start again with Symfony2??
--
You received this message because you are subscribed to the Google Groups "sfshop" group.
To post to this group, send email to sfs...@googlegroups.com.
To unsubscribe from this group, send email to sfshop+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sfshop?hl=en.
The main collection right now is
https://github.com/docteurklein/Symfony2-e-commerce. There is also a
payment bundle https://github.com/schmittjoh/PaymentBundle with a
paypal Bundle to accompany it
https://github.com/schmittjoh/PayPalPaymentBundle I will be releasing
a Monetary and Currency Bundle late next week that will work with work
with both projects.
On Sun, Dec 12, 2010 at 2:15 AM, Alexandru-Emil Lupu
But beyond just that, I think by having a ProductBundle, it makes it
have any number of products and how that is implemented can be a very
personal choice. I'm talking with someone right now who would like to
see this in more of an SAP type environment (a product could be an
part in inventory that could get sold to a distributor or somewhere
internal to the company), which is very different from my current need
of selling digital products, or selling a seat for an event or the
obvious physical widget. However, with a common interface, you could
have a common way of dealing with any of products and you could have
an Amazon like store that sells any type of product.
For example in your CatelogBundle, your CatalogInterface would have a
dependency on the ProductInterface and both the CatalogInterface and
ProductInterface would have a depenceny on a CategoryInteface. By
using Dependency Injection you can configure which Product and
Category implementation you want to use in your CatalogBundle. If you
wanted to package three of those Models in your Bundle you could, but
having the flexibility to configure these in from independent an
ProductBundle and CategoryBundle is very powerful. Of course, with a
set CatalogInterface you could have different implementations of a
Catalog.
Basically, I see it as anything that is a component in the ecommerce
system, put a good interface on it, then you open the door for people
to cherry pick what they need. This is what happened on the
PaymentBundle. I saw Johannes was working on a PaymentBundle,
approached him about making it work with a larger system. I don't
know what he needs it for, doesn't matter, we can build an Auth.net or
Amazon Payment Bundle on top of it. He based his interface of
http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/index.jsp?topic=/com.ibm.commerce.api.doc/overview-summary.html
which I have started looking at to put things together. The interface
for the payment branch
https://github.com/IamPersistent/Symfony2-e-commerce/tree/payment I
am putting together is based on what I found here.
I'm thinking right now, that you have to have some type of workflow
listener/handler to handle the various steps involved in the commerce
experience. This would facilitate the various steps and rules that
you have for your specific situation. That is part of what I have
been working toward on my fork with the Order branch.
Much of this has been evolving by talking to various people so I'm
very open on all of this. I just want a system flexible enough that I
can use parts of it, literally, for any situation that come up.
I haven't talked to Florian
http://github.com/docteurklein/Symfony2-e-commerce about this yet, but
I would like to see the bundles pulled out of the main
Symfony2-e-commerce site and moved into individual bundles that are
submodules in the Symfony2-e-commerce system. I think this would help
with developers being able to implement the bigger picture. But
really the biggest thing right now is the interfaces that can work
between all of the various components in the system.
Richard
On Sun, Dec 12, 2010 at 3:51 AM, Alexandru-Emil Lupu
--
You received this message because you are subscribed to the Google Groups "sfshop" group.
To post to this group, send email to sfs...@googlegroups.com.
To unsubscribe from this group, send email to sfshop+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sfshop?hl=en.
Richard
Le 14/12/2010 01:04, Richard Shank a �crit :