>I'm pretty sure the topic of reports has been addressed before on this list
Indeed, it has been addressed before, cause it's one of the satchmo weak points right now. I'm sure it's in django-devs agenda, among top feature requests. And I'm just asking about it again, to know the current state of the question. >Pardon my skepticism that code can reach perfection in merely 19 commits. I >tend to abstain from undocumented projects Regarding satchmo reporting tools, I recall Chris Moffitt saying it could be a starting point: http://bitbucket.org/chris1610/satchmo/issue/1166/canned-reports-in-satchmo >I do not say this flippantly but, having worked for many real-world clients, I >lack the imagination to envision a single tool for clients to generate the ad >hoc queries they inevitably require. I'm sure you can think of some basic -non ad hoc- basic queries, every single satchmo store would benefit of, specially if it's simple, maybe graphical, and you can get an idea of how is your business/products/ categories going (this year, month, week...) at first glance. Read "Rachel" comments: http://groups.google.com/group/satchmo-users/browse_thread/thread/96a6c8e9e914251a/ >Concrete ideas/proposals? To modify and adapt the admin according to satchmo needs, to begin with. Thanks for taking the time to reply, John. On Aug 4, 6:35 am, John-Scott Atlakson <[email protected]> wrote: > I'm pretty sure the topic of reports has been addressed before on this list. > > The particular project you point to has not been updated since November 2009, > which is a long time in the DVCS world. I must admit I have not tried to use > this code, perhaps it is the best thing ever and needs no improvement. Pardon > my skepticism that code can reach perfection in merely 19 commits. I tend to > abstain from undocumented projects ('populate with some values' does not > count) as I do not have the spare time to reverse engineer other's code. Even > if the code is 'free', my time is not. > > What do *you* have in mind to improve Satchmo in this respect? I do not say > this flippantly but, having worked for many real-world clients, I lack the > imagination to envision a single tool for clients to generate the ad hoc > queries they inevitably require. Every client seems to want something just > different enough from the others to make all your 'reusable' code not > reusable at all. > > Concrete ideas/proposals? > > On Aug 3, 2010, at 11:59 PM, Albert Pi wrote: > > > Anyone has tried > > this:http://github.com/trent/satchmo-reporting-tools/tree/master/reporting... > > ? > > > What do you have in mind to improve Satchmo in that aspect? > > > -- > > 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 > > athttp://groups.google.com/group/satchmo-users?hl=en. > > -- 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.
