Hello,
Congratulation for byteflow it hits the sweet spot of my requirements
and I am really happy with its capacity. I have been testing it for
some days and I have nothing to say except it is rich project focus on
blogging which is nice. No that I have done my choice and that
Byteflow is the winner !!!! :-)
I need to deploy it and this is what I would like to discuss here,
Byteflow is built on the logic that everything is included and it just
run. This is a very compelling argument for people that just want to
test Byteflow but it becomes a bit of a pain as soon as you want to
deploy it. The fact that a lot of external library are stored inside
Byteflow obfuscate the difference between dependency and Byteflow
internal code. It makes it hard to integrate into a large django
project. In addition to this it leads you to hack the PYTHONPATH into
the settings.py to avoid the installation the dependency.
I believe that it is possible to keep the quality of the first user
experience (easy to install) without having to suffer from the
monolithic/duplication of code later on.
This can be achieve by using distutils (setup.py) / virtualenv / pip.
In order to prove this I have started a branch on bitbucket
http://bitbucket.org/yml/byteflow/. The goal is to solve the ticket
#148 and #140. At this stage I think that it works now it needs to be
fine tune to freeze the different package to the required version.
I would be glad to hear from you on whether or not such approach could
be eventually merge into trunk.
#140 -- http://byteflow.su/ticket/140
#148 -- http://byteflow.su/ticket/148
