Graphicslab's blog http://graphicslab.org/blog This is the Graphicslab's blog en-us Sat, 26 Jul 2014 03:02:54 GMT Sat, 26 Jul 2014 03:02:54 GMT ale@graphicslab.org ale@graphicslab.org a.l.e http://graphicslab.org/blog/ 14. Juni 2013 ab 20:00 - An Open Evening with Open Graphics @ Zurich ![CDATA[Grafiklabor]]![CDATA[ Fonts]] Wed, 12 Jun 2013 20:00:00 GMT An Open Evening with Open Graphics

  1. Juni 2013
    ab 20:00

Im Dock 18
Rote Fabrik
Zürich

Mit

Ale Rimoldi
(Coder und Community-Builder. Grafiklabor, Scribus, LGM)

Manuel Schmalstieg
(Designer und Publizist. Greyscale Press, Low-Rez.tv) präsentieren

Moderation
Mario Purkathofer

Freier Eintritt, kühles Bier.

Poster 1: The European Map of FLOSS

Die Idee ist kürzlich im Gespräch zwischen Manuel Schmalstieg und Julien Deswaef am Libre Graphics Meeting (LGM) in Madrid enstanden: Lasst uns eine europaweite, politische Karte der Freien Software zeichnen. Mit folgender Faustregel: Nur ein Projekt pro Nation. Welche freie Software steht für die Schweiz? MyPaint oder TYPO3 oder Cyberduck oder OpenJustitia oder gar Vim?...

Poster 2: Libre Type Klassifizierung

Wir schreiben das Jahr 2013 und der Hype um Webfonts und Freie Schriften tobt. Höchste Zeit, unser Wissen über Klassifizierung der Schriftarten auf den neusten Stand zu brigen. Wer trennt Renaissance-Antiqua von Barock-Antiqua, Serifenlose Linear-Antiqua von Amerikanischer Grotesk? Oder müssen gar neue (Unter-)Kategorien entworfen werden?

Wer mitmacht, wird mit einem A0 Poster belohnt.

Printed Books oder eBooks: Wohin führt uns die DTP-Zukunft?

Immer mehr Leute lesen Bücher und Zeitschriften auf digitalen Geräten. Was wird dann in 20 Jahren noch gedruckt? Und wie können wir unsere Werkzeuge für die Zukunft vorbereiten?

Was ist sonst noch geplant?

  • Exklusiv-Bericht vom LGM 2013 (Libre Graphics Meeting) in Madrid, mit Video-Ausschnitten der besten Talks.
  • Vorankündigung zum LGM 2014.
  • CD-Rohlinge mit ausgewählten (und legalen!) Libre Fonts (darunter ein rarer proportionaler Schnitt der Kult-Monospace-Font Inconsolata).
]]>
a.l.e http://graphicslab.org/blog/ Grafiklabor am 5. Juni 2013: Mypaint ![CDATA[Mypaint]] Mon, 03 Jun 2013 23:00:00 GMT Scribus Scripting with Python Mypaint,

morgen Abend, den 5. Juni 2013, findet an der

Stampfenbachstrasse 69
Raum F11/F12 der ETHZ

ein MyPaint Workshop zusammen mit Martin, dem Author des Programms statt.

Wenn du also gerne malst und dir einmal aus erster Hand die wichtigsten Funktionen erklären lassen möchtest, bist du gerne eingeladen um 18.00 Uhr vorbeizukommen.

]]>
a.l.e http://graphicslab.org/blog/Grafiklabor-Scribus-New-Scripter-Script Grafiklabor: The first Script ![CDATA[Grafiklabor]]![CDATA[ Scribus]]![CDATA[ Script]] Sun, 06 Jan 2013 20:00:00 GMT Four brave scripters in Zurich, one in Rennes and one chatting from home have spent their Sunday afternoon by trying to write the first script with the Scribus new Scripter.

The goals was to port the Calendar script to the new API.

The results are mixed: while we still don't have a new Calendar script, we have learned a lot of things:

  • We could create a script that launches a dialog created with Qt Designer.
  • We have created a github repository where we can continue to work on the script
  • Short after the end of the workshop I've found a big error we made and could get the Scripter to create a new document, which was our first step.
  • But, the error messages the Scripter is returning are not easy to understand, the output is way too verbose and the window where they're shown cannot be resized!
  • Also, there is no shortcut to re-launch the last script
  • The warning about the includes being "unsafe" is disturbing. If there should be such a warning, then it should only be shown once per script (and user) not on each launch.

And there are also a few smaller issues we faced: - We could only load an .ui file by entering it's full path, not it's path relative to the running script - We could not find a way to query Python or the Scripter for the path of the current script. - It's not possible to copy paste the errors from the Python console in Scribus - The "Dialogs" API is not documented - Scripter.dialogs.newDocument is not callable as a function. - There seems to be no way to create a new paragraph style - There seems to be no way to query the current unit (cm, mm, ...) and set a specific one - There are no constants for expressing the units (Scripter.UNIT_POINTS)

