
For the Backbone application I [talked about](https://veerasundar.com/blog/communicating-between-views-in-backbone/) earlier in this blog, I needed a way to organize child views of my main `ApplicationView`. At present, the main view contains three child views: `HeaderView`, `DocumentView` and `SidebarView`.

Initially my approach was to use an array. So, I created a property named `childViews : []` in my `ApplicationView` and added child views as below.

```javascript
createChildViews : function(){
  this.childViews = [];
  this.childViews['header'] = new HeaderView();
  this.childViews['document'] = new DocumentView();
  this.childViews['sidebar'] = new SidebarView();
}
```

This worked well until I tried to iterate the `childViews` array using Underscore's `_.each` method. Both native `Array.forEach()` and `_.each()` failed to iterate through `childViews[]`. Later, when I debugged, I found out that `childViews.length` was returning 0.

That got me puzzled, as I was clearly adding elements to the array, but the code says the array length was zero. Seriously, JS?

After a couple of minutes of Googling, figured out that, in JavaScript, when you add an element to an Array using **named index**, it doesn't affect the length property of that array.

For example, have a look at below code:
```javascript
var myArray = [];
myArray['header'] = 'Element Header';
myArray['document'] = 'Element Document';
alert(myArray.length); // alerts 0
myArray[0] = 'Zeroth element';
alert(myArray.length); // alerts 1
```

As you can see, when we add elements to `myArray` using named indexes, it doesn't affect the array length at all. But, when you add an element using an integer index, the array's length property changes.

So, with that learning, I dumped the arrays and changed my Backbone view code to handle the child views as below:

```javascript
createChildViews : function(){
  this.childViews = {
    header : new HeaderView(),
    doc : new DocumentView(),
    sidebar : new SidebarView()
  };
}

iterateChildViews : function(){
  _.each(this.childViews, function(childView){
    // make sure we are not touching other properties of childViews object.
    if(childView instanceof Backbone.View){
      // Do something with the view.
    }
  }, this);
}
```

With this code, even if I want to access my child views as `this.childViews['header']`, I am still be able to do so. And I could iterate my child views as well. Win!
```


Parent Views and Child views in Backbone


Today I learned a neat trick to organize imports in Eclipse. Of course, one can use **Ctrl Shift O **to remove the unused imports at file level. But what if you want to remove the unused imports for several files, may be at package level?

Simple - in the **Package Explorer** window, right click on the package that you want to modify and then select **source -> Organize Imports **which will analyse all the files inside that package and then remove the unused imports.

One more nifty trick is that you can automatically organize the imports when you save the file. To enable this, go to **Windows -> Preferences -> Java -> Editor -> Save Actions **and then enable **Perform the selected action on save -> Organize imports**. After this, whenever you save a java file, eclipse will remove the unused imports automatically.


Organize imports in Eclipse


Mind Maps are **great**! Repeat, Mind Maps are **very, very great**! Let me show you why.

My work often demands me to switch between several tasks. In any given day, I have to work on several different features, bug fixes and analysis. At first, I was using simple text files to keep things organized. But then as the time goes on, this method proved very in-efficient and time consuming.

So I moved to Mind Maps. I use the free Mind Mapping software [SciPlore MindMapping][1] (I tried [FreeMind][2] too!) to organize my day-to-day notes.

[1]: http://www.sciplore.org/software/sciplore_mindmapping/
[2]: http://freemind.sourceforge.net/

Let me tell How I organize my notes using Mind Map, in the hope that if you are planning to use Mind Map, you'll have some reference to start.

## Starting with the base structure:

Here's how my top level mind map looks like:

![mind mapping structure ][3]As you can see, there are three top level nodes under _Global_:

[3]: https://veerasundar.com/img/2011/03/mind-map-1.png "mind-map-1"

1.  **\*Constants **- \*I use this node to store some static information like, stage URLs, test account names, passwords, etc.
2.  **_Methods _**- This is my knowledge store. I use this node to organize any techniques, or how-to-dos. For example, how to deploy a build on stage, how to remove clearcase views etc.
3.  **_Variables _**- This is the most happening node in this lot. This is my _working space._ This node contains my every day-to-day notes and activity logs. So, lets go further into this node and how I organize this one.

## Organizing the working directory:

![mind-map-working-directory][4]I further split the *Variables *into several team that I'm part of and year (to reduce the clutter) and to Sprints. At work, we follow Agile methodology, so it is very easy for me to organize notes per Sprint. Again for each sprint, I will work on stories as well as bugs. So, I splitted that too.

[4]: https://veerasundar.com/img/2011/03/mind-map-working-directory.png "mind-map-working-directory"

## Not just organizing, but visually prioritizing tasks

Here comes the good part. SciPlore lets me to put some icons next to each node. There are n-number of little icons that I can use to classify a node. For example, if a task is blocked for some reason, then I can assign a RED SIGNAL icon, so that I can immediately recognize the show-stopper if I come back to this task after switching between several tasks. Similarly there are lot more icons there which I can use. Here's a sample classification of one of my Sprint tasks.  
![mind-map-icons][5]

[5]: https://veerasundar.com/img/2011/03/mind-map-icons.png "mind-map-icons"

As you can see above, I have prioritized some stories with the numbers and marked some of them as completed. So, if I just open the stories node, I'll immediately get a picture of what is done and what is yet to be done.

## So, why should you use Mind Maps?

Let me list some of the benefits I get through Mind Maps.

1.  I spend **less time **searching for informations.
2.  I **immediately get to know **what is happening in my project. What's done, what's blocked and what's yet to be done (by means of assigning proper icons). So, at a glance, you get the whole status.
3.  **Visually organizing **rather than copy pasting and using indentation to group things, when compared with text files.
4.  Rather than scattering notes files into multiple folders, I can use a **single mind map **file to store them all.
5.  **Less Clutter **- SciPlore lets me to hide unwanted nodes so that I can focus only on the active task.

So, if you want all the above benefits, you should consider using Mind Maps! It's all up to you. ![:)][6] But, if you are already using Mind Map, I would be really interested to know your story.

[6]: https://veerasundar.com/blog/wp-includes/images/smilies/icon_smile.gif

Feel free to leave a comment about what do you feel about this post!


#organize (3)