-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of bulia byak Sent: donderdag 8 maart 2007 18:02 To: Jose Hevia Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Google Summer of Code Ideas
On 3/8/07, Jose Hevia <jose.francisco.hevia@...400...> wrote:
Another idea:
Add some kind of UI for effects. I found it really
difficult to use them.
Something like: -(human) select two objects and X effect. -(computer)The first object is not valid. It needs to be
four points long.
-(human) select two valid objects and X
Sure. Many effects need to be moved to the core and made much more interactive and friendly. If we're having them as effects it's not because we want them to stay that way. It's simply because for someone, it was much easier to code, say, Envelope in Python as an extension, and we decided that it's better for Inkscape to have this functionality via a clunky Envelope extension than to not have it at all.
A very quick reply, note that his is getting a bit off topic. At the moment, extensions specify which type of objects they require (rect, path, any, etc); however Inkscape seems to ignore this information. One step in the right direction would be for Inkscape to react on this information. For example: to use the function plotter you must have a rectangle selected. But Inkscape does not require you to, and therefore users think the function plotter does not work.
Summary: Inkscape should use the <object-type> specifier in INX-file.