<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    
    <title>Shadowmaster’s Blog - Wesnoth-TC</title>
    <link>http://shadowm.rewound.net/blog/</link>
    <description>A light in the darkness, where everything is possible...</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.6.2 - http://www.s9y.org/</generator>
    
    

<item>
    <title>Wesnoth-TC 1.5.1, and the future</title>
    <link>http://shadowm.rewound.net/blog/archives/241-Wesnoth-TC-1.5.1,-and-the-future.html</link>
            <category>Miscellaneous</category>
            <category>Personal</category>
            <category>Projects</category>
            <category>Software</category>
            <category>Wesnoth</category>
            <category>Wesnoth RCX</category>
            <category>Wesnoth-TC</category>
    
    <comments>http://shadowm.rewound.net/blog/archives/241-Wesnoth-TC-1.5.1,-and-the-future.html#comments</comments>
    <wfw:comment>http://shadowm.rewound.net/blog/wfwcomment.php?cid=241</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://shadowm.rewound.net/blog/rss.php?version=2.0&amp;type=comments&amp;cid=241</wfw:commentRss>
    

    <author>nospam@example.com (shadowmaster)</author>
    <content:encoded>
    &lt;p&gt;Wesnoth-TC 1.5.1 has just been released... or maybe not. It has actually been tagged for more than 24 hours already.&lt;/p&gt;

&lt;p&gt;This version is really just a bug-fix release, which is why it’s not 1.6.0. In fact, it only really addresses some build-time issues that have cropped up over the last couple of years.&lt;/p&gt;

&lt;h3&gt;Downloads&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Source code:&lt;/strong&gt; &lt;a href=&quot;http://sourceforge.net/projects/wesnoth-tc/files/1.5.1/wesnoth-tc-1.5.1.tar.bz2/download&quot;&gt;wesnoth-tc-1.5.1.tar.bz2&lt;/a&gt; (156.2 KiB)&lt;br /&gt;
			&lt;small&gt;SHA1 checksum: &lt;tt&gt;f9be5147991719b114046e0573d46ca39479ce69&lt;/tt&gt;&lt;/small&gt;&lt;/li&gt;
			&lt;li&gt;&lt;strong&gt;Windows (Win32) binary:&lt;/strong&gt; &lt;a href=&quot;http://sourceforge.net/projects/wesnoth-tc/files/1.5.1/wesnoth-tc-1.5.1-win32.zip/download&quot;&gt;wesnoth-tc-1.5.1-win32.zip&lt;/a&gt; (383.6 KiB)&lt;br /&gt;
			&lt;small&gt;SHA1 checksum: &lt;tt&gt;b74f26ea3743917433be4f3ca0c0be1a5647b40b&lt;/tt&gt;&lt;/small&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;Instructions&lt;/h3&gt;

&lt;p&gt;Both distributions come with a &lt;tt&gt;README&lt;/tt&gt; file, and the source code distribution also includes an &lt;tt&gt;INSTALL&lt;/tt&gt; file with detailed instructions for configuring, compiling and installing Wesnoth-TC. The Windows binary distribution doesn&#039;t require any installation besides unpacking it into an appropriate directory — which you may optionally add to &lt;tt&gt;PATH&lt;/tt&gt;.&lt;/p&gt;

&lt;h3&gt;The past, and the future&lt;/h3&gt;

&lt;p&gt;&lt;a href=&quot;http://forums.wesnoth.org/viewtopic.php?p=319979#p319979&quot;&gt;Long ago&lt;/a&gt;, this came into existence. At the time, I needed a quick way to preview my own team-colored unit sprites without going through the hassle of starting/restarting Wesnoth (or its internal cache), loading a saved game, and creating units in debug-mode. That was my initial motivation for writing Wesnoth-TC, and since it was tailored to my specific needs, it was born as a console application. I later decided to publish and extend it, hoping that someone else would provide a good full-featured user interface for it.&lt;/p&gt;

&lt;p&gt;Actual artists prefer using &lt;em&gt;graphical&lt;/em&gt; user interface applications on Windows and Mac OS X, and with good reason. That’s the software interaction paradigm that suits visual types better for obvious reasons, and that’s why I took it upon myself to write a larger GUI front-end for Wesnoth-TC that could be built and run on the three major platforms from a single code-base.&lt;/p&gt;

&lt;p&gt;That front-end quickly became an &lt;em&gt;adaptation&lt;/em&gt; of the original back-end code. And thus &lt;a href=&quot;/projects/wesnoth-tc.php&quot;&gt;Wesnoth RCX&lt;/a&gt; became an entirely separate project sharing little more than a bit of history with Wesnoth-TC. And most importantly, Wesnoth RCX became the first GUI (Qt 4) application I have ever written.&lt;/p&gt;

&lt;p&gt;Over time, my needs and personal preferences have changed. Wesnoth-TC now feels largely inferior to RCX merely because of the lack of a native front-end for it. RCX has also recently gained visual palette and color range editing capabilities, which renders Wesnoth-TC’s definition file system somewhat obsolete. Furthermore, RCX has continued to compile and run correctly over time regardless of the Qt 4 version currently installed, whereas Wesnoth-TC has broken in a few occasions with newer development environments.&lt;/p&gt;

