<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sergiy&#039;s Noter</title>
	<atom:link href="http://sergiy.kyrylkov.name/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://sergiy.kyrylkov.name/blog</link>
	<description>Technical Blog of Sergiy Kyrylkov</description>
	<lastBuildDate>Wed, 01 Dec 2010 07:46:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Python Twitter 0.6 followers bug</title>
		<link>http://sergiy.kyrylkov.name/blog/2010/06/python-twitter-0-6-followers-bug/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2010/06/python-twitter-0-6-followers-bug/#comments</comments>
		<pubDate>Sun, 27 Jun 2010 06:37:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[e-commerce]]></category>
		<category><![CDATA[python twitter]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=137</guid>
		<description><![CDATA[If you want to use Python with Twitter API, skip Python Twitter library for now.  Get followers for any user bug makes version 0.6 pretty much useless.  In addition to this, both next_cursor and previous_cursor are not supported.
]]></description>
			<content:encoded><![CDATA[<p>If you want to use Python with Twitter API, skip <a href="http://code.google.com/p/python-twitter">Python Twitter library</a> for now.  <a href="http://code.google.com/p/python-twitter/issues/detail?id=47">Get followers for any user bug</a> makes version 0.6 pretty much useless.  In addition to this, both next_cursor and previous_cursor are not supported.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2010/06/python-twitter-0-6-followers-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Payment problems in Magento Paypal Standard with IPN after upgrade from 1.3.x to 1.4.0.1</title>
		<link>http://sergiy.kyrylkov.name/blog/2010/05/payment-problems-in-magento-paypal-standard-with-ipn-after-upgrade-from-1-3-x-to-1-4-0-1/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2010/05/payment-problems-in-magento-paypal-standard-with-ipn-after-upgrade-from-1-3-x-to-1-4-0-1/#comments</comments>
		<pubDate>Fri, 21 May 2010 18:04:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[e-commerce]]></category>
		<category><![CDATA[magento]]></category>
		<category><![CDATA[paypal]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=66</guid>
		<description><![CDATA[Those who, after a seemingly successful upgrade from Magento 1.3.x to Magento 1.4.0.1, have problems with Magento acknowledging PayPal payments (changing order status from Pending Payment to Processing) and sending out New Order emails to their clients should do/check the following things:

In PayPal: Go to My Account -&#62; Profiles -&#62; More Options -&#62; Instant Payment [...]]]></description>
			<content:encoded><![CDATA[<p>Those who, after a seemingly successful upgrade from Magento 1.3.x to Magento 1.4.0.1, have problems with Magento acknowledging PayPal payments (changing order status from <em>Pending Payment</em> to <em>Processing</em>) and sending out New Order emails to their clients should do/check the following things:</p>
<ol>
<li><strong>In PayPal</strong>: Go to <em>My Account -&gt; Profiles -&gt; More Options -&gt; Instant Payment Notification Preferences -&gt; Edit Settings</em> and change instant payment notification (IPN) URL in PayPal IPN settings from:
<pre>http://www.yoursite.com/paypal/standard/ipn/</pre>
<p>to:</p>
<pre>http://www.yoursite.com/paypal/ipn/standard/</pre>
</li>
<li><strong>In Magento admin panel</strong>: Go to <em>Systems -&gt; Configuration -&gt; Payment Methods -&gt; PayPal Website Payments Standard</em> and check that <em>Payment Action</em> is set to <em>Sale </em>and <em>New Order</em> status to <em>Processing</em></li>
<li><strong>In Magento code</strong>: In file <em>Ipn.php</em> located in <em>app/code/core/Mage/Paypal/Model/Ipn.php</em> find function:
<pre><code>public function getIpnFormData($key = null)</code></pre>
<p>comment out line:</p>
<pre><code>//return isset($this-&gt;_ipnFormData[$key]) ? $this-&gt;_ipnFormData[$key] : null;</code></pre>
<p>and add the following line immediately after it:</p>
<pre><code>return isset($this-&gt;_ipnFormData[$key]) ? urldecode($this-&gt;_ipnFormData[$key]) : null;</code></pre>
</li>
</ol>
<p>This should do it.  Your order status should be changing from <em>Pending Payment</em> to <em>Processing</em> and emails should work also.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2010/05/payment-problems-in-magento-paypal-standard-with-ipn-after-upgrade-from-1-3-x-to-1-4-0-1/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Установка 1С:Предприятия 8.1 на Red Hat Enterprise Linux 5 (RHEL 5, CentOS 5)</title>
		<link>http://sergiy.kyrylkov.name/blog/2008/03/%d1%83%d1%81%d1%82%d0%b0%d0%bd%d0%be%d0%b2%d0%ba%d0%b0-1%d1%81%d0%bf%d1%80%d0%b5%d0%b4%d0%bf%d1%80%d0%b8%d1%8f%d1%82%d0%b8%d1%8f-8-1-%d0%bd%d0%b0-red-hat-enterprise-linux-5-rhel-5-centos-5/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2008/03/%d1%83%d1%81%d1%82%d0%b0%d0%bd%d0%be%d0%b2%d0%ba%d0%b0-1%d1%81%d0%bf%d1%80%d0%b5%d0%b4%d0%bf%d1%80%d0%b8%d1%8f%d1%82%d0%b8%d1%8f-8-1-%d0%bd%d0%b0-red-hat-enterprise-linux-5-rhel-5-centos-5/#comments</comments>
		<pubDate>Sun, 23 Mar 2008 13:11:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=60</guid>
		<description><![CDATA[Для установки сервера 1С:Предприятия 8.1 (без Web Services) и PostgresSQL 8.2 понадобятся следующие пакеты:

1C_Enterprise-server
1C_Enterprise-server-nls
1C_Enterprise-common
1C_Enterprise-common-nls
postgresql
postgresql-server
postgresql-contrib
postgresql-libs

Пошаговые инструкции:

Устанавливаем сервер 1С:Предприятия 8.1
    rpm -ivh 1C_Enterprise-common-8.1.11-67.i386.rpm
    1C_Enterprise-common-nls-8.1.11-67.i386.rpm
    1C_Enterprise-server-8.1.11-67.i386.rpm
    1C_Enterprise-server-nls-8.1.11-67.i386.rpm

Устанавливаем PostgresSQL 8.2
    rpm -ivh postgresql-8.2.4-6.1C.i386.rpm
    postgresql-contrib-8.2.4-6.1C.i386.rpm
    postgresql-server-8.2.4-6.1C.i386.rpm
    [...]]]></description>
			<content:encoded><![CDATA[<p>Для установки сервера 1С:Предприятия 8.1 (без Web Services) и PostgresSQL 8.2 понадобятся следующие пакеты:</p>
<ul>
<li>1C_Enterprise-server</li>
<li>1C_Enterprise-server-nls</li>
<li>1C_Enterprise-common</li>
<li>1C_Enterprise-common-nls</li>
<li>postgresql</li>
<li>postgresql-server</li>
<li>postgresql-contrib</li>
<li>postgresql-libs</li>
</ul>
<p>Пошаговые инструкции:</p>
<ol>
<li>Устанавливаем сервер 1С:Предприятия 8.1
<p>    <tt>rpm -ivh 1C_Enterprise-common-8.1.11-67.i386.rpm<br />
    1C_Enterprise-common-nls-8.1.11-67.i386.rpm<br />
    1C_Enterprise-server-8.1.11-67.i386.rpm<br />
    1C_Enterprise-server-nls-8.1.11-67.i386.rpm</tt></li>
<p></p>
<li>Устанавливаем PostgresSQL 8.2
<p>    <tt>rpm -ivh postgresql-8.2.4-6.1C.i386.rpm<br />
    postgresql-contrib-8.2.4-6.1C.i386.rpm<br />
    postgresql-server-8.2.4-6.1C.i386.rpm<br />
    postgresql-libs-8.2.4-6.1C.i386.rpm</tt></li>
<p></p>
<li>Инициализируем кластер PostgresSQL с локалью <i>ru_RU.utf8</i> для русского языка или <i>uk_UA.utf8</i> для украинского:
<p>    <tt>su - postgres -c 'initdb --locale=uk_UA.utf8 -D /var/lib/pgsql/data/'</tt></li>
<p></p>
<li>Отключаем пароли на подключение к PostgresSQL, заменяя в файле <i>/var/lib/pgsql/data/pg_hba.conf</i> строку
<pre>host   all     all    0.0.0.0/0    md5</pre>
<p>    на</p>
<pre>host   all     all    0.0.0.0/0    trust</pre>
<p></p>
<li>Запускаем PostgresSQL
<p>    <tt>/sbin/service postgresql start</tt></li>
<p></p>
<li>Подключаемся к PostgresSQL
<p>    <tt>psql -h localhost postgres postgres</tt></p>
<p>    меняем пароль пользователя <i>postgres</i></p>
<p>    <tt>ALTER USER postgres PASSWORD 'new_password';</tt></p>
<p>    и выходим</p>
<p>    <tt>\q</tt></li>
<p></p>
<li>Включаем пароли на подключение к PostgresSQL, заменяя в файле <i>/var/lib/pgsql/data/pg_hba.conf</i> строку
<pre>host   all     all    0.0.0.0/0    trust</pre>
<p>    на</p>
<pre>host   all     all    0.0.0.0/0    md5</pre>
<p></p>
<li>Перезапускаем PostgresSQL
<p>    <tt>/sbin/service postgresql restart</tt></li>
</ol>
<p></p>
<p>Если у Вас установлен Apache и возникают проблемы с библиотеками при замене родного системного PostgresSQL 8.1 на 8.2 &#8211; читаем <a href="http://www.westnet.com/~gsmith/content/postgresql/pgrpm.htm">Installing the PostgreSQL 8.2 RPMs on RHEL 5/CentOS 5</a></p>
<p>Вкратце, при апгрейде <i>postgresql-libs</i> с версии 8.1 до версии 8.2, библиотека <i>libpq.so.4</i> заменяется на <i>libpq.so.5</i>.  Однако <i>libpq.so.4</i> необходима для системного httpd Apache и после апгрейда <i>postgresql-libs</i> с версии 8.1 до версии 8.2, httpd Apache станет не работоспособным.</p>
<p>Для решения проблемы достаточно установить <i>compat-postgresql-libs</i> (<i>compat-postgresql-libs-4-1PGDG.rhel5.i686.rpm</i>) с опцией замены файлов</p>
<p>  <tt>rpm -iv --replacefiles compat-postgresql-libs-4-1PGDG.rhel5.i686.rpm</tt></p>
<p>  <i>compat-postgresql-libs</i> также содержит <i>libpq.so.4</i> и после его установки апгрейд <i>postgresql-libs</i> с версии 8.1 до версии 8.2 становиться возможным, так как с удалением <i>postgresql-libs</i> версии 8.1, <i>libpq.so.4</i> поставляется пакетом <i>compat-postgresql-libs</i>.</p>
<p>Скачать <i>compat-postgresql-libs</i> можно здесь: <a href="http://www.postgresql.org/ftp/binary/v8.2.7/linux/rpms/redhat/rhel-5-i386/">http://www.postgresql.org/ftp/binary/v8.2.7/linux/rpms/redhat/rhel-5-i386/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2008/03/%d1%83%d1%81%d1%82%d0%b0%d0%bd%d0%be%d0%b2%d0%ba%d0%b0-1%d1%81%d0%bf%d1%80%d0%b5%d0%b4%d0%bf%d1%80%d0%b8%d1%8f%d1%82%d0%b8%d1%8f-8-1-%d0%bd%d0%b0-red-hat-enterprise-linux-5-rhel-5-centos-5/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>SELinux and Samba</title>
		<link>http://sergiy.kyrylkov.name/blog/2007/07/selinux-and-samba/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2007/07/selinux-and-samba/#comments</comments>
		<pubDate>Tue, 03 Jul 2007 13:39:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=59</guid>
		<description><![CDATA[Those who installed Samba on RHEL or any other SELinux enabled distribution may have faced the problem when they actually cannot access any Samba shares from their Windows machines.  Samba logs in /var/samba/log may show lots of such messages:
[2007/07/03 16:37:44, 0] smbd/service.c:make_connection_snum(911)  '/opt/blah' does not exist or permission denied when connecting to [blah] [...]]]></description>
			<content:encoded><![CDATA[<p>Those who installed Samba on RHEL or any other SELinux enabled distribution may have faced the problem when they actually cannot access any Samba shares from their Windows machines.  Samba logs in <em>/var/samba/log</em> may show lots of such messages:
<pre>[2007/07/03 16:37:44, 0] smbd/service.c:make_connection_snum(911)  '/opt/blah' does not exist or permission denied when connecting to [blah]   Error was Permission denied</pre>
<p>This is probably an SELinux problem and to fix it you&#8217;ll need to execute:
<pre>chcon -t system_u:object_r:samba_share_t /opt</pre>
<p>or, in  order to survive relabel:
<ul>
<li>add these lines to <em>/etc/selinux/targeted/contexts/files/file_contexts.local</em> file (if you are using <em>targeted</em> policy):
<pre>/opt(/.*)?  system_u:object_r:samba_share_t:s0</pre>
</li>
<li><em>probably</em>, reboot</li>
<li>execute:
<pre>restorecon -R /opt/</pre>
</li>
</ul>
<p>This will set appropriate SELinux context on all files in <em>/opt</em> directory and SELinux won&#8217;t prevent Samba access anymore.</p>
<p>To allow Samba to share your home directories with SELinux execute the following:
<pre>setsebool -P samba_enable_home_dirs 1</pre></p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2007/07/selinux-and-samba/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fedora Legacy Shutdown</title>
		<link>http://sergiy.kyrylkov.name/blog/2007/03/fedora-legacy-shutdown/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2007/03/fedora-legacy-shutdown/#comments</comments>
		<pubDate>Thu, 01 Mar 2007 20:42:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=57</guid>
		<description><![CDATA[Fedora Legacy project announced shutdown on February 9th, 2007.  It is definitely bad news for Fedora unless Fedora people understand what they do and do this on purpose.  They just dropped Server spin from Fedora 7 release and now there is no way to get security updates beyond 18 month period for older [...]]]></description>
			<content:encoded><![CDATA[<p>Fedora Legacy project <a href="http://www.fedoralegacy.org/">announced shutdown</a> on February 9th, 2007.  It is definitely bad news for Fedora unless Fedora people understand what they do and do this on purpose.  They just dropped Server spin from Fedora 7 release and now there is no way to get security updates beyond 18 month period for older Fedora releases.</p>
<p>We have several servers running Fedora and this means that now we must be thinking about either upgrading them to the most recent release of Fedora every 18 months or consider changing the Linux distribution we rely on.  An upgrade every 18 months may not sound that bad for a workstation, but for a fully configured server it is definitely a hassle, taking into account many issues that can arise.</p>
<p>I do hope Fedora guys reconsider their support policy for maintenance distributions.  However it is quite possible that Red Hat endorsed Fedora Legacy shutdown to drive more people toward Red Hat Enterprise Linux, in which case the chances for reconsideration are quite low.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2007/03/fedora-legacy-shutdown/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fedora 7 Test 2 &#8211; no Server spin</title>
		<link>http://sergiy.kyrylkov.name/blog/2007/03/fedora-7-test-2-no-server-spin/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2007/03/fedora-7-test-2-no-server-spin/#comments</comments>
		<pubDate>Thu, 01 Mar 2007 19:28:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=56</guid>
		<description><![CDATA[Fedora 7 Test 2 has been released today, however it doesn&#8217;t provide a separate Server spin.  It turns out this feature has been cancelled, which is too bad, however understandable, taking into account how much Fedora people intend accomplish with Fedora 7.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.redhat.com/archives/fedora-announce-list/2007-March/msg00000.html">Fedora 7 Test 2</a> has been released today, however it doesn&#8217;t provide a separate Server spin.  It turns out this feature <a href="http://fedoraproject.org/wiki/Releases/FeatureFedoraServer">has been cancelled</a>, which is too bad, however understandable, taking into account how much Fedora people intend accomplish with Fedora 7.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2007/03/fedora-7-test-2-no-server-spin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GPS navigators web site launched</title>
		<link>http://sergiy.kyrylkov.name/blog/2006/09/gps-navigators-web-site-launched/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2006/09/gps-navigators-web-site-launched/#comments</comments>
		<pubDate>Sat, 02 Sep 2006 16:25:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[e-commerce]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=55</guid>
		<description><![CDATA[Finally, after spending many days preparing, organizing and verifying information about Garmin GPS devices, we&#8217;ve launched GPS Navigator web site in Ukraine.
]]></description>
			<content:encoded><![CDATA[<p>Finally, after spending many days preparing, organizing and verifying information about Garmin GPS devices, we&#8217;ve launched <a href="http://www.gps-navigator.com.ua/">GPS Navigator</a> web site in Ukraine.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2006/09/gps-navigators-web-site-launched/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google July 27</title>
		<link>http://sergiy.kyrylkov.name/blog/2006/07/google-july-27/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2006/07/google-july-27/#comments</comments>
		<pubDate>Sun, 30 Jul 2006 03:02:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[e-commerce]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=54</guid>
		<description><![CDATA[On July 27, exactly one month after June 27, one of our larger web sites Multiplex Systems Store regained its position for all competitive sets of keywords. What exactly caused the problem still remains a question, but this is something that is referred to as &#8220;data refresh&#8221; by Matt Cutts.
As a preventive measure for future, [...]]]></description>
			<content:encoded><![CDATA[<p>On July 27, exactly one month after June 27, one of our larger web sites <a href="http://store.mpxsys.com.ua/">Multiplex Systems Store</a> regained its position for all competitive sets of keywords. What exactly caused the problem still remains a question, but this is something that is referred to as &#8220;data refresh&#8221; by <a href="http://www.mattcutts.com/blog/">Matt Cutts</a>.</p>
<p>As a preventive measure for future, we are launching a static web site <a href="http://www.gsm-modem.com.ua/">GSM Modem</a> devoted exclusively to GSM modems, including GSM/GPRS/EDGE modules, terminals, PC cards and other equipment. The content is not there yet (just the domain) but we plan to add it soon. Initially it will be in Russian, but we may add Ukrainian and English content.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2006/07/google-july-27/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google June 27</title>
		<link>http://sergiy.kyrylkov.name/blog/2006/07/google-june-27/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2006/07/google-june-27/#comments</comments>
		<pubDate>Sun, 02 Jul 2006 22:14:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[e-commerce]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=53</guid>
		<description><![CDATA[It looks like something quite bad happened to Google search on June 27. There are long threads about this event on Webmaster World.com: June 27 &#8211; changes and June 27 &#8211; changes Part 2 but everybody can only guess why certain sites have been hit and certain have not. 
Unfortunately Multiplex Systems Store is one [...]]]></description>
			<content:encoded><![CDATA[<p>It looks like something quite bad happened to Google search on June 27. There are long threads about this event on Webmaster World.com: <a href="http://www.webmasterworld.com/forum30/34979.htm">June 27 &#8211; changes</a> and <a href="http://www.webmasterworld.com/forum30/35023.htm">June 27 &#8211; changes Part 2</a> but everybody can only guess why certain sites have been hit and certain have not. </p>
<p>Unfortunately <a href="http://store.mpxsys.com.ua/">Multiplex Systems Store</a> is one of the sites that suffered badly from this event. It produced top 5 search results for a wide range of keywords and products for several month now. However, after June 27, almost all results went to nowhere, almost zeroing traffic from Google. The resolution is yet to be found.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2006/07/google-june-27/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JBuilder is not dead</title>
		<link>http://sergiy.kyrylkov.name/blog/2006/06/jbuilder-is-not-dead/</link>
		<comments>http://sergiy.kyrylkov.name/blog/2006/06/jbuilder-is-not-dead/#comments</comments>
		<pubDate>Fri, 16 Jun 2006 10:29:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[java]]></category>

		<guid isPermaLink="false">http://sergiy.kyrylkov.name/blog/?p=52</guid>
		<description><![CDATA[Borland posted JBuilder roadmap outlining future development of JBuilder including previously announced JBuilder 2007 codenamed &#8220;Peloton&#8221;. It is expected to be released in Q4 of 2006 and will be based on Eclipse for its core IDE features. Features will include: 

Support for new Java standards including Java SE 6 and the latest JSRs
Visual GUI development [...]]]></description>
			<content:encoded><![CDATA[<p>Borland posted JBuilder roadmap outlining future development of JBuilder including previously announced JBuilder 2007 codenamed &#8220;Peloton&#8221;. It is expected to be released in Q4 of 2006 and will be based on Eclipse for its core IDE features. Features will include: </p>
<ul>
<li>Support for new Java standards including Java SE 6 and the latest JSRs</li>
<li>Visual GUI development for Swing and SWT</li>
<li>Certified Eclipse bundle, updated regularly with the latest plug-ins</li>
<li>Visual Web Services development using a familiar GUI, full round-trip development of web services and web service clients</li>
<li>Virtual Peer-to-Peer Collaboration allowing distributed teams to work together with live co-editing and co-debugging (first introduced for JBuilder 2006 as a separate product)</li>
</ul>
<p>For more information check the full <a href="http://bdn.borland.com/article/33519">product roadmap</a> at Borland&#8217;s web site.</p>
]]></content:encoded>
			<wfw:commentRss>http://sergiy.kyrylkov.name/blog/2006/06/jbuilder-is-not-dead/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

