On Thu, Mar 8, 2012 at 2:08 PM, Abhiram Ampabathina <abhiram.ampabath...@gmail.com> wrote: > > Regarding the problem of relating two modules may not be a problem. We > could give or list every use of that module, when a user chooses that > particular module. The GUI shall support both the individual > functionality and also the relational functionality.
I'm sorry, I don't think I quite get what you mean when you say "relational functionality". Could you please explain this in more detail? > Yeah > gamma.sympy.org is beautiful in its own way. My point is we could > integrate documentation, test-environment and possibly we could render > the code of a particular module(both individual and related). The user > may feel to use documentation, testing and also look at the code, at > the same time. Ofcourse, the concept of a practical guide is > fantastic, we could also do it in that way. Yes, sounds nice. However, if the user is going to see the code, I'd suggest that this code should be somehow annotated, to make it easier to comprehend for a non-programmer even. > Attetion: How do we include new module, methods, packages in our Quick > guide? > Well the answer to that is we could give a nice backend(CMS like > thing) to the user to include a new module. > That backend takes the user through different steps to include a new > module. Like > > Step1. What module is that you want to include ? > Step2. Under which category is that you want to include? (Algebra, > Functions, Series etc.,) > Step3. Please check the existing modules in that category for any > duplication of your code?(Incase if they are duplicating it.) > Step4. If verified, please give sufficient description about that > module... > Step5. Please create a test environment by giving right inputs to your > code? > Step6. If ok, push the module. Sounds reasonable. I think it may be useful to allow every user to add his custom modules to his own "snapshot" in order to test them within the framework. If your project ends up being online, it may make sense to allow the user to make his modified snapshot publicly accessible, so that people could test the new modifications before including them into the official repository. > Sergiu, i am gonna quickly do another screenshot with the necessary > changes you have specified(with "The Practical Guide" like Thing). > I am sure its gonna take us somewhere to decide. Sure, cool. I'll look into the new screenshots in a moment. Sergiu -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