&lt;p&gt;Wesnoth-TC truly feels like a relic now, one I don’t really want to continue developing at this time when I feel RCX is more fun to improve and work with. I had plans to eventually integrate a full-fledged implementation of the Wesnoth &lt;a href=&quot;http://wiki.wesnoth.org/ImagePathFunctionWML&quot;&gt;Image Path Functions&lt;/a&gt; mechanism, but that seems over-ambitious right now.&lt;/p&gt;

&lt;p&gt;So, yeah, Wesnoth RCX is the future. Stay tuned for version 0.2.0, coming soon with more features and improvements.&lt;/p&gt; 
    </content:encoded>

    <pubDate>Tue, 31 Jul 2012 04:58:00 +0000</pubDate>
    <guid isPermaLink="false">http://shadowm.rewound.net/blog/archives/241-guid.html</guid>
    
</item>
<item>
    <title>Wesnoth-TC and Wesnoth RCX moved to Github</title>
    <link>http://shadowm.rewound.net/blog/archives/240-Wesnoth-TC-and-Wesnoth-RCX-moved-to-Github.html</link>
            <category>Miscellaneous</category>
            <category>Personal</category>
            <category>Projects</category>
            <category>Software</category>
            <category>Wesnoth</category>
            <category>Wesnoth RCX</category>
            <category>Wesnoth-TC</category>
    
    <comments>http://shadowm.rewound.net/blog/archives/240-Wesnoth-TC-and-Wesnoth-RCX-moved-to-Github.html#comments</comments>
    <wfw:comment>http://shadowm.rewound.net/blog/wfwcomment.php?cid=240</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://shadowm.rewound.net/blog/rss.php?version=2.0&amp;type=comments&amp;cid=240</wfw:commentRss>
    

    <author>nospam@example.com (shadowmaster)</author>
    <content:encoded>
    &lt;p&gt;I have just finished moving &lt;a href=&quot;/projects/wesnoth-tc.php&quot;&gt;Wesnoth-TC and Wesnoth RCX&lt;/a&gt; to &lt;a href=&quot;https://github.com/&quot;&gt;Github&lt;/a&gt; — in my humble uneducated non-expert opinion, a much nicer place to be than Gitorious, which still lacks native &lt;a href=&quot;http://cia.vc/&quot;&gt;CIA.vc&lt;/a&gt; support after all these years. Instead, Github supports CIA.vc &lt;strong&gt;and&lt;/strong&gt; a large amount of alternatives which I’ll probably never use.&lt;/p&gt;

&lt;p&gt;The project page on this website has been updated accordingly. If you were tracking the repositories at Gitorious, you will &lt;strong&gt;not&lt;/strong&gt; be able to get further updates unless you update your configuration to point to the new locations:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;strong&gt;Wesnoth-TC:&lt;/strong&gt;&lt;br /&gt;
    HTTP transport: &lt;pre&gt;https://github.com/shikadilord/wesnoth-tc.git&lt;/pre&gt;
    Git transport: &lt;pre&gt;git://github.com/shikadilord/wesnoth-tc.git&lt;/pre&gt;
  &lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Wesnoth RCX (codename &lt;em&gt;Morning Star&lt;/em&gt;):&lt;/strong&gt;&lt;br /&gt;
    HTTP transport: &lt;pre&gt;https://github.com/shikadilord/morningstar.git&lt;/pre&gt;
    Git transport: &lt;pre&gt;git://github.com/shikadilord/morningstar.git&lt;/pre&gt;
  &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Updating client repositories is actually far easier than it sounds:&lt;/p&gt;

&lt;pre&gt;$ git remote set-url origin &amp;lt;new URL&amp;gt;&lt;/pre&gt;

&lt;p&gt;Afterwards, you should be able to fetch/pull as usual.&lt;/p&gt;

&lt;p&gt;This switch actually began some time ago when I was considering resuming Wesnoth RCX’s development (which stagnated &lt;a href=&quot;http://shadowm.rewound.net/blog/archives/139-Wesnoth-RCX-0.1.4.html&quot;&gt;‘some’ time ago&lt;/a&gt; too). It took a while, but I finally seem to be back on track, all thanks to my currently unannounced self-imposed campaign development break — a break that should allow me to get back to business soon enough, with the renewed energy and &lt;em&gt;coder momentum&lt;/em&gt; I will seriously need in order to pull &lt;a href=&quot;http://shadowm.rewound.net/blog/archives/236-After-the-Storm-0.8.1.html&quot;&gt;&lt;em&gt;*it*&lt;/em&gt;&lt;/a&gt; off.&lt;/p&gt;

&lt;p&gt;Wesnoth RCX 0.2.0 will probably be released before the end of this week, as soon as I make sure everything works as intended, which will be less trivial this time due to the new shiny features it packs. There’s also a couple of Windows-specific oddities that I want to tackle before releasing.&lt;/p&gt;

&lt;p&gt;Oh, and in the meantime there will be an update regarding Wesnoth-TC’s future.&lt;/p&gt;
 
    </content:encoded>

    <pubDate>Mon, 30 Jul 2012 09:11:13 +0000</pubDate>
    <guid isPermaLink="false">http://shadowm.rewound.net/blog/archives/240-guid.html</guid>
    
</item>

</channel>
</rss>