Voilà, the work on the scripter is not over! I've created a "scripter" repository on the Scribus git server and I'm working to program all the commands needed for the calendar script.

]]>
a.l.e http://graphicslab.org/blog/ Grafiklabor on January 6th 2013: Scribus Scripting with Python ![CDATA[Scribus]] Sat, 01 Jan 2011 23:00:00 GMT Scribus Scripting with Python

Sunday, January 6th 2013
14:00 - 18:00

Grafiklabor, Zurich
Creativ Design, Rennes
+ Online participation

One of the nice features of Scribus, is that you can write simple Python scripts and create new features or automate repetitive tasks.

During this workshop we will discover the new Scripter engine Henning and Jain have been working on, over the last few years. It is now part of Scribus 1.5.0svn and it will be the default Scripter engine shipped with Scribus 1.6.

We will first have a look at the concepts behind the Scripter and find the main differences with the current Engine.

In a second step we will take the existing Calendar script - which is distributed with Scribus -, rewrite it to use the new Scripter and publish it in the Scribus Wiki. Depending on the number of participants we will work all together by using a collaborative text editor or split the script in tasks and define small groups working on each tasks.

If there is some time left, we will learn how to add new commands to the new Scripter.

We will keep a log of the workshop and publish our notes on the new Scripter as a blog article.

The Workshop will be both a real life event at Grafiklabor, Dock 18 in Zurich, Switzerland and at Creativ Design in Rennes, France. You will also be able to attend as an online participant.

All you need is:

  • a computer with Linux installed
  • Scribus 1.5.0svn with the new Scripter
    • compiled with the following cmake parameters: cmake -DCMAKEINSTALLPREFIX:PATH=/home/yourname/bin/scribus -DWANTDEBUG=1 -DWANTSCRIPTER2=1 -DWANTGUILANG="en_GB;de;fr;it;en" ..
    • if it can help, we can provide a PPA that you can install in Ubuntu and Linux Mint.

At both venues, we will provide laptops with the needed software installed.

To help us with organizing, you're invited to register at

http://doodle.com/ei6xc5euy3un5p8g

]]>
a.l.e http://graphicslab.org/blog/Grafiklabor-Programm-Winter-2012-2013 Grafiklabor: Programm im Winter 2012/13 ![CDATA[Grafiklabor]] Sat, 06 Oct 2012 22:00:00 GMT Sonntag treffen wir uns wieder im Dock 18 und beschäftigen uns mit Scribus und der Gestaltung von Zeitschriften, Newslettern und Vereinsblättern.

Wir werden unsere Erfahrung austauschen und dann fassen wir unsere Gedanken einerseits in einem "prägnanten" How-To und anderseits in einer Feature-(Wunsch)Liste zusammen.

Bis am Sonntag ab 14 Uhr im Dock 18!

Hier noch das Programm für's Winter 2012/13:

7.10.2012 Mini booksprint: Zeitschriftgestalten mit Scribus

4.11.2012 Übersetzungssprint: Einführung in Gimp aus dem Französischen übersetzen

2.12.2012 Freiegrafiksoftware: Überblick und Installparty

6.1.2012 Public Domain Jam

3.02.2012 Einsatz freier Grafiksoftware im Unterricht

]]>
a.l.e http://graphicslab.org/blog/ Compiling a Scribus Git branch ![CDATA[Scribus]] Wed, 05 Sep 2012 13:00:00 GMT A few weeks ago, Anil announced on the mailing list that he has worked on Pierre's code and got indic scripts to work with the current code. Since then, lot of people have been asking how to get the code and test it. This is a good chance to write a short article explaining how to compile Scribus, for people that only want to test it and not contribute code!

If you want to follow the steps described in this article you will need: - a recent Ubuntu or Debian testing, - at least 1 GB of RAM - 3 GB of free hard disk space - a multicore processor - basic knowledge about the terminal (cd, mkdir, rm, ls, pwd, ...)

In the future, I plan other articles for other distributions and even on compiling Scribus without having to touch the terminal... but let's start with this one!

Finally, if you need help, just drop in our IRC channel and yuo will find somebody to hold your hand: irc://irc.freenode.net or http://wiki.scribus.net/canvas/Special:WebChat .

The steps you will go through

Let's first summarize what you will need to do: - getting all the software and libraries needed to compile Scribus, - getting the Scribus source code, - compiling Scribus, - running the development version of Scribus.

Getting all you need

