googlecl  0.9.15
About: GoogleCL is a command line utility to use google services like youtube, blogger etc. (fork of the original Google tool).
  Fossies Dox: googlecl-0.9.15.tar.gz  ("inofficial" and yet experimental doxygen-generated source code documentation)  

googlecl Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies
  4. googlecl-0.9.15.tar.gz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
README.md

#Google CL

Downloads

GoogleCL is a command line utility to use google services like youtube, blogger etc.

It was developed by Mr.Tom H. Miller from Google and was hosted here.

This is a fork of the above project to keep the development up and running. Hope you enjoy it and if you do, you can tip me here at https://gratipay.com/vinitkme/. Thanks! :)

Installation

Installation is simple, Just run this command in your shell:

git clone https://github.com/vinitkumar/googlecl.git
cd googlecl
python setup.py install

Contribution:

Few things should be kept in notice before contributing:

  • Few changes in the documentation structure and format(Markdown) has been done.
  • Pycco has been used to generate documentation. I believe in Literate programming and felt that it would be easier for developers to understand the existing code.
  • Follow the same styleguide and naming conventions as present in the code.
  • Follow [github flow] (http://guides.github.com/overviews/flow/), It is a dead simple way to deal with development using and I prefer it.
  • Branch naming could be issue related. Say there is issue #23, create a branch name feature/fix-issue23 or bugfix/issue23. It would really help.

Thanks!