On Aug 4, 2010, at 1:14 AM, Albert Pi wrote: >> 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. >
As a long time lurker on django-dev, I would certainly differ from the assessment that this is a 'top feature request' there. However, I am not discrediting your attempt to stir up discussion on this topic. If there are good ideas out there, lets have them! >> 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 am merely an end user and developer of custom Satchmo installs. I have no place to contradict what a core developer may deem desirable in the official distribution. That said, many of my frustrations with Satchmo is that it attempts to be everything so it takes some effort to ignore/disable its dependencies on 3rd party apps (django-registration et al). The reporting tools may very well turn out to be some sort of 'start'. Again, I have not dug through the undocumented code. I was just voicing skepticism on this point. > >> 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/ > Sure, I can imagine simple reports. I'm just saying that none of my real world clients request these sorts of reports. They always want very specific and aggregated reports that require bundling certain categories of products (but not other categories), etc. which requires a bit of automation and a bit of hard coding. I haven't yet seen the light on how I can abstract this into a one-size-fits-all. >> Concrete ideas/proposals? > To modify and adapt the admin according to satchmo needs, to begin > with. I'm completely in conceptual agreement with the recent proposal to spin off the Satchmo 'admin' interface from the Django admin interface. Again, I feel too often that apps like Satchmo and django-cms try to monkey patch their way into the admin or otherwise proceed as if they are the only app in town. Of course it's tempting to leverage the conveniences of the admin, I get that. But the reality is that these monkey patches do not always play well with others or even make for a compelling user experience. A few of my client's refuse to use the Satchmo bits of the admin, requiring us to manually manage products for them...extremely low margin, uninteresting work but the clients can't be bothered to sort out the undocumented and perplexing bits of the admin. So yes. Django's admin is a pretty decent CRUD interface. Satchmo could do with a tailored interface. Agreed. The trick is making concrete proposals and effectively channeling the few developers out there that have spare cycles to spend on this task. I wish I had that sort of time, but sadly I barely have time to submit patches for documentation typos/gaps at the moment. > > > Thanks for taking the time to reply, John. > > > -- 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.