The Linux distributions provide everything you need to compile new software, but often it is not installed by default. You will need: - a compiler (gcc) and the make tools, - the Qt development tools, - the header files that describe how Scribus can use the external libraries it needs, - git to check out the Scribus code.

Linux knows what software can be installed by looking at the content of repositories. In Debian and Ubuntu this list is located in the file /etc/apt/sources.list. The first step is to make sure that you the source packages are included: - On Debian make sure that you have a line like deb-src http://ftp.ch.debian.org/debian/ wheezy main non-free contrib in your /etc/apt/sources.list . In order to make sure that all the repositories are up to date you should update the list of avalaible software by

$ sudo apt-get update
- On Ubuntu start the "Software sources" application and make sure that in the "Ubuntu Software" tab has the check box for "Source Code" checked. You can find more help on adding repositories in the Ubuntu help pages: https://help.ubuntu.com/community/Repositories/Ubuntu . When closing the window, don't forget to click on the "Reload" button and update the list of avalaible software.

It's now time to add all the software needed to compile Scribus. Open a terminal and run:

$ sudo apt-get build-dep scribus
This will ask you for your password and then install everything Scribus 1.4 (the Scribus version that Ubuntu and Debian are providing) needs to be compiled.

Since you will be compiling Scribus 1.5.x There are a few libraries that are new and that you will have to install, too:

$ sudo apt-get install libqtwebkit4 libqtwebkit-dev
$ sudo apt-get install libicu48 libicu-dev
$ sudo apt-get install libcairo2-dev
$ sudo apt-get install libpoppler-private-dev
$ sudo apt-get install git

Prepare your directories

You will need a directory where you will put the Scribus source code and, on the other side, one where the binaries will be installed.

In your home, create the two directories: - "Source" where the source code will reside, - "Bin" where Scribus 1.5.x will be installed.

Getting the code

The Scribus contributors are using a git server to share their work. Each new feature is located in its own branch and can be tested separately. While only people having already provided patches can write to it, everybody can download, read and compile the code.

In order to get the code: - open a terminal and make sure that your in your home - go into the "Source" directory - get the Scribus code and put it into the "scribus" directory:

$ cd Source/
$ git clone git://git.scribus.net/scribus.git scribus
$ cd scribus/

If you want to activate the "indic" branch you will have to check it out:

$ git checkout indic

Compiling Scribus

First, you will have to make sure that you are in the ~/Source/scribus/Scribus/ directory in a terminal.

Your second step is to create a build/ directory where all the temporary files generated during the compilation will be written and cd into it

$ mkdir build/
$ cd build/

Now that you're in the build/ directory you can launch the program that will make sure that everything needed for the compilation is there and will prepare all the settings for the compilation:

$ # Warning: in the line below some some of the underline signs are missing.
  #Please have a look at the same line at the bottom of this article to see the real parameters.
$ cmake -DCMAKE_INSTALL_PREFIX:PATH=~/Bin/scribus -DWANTDEBUG=1 -DWANTNOOSG=1 -DWANTPRIVATECAIRO=0 ..

If you get any error, please come and ask us in our IRC channel! And don't forget the two dots at the end of the cmake command!

Now that everything is ready, compiling Scribus is just a very simple step:

$ make -j4
Where "-j4" will try to use up to 4 processors or threads in parallel and massively speed up the compilation.

After some time, between 10 minutes and one and a half hour depending on the CPUs available, Scribus will be compiled!

Once make is done, you can install Scribus in ~/Bin/scribus/:

$ make install

If everything worked well, you can now launch Scribus with the command:

$ ~/Bin/scribus/bin/scribus

You can create a link to it on your desktop or in your programs bar.

And if something didn't workout correctly, we are all there in the IRC channel (irc://irc.freenode.net or http://wiki.scribus.net/canvas/Special:WebChat) to give you hints on how to sort everything out!

TL;DR

If all this is too long to read, here is just the list of commands you need:

$ # make sure that the source repositories are in your sources.list
$ cat /etc/apt/sources.list
$ sudo apt-get update
$ sudo apt-get build-dep scribus
$ sudo apt-get install libqtwebkit4 libqtwebkit-dev
$ sudo apt-get install libicu48 libicu-dev
$ sudo apt-get install libcairo2-dev
$ sudo apt-get install git
$ cd
$ mkdir Bin
$ mkdir Source
$ cd Source/
$ git clone git://git.scribus.net/scribus.git scribus
$ cd scribus/
$ git checkout indic
$ cd Scribus/
$ mkdir build/
$ cd build/
$ cmake -DCMAKE_INSTALL_PREFIX:PATH=~/Bin/scribus -DWANT_DEBUG=1 -DWANT_NOOSG=1 -DWANT_PRIVATE_CAIRO=0 ..
$ make -j4
$ make install
$ ~/Bin/scribus/bin/scribus

That's all folks!

]]>