I was reading an article the other day talking about Agile and the idea of customer driven direction. Here’s an extract:
“One of the concerns that is sometimes expressed about Agile approaches is that they are ‘too customer-driven’, implying that customers are not always the best people to define the direction of a product or a change. So is ‘the customer always right’, and is it good Agile practice to ‘give the customer what they want’?”
What struct me about this is how people view their world. The assumption above is that both parties are attempting to do the same thing. Hence the discussion about is the customer best placed to make these decisions.
So called because this article puts together all the parts of a web service by hand so that when you use the available tools out there designed to make things easier and quicker you can work out what has gone wrong and how to fix it.
If you intend to build an application designed for more than a single user then you will need to provide a means for users to authenticate themselves. Authentication is the means for a user to provide information that allows your application to identify who you are.
The application will then typically use authorisation to check which functions and information you are allowed to access. To take a look at what is involved in an authentication system lets build a simple system to get you started.
When I first started out in programming I made the same mistake as I see countless people make when starting. I wrote code for me and that worked, and that was good enough for me. As time passed and the code I produced expanded and became more ambitious so my bad habits became more ingrained. I think it is something we all do; we all go through. It is not until we encounter an issue, a reason to change, that we appreciate the error of our ways. Continue reading “Java application dynamic configuration using a properties file”→
If your java desktop application needs to store data in a database between sessions then a good solution is to embed a database into your solution. What this gives you is an application which installs the database as part of the application, builds the database tables and populates it with any initial data. This approach avoids the need for the user to install a database separately from the application.
In the previous post we looked at displaying information in a hierarchy using JTree.
Now all this is fine but, usually when we use a JTree it is because we want to be able to select an item, one or more. For our example let us concern ourselves with selecting a single item and displaying the detail associated with that item. Continue reading “Using JTree to select information”→
In the last post we saw how you can easily create a JTree using an array of strings. The JTree however did not display the values in a hierarchy but displayed all the values at the same level. So in this post we will build our Java Desktop Application using JTree with a hierarchy. Continue reading “Using JTree to display a hierarchy”→