- Going to work on CELL, SELECTION, TABLE, CONTAINER, Para level functionalities
  > Start with justification/alignment
    LEFT, RIGHT, CENTER, INHERIT PARENT
  > Also font-size, color

- Different context menus for table and para proper handling
 
- undo - redo support
- handle <br> and <div> in table cells and in text
- Proper width scaling in PDF
- Load JSON file and make proper text/table sections

- font size support per cell / table / container levels
- foreground/background support per cell / selection 
- multiple cell selection for coloring, fontsize


LOW PRIORITY
- cursor key movement natural, made some conceptual example in arrow_tab_control
  > will handle later -- low priority
- should be able to justify left/right/center a column

=================================================================================
BIG CHALLENGES
- resize columns based on zoom of browser and parent
- column resizing for merged cells (finally fixed by a top row with max columns)
  > was too hard to get fixed
- Merge related issues. Problems with insert/delete row/col
- Not much expertise in javascript


10 RULES OF PROGRAMMING
- Great code produces magical functionalites. It does the right thing 
  Even if you did not think about it earlier.
  Or suggests adding great functionalities
- Code should always be working
  previous functionalities retained as you develop new ones
- If your code does not look like english -- think ???
- If you can't get a task completed in 15 min, there is some issue --- think ???
- Don't write code -- as little as possible
  The more code you write, the more bugs you will introduce
  If you are writing more than 10-15 lines to achieve a functionality -- think ???
- No function more than screen height
- Divide code into files/functions. Try having hierarchy in code structure.
  > High level functionalities zooming to detail levels.
- You are responsible for bugs in code not QA
- Getting a bug in code should not be taken lightly by you
  First nature is to give excuses -- Take responsibility, fix IMMEDIATELY
  Don't assume, your code has to have bugs
  If QA reports bugs, get it fixed ASAP
  If you are spending time on fixing bug, you did not write code properly
  Or have a better explanation
  When you complete a functionality, test. Think where it can fail
  You should be able to bet your neck on code you have written
  Getting a bug in your code should be taken very seriously
- SUPER programmers are 10x programmers
- SUPER programmers should have the capability to think while development also
  > Programming should not require too much tension
    If you are getting tired during programming, you don't know how to program
    Or you don't have reasonable command over language
  > Just like you drive a bicycle or speak.
  > Thinking about specs should be major part, code writing secondary 80:20
  > After all, you are just going to write 10 lines
- It is ok for junior programmers to follow orders / specs as is.
- Senior programmers should challenge specs and get specs modified if issues in specs
  > Programmer is in the trench, he needs to understand the usage why it is done
    and should suggest improvements
- Try to achieve something significant in a day

Summary:
- Write as little code as possible
- Write code in English 
- Small functions - Divide into files/directories
- Progress every 15 min
- Bug in code -- you didn't think deep enough. Did not test it
- 

javascript based resizer: http://jsfiddle.net/3jMQD/
=================================================================================
git log | grep "   " > out.txt
tac out.txt 


   















SPECIFICATIONS:
=================================================================================
Problem Statement:
Make a section which supports adding TEXT/PARA as well as TABLES. Standard editing features of TEXT / TABLES are expected.

DETAILS:

BROWSER RESIZING
- browser resizing should not disturb layout
- mixture of browser and container resizing should not disturb

MULTIPLE RESOLUTION SUPPORT
- Tables/Paras should stay same for multiple computer resolutions

RESIZING CONTAINER
- resizing parent container should not disturb layout

ADDING TABLE
- Ability to add a table (rows x columns)
  > distribute columns equally in 100% of parent
  > All properties should be maintained on loading

DELETING TABLE
- Delete current table

ADD TEXT/PARA SECTION
- Add text/para section
- Add text section before table
- Add text section after table

RESIZING COLUMNS SUPPORT
- A intuitive way of resizing columns should be present

ADDING COLUMNS/ROWS
- Ability to add a column above/below
- Ability to add a row above/below

DELETING ROWS/COLUMNS
- Ability to delete column
- Expand to full width remaining (if full width)
- Ability to delete row

CELL MERGING
- The cell next to current one will be merged with current
- If next cell has longer span, take that into consideration  

CELL SPLIT
- If cell is merged, we should be able to split it
- Should not split if already column span is 1

SAVE/LOAD FUNCTIONALITY
- Should be independent of resolution/zooming
- Should support save on one computer resolution and load on another
- all resized columns / other layout should stay same

TABLE LEVEL FORMATTING
- alignment of all cells
- horizontal alignment of table
- fontsize of entire table

CELL FORMATTING
- Set foreground color of text in cell/selected cells
- Set background color cell/selected cells
- decrease/increase font size in a cell
- Italic Bold, etc. 

MULTIPLE SELECTION OF CELLS
- for fontsize change
- Justification
- coloring

ENTIRE CONTAINER FORMAT
- Base font size increase/decrease support
- Set basefontsize

USER EXPERIENCE
- Natural cursor movement via arrow keys and tabs - A Bit harder in contenteditable
- Right click submenu for different commands

CONVERT DATA FROM ALL ABOVE FEATURES TO PROPER PDF
- Rewrite html-table parsing code to support all of above
  Support all above features - most of above carry to backend

FORMATTING SUPPORT AT APPROPRIATE LEVELS
- Cell, Selection, Table, Container, para

CONTEXT-SENSITIVE MENU
- Para and Table level context menus

UNDO REDO SUPPORT
- ......

- ADD SUPPORT FOR RADIO BUTTONS

- ADD SUPPORT FOR DROPDOWN

- ADD SUPPORT FOR CHECKBOX


ADD DOCUMENTATION FOR FRONT AND BACKEND

LEARN JAVASCRIPT/CSS ALONG TO MANAGE REQUIREMENTS ABOVE
=================================================================
ARCHITECTURAL SPECIFICATIONS

- MasterController should control the main div which can have
  multiple types of view types (table, para, graph, ...)
- TableController should control all tables, and ...
- BaseController should have common functionality

=================================================================
May 13th
3:50PM Going to fix load save issue for changed resolution
       Going to save the container width during save process
       And going to scale the table columns on load process

4:15PM Going to start on Merge issue, 
       first going to think about strategy/specs more closely.

	   - Will allow for merge in top row only
	   - will merge the next cell with current cell
	   - May allow selected cells to be merged - Later
	   - The distribution of cells below merged cells would divide equally
	   - First start off by deleting the next cell
	   - merging cells worked, but resizing is broken.
	   - previously was using CSS resizing, now have to look into javascript resizing
	     so that I have better control. But, I do suspect that might run into same
	     problem. If I run into same problem, then will have to implement table myself probably

7:40PM
	Implemented a new strategy for resizing with merging
	Added a top thin row for resizing, now javascript not needed again.
	This one was hard to overcome, took like 1 hour to find solution.
	This is an example, where I was stuck due to "table" not properly supporing width stuff
	for tables with colspan.


8:30PM: After dinner, started testing. Found an issue with insert column if cells merged. 
        Not fixing it for the time bing.

        Continued testing - can't leave it for QA to find issues, I am the developer
                            and I am responsible for reliability of codes.

        Merging is a relatively complex thing to handle after merging
        	previous functionality has issues.

11:15PM:
	Have done signficiant implementation: 
		Delete row/col, 
		A context menu,
		color filling

May 14th.
12:15AM.  Need to fix the bugs so that can shift to PDF.

3:20AM. Fixed the bug of merge cells.

4:07AM. Decrease, increase fontsize implemented.
	
May 16th.
8:05 Resume work.