Hi. Since the topic is plugin development, and I'm also starting, I'd like to ask some questions too :-)
I just started what I believe will be a very large plugin. To be more exact, I intend to have plugins that will complement this plugin. Since this can become rather messy, I'd like a few directions on how to organize it be better fit with Spyder's development. I've noticed that non-core plugins are all mixed in a single folder. So far, I've created a subfolder in the spyderplugins dir, and intend to put it all there, with just a file in the root to load the other components. Does that sound right? I've also noticed that some resource are rather scattered (Linux-style). For example, the breakpoints plugin is in the spyderplugins dir, loading its GUI from the widgets subdir (which also contains GUIs for the profiler and pylint plugins), and loads some images from the /spyderlib/images dir. I understand those plugins are rather simple and can benefit from such an arrangement, but I'm unsure if that will fit my (probably more complex) plugin. I also designed my GUI with Qt Designer, which generates a .ui file. I noticed that Spyder itself doesn't use this approach. Is there an specific reason why that's so? From what I can tell, it's probably because of the plugin structure, and maybe because of the different PyQt/PySide UI code generators. Since I intend to have plugins that will complement my "core" plugin, are there any tips in this direction? Since I have to use another QMainWindow, is it possible that Spyder's pluggable approach is better in the long run? Cheers, Ronan -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib. For more options, visit https://groups.google.com/groups/opt_out.
