There was a snag in the KookBook 0.2.0 release, and 0.2.1 is available.
Get it here: kookbook-0.2.1.tar.xz
Btw, anyone can tell me the purpose of
|
1 |
git archive --prefix=foo |
compared to
|
1 |
git archive --prefix=foo/ |
When would anyone use the former?
I got a bit traction on KookBook and decided to fix a few bugs, mostly in the touch client, and add some features.
Get it here: kookbook-0.2.0.tar.xz
KookBook is now also available in Debian, thanks to Stuart Prescott
KRecipe converter
Some people has a large recipe collection in KRecipe and would like to try out KookBook. I wrote a convertion python script now available. It works in “current directory” and reads the krecipe database from there and outputs KookBook markdown files in same repository. It has so far been tried on 1 database.
Bug fixes
Future
Some people have started talking about maybe translation of the interface. I might look into that in the future.
And I wouldn’t be sad if some icon artists provided me with a icon slightly better than the knife I drew. Feel free to contact me if that’s the case.
Happy kooking!
Continuing in Aurelien Gateau‘s release month, where I recently joined in with Kookbook, I’m now also following up with Kolorfill, an app I also described in the past.
It is a simple flood filling game written using the amazing Kirigami framework.
Have fun with it.
Release Time
A little while ago, I blogged about an application I was writing for my cooking recipes.
I have now gotten to a point where I will declare it version 0.1. The release can be found on a KDE Download server near you: https://download.kde.org/unstable/kookbook/kookbook-0.1.0.tar.xz.mirrorlist.
Desktop app
As written back then, Kookbook is basically displaying markdown, parses semi-structured markdown for ingredients and tags and allows accessing the recipes that way. Kookbook also offers to open a system editor for editing the content.
This is the “normal” view:
Support for images in recipes has also been added since previous blog post.
Mobile app
Since the may blog post, I have also written a little more basic touch-friendly user interface. It does not offer the full set of desktop features, namely it doesn’t offer to launch an editor for you, and it also only allows to access the recipes thru their names, not thru all the other ways of finding recipes. Though the last part is up to discussion for further releases.
The main page looks like
And lets you search thru the titles to find the one you are after.
The recipe view is more or less the same. 
The code
The code itself is mit/x11 licensed, and contains a couple of interesting bits that others might want to take advantage of:
Have fun
Go forth, do cooking. And feel free to share recipes. Or create patches.
So, it has been a busy week of Qt and KDE hacking in the beautiful city of Vienna.
Besides getting quite some of the Viennese staple food, schnitzel, it was an interesting adventure of getting smarter.
And lots of other stuff.
Besides getting smarter, also getting to talk to people about what they do and to write some patches are important events.
I also wrote some code. Here is a highlight:
And a lot of other minor things, including handling a couple of Debian bugs.
What I’m hoping to either put to my own todolist, or preferably others, is
I felt productive, welcome and … ready to sleep for a week.
I was invited by my boss to a dinner. He uses exchange or outlook365 or something like that. The KMail TNEF parser didn’t succeed in parsing all the info, so I’m kind of trying to fix it.
But I need test data. From Exchange or outlook or outlook365. That I can add to the repoository for unit tests.
So if you can help me generate test data, please setup a meeting and invite me. publicinvites@sune.vuorela.dk
Just to repeat. The data will be made public.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
Item { property string text; Text { ... } MouseArea { onClicked: { if (parent.text === "Quit") { Qt.quit() } else if (parent.text === "Start") { globalObject.start() } else if (parent.text === "Stop") { globalObject.stop() } } } } |
I don’t always understand why people do things in some ways.
Once again, I got surprised by the 80 bit x87 FPU stuff.
First time was around a decade ago. Back then, it was something along the lines of a sort function like:
|
1 2 3 4 5 6 7 8 9 |
struct ValueSorter() { bool operator (const Value& first, const Value& second) const { double valueFirst = first.amount() * first.value(); double valueSecond = second.amount() * second.value(); return valueFirst < valueSecond; } } |
With some values, first and would be smaller than second, and second smaller than first. All depending on which one got truncated to 64 bit, and which one came directly from the 80bit fpu.
This time, the 80 bit version when cast to integers was 1 smaller than the 64 bit version.
Oh. The joys of x86 CPU’s.
I found this construct some time ago. It took some reading to understand why it worked. I’m still not sure if it is actually legal, or just works only because m_derivedData is not accessed in Base::Base.
|
1 2 3 4 5 6 7 8 9 10 11 |
struct Base { std::string& m_derivedData; Base(std::string& data) : m_derivedData(data) { } }; struct Derived : public Base { std::string m_data; struct Derived() : Base(m_data), m_data("foo") { } }; |
Last time, I was doing a recipe manager. This time I’ve been doing a game with javascript and QtQuick, and for the first time dipping my feet into the Kirigami framework.
I’ve named the game Kolorfill, because it is about filling colors. It looks like this:
The end goal is to make the board into one color in as few steps as possible. The way to do it is “Paint bucket”-tool from top left corner with various colors.
But enough talk. Let’s see some code:
https://cgit.kde.org/scratch/sune/kolorfill.git/
And of course, there is some QML tests for the curious.
A major todo item is saving the high score and getting that to work. Patches welcome. Or pointer to what QML components that can help me with that.
Recent Comments