Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Apr 9, 2010
  1. Added delete method.

    authored
Commits on Apr 8, 2010
Commits on Apr 4, 2010
  1. Renamed Buglist.

    authored
    Because the former buglist didn't listed any bugs, but projects, I
    renamed it to 'Projects'.
  2. Fixed tests.

    authored
    Because after saving the forms, the user is returned to the BugList
    view. The view runs in a while loop expecting key input from the user.
    We have to set the input to quit the view, otherwise the tests will
    never finish due to be stuck in the loop.
  3. Setup and use the new formwidgets.

    authored
    Currently there is no correct distinction betwen a terminal view and a
    layoutwidget. Somehow concepts overlap each other, because they all use
    urwid widgets.
Commits on Apr 2, 2010
  1. Added better widget support.

    authored
    The new implementation is inspired by z3c.form and borrows a bit of the
    testsetup. My current implementation sucks in a way that it doesn't work
    if I want to create Addforms.
  2. Added tags recipe to create ctags file.

    authored
    This makes it easier for editors such as vim to complete methods or
    classes.
Commits on Mar 28, 2010
  1. Refactor the run method into the view.

    authored
    The run method is currently only handling key events. Currently I found
    a way of registering keys with actions. This way could be extended to
    make it easier for adding new views and configure keys for them.
  2. Make use of the configuration utility.

    authored
    I added a new keywidget, which shows the current mapping between keys
    and views. The widgets are now adapters, adapting a TerminalView. That
    will allow to move the run method out of the view definition, which
    currently holds duplicated code.
  3. Also be able to register and retrieve key configuration.

    authored
    The we want to dynamically assign keys to views through the
    configuration. This is now possible.
  4. Don't use an extra recipe for generating the bootstrap script.

    authored
    The script is now generated by zc.recipe.egg. I should have looked into
    this recipe before. Most of the "bootstrap" functionality is moved to
    it's own module and registered as an entry_point.
Commits on Mar 23, 2010
  1. Factored out the configuration part.

    authored
    The color configuration and registration is now provided by a
    configuration utility. This makes it easier to leave the configuration
    out of any model or view.
  2. WIP for a configuration via configparser.

    Roman Joost authored committed
Commits on Mar 21, 2010
  1. Namechanges for classes.

    authored
    Changed name from Dashboard to buglist, because that's what it's
    supposed to do (although it's currently showing projects). The
    NewProjectForm is actually more an editproject form. The new
    (newprojectform) will adapt the application as the context object.
  2. Interface change for application view.

    authored
    The application view doesn't implement it's specialized interface
    anymore, but terminal view. It's now the default view for the
    application.
  3. Implemented the widget setup into it's own class.

    authored
    The widget setup which was usually a frame for the whole view, went into
    it's own designated widget. I'm thinking about moving the whole code
    even further into a more pluggable way of defining the layout or
    widgets.
  4. Changed name of baseclass to distinguish the purpose of the widgets.

    authored
    Because I like to add more widgets, I need to distinguish the one from
    the others.
  5. Fixed the color assignment for the widgets.

    authored
    The color assignment for the input widgets background were wrong and
    therefore only rendered if they received focus. Changed it to make it
    to look better.
Commits on Mar 20, 2010
  1. Finally store projects in the database.

    authored
    I now use zope.container for the folder like structure, after finding
    out, that I can't use or inherit from BTrees directly - stupid me. The
    database is now used by the application object, which acts like a
    dictionary type object. Keys and Values set to the application will be
    stored in the database, acting as a root-object in the database.
Commits on Mar 19, 2010
  1. Small refactoring to make run/render methods consistent.

    authored
    The usage of render and run methods were not consistent due to earlier
    tries of moving them entirely into a different component. Still glued
    together with the views, I needed to make them at least consistent with
    the rest of the views.
  2. Removed the keydispatcher.

    authored
    I'm now sending almost all key events to the top widget itself (except
    the button). The button needs to be improved, so it's easier to
    distinguis if it's clicked what to do. I tried a signal connect, but
    can't stop the event loop in the view. That somehow needs a better
    solution.
Something went wrong with that request. Please try again.