Proper version control is a must for everyone who programs more than a few lines of code. Even if you develop your applications all by yourself it is very handy to be able to branch and merge your code, be able to roll back to previous versions or undo changes you made in the past. It works great for regular applications, but managing web applications or websites is a tad harder for two reason: You need a webserver to get your application going and you usually have to manage database revisions as well.
In the not-too-distant past, ENIAC was programmed with switches and a plugboard. Stored program computers soon followed that allowed one to write a program, load it into the computer memory, and run it. Initially, those programs had to be written in or manually translated into binary machine code, but soon assembly languages and assemblers were developed to simplify the process.
Currently there is no way for users to add documentation to components defined in mxml files. The asdoc tool doesn't read the comments in mxml files. Increasingly more components in the flex framework are being written in mxml.
Adding support for mxml in the asdoc tool would help developers to generate documentation for their components.
Several customer have also added requests in JIRA to support class level comments in mxml files.
In this InfoQ interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
Discover the Toolkit for Data Collection and Visual Analysis for Multi-Core Systems; it targets many common performance problems pertaining to Java applications running on multi-core or multi-processing platforms. These problems can have a major impact on the overall performance of Java middleware and applications. This toolkit has been designed for easy use by users with average skills.
For the past year I’ve been looking at the way I develop web based projects and how I can make it easier, better, faster, more stable, but most of all, portable. Like many PHP developers out there, I work on multiple projects at the same time. It’s not unusual for me to have three projects under development at any given time with an additional five projects that I’ve abandoned that I’m not yet willing to delete. I’ve developed a way of working with them that works for me. I’ve even written a Zend Framework based cli tool that sets up my work environment the way I like it.
A lot has been going on in Dojo-land, and we're finally ready to push out the release. I have tentatively named this the 'Sliced Bread' release, as over the last six months each new item has truly felt like "the best thing since sliced bread". This iteration of the Dojo Toolkit has a very large delta, countless levels of innovation, cleverness, polish, and usefulness, as well as several internal changes regarding the overall project.
One of our early goals for Google Chrome was to make the browser as fast as we possibly could. But in addition to raw speed, we wanted it to be highly responsive. After all, it doesn't matter how fast pages can be loaded if the user interface is locked up!
Introducing Geode, an experimental add-on to explore geolocation in Firefox 3 ahead of the implementation of geolocation in a future product release. Geode provides an early implementation of the W3C Geolocation specification so that developers can begin experimenting with enabling location-aware experiences using Firefox 3 today, and users can tell us what they think of the experience it provides. It includes a single experimental geolocation service provider so that any computer with WiFi can get accurate positioning data.
Inspired by the success of my “Awk One-Liners Explained” article (30,000 views in first three days), I decided to explain the famous sed one-liners as well.
These one-liners, just like the Awk one-liners, are compiled by Eric Pement.
Let's say you want the toolbar to be on the right side of your application. Let's also say that you want the icons to be larger than 16x16 or 24x24. At the same time, you want to use the NetBeans Actions system, so you can't simply create a TopComponent and then put buttons on the TopComponent. How to solve this problem? Use Lookup!