Rewriting cppo one piece at a time
Go to file
T. Joseph Carter b55ea886c1 Style cleanup to
This is still a good ways from "proper" because this code is still kinda not
really done.
2017-07-21 14:21:53 -07:00
blocksfree Style cleanup to 2017-07-21 14:21:53 -07:00
doc Document two more test disks 2017-06-24 03:11:26 -07:00
.editorconfig Add git files and cppo to .editorconfig 2017-07-18 11:03:24 -07:00
.gitignore Let's _not_ accidentally commit a __pycache__ 2017-06-24 03:21:21 -07:00
.pylintrc Help prevent false positive sin pylint 2017-07-20 04:16:02 -07:00
COPYING.txt Add license, Copyright notices, history doc 2017-07-07 06:29:19 -07:00
cppo Lint cppo: Docstrings, warning disables 2017-07-19 08:47:17 -07:00 Fix links 2017-07-16 12:01:19 -07:00 Fix links 2017-07-16 12:01:19 -07:00

BlocksFree and cppo-ng

This project began as cppo-ng, an attempt to begin evolving cppo, a script written by Ivan Drucker, to be more pythonic. It's growing into something a bit bigger than that, however. See if you want details about where it started and how it's gotten here.

The goal is no longer simply to clean up the cppo script!

What we actually want


  • A scriptable AppleCommander-ac-like tool
  • cppo with all of its present external interface.
  • The features of CiderPress from the command line
  • Native feel on Windows, Mac, and Linux at the minimum
  • Future: A GUI tool that can display characters natively

It should be quite doable to build a tool like AppleCommander-ac with the ability to read, write, convert, dump, and other things that one currently does with AppleCommander. Moreover, it should be no major thing to have it be able to output data in a mechanical format that can be processed by shell scripts or JSON that can be processed by anything more functionally complete. That will resolve the issues of the thing being written in Python if you need something else for the majority of cases. It's not a perfect solution for Windows outside of development tools, but development tools are the primary application for this.

We have tools that need cppo and we cannot assume that we're the only ones who do. We could maintain the existing script, but it has both bugs and limitations. Better to emulate the old cppo using a new interface. You can do this with a runner that provides the old interface alongside the modern one. That's the plan.

The possibility of using urwid exists to provide a textual interface. It's probably desirable for any GUI to be abstract enough to have multiple implementations, but the idea that you might want a textual interface should be considered.


If you'd like to write some. :)


Yes please!