On Wed, Jun 9, 2010 at 12:25 PM, David Winslow <[email protected]> wrote:
>> === 0. Test Framework ===
> A little more detail here would be nice; what tools do you intend to use for
> these tests?
a. For the 404 tests I plan to use Django's testing framework, for example:
>>> c = Client()
>>> c.get('/customers/details/', {'name': 'fred', 'age': 7})
More info here[1]
[1] http://docs.djangoproject.com/en/dev/topics/testing/
b. For the javascript tests, I have no idea. I know I could test the
minified files with JSLint[2], but I don't know if it's even possible
to programmatically see if there are any Javascript errors after
rendering the page, for example the ones that Firebug show at the
bottom or the ones that IE explorer shows with the alert popup. If it
isn't possible then we would just skip this part.
[2] http://github.com/FND/jslint-cli
> I have some docs about the Django apps that I've been sitting on for a
> while; they are part of a larger developer manual that is not very correct
> right now. The Django stuff is pretty recent though, I'm fairly confident
> it's all correct.
Great!
> All for moving the CAPRA site out of the main repository.
Cool.
> As mentioned earlier, I don't think we should mess with the JavaScript too
> much until Andreas gets back from his vacation and finishes the refactoring
> currently under way.
Fair enough, as far as I know the Javascript part is currently broken
in GeoNode right now so that's another reason to just leave any
changes that affect it for later. I agree with you.
> What's involved in adding a project profile to Pinax? Are we going to have
> to convince the Pinax guys that SDI is a useful profile for their social
> networking toolkit (might be a hard case to make)?
The case has already been made, there have been talks of a "geopinax"
for a lot of time and even some integration of "foursquare type"
applications. They are very inclusive and I know already a lot of the
folks in the community. In the remote case that they don't like our
geonode profile, we can just create a geonode-admin.py script that
mimics or extends pinax-admin.py, just as pinax-admin.py extends
django-admin.py.
> I'm not against these changes, but I'd like to see a bit more info about
> what's going on.
I'll add this information to Trac, expand it and seek some feedback
from Sebastian too.
Thanks for responding so quickly,
Ariel.
