added 2008 Fri May 16 17:02:59 by aglover
The hip team over at easyb.org has been diligently working towards a 1.0 release and recently added the notion of fixtures for stories; that is, the DSL has been updated to include: before_each and after_each. These constructs operate much the same as JUnit’s original fixtures in that code in the before_each closure is executed before each scenario and after_each, after.
The hip team over at easyb.org has been diligently working towards a 1.0 release and recently added the notion of fixtures for stories; that is, the DSL has been updated to include: before_each and after_each. These constructs operate much the same as JUnit’s original fixtures in that code in the before_each closure is executed before each scenario and after_each, after.
added 2008 Fri May 16 16:19:00 by Jacek
A major hack to the YAML file format to further reduce the number of lines and indentation levels in it, thus making it way more compact than XML or JSON. Java SwingBuilder is an attempt to bring dynamic language-type productivity to Java Swing UI development by defining the layout/event wiring/binding in a separate YAML file and leaving the Java class to focus on pure business-side code. Inspired by Groovy SwingBuilder (the concept in general), Ruby on Rails (YAML is the new JSON/XML, but leaner) and GTK+ libGlade (for the idea of keeping layout and event wiring in a separate file). End goal of the project: to define max content with the least amount of code.
A major hack to the YAML file format to further reduce the number of lines and indentation levels in it, thus making it way more compact than XML or JSON. Java SwingBuilder is an attempt to bring dynamic language-type productivity to Java Swing UI development by defining the layout/event wiring/binding in a separate YAML file and leaving the Java class to focus on pure business-side code. Inspired by Groovy SwingBuilder (the concept in general), Ruby on Rails (YAML is the new JSON/XML, but leaner) and GTK+ libGlade (for the idea of keeping layout and event wiring in a separate file). End goal of the project: to define max content with the least amount of code.
added 2008 Fri May 16 9:53:29 by bloid
I been wanting to write about GlazedLists + Groovy since 2GX, as James and I made a demo of a Grails/Swing powered RSS/Atom aggregator that, among other things, took advantage of GlazedLists to create JTable, scratch that, a sorted, observable JTable with minimal code.
I been wanting to write about GlazedLists + Groovy since 2GX, as James and I made a demo of a Grails/Swing powered RSS/Atom aggregator that, among other things, took advantage of GlazedLists to create JTable, scratch that, a sorted, observable JTable with minimal code.
added 2008 Thu May 15 18:04:13 by cwalcott
In the this post I discuss my thoughts on using Grails for the first time, and compare it to my experience as a Rails developer.
In the this post I discuss my thoughts on using Grails for the first time, and compare it to my experience as a Rails developer.
added 2008 Thu May 15 17:35:26 by aglover
Gant is a Groovy-based build system that uses Ant’s extensive collection of flower power tasks without all of the nasty XML– this enables you to leverage greater flexibly when it comes to hiply assembling software. Capitalizing on this flexibility within a CI process, however, can be somewhat challenging, unless, that is, you happen to be using Hudson, baby!
Gant is a Groovy-based build system that uses Ant’s extensive collection of flower power tasks without all of the nasty XML– this enables you to leverage greater flexibly when it comes to hiply assembling software. Capitalizing on this flexibility within a CI process, however, can be somewhat challenging, unless, that is, you happen to be using Hudson, baby!
added 2008 Thu May 15 16:52:56 by bloid
Grails just had its time — taglibs. Now, because of the pain of JSP tag libraries, I’ve avoided anything that sounded anything like UI taglibs. But, I was starting to repeat myself in views, and in such a way that partials seemed a bit hokey. This is where custom tags come in.
Grails just had its time — taglibs. Now, because of the pain of JSP tag libraries, I’ve avoided anything that sounded anything like UI taglibs. But, I was starting to repeat myself in views, and in such a way that partials seemed a bit hokey. This is where custom tags come in.
added 2008 Thu May 15 15:15:51 by bloid
A few weeks ago I was writing a method in Groovy that needed to return three different results, two strings and one array. As I was writing it, I said to myself, "this code is ugly, I wish I could return multiple values from methods in Groovy."
A few weeks ago I was writing a method in Groovy that needed to return three different results, two strings and one array. As I was writing it, I said to myself, "this code is ugly, I wish I could return multiple values from methods in Groovy."
added 2008 Thu May 15 9:00:34 by jansokol
Last few days I am working on grailstutorials and this is the first time that I am doing some bigger project than experimenting with Grails. While so far I had that feeling now it is even more clear to me while development with Grails is so easy and fast. I will try to share my understanding how high efficiency is achieved when working with grails. Let us see what more or less common web application requires to be implemented: (This list is not full list and I can add number of points into this list)
Last few days I am working on grailstutorials and this is the first time that I am doing some bigger project than experimenting with Grails. While so far I had that feeling now it is even more clear to me while development with Grails is so easy and fast. I will try to share my understanding how high efficiency is achieved when working with grails. Let us see what more or less common web application requires to be implemented: (This list is not full list and I can add number of points into this list)
added 2008 Thu May 15 8:29:29 by aalmiray
The demo application from the Groovy SwingBuilder Tech Session at JavaOne 2008 is now runnable via WebStart. (note to self, link to SDN site when the presentaiton goes live). The source code may also be browsed via FishEye. There are a couple of points I wish to call out that were touched on in the tech session
The demo application from the Groovy SwingBuilder Tech Session at JavaOne 2008 is now runnable via WebStart. (note to self, link to SDN site when the presentaiton goes live). The source code may also be browsed via FishEye. There are a couple of points I wish to call out that were touched on in the tech session
Sponsors
added 2008 Wed May 14 5:54:40 by bloid
... or better yet, help it out. Let's recap a bit on the state of Groovy support in the 3 mayor IDEs.
... or better yet, help it out. Let's recap a bit on the state of Groovy support in the 3 mayor IDEs.
added 2008 Tue May 13 15:40:54 by aalmiray
I was writing a very simple Grails application and ran into a problem when I accidentally used a SQL keyword as a property name. This post documents what happened, and how I (pretty easily) fixed it.
I was writing a very simple Grails application and ran into a problem when I accidentally used a SQL keyword as a property name. This post documents what happened, and how I (pretty easily) fixed it.
added 2008 Tue May 13 14:19:35 by bloid
Before we begin, a quick Groovy primer. We start with the fact that Groovy is Java and Java is Groovy. If you have written Java code, you have written Groovy code. Our tasks within this article will be to do 3 things: format a date, read and write to a properties file, and parse XML. Let’s look at the Groovy code for each of these in detail.
Before we begin, a quick Groovy primer. We start with the fact that Groovy is Java and Java is Groovy. If you have written Java code, you have written Groovy code. Our tasks within this article will be to do 3 things: format a date, read and write to a properties file, and parse XML. Let’s look at the Groovy code for each of these in detail.
added 2008 Tue May 13 13:10:26 by palsforpals
One interesting session at JavaOne 2008 was hosted by Raghavan aka Rags from Sun Microsystems. The session was called the Script Bowl and was a war between the scripting gurus from Groovy, JRuby, Jython and Scala. All the four languages are dynamic scripting languages that run on the JVM. LaForge represented Groovy, Nutter represented JRuby, Wierzbicki represented Jython and Jorge Ortiz represented Scala...
One interesting session at JavaOne 2008 was hosted by Raghavan aka Rags from Sun Microsystems. The session was called the Script Bowl and was a war between the scripting gurus from Groovy, JRuby, Jython and Scala. All the four languages are dynamic scripting languages that run on the JVM. LaForge represented Groovy, Nutter represented JRuby, Wierzbicki represented Jython and Jorge Ortiz represented Scala...
added 2008 Tue May 13 10:36:50 by Jacek
Completed work on bean binding, SwingWorker integration for long running methods. Java SwingBuilder is an attempt to bring dynamic language-type productivity to Java Swing UI development by defining the layout/event wiring/binding in a separate YAML file and leaving the Java class to focus on pure business-side code. Inspired by Groovy SwingBuilder (the concept in general), Ruby on Rails (YAML is the new JSON/XML, but leaner) and GTK+ libGlade (for the idea of keeping layout and event wiring in a separate file). End goal of the project: to blow JavaFX away and ensure pure Java is king. *grin*
Completed work on bean binding, SwingWorker integration for long running methods. Java SwingBuilder is an attempt to bring dynamic language-type productivity to Java Swing UI development by defining the layout/event wiring/binding in a separate YAML file and leaving the Java class to focus on pure business-side code. Inspired by Groovy SwingBuilder (the concept in general), Ruby on Rails (YAML is the new JSON/XML, but leaner) and GTK+ libGlade (for the idea of keeping layout and event wiring in a separate file). End goal of the project: to blow JavaFX away and ensure pure Java is king. *grin*
added 2008 Mon May 12 11:56:21 by bloid
This interview was done at the press room of JavaOne 2008, so expect some background noise.. but the overall quality should be quite well. Guillaume talks about the recent 1.6 Beta 1 release of Groovy, the roadmap, G2One, DSLs and more.
This interview was done at the press room of JavaOne 2008, so expect some background noise.. but the overall quality should be quite well. Guillaume talks about the recent 1.6 Beta 1 release of Groovy, the roadmap, G2One, DSLs and more.
added 2008 Mon May 12 11:53:54 by danielstoner
Let’s imagine a very simple scenario. You are writing an application which would benefit from some user specific customization after deployment. Maybe some of your customers have specific algorithms to be executed in the context of your application. Maybe your application doesn’t solve just one problem but it is designed to solve a class of problems but the number of variants is too high for you to capture at development time.
Let’s imagine a very simple scenario. You are writing an application which would benefit from some user specific customization after deployment. Maybe some of your customers have specific algorithms to be executed in the context of your application. Maybe your application doesn’t solve just one problem but it is designed to solve a class of problems but the number of variants is too high for you to capture at development time.
added 2008 Mon May 12 7:51:26 by bloid
This is the long overdue follow up to my Writing a Simple Issue Tracker in Grails post. In this post I'll be detailing how to add security with the JSecurity plugin.
This is the long overdue follow up to my Writing a Simple Issue Tracker in Grails post. In this post I'll be detailing how to add security with the JSecurity plugin.
added 2008 Sun May 11 20:12:15 by alext
invokedynamic from prospective of Groovy Core Developer
invokedynamic from prospective of Groovy Core Developer
added 2008 Sun May 11 18:32:39 by jeffrichley
It is simply amazing how many people and how much energy is at JavaOne. All of the movers and shakers of the industry are here to give out sage words of wisdom. Listen to this lighthearted overview of day two and three of JavaOne.
It is simply amazing how many people and how much energy is at JavaOne. All of the movers and shakers of the industry are here to give out sage words of wisdom. Listen to this lighthearted overview of day two and three of JavaOne.
added 2008 Sat May 10 23:44:25 by p3t0r
JavaOne 2008 is over. I’m still processing everything I’ve seen, but so far I didn’t see to much I didn’t know about before; certainly nothing shocking. Here are some of my observations related to Java7 and alternative languages for the JVM
JavaOne 2008 is over. I’m still processing everything I’ve seen, but so far I didn’t see to much I didn’t know about before; certainly nothing shocking. Here are some of my observations related to Java7 and alternative languages for the JVM
added 2008 Sat May 10 4:03:15 by Jacek
Latest updates on bean binding, SwingWorker integration for long running methods and bean validations. Java SwingBuilder is an attempt to bring dynamic language-type productivity to Java Swing UI development by defining the layout/event wiring/binding in a separate YAML file and leaving the Java class to focus on pure business-side code. Inspired by Groovy SwingBuilder, Ruby on Rails (YAML) and GTK+ libGlade.
Latest updates on bean binding, SwingWorker integration for long running methods and bean validations. Java SwingBuilder is an attempt to bring dynamic language-type productivity to Java Swing UI development by defining the layout/event wiring/binding in a separate YAML file and leaving the Java class to focus on pure business-side code. Inspired by Groovy SwingBuilder, Ruby on Rails (YAML) and GTK+ libGlade.
added 2008 Fri May 9 21:27:11 by tednaleid
If you’ve ever wondered what methods a groovy class has available for you to call, all you need to do is ask the metaClass...
If you’ve ever wondered what methods a groovy class has available for you to call, all you need to do is ask the metaClass...
added 2008 Fri May 9 12:08:46 by cwensel
A tool for those groups that need to expose Hadoop to the 'casual' user who needs to get and manipulate valuable data on a Hadoop cluster, but doesn't have the time to learn Java, the Hadoop API, or to think in MapReduce to solve problems that are a notch or more above trivial.
A tool for those groups that need to expose Hadoop to the 'casual' user who needs to get and manipulate valuable data on a Hadoop cluster, but doesn't have the time to learn Java, the Hadoop API, or to think in MapReduce to solve problems that are a notch or more above trivial.
added 2008 Fri May 9 9:37:45 by jeffrichley
Dynamic languages are coming on strong and this year's JavaOne has quite a bit to talk about. Here is a reflection on one of the Groovy talks.
Dynamic languages are coming on strong and this year's JavaOne has quite a bit to talk about. Here is a reflection on one of the Groovy talks.
added 2008 Wed May 7 17:17:55 by HamletDRC
We're trying to decide whether to use Groovy or Java as a service layer on a project. This is my argument for Groovy. Would you use Groovy?
We're trying to decide whether to use Groovy or Java as a service layer on a project. This is my argument for Groovy. Would you use Groovy?
added 2008 Wed May 7 14:30:26 by aalmiray
As you may or may not know, I have been working on Groovy Monkey for some time now. I think it is a useful tool and has a number of benefits over its predecessor Eclipse Monkey. Right now I am hoping that I will have the opportunity to take over Eclipse Monkey and take all of Groovy Monkey's improvements and make them more available to everyone.
As you may or may not know, I have been working on Groovy Monkey for some time now. I think it is a useful tool and has a number of benefits over its predecessor Eclipse Monkey. Right now I am hoping that I will have the opportunity to take over Eclipse Monkey and take all of Groovy Monkey's improvements and make them more available to everyone.
added 2008 Wed May 7 9:36:32 by bloid
Currenttly, I'm in the process of building a Grails application. While I've built several prototypes/quick hacks, this is actually the first 'real' application I'm building. "So", I thought, "if this is a real application, I'm in need of some real tests!". When you're in the normal flow of developing a Grails application, everything goes so fast, you almost forget about writing the tests. So I decided to do it a bit differently, and do it just like in Java: do it TDD!
Currenttly, I'm in the process of building a Grails application. While I've built several prototypes/quick hacks, this is actually the first 'real' application I'm building. "So", I thought, "if this is a real application, I'm in need of some real tests!". When you're in the normal flow of developing a Grails application, everything goes so fast, you almost forget about writing the tests. So I decided to do it a bit differently, and do it just like in Java: do it TDD!
added 2008 Tue May 6 15:36:45 by jsugrue
This gathering was put on by the people who take the excellent NFJS series around the United States throughout the year. I was fortunate enough to attend my first one just a few weeks ago in Seattle and am happy to say that in the course of one weekend, the symposium reminded me of so many reasons why I got into developing software. With that kind of introduction you might think I would have high hopes for the session here tonight and you are right! Fortunately for the
This gathering was put on by the people who take the excellent NFJS series around the United States throughout the year. I was fortunate enough to attend my first one just a few weeks ago in Seattle and am happy to say that in the course of one weekend, the symposium reminded me of so many reasons why I got into developing software. With that kind of introduction you might think I would have high hopes for the session here tonight and you are right! Fortunately for the
added 2008 Tue May 6 2:16:49 by bloid
I like to do things the right and clean way. And shutting down a service under Linux is done by calling the start-/stop-script under /etc/init.d with the parameter stop. Even graphical front-ends, may they be YAST or webmin or whatever stick to this rule. The advantage is, the whole know-how of how to shutdown one specific service is hidden in the start-/stop-script. Killing a process directly is real evil, because the process (and dependend processes) don't get the chance to do whatever they have to before shutting down. Otherwise databases get corrupted, stale files claim disk space, memory is hogged by zombie processes and the like.
I like to do things the right and clean way. And shutting down a service under Linux is done by calling the start-/stop-script under /etc/init.d with the parameter stop. Even graphical front-ends, may they be YAST or webmin or whatever stick to this rule. The advantage is, the whole know-how of how to shutdown one specific service is hidden in the start-/stop-script. Killing a process directly is real evil, because the process (and dependend processes) don't get the chance to do whatever they have to before shutting down. Otherwise databases get corrupted, stale files claim disk space, memory is hogged by zombie processes and the like.
added 2008 Mon May 5 21:09:23 by bloid
FEST stands for Fixtures for Easy Software Testing, it targets UI testing (Java Swing for the time being). Easyb makes Behavior Driven Development a snap. Use them together and you have a recipe for success. Let's revisit a previous example of FEST+Groovy, a very basic app that retrieves the definition of a word the user may type
FEST stands for Fixtures for Easy Software Testing, it targets UI testing (Java Swing for the time being). Easyb makes Behavior Driven Development a snap. Use them together and you have a recipe for success. Let's revisit a previous example of FEST+Groovy, a very basic app that retrieves the definition of a word the user may type
12345678910111213 ... 14 »
