blob: c4ea935b142eb4f8969a9b5303a4a922c2e34f9d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
#+title: Status Report for Week #10
#+date: 2011-08-04
#+layout: post
#+category: gsoc
Week #10 was actually quite fun. I added =POD= documentation to
=Dancer::Script=, fixed some tests that were broken by the move to
=Dancer::Object=, and also fixed typos and other stuff.
So what was the fun part? Particularly, studying everybody else
documentation in the =Dancer::Cookbook=, I still don't think that my
documentation is the best, but far from very-basic is what I was
trying to achieve.
I did meet with my mentors to discuss the work of week #10, which was
really not very detailed in the project schedule. It was about dealing
with the plugin reimplementation of =Dancer::Plugin= to
=Dancer::Script=. After a couple of questions, we decided that it
would be best to see how other web frameworks handle their files.
*** What I worked on Week #10
My whole work for that week was to achieve better results for the =t=
test files. So after commiting and commiting, nothing worked, until I
got to the point that I had to review every test. So the answer of
every issue was the fact that we moved to =Dancer::Object=. Here is
[[https://github.com/gnusosa/Dancer/commit/4e047458d57e6b282418cb6189cbf306954167f6][the commit for the tests files]].
I also took a look to the documentation in other modules, and added to
the module my version of what I think is correct for =Dancer::Script=.
You can find the documentation in [[https://github.com/gnusosa/Dancer/commit/6fd70b55bcaa2b7d017b2fcf29809da6181a7bfe][this commit]] and in [[https://github.com/gnusosa/Dancer/commit/b147630522fe23d9986b0f7bbdbfed7162b96e4b][this commit]].
*** What's next?
- Add a better documentation.
- Look for a new method to store template files.
- Implement the new method to store template files.
- Add tests for the documentation (if possible).
For week #11, it's mostly study and implement several new ideas. Just
like in any other features, Dancer is gaining from the knowledge and
methods that other frameworks have successfully applied. One phrases
comes to mind, "standing on the shoulders of giants..."
|
