hoppfrosch

Just for information: I already have a fork https://github.com/hoppfrosch/clipjump on which I already collaborated with Avi via pull requests. Things I've done in the past: mostly worked on the documentation...

No duplicates should be implemented as an option - so everyone could choose behaviour according to its own flavour

As you marked this as ready: Any guess, when we will see this released?

Just a few raw thoughts ... I think you should avoid redundancy with storing clips . Isn't the information about channels stored in the database? I would suggest something like...

> Similarly we will use a separate table for columns. What do you mean here?

I have had a look onto database schema of [Ditto](http://ditto-cp.sourceforge.net/), which uses also sqlite. They provided also a table `clipboardformat`\- so I wasn't sure we need the info for Clipjump...

I had a little time and started with implementation of a SQLite database class for Clipjump, based on the database model suggested above: https://github.com/hoppfrosch/Clipjump/tree/hoppfrosch/feature/class_clipjumpdb

Which helper method do you mean? Is throwing exception the desired error handling method since you haven't used it throughout the yet existing code?

> The thing is that History came first and channels came later. So when History feature was implemented, it was super important because it provided a gui to browse what...

Hmmm - I doesn't work the last times I tried. I have to validate this again ...