No description
- Python 99.2%
- Shell 0.3%
- Perl 0.3%
- Batchfile 0.1%
rationale: empty lines between entries do not seem to be supported by the spec http://web.archive.org/web/20100222214101/http://web.intuit.com/support/quicken/docs/d_qif.html and I have found at least one application reading QIF that works properly without the blank lines, and fail to work with the blank lines also: most QIF files generated by other apps in the wild seem not to have any empty lines between entries |
||
|---|---|---|
| contrib | ||
| desktop | ||
| docs | ||
| icons | ||
| man | ||
| modules | ||
| scripts | ||
| tools | ||
| weboob | ||
| .gitignore | ||
| .mailmap | ||
| AUTHORS | ||
| build.mk | ||
| ChangeLog | ||
| COPYING | ||
| INSTALL | ||
| MANIFEST.in | ||
| README | ||
| release.sh | ||
| setup.cfg | ||
| setup.py | ||
Weboob is a project which provides a core library, modules and applications. Overview -------- The core library defines capabilities: features common to various websites. For example, http://www.youtube.com and http://www.dailymotion.com are both videos providers: Weboob defines the “ICapVideo” capability. Each module interfaces a website and implements one or many of these capabilities. modules can be configured, which means that the end-user can provide personal information to access the underlaying website (login/password for example). Applications offer the ability to the end-user to work with many modules in parallel, in a multi-threaded way. For example, one could search a video on many providers websites. Applications are toolkit-agnostic. They can use Gtk, Qt or text-only, more adapted to reuse data through pipes. The core library provides base classes which help the developer to write modules and applications. Weboob is written in Python and is distributed under the AGPLv3+ license. Bash completion --------------- To enable bash completion, just source the tools/weboob_bash_completion file from your ~/.bash_completion file (which is sourced by /etc/bash_completion).