Hi, Stephane,

That's absolutely right.  I have the UI complete for the
administrator, however with family/work/school I have yet to find the
time to integrate it.  Regarding your other comments, the main purpose
of this project was to provide a means for my introduction to Python/
Pylons.  So, with all the learning I had to do, documentation kind of
fell to the background.  Over the coming months I hope to:

Improve documentation
Improve the project
Integrate a backend UI and improve the functionality (comment
handling, etc, etc)

I hope to have an official release of the project sometime in the
future, however, keeping in mind that I have other work that pays the
bills, that may or may not happen.  I definitely appreciate your
feedback.

Jason

On May 20, 5:32 am, KLEIN Stéphane <[email protected]> wrote:
> On 13 mai, 15:30, leveille <[email protected]> wrote:
>
> > I am on the cusp of finishing my first Pylons (and also first real
> > Python) application (a blog, imagine that).  I still have some cleanup
> > work to do (cache integration, skinning admin UI, DRY cleanup),
> > however overall I think I'm in pretty good shape.  If any of you
> > Pylons Acolytes are interested in taking a peak, I would appreciate
> > any kind of pre-deployment feedback, regardless of how picky.  For
> > example, do you see something I'm doing that isn't very Pythonic?
>
> >http://github.com/leveille/wurdig/tree/master
>
> > Things I am aware of:
>
> > - Horrible test coverage (perhaps 1%)
> > - Horrible docs
>
> Just one question : I suppose than the look of backoffice pages isn't
> "designed" yet ?
>
> Regards,
> Stephane
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to