On Mar 27, 4:25 am, Christopher Johnson <c...@ifpeople.net> wrote:
> Hi all,
>
> We were trying to set up the latest version of agilito (trunk) on our
> development server to provide a demo environment. Unfortunately, the
> documentation on the wiki (http://code.google.com/p/agilito/wiki/DevGettingStarted) has grown out of
> date and doesn't mention a bunch of newer dependencies. We were trying on
> FreeBSD server, which is a bit more cumbersome to get the libraries
> installed, so wanted to ask if:
>
> - anyone has updated info on installing they can add tohttp://code.google.com/p/agilito/wiki/DeivGettingStarted
That page has been updated. There are two external dependencies,
pyExcelerator and matplotlib. The installer is supposed to complain
explicitly about them not being present, but these two are the only
ones that aren't self-contained in the install, all other dependencies
will be fetched upon request by the installer script and installed
inside the django project being created.
Emile
Can you be specific on what was cumbersome?
On Mar 27, 2:48 pm, Matías Iturburu <maturb...@gmail.com> wrote:
> I've tried to update our copy of agilito and found the process too
> cumbersome.
I've changed things around so the external dependencies are optional.
> I also dislike the idea of depending on non-python libraries. I
It makes pretty graphs of various kinds ;) It's also very, very much
On Mar 27, 3:41 pm, Matías Iturburu <maturb...@gmail.com> wrote:
> my virtualenv's python (I didn't understood why we needed matplotlib at
> all).
faster at generating the burndown graph than the flash version. But at
the end of the day, we could argue that none of it all is really
needed, as such. It just makes my life easier, and I'm all for that.
pyExcelerator is pure python, BTW. I've made it optional in the
install, but it would be possible to just fetch it from the pyEx cvs
as part of the install. It's just available in most Linux repos. I
must admit it's been a while since I last spent time with any of the
BSDs.
I'm not quite following. Do you want to make it an API of sorts? Or a
> On a side note at revoluciones we were talking about how agilito fit in our
> PM needs and how in which aspects it's too much "bureaucratic". Some of the
> things we need are in the line of reducing agilito to a series of views and
> models that could enable our site to have a "Project Management Component",
> and not a full fledged PM site as agilito is now, make it less
> standalone-ish.
product you could drop into another Django app? I was under the
impression that was already pretty much possible.
Emile
I have no real experience with python eggs, so I'm afraid I will not
On Mar 27, 4:25 pm, Matías Iturburu <maturb...@gmail.com> wrote:
> > I'm not quite following. Do you want to make it an API of sorts? Or a
> > product you could drop into another Django app? I was under the
> > impression that was already pretty much possible.
>
> I think it's not _pluggable_ enough, it's not even a python egg. Also, from
be of immediate use here. Willing to learn though.
Ah, yeah, I'm with you on that one. Does Django have anything to
> a _design_ point of view (as in web/graphic design, not eng or informatic)
> it should be easier, to integrate with a site that has his own header,
> login, search, footer section, and/or layout and colors, without having to
> tweak agilito's templates or stylesheets
support that?
Is the newstyle branch integratable? I didn't have much luck last time
I tried. Does the fact that you'll be working on the newstyle branch
mean that r182 would be rolled back in the interim? I could do that.
Emile
pyExcelerator is pure python, BTW. I've made it optional in the
install, but it would be possible to just fetch it from the pyEx cvs
as part of the install. It's just available in most Linux repos. I
must admit it's been a while since I last spent time with any of the
BSDs.
I'm not quite following. Do you want to make it an API of sorts? Or a
> On a side note at revoluciones we were talking about how agilito fit in our
> PM needs and how in which aspects it's too much "bureaucratic". Some of the
> things we need are in the line of reducing agilito to a series of views and
> models that could enable our site to have a "Project Management Component",
> and not a full fledged PM site as agilito is now, make it less
> standalone-ish.
product you could drop into another Django app? I was under the
impression that was already pretty much possible.
Emile
Regards,
Emile
Emile