On 22 Jul, 11:41, rafael <[email protected]> wrote: > Hi Pavel, > > I will be in #getpaid so we can talk more. > > My usecase is similar to yours. T-shirts with different colours, sizes, > etc, wich imply in extra cost. > > Is Mikko example gatpaid.atshop? He wrote this addon (but not finished) > and this could be a starting point for us.. > > Two heads are always better then one and we could try to do this > together. I am sure Mikko will help also.. > > I have one question on your approach. Why is the product id independent > from the variation? Why not make getpaid generate a id for each > combination product/variation? > > About the product view, as your furniture is not in stock you don't have > a picture of every product/variation, right? How do you think you will > show those variations? > > I was thinking about a set of images and a slideshow that could display > the variations. Mikko mentioned xslt, that would be great to generate > svg files that could merge (in my case) tshirts and the stamps... > > Anyway, I will be hanging in getpaid. Ping me there so we can talk more. > > I am sending this email also to the dev list so more people can be up to > this issue and give suggestions... > > Thanks > > Rafael > > Em 21-07-2010 17:03, Pavel Bogdanovic escreveu: > > > Hi Rafael, > > sorry for delay. I have not startetd yet to develop. But I can explain > > shortly our usecase. > > > Our customer is selling furniture. These furniture can be delivered in > > several variations. But they are not at stock in all veriations. They > > will be produced according the choosen variation. But the price > > depends on the variation. f. e. a chair could be 180 EUR in black > > white and blue. But the other red variant costs 20 EUR surcharge. the > > product id is independent from the variation. > > When I start to code it I plan to start with the product view which is > > very case specific and does hopefully not touch getpaid. Mikko > > brainstormed that I should have any line item class which fits to my > > wishes and fits to getpaid. He showed me some code which could be an > > inspiration from his "variations". Sorry, I have to look into another > > notebook to find his example. > > Btw his usecase is different. He has a lot of products in different > > variations in stock. Every variation has a unique product id. > > I would really appreciate your help and would like to contribute to > > getpaid. I ll try to catch you at the irc tomorrow. > > > greetings > > Pavel > > ________________________________________ > > >> Hi Pavel, > > >> We have talked before in #getpaid. Mikko gave me your email because > >> we were discussing product variation implementation in getpaid. He told > >> me you are working on this. I would like to know the progress of this > >> work and if is there anything I can help. > >> I really think this should not be an add on product, but an out of > >> the box funcionality, because it means modifying getpaid.core. I have > >> not coded anything yet, because I was waiting some replys to the email I > >> sent to the getpaid-dev list. > >> I will be in #getpaid so we can discuss this... > > >> Thanks, > > >> Rafael
-- GetPaid for Plone: http://www.plonegetpaid.com (overview info) | http://code.google.com/p/getpaid (code and issue tracker) You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en?hl=en
