I’ll be busy for a while, as it’s time for me to show what I’ve got! I’ll have to work hard for the next 2 months. After that I’d like to work again on this project.
- Take some rage (it may come from a different source, still counts);
- Put it into your code;
- Get working status-bars in a very short time;
- Swear in a programming language of choice for the remaining time;
If someone is reading this blog, sorry for being not that active in the last week. The issue here it’s that I’m also working on my master thesis, so from time to time I’ll be simply busy.
Fortunately (or unfortunatey, depending on the point of view), for the moment I’m waiting for my contacts. Free time. Let’s work on this project (for which I decide what to do).
No answer to my question, so I guess I’ll go on keeping my current code, with redundant signals fooling around my application. Maybe I’ll directly write to developers. Not today.
I’ll be working on the plumber-side of the application: markdown encoding.
In those days I’ve been busy, so I didn’t continue my work on Notedown. I’m trying to figure out how to deal with a strange behavior of the toolkit.
In the last two days I’ve written a working prototype of the main window that will compose NoteDown. It can be found in the git repository. Supported operations:
I still need to study some aspects of GTK, but tonight I wanted to place a small code base. In this case is not about the GUI, but about the core of the program! I’ve got:
- A simple configuration class (a few lines of Python and here we go!)
- GUI selection is configurable (which means that the software is not strictly bound to GTK: different toolkit could be added in future, allowing (for instance) to run seamlessly the stuff under a QT-based environment;
- Paragraph and Text Block abstractions (i.e. something like an intermediate representation of the text format which an be conveniently translated in Markdown.
I was thinking that, as there’s can be multiple choice in terms of GUI, there could be also room for different output formats besides Markdown. No, I don’t want to end with yet another word processor! The first rule here is simplicity! I’m just saying that Markdown has got many siblings…
Enough for today.
Unfortunately (well, also reasonably) the tutorial doesn’t give much complete documentation nor details about how everything works. However important information can just be obtained from the GTK C reference manual.
After playing with the Multiline Text Editor example, I started wondering how to save stuff and read formatting information. The documentation about the GtkTextIter component answered my first question, but I need to conceive a good way of retrieving the tags. Nothing I can’t handle.