<div class="blog">
<h1 id="NAME">
-The beginnings of modular design for SDL Perl
+The Future and Beyond!
</h1>
<div class="CONTENT">
-<div style="text-align: right;"><i>“Do or do not... there is no try.”</i><br />
-</div><div style="text-align: right;"><i>--yoda </i><br />
+<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 />
-</div><h1>The design before</h1><br />
-The bindings before were all in <a href="http://github.com/kthakore/SDL_perl/blob/master/src/SDL.xs">one huge XS file</a>. This was then exported into the SDL module. This means that the XS file has to handle with macros if any component (e.x SDL_Mixer) is not compiled. Moreover having ever binding in one XS file prevents use to treat C structs as object with only one point of free and malloc. This would be BEGIN and DESTROY in Perl. Also the monolithic design introduces a lot of bugs because we have to use free and malloc all over the place. Lastly SDL monolithic design has the constructor for all structs in both Perl and in XS. <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 />
-<h1>The design we are aiming for</h1>Simple <a href="http://github.com/kthakore/SDL_perl/blob/master/src/Rect.xs">one XS</a> per Module. This would also simplify the Build code.<br />
<br />
-<h2>First Step </h2><br />
-We have began with SDL Rect. It is in github master branch now. We are in the progress of making it back compatible. Originally SDL::Rect took named variables as parameters for new(). Now since the constructor <a href="http://github.com/kthakore/SDL_perl/blob/master/src/Rect.xs#L16">is in XS</a> we have only unnamed parameters. <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 />
-<h3>Before</h3><br />
-SDL::Rect->new( -x => 0, -y => 0, -width => 0, -height => 0);<br />
-<br />
-<h3>After</h3><br />
-SDL::Rect->new(0, 0, 0, 0);<br />
-<br />
-Ideally we would like both ways of constructing Rect.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3102167581424744259-6151839795039915111?l=yapgh.blogspot.com' alt='' /></div>
-<p><a href="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/0/da"><img src="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/0/di" border="0" ismap="true"></img></a><br/>
-<a href="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/1/da"><img src="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/YetAnotherPerlGameHackeryapgh/~4/uEzoBWRJEks" height="1" width="1"/></div></div>
\ No newline at end of file
+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