 It working? Yes. Thanks for having me here. My name is Manuel from Grayscale Publishing. I will actually talk tomorrow morning. This will be my regular talk at 10am or 10am. But I was very, very impatient, so I subscribed for this lighting talk. It will be dedicated to the Scribes community. So I hope they are arriving. Any Scribes programmers here? Yes? Only one? Well, so a little bit of boring introduction, and so they will see just the actually important part. This will be a short presentation of my most important feature request. As a designer, as a graphic designer working with Libre software, what would be the most kick-ass killer feature that would improve my workflow tremendously? Now, I'm making three assumptions on which I base this request. They are first assumption. Many graphic designers, especially working with Libre software on various platforms, know a bit about the basics of the CSS style sheet language. In the future, more and more of them will know about it, the younger generation of designers. And third assumption, most of the textiles we used to apply, like bold underline, padding here and there on top and bottom of the paragraph and so on, have an equivalent in CSS or will have in the future and will be maybe surpassed by it. So based on that logical conclusion, what we want to see in a graphical user interface is a code view where you can see the raw code of your style. We're almost there in Scribers, actually, so this is an example of this layout software and here you have the window where a style is defined. You have a number of properties and here I have a style which is named underlined and actually the only thing that I defined manually is the underlining. If you have a look at the source code of the Scribers file, which is an XML format, a bit like the stuff that Julien talked about this morning with Inkscape, you can see the code, the source code, XML, it's readable. And if you know where to look, you can find actually the style that we defined. It looks like that. It has a few parameters. One of them is underline, okay? It doesn't define a size. It doesn't define a typeface. That's what I can see here. But strangely in the user interface, there is a font and there is a size. Actually, this is not defined in this style. It's inherited from the default style. So actually this user interface is making things more complicated than either. The needed and what happens even worse if I define a font now, let's say I change the font family to the beautiful Chivo, which is the font of this presentation, then I see, okay, it's now defined in my code, but I cannot remove it anymore. I cannot undefine it or I would go through some very complicated process. I don't know if it's possible. There is no workflow for that. So what would be beautiful, really beautiful would be a code view, a very simple window where you see exactly the same thing as in the source code, the parameters that are in the style. So one, I would know what is there and two, I can remove what I don't want without a complicated interface, very simple and very familiar to people who know a bit web design and what would be really nice would be if the syntax would get as close as possible to CSS, like it would understand some CSS stuff. And I think it makes sense for the future as well. As we have heard yesterday during one talk, print design and electronic book design will merge at some point, very certainly the workflows will be very close. This software scribe is actually already does in the development versions, HTML, export, import, ePubExport is on the works. So there is already transformation. So it makes sense to do it, I think. Thank you. As we have four talks, I take two questions. Anyone? Question, should this be done? So in the first minute of the talk, all the scribus guys here arrived, so it's not that bad situation and they all agree, I think, with you. So do you need to show the first slide again? I think a code view would be the wrong answer to the real problem. So I think it should be like dialogue should be improved so it better tells you what is defined, what is not defined and also tells you if there is undefined property there. So there is some mismatch also between the underlying styling engine and the UE for editing styles. So that should be improved. And my personal idea for the future would be to probably go to CSS, XML plus CSS internally anyway. But I have been very inactive for the last half years, so it's nothing happening unfortunately. So can you answer the question? Would better interface to the style definition be the answer to your question? I don't believe so. I think you can make it more complicated but you cannot really make it much more simple. On the other hand, you cannot make it more simple than that. So I think this would be genuinely useful and also it would be a feature that doesn't exist in proprietary software I know of which have the same problems actually. Thanks. Thank you Manu. Hello. Buenos dias. Si tiene alguna pregunta en español, es ok. Pero hablo en inglés. So I'm from OSP. The band over there sort of centered around Brussels, group of designers doing design, graphic design, media design with free software only. Also redistributing our own work under free licenses. And today I'd like to talk a bit about the problems we have sharing our work among each other and to the wider audience at large. I'll first show you sort of the before. So something really powerful that we learned from the free software movement is that basically the tools we use to work together are also the same tools we used to share our work with a larger community. So we work putting all our files in Git repositories that have public access and interface to browse them to look at what's in there. Just like for example you can browse through all the code on GitHub and see who is working on a project and what people are doing without being involved in any way in this project. And this is a really nice way of sharing because people are using these tools to work together in a group and at the same time already opening up the work for everybody would be interested in either working together on a project or reusing projects. So here we see the Git server of Constant, the arts organization in Brussels, similar to Media Lab Rado here, where we have OSP projects and also projects of other groups related to Constant. And here already immediately we see something very particular. This interface is quite texty, so to say. So if we go to one of our works for example, like I saw. So this is an example of a project we're working on which has all our projects have many different kinds of media. So for example we might download images for inspiration. For this I don't think we, but we might have like Scribes files, Inkscape files. We might have a Django project in there. We have typefaces. Let's see, maybe better to show a project with a bit more different kinds of work in there. Like also workshop, like the workshop we did for merits, what was this called? Okay, that's right. More for logic. We work with a native speaker of the American, two minutes. So that means have to be very, so you see for example an OTF file in here, but there's Python files and this is where these interfaces sort of are really happy because they're meant to actually just show this stuff. So it's really inaccessible to people who know nothing of our workflow because they're like what's a Slav file? Is that like a recipe for salad or what's going on? I'm really bad at jokes. So we try to visualize this and this is basically a same kind of view. You see a different project we work on. You see the commits, so when we added new things to our repositories. This is really nice because this is a funding application. So now we are browsing through the repository and now we see for example we have actually visualized the different parts of it. So we see this is a PDF and we already see a little preview for the PDF and we can also load it up bigger with the screen is a bit small. Now we see a bigger preview of the PDF. So basically this is one minute. So basically what we did is we made these kind of previews for images, for fonts and for PDFs and for SVGs. And we would like to go further still in making also the diffs so seeing the changes because that's really important. So what happens within each step? And our code, we separate it really cleanly into an API and into the OSP website. So the underlying project can be built on and we are really, really looking forward to hearing of people interested and in working with other people. We won't unfortunately be at the, what's the name of the project, Interactivos. But we are very interested of people during this time want to know more about this project or hack on it or maybe reuse it for their own goals. So please do reach out. Thank you. So one question. If I say two questions, is that easier? No questions. Okay. Well, they're all around so... No? Please. Really no questions? Come on guys. Are you considering adding some sort of way to comment on the changes and everything? I think there would be a really useful feature to do that because it makes it more of a collaboration tool also. Like you did a comment and say, hey, but why did you do that? And then it's not just a conversation we have when we are at the same desk in Brussels but you can work better. But we haven't really found what's the most straightforward way. You could have it in a database next to it or you could try and really do it with a Git native object like a Git commentary. But it's really something that we'd be really interested in having, yes. Okay. This is a talk about a new project of the Krita and Krita Foundation called NUSIS. And first of all, I'm going to present myself. I am Ramon Miranda. I am a professional illustrator. This is my nickname, the SOC. And I usually own IRC by the Ramon and Nick. So if you want to talk with me, then you can do it. My role in free license open source applications is to make resources and to make video training and tutorials because not every people don't know how to use the software. The community needs good documentation and tutorials to teach all those people to understand how to use the programs to create the art. I also use my own artwork to promote the open source use. And that's all. At the Krita Foundation, we will have another talk with both, to speak better and explain better what is the Krita Foundation. But basically, it's a foundation to develop free graphic software, especially Krita, and to provide services for users and developers of Krita and to provide artists and studios with everything they need to create digital art. This is the project. This is the cover and studio color study to present you the project, which is called Music. This is what I want to teach you to make evocative images. The techniques you use, you need to understand and to manage to make this kind of image. The DVD covers two different aspects, which is the theory and the seed in action. And then we study, just for example, the essentials and the interface and how to use the doggers in a proper way to get a good workflow. And understanding the capacity of Krita to manage brass and jeans separately in a modular style. And also the common things like liar, mask. And the seed in action is the practical side of the DVD, which is based on basic exercises to understand better what we are learning. Just like sketching techniques and why we sketch it this way and what is inside our minds when we are sketching, like brainstorming. And use the values and mood to create a good atmosphere. And the typical face elements like eyes, noses, lips, this kind of stuff. And of course props like jewelry and metals, this kind of things. Much more, just the icons for presets to use inside Krita. The final image is in the native format for Krita and a set of presets that I used on the DVD. And of course your name on the credits to be a bit famous. This is the Krita interface. You can see it can be a bit complex if you get out all the doggers. But we can simplify just to understand how the interface works, difference the parts and explain in depth what does each part. The goal for this DVD is to teach you characters, design and atmosphere. Just from scratch to the final piece, seeing all the process to create finest artwork. And also the brainstorming process, which I think is important because usually we see a lot of finished images but we don't see the process. And this is one of the main parts. And this is two optional covers for the DVD, two images, which are not finished in the image. You can see the finished images. I have to do it. And this is the interface that I plan for the DVD. I think the simpler, the better. And it's clean just to teach you the principles by videos and popovers text that I think is going to be really easy to understand. This is not a project that you have to wait a long time. We have only two months to be released in the academy. So I have to be in the hurry. And you can pre-order now. How much is this DVD? Well, this DVD has a special price. We already have 50 pre-orders in a week, which is really cool. It's less than a pair of pants, 30 euros. And it's cheaper than a puppy. So thank you. Questions, yes. Dog, anyone? So, order the DVD, no? Order the DVD. Thank you. We are other pieces of OSP. Here are Pierre, Stephanie and Ludy. And we'd like to present you one of the work we are currently working on. This is a collaboration with a theatre based in Brussels. Here you can see the facade of the building. So we work with this theatre with the two directors of this theatre from three years now. And we work in there. We work with them in the theatre itself. So we made a logo. So this is a kind of mise-en-la-bime of old pieces of the previous logo they had. We customized some fonts for this. The logo is included into the boot of the B. In the UME font we customized. We made some posters. We played with graphics. Graph. We also draw flyers. So posters again. And a program. This one was made in Scribus. We forgot to put the first one which was made in context. This is a stamp to patch some SVG standards incompatibility from a multi-line inkscape text. It's not embedded in Scribus when we import an SVG. So the stamp is there to repair this. This is a website with image magic scripting. Every year we cook some new script after the images. A new version of the website. This is a kind of fencing or semi-program made in the LibreOffice character. Which was quite an adventurous experience. This is a summer tunnel to dive into a new season of last year. We work also every year with a letter painter. He beautifully interprets the UME font by hand on the wall of the Berlin. So we used a hell of tools in those two years. And now what to use? Yes, because you see maybe these four ones on the left are the ones we use for finalize to lay out at the end. Most of the PDF we output are finalized in Scribus. And it's an opportunity to thank everyone involved in these tools to have done it because we use it a lot. But for the new, for the third year, we want to do something around parallel universe. Kind of manga style booklet. Something quite heavy, maybe more than 100 pages. And this kind of drawing of it. We want something quite fluid or something liquid in the way the mix of pictures and typography can literally flow through the pages. So we also begin to lay out it with Scribus in this case. But we end up with some fluidity problem, liquidity problem. And because as, yes. Yeah, we can do Claudia and Manuel because this lightning talk is really, we had the idea to do it because of their talk. Yes, it's clearly a kind of answer or a testimony to Claudia and a different approach from Manuel. We live in the same apartment. So yesterday evening we were discussing, ah, okay, you do, you will do something about it. And because we have learned or we are learning HTML plus CSS, we say, okay, let's do it that way. Of course, it's the mess at some point. But if we list all the issues, it seems to be possible. Just at the beginning of the process. But yes, there is text flow now in multiple ways, but the CSS region is a good candidate. The PDF output is seen quite clean with WebKit. We have to try with Blink. You have to enable... Ludivine will show you. The press images are okay if you cheat a bit. Pagination could be added through the final output on PDF, but maybe other ways also. Through directly in CSS. Image flow, you can... It's what we call to say that it's cut out and CMIK images will find ways. We will show you just an experiment. It's just the beginning, so we are trying and playing with CSS and flowing stuff. And we have a lot of fun doing this. But we can already say that if you are experimenting with this, and we are really curious about some help because we already imagine we will have some problems. But what is interesting to show is the WebKit flex. Did you show how to enable this? It could be nice. This feature is not available on every browser, so we can use it on Chromium. And for this, you have to enable this feature so we can show you how to do this. It's quite... You have to look for WebKit because it's quite a long page of the explainer size. So what's nice is when the picture really flows into the different blocks, you can stretch the boxes. This is not so amazing to see, but we are really excited about this. Yes, it's amazing. As a designer, point of views. Okay, we can... So that's maybe an answer to the liquidity we were discussing yesterday, the beginning of an answer. At this point, we will work on it tomorrow. We take two questions and I take the honor to ask one. So how do you go to print from this? We will do a PDF, we will tune it and we will give it to the printer, basically. The thing is that, for example, this flex feature, when you export it, we can try it here, live, but then it's out of the boxes, everything is... The flowing is okay. Okay. Questions? No questions? Seriously? No questions? Okay. Thank you very much for an exciting prospect.