Hi All,
This weekend I checked in with several of the developers to see how they're progressing on features. Below is the updated status.
Of the 24 tasks, 4 have been resolved so far (3 are done, 1 is going to be held until the next release.) I know folks will hammer out more in the next couple weeks, but we'd probably be in a more comfortable position right now if we had 12 resolved (either done or held).
Could you review this list and see if I've missed some that are done, or if there are items that can be safely held for the next release?
Thanks, Bryce
Current Feature Work
ICC Preview =========== Jon Cruz is working on this. Plans to have feature to a finished point for the release.
* Update Release Notes
CMYK support ============ Jon Cruz is working on this. Plans to have feature to a finished point for the release.
* Update Release Notes
ArtLibre named icon and cursor loading ====================================== Jon Cruz is working on this. Plans to have feature to a finished point for the release.
* Update Release Notes
Palette editing and per-file color sets ======================================= Jon Cruz is working on this. Plans to have feature to a finished point for the release.
* Update Release Notes
Tablet Bugs =========== MentalGuy is working on this. Says for the release he wants to get these resolved.
Something drops tablet motion events on the floor while the button is held down. This occurs for some tools, but not with others. The bugs are quite annoying but weird. They don't affect all tablet users.
4/29 - Still underway
Brush size adjustment on zoom toggle for calligraphic pen ========================================================= MentalGuy is working on this and plans to have it to a finished point for the release.
Layer dialog ============ This is an important feature for the release, and on MentalGuy's todo list. However, work has been stuck getting Inkscape::LayerManager to compile due to a subtle detail with sigc::mem_fun(), and it's uncertain if there is sufficient time to unstick it and finish the feature prior to the release. Additional people's help may be needed here.
[Beyond the memory issue, are there other aspects to the layer dialog that others could help with, such as UI work or coding helper features or whatever? --bh]
* Update Release Notes
4/29 - Still under way
Fit Canvas to Selection - DONE ======================= This is a feature ACSpike has been working on, and plans to complete for the release. The patch is here:
http://www.ekips.org/comp/inkscape/inx/current.diff
ODG Format Support ================== Ishmal is working on this currently. Help is needed from someone who knows inkscape gradients, such as mental or bulia. He needs to know how to read gradient info from an SPGradient object.
DOM Support =========== Ishmal has been working on this. The newest code is all imported and builds. [Is there anything else needing to be done prior to release?]
SIOX Support ============ Ishmal has this over half done. The code is all imported and building, and the selection mechanism is now done. Getting Inkscape and SIOX intercommunication working, but this can be built as a filter to potrace, which simplifies things. The transformation issues reported previously have been sorted out, using a "confidence matrix".
Extensions ========== Ted is focusing on cleaning up extension parameters and felt he'd have this wrapped up by the end of the month. The plan is to have longer text (tool tips) available, and a few more widgets. More spacing in the autogui will be added to make it look nicer.
* Ted reports there is an unverified bug in the ordering of the effects in the menu, to be investigated.
The Extension Editor is further off, and not being planned for this release.
5/1 - Ted reports the feature is not yet working, but feels it shouldn't be a problem to get it fixed in the next couple weeks.
Snapping ======== Ralf is coming up to speed on this issue. Hopefully Carl can also shed light on things. On 4/26 Carl said he hopes to have a look at it over the coming week.
* Need to fix the freeze when dragging multiple selected objects: http://sourceforge.net/tracker/index.php?func=detail&aid=1429049&gro...
* Update Release Notes
Rendering Performance Speedup - DONE ============================= Andrius has a very interesting rendering speedup patch. The feature is complete and accepted for the release. There is one known issue to address with scrolling, but Andrius feels this can be fixed.
4/30 - Andrius reports this is now done, and no other issues are known.
Screenshots =========== Scislac has taken this task on, and plans to have it done for the release.
Two screenshots are done currently, and one more is in the works. There will be a call for more screenshots on the Deviant Art site.
Tutorials ========= Calligraphy is mostly done, and a few of the other updates to the other tutorials have been drafted but that stuff definitely needs more work. Should be possible to have them done by the end of April.
Man page should be current.
Bulia will update keys.xml shortly.
Note: The sooner these can be finalized, the sooner translators can get going on them.
Calligraphic interface tweak ============================ Bulia is working on this change requested by MentalGuy, and feels they are minor and should have no trouble completing for the release.
Windows font handling bugfixes - DONE ============================== Richard (cyreve) has completed these bug fixes and updated the release notes.
* Update ReleaseNotes
Python Extensions on Windows ============================ !!! No owner has been identified for this task !!!
Bulia reports that extensions that rely on PyXML still do not work on Windows. Due to the number of python extensions, this would be a major missing feature for Windows users.
Text/Fonts UI ============= deadchip (aka Milosz Derezynski <internalerror at gmail dot com>) has written a font lister Gtkmm class, to enable re-use of the font list. He is planning to write a font picker dialog, and rewrite the current font picker to use the font _listing_ class. This enables using normal Gtk components (ListStore, etc.) for accessing the font info. He plans to have this work done by May 1st, or May 15th at the latest.
Windows "dialogs on top" Patch for GTK ====================================== !!! No owner has been identified for this task !!!
This is not exactly an Inkscape-specific problem, since the code changes wouldn't be to Inkscape, but it would be nice to have it finally fixed. This 0.44 release effort may be a good vehicle to tie it to, but we won't hold up the release if it doesn't get done. Scislac had contacted the author previously.
* Send a reminder email to the author to find status on this
Undo/Redo Dialog - HOLD ================ Gustav Broberg (broberg at kth dot se) is planning to try to get the changes Mental suggested prior to the Feature Freeze.
We have a patch for this. Also needed is undo annotations.
4/30 - Gustav reports that due to more changes required than expected, this feature will be postponed until the next release.
New File Chooser in Export ========================== We have a patch for this, but there were some thoughts of embedding it in the export dialog directly. In the spirit of "patch first, discuss later", the best approach may be to stick in the current patch for 0.44, see what folks think, and do the embedding later.
Additional Release Tasks ======================== The following tasks will need to be done for the release, but are not required to be done prior to the Feature Freeze:
* Identify the list of must-fix bugs. To keep the freeze phase from dragging out, we will need to be very choosy in what we allow to be must-fix bugs.
* Set up a ReleaseChecklist wiki page or similar to keep track of The List.
* Designate 2 release maintainers.
* Keep and update the above list and encourage people to achieve completion of the items.
* Notify translators to complete translation work
* Wiki updates + Update Roadmap + Review/Update FAQ + Update InkscapeFeatures
* PR / marketing efforts + Plan efforts + Draft press release + Finalize press release + Send out press release [rejon]
* Packaging
On 5/1/06, Bryce Harrington <bryce@...961...> wrote:
ICC Preview
Jon Cruz is working on this. Plans to have feature to a finished point for the release.
CMYK support
Jon Cruz is working on this. Plans to have feature to a finished point for the release.
What exactly is this, apart from the existing ICC support for bitmaps? Just curious.
Brush size adjustment on zoom toggle for calligraphic pen
MentalGuy is working on this and plans to have it to a finished point for the release.
Mental, is this what you described - some kind of visual pen width changer? Do you think it will be ready for this release?
Fit Canvas to Selection - DONE
This is a feature ACSpike has been working on, and plans to complete for the release. The patch is here:
http://www.ekips.org/comp/inkscape/inx/current.diff
Hey, the patch was committed long ago :)
ODG Format Support
Ishmal is working on this currently. Help is needed from someone who knows inkscape gradients, such as mental or bulia. He needs to know how to read gradient info from an SPGradient object.
I'll try to show up on jabber one of these days; otherwise just drop me a mail.
Calligraphic interface tweak
Bulia is working on this change requested by MentalGuy, and feels they are minor and should have no trouble completing for the release.
This is done about a week ago.
New File Chooser in Export
We have a patch for this, but there were some thoughts of embedding it in the export dialog directly. In the spirit of "patch first, discuss later", the best approach may be to stick in the current patch for 0.44, see what folks think, and do the embedding later.
The patch was committed.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
On May 1, 2006, at 1:28 PM, bulia byak wrote:
On 5/1/06, Bryce Harrington <bryce@...961...> wrote:
ICC Preview
Jon Cruz is working on this. Plans to have feature to a finished point for the release.
CMYK support
Jon Cruz is working on this. Plans to have feature to a finished point for the release.
What exactly is this, apart from the existing ICC support for bitmaps? Just curious.
Well... now that we have <color-profile> support, we can add things to paint specifications.
Here's a base example drawn from some file I found on an examples page:
<text x="25" y="100" font-family="Verdana" font-size="20" fill="steelblue icc-color(cmyk, 0.8, 0.1745, 0.098, 0.2)">Happy Happy Print People</text>
The code for parsing that fill, and specifically for parsing the icc- color part, is in. There are a few things (mainly with the color choosers) that use a union in the paint spec instead of a few fields and flags. That is, the current code assumed you might have a color name *or* an icc-color part, but not that you might want both, which is what the spec gives.
Peter was working on purging that union. Once that's done, we will then be able to have full color support, including recalculating the rgb version (falling back to named values when present) as the icc values are changed. We probably won't have a lot of support in the UI, but it should give those people who care about print output the ability to use CMYK color for target printers.
And as far as ICC Preview goes, we can easily chain a profile for "your current display" along with one for "the target device" and get a preview of how things will look on something other than your box. (The calls are basically those used for the current <image> support). Oh, and the calls also allow for flagging out of gamut colors.
Bryce Harrington wrote:
Tablet Bugs
Something drops tablet motion events on the floor while the button is held down. This occurs for some tools, but not with others. The bugs are quite annoying but weird. They don't affect all tablet users.
I want to double check, is this tablet specific, general, or possibly an XFree/X.org issue? I know that there are some issues with X, which is why I ask.
Screenshots
Scislac has taken this task on, and plans to have it done for the release.
Two screenshots are done currently, and one more is in the works. There will be a call for more screenshots on the Deviant Art site.
Damn XGL... VNC isn't working with it and it's what I'm logged into at home. It won't be nearly as in-depth as what I had at home but I will send an email to the list and post on da in about an hour or two.
Tutorials
Calligraphy is mostly done, and a few of the other updates to the other tutorials have been drafted but that stuff definitely needs more work. Should be possible to have them done by the end of April.
I made quite a bit of progress over the weekend with updating the tutorials. I also have the ability to generate the svgs & html again thanks to everyone's help... but of course it isn't that easy. It makes it through the build process but it has errors along the way and the output is VERY broken. An example of the errors I get would be:
(inkscape:22685): Gdk-CRITICAL **: gdk_display_list_devices: assertion `GDK_IS_DISPLAY (display)' failed ** Message: error loading pixbuf at close
Windows "dialogs on top" Patch for GTK
!!! No owner has been identified for this task !!!
This is not exactly an Inkscape-specific problem, since the code changes wouldn't be to Inkscape, but it would be nice to have it finally fixed. This 0.44 release effort may be a good vehicle to tie it to, but we won't hold up the release if it doesn't get done. Scislac had contacted the author previously.
- Send a reminder email to the author to find status on this
I had contacted the author in the past, and most recently passed his contact info on to Bulia. I know that the last couple attempts I made to contact him were unsuccessful, so, hopefully Bulia has more luck. The dialogs on top patch will not be accepted by the GTK folk though in it's current state. The issue relates to dialog ownership and minimizing windows. Basically, since we have dialogs shared between multiple canvases, if you minimize a canvas it takes all dialogs with it. Tor didn't like that.
- Notify translators to complete translation work
I will notify them when I've committed all of my tutorial updates. That at least takes care of that aspect.
- PR / marketing efforts
- Plan efforts
- Draft press release
- Finalize press release
- Send out press release [rejon]
I will also do the typical PR on the deviantart front. (sorry no time to proof-read)
-Josh
Bryce Harrington wrote:
Extensions
Ted is focusing on cleaning up extension parameters and felt he'd have this wrapped up by the end of the month. The plan is to have longer text (tool tips) available, and a few more widgets. More spacing in the autogui will be added to make it look nicer.
- Ted reports there is an unverified bug in the ordering of the effects in the menu, to be investigated.
The Extension Editor is further off, and not being planned for this release.
5/1 - Ted reports the feature is not yet working, but feels it shouldn't be a problem to get it fixed in the next couple weeks.
I don't know what was contained in last night's committing spree by Ted, but IMHO the most needed addition to the autogui is an explanatory paragraph. Ted, if this isn't part of your immediate plans can you give me a few pointers so that I could try to hack it out before release?
Python Extensions on Windows
!!! No owner has been identified for this task !!!
Bulia reports that extensions that rely on PyXML still do not work on Windows. Due to the number of python extensions, this would be a major missing feature for Windows users.
I can not reproduce this report. I just tested Daniels build dated 0605020200 and Bob's build dated 0604281723 on a freshly built computer that has never seen the light of Python. I experienced no errors and the effects I tested functioned properly.
I'd like a few other opinions. The the black shell window that pops up when invoking python.exe has proven very confusing for the Wishbladers, who are representitive of our least technical users. The uninitiated often close this window and wonder why they see no effect. Would it be possible to replace a call to python.exe with a call to pythonw.exe and what would take the place of the black shell window that we currently use as a sort of progress indicator?
Aaron Spike
On Tue, 2 May 2006, Aaron Spike wrote:
I don't know what was contained in last night's committing spree by Ted, but IMHO the most needed addition to the autogui is an explanatory paragraph. Ted, if this isn't part of your immediate plans can you give me a few pointers so that I could try to hack it out before release?
Well, I wasn't think "explanatory paragraph", perhaps I misunderstood your previous e-mails. What I've been working on is tooltips for all the parameters in the autogui, and tooltips for the effects in the status bar. A whole paragraph sounds like a lot of screen real estate... Do you think that the two upgrade above would solve the same problem you're thinking about?
I'd like a few other opinions. The the black shell window that pops up when invoking python.exe has proven very confusing for the Wishbladers, who are representitive of our least technical users. The uninitiated often close this window and wonder why they see no effect. Would it be possible to replace a call to python.exe with a call to pythonw.exe and what would take the place of the black shell window that we currently use as a sort of progress indicator?
Well, changing what is called is a "one-liner" in script.cpp, there is a little table of how the various script types are called. That should be easy, but I'll let you make the change as I have no way to test it.
As far as a progress bar, yeah, I just haven't figured out a good way to do it. Ideally, I'd like to implement it in some way that the extension authors don't have to do it on their own. Though, they certainly could today. That wouldn't take into account other Inkscape tasks like loading and saving the document.
--Ted
ted@...11... wrote:
Well, I wasn't think "explanatory paragraph", perhaps I misunderstood your previous e-mails. What I've been working on is tooltips for all the parameters in the autogui, and tooltips for the effects in the status bar. A whole paragraph sounds like a lot of screen real estate... Do you think that the two upgrade above would solve the same problem you're thinking about?
No, I really think it needs an explanatory paragraph for some effects. Function plotter requires a selected rectangle (or did last time I checked). Something short like that could perhaps fit into the status bar. But Envelope (formerly Summer's Night) would likely require a short paragraph to explain. With no explanation there is very little likelyhood that a user will ever figure these out.
Well, changing what is called is a "one-liner" in script.cpp, there is a little table of how the various script types are called. That should be easy, but I'll let you make the change as I have no way to test it.
Someday. Right now the black window really helps to know that something is going on.
As far as a progress bar, yeah, I just haven't figured out a good way to do it.
Worst case scenario, how about a small dialog with a cancel button that reported the name of the effect and says that it is processing?
Aaron Spike
On Tue, 2 May 2006, Aaron Spike wrote:
No, I really think it needs an explanatory paragraph for some effects. Function plotter requires a selected rectangle (or did last time I checked). Something short like that could perhaps fit into the status bar. But Envelope (formerly Summer's Night) would likely require a short paragraph to explain. With no explanation there is very little likelyhood that a user will ever figure these out.
Okay, that's so much easier than what I was doing :) I'll add it as a parameter type. That way you have some control of where it gets placed in the dialog.
Worst case scenario, how about a small dialog with a cancel button that reported the name of the effect and says that it is processing?
That can be done, but the cancel button won't work as the execution thread is given to the script. But, it might look good :)
--Ted
Aaron Spike wrote:
Python Extensions on Windows
!!! No owner has been identified for this task !!!
Bulia reports that extensions that rely on PyXML still do not work on Windows. Due to the number of python extensions, this would be a major missing feature for Windows users.
I can not reproduce this report. I just tested Daniels build dated 0605020200 and Bob's build dated 0604281723 on a freshly built computer that has never seen the light of Python. I experienced no errors and the effects I tested functioned properly.
Python extensions work just fine, and have been working for months. I installed PyXML in the copy of python before adding it to the gtk bundle.
I suspect (but am not sure) that the problem might be that some users have python installed independently of Inkscape, and that the other python.exe is in the PATH, and that their copy of python does not have PyXML.
If this is the case, then I suggest that we experiment with launching python and perl scripts via the embedded interpreters rather than shelling out.
bob
On Tue, 2 May 2006, Bob Jamison wrote:
If this is the case, then I suggest that we experiment with launching python and perl scripts via the embedded interpreters rather than shelling out.
I would love it if someone would take this on. I think you should be able to do this and have it so that the scripts only get parsed once also. Make them execute a little faster. Plus, memory can be saved by using the load/unload functions which are already connected to an expiration timer.
Might be a good SoC project, it would probably need a little more than just this (could count for about half) -- but be creative :)
--Ted
participants (7)
-
unknown＠example.com -
Aaron Spike -
Bob Jamison -
Bryce Harrington -
bulia byak -
Jon A. Cruz -
Joshua A. Andler