> 1. Adding a basic store reporting/dashboard functionality. Based on the > feedback on this list I think it does make sense for Satchmo to make it easy > to see a couple of things like low inventory, top sellers, top purchasers, > etc. I also think it should be easy for your end users to download sales > info into an Excel file for further analysis.
There seems to be some work on this functionality over at django-cms see http://www.django-cms.org/en/blog/2009/10/29/dashboard-proposal-update/ and http://groups.google.com/group/django-cms/browse_thread/thread/1369850f852151a7?hl=en >From a developers/integrators point of view it would be really useful if the dashboard is some kind of pluggable app which can be utilised by satchmo, django-cms and any other app. The issue with this I would think is that the dashboard already seems to have some traction over at django-cms and also django-cms, from my initial impressions, seems like rather than splitting things out into separate apps (ie django- bursar) its more about keeping things all internal. I could be totally wrong as I have only been reading the lists over there for a short time and only played round with django-cms for half a day or so, perhaps someone whose more familiar with django-cms would like to comment? So, definitely I would be interested in helping build some kind of pluggable dashboard. There is also a django app called django- dashboard however I have not used it and it seems to in its infancy and has no docs. It does appear to be pretty clean however, so could be a possibility? > 2. Updating the default store look and feel. I want to maintain the > simplicity of the current store but I agree that it could be jazzed up a bit > to make it more modern and more appealing. Definitely I think this should be a high priority. I think first off the current markup could do with some work so that the bulk of the look/feel can be done through CSS. At the moment there are quite a few issues with doing this. I'm definitely not an expert on this area, but I can do the work and make things look pretty nice however it might be nice if a designer can chip in with some designs which can be cut. > Admin interface updates - If you have done some nice customization of the > admin for product addition or reporting, I'd like to see it. I am in the process of writing about the things I did for my POS integration, I will post to this list when I have something that I think will be helpful. This work was not in the admin however perhaps it may be useful. Cheers Alex On Nov 1, 3:27 am, Chris Moffitt <[email protected]> wrote: > Now that things have settled down a bit from the 0.9 release, I'd like to > turn the discussion to 1.0. I have a few thoughts on what I'd like to see > but I'm open to feedback so please feel free to discuss. > > A few general guidelines: > - I would like to minimize the amount of backwards incompatible changes > between 0.9 and 1.0. The biggest changes I'd like to avoid are major db > schema changes. The 0.9 -> 1.0 upgrade path needs to be fairly > straightforward. > - I don't like setting dates for a release (because they tend to fly right > by) but I'd prefer to keep this development cycle fairly short i.e. 3-4 > months. Sometime around Pycon would be a nice time for 1.0 (although this > may depend on the Django release cycle) > - I am open to an intermediate release before 1.0. I'm going to wait and see > what the scope of change and updates looks like though. > - I still need to figure out whether this will be pegged to Django 1.1 or > 1.2 > > With those caveats in mind, here's what I'm thinking is in scope: > - Modifying Satchmo to use django-bursar for payment processing > - Also modifying Satchmo to use the new livesettings and keyedcache > implementations that Bruce has spun off from Satchmo. > - Minor feature updates and improvements > - Bug fixes, documentation and translation updates > > There are also a couple of other ideas I have that I would like to tackle > but need some help: > 1. Adding a basic store reporting/dashboard functionality. Based on the > feedback on this list I think it does make sense for Satchmo to make it easy > to see a couple of things like low inventory, top sellers, top purchasers, > etc. I also think it should be easy for your end users to download sales > info into an Excel file for further analysis. > 2. Updating the default store look and feel. I want to maintain the > simplicity of the current store but I agree that it could be jazzed up a bit > to make it more modern and more appealing. > 3. Pluggable invoice generating back ends. I know lots of people dislike > trml so it should be a bit easier to swap in your own generating backend. > 4. Wizards or other streamlined steps to add new products. I am resigning > myself to not drastically changing our product models but I do think we > could improve the whole product creation process with some streamlined admin > interface changes. > > So, what does this mean for you? Well, I could really use your help. See > the thoughts below: > > I am not a design guy so #2 will not happen without someone stepping forward > to lead the way. I will help all I can but someone else will need to lead > that charge. If you're so inclined, please chime in. > > Documentation updates - If you have specific ideas for new tutorials or doc > updates, please create a ticket and include some ideas. This ticket is a > great example > -http://bitbucket.org/chris1610/satchmo/issue/910/tutorials-on-using-s... > used the ideas to create the tutorial here > -http://www.satchmoproject.com/docs/svn/tutorial1.htmlI would be happy to > create more, I just need to make sure they are useful. > > Admin interface updates - If you have done some nice customization of the > admin for product addition or reporting, I'd like to see it. > > If you have other ideas or things you'd like to include, let me know. The > nice thing about our move to bitbucket is that there is a ver low barrier to > you committing. You can create your own fork, make your changes and let me > know when they're ready for inclusion. I can then easily review and pick and > choose what I want to include. It's a really nice model and some people have > already started doing it. I encourage others to do the same. > > This is a long email so I'll stop for now. Hopefully this will generate some > good discussion and more importantly identify some willing folks to step > forward and help us make 1.0 a solid foundation for Satchmo. > > -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 -~----------~----~----~----~------~----~------~--~---
