To me the weakest point is total loss of control over communication flow, threads/widgets creation and signal processing. I occasionally get segfaults on the start, probably due to some race condition during this phase.
It is very interesting to reverse Spyder bit by bit, but sometimes the documentation is that I really want to see. Especially interprocess socket communication protocol, which can easily deadlock on attempt to reverse it by using print statements. My ideal long term wannabes to speed up development are: 1. interactive debug <canvas> that visualizes Spyder start up procedure and signals (processingjs in Qt HTML5 window, which receives 'pings' from probes scattered over the Spyder's body) 2. centralized debug panel for all signals (registration, processing, errors) 3. docs for communication protocol - with components, threads and examples That will help A LOT. =) In exchange I will try to complete my draft blog post for a better plugin API. -- anatoly t. On Tue, May 1, 2012 at 4:15 AM, Carlos Córdoba <[email protected]> wrote: > Hi Jed, > > I can help you with reviews and testing. Please publish a bookmark and we > can start to work from there. It'll be a great addition to the project > because I think right now our weakest point is debugging. > > Cheers, > Carlos > > El 30/04/12 12:24, Jed Ludlow escribió: > > > On Monday, April 30, 2012 1:01:08 AM UTC-6, anatoly techtonik wrote: >> >> As far as I can tell this task is free to take. I've updated Roadmap page >> with a correct link to all the issues we currently have >> at http://code.google.com/p/spyderlib/issues/list?q=MS=v2.2 >> > I have started work on a plugin to list breakpoints as suggested by issue > 318 since having such a list would make troubleshooting work on issues 845, > 955, 634, and 609 much easier. The first goal would be something very simple > that simply provides a listing of the breakpoint dictionary straight from > .spyder.ini. But I"ll be honest my time is very limited, and my progress > will be probably be slow. If there is a willing collaborator that might > speed things along. Anyone interested in pitching in? > -- > You received this message because you are subscribed to the Google Groups > "spyder" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/spyderlib/-/-OfCZXZLFQAJ. > 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/spyderlib?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "spyder" 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/spyderlib?hl=en. -- You received this message because you are subscribed to the Google Groups "spyder" 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/spyderlib?hl=en.
