2011/12/5 Alex Valavanis <valavanisalex@...400...>:
Hi Josh,
I've been pretty busy at work lately, so I haven't had time to do much. I'm working on backporting some of the recent bug fixes to the downstream Ubuntu package, so hopefully this should help with 0.48.3/0.49 pre-release testing. I'll also (finally) sort out the upstream stable PPA in the near future, I hope.
From my perspective, as an inkscape-dev novice, I find it pretty
difficult to get involved with the development of new features because I'm not really familiar enough with the Inkscape source or gtk+. Although there is a nice to-do list of simple coding tasks[1] and a development roadmap,[2] it's possibly worth noting that there are currently only six blueprints and ~25 unfixed bugs actually tied to the 0.49 release. Personally, I'd find it much easier to get heavily involved in the project if (a) it's clear exactly what is required for each release and (b) there's an indication of how difficult each task is. Perhaps, therefore, it would be worth making more use of blueprints and targeting bugs/wishlist items to the forthcoming release so that we can more easily see our progress, and the light at the end of the tunnel. Also, some projects use a "bitesize" bug tag to indicate the easy items. This might be more maintainable/accessible than the current wiki page?
Best wishes,
AV
[1] http://wiki.inkscape.org/wiki/index.php/Janitorial_tasks [2] http://wiki.inkscape.org/wiki/index.php/Roadmap
I second this (thanks for the links Alex).
Something else, I noticed a memory leak when opening the object properties window. Frequently 40-70 kB of memory seems to be consumed and not released. Steps I used: - create a rectangle and select it - repeatedly: - click on the right-mouse button and select Object Properties - close the object properties window
When I look into the code, it seems to be due to the call to sp_attribute_table_set_object via sp_attribute_table_new. I can not exactly point out where the leak occurs, though when I see the files sp-attribute-widget.cpp and sp-attribute-widget.h, I thought about refactoring these files. If possible I'd like to: - refactor SPAttributeWidget and SPAttributeTable to real cpp classes derived from gtk::widget - get rid of the double pointers **attributes and **entries (making use of std::vector) - making use of std::string as opposed to c type strings (or is Glib::ustring better?)
Anyone working on this (sp-attribute-widget.cpp, object-attributes.cpp)? Any comments? And in case of troubles anyone who can help me?
Regards K