2010/6/3 Chris Moffitt <[email protected]>: > Now that 0.9.1 is out the door, I wanted to outline my thoughts for the next > release. My purpose is to drive some discussion about what we should focus > on. > > 1. I would like to get the django csrf updates incorporated into Satchmo > trunk so it can use this improved feature. An initial fork has been started > here - https://bitbucket.org/dhmorgan/satchmo > > 2. Updates to the admin interface. I would really like to see some efforts > at making the admin interface a little more streamlined so that it isn't as > intimidating to a new user. I think some judicious use of jquery could > probably make some big steps. I'd also like to see some rudimentary > reporting so that the admin interface is more useful to store owner. I think a first and simple step is to integrate django-grapelli, wich is well designed, coded and eyes catchy. It gives some pretty inline admin and can remain optional. > > 3. Evaluating improvements to the product model to support improved product > model inheritance. There has been some good discussion here and I'd like to > see if we can make some of that a reality without massive > backwards-incompatible changes. Actually I think we need to make more simple and solid the main workflow/api when dealing with product. Separating what is really required for a product to exist (sku, pricing, title, qty, shipping rules), what is qualifying the product inheritance(abstract parent reference and variations) and what is needed for displaying a product(description, photos, attributes etc...). Well designing this part is the key for future elegant webservice api... Also I think backward incompatible changes will be unavoidable., but south migrations can help... The next part is to refactor products templates tags / context processors to ensure data processing and html rendering are really separated in a way we designers can only works on templates with a clear usage definition guide... > > 4. Figure out why caching-app-plugins does not work with the new caching > template loader. > > Other than those items, I'm sure we'll continue to focus on documentation, > bug fixes and translations. > > Some optional items: > - Bursar split. I'm still in favor of this but am not sure exactly how much > work is still needed there. Agree for that, payment and shipping must be separated to gain a whole of benefits with side projects... > - One of my pony requests is an improvement to the overall look and feel of > the default store. I like that there is minimal cruft that needs to be > removed from the default templates but I would prefer that Satchmo out of > the box looked more presentable to a customer and had some cleaner markup. > It would be cool if we could get some templates out there to jump start that > aspect of deploying Satchmo. Not sure, cause it's design and design is a subjective and value added job in this case... I really prefer to show in early customer meeting look what we can do with an exhaustive api/documentation and notes on workflow than a "look how does it's pretty"... A standard xhtml / css compliant clear and minimal design(white/grey/black + 1 blue color link) should do the job. I'll work on that when finding a few hours. > > Anyway, those are a few thoughts. I'm curious if anyone else has anything > major they would like to advocate for. Feel free to bring up here. A main context processor for cart and shipping in order to have contextual dict for displaying on all pages of the website what is the cart amount and simulate shipping based on logged or not information(get_lowest_shipping_cost). > > Thanks, > Chris > > -- > You received this message because you are subscribed to the Google Groups > "Satchmo users" 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/satchmo-users?hl=en. >
-- Franck Bret --------------------- 06 03 90 65 98 -- You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en.
