What is the status of this ecommerce shop?

[TimvanSteenbergen]

Hi All, Just curious:does this ecommerce-shop have a open-source future? Does it still get developed. Or is the development finished and only in use at speckcommerce?

[merlindorin]

hi you, I'm not very closed to this project. I think that one of the main goals of "speck" is modularity... that's why you can find a lot of module at the root of speckcommerce and some commits are "recent" (10days).

I've some interest in this answer, modularity is interesting and we work in this way but I didn't found any POC or anything like that. Maybe I'm a dumb with search engines.

[shipleyr]

We have implemented our ecommerce solution using Speck at the base. We have made a fair amount of development into it and made some customisations to fit our ends (Mostly display related). It's a project that I think has a very good future but will only be so if people invest into the solution. Our site is at www.tcc-net.com if you fancy a look.

[merlindorin]

Hi shipleyr, did you have a working project on it? I think you haven't release the code on github?

To contribute on it... this will be hard for my company, too young to have a contribution on early project with big goals. But if a client need an answer that cannot be answered with other e-commerce, this can be interesting to work on it (zf2 power ^^ )

[shipleyr]

Ours is a commercial website so our updates are closed source. We have contributed the changes we have made back into the open source project where applicable.

Because the solution is very modular it is very simple to extend or augment the platform. Most of our customisations are specifically written as extension modules and as mentioned are closed source due to the commercial nature of the site.

[merlindorin]

I think that your customisation are related to TW bootstrap :p. I hope that you will have commercial success for your implementation.

Just a question, did you keep the hard relation between server-side and client-side?

[shipleyr]

Not sure I follow you at all.
How do you mean related to TW Bootstrap?
Also what are you referring to about a "hard relation between server-side and client-side"?

[merlindorin]

I have many things to say but a disastrous English :/
For TW Bootstrap, it was just a troll. Each new project create an interface based on Twitter Bootstrap. When you said "customisation", I was saying "Yet Another Twitter Bootstrap Implementation" :p. No judgement, just a little joke.

For the second point, it's just about how the web is usually built. Servers generate html code based on template (phtml, twig, smarty, etc) and I'm not found of that and I'm looking for projects with a strict separation between server and client. This can be usually called an engine and I didn't found any e-commerce engine that work only on webservice/restservice or other type of service with no html view. This is what I was meaning by "hard relationship".

So... my question was just : do you have a service approach of your "speck" implementation (what you called : customization")?

[shipleyr]

Our display related updates were to create an interface that didn't look like a traditional Bootstrap project. It's still based on bootstrap but just doesn't look like it. The generic theme built with Speck was intended to be a starting point and always meant to be replaced with an individual project's skin.

With the server/client comment. I am not sure how you would implement such an interface for this. The view has to come from somewhere so why not templates? It makes the most sense. I do have some requirements to write some rest calls for some future functionality but not right now. It would be simple stuff. If you required a rest interface you could extend the modules and write your own views or return everything as JSON if you required. Again as the project is very modular that kind of customisation would not be difficult.

Most of our customisation work was reated to display and the checkout process to utilise our payment provider and as we sell training products we needed the ability to capture delegate information during the checkout so we implemented that.

[merlindorin]

Ok, thank you for your reply.

About the server/client section, include the "html view" in a php project is not really good because templates are static with dynamic content based on data (ex : loop entries for blog). Why create a phtml file in server and not in html file with {{ }} and a regex like that "/{{(.+?)}}/g" (or near) for datas.

For example, in my company, I build our applications like that :
*2 projects
*PHP for business logic that provide data (REST w/ json)
*HTML/JS for the view and user logic in interface

JS call Data ---> PHP use business logic ---> Generate Response in Json ---> JS render data using a templating system like handlebar

If I have to plug a mobile, it's easy, I can use the rest interface. I can combine backbone with a localstorage to store data and ask for refresh if necessary. I don't use the server for rendering HTML page, this decrease time to response, etc.

For the point to expose services to rest is easy, that's true. Maybe if I have time I will try with apigilty.