As we mentioned in out last post we have been working on a site to help Java Developers use Open Source Projects. The site is in an early stage but we want to work on the site openly and improve it with your feedback.
Out goal is to help you use an Open Source Project. We want to help you easily look at the API’s/Javadoc; Make it easy to get a code snippet for using a feature in a library; Simplify finding the right blog post; And even get you a high-level view of the project.
Yes, it’s a big goal, but we feel like there is so much that can be done to make out lives as coders easier. We hope this is a good first step in the right direction.
Check out the site: http://CodeMaps.org. If you can’t find your favorite project we can help! Click the ‘Add Project’ button on the top, and our engine will import the project for you to view.
Oh yeah, make sure to let us know what you think. We want CodeMaps to grow into something that you use want to tell your friends about!
Whoops! We made a mistake.
We have been trying to build something amazing to help developers quickly understand how to get moving with large projects. As we have been doing that, we have been hearing a growing set of requests for help with Open Source Projects.
We have spent the last last few months improving our engine and building a couple of cool features to help the users with open source projects – in large part based on ideas that were sent to us. Well, it’s Spring, and it’s time to pull the covers off.
We are almost ready for our public release, but before that we want feedback from the community on what we have built. Want to be one of the first to find, sign up up now here: http://atxa.io/Hsv3Mx
Update: Some of our initial visitors had some issues while completing the feedback form. We apologize for it and the issue has been fixed. If you face any issues please drop us a note at firstname.lastname@example.org. Thanks!
Finding the right format for users to edit and view your Eclipse plugin’s data can be tricky. Eclipse provides many different types of editors for modification of its resources. Some examples of these are the Java, Text, JSP, XML, Ant editor etc. It also provides tabbed editors like the Plug In Manifest Editor which can have multiple sub editors as tabs in one editor. A simple example template to extend the tabbed editor when creating a new plug-in, is provided in Eclipse by default. For our project we needed to add a compare editor and a GEF editor as sub editors. This post should help you become more familiar with creating custom tabbed editors in Eclipse.
Eclipse is turning 10 years – and we have been in a mood to celebrate it. We have been involved in a lot of Eclipse related events in the past, but wanted to do something special this year.
If you are in Boston, come join us next week. We will be having free pizza, beer and even a birthday cake. We will have a bunch of people who really know Eclipse inside-out and will be showcasing a bunch of the cool technology being built these days.
Time and Location: We have planned to have the event on 17 November 2011 at 6:30PM, at Constant Contact, (Reservoir Place, 1601 Trapelo Road, Waltham, MA 02451 – see on map).
More details on the Architexa Company Updates.
When development teams are in the same room, it is not surprising to see diagrams being used – if only being shared via sketches made on pads, or through the use of whiteboards. Interestingly, despite the fact that OSS teams are distributed geographically, diagrams also play an important role in OSS development.
There was a helpful research done by Koji Yatani et al. at University of Toronto and Oregon State University. They studied developers on the Ubuntu project and found that developers create and distribute digitalized diagrams as opposed to physical sketches. While the uses of diagrams are specific to the Ubuntu projects, there are definitely lessons that we can learn to apply in other OSS projects to ensure successful development.
Yes, diagrams. All of us use diagrams in one way or another. Mostly, diagrams are used to enhance communication and to illustrate what exactly one is talking about.
“But that’s it. Diagrams are sketches which are meant to be thrown away without deserving a second look.”
Now that’s where you’re wrong. In fact, diagrams are more useful than they appear to be. Yes, diagrams often become outdated fast in the software development industry and that tends to lead to people having a biased view against them. They often quickly assume diagrams are useless.
What exactly makes a codebase easy to understand; the documentation or the tools that you use? In our effort to help developers who are working with large codebases, we conducted a survey (see details and highlights) to find out what techniques developers use to better understand code.
Every developer cares about code quality. But how do you maintain code quality throughout the software development cycle? Readability, modularity, and efficiency all are important factors of writing good code but there isn’t much agreement on the best way to maintain a high level of code quality.
One factor which is often missed in discussions is code visibility, or making sure your code has a clear structure so that others can easily understand it. (Take a look at the diagram above for some of the difficulties encountered when there is a lack of code visibility).
I have been looking into the practicality of UML and find this answer on stackoverflow very interesting:
Using UML is like looking at your feet as you walk. It’s making conscious and explicit something that you can usually do unconsciously. Beginners need to think carefully about what they’re doing, but a professional programmer already knows what they’re doing. Most of the time, writing the code itself is quicker and more effective than writing about the code, because their programming intuition is tuned to the task.
My question is: Is it all that bad to walk while looking at your feet? It is often said that learning to walk is one of the hardest skills a person has to learn. However, in time walking doesn’t seem like a “learned skill” anymore because we do it so much that it seems natural. But what happens when we are walking along a tricky path strewn with pebbles, banana-peels and the like; wouldn’t we feel safer to look at our feet as we walk?