In the midst of changing hosting companies and domain providers, one thing that I forgot about was the TeamDocs website. This has now been recreated and updated. Instead of using Drupal, I am using, instead, MediaWiki. This is more of an experiment to see how a Wiki works for software projects.
I have also officially moved the code from Javaforge to Google Code. Google just makes things so easy, like allowing anonymous downloads of the source code. I still haven’t figured out how to do this on Javaforge.
This is just a list of links that I have open in Firefox and don’t want to forget. Hopefully I will find time to read each one over the next little while.
* “Creating an AJAX feed viewer using Yahoo! UI and the new Grid Component”:http://www.jackslocum.com/yui/2006/09/04/creating-an-ajax-feed-viewer-using-yahoo-ui-and-the-new-grid-component/
* “Presentation: AOP – Myths and Realities”:http://www.infoq.com/news/AOP-Ramnivas-Laddad
* “SQLyog Community Edition”:http://www.webyog.com/en/ — Free MySQL administration application
* “10 Steps to Learning Ruby on Rails”:http://www.urbanpuddle.com/articles/2006/09/06/10-steps-i-took-to-learn-ruby-on-rails
* “Setting up Subversion and websvn on Debian “:http://www.howtoforge.com/debian_subversion_websvn
* “Koove Coding Challenge”:http://www.koove.com/programming-contest/
* “EJB 3.0 Enterprise Beans for the JBoss Application Server”:http://www.netbeans.org/kb/55/ejb30-jboss.html
* “JOTM Transactions In Spring And Hibernate”:http://today.java.net/pub/a/today/2006/08/31/jotm-transactions-in-spring-and-hibernate.html
* “RadRails”:http://www.radrails.org/page/download
I think that is it for now. Too many things to learn and play with.
I found this link via “the List”:http://www.evolt.org and thought it was very cool. It solves a lot of problems if you are trying to add “Flash content to your web pages”:http://blog.deconcept.com/swfobject/.
bq. SWFObject is a small Javascript file used for embedding Macromedia Flash content. The script can detect the Flash plug-in in all major web browsers (on Mac and PC) and is designed to make embedding Flash movies as easy as possible. It is also very search engine friendly, degrades gracefully, can be used in valid HTML and XHTML 1.0 documents*, and is forward compatible, so it should work for years to come.
I am building a small client/server app and was trying to figure out how to transfer object state between the client and the server. At first I thought about using serialized objects or maybe Java RMI, but then I found a little library that transfers object state via XML. The library is called “XStream”:http://xstream.codehaus.org/.
With just a few bits of code, I can transfer an entire object from.
XStream xstream = new XStream();
String xml = xstream.toXML(anObject);
Then I just need to transfer the resulting String. Then, once transfered, to convert it back into an object, I just need to call the following:
Foo foo = (Foo)xstream.fromXML(xml);
I am sure that there are more tricks you can do with it, but for transfering object state, XStream makes things incredibly simple. On “theServerSide.com”:http://www.theserverside.com there have been a few threads about converting Objects to XML and XStream always comes up as a recommendation. I definitely second it.
Oracle has a very thorough tutorial on how to work with “Spring 2.0 in JDeveloper”:http://www.oracle.com/technology/products/jdev/howtos/1013/SpringwithJDev/index.html.
bq. In this article we’ll show you how to set up JDeveloper to use the Spring framework, and then highlight some of the functionality in JDeveloper that can make your development experience with Spring more productive.
nutrun has posted an article on “Java Components–what they are and how to build them”:http://nutrun.com/weblog/the-future-of-software-is-back-to-the-basics/. I basically agree with all of the points in the article. At work, one of the things that we stress is to encapsulate our business rules inside of nice little components that expose a very simple public interface. This will hopefully allow us to reuse some of these components down the road (or that is the theory at least).
[A] Component is essentially a bunch of Classes collaborating inside their little cosmos and communicating with the rest of the world through a narrow interface.
In its simplest form, say, a Java component, is some code in a package.
Writing a component is easy, provided we keep one simple rule in mind. The world is oblivious to what happens inside the component. The world is only interested in what the component can provide it with and what the component needs to perform its task. In other words, the world should only care calling the methods of a Component’s public Interface.
I found this post on the Darren Hobbs website and thought it summed up the “problem/myth of adding more people to a project”:http://www.darrenhobbs.com/archives/2006/09/yet_another_ana.html and the reason why this does not reduce the time needed for development.
[I]t came to me today that software projects are like turkeys.
You can’t achieve the same effect when roasting a turkey by doubling the temperatuire and halving the cooking time. Similarly a project cannot have the number of people doubled and the duration halved and get the same result. The rate of knowledge crunching is not increased by adding more people.