No subject

Thu Mar 10 16:39:45 CET 2011

these works great for me, since it gives more time to study and learn
from the testing settings that Dancer modules work with. I've barely
played with tests before, and I think this is a great time to start
working on a topic I lack knowledge of.

Because the module rough draft was written in a quick matter, sawyer
decided to modify the project schedule, and add other tasks according
to the time and the work done. You can find the new project schedule
in my GSoC section. (http://log.gnusosa.net/code/gsoc/project-schedule)

--
You received this message because you are subscribed to the Google Groups
"tpf-gsoc-students" group.
To post to this group, send email to tpf-gsoc-students at googlegroups.com.
To unsubscribe from this group, send email to
tpf-gsoc-students+unsubscribe at googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tpf-gsoc-students?hl=en.

-- 

franck cuny

http://lumberjaph.net - http://github.com/franckcuny

--bcaec544eb727a272f04a48ebdd7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi everybody<div> </div><div>I&#39;m not sure everybody know that this y=
ear we have a GSoC student: Carlos. Here is his status report, I&#39;ll ask=
 him to CC the list his next status.</div><div> </div><div>I&#39;m sure =
this could be interesting to some of you :) 
 <div class=3D"gmail_quote">---------- Forwarded message ---------- F=
rom: gnusosa &lt;<a hre=
f=3D"http://gnusosa.mx">gnusosa.mx</a>@<a href=3D"http://gmail.com">gmail.c=
om</a>&gt; 
Date: Tue, May 31, 2011 at 10:23 AM Subject: GSoC Status Report for Week=
 #1 To: tpf-gsoc-students &lt;<a href=3D"mailto:tpf-gsoc-students at google=
groups.com">tpf-gsoc-students at googlegroups.com</a>&gt; Sorry for=
 the late report, but I was socializing with my family and

friend in this Memorial Weekend. Basically, a holiday in the US. 
Nevertheless, it is not an excuse for my late report. Anyhow, same 
format continues you can find my report in my blog in the following 
address: <a href=3D"http://log.gnusosa.net/code/gsoc/status-report-1" targe=
t=3D"_blank">http://log.gnusosa.net/code/gsoc/status-report-1</a> 
 
######################### 
 
Status Report for Week #1 
 
Since I started working in the middle of the Community Bonding Period, 
there was not much to do to the module in the week #1. However, some 
progress was made with the module. For now, the module Script.pm is 
fully capable of writing a dancer app from the call of the script bin/ 
dancer. These was the expected work for the week #1. 
 
What I worked on the week #1? 
Well basically, moving the functions to object-oriented methods. We 
all know that by default in almost every module, you add Module- 
&gt;new(%args)-&gt;run; and the methods. From that I also moved the 
functions from get_* to set_*, for example, get_lib_path to 
set_lib_path in the new object constructor. You can find more detail 
in the most recent commit I made in my github account.(https:// 
<a href=3D"http://github.com/gnusosa/Dancer/commit/" target=3D"_blank">gith=
ub.com/gnusosa/Dancer/commit/</a> 
e946254caa5b33cdcb75a60b34ec39ee5e3c56e8) 
 
What I learned in the week #1? 
I learned to appreciate steps and instructions, for the second time I 
screwed up my repo, and all because I thought moving and stripping 
functions would reduce work. When in reality, I was just adding more 
work and steps. Reinvention of the wheel destroys, and it takes the 
most precious hours of your day. On another side, git is the tool of 
the year for me. I love to sync and clone repositories in my two 
netbooks, any change can be updated in any local repo in matter of 
seconds. torvalds++ 
Related to Perl code, I learned that idiomatic pragmas and other 
idiosyncrasies are great for refactoring, but not for rough drafting. 
I guess Perl sticks to the Unix philosophy point, which tell us that 
simple is better. However, I think that a more idiomatic code is more 
maintainable, but I don&#39;t want to start a debate, I just want to keep<b=
r>
learning. I guess, time and work will tell. As of working habits, I 
made better use of perldoc and man for any Perl related documentation. 
I bought Modern Perl and Effective Perl Programming, and both books 
are next to my keyboard on a daily basis. The chapter &quot;Objects&quot; i=
n 
Modern Perl helped me to grasp what was essentially needed to migrate 
the functions to object methods, and adding the new class object. Most 
doubts on the topic, were later answered by franck in the middle of my 
commits revisions. 
 
What&#39;s next? 
For week #2, the tasks are as follows: 
 
 =C2=A0 =C2=A0Migrate the script to an Object Oriented module. 
 =C2=A0 =C2=A0Write tests for the OO Module. 
 =C2=A0 =C2=A0If needed, refactor and modify the module.