Cool project!

8 views
Skip to first unread message

Sandy Armstrong

unread,
Apr 24, 2010, 10:03:29 AM4/24/10
to QtNote
Hey all,

Upstream Tomboy maintainer here. Heard about your project through a
google alert. Sounds really cool! I've often thought there would be
a few advantages to having a native Qt client for Tomboy notes, but
never had the time to work on it myself. Unfortunately Tomboy only
really gets attention on KDE when somebody files a bug, so an actively-
maintained Qt client could be really advantageous to KDE users (and
maybe even Windows users, since Qt tends to work better on Windows
than GTK+).

I have't had any luck building QtNote so far (I get "ISO C++ forbids
declaration of ‘Q_OBJECT’ with no type"), but I'm running GNOME and
have no real experience building Qt projects, so I'm sure I just need
to set up my dev env a bit better. Still, it looks promising.

I've never looked at Conboy's C code for sync, but I wonder if it
would be possible to library-ize the pieces that deal with web sync so
that you folks can share some code and make quicker progress.

Anyway, if you have any questions about Tomboy quirks, feel free to
bug me on tomboy-list. Also, you're welcome to announce major
releases there if you like; Tomdroid and Conboy already do.

Have fun and good luck,
Sandy


--
Subscription settings: http://groups.google.com/group/qtnote-discuss/subscribe?hl=ru

Rion

unread,
Apr 24, 2010, 10:50:20 AM4/24/10
to qtnote-...@googlegroups.com
Actually i'm not going to clone all features of tomboy. I even have
some doubts about rich text support but i think i'll try to make
extensible pluggable architecture. In other words i want very
light-weight and simple app but hopefully not losing most-wanted
features.

Q_OBJECT thing happens with Qt < 4.6. I've fixed this in svn but
unfortunatelly already after release.

regarding Conboy, i didn't see it too. probably i'll look in near
future (right now for example =) )

and thanks for suggestion about tomboy-list =)

Sandy Armstrong

unread,
Apr 24, 2010, 11:36:25 AM4/24/10
to qtnote-...@googlegroups.com
On Sat, Apr 24, 2010 at 7:50 AM, Rion <rio...@gmail.com> wrote:
> Actually i'm not going to clone all features of tomboy. I even have
> some doubts about rich text support but i think i'll try to make
> extensible pluggable architecture. In other words i want very
> light-weight and simple app but hopefully not losing most-wanted
> features.

Oh, cool. Building a straight clone is probably not all that useful,
but a new innovative client certainly is. Looking forward to seeing
what you come up with.

If you do think adding new features to the tomboy note file format are
necessary, I'd love to collaborate on that, too.

> Q_OBJECT thing happens with Qt < 4.6. I've fixed this in svn but
> unfortunatelly already after release.

Ah, I see. Got it building/running now. I should file a bug for the
fact that clicking on the tray icon shows a giant 400+ note menu for
me. :-)

Thanks,
Sandy

Rion

unread,
Apr 24, 2010, 12:55:01 PM4/24/10
to qtnote-...@googlegroups.com
I already thought today about this issue =)
will be fixed in the next release. the only thing which stops me is absence
of knowledge how to optimize process of reading. I didn't look much, but
i guess tomboy uses some internal database for storing last modify dates
and titles of notes.

2010/4/24 Sandy Armstrong <sanforda...@gmail.com>:
>  I should file a bug for the
> fact that clicking on the tray icon shows a giant 400+ note menu for
> me. :-)
>


Sandy Armstrong

unread,
Apr 25, 2010, 11:17:24 AM4/25/10
to qtnote-...@googlegroups.com
Tomboy keeps a fair amount of note data in memory...basically
everything but actual note content (although I believe that once a
search occurs, all note content remains in memory).

Our note-loading process is far from optimal. We read every note file
at startup to extract things like title, date modified, whether or not
it should be shown at startup, what notebook it belongs to, etc. This
isn't actually that big of a performance hit, but it could definitely
be optimized.
Reply all
Reply to author
Forward
0 new messages