[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-dev] [GSoC] APAF Report



Follows the report of the last 10 days.

Coding. hellais warned me about a possible xsrf vulnerability in the
APAF's panel, which should be fixed with 629828d . I have also
successfully implemented a working django blog engine - ZinniaBlog -
on the top of apaf.

Documentation. Discussing with my mentor, it came out the need to use
both sphinx and a wiki. The first one, for APIs documentation - that
are not going to change often, and should be more or less stable; the
second one, for tutorials and external services - more probable to
change frequently, and with a more interactive support from a possible
community. So, I've updated the documentation also with latest code
changes, and put it on readthedocs:
http://apaf.readthedocs.org/en/latest/index.html

Some random cleanup - GUI modules have been moved to a new package
apaf.ui, html templates split from static/ and moved to a new
templates/ directory, etc.

Frontend. Re-started the development of panel pages. using cyclone's
templates. Basically, we plan to have both a javascript application
taking into account tor network's delays, and a plain html for
browsers having js disabled.


-- 
Ã
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev