 Now that you know how to deal with UI files, I have some ideas where you can start with very simple easy hacks to improve the situation for draw. And the presentation is about what user thinks of where we can improve our program. No presentation without a puppy and kitten. And the discussion started with a call from Michel Renon, who said eat your own dog food and use draw, for instance, to scribble the mock-ups. I immediately stop those ideas and say no, no, no. There are millions of arguments against using this. And in the end, I was thinking draw, who needs draw? It's just a graphic program. I don't want to do graphics. I have gimp and inkskip and all these things. But if I have no idea what is draw good for, the best is to ask the community. One option could have been if the community, they or the users in the community, they majority that they are not using draw that we could have a vision to drop it out of the program. Another idea could have been that users apply it for a simple drawings, just a few scribbles or whatever. So we prepared a survey, the darkened options are some just demographic questions. And I will report the two open free test questions where people can respond freely. So they were asked for what purpose to use liberal office right now. And I expected replies like I use it in my spare time to whatever, scribble a simple drawing or whatever. And say what kind of vision they have for the future. Where should we go to what and in which screws should we turn around to make it better to improve it. It could be that people tell us do not develop draw, skip it. So what happens is as usual in open source you expect with free text question to have just a small number of replies where you can get a quick impression but open source is sometimes kind of a problem and we got 2000 replies. If you get 2000 of answers like this it's getting a little bit complicated to analyze the results. People tell us what they do. So this question is about what purpose they are using. And they tell us flow charts, organograms and slides for presentation are included here and there. People tell about PDF files and of course they do have typos in there, brittle somewhere. We have got a large number of users because it was put on some kind of Russian side, quite Russia I'm not sure about but many were not native speakers. So it's not easy to get an impression out of a large number of those results. This one is one example. It could be as well a little bit smaller. Typically we get only one sentence or a few words. This one is sorted by a kind of organization that I applied to the answers in this case Visio. I try to get through the answers and analyze each report, each writing for the content. And if I get an impression that Visio would be a kind of competitor then people want to get draw as a similar program like Visio. I make a set of flag in Calc, I did it in Calc, set of flag for this particular answer and in the end I count it through. So what I want to show is that there are various combinations Visio, the first two one just make it like Visio, the next one says it could be also a replacement for AutoCAD. I think it's a good challenge for you that you know how UI files are created now. We make it like AutoCAD, the third or fourth one make it like flow charts, create flow charts from the program but have it also like Visio. And of course we get something completely else. People reply, I give up, it's a stupid program, it does not work for me. It is counter-intuitive, you cannot do simple tasks and really funny replies, fuck liberal office. It's all shit, only a few but it's very typical for this kind of replies. So what do you do is, so I collect, I guess all the threes are collected in a category of I do not use draw it all. So what we get as an output of this survey is the number of replies. The majority, it should be readable, majority says or has something like a scheme or a diagram as a idea what draw is being used for. It's still the purpose of draw. I use draw for creating schemes or diagrams. No answer is the second one categories or people give no reply, do not write anything in the survey as a report they told us the age or something like that. Next one, it should be simple, simple as a keyword which comes into mind, the usage of PDF. I was not aware before running this survey that draw is the first program to open PDF and edit, use draw as a PDF editor. Flow chart and so on, I guess you can read it through and it's still a good number of information that people have and it's not really, you cannot grasp it, where do we go in the future? Do we have to make it simpler or should we improve on URL usage just to take one of the answers? We need to boil it down even further to get some categories. First of all, I have again something for the next question about what people expect in the future and it's not that much more information in there. What they do now mostly should be improved for the future use. So if people use it for drawing schemes they want to get improvements there. Most want to have it a better import export filter to have an interoperability with draws and like. But they tell us a lot of various programs and formats that should be used. Usability is on the top, make it easier, simpler, more obvious what should be improved, what particular feature makes sense, be bug fixing, but on the next time is block diagrams, flow chart, mind maps, it's a combination of replies. People want to get improvements for those type of functionality. Next step to aggregate all the information into something that is handable is to group all the keywords into something like, for instance, block diagrams. It's obvious that if people report I use it for schemes and please make it better for working with flow charts, can use and improve on the block diagram tools. Reported a scheme diagram, UML, of course drawing UML diagrams and networking things is what people use their software architecture, some kind of I'm not a developer so I do not know for sure but what's the network or software diagram but it should be some kind of simple shape and connectors. Shape and connectors are what makes a block diagram basically. Mind maps and genograms are of course something similar. You draw a simple shape and connectors. What is needed to improve for block diagrams? By the way, a TDF number above its meta tickets that I created from the tickets I will show now where we should improve. It collects all the tickets that belongs to these block diagram features. It's a meta ticket. So improvements to connectors and labels, it's obvious. We have no, this is a picture, we have nothing to, no pointer, we have nothing to hop a line to make it clear that a line is going in over another. Other tools do have it, either as illustrated here as a hopping over the line or by intersection. In Visio you can easily create it or another feature which is illustrated here, the places where the connectors are put onto shape is something which could be improved. So improvements to connectors and labels, of course labels, if you label a connector it is sometimes written through the label and you cannot read it anymore. So you need to do this a workaround, put some background behind it or the line. It's not that nice. As you can see, there are a huge number of tickets written before that goes in this direction. Another big topic is outer generation of diagrams. People want just to enter the text and wants program to create the graphics. It is called smart diagrams or something like that in Microsoft. In other tools, it's a well-known feature and should be, yeah, simplifies the workflow. Standardization as part of it. There are types of diagrams. It should be created or it's kind of a style of a diagram that could be implemented here. To go a little bit faster. Besides from the block diagram, which is interesting, we have features to create a vector graphic. This example on the right side is a floor plan. It is something, it was added in the survey. Someone creates a floor plan with draw in a really high level configuration. It's amazing how much information you can put into the diagram and he says it's pretty easy. If you know how to do it, it might be easy. In this case, we need to deal with different issues. We do not need to care about connectors or labels. It's more about other features. First of all, competitors told us from in the survey are kind of Sarah designer, AutoCAD of course, CoralDraw. Pencil and Inkscape Pencil is a program to scribble mockups for UIs. If you know my kind of sketches for UI proposals, I do it with Balsamic Mockups, which is a well-known program. The open source version of it is Pencil. Inkscape of course is known as the big player in vector graphics. What do we need to improve? It is, first of all, Shapes Library. It's blinking. It should not blink. It's a cool feature of Impress. Improvement to the Shape Library, if you get more pre-designed dancers out of the Shapes Library, of the Gallery, you can do it much more quickly to create a nice vector graphics or a mockup. Layer handling. Layers are a really strange topic and it's very difficult. You can see it on the number of tickets that we have. It's kind of weird implemented in draw and people do not understand how to handle it. We need to simplify it. And something similar is blinking object selection, which is, it blinks, of course, it blinks because of the relevance. Object selection and alignment is an important thing. You cannot easily select objects in draw. If you have many of small pieces there, it's hard to select all these tiny things. You cannot use, no. We have those two last items are written in green because we made a proposal recently about how it could be solved. Perhaps it's time to show the idea. Vector graphics. So we have block diagrams. Vector graphics has two different visions for the future of draw. What else? What else comes later? First of all, vector graphic means we need brushes. Brushes are variation to lines. If you have a scribble, you don't want to show it as a clear line, but like a hand drawn thing that's done by a brush. So it is something which is contained in most vector diagrams or blurry line. Blurry like shadows. Realistic shadows is requested sometimes. And as you can see, shadow would be nice not only for vector graphics. You may want to have a shadow behind a shape for block diagrams. It's a nice feature. And it's kind of arbitrary selection of feature requests to a topic. But it's my way to organize the big topics. People request ARC as the lowest example on the right hand. We have measure lines for vertical or horizontal lines. And one request is for angels. Which would be really helpful if a draw goes into a cat direction. We have 3D effects. It's a cool thing and I'm afraid no one uses it. Draw could be a little bit exaggerated replacement for blender. You create a vector graphic. Okay, a little bit too far. Geographic maps, it's a cool thing. Some need to put it somewhere. Geographic maps is the idea to have a map in draw and to add some information as an overlay to the line, to the graph. Could be a future of draw. More. Now, block diagram, vector graphic. Next one is text processing. A lot of re-draws, what is draw being used for is to create something for dealing with text. Like creating posters, A0 posters, business card flyers, all the stuff which requires exact placement of text or images behind it, something like that. And of course, the PDF editing is part of the digital text processing. Would be a competitor to Letech and publisher Scribbles for instance. We need to improve on the PDF filter handling. The list is here limited. We have, I guess, much more tickets regarding PDF. Those are found in the draw category. Component like is draw. Table handling is requested a couple of times. So people are using tables in draw to organize the information. Kind of weird to me, but it is not that uncommon to do so. Styles, a big topic. Styles is something which should be improved at every variant's application because it makes it easier and quicker to get to a result. Combines a lot of weird properties into one result and you have one click interaction kind of. So what else, working with frames and text wrapping and all the features, how text is organized in a drawing is of interest. For instance, you want to run the text on a polygon to make it look like whatever. I have no good example, but it could be interesting. Number three or four, what else? Of course, it could be also a program to manipulate pixels. Which is, I guess, not really the first idea of draw, draw is not a pixel editor and it will never be. What we have is features to deal with images. You can add an image and change the contrast, brightness, all the like. But in the end, we need to decide to not do work regarding pixels. I think five minutes left for discussion is better than showing more.