<li><a href="#list_modes_formats_flags">list_modes(formats,flags)</a></li>
<li><a href="#video_mode_ok_width_height_bpp_flags">video_mode_ok(width,height,bpp,flags)</a></li>
<li><a href="#set_video_mode_width_height_bpp_flag">set_video_mode(width,height,bpp,flags)</a>
-<ul>
-<li>
<ul><li><a href="#List_of_avalaibles_flags">List of avalaibles flags</a></li>
</ul>
</li>
-</ul>
-</li>
<li><a href="#update_rect_surface_x_y_width_height">update_rect(surface,x,y,width,height)</a></li>
<li><a href="#update_rects_surface_rects">update_rects(surface,rects) </a></li>
<li><a href="#flip_surface">flip(surface)</a></li>
set_video_mode returns a SDL::Surface on succés or it returns undef on error, the error message is retrieved using <code>SDL::get_error</code>.</p>
</div>
-<h4 id="List_of_avalaibles_flags">List of avalaibles flags</h4>
+<h3 id="List_of_avalaibles_flags">List of avalaibles flags</h3>
<div id="List_of_avalaibles_flags_CONTENT">
-<pre>
-
-
- SDL_SWSURFACE Create the video surface in system memory
- SDL_HWSURFACE Create the video surface in video memory
- SDL_ASYNCBLIT Enables the use of asynchronous updates of the display surface.
- This will usually slow down blitting on single CPU machines, but may provide a speed increase on SMP systems.
- SDL_ANYFORMAT Normally, if a video surface of the requested bits-per-pixel (bpp) is not available, SDL will emulate one with a shadow surface.
- Passing SDL_ANYFORMAT prevents this and causes SDL to use the video surface, regardless of its pixel depth.
- SDL_HWPALETTE Give SDL exclusive palette access. Without this flag you may not always get the colors you request with SDL::set_colors or SDL::set_palette.
- SDL_DOUBLEBUF Enable hardware double buffering; only valid with SDL_HWSURFACE. Calling SDL::flip will flip the buffers and update the screen.
- All drawing will take place on the surface that is not displayed at the moment.
- If double buffering could not be enabled then SDL_Flip will just perform a SDL::update_rect on the entire screen.
- SDL_FULLSCREEN SDL will attempt to use a fullscreen mode. If a hardware resolution change is not possible (for whatever reason),
- the next higher resolution will be used and the display window centered on a black background.
- SDL_OPENGL Create an OpenGL rendering context. You should have previously set OpenGL video attributes with SDL::gl_setattribute.
- SDL_OPENGLBLIT Create an OpenGL rendering context, like above, but allow normal blitting operations.
- The screen (2D) surface may have an alpha channel, and SDL::update_rects must be used for updating changes to the screen surface.
- NOTE: This option is kept for compatibility only, and will be removed in next versions. Is not recommended for new code.
- SDL_RESIZABLE Create a resizable window.
- When the window is resized by the user a SDL_VIDEORESIZE event is generated and SDL::set_video_mode can be called again with the new size.
- SDL_NOFRAME If possible, SDL_NOFRAME causes SDL to create a window with no title bar or frame decoration.
- Fullscreen modes automatically have this flag set.
-
-
-
-
-</pre>
+<dl>
+ <dt>SDL_SWSURFACE</dt>
+ <dd>
+ <p>Create the video surface in system memory</p>
+ </dd>
+ <dt>SDL_HWSURFACE</dt>
+ <dd>
+ <p>Create the video surface in video memory</p>
+ </dd>
+ <dt>SDL_ASYNCBLIT</dt>
+ <dd>
+ <p>Enables the use of asynchronous updates of the display surface.
+This will usually slow down blitting on single CPU machines, but may provide a speed increase on SMP systems.</p>
+ </dd>
+ <dt>SDL_ANYFORMAT</dt>
+ <dd>
+ <p>Normally, if a video surface of the requested bits-per-pixel (bpp) is not available, SDL will emulate one with a shadow surface.
+Passing SDL_ANYFORMAT prevents this and causes SDL to use the video surface, regardless of its pixel depth.</p>
+ </dd>
+ <dt>SDL_HWPALETTE</dt>
+ <dd>
+ <p>Give SDL exclusive palette access. Without this flag you may not always get the colors you request with SDL::set_colors or SDL::set_palette.</p>
+ </dd>
+ <dt>SDL_DOUBLEBUF</dt>
+ <dd>
+ <p>Enable hardware double buffering; only valid with SDL_HWSURFACE. Calling SDL::flip will flip the buffers and update the screen.
+All drawing will take place on the surface that is not displayed at the moment.
+If double buffering could not be enabled then SDL_Flip will just perform a SDL::update_rect on the entire screen.</p>
+ </dd>
+ <dt>SDL_FULLSCREEN</dt>
+ <dd>
+ <p>SDL will attempt to use a fullscreen mode. If a hardware resolution change is not possible (for whatever reason),
+the next higher resolution will be used and the display window centered on a black background.</p>
+ </dd>
+ <dt>SDL_OPENGL</dt>
+ <dd>
+ <p>Create an OpenGL rendering context. You should have previously set OpenGL video attributes with SDL::gl_setattribute.</p>
+ </dd>
+ <dt>SDL_OPENGLBLIT</dt>
+ <dd>
+ <p>Create an OpenGL rendering context, like above, but allow normal blitting operations.
+The screen (2D) surface may have an alpha channel, and SDL::update_rects must be used for updating changes to the screen surface.
+NOTE: This option is kept for compatibility only, and will be removed in next versions. Is not recommended for new code.</p>
+ </dd>
+ <dt>SDL_RESIZABLE</dt>
+ <dd>
+ <p>Create a resizable window.
+When the window is resized by the user a SDL_VIDEORESIZE event is generated and SDL::set_video_mode can be called again with the new size.</p>
+
+
+
+
+ </dd>
+ <dt>SDL_NOFRAME</dt>
+ <dd>
+ <p>If possible, SDL_NOFRAME causes SDL to create a window with no title bar or frame decoration.
+Fullscreen modes automatically have this flag set.</p>
+ </dd>
+</dl>
<p>Note 1: Use SDL_SWSURFACE if you plan on doing per-pixel manipulations, or blit surfaces with alpha channels, and require a high framerate. When you use hardware surfaces (by passing the flag SDL_HWSURFACE as parameter), SDL copies the surfaces from video memory to system memory when you lock them, and back when you unlock them. This can cause a major performance hit. Be aware that you may request a hardware surface, but receive a software surface because the video driver doesn't support hardware surface. Many platforms can only provide a hardware surface when using SDL_FULLSCREEN. The SDL_HWSURFACE flag is best used when the surfaces you'll be blitting can also be stored in video memory.</p>
<p>Note 2: If you want to control the position on the screen when creating a windowed surface, you may do so by setting the environment variables SDL_VIDEO_CENTERED=center or SDL_VIDEO_WINDOW_POS=x,y. You can also set them via <code>SDL::putenv</code>.</p>
<p>Note 3: This function should be called in the main thread of your application.</p>
<p>Creates an empty SDL::Surface from pixel data
Allocate an empty surface (must be called after SDL::set_video_mode)
If bitsPerPixel is 8 an empty palette is allocated for the surface, otherwise a 'packed-pixel' SDL::pixel_format is created using the [RGBA]mask's provided (see SDL::pixel_format). The flags specifies the type of surface that should be created, it is an OR'd combination of the following possible values. </p>
-<pre> SDL_SWSURFACE SDL will create the surface in system memory.
- This improves the performance of pixel level access, however you may not be able to take advantage of some types of hardware blitting.
-
- SDL_HWSURFACE SDL will attempt to create the surface in video memory.
- This will allow SDL to take advantage of Video->Video blits (which are often accelerated).
-
- SDL_SRCCOLORKEY This flag turns on color keying for blits from this surface.
- If SDL_HWSURFACE is also specified and color keyed blits are hardware-accelerated, then SDL will attempt to place the surface in video memory.
- If the screen is a hardware surface and color keyed blits are hardware-accelerated then the SDL_HWSURFACE flag will be set.
- Use SDL_SetColorKey to set or clear this flag after surface creation.
-
- SDL_SRCALPHA This flag turns on alpha-blending for blits from this surface.
- If SDL_HWSURFACE is also specified and alpha-blending blits are hardware-accelerated,
- then the surface will be placed in video memory if possible.
- If the screen is a hardware surface and alpha-blending blits are hardware-accelerated then the SDL_HWSURFACE flag will be set.
- Use SDL_SetAlpha to set or clear this flag after surface creation.
+<dl>
+ <dt>SDL_SWSURFACE</dt>
+ <dd>
+ <p>SDL will create the surface in system memory.
+This improves the performance of pixel level access, however you may not be able to take advantage of some types of hardware blitting.</p>
+ </dd>
+ <dt>SDL_HWSURFACE</dt>
+ <dd>
+ <p>SDL will attempt to create the surface in video memory.
+This will allow SDL to take advantage of Video->Video blits (which are often accelerated).</p>
+ </dd>
+ <dt>SDL_SRCCOLORKEY</dt>
+ <dd>
+ <p>This flag turns on color keying for blits from this surface.
+If SDL_HWSURFACE is also specified and color keyed blits are hardware-accelerated, then SDL will attempt to place the surface in video memory.
+If the screen is a hardware surface and color keyed blits are hardware-accelerated then the SDL_HWSURFACE flag will be set.
+Use SDL_SetColorKey to set or clear this flag after surface creation.</p>
+ </dd>
+ <dt>SDL_SRCALPHA</dt>
+ <dd>
+ <p>This flag turns on alpha-blending for blits from this surface.
+If SDL_HWSURFACE is also specified and alpha-blending blits are hardware-accelerated,
+then the surface will be placed in video memory if possible.
+If the screen is a hardware surface and alpha-blending blits are hardware-accelerated then the SDL_HWSURFACE flag will be set.
+Use SDL_SetAlpha to set or clear this flag after surface creation.</p>
+ </dd>
+</dl>
-</pre>
<p>[RGBA]mask are the bitmasks used to extract that colour from a pixel.
For instance, Rmask being FF000000 means the red data is stored in the most significant byte.
Using zeros for the RGB masks sets a default value, based on the depth. (e.g. SDL::create_RGB_surface(flags,w,h,32,0,0,0,0);).
The alpha parameter is the per-surface alpha value; a surface need not have an alpha channel to use per-surface alpha and blitting can still be accelerated with SDL_RLEACCEL.</p>
<p>Note: The per-surface alpha value of 128 is considered a special case and is optimised, so it's much faster than other per-surface values.</p>
<p>Alpha affects surface blitting in the following ways: </p>
-<pre> RGBA->RGB with SDL_SRCALPHA The source is alpha-blended with the destination, using the alpha channel.
- SDL_SRCCOLORKEY and the per-surface alpha are ignored.
-
- RGBA->RGB without SDL_SRCALPHA The RGB data is copied from the source. The source alpha channel and the per-surface alpha value are ignored.
- If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
-
- RGB->RGBA with SDL_SRCALPHA The source is alpha-blended with the destination using the per-surface alpha value.
- If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
- The alpha channel of the copied pixels is set to opaque.
-
- RGB->RGBA without SDL_SRCALPHA The RGB data is copied from the source and the alpha value of the copied pixels is set to opaque.
- If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
-
- RGBA->RGBA with SDL_SRCALPHA The source is alpha-blended with the destination using the source alpha channel.
- The alpha channel in the destination surface is left untouched. SDL_SRCCOLORKEY is ignored.
-
- RGBA->RGBA without SDL_SRCALPHA The RGBA data is copied to the destination surface.
- If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
-
- RGB->RGB with SDL_SRCALPHA The source is alpha-blended with the destination using the per-surface alpha value.
- If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
-
- RGB->RGB without SDL_SRCALPHA The RGB data is copied from the source.
- If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
-
-
-
-
-</pre>
+<dl>
+ <dt>RGBA->RGB with SDL_SRCALPHA</dt>
+ <dd>
+ <p>The source is alpha-blended with the destination, using the alpha channel.
+SDL_SRCCOLORKEY and the per-surface alpha are ignored.</p>
+ </dd>
+ <dt>RGBA->RGB without SDL_SRCALPHA</dt>
+ <dd>
+ <p>The RGB data is copied from the source. The source alpha channel and the per-surface alpha value are ignored.
+If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.</p>
+ </dd>
+ <dt>RGB->RGBA with SDL_SRCALPHA</dt>
+ <dd>
+ <p>The source is alpha-blended with the destination using the per-surface alpha value.
+If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.
+The alpha channel of the copied pixels is set to opaque.</p>
+ </dd>
+ <dt>RGB->RGBA without SDL_SRCALPHA</dt>
+ <dd>
+ <p>The RGB data is copied from the source and the alpha value of the copied pixels is set to opaque.
+If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.</p>
+ </dd>
+ <dt>RGBA->RGBA with SDL_SRCALPHA</dt>
+ <dd>
+ <p>The source is alpha-blended with the destination using the source alpha channel.
+The alpha channel in the destination surface is left untouched. SDL_SRCCOLORKEY is ignored.</p>
+ </dd>
+ <dt>RGBA->RGBA without SDL_SRCALPHA</dt>
+ <dd>
+ <p>The RGBA data is copied to the destination surface.
+If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.</p>
+ </dd>
+ <dt>RGB->RGB with SDL_SRCALPHA</dt>
+ <dd>
+ <p>The source is alpha-blended with the destination using the per-surface alpha value.
+If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.</p>
+ </dd>
+ <dt>RGB->RGB without SDL_SRCALPHA</dt>
+ <dd>
+ <p>The RGB data is copied from the source.
+If SDL_SRCCOLORKEY is set, only the pixels not matching the colorkey value are copied.</p>
+ </dd>
+</dl>
<p>Note: When blitting, the presence or absence of SDL_SRCALPHA is relevant only on the source surface, not the destination.
Note: Note that RGBA->RGBA blits (with SDL_SRCALPHA set) keep the alpha of the destination surface. This means that you cannot compose two arbitrary RGBA surfaces this way and get the result you would expect from "overlaying" them; the destination alpha will work as a mask.</p>
<p>Note: Also note that per-pixel and per-surface alpha cannot be combined; the per-pixel alpha is always used if available. </p>
</div>
<h2 id="unlock_YUV_overlay_overlay">unlock_YUV_overlay(overlay)</h2>
<div id="unlock_YUV_overlay_overlay_CONTENT">
-<p>The opposite to <code>SDL::lock_YUV_overlay. Unlocks a previously locked overlay. An overlay must be unlocked before it can be displayed.
-It returns 0 on succés or -1 on error.
-
-</code></p>
+<p>The opposite to <code>SDL::lock_YUV_overlay</code>. Unlocks a previously locked overlay. An overlay must be unlocked before it can be displayed.
+It returns 0 on succés or -1 on error.</p>
</div>
<h2 id="display_YUV_overlay_overlay_dstrect">display_YUV_overlay(overlay,dstrect)</h2>
<div class="blog">
-<div class="hover" onclick="window.location.href='/blog-0001.html'"><a href="/blog-0001.html">Once in a while .... (set_event_filter)</a><br /><span style="font-size: 10px">Friday, 13 November 2009</span><br />So I have been hacking for a while on SDL::Events::set_event_filter. The code below is an example usage. The magic behind this is here <br /> 1 #!/usr/bin/perl -w<br /> 2 use strict;<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0002.html'"><a href="/blog-0002.html">Hello Mouse? An Example of the New Event Code</a><br /><span style="font-size: 10px">Wednesday, 11 November 2009</span><br />You need the new code from the redesign branch to use this . <br /> #!/usr/bin/env perl<br />use SDL;<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0003.html'"><a href="/blog-0003.html">Development Update</a><br /><span style="font-size: 10px">Monday, 09 November 2009</span><br />Had an exam on the weekend so I am a bit late. Here is the progress so far. <br /> SDL::Video at 97% SDL::Events at 25% ~1000 tests cases passing on Windows and Linux <br /> <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0004.html'"><a href="/blog-0004.html">Development Update</a><br /><span style="font-size: 10px">Monday, 02 November 2009</span><br />In the past week the SDL Perl team has been busy! This is what we have accomplished<br /> Commitment to Testing! In an effort to focus on continuing our focus on testing we have setup a Smolder site for the SDL redesign process. Currently we have two platforms (linux, windows32) regularly tested on here. If there are more people following the redesign process and would like to share their test results; contact us at sdl-devel@perl.org and we will provide access to you.<br /> SDL::Video For the core development most of the focus has been on redesigning around the Video category of the SDL perl API. As of now we are 50% done . 19 functions out of 38 functions have been implemented and tested. <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0005.html'"><a href="/blog-0005.html">The Future and Beyond!</a><br /><span style="font-size: 10px">Saturday, 24 October 2009</span><br /> Updates 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 /> Core Development Acme ( Leon Brocard ): Has started to work on the Redesign Effort with me. The help is much appreciated! Enjoy your vacation. <br /> Website and Windows Testing FROGGS (Tobias Leich): 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 />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0006.html'"><a href="/blog-0006.html">The beginnings of modular design for SDL Perl</a><br /><span style="font-size: 10px">Sunday, 11 October 2009</span><br /> The design before <br />The bindings before were all in one huge XS file . 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 /> The design we are aiming for Simple one XS per Module. This would also simplify the Build code.<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0007.html'"><a href="/blog-0007.html">Why and How Frozen Bubble is going to CPAN</a><br /><span style="font-size: 10px">Friday, 02 October 2009</span><br /> <br /> [more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0008.html'"><a href="/blog-0008.html">HackFest: Results</a><br /><span style="font-size: 10px">Monday, 28 September 2009</span><br /> MacOSX build is working again. It's still rough but Tetris works on it now. dngor++ SDL::Tutorial::Tetris is on CPAN as v0.15. nferraz++ SDL Perl docs are a little better now. magnet++ Finally experimental Rect and Game::Rect are behaving. There is still more work needed in Game::Rect. Moreover there are more tests on the experimental release. garu++ Also POGL is working experimentally with SDL. <br /> Hopefully I can get the first three results into the next release soon. The next release 2.2.3 will go up as a developmental release first. Also the experimental branch is going up as version 2_4.<br /> Developers All developers please tell me what to put you guys want to be put down as on the <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0009.html'"><a href="/blog-0009.html">Updates, Falling Block Game, and Hack Fest</a><br /><span style="font-size: 10px">Wednesday, 23 September 2009</span><br />You can grab the code . Note you will have to install deps yourself. Read the README file. It is not a tutorial yet, because it was hacked together in ~50 hours. But it playable now. During building this I found out that MacOSX (and Snow Leopard) has died again.<br /> Hackfest So with dngor's help this sunday (27/09/09) we will have a hackfest to fix MacOSX support. Anyone with a MacOSX and wants to help is welcome on <a href="http://widget.mibbit.com/?settings=89f140215d60860684cee2f6a917607f&server=irc.perl.org&channel=%23sdl">#sdl irc.perl.org . We will also try to fix up a lot of docs and the tutorial for a early next week release. Also if we can we will migrate to the new site.[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0010.html'"><a href="/blog-0010.html">Thanks nothingmuch, and updates</a><br /><span style="font-size: 10px">Friday, 18 September 2009</span><br /> After a struggling with XS and opaque C structs in the experimental SDL::Rect for a long time. Nothingmuch comes along and solves my problem with this beautiful module XS::Object::Magic . So I will start moving my ugly XS to Magic Land.<br /> SDL Perl Tutorials <br />This past week I have been working on the sorry state of SDL Perl tutorials. Currently I am working on a Tetris Clone . I am hoping to have it done by next Thrusday for TPM meeting. This tutorial is a mix of several tutorials I found online . Another Lunar Lander tutorial has been submitted by Nelson Ferraz.<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0011.html'"><a href="/blog-0011.html">Design of SDL::Rect</a><br /><span style="font-size: 10px">Saturday, 12 September 2009</span><br />Lately we have been working on cleaning up the XS name spaces of SDL perl. After some bumps and falls we came up with a separated Rect module. Rect is one of the most simple C struct as shown below. <br /> <br />Using the awesome perlobject.map as a reference I was able to create a blessed perl object in XS . So now SDL::Rect->new(...) gave us a blessed reference ready to go. And as an icing it would destroy itself properly no matter where it was used. But once I brought it into our existing code base, garu pointed out the extending it was a little bit of a mess. So far to extend Rect we have to something like below. Any comment or advice would be much appreciated.<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0012.html'"><a href="/blog-0012.html">Updates and Design Decisions</a><br /><span style="font-size: 10px">Wednesday, 09 September 2009</span><br /> <br /> <br /> --yapgh [more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0013.html'"><a href="/blog-0013.html">Why I will be sticking to CPAN</a><br /><span style="font-size: 10px">Sunday, 06 September 2009</span><br />Recently there was really long discussion on sdl-devel@perl.org about providing packages for SDL perl rather than focusing on CPAN releases. The gists of the argument was that SDL perl should be making platform specific packages for end users. I agree with this idea but I do have to face the truth. <br />The truth is there are very few developers currently working on SDL Perl. The truth is CPAN provides several tools that which currently drives development for SDL Perl. There are people interested in packaging SDL Perl ( kmx , jean and Jerome Quelin). The truth is there are other very critical areas we can focus on. <br />If there are people looking to package SDL Perl for their platform please contact us at sdl-devel@perl.org.[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0014.html'"><a href="/blog-0014.html">Frozen Bubble coming to CPAN</a><br /><span style="font-size: 10px">Friday, 04 September 2009</span><br /> To do this the Makefile.PL will need to be rewritten a little bit. Moreover we will need to make test using code from Frozen Bubble so that it can be smoke tested on CPAN. If contributors need more information please contact me. [more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0015.html'"><a href="/blog-0015.html">Newbie Friendly Perl Projects</a><br /><span style="font-size: 10px">Thursday, 03 September 2009</span><br />This is a reply to szabgab's post on how to get newbies interested in Perl modules. Being a newbie in Perl myself I thought I should take a shot.<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 /> Look at SDL docs [ link ] See where SDL_perl is using the same functions [ link ] and the docs to this file [ link ] Use the pod format to add it to the source [ link to using pod ] {BONUS} Come up with tutorial or cookbook [ link to example ] Submit code to github [ link ] or email them to me [<a href="mailto:kthakore@cpan.org">link ]<br /> <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 /> --yapgh [more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0016.html'"><a href="/blog-0016.html">Can someone please point me to good XS documentation!</a><br /><span style="font-size: 10px">Thursday, 03 September 2009</span><br /> A poor man begs,<br />A troubled man prays,<br />who shall answer? <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0017.html'"><a href="/blog-0017.html">More Games + Update</a><br /><span style="font-size: 10px">Tuesday, 01 September 2009</span><br />So while I am hacking away on v2.4 and breaking a lot of things. Here is a link to some more games for SDL Perl. These only work in windows now but I will look into bringing them to CPAN (with Garry's permission). <br /> --yapgh <br />These where reported by Garry Taylor. Here is the rest of the email:<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0018.html'"><a href="/blog-0018.html">Updates on Plan for v2.4</a><br /><span style="font-size: 10px">Monday, 31 August 2009</span><br /> After some hunting for memory leaks, it became obvious that some rewrite of XS will be necessary. Since this will be a big undertaking I asked for some help from chromatic and garu . We came up with the following plan for v2.4. <br /> Currently all XS is mapped to the SDL_perl module. This does not reflect the modular nature of the sdl libs. So the plan is to gradually move SDL structs and their respective functions to their correct namespaces. We will start with SDL::Rect as garu has added many tests for it. This way the build system will be a lot easier to hack since Module::Build was made for one XS per module. Moreover we will move the Build utilities to Alien::SDL, making it even simpler. The main idea is to adhere to single responsibility principle and encapsulation. <br /> Obviously this will take some time and effort, but it will pay off in the long run. Any help will be greatly appreciated. <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0019.html'"><a href="/blog-0019.html">Code is not the only thing</a><br /><span style="font-size: 10px">Sunday, 30 August 2009</span><br /> After only several weeks of maintaining SDL perl, Today I have come to noticed how important it is to update README's, docs and so on. I will redouble my effort to do this . <br /> However I am not sure where to start updating docs. Has anyone re-documented old modules before? Any advice? If anyone is interested in helping me to sort out documentation please contact me on sdl-devel@perl.org. For people wanting to learn the SDL base there is no better way.<br /> [more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0020.html'"><a href="/blog-0020.html">SDL Perl v2.2.2 out and Plans for v2.4</a><br /><span style="font-size: 10px">Saturday, 29 August 2009</span><br /> I have release v2.2.2 which includes several bug fixes:<br /> Made App loop() faster RT Patched support for add support for gluquadric* sub RT Made App init slimer RT Added faster SDL::Color alternative RT Added better error reporting for TTFont errors Added experimental win32 support RT [Update: v2.2.2.5 is better for windows support] <br /> You can grab this release off CPAN . <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0021.html'"><a href="/blog-0021.html">Catching memory leaks in XS</a><br /><span style="font-size: 10px">Friday, 28 August 2009</span><br />So I am trying to find and plug memory leaks in SDL perl. Most of the memory leaks occur because in XS a reference is still held. One very expensive mem leak was caught by TELS really early on here . The problem occurs where in XS there is<br /> RETVAL = (cast *) safemalloc( ... ); and safefree(...) is never called.<br />Here is a in code example lines 1082 on. <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0022.html'"><a href="/blog-0022.html">Alien::SDL 0.01 released!!!</a><br /><span style="font-size: 10px">Thursday, 27 August 2009</span><br />With yesterday's frantic coding to get windows compatibility setup we were left with a very crude way of installing. After some late night hacking I finally came up with Alias's suggestion to have Alien::SDL. All thanks to Alias's generous access to his windows farm , I was able to make a easier module to install SDL deps on windows. Future plans are in place to get sources and compile them for other platform.Hopefully a SDL perl release will be out soon to use Alien::SDL now.<br />The above script is in test/testsprite.pl. <br />Until then you can do:<br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0023.html'"><a href="/blog-0023.html">SDL perl is coming to Strawberry!!</a><br /><span style="font-size: 10px">Wednesday, 26 August 2009</span><br />You can follow the history here .<br />It has been tested on winXP 32/64 bit strawberry so far. Here is how you can get it.<br /> Go here to get the code Click download, choose .tar.gz Save the resultant kthakore....tar.gz somewhere Get this and extract it on C:/strawberry/ Last do pip kthakore......tar.gz (I find this so amazing!!) Play with C:/strawberry/cpan/build/SDL/test/*.pl or post a bug report <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0024.html'"><a href="/blog-0024.html">My milestones (itches) for gaming in Perl</a><br /><span style="font-size: 10px">Tuesday, 25 August 2009</span><br />As a new Perl developer I am able to contribute with great enthusiasm due to the great community and the fancies of the language. However I know that these things will fade and I will need something else to take the place. Usually what has worked for me in the past was to set milestones. These will act as roots, keeping me interested in being involved. After all in words better than mines.<br /> We all “scratch our own itches”. It’s why I started Linux, it’s why I started git, and it’s why I am still involved. -- Linus <br /> <br />[more]<br /><br /></div><div class="hover" onclick="window.location.href='/blog-0025.html'"><a href="/blog-0025.html">SDL Perl Windows Status</a><br /><span style="font-size: 10px">Monday, 24 August 2009</span><br />Hello windows users,<br /> Here is a simple picture explaining the status of SDL Perl on windows. I am hoping this changes. I know that Alias is interested in this too. <br />Here are steps needed to solve this:<br />[more]<br /><br /></div></div>
+<div class="hover" onclick="window.location.href='blog-0001.html'"><a href="blog-0001.html">Once in a while .... (set_event_filter)</a><br /><span style="font-size: 10px">Friday, 13 November 2009</span><br />So I have been hacking for a while on SDL::Events::set_event_filter. The code below is an example usage. The magic behind this is here <br /> 1 #!/usr/bin/perl -w<br /> 2 use strict;<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0002.html'"><a href="blog-0002.html">Hello Mouse? An Example of the New Event Code</a><br /><span style="font-size: 10px">Wednesday, 11 November 2009</span><br />You need the new code from the redesign branch to use this . <br /> #!/usr/bin/env perl<br />use SDL;<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0003.html'"><a href="blog-0003.html">Development Update</a><br /><span style="font-size: 10px">Monday, 09 November 2009</span><br />Had an exam on the weekend so I am a bit late. Here is the progress so far. <br /> SDL::Video at 97% SDL::Events at 25% ~1000 tests cases passing on Windows and Linux <br /> <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0004.html'"><a href="blog-0004.html">Development Update</a><br /><span style="font-size: 10px">Monday, 02 November 2009</span><br />In the past week the SDL Perl team has been busy! This is what we have accomplished<br /> Commitment to Testing! In an effort to focus on continuing our focus on testing we have setup a Smolder site for the SDL redesign process. Currently we have two platforms (linux, windows32) regularly tested on here. If there are more people following the redesign process and would like to share their test results; contact us at sdl-devel@perl.org and we will provide access to you.<br /> SDL::Video For the core development most of the focus has been on redesigning around the Video category of the SDL perl API. As of now we are 50% done . 19 functions out of 38 functions have been implemented and tested. <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0005.html'"><a href="blog-0005.html">The Future and Beyond!</a><br /><span style="font-size: 10px">Saturday, 24 October 2009</span><br /> Updates 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 /> Core Development Acme ( Leon Brocard ): Has started to work on the Redesign Effort with me. The help is much appreciated! Enjoy your vacation. <br /> Website and Windows Testing FROGGS (Tobias Leich): 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 />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0006.html'"><a href="blog-0006.html">The beginnings of modular design for SDL Perl</a><br /><span style="font-size: 10px">Sunday, 11 October 2009</span><br /> The design before <br />The bindings before were all in one huge XS file . 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 /> The design we are aiming for Simple one XS per Module. This would also simplify the Build code.<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0007.html'"><a href="blog-0007.html">Why and How Frozen Bubble is going to CPAN</a><br /><span style="font-size: 10px">Friday, 02 October 2009</span><br /> <br /> [more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0008.html'"><a href="blog-0008.html">HackFest: Results</a><br /><span style="font-size: 10px">Monday, 28 September 2009</span><br /> MacOSX build is working again. It's still rough but Tetris works on it now. dngor++ SDL::Tutorial::Tetris is on CPAN as v0.15. nferraz++ SDL Perl docs are a little better now. magnet++ Finally experimental Rect and Game::Rect are behaving. There is still more work needed in Game::Rect. Moreover there are more tests on the experimental release. garu++ Also POGL is working experimentally with SDL. <br /> Hopefully I can get the first three results into the next release soon. The next release 2.2.3 will go up as a developmental release first. Also the experimental branch is going up as version 2_4.<br /> Developers All developers please tell me what to put you guys want to be put down as on the <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0009.html'"><a href="blog-0009.html">Updates, Falling Block Game, and Hack Fest</a><br /><span style="font-size: 10px">Wednesday, 23 September 2009</span><br />You can grab the code . Note you will have to install deps yourself. Read the README file. It is not a tutorial yet, because it was hacked together in ~50 hours. But it playable now. During building this I found out that MacOSX (and Snow Leopard) has died again.<br /> Hackfest So with dngor's help this sunday (27/09/09) we will have a hackfest to fix MacOSX support. Anyone with a MacOSX and wants to help is welcome on <a href="http://widget.mibbit.com/?settings=89f140215d60860684cee2f6a917607f&server=irc.perl.org&channel=%23sdl">#sdl irc.perl.org . We will also try to fix up a lot of docs and the tutorial for a early next week release. Also if we can we will migrate to the new site.[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0010.html'"><a href="blog-0010.html">Thanks nothingmuch, and updates</a><br /><span style="font-size: 10px">Friday, 18 September 2009</span><br /> After a struggling with XS and opaque C structs in the experimental SDL::Rect for a long time. Nothingmuch comes along and solves my problem with this beautiful module XS::Object::Magic . So I will start moving my ugly XS to Magic Land.<br /> SDL Perl Tutorials <br />This past week I have been working on the sorry state of SDL Perl tutorials. Currently I am working on a Tetris Clone . I am hoping to have it done by next Thrusday for TPM meeting. This tutorial is a mix of several tutorials I found online . Another Lunar Lander tutorial has been submitted by Nelson Ferraz.<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0011.html'"><a href="blog-0011.html">Design of SDL::Rect</a><br /><span style="font-size: 10px">Saturday, 12 September 2009</span><br />Lately we have been working on cleaning up the XS name spaces of SDL perl. After some bumps and falls we came up with a separated Rect module. Rect is one of the most simple C struct as shown below. <br /> <br />Using the awesome perlobject.map as a reference I was able to create a blessed perl object in XS . So now SDL::Rect->new(...) gave us a blessed reference ready to go. And as an icing it would destroy itself properly no matter where it was used. But once I brought it into our existing code base, garu pointed out the extending it was a little bit of a mess. So far to extend Rect we have to something like below. Any comment or advice would be much appreciated.<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0012.html'"><a href="blog-0012.html">Updates and Design Decisions</a><br /><span style="font-size: 10px">Wednesday, 09 September 2009</span><br /> <br /> <br /> --yapgh [more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0013.html'"><a href="blog-0013.html">Why I will be sticking to CPAN</a><br /><span style="font-size: 10px">Sunday, 06 September 2009</span><br />Recently there was really long discussion on sdl-devel@perl.org about providing packages for SDL perl rather than focusing on CPAN releases. The gists of the argument was that SDL perl should be making platform specific packages for end users. I agree with this idea but I do have to face the truth. <br />The truth is there are very few developers currently working on SDL Perl. The truth is CPAN provides several tools that which currently drives development for SDL Perl. There are people interested in packaging SDL Perl ( kmx , jean and Jerome Quelin). The truth is there are other very critical areas we can focus on. <br />If there are people looking to package SDL Perl for their platform please contact us at sdl-devel@perl.org.[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0014.html'"><a href="blog-0014.html">Frozen Bubble coming to CPAN</a><br /><span style="font-size: 10px">Friday, 04 September 2009</span><br /> To do this the Makefile.PL will need to be rewritten a little bit. Moreover we will need to make test using code from Frozen Bubble so that it can be smoke tested on CPAN. If contributors need more information please contact me. [more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0015.html'"><a href="blog-0015.html">Newbie Friendly Perl Projects</a><br /><span style="font-size: 10px">Thursday, 03 September 2009</span><br />This is a reply to szabgab's post on how to get newbies interested in Perl modules. Being a newbie in Perl myself I thought I should take a shot.<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 /> Look at SDL docs [ link ] See where SDL_perl is using the same functions [ link ] and the docs to this file [ link ] Use the pod format to add it to the source [ link to using pod ] {BONUS} Come up with tutorial or cookbook [ link to example ] Submit code to github [ link ] or email them to me [<a href="mailto:kthakore@cpan.org">link ]<br /> <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 /> --yapgh [more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0016.html'"><a href="blog-0016.html">Can someone please point me to good XS documentation!</a><br /><span style="font-size: 10px">Thursday, 03 September 2009</span><br /> A poor man begs,<br />A troubled man prays,<br />who shall answer? <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0017.html'"><a href="blog-0017.html">More Games + Update</a><br /><span style="font-size: 10px">Tuesday, 01 September 2009</span><br />So while I am hacking away on v2.4 and breaking a lot of things. Here is a link to some more games for SDL Perl. These only work in windows now but I will look into bringing them to CPAN (with Garry's permission). <br /> --yapgh <br />These where reported by Garry Taylor. Here is the rest of the email:<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0018.html'"><a href="blog-0018.html">Updates on Plan for v2.4</a><br /><span style="font-size: 10px">Monday, 31 August 2009</span><br /> After some hunting for memory leaks, it became obvious that some rewrite of XS will be necessary. Since this will be a big undertaking I asked for some help from chromatic and garu . We came up with the following plan for v2.4. <br /> Currently all XS is mapped to the SDL_perl module. This does not reflect the modular nature of the sdl libs. So the plan is to gradually move SDL structs and their respective functions to their correct namespaces. We will start with SDL::Rect as garu has added many tests for it. This way the build system will be a lot easier to hack since Module::Build was made for one XS per module. Moreover we will move the Build utilities to Alien::SDL, making it even simpler. The main idea is to adhere to single responsibility principle and encapsulation. <br /> Obviously this will take some time and effort, but it will pay off in the long run. Any help will be greatly appreciated. <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0019.html'"><a href="blog-0019.html">Code is not the only thing</a><br /><span style="font-size: 10px">Sunday, 30 August 2009</span><br /> After only several weeks of maintaining SDL perl, Today I have come to noticed how important it is to update README's, docs and so on. I will redouble my effort to do this . <br /> However I am not sure where to start updating docs. Has anyone re-documented old modules before? Any advice? If anyone is interested in helping me to sort out documentation please contact me on sdl-devel@perl.org. For people wanting to learn the SDL base there is no better way.<br /> [more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0020.html'"><a href="blog-0020.html">SDL Perl v2.2.2 out and Plans for v2.4</a><br /><span style="font-size: 10px">Saturday, 29 August 2009</span><br /> I have release v2.2.2 which includes several bug fixes:<br /> Made App loop() faster RT Patched support for add support for gluquadric* sub RT Made App init slimer RT Added faster SDL::Color alternative RT Added better error reporting for TTFont errors Added experimental win32 support RT [Update: v2.2.2.5 is better for windows support] <br /> You can grab this release off CPAN . <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0021.html'"><a href="blog-0021.html">Catching memory leaks in XS</a><br /><span style="font-size: 10px">Friday, 28 August 2009</span><br />So I am trying to find and plug memory leaks in SDL perl. Most of the memory leaks occur because in XS a reference is still held. One very expensive mem leak was caught by TELS really early on here . The problem occurs where in XS there is<br /> RETVAL = (cast *) safemalloc( ... ); and safefree(...) is never called.<br />Here is a in code example lines 1082 on. <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0022.html'"><a href="blog-0022.html">Alien::SDL 0.01 released!!!</a><br /><span style="font-size: 10px">Thursday, 27 August 2009</span><br />With yesterday's frantic coding to get windows compatibility setup we were left with a very crude way of installing. After some late night hacking I finally came up with Alias's suggestion to have Alien::SDL. All thanks to Alias's generous access to his windows farm , I was able to make a easier module to install SDL deps on windows. Future plans are in place to get sources and compile them for other platform.Hopefully a SDL perl release will be out soon to use Alien::SDL now.<br />The above script is in test/testsprite.pl. <br />Until then you can do:<br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0023.html'"><a href="blog-0023.html">SDL perl is coming to Strawberry!!</a><br /><span style="font-size: 10px">Wednesday, 26 August 2009</span><br />You can follow the history here .<br />It has been tested on winXP 32/64 bit strawberry so far. Here is how you can get it.<br /> Go here to get the code Click download, choose .tar.gz Save the resultant kthakore....tar.gz somewhere Get this and extract it on C:/strawberry/ Last do pip kthakore......tar.gz (I find this so amazing!!) Play with C:/strawberry/cpan/build/SDL/test/*.pl or post a bug report <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0024.html'"><a href="blog-0024.html">My milestones (itches) for gaming in Perl</a><br /><span style="font-size: 10px">Tuesday, 25 August 2009</span><br />As a new Perl developer I am able to contribute with great enthusiasm due to the great community and the fancies of the language. However I know that these things will fade and I will need something else to take the place. Usually what has worked for me in the past was to set milestones. These will act as roots, keeping me interested in being involved. After all in words better than mines.<br /> We all “scratch our own itches”. It’s why I started Linux, it’s why I started git, and it’s why I am still involved. -- Linus <br /> <br />[more]<br /><br /></div><hr /><div class="hover" onclick="window.location.href='blog-0025.html'"><a href="blog-0025.html">SDL Perl Windows Status</a><br /><span style="font-size: 10px">Monday, 24 August 2009</span><br />Hello windows users,<br /> Here is a simple picture explaining the status of SDL Perl on windows. I am hoping this changes. I know that Alias is interested in this too. <br />Here are steps needed to solve this:<br />[more]<br /><br /></div><hr /></div>
projects / sdlgit/SDL-Site.git / commitdiff