Skip to content

Software Development News: .NET, Java, PHP, Ruby, Agile, Databases, SOA, JavaScript, Open Source

Methods & Tools

Subscribe to Methods & Tools
if you are not afraid to read more than one page to be a smarter software developer, software tester or project manager!

Open Source

Survey: Is NetBeans IDE 8.1 Ready for Release?

NetBeans Highlights - Wed, 10/07/2015 - 13:25
The release candidate of NetBeans IDE 8.1 is available, with many bug fixes. Once you have downloaded and used NetBeans IDE 8.1 RC, we would like to know what you think about it. Take the NetBeans IDE 8.1 Community Acceptance Survey and tell us about your experience! The survey will be opened until November 1st. Thank you in advance for participating in the survey! Jiri Kovalsky NetBeans Community Manager
Categories: Java, Open Source

NetBeans Day San Francisco, Sunday October 25, 2015

NetBeans Highlights - Wed, 10/07/2015 - 13:25
Join the NetBeans team at NetBeans Community Day at JavaOne 2015! NetBeans Community Day is open and free to registered JavaOne conference attendees.
Categories: Java, Open Source

Free: NetBeans Day Paris, Friday October 16, 2015

NetBeans Highlights - Wed, 10/07/2015 - 13:25
La communauté NetBeans vous invite pour une conférence gratuite d'une journée. Venez rencontrer d'autres utilisateurs de NetBeans, découvrir ou apprendre à utiliser NetBeans.
Categories: Java, Open Source

Free: Oracle Cloud Day 2015, Tuesday October 6, 2015

NetBeans Highlights - Wed, 10/07/2015 - 13:25
Oracle Cloud Day is coming to the Netherlands! For example, in an interactive workshop, you will see many demos.
Categories: Java, Open Source

Build with NetBeans IDE, Deploy to Oracle Java Cloud Service

NetBeans Highlights - Wed, 10/07/2015 - 13:25
Save time and effort deploying applications. Learn to set up Oracle Java Cloud Service, then install and use the Oracle Cloud plugin in the NetBeans IDE.
Categories: Java, Open Source

Build a Rich Client Platform To-Do Application in NetBeans IDE

NetBeans Highlights - Wed, 10/07/2015 - 13:25
Practice using NetBeans IDE features that improve code quality and increase developer productivity.
Categories: Java, Open Source

Video: Installing and Using Java ME SDK 8.0 Plugins in NetBeans IDE

NetBeans Highlights - Wed, 10/07/2015 - 13:25
This screencast demonstrates installation and usage of Oracle Java ME SDK 8.0 Plugins in NetBeans IDE on the Windows operating system.
Categories: Java, Open Source

MetaEdit+ plugin for Eclipse

Date Created: October 6, 2015 - 01:41Date Updated: October 6, 2015 - 09:13Submitted by: Risto Pohjonen [MetaCase]

Plugin for integrating Eclipse with MetaEdit+

The MetaEdit+ plugin for Eclipse provides integration between MetaEdit+ and Eclipse. The plugin allows you to browse MetaEdit+ models and use the main MetaEdit+ functions from Eclipse. It can also automatically import into Eclipse the source code generated from MetaEdit+.

