Google Summer of Code Project Idea: PGF Export
Hey all,
I'm interested in creating a TeX exporter which uses PGF/Tikz instead of PSTricks, as PSTricks does not work well with pdflatex. Looking at the PSTricks code, it doesn't seem like this would be too terribly difficult to implement.
Another idea that I had was to streamline the gradient editor so that it's easier to use. For the most part, Inkscape has a fantastic GUI, but the current gradient editor is very cumbersome to use. Here's a quick and ugly mock-up for a more intuitive version: www.annoware.com/temp/gradmockup.png
What do you think?
Cheers, Caleb
Caleb Reach wrote:
I'm interested in creating a TeX exporter which uses PGF/Tikz instead of PSTricks, as PSTricks does not work well with pdflatex. Looking at the PSTricks code, it doesn't seem like this would be too terribly difficult to implement.
This could be good because it should fit within our recommendation that GSoC project be implemented outside of the Inkscape core as extensions to facilitate refactoring work. Have you taken a look at other output extensions in the Inkscape cope?
Another idea that I had was to streamline the gradient editor so that it's easier to use. For the most part, Inkscape has a fantastic GUI, but the current gradient editor is very cumbersome to use. Here's a quick and ugly mock-up for a more intuitive version: www.annoware.com/temp/gradmockup.png http://www.annoware.com/temp/gradmockup.png
Can you describe in detail the changes you would like to make to improve the gradient editor?
Aaron Spike
Nice! There are lots of requests for better TeX-related features in the bug tracker. You may want to troll through there to generate some ideas, and to see what sort of features other users are looking for. Citing user requests could also strengthen your application a lot...
For starters: https://bugs.launchpad.net/inkscape/+bug/170802 PS + LaTeX export https://bugs.launchpad.net/inkscape/+bug/171141 Richer text layout features https://bugs.launchpad.net/inkscape/+bug/172195 Export LaTeX with PGF/TikZ macros
-T
On Mon, Mar 24, 2008 at 6:45 PM, Aaron Spike <aaron@...749...> wrote:
Caleb Reach wrote:
I'm interested in creating a TeX exporter which uses PGF/Tikz instead of PSTricks, as PSTricks does not work well with pdflatex. Looking at the PSTricks code, it doesn't seem like this would be too terribly difficult to implement.
This could be good because it should fit within our recommendation that GSoC project be implemented outside of the Inkscape core as extensions to facilitate refactoring work. Have you taken a look at other output extensions in the Inkscape cope?
Another idea that I had was to streamline the gradient editor so that it's easier to use. For the most part, Inkscape has a fantastic GUI, but the current gradient editor is very cumbersome to use. Here's a quick and ugly mock-up for a more intuitive version: www.annoware.com/temp/gradmockup.png http://www.annoware.com/temp/gradmockup.png
Can you describe in detail the changes you would like to make to improve the gradient editor?
Aaron Spike
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Mon, Mar 24, 2008 at 9:35 PM, Caleb Reach <jtxx000@...400...> wrote:
Another idea that I had was to streamline the gradient editor so that it's easier to use. For the most part, Inkscape has a fantastic GUI, but the current gradient editor is very cumbersome to use. Here's a quick and ugly mock-up for a more intuitive version: www.annoware.com/temp/gradmockup.png
Gradient editor is going to be removed. You don't need it already. Everything is on canvas. The only reason it's not yet completely killed is that we need to add a numeric offset control for the selected stop to the Gradient tool controls. As soon as that is added, no ugly dialogs will remain for editing gradients.
bulia byak wrote:
On Mon, Mar 24, 2008 at 9:35 PM, Caleb Reach <jtxx000@...400...> wrote:
Another idea that I had was to streamline the gradient editor so that it's easier to use. For the most part, Inkscape has a fantastic GUI, but the current gradient editor is very cumbersome to use. Here's a quick and ugly mock-up for a more intuitive version: www.annoware.com/temp/gradmockup.png
Gradient editor is going to be removed. You don't need it already. Everything is on canvas. The only reason it's not yet completely killed is that we need to add a numeric offset control for the selected stop to the Gradient tool controls. As soon as that is added, no ugly dialogs will remain for editing gradients.
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org
What about setting the same gradient for multiple objects, so that you are able to edit the gradient for all those objects simultaneously? This doesn't require the gradient editor, and I think I'm for removing it, but there should be some control over whether the gradient is forked or not when assigning it to a new object.
Regards, Krzysztof Kosiński.
On Tue, Mar 25, 2008 at 10:48 PM, Krzysztof Kosiński wrote:
require the gradient editor, and I think I'm for removing it, but there should be some control over whether the gradient is forked or not when assigning it to a new object.
Preferences, MIsc tab, 2nd option from above ;-)
Alexandre
participants (6)
-
Aaron Spike -
Alexandre Prokoudine -
bulia byak -
Caleb Reach -
Krzysztof Kosiński -
Tom Davidson