Re: [Inkscape-devel] Google Summer of Code 2012
Hello, I'm Yevgeny Lezhnin. I wish to submit to inkscape in gsoc 2012. I know c++ and can work with gtk+. I think I know how to make 'new from template' dialog: I can change menu entries in menus-skeleton.h verbs.cpp gdl-dock-bar.c gdl-switcher.c , and add new dialog source to dialogs folder. But I'm also interested in better svg standard coverage. I used inkscape for drawing diagrams in svg format, but there was some compatibility problems in firefox browser.
And another thing: is there any good bug for gtk+ interface developer?
Hi Yevgeny,
Glad to hear of your interest in Inkscape. You mention better SVG standard coverage as an interest. What in particular would you be interested in working on related to it? I'm primarily addressing this before the "new from template" dialog as it would be of higher priority to the project.
As for bugs, searching the tracker is the easiest way to find one of interest. I am sure we have a number of bugs that would be pretty straightforward fixes that relate to GTK. You may want to join our IRC channel to see if there is anyone around to chat with (I should be for a few hours at least).
Cheers, Josh
On Tue, Mar 27, 2012 at 6:41 AM, Yevgeny Lezhnin <z_lezhnin@...2835...> wrote:
Hello, I'm Yevgeny Lezhnin. I wish to submit to inkscape in gsoc 2012. I know c++ and can work with gtk+. I think I know how to make 'new from template' dialog: I can change menu entries in menus-skeleton.h verbs.cpp gdl-dock-bar.c gdl-switcher.c , and add new dialog source to dialogs folder. But I'm also interested in better svg standard coverage. I used inkscape for drawing diagrams in svg format, but there was some compatibility problems in firefox browser.
And another thing: is there any good bug for gtk+ interface developer?
This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 27.03.2012 23:25, Josh Andler wrote:
Hi Yevgeny,
Glad to hear of your interest in Inkscape. You mention better SVG standard coverage as an interest. What in particular would you be interested in working on related to it? I'm primarily addressing this before the "new from template" dialog as it would be of higher priority to the project.
As for bugs, searching the tracker is the easiest way to find one of interest. I am sure we have a number of bugs that would be pretty straightforward fixes that relate to GTK. You may want to join our IRC channel to see if there is anyone around to chat with (I should be for a few hours at least).
Cheers, Josh
I think Multiple page support is an interesting project and I think it is a clear task. Also I'm interested in some other points of the paragraph, but they are not so clear. Is there any big or noticeable problems with SVG compliance? About svg viewbox support: viewbox is an svg tag? What is the problem with it?
You think all four points in better svg standard coverage would be too much for the project?
On Tue, Mar 27, 2012 at 11:30 AM, Yevgeny Lezhnin <z_lezhnin@...2835...> wrote:
I think Multiple page support is an interesting project and I think it is a clear task. Also I'm interested in some other points of the paragraph, but they are not so clear. Is there any big or noticeable problems with SVG compliance? About svg viewbox support: viewbox is an svg tag? What is the problem with it?
You think all four points in better svg standard coverage would be too much for the project?
Problems with SVG compliance? Yes. Most notably would probably be our use of flowText and not having proper compliant fallbacks in place. With viewbox, from my understanding viewboxes themself are not really too hairy, but there's also a need for proper UI and sane canvas/rendering displaying. I think the mention of "Full" viewbox support is probably due to someone mentally including viewports and other related items.
Yes, all 4 main points and sub-points would be far too much for a GSoC project. Multiple Page support and the SVG 2.0 related items will require implementing proper fallback support since they are not in a finalized standard (and we are likely to be the only viewer supporting them for a while). The most sane way we've discussed is to use svg:switch and foreignElement. See the irc meeting notes at http://inkscape.13.n6.nabble.com/Minutes-of-the-Inkscape-team-IRC-meeting-25... specifically go to 2.1.1 to see a piece of discussion about it.
One thing to take into account when coming up with a proposal is if you have many other plans for the summer. Are there other work or travel plans that will be time consuming? Chances are that GSoC will be much more time consuming than you may be expecting (especially if you have not participated before).
Cheers, Josh
Hello. After discussing project proposal variants with Alexander Prokoudine I have decided, that there is a better project to participate: Text layout rewrite. I think I can work on this project and create code for treating normal SVG text right.
I found one small bug (1), but I don't sure that it is enough for application.
On Fri, 2012-03-30 at 00:04 +0700, Yevgeny Lezhnin wrote:
Hello. After discussing project proposal variants with Alexander Prokoudine I have decided, that there is a better project to participate: Text layout rewrite. I think I can work on this project and create code for treating normal SVG text right.
I found one small bug (1), but I don't sure that it is enough for application.
I began a Wiki page on redoing Inkscape's text handling.[1] The current implementation assumes that everything is flowed text and that normal text is just a special case where the text is flowed into an infinitely wide box. I'll call this a top-down approach. What I describe in the Wiki is a bottom-up approach. I think this is a simpler approach that more easily allows adding new features.
There is one thing to keep in mind: SVG 2 will have text flow into arbitrary shapes using the same mechanism that CSS will use[2]: CSS Exclusions[3] and CSS Regions[4]. Changes to our code should be compatible with these specs. It is too early to know how SVG will incorporate these specs so everything for the moment should be kept in the Inkscape name space.
Tav
[1] http://wiki.inkscape.org/wiki/index.php/TextRework [2] http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Input#Text_flow_to_... [3] http://dev.w3.org/csswg/css3-exclusions/ [4] http://dev.w3.org/csswg/css3-regions/
Thank you for the information. There are plenty of bugs related to floated text in launchpad. Is work on some of this bugs would be usefull for the project?
You are mentor, right? Alexandre told me, that you probably would be a mentor for this project. Also he told that inkscape problems with text, and floated text in particular are old problems.
Yevgeny Lezhnin
On 30.03.2012 01:26, Tavmjong Bah wrote:
I began a Wiki page on redoing Inkscape's text handling.[1] The current implementation assumes that everything is flowed text and that normal text is just a special case where the text is flowed into an infinitely wide box. I'll call this a top-down approach. What I describe in the Wiki is a bottom-up approach. I think this is a simpler approach that more easily allows adding new features.
There is one thing to keep in mind: SVG 2 will have text flow into arbitrary shapes using the same mechanism that CSS will use[2]: CSS Exclusions[3] and CSS Regions[4]. Changes to our code should be compatible with these specs. It is too early to know how SVG will incorporate these specs so everything for the moment should be kept in the Inkscape name space.
Tav[1] http://wiki.inkscape.org/wiki/index.php/TextRework [2] http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Input#Text_flow_to_... [3] http://dev.w3.org/csswg/css3-exclusions/ [4] http://dev.w3.org/csswg/css3-regions/
Hello, I'm writing project project, here it is in attachment. Is it all right?
My project is text layout rewrite, main point is to treat normal svg text as basic format of the text. Floated text should be only special format. Now it is otherwise: floated text is basic format, if we need normal text we get floating text, that flowed into an infinitely wide box. New approach will allow to add new features easier. This work is very important, because text is needed at almost every scheme or diagram. And text realization that inkscape has now is not the best, users are suffering from text input logic bugs. Now inkscape is known for failing in text treatment. So I think, that this project is one of the possibilities to make something useful to opensource community.
Other part is adding some features such as hyphens and indentation to floated text. New text implementation should make possible adding new features to text treatment.
On Thu, Mar 29, 2012 at 10:04 AM, Yevgeny Lezhnin <z_lezhnin@...2835...> wrote:
Hello. After discussing project proposal variants with Alexander Prokoudine I have decided, that there is a better project to participate: Text layout rewrite. I think I can work on this project and create code for treating normal SVG text right.
This would be excellent and I'm glad Tav responded with some great starter info for you.
I found one small bug (1), but I don't sure that it is enough for application.
We do require two accepted patches before you're eligible to participate with our project. It's actually our requirement for everyone, once a person has two accepted patches we grant commit access (if the person desires). Do note though, if you meet the requirements for SoC and are accepted, you would be working in a branch during the summer, not trunk. :)
Cheers, Josh
participants (3)
-
Josh Andler -
Tavmjong Bah -
Yevgeny Lezhnin