Open source forks are not always a good thing. Sometimes an already small community gets split so far that the projects die of neglect. Of course Echo2 has been so moribund for the last few months that I think this particular fork is a good thing. The folks from NextApp seem to have gotten a kick in the pants as a result of this development. I’ve never seen them this engaged in the forum.
Let the competition begin.
[source]
Daniel from Karora has written an article showing what you should do to migrate Echo2Impress to Cooee, automating the whole thing with Maven.
It’s a nice article, expecially if you, as me, don’t know Maven. Too bad E2I is not showing its beautifulness as it seems the styles are missing. Here is how it should look. Eventually I will rewrite that article.
Anyway, a huge “thank you” to the Karora guys for using E2I :)
Today news is the announcement of Karora
Karora is an open source group developing frameworks for Web 2.0 application delivery.
Karora is the natural consequence of the way Echo2 has been managed by Nextapp until today. One of the last question have been asked in a talk was “Is the development open?” and my answer was “No, it is not”.
The community reacted, as it should have done months ago, and Karora is the very first “practical” reaction.
The Karora group has released three different projects:
Karora aims is to publicly develop Echo2 and related projects AND to give the community what it has kept on asking for a long time
I’ve asked for a bug tracker for a loooong time: lots of promises, but no bug tracker. I’ve even set up one on my own, asking Tod to check it out if it would have fit for Echo2, but received no answers.
But the most important part of Karora (Cooee in particular) is the availability of a sandbox, so finally every component sent into that messy Echo2 forum can now find home and eventually incubate and mature with the contributions of the community.
Once more, the bazaar seems to overtake the cathedral.
Un mini post per ringraziare tutte le persone presenti ieri al meeting di Maggio del JUG Torino.
Come al solito ho cominciato zoppicando (e questa volta più del solito! Stavo quasi per dire “ok, aspettate, ricomincio”. Ho evitato per un pelo…) ma il resto dello talk è andato credo abbastanza bene. Mi piace quando la persone che hai davanti intervengono, obiettano, commentano, perchè vuol dire che, gli piaccia o no quello che gli racconti, ti stanno seguendo.
Grazie ancora a tutti!
La nuova vita a Torino comincia il 24 maggio, ore 18.30, quando terrò il secondo talk della mia vita.
Parlerò di Echo2, il mio amato toolkit ajax. Diversamente dal talk di dicembre a Milano, aggiungerò qualche riferimento a Echo-Core, la libreria di base che io e Concept abbiamo sviluppato e usiamo quotidianamente per lo sviluppo delle nostre applicazioni.
Se siete da queste parti, fate un salto, potreste divertirvi (almeno ci spero ;))
La locandina e di seguito l’agenda della serata
presso CSP spa Corso Svizzera 185, Torino
Fabbricato 1, scala H, 2° piano
Agenda:
18:30: check-in
18:45: JugTO Quickie: Web & HTTP the Ajax way
come funzionano le applicazioni Ajax
Carlo Bottiglieri
19:00 JugTO Seminar: Echo2: Rich Internet Applications the Swing way
come sviluppare Rich Client Application senza una riga di html o javascript, con il framework Echo
Federico Fissore
A quick one: AgentSmith has graduated from the javatools incubator and is now part of the javatools project.
Current release (0.8) will become 1.0 during the following weeks.
Eclipse will finally store user installed plugins into user’s $HOME folder IF the folder into which Eclipse is installed is not writable.
This problem affected every Linux distribution and, thanks to the guys from the Fedora project (Ben Konrath in particular), a patch was provided since Eclipse 3.1.
The bug was filed on April, 2005 (!!!). Hopefully linux-distro project will take care of such problems in the future.
[ More details ]
Ok, I must admit it, I can’t hide: I was wrong. I’ve just discovered that Agent Smith features are already available. To everyone.
A brief explanation.
I’m an Eclipse user. I have been (silly) used in reloading my webapp every time I changed a Struts action or a piece of an Echo2 application.
I wanted to find a way to avoid reloading my webapp.
I saw Groovy. But it didn’t work with Echo2, because of the API.
I saw the Instrumentation interface and I thought: “Hey I will do that: Grovvy won’t be necessary”.
So Agent Smith saw the light. And it was just reaching version 1.0 when I was told that, actually, Eclipse has already a feature like Smith. And it’s really simple to activate it.
So, Smith is dead. Long live to Smith. Thanks to Adrians at the Echo2 forums for finally pointing that out.
I’m very sad, you know. I’ve wasted some days. The most disappointing aspect is that it took two weeks of marketing for someone to come out and say “Hey, you are wrong”.
But!
I know I’m not the only one with this lack of knowledge, so let me flip the bad news in a good news and let me explain how to avoid reloading apps with Eclipse.
Right click on your, say, web project and “Debug as”, “Debug on Server”. Now code.
I can hear you: “Whaaaaaatt? THAT simple!?!?“.
Yes, that simple.
Agent Smith has just been approved by the java-tools community at java.net. It’s currently in the “incubator” but I’m sure it will graduate soon.
Following my previous post, in the agent smith post series.
Smith comes in two versions: one is java5 only, the other is java6+, meaning you must have at least java 6 (or mustang) to run it.
The two versions differ in one feature only: the ability to load the agent after the jvm start up, instead of the usual way that’s by specifying it with a command line parameter. Anyway, such feature is experimental (even if I use it daily).
Let’s see what to do to begin using Smith.
ant dist
javac Main.java
java -javaagent:<PATH_TO_SMITH_JAR>=<PATH_TO_CURRENT_FOLDER> Main
Every path must be absolute.
You should see two messages repeating every one second
Bar: I’m doing something
Bar$Foo: What else???
Easier done than said :)
Next time we’ll set up Tomcat to use Smith into a webapp.