<div class="blog">
<h1 id="NAME">
-Newbie Friendly Perl Projects
+The Future and Beyond!
</h1>
<div class="CONTENT">
-<div style="text-align: right;"><i>A seed needs soft soil and water to grow</i></div><div style="text-align: right;"></div>This is a reply to <a href="http://szabgab.com/blog/2009/09/1251862435.html">szabgab's</a> post on how to get newbies interested in Perl modules. Being a newbie in Perl myself I thought I should take a shot.<br /><br />I was thinking you can make projects more accessible to newbies by having a step by step plan included with where they need to look. For example for docs of SDL_perl:<br /><ol><li>Look at SDL docs [<a href="http://www.libsdl.org/cgi/docwiki.cgi/SDL_API_by_name">link</a>]</li><li>See where SDL_perl is using the same functions [<a href="http://cpansearch.perl.org/src/KTHAKORE/SDL_Perl-v2.2.2.11/src/SDL.xs">link</a>] and the docs to this file [<a href="http://cpansearch.perl.org/src/KTHAKORE/SDL_Perl-v2.2.2.11/lib/SDL.pm">link</a>]</li><li>Use the pod format to add it to the source [<a href="http://perldoc.perl.org/perlpod.html">link to using pod</a>]</li><li>{BONUS} Come up with tutorial or cookbook [<a href="http://search.cpan.org/%7Edrolsky/Moose-0.89/lib/Moose/Cookbook.pod">link to example</a>]</li><li>Submit code to github [<a href="http://github.com/guides/home">link</a>] or email them to me [<a href="mailto:kthakore@cpan.org">link</a>]<br /></li></ol><br />Basically assume nothing is known. I know this may seem demeaning but I am a newbie to Perl and sometimes I hate looking for crust (docs). I call it crust because a crust is useful for me to eat a pizza slice, but it has no flavor .<br /><br /><i>--yapgh </i><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3102167581424744259-581981098917545448?l=yapgh.blogspot.com' alt='' /></div></div></div>
\ No newline at end of file
+<div style="text-align: right;"><i>I do not think about awesomeness...<br />
+I just am awesomeness<br />
+n.n<br />
+--<a href="http://irclog.perlgeek.de/sdl/2009-10-20#i_1620287">KatrinaTheLamia</a></i><br />
+</div><br />
+<h3>Updates</h3>Since the last post SDL Perl has seen an increase of interest to both use and contribute to SDL Perl. Before I dig into the updates, I would like to acknowledge them.<br />
+<h3>Core Development</h3><b>Acme (<a href="http://use.perl.org/%7Eacme/journal/">Leon Brocard</a>):</b> Has started to work on the Redesign Effort with me. The help is much appreciated! Enjoy your vacation. <br />
+<br />
+<h3>Website and Windows Testing</h3><b>FROGGS (Tobias Leich):</b> Came in as a new user to SDL Perl. And after breaking the redesigned SDL Perl in as many ways possible he has decided to help out on the new site. <br />
+<br />
+<br />
+<h3>Last Legacy Release</h3><br />
+Ok! Now this weekend hopefully we will release our last legacy release, after this we move on! This release will focus on showing of SDL + Perl possibilities.<br />
+<h3>Pong + SDL::Game::Rect</h3><a href="http://onionstand.blogspot.com/">garu</a> has been working on making SDL object extensions that provide a more perly way to use and play with the SDL bindings. To demonstrate the benefits of this SDL::Tutorial::Pong is done and being polished up. SDL::Game::Rect is a peek in to the design and vision we have for SDL down the road.<br />
+<h3>Design</h3>The design we have settled on for future release for SDL Perl can be broken in to two layers, SDL::* and SDL::Game::*. Previously the SDL Perl library tried to provide C bindings and provide Perl Idiomatic access. This was messy in regards to the single responsibility principle (do one thing and do it well).<br />
+<br />
+We have decided to separate these two focuses into the two name spaces SDL::* and SDL::Game::*. SDL::* will provide straight access to SDL's C API, nothing less and nothing more. SDL::Game::* will extend and make pretty unicorns for Perl. <br />
+<br />
+This design has already begin to pay of. One major benefit been in the XS <a href="http://github.com/kthakore/SDL_perl/commit/20f544ea4f3e7b34c68445aba89ed9c69d411ddf">readability</a>. Moreover since structs are treated as objects, Perl manages their destruction, and deliver less memory leaks.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3102167581424744259-4327446497206876141?l=yapgh.blogspot.com' alt='' /></div>
+<p><a href="http://feedads.g.doubleclick.net/~a/SxZJQYdkG8_YzEHzsEro4b9mCZ8/0/da"><img src="http://feedads.g.doubleclick.net/~a/SxZJQYdkG8_YzEHzsEro4b9mCZ8/0/di" border="0" ismap="true"></img></a><br/>
+<a href="http://feedads.g.doubleclick.net/~a/SxZJQYdkG8_YzEHzsEro4b9mCZ8/1/da"><img src="http://feedads.g.doubleclick.net/~a/SxZJQYdkG8_YzEHzsEro4b9mCZ8/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/YetAnotherPerlGameHackeryapgh/~4/JNZlGzpmYZQ" height="1" width="1"/></div></div>
\ No newline at end of file
projects / sdlgit/SDL-Site.git / blobdiff