shwetapurushe

I have just finished playing around with M. Bostoc's collapsible tree. Here is a link to his original version. This tree has a right to left orientation, and I wanted a top to bottom. He does provide an option for tree orientations here .  Sources showing how to vertically orient it online, showcase a very simple non interactive tree.  SO i just changed his original code a bit, just small x, y tweaks (mainly the diagonal and the node transitions). Quiet simple actually. And this is what it looks like.  Also including the code and the hierarchical JSON object used.  Hope this helps. :)

Note # 2 Purpose of these notes is to serve as personal logs as i continue modifying the Weave Analyst. Weave Analyst Using the Webstorm 10 IDE. Trying to deploy a web application. Webstorm uses its own built-in server port, but I wanted to deploy it to the Tomcat server. Quick fix : move the development folder in Tomcat >> webapps >> Root >> Git updates from this new directory TODO : write build files and deploy to the server. 

Weave Analyst Notes : #1 Purpose of these notes is to serve as personal logs as i continue modifying the Weave Analyst. Weave Analyst ng-if VS ng-show So my angular app was taking longer than i expected it to load yesterday. It was a tiny app, not more than say 50 lines. Turns out i was running into an issue with ng-if. ng-if does something depending on the true or false evaluation of its expression. Turns out ng-if removes or recreates an element from the DOM, and recreates the DOM tree from scratch. Every removal destroys the old scope and every recreation creates a new one. Not good if ng-model and ng-if together are inheriting something from the parent scope. Not good at al!! On the other hand ng-show and ng-hide simply modify the CSS(namely the display property) of the DOM element. The element is never destroyed. Additional documentation :  ng-If

Embedding gist code in Blogger Moski provides a really simple and quick way to do this here.  Awesome.  However I would like to add that the source for his gistLoader. js file gave me problems. It took me forever to understand how to do this right. And if one is new to blogger or not very proficient, things seem to take forever. Ok! Ok! Giving you a quick solution. If you're having problems getting Moski's code to work for you after following all his instructions, try replacing the github source he mentions with another one. So instead o f <script src="https://raw.github.com/moski/gist-Blogger/master/public/gistLoader.js" type="text/javascript"> Use another source like : <script src=" https://s3.amazonaws.com/ moski/gistLoader.js "></script> </div> HTML content of blog should look like this Worked for me. Hope it works for you. 

Started with React finally. :) Just getting hands dirty. Theory and understanding will follow. Main goal of React help develop large apps which handle data that changes continuously over time. Whenever underlying data changes React automatically updates only the specified parts that have changed. Starting with React.render() requires: a single component HTML element or custom component the parent element to mount to optional callback function tried this and it works!!

Updates for the past four days: I explored base64 encoding of strings using Javascript and Java. I wrote code for both using Java on the back end and Javascript for the front end. My ultimate aim was to save a snap shot of a given analysis query as a property in the database and retrieve the snapshots as and when desired to get an idea of what a query looks like. But ultimately part of my package uses Actionscript 3.0 and i ended up doing the string encoding in that. And i store the Base64 string in the database. I dont know if this is the best practice of storing images bur will need to do more research for that. Below is a snapshot of what i achieved. It is a rough prototype and not the final UI.

06/12 and 06/13 I continued working on the Image loading feature for the workstation. I have decided storing images in the database using Base64 encoding.  I spent yesterday testing whether it is better to do the image encoding on the client side or the server side. Decided on generating a string on the client side and sending it over to the server.  Today will be testing server return of image and try to finish full fledged output interface development.