The integration between MetaEdit+ models and Eclipse includes:

  • launching MetaEdit+ from Eclipse and logging in, opening MetaEdit+ projects and starting its API,
  • showing the MetaEdit+ model hierarchy in an Eclipse tree view,
  • opening and editing MetaEdit+ models from Eclipse,
  • running generators on MetaEdit+ models, and importing the results as Eclipse solutions.

    See installation instructions, getting started and the plugin guide for details.

  • Categories: Open Source

    EclipseCon North America 2016 - Call for Papers

    Eclipse News - Mon, 10/05/2015 - 17:49
    The call for papers is now open. Be the first to submit your talk!
    Categories: Open Source

    Project of the Week, October 5, 2015 Front page news - Mon, 10/05/2015 - 06:08

    Here are the featured projects for the week, which appear on the front page of


    GnuCash is a personal and small-business finance manager with a check-book like register GUI to enter and track bank accounts, stocks, income, and expenses. GnuCash is designed to be simple and easy to use, but still based on formal accounting principles.
    [ Download GnuCash ]

    Equalizer APO

    Equalizer APO is a parametric/graphic equalizer for Windows. It is implemented as an Audio Processing Object (APO) for the system effect infrastructure introduced with Windows Vista. It features a virtually unlimited number of filters, works on any number of channels, has low CPU usage, has a modular graphical user interface, and is very low latency which makes it well suited for interactive applications.
    [ Download Equalizer APO ]


    Our goal is to improve upon VisualBoyAdvance by integrating the best features from the various builds floating around. In order to uncompress the downloaded package, you need WinRAR or 7-Zip.
    [ Download VBA-M ]


    TYPO3 is an enterprise class Web CMS written in PHP/MySQL. It’s designed to be extended with custom written backend modules and frontend libraries for special functionality. It has very powerful integration of image manipulation.
    [ Download TYPO3 ]


    A full featured OS for an aging PC. Aging hardware needs the right system on it to squeeze a few more years out of your current system without sacrificing performance, capability, usability, and aesthetics.
    [ Download LXLE ]


    SMPlayer is a free media player for Windows and Linux, with built-in codecs that can also play and download Youtube videos. It also remembers the settings of all files you play, so you can leave a movie and later resume at the same point you left it, and with the same settings: audio track, subtitles, volume, etc. SMPlayer also features the ability to play Youtube videos or download subtitles.
    [ Download SMPlayer ]


    dispcalGUI is a graphical user interface for the display calibration and profiling tools of Argyll CMS, an Open Source color management system. Calibrate and characterize your display devices using one of the many supported hardware sensors, with support for multi-display setups and a variety of available settings like customizable whitepoint, luminance, tone response curve, the option to create matrix and look-up-table ICC profiles, with optional gamut mapping, and some proprietary 3D LUT formats.
    [ Download dispcalGUI ]

    Stella – Atari 2600 Emulator

    Stella is a multi-platform Atari 2600 VCS emulator. It allows you to play all of your favorite Atari 2600 games again! Stella was originally developed for Linux by Bradford W. Mott, and is currently maintained by Stephen Anthony.
    [ Download Stella – Atari 2600 Emulator ]

    PlatformIO Storage

    PlatformIO is a cross-platform code builder and the missing library manager, ready for embedded development, IDE and Continuous integration, and Arduino and MBED compatible. You have no need to install any IDE or compile any tool chains. PlatformIO has pre-built different development platforms, including compiler, debugger, uploader (for embedded boards), and many other useful tools. PlatformIO also has pre-configured settings for the most popular Embedded Boards. You have no need to specify in Project Configuration File type, frequency of MCU, or upload protocol. PlatformIO Library Manager allows you to organize external libraries. You can search for new libraries via the Command-Line or Web interfaces. Due to platformio lib update command you will also have up-to-date libraries.
    [ Download PlatformIO Storage ]

    Categories: Open Source

    October 2015, “Staff Pick” Project of the Month – TeXstudio Front page news - Fri, 10/02/2015 - 21:42

    For our October “Staff Pick” Project of the Month, we selected TeXstudio, an integrated writing environment for creating LaTeX documents. Benito van der Zander and Tim Hoffmann, TeXstudio’s Lead Developers, shared their thoughts about the project’s history, purpose, and direction.

    SourceForge (SF): Tell me about the TeXstudio project please.
    Benito van der Zander (van der Zander): TeXstudio is a (La-) TeX integrated writing environment (IWE). While IDEs are there to develop computer programs, TeXstudio is there for writing (La-)TeX. TeX is a programming language for natural language text, which takes a plain text with macro annotations and compiles it to PS or PDF. The advantage is that you get a document with consistent style and nice formulas, where some parts of it can be generated algorithmically and stored in a normal version control system. The disadvantage is that it is less intuitive to write. This is where TeXstudio comes into play and makes the writing intuitive again. For example it auto generates most TeX commands, shows the source with highlighting, marks invalid parts, and previews the resulting document.

    SF: What made you start this?
    van der Zander: I was writing a novel about how to migrate from Windows to Linux, while searching for a cross-platform LaTeX editor that would have features to support novel writing, (i.e. inline spelling, grammar, and style checking). The most complete cross-platform LaTeX editor seemed to be Texmaker. However, it had many little bugs and no inline spell checker so I wrote a lot of patches for it. But they were not accepted so I had to fork it, which resulted in TeXstudio.
    Tim Hoffmann (Hoffmann): For me, it started when I was looking for a LaTeX editor to write my PhD thesis. None of the available programs fulfilled my needs, but Texmaker and Benito’s fork came closest. So I started writing some patches and small extensions. I found that TeXstudio was more open to contributions. Over time, I got more and more involved.

    SF: Has the original vision been achieved?
    van der Zander: The focus has moved from novel writing to the writing of math-heavy documents. Also the novel writing support was not as helpful as expected. The spell checker based on Hunspell works fine, but the grammar checker based on LanguageTool returns too many false negatives and positives. The style checker should have implemented some writing guidelines by Andreas Eschbach, which suggest you strike out every adjective to see if these words are necessary. The strikeout worked but not the adjective search. To really improve it we would need to research natural language theory but that is outside of the scope of this project, so we are waiting to improve the underlying libraries. I had hoped to get it established as a general-purpose text editor but as TeXstudio grows it becomes more LaTeX-centric. And we are now three core developers with different goals and visions.
    Hoffmann: To me, the vision of TeXstudio is an editor that lets me focus on the text I want to write, not being distracted by technical aspects. We’ve come a great deal towards that goal, even though there is still room for improvement.

    SF: Who can benefit the most from your project?
    van der Zander: Everyone who writes something using LaTeX, be it research papers, PhD theses, or novels.
    Hoffmann: That’s true. TeXstudio significantly reduces the entry barrier for LaTeX beginners. Due to its high configurability and scripting support, more advanced users can adapt TeXstudio to their needs and work most efficiently.

    SF: What core need does TeXstudio fulfill?
    van der Zander: Writing a LaTeX document in an editor that understands LaTeX and does not display it as plaintext.
    Hoffmann: LaTeX was invented 30 years ago and in some areas is still better than modern WYSIWYG word processors. However, due to the limited computation power at that time, it was designed to the needs of the computer and not to the needs of the user. As a user interface, TeXstudio bridges this gap by working around many of the shortcomings and limitations of LaTeX. This makes LaTeX significantly easier and more fun to use. Hence our slogan: “LaTeX made comfortable”.

    SF: What’s the best way to get the most out of using TeXstudio?
    van der Zander: Just start writing your text and while you are at it, here are some useful features to help you:

    • Unconnected block editing—You can select multiple parts of a file and edit them simultaneously, no matter where they are. This is especially powerful when searching for a regular expression. If you want to change all matches, you do not need to think about a replacement expression, just let it select all matches and edit them in the editor.
    • User scripts with triggers—You can write an arbitrary JavaScript function that is called, whenever you type or do something. You could write something to play Conway’s’ Game of Life in the editor.
    • Magic comments—TeXstudio does not use project files like most IDEs; rather, it stores all metadata in tex files itself. So, you can put % !TeX program = xelatex at the beginning of a file, if you want it to be always compiled with xelatex.
    • Inline preview—It is easy to see that there is a PDF viewer showing the entire output document, but you can also view only parts of an document embedded in the text or as tooltips.
    • Implicit cut buffer—You can surround text with parentheses or a command, do not write something on both sides of the text.  Just select the text and write the command/opening parenthesis, then TeXstudio’s auto completion will automatically restore the overridden text and surround it with the opening and closing parentheses.

    SF: What has your project team done to help build and nurture your community?
    van der Zander: We mostly work with the classics like bug/feature tracker, mailing lists, and personal mail. Once we renamed the project and let the community vote on the new name.
    Hoffmann: Generally, we try to be responsive and helpful, be it bug reports, feature requests or any other questions. Also, we are lowering the entry barrier for contributions, for example, we just included an online translation service. Now, you don’t need any specialized tools or knowledge to provide a translation.

    SF: Have you all found that more frequent releases helps build up your community of users?
    van der Zander: They seem to help a lot with us becoming SF’s project of the week and month.
    Hoffmann: Distributing new features and bug fixes regularly certainly helps to have better software. I expect that it has a positive effect on the community, but it’s hard to tell.

    SF: What was the first big thing that happened for your project?
    van der Zander: We do not really have big things, just many little things working together.

    SF: What is the next big thing for TeXstudio?
    van der Zander: I always wanted to add a macro AI, where you could edit some text, and than the AI would replay those actions on other parts of the text. It would be like a VI-mode but you would not have to remember any commands, and you would not need to tell it. Also, a lot of people have asked for touch screen or git support.
    Hoffmann: In fact, there are lots of big and small ideas around, for example,
    an auto-updating life view of your resulting document.

    SF: How long do you think that will take?
    van der Zander: Years…

    SF: Do you have the resources you need to make that happen?
    van der Zander: At the moment, I do not have time to do any of that. Also the macro AI would need many samples of typical editing tasks.
    Hoffmann: Since TeXstudio has grown, we invest a lot of time in maintenance and community work. Time for big things is rare. We make the best from our limit resources by using small steps and continuity.

    SF: If you had it to do over again, what would you do differently for TeXstudio
    van der Zander: One of the first things was to switch from the standard QTextEdit to a library called QCodeEdit. QTextEdit renders rich text like HTML, while QCodeEdit was made for editing source code, which is much more like LaTeX. It would have been wise to use another editor component. Also we would write more test cases for features we added. It always happens that some of the new features break stuff.
    Hoffmann: Stability, clean code and testing should have had a higher priority.

    SF: Why?
    van der Zander: I used QCodeEdit 2, which was abandoned by the author in favor of QCodeEdit 3, which got a much better internal design. But then he never truly finished QCodeEdit 3, so we were stuck with maintaining the old library ourselves. And it is still had a lot of minor editing/rendering bugs that we had to fix.
    Hoffmann: We did not foresee the dimensions the code and the user base would reach. At the beginning, a feature that just worked for the usual need was okay. Now, it really needs to be correct because one of the many users will step on even the remotest bug.

    SF: Any reason you can’t do that now?
    van der Zander: Switching QCodeEdit to another editor component now, would invalidate all the work we have done on it so far.
    Hoffmann: We are gradually improving our code, but resources are very limited. Therefore, we’ve just revised our release scheme and update notifications to make using of beta and release candidate versions easier. This will be available from version 2.10.4 on. I encourage willing users to subscribe at least for release candidates. We hope to track down bugs more early with the help of the community.

    SF: Is there anything else we should know?
    van der Zander: There will be a new release, 2.10.4, very soon. So be on the lookout!
    Hoffmann: Help in any way is very welcome. You don’t necessarily have to be a programmer to contribute to TeXstudio: Documentation, translation, UI/icon design, tutorials and screencasts are some of the non-programming areas that would certainly benefit from more attention. If you are interested, just contact one of the developers. We’ll find a task that’s fun for you and that puts your talents to good use.

    Categories: Open Source

    October 2015, “Community Choice” Project of the Month – fre:ac Front page news - Fri, 10/02/2015 - 21:39

    For our October “Community Choice” Project of the Month, the community elected fre:ac, an audio converter and CD ripper for various formats and encoders. Robert Kausch, fre:ac’s Lead Developer, shared his thoughts about the project’s history, purpose, and direction.

    SourceForge (SF): Tell me about the fre:ac project please.
    Robert Kausch (Kausch): fre:ac is an audio converter and CD ripper that tries to provide a simple and intuitive interface without sacrificing features. It scales all way the from converting CD tracks to MP3 files with a single click to replicating whole music libraries in a different format while preserving folder and file name structure.

    SF: What made you start this?
    Kausch: Back in the days I just couldn’t find a free and easy to use CD ripper, so I decided to write my own. Around the same time, someone came up with the Bonk audio format which I added support for as a distinguishing feature. That provided for the original project name BonkEnc Audio Encoder. The project was finished quite soon, but after publishing it on SourceForge, people started requesting more features and it developed its own momentum.

    SF: Has the original vision been achieved?
    Kausch: Yes, absolutely! This project was supposed to be a simple CD to MP3/Bonk ripper to be used by maybe a few dozens of people. Today, it’s one of the most popular audio converters with tens or hundreds of thousands of users from all around the world.

    SF: Who can benefit the most from your project?
    Kausch: Anyone who needs some kind of audio format conversion.

    SF: What core need does fre:ac fulfill?
    Kausch: Any kind of audio format conversion. Whether you need to rip CDs to FLAC files for archival, convert to MP3 for your mobile device or create audio books with chapter marks, fre:ac should be the tool of choice.

    SF: What’s the best way to get the most out of using fre:ac?
    Kausch: Users should first explore the interface, which is designed to be intuitive and self-explanatory. A quick tutorial for ripping CD tracks to MP3 files as well as some “How to” style questions and answers are included with fre:ac. In addition, lots of more advanced community made tutorials are available on the Internet.

    SF: What has your project team done to help build and nurture your community?
    Kausch: I am the only developer and provide most of the support, so there is no real project team. The SourceForge forums and tracker are of great help for keeping in touch with the community and I use email to talk to individual users. In addition, releases and other news are posted on Twitter and since about two years ago. I have also been writing regular blog posts to talk about everything that’s going on in fre:ac development. I got inspired to doing this when reading the regular blog posts of the Haiku and ReactOS operating system projects, which give insight of what’s going on behind the scenes between releases.

    SF: Have you all found that more frequent releases help build up your community of users?
    Kausch: While new releases always spark a lot of interest, I try not to release too often or too early. As my resources are limited, it’s crucial that releases are stable and do not trigger too many bug reports. This leaves more time for implementing new features.

    SF: What was the first big thing that happened for your project?
    Kausch: The name change from BonkEnc to fre:ac. It was a lot of work to update the site and software and notify everyone about the new name, and it kind of felt like a restart of the whole project.

    SF: What helped make that happen?
    Kausch: A few years after starting the project, I didn’t really like the old name anymore. Especially as it turned out that the eponymous Bonk format had become obsolete. At some point I started looking for a new name and ultimately ended up with fre:ac, a contraction of free audio converter.

    SF: What was the net result for that event?
    Kausch: I like the new name much better but, that aside, I don’t think it had a major impact on the fate of the project.

    SF: What is the next big thing for fre:ac?
    Kausch: The upcoming 1.1 release will be an almost complete rewrite of fre:ac’s core based on a modular architecture providing lots of new features and support for alternative operating systems. People can already try the preview releases dubbed snapshots that are released every few weeks. With so many changes, you might expect this to be released as version 2.0, but I decided to stick to 1.1 as I think this is what fre:ac 1.0 should have been originally.

    SF: How long do you think that will take?
    Kausch: I hope to be able to make a 1.1 beta release at the end of this year or in early 2016. The final 1.1 release should then be finished within half a year after the beta.

    SF: Do you have the resources you need to make that happen?
    Kausch: I hope so. The most important resource is time and I’m a little limited on it. I’m working on fre:ac in my free time besides doing a regular 9 to 5 job as a software engineer.

    SF: If you had it to do over again, what would you do differently for fre:ac
    Kausch: If I started a project like this now, I would use a modular architecture from the start. The original project was never meant to become this big, though, so having a monolithic architecture seemed sufficient back then.

    SF: Why?
    Kausch: A modular architecture makes it much easier to add new codecs and other features. It also helps when it comes to porting the software to other platforms.

    SF: Any reason you can’t do that now?
    Kausch: I’m doing that in the ongoing fre:ac 1.1 development effort.

    SF: Is there anything else we should know?
    Kausch: I’d like to thank everyone who helped getting the project this far. Translators, regular testers and especially the users who report bugs and make feature requests. The project would never have grown this big without you!

    Categories: Open Source

    Google Summer of Code wrap-up: Red Hen Lab

    Google Open Source Blog - Fri, 10/02/2015 - 18:00
    For our Google Summer of Code wrap-up this week we have The Distributed Little Red Hen Lab. A new organization for 2015, Red Hen Lab had three student projects. Read on to learn about the Lab and their effort to scan a huge repository of international television news programming. redhenlogo.jpgThe Distributed Little Red Hen Lab is an international consortium for research on multimodal communication. We develop open source tools for joint parsing of text, audio/speech and video, using datasets of various sorts, most centrally a very large dataset of international television news called the UCLA Library Broadcast NewsScape. Red Hen uses 100% open source software. In fact, not just the software but everything else—including recording nodes—is shared in the consortium.
    The Red Hen archive is a huge repository of recordings of TV programming, processed in a range of ways to produce derived products useful for research, expanded daily, and supplemented by various sets of other recordings. Our challenge is to create tools that allow us to access audio, visual, and textual (closed-captioning) information in the corpus in various ways by creating abilities to search, parse and analyze the video files. However, as you can see, the archive is very large, so creating processes that can scan the entire dataset is time consuming, and often with a margin of error.
    Our projects for Google Summer of Code 2015 (GSoC) challenged students to assist in a number of projects, including some that have successfully improved our ability to search, parse and extract information from the archive.
    Ekateriana Ageeva - Multiword Expression Search and Tagging
    Ekaterina built a multiword expressions toolkit (MWEtoolkit), which is a tool for detecting multi-word units (e.g. phrasal verbs or idiomatic expressions) in large corpora. The toolkit operates via command-line interface. To ease access and expand the toolkit's audience, Ekaterina developed a web-based interface, which builds on and extends the toolkit functionality.
    The interface allows us to do the following:
    • Upload, manage, and share corpora
    • Create XML patterns which define constraints on multiword expressions
    • Search the corpora using the patterns
    • Filter search results by occurrence and frequency measures
    • Tag the corpora with obtained search results

    The interface is built with Python/Django. It currently supports operations with corpora tagged with Stanford CoreNLP parser, with a possibility to extend to other formats supported by MWEtoolkit. The system uses part of speech and syntactic dependency information to find the expressions. Users may rely on various frequency metrics to obtain the most relevant search results.
    Owen He - Automatic Speaker Recognition System
    Owen_He-web.jpgOwen used a reservoir computing method called conceptor together with the traditional Gaussian Mixture Models (GMM) to distinguish voices between different speakers. He also used a method proposed by Microsoft Research last year at the Interspeech Conference, which used a Deep Neural Network (DNN) and an Extreme Learning Machine (ELM) to recognize speech emotions. DNN was trained to extract segment-level (256 ms) features and ELM was trained to make decisions based on the statistics of these features on a utterance level.
    Owen’s project focused on applying this to detect male and female speakers, specific speakers, and emotions by collecting training samples from different speakers and audio signals with different emotional features. He then preprocessed the audio signals and created the statistical models from the training dataset. Finally, he computed the combined evidence in real time and tuned the apertures for the conceptors so that the optimal classification performance could be reached. You can check out the summary of results on GitHub.
    Vasant_Kalingeri-web.jpgVasanth Kalingeri - Commercial detection system
    Vasanth built a system for detecting commercials in television programs from any country and in any language. The system detects the location and the content of ads in any stream of video, regardless of the content being broadcast and other transmission noise in the video. In tests, the system achieved 100% detection of commercials. An online interface was built along with the system to allow regular inspection and maintenance.
    Initially the user uses a set of hand tagged commercials. The system detects this set of commercials in the TV segment. On detecting these commercials, it divides the entire broadcast into blocks. Each of these blocks can be viewed and tagged as commercials by the user. There is a set of 60 hand labelled commercials for one to work with. This process takes about 10-30min for a 1hr TV segment, depending on the number of commercials that have to be tagged.
    When the database has an appreciable amount of commercials (usually around 30 per channel) we can use it to recognize commercials in any unknown TV segment. On making changes to the web interface, the system updates its db with new/edited commercials. This web interface can be used for viewing the detected commercials as well. For more information see Vasanth’s summary of results.
    By Patricia Wayne, UCLA Communication Studies
    Categories: Open Source

    Download Eclipse Mars.1

    Eclipse News - Fri, 10/02/2015 - 17:00
    Eclipse Mars.1 has just been released and is available for download.
    Categories: Open Source

    Clone abstractor for C++ methods

    Date Created: October 2, 2015 - 04:35Date Updated: October 6, 2015 - 09:11Submitted by: Krishna Narasimhan [Goethe University, Frankfurt]

    Abstract—Software clones are prevalent. In the work of Lague et al., they observe that 6.4% and 7.5% of the source code
    in different versions of a large, mature code base are clones. The work of Baxter et al. reports even higher numbers, sometimes exceeding 25%. We consider the prevalence of such near miss clones to be strong indicators that copy-paste-modify is a wide-spread development methodology. Even though clones are prevalent, they are a significant development headache. Specially, if bugs arise in one of the clones, they need to be fixed in all of the clones. This problem is acknowledged in the work of Juergens et al. who say in their work that “cloning can be a substantial problem during development and maintenance”, since “inconsistent clones constitute a major source of faults”. A similar concern is raised in practitioner literature suggesting that clones should be removed in some form or the other. We present a tool that can be installed as a plugin to Eclipse CDT, the development environment for C/C++. The research prototype comes with a refactoring option called ”Copy Paste merge” refactoring, which is available as a menu option in the modified version of the Eclipse CDT.

    More details on how to use the tool and a test input file is available here:

    Categories: Open Source

    Dojo Recap – Week Ending September 25, 2015

    The Dojo Toolkit - Announcements - Thu, 10/01/2015 - 18:37

    Last week we made fixes in the Dojo 1.x codebase as we start preparing for a Dojo 1.11 release, and further progress towards Dojo 2. Let us know if you would like to get involved!

    Last week in Dojo 1.x

    Last week we fixed the following issues in Dojo 1.x:

    DojoX Util Up next in Dojo 1.x

    We are starting to put together a release plan for 1.11, and updated point releases for earlier versions of Dojo. We have about 100 more issues to resolve, and then we’ll be ready for the 1.11 release! The main things we are considering for 1.11 are as follows:

    Other packages commonly used with Dojo 1.x

    The community has also made some recent updates to dgrid and Intern over the past two weeks.


    Over the last two weeks, we landed 5 fixes to dgrid master as we work towards a dgrid 0.5 release.

    Intern Last week in Dojo 2

    We’re making further progress on Dojo 2 as well:

    class declaration

    We have a newly revised class declaration / composition proposal ready for review!


    No updates last week.


    No updates last week.


    No updates last week.


    No updates last week.


    No updates last week.


    No updates last week.


    No updates last week.


    We have a newly revised parser proposal that is ready for your review and feedback!


    No updates last week.

    Last week, we spent most of our time planning out a reference application for Dojo 2, as well as evaluating a variety of options and features which will help improve the overall approach to Dojo 2.

    This week’s Dojo 2 efforts

    Here we’ve identified a few of our aspirations for the upcoming week. This week in Dojo 2, we have more code reviews to complete and pull requests to land. If you’re interested in helping out in these areas, or other parts of Dojo 2, just let us know, either in the comments or on IRC.

    class declaration
    • Discuss feedback on the proposal
    • Rename package to compose
    Core Crypto DOM
    • Triage any bug reports or pull requests that may come in this week
    dstore i18n Loader parser
    • Respond to proposal feedback

    Over the last couple of weeks, and this week, we’ve also been working on evaluating other projects out there to determine how they can benefit or inspire our efforts, or offer possible integration options. We’ve also been working on a reference application that we will be using to document and validate the APIs in Dojo 2.

    Weekly IRC meeting

    As usual, our weekly IRC meeting is on #dojo-meeting at 9am Pacific time on Tuesday.

    View the Dojo weekly meeting logs

    This week’s agenda
    • 1.11 release plan (we’re aiming for November for the release)
    • Discuss open 2.x challenges

    The Dojo 2 loader, core, and dom are near an alpha state! Progress is being made on routing, crypto, i18, dstore, class declaration and parser. Please let us know if you plan to work on any features, or would like to get involved, so we can collaborate.

    Categories: Open Source, RIA

    Case Study: RQL Playground

    The Dojo Toolkit - Announcements - Thu, 10/01/2015 - 18:23

    This post continues our series of interviews with users of Dojo. This time, we interview Michal BelianskĂœ of Gratex International, creators of the RQL Playground.

    RQL PlaygroundRQL Playground Q: How did you first learn about Dojo?

    A: We have conducted research about available toolkits and frameworks and have chosen Dojo. We first learned about Dojo during our research.

    Q: Why did you choose Dojo?

    A: There were several toolkits available of varying quality and completeness. Dojo’s components provide good solutions to common user experience problems (like DOM manipulation, CSS queries, pane-based layouts, data binding, etc.). Dojo ships with a Dijit widget system and extensive component set, instead of combining components from several different sources.
    And last but not least, the package system makes it easy to manage large-scale UI development projects.

    Q: Were you previously using another toolkit?

    A: Yes, an in-house developed XML-based AJAX framework that we used and improved for 8 years.

    Q: What does your application or service do?

    A: Our application provides a playground for RQL (Resource Query Language) for testing RQL queries on passed data. You can enter the source JSON, query (in RQL) and also create your own operators. It contains some predefined samples with associated predefined queries.

    Q: How does your application use Dojo?

    A: The front-end UI is built mainly with a set of Dojo widgets and other libraries like CodeMirror and xstyle. We also extend existing Dijit widgets with required functionality for playground purposes, such as a closable dijit/TitlePane.

    Q: Overall what is your experience with Dojo?

    A: We like that Dojo is robust in the way that many other toolkits and frameworks are not, providing not only a set of useful and easy extendable widgets, but plenty of ready to use components.

    Q: What are your future plans with Dojo?

    A: We are looking to start working with TypeScript and are interested to see how Dojo 2 can improve our productivity. We’re skeptical but keeping an open point of view about TypeScript!


    Thanks Michal for telling us about your experience with Dojo. If you would like to share your experience with Dojo, please contact us.

    Categories: Open Source, RIA