QA says, “Thank you very much”

Few days back, J. O’Conner blogged about his recent experience with the NetBeans Community, and calling himself a proud member.

I’ve always known that I’m a NetBeans user, but I would never have gone so far as to call myself a community member. I feel differently after this experience though. I’m glad to be part of the NetBeans community. If you use NetBeans, you’re part of the community too!

Wow 🙂 Later that day, I got an email from NetBeans QA Team and I also had similar experience. Here’s what QA said,

In the past you have taken the time to report issues that you encountered while using the NetBeans IDE. As you may be aware already, a new version NetBeans IDE 6.5 has just been released.

We’d like to inform you that the following issues you reported have been addressed in the new version;

Aug 28, 2008

Three months back, I had blogged NetCAT 6.5 Weekly Report #6, where I had said,

Actually, when bugs filed by a user get fixed, they are not visible in My Issues, which is different for every user.

Nov 25, 2008

This day, when I received the mail and found out that, NetBeans QA Team had fixed 8 bugs filed by me during the development phase of NetBeans 6.5 and NetCAT Program.

We really appreciate your contribution to help us make NetBeans IDE (Platform, Java SE, Java Web and EE, Java ME, Ruby, C/C++, PHP, SOA) better for you as well as for other users. We look forward to receiving feedback from you in the future.

Wow, thats indeed a great way to notify the user, I mean community member. Happy NetBeaning!

“Thank you very much”

Advertisements

WOW, I am ranked 10th!

Growing Blogs

Blogs of the day, as maintained by WordPress, I guess! I saw trackbacks in my blog admin and was surprised to find out that I was ranked 10th on 21st Nov, 2008!

Others

Nothing much, I am having exams these days, watching India thrash England 5-0 in 7 match ODI Series being played in India.

Looking forward to see “Quantum of Solace” this weekend. Hope to have an action-packed weekend…

NetCAT 6.5 Weekly | Final Report

Development Simplified, Once Again

Well, its on every blogosphere now, NetBeans 6.5 IDE has been officially released. Everyone have already given an overview of almost every feature. I thought of blogging something unique, as always 😉

NetCAT Ends..

Jiri Kovalsky, NetCAT 6.5 Coordinator mailed us today at the NetCAT mailing list, points are calculated and results are out. Here’s what he says,

Hello folks,

I am glad to announce that final CAT points were calculated and published including a detailed breakdown of activity for every NetCAT participant.

Now, let me announce our winners! I think it’s actually not a surprise for those of you who were reading my NetCAT status reports regularly. So, in the “Most helpful NetCAT 6.5 member” category I am happy to congratulate to the following 3 NetCAT participants:

1. Saptarshi Purkayastha, India   1519 (13.09)
2. Rajiv Perera, Sri Lanka        1495 (13.35)
3. Eric Smith, USA                 710  (6.12)

Wow, first two are too close. Hats off to Jirka for the calculations, and Saptarshi, Rajiv, Eric congratulations for being the Most Helpful Members.

My Score..

Well, as you have seen some astonishing figures. I am way too behind them. I earned 253 points with 2.18 efficiency. I had opted to focus on PHP support and Documentation. I am glad to see community is liking the PHP support and they are applauding the efforts of PHP Team.

If you are interested to see breakdown of my points, have a look at this page; http://qa.netbeans.org/processes/cat/65/activity.html#55

I have filed 16 Bugs, 1 RFE and sent 157 mails. I took part in Top 6.5 Annoyances survey, Community Acceptance survey and Satisfaction survey.

I finished at 13th position out of 60 participants 😀


Blogs Summary..

Now, that it has come to an end, I would like to share my blogs which I posted since NetCAT began, specifically related to NetCAT.

Weekly Reports

Issues, Debates

Special

Thank You

I enjoyed every bit of it and it was a great experience. Also, special thanks to NetBeans Team as they listen to several debatable issues and are keen to resolve them in right manner.

NetBeans 6.5 boots with a b'day stamp on splash screen!

Here’s one instance, how they listen to community suggestions…

Simplify Development | NetBeans 6.5

The Only IDE You Still Need..

NetBeans™ IDE 6.5 introduces several new features, including a robust IDE for PHP, JavaScript, Debugging for Firefox and IE, and support for Groovy and Grails. This release also includes a number of enhancements for Java™, Ruby and Rails, and C/C++ development. Java™ feature highlights include: built-in support for Hibernate, Eclipse project import, and Compile-on-Save.

NetBeans™ IDE 6.5 also contains all 6.1 features including an intelligent JavaScript Editor, support for Spring Framework, ClearCase (via Update Center), and RESTful Web Services.

Combining excellent out of the box experience, compelling features, and a great plugin ecosystem, NetBeans™ IDE 6.5 is a must-download for developers.

Intuitive and feature-rich IDE for PHP

  • Simplify your PHP development with the award-winning open source NetBeans IDE.
  • Value Proposition: The NetBeans IDE for PHP offers the best of both worlds: the productivity of an IDE (code completion, real-time error checking, debugging and more) with the speed and simplicity of your favorite text editor. The IDE also includes a database explorer, JavaScript editor and debugger, and integrated VCS support. All of these features and more in a less than 30mb download.

Web development simplified

  • Simplify web development with the NetBeans IDE.
  • Value Proposition: The NetBeans IDE supports end to end web development for PHP, Ruby, Java, or Groovy developers. Featuring an advanced JavaScript editor with debugging for Firefox and IE, CSS/HTML code completion, database explorer/SQL query editor, and easy integration with you web stack of choice, the NetBeans IDE provides the web development tools you need.

Python EA Release

Simplify your Python development with the NetBeans IDE for Python- Early Access. This community driven project combines the practical development expertise of Python developers with the experience of IDE development by the NetBeans community.

Download Python EA Release

Developers can enjoy great editor features such as code completion, semantic highlighting, instant rename, smart indentation, pair matching, and more. The EA release also includes a community developed Python debugger as well as the ability to choose between the Python and Jython runtimes.

Python EA Download Webpage

Enjoy NetBeaning!

Blog Series | New Project Type

Today, I begin a blog series on my learnings of NetBeans API’s, interacting with experienced folks on the mailing lists and browsing through NetBeans sources, that might help me (possibly others as well) “Create a New Project Type” in NetBeans IDE.

Abstract

I will be creating a project type that I could use in my final year project based on NetBeans Platform (updated Jun 10 ’09). Right now, I don’t know how long this series would last, but I would try to cover as much as I learn. Feel free to present your views (negative/positive), suggestions or enhancements to the approaches I will follow.

Introduction

The NetBeans IDE (starting with version 4.0) organizes user work into projects. Each project corresponds to exactly one project folder on disk. A given disk folder may be a project folder or not; you cannot have two projects in one folder.

What do I think?

I think they are talking about a disk folder having a single /nbproject sub-folder, would be considered as a project by NetBeans. That means, we need to create an implementation of an interface, Project.

Project (Project API)

This (public) interface (which extends another interface Lookup.Provider) resides in Project API (Its primarily of interest to the project type provider modules, infrastructure & generic GUI).

public interface Project
extends Lookup.Provider

Now, there are two methods to be implemented, one of them specified by Lookup.Provider[1], present in Project (due to inheritance) and the other by Project[2] itself.

Refer Javadocs…

[1] http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-projectapi/org/netbeans/api/project/Project.html#getLookup()

Objects implementing interface Lookup.Provider are capable of and willing to provide a lookup (usually bound to the object).

[2] http://bits.netbeans.org/dev/javadoc/org-netbeans-modules-projectapi/org/netbeans/api/project/Project.html#getProjectDirectory()

Lookup getLookup()

Get any optional abilities of this project.

As we are providing a project, so there are a number of interfaces which one should consider implementing and including in lookup, some of which are described in the related Javadocs. I will discuss only those which I have implemented.

private Lookup lookup =
                Lookups.fixed(new Object[]{
                    this,
                    new MarkupInfo(),
                    new MarkupLogicalView(this),
                    new MarkupProjectOpenedHook(),
                    new MarkupProjectXmlSavedHook()
                });

Twist in the Tale..

Hey, I had just mentioned and as per the Javadocs, we are required to add implementation of some of the recommended abilities, which I would refer to MarkupInfo (implementation of ProjectInformation) and MarkupLogicalView (implementation of LogicalViewProvider).

However, one can also add some instances of classes extending certain abstract classes. In the above case, I would refer to MarkupProjectOpenedHook (subclass of ProjectOpenedHook) and MarkupProjectXmlSavedHook (subclass of ProjectXmlSavedHook) as the abstract classes.

Status: In Progress, Not Yet Usable

Online Resources

There’s a guide which should give developers of NetBeans modules (extensions), a basic idea of how to write new project types for NetBeans 4.x, as well as use certain important parts of the project and build system functionality from other kinds of modules.

NOTE

The reader is assumed to be familiar with the basics of developing NetBeans modules: how to compile Java sources against API-providing modules, make the JAR, write the manifest and XML layer, register services in global lookup, etc.

For background, the reader is encouraged to first look at the general design document which explains how the different pieces of the architecture work together to provide the user functionality.