<?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>Espeo Software &#187; english</title>
	<atom:link href="http://www.espeo.pl/kategoria/blog/english/feed" rel="self" type="application/rss+xml" />
	<link>http://www.espeo.pl</link>
	<description>Oprogramowanie na zamówienie - aplikacje inter/intranetowe, desktop, mobilne. Wykorzystujemy technologię Java, Java EE, Flex, Grails</description>
	<lastBuildDate>Mon, 30 Jan 2012 14:34:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Open Flash Chart 2 on Grails</title>
		<link>http://www.espeo.pl/2010/09/10/open-flash-chart-2-on-grails</link>
		<comments>http://www.espeo.pl/2010/09/10/open-flash-chart-2-on-grails#comments</comments>
		<pubDate>Fri, 10 Sep 2010 18:40:32 +0000</pubDate>
		<dc:creator>Sylwia Rogowicz</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[technologia]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[charts]]></category>
		<category><![CDATA[grails]]></category>
		<category><![CDATA[groovy]]></category>

		<guid isPermaLink="false">http://blog.espeo.pl/?p=343</guid>
		<description><![CDATA[Demand for a new feature for our accounting office management application  appeared recently. Service is made in Grails, so  I started from searching charts plugins for this framework. I could choose between Google Chart plugin, JFreeChart and Open Flash Chart. The last one really took my attention &#8211; you know, nice flash effects possible. I never used Open Flash Charts before and  decided to spend one afternoon and play with it. It was very easy to install and take into use, just by following the short instruction from http://mybytes.wordpress.com/2009/03/09/grails-open-flash-chart-06-is-out It is suggested there to see demo, so I checked out the plugin from svn and watched the samples.  Library gives us many possible charts to present data . I started to prepare 3 test charts using API in Java for Open Flash Chart 2 , same charts I will probably need in my project in the future: Pie chart, Horizontal Bars and more complex one: Bars and Lines presented at one chart. Pie went smoothly  and looked tasty, the most complex chart also, but I was not able to prepare labels for y axis for horizontal bars. It confused me, I found a package with fix called   OFC2Patches-DZ-Ichor.zip on this site http://www.ofc2dz.com/index.html#Examples Hints ( and patches) there are very useful if you have some problems with library. Of course when one problem was solved, the ready made chart &#8211; the more complex one stopped working properly with a new patch for the library. This is code sample for the complex one – 3d bar and line with dots using OFChart library, as you can notice it is easy to use and readable. Everything is fine as long as you are stopped by some more complex feature or bug. Why not to omit this and take advantage of groovy? An swf file gets data that are going to be presented as json data and we have such a groovy2json converter on the board.  Manipulating Lists and Maps we can prepare even the most complicated json file.  I do not need any fixes or patches then. The same example with Lists and Maps below: In both cases chart looks the same of course]]></description>
		<wfw:commentRss>http://www.espeo.pl/2010/09/10/open-flash-chart-2-on-grails/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Our scrum project retrospective in practice</title>
		<link>http://www.espeo.pl/2010/09/09/our-scrum-project-retrospective-in-practice</link>
		<comments>http://www.espeo.pl/2010/09/09/our-scrum-project-retrospective-in-practice#comments</comments>
		<pubDate>Thu, 09 Sep 2010 12:24:39 +0000</pubDate>
		<dc:creator>Pawel Rogowicz</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[english]]></category>

		<guid isPermaLink="false">http://blog.espeo.pl/?p=332</guid>
		<description><![CDATA[Recently our team finished working on a project so the time has come to make a project retrospective. With a shame I must admit that it was a first time for us, because although we use Scrum for a long time, in previous projects there was never time to do it. I decided that to do it correctly and to get best results we should follow some good and tried practices &#8211;  for some time in our library there was a book &#8220;Agile Retrospectives: Making good teams great&#8221; so that was excellent opportunity to use it. After getting through the book I chose a few activites for different phases of retrospective and it was: Satisfaction Histogram &#8211; for measuring level of satiscfaction about the team, project process and product created Timeline and Color Code Dots &#8211; to gather memories of best and worst moments of projects Patterns and Shift &#8211; to observe some specific patterns in a timeline Five Whys &#8211; getting to reasons of some issues by asking &#8220;Why&#8221; question Brainstorming &#8211; to find solution for problems. So how did it work out? In general the team liked it, it was something new and quite funny, especially Timeline where some very specific moments were recalled. A Satisfaction Histogram proved that guys are really happy about the team and way of working together, but less happy about product they created. They did not like Five Whys activity so much &#8211; somehow it was odd to ask Why questions, to get into essence of problem beucase in most cases  the answer was &#8220;Because there was not enough time&#8221; &#8211; but maybe we didn&#8217;t do it correctly?. We really got some very nice reflections ad things to improve for the future, most important were: educating Product Owner on how to work effectively with a team putting more attention to Sprint 0, by making a list of common things to do organizing more workshops obout design and architecture. Will we use such activities in the future? Definitely, but also need  to work better on timeboxing it because 8 hours was even not enough. Also I really hope that conclusions we made won&#8217;t be fogotten and would be valuable for our future projects and will improve Scrum process. And a book about retrospectives is highly recommended.]]></description>
		<wfw:commentRss>http://www.espeo.pl/2010/09/09/our-scrum-project-retrospective-in-practice/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Groovy/Grails update</title>
		<link>http://www.espeo.pl/2010/08/23/groovy_grails_update</link>
		<comments>http://www.espeo.pl/2010/08/23/groovy_grails_update#comments</comments>
		<pubDate>Mon, 23 Aug 2010 11:39:37 +0000</pubDate>
		<dc:creator>Krzysztof Konwisarz</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[news]]></category>
		<category><![CDATA[technologia]]></category>
		<category><![CDATA[grails]]></category>
		<category><![CDATA[groovy]]></category>

		<guid isPermaLink="false">http://blog.espeo.pl/?p=301</guid>
		<description><![CDATA[Groovy and Grails releases in the last months appear so often that it is really easy to miss them. Starting with Groovy: it&#8217;s current version is 1.7.4, and the maintenance updates from this branch bring little more than bugfixes, so the below list contains mainly the changes introduced in 1.7.0: anonymous inner classes – for Java compatibility nested static classes – functionality exists, but it is best to use static nested classes if any added annotations on imports, packages and variable declarations – this allows for instance to declare dependencies with Grape within your code more readable asserts output with Power Asserts AST Viewer and AST Builder to facilitate the use of AST transformations Groovy Truth expanded – every class now can customize the way it is evaluated to boolean by implementing its asBoolean() method batch updates using sql.witchBatch() and sql.withTransaction() numerous improvements in testing, collection methods, GroovyScriptEngine, Groovy console and other More on this, especially the exact behavior and limitation of nested classes in Groovy 1.7.0 Release Notes. &#160; Unlike in Goovy, in each of Grails 1.3.x branch releases new features are implemented. Its current version (1.3.4) uses Spring 3.0.3. With 1.3.0 and the following quite a few changes were made: GORM: dirty checking for domain classes with .isDirty() and .isDirty(&#8216;fieldName&#8217;) methods Hibernate derived properties – domain class property value can be now calculated from a formula; here is a nice post on derived properties themselves. named queries can be combined – nested within another named query, chained one by one or made more specific by supplying additional conditions when invoked .find() and .findAll() query results can now be cached GSPs: default layout – if defined, it will be used by all pages that do not explicitly declare to use one &#60;g:join&#62; tag concatenates strings separating them with a specified delimiter &#60;g:unless&#62; tag is a handier version of negated &#60;g:if&#62; filters the order in which filters are executed can be specified testing: upgraded to JUnit 4 TagLib testing allows to test custom tags that use the pageScope property plugins classes, views and templates provided by plugins can be overridden inline plugins don&#8217;t have to be plugin-packaged before use dependency management: you can specify plugin repositories you want to use in BuildConfig.groovy publishing plugins on Maven compatible repositories declaring plugin dependencies with the IvyDSL every-day use: script name typo detection in command line when creating artifacts suffixes like *Controller, *Service are now added only when user hasn&#8217;t supplied one multiple HTTP proxy configuration grails doc –-pdf exports generated documentation to PDF and –-init generates a documentation template Grails release notes for more details: http://www.grails.org/1.3 Release Notes http://www.grails.org/1.3.1 Release Notes http://www.grails.org/1.3.2 Release Notes http://www.grails.org/1.3.4 Release Notes &#160; As for IDEs – having used Netbeans and Spring Tools Suite lately I must say, that the latter is a long awaited improvement in Groovy/Grails free IDE support. There is still a lot to be done, but at the moment syntax highlighting works quite well, code completions gives some hints without making you wait for ages, and even refactoring works sometimes ;). &#160;]]></description>
		<wfw:commentRss>http://www.espeo.pl/2010/08/23/groovy_grails_update/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>We have made our first steps in Germany</title>
		<link>http://www.espeo.pl/2010/07/05/we-have-made-our-first-steps-in-germany</link>
		<comments>http://www.espeo.pl/2010/07/05/we-have-made-our-first-steps-in-germany#comments</comments>
		<pubDate>Mon, 05 Jul 2010 11:16:22 +0000</pubDate>
		<dc:creator>Tomasz Rakowski</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[news]]></category>

		<guid isPermaLink="false">http://blog.espeo.pl/?p=296</guid>
		<description><![CDATA[Our neighbour &#8211; Germany, wasn&#8217;t actually one of our key destinations lately.  Being focused on typically English speaking markets (England, Scotland,  Ireland) we had no time to investigate new ones. But this time we decided to change it and explore new destinations,  especially such promising like Germany (one of the richest markets in Europe as you know). Even when it is hardly possible to find some time for it &#8211; we decided to do it anyway&#8230; An opportunity to make our first steps in Germany emerged about a week ago, when we were invited by the Wielkopolska ICT Cluster to participate in Berlin-Wielkopolska 2010 Forum, a first conference of collaboration between these two regions. As nearly everything what is made for the first time, the conference wasn&#8217;t surprisingly successful. On the other hand I managed to establish some interesting local contacts and people enjoyed the idea in general &#8211; so it could be good start for more future events of this kind. I have never been to Berlin, even though it is closer to Poznan than Warsaw is (it was shocking for me when I discovered it)! No borders now so travelling was smooth and easy. It turned out that schedule is so tight we weren&#8217;t able to see some more of Berlin. At least we had chance to see a bit more of the most modern technology park in Europe (as Germans say) &#8211; one I can tell, they have invested there a lot! It&#8217;s called Adlershof and it&#8217;s astonishing how fast it grows. I discovered that they&#8217;re open for cooperation and they&#8217;re kind of forced by the law to reply to my enquiry so it is good news for me &#8211; I will definitely take advantage of it. I hope we&#8217;ll find some proper business partners in Germany this year &#8211; hopefully the process began.]]></description>
		<wfw:commentRss>http://www.espeo.pl/2010/07/05/we-have-made-our-first-steps-in-germany/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

