Some refactoring changes to Glashammer

2 views
Skip to first unread message

Ali Afshar

unread,
Sep 18, 2009, 6:05:22 AM9/18/09
to glashammer
Hi everyone. I am doing some gardening in the bundles package which is
based around the concept that our bundles are:

1. bundles will be core and well-maintained - these ones may well be
required by other parts of Glashammer.
2. 3rd party bundles which other parts of Glashammer don't depend on,
and will have varying level of maintenance depending on the author
3. depracated bundles that we keep around just in case anyone is
crazy.

Since I have no idea how many people use Glashammer etc, I really
don't know the effect of changing some parts of the API will have on
everyone. So please let me know some feedback.

Ali

Ali Afshar

unread,
Sep 18, 2009, 7:18:30 AM9/18/09
to glash...@googlegroups.com

I have placed my changes here, if no one complains too much I will
push them after the weekend.

http://bitbucket.org/aafshar/glashammer-bundles-refactor/overview/

Ali

hallsy

unread,
Oct 19, 2009, 5:19:36 AM10/19/09
to glashammer
Looks fine to me.
I'm using Glashammer extensively for my project, which will be hosted
on GAE.
I took a while looking round the different Python web frameworks and
chose Glashammer because it seemed the right balance between power and
complexity.
Hope you keep it going.
David
Reply all
Reply to author
Forward
0 new messages