Description: Visualization of WordNet using Force-Directed Graphs.
Features - Presentation of words and meanings as graph nodes, and relations as edges between them - Visualization is interactive allowing moving nodes around - Autocomplete of words - Customization of visualization elements - Audio Pronunciation of words.
version 0.2: - Improved layouting algorithm based on TGLayout from touchgraph.com - Audio pronunciation using sound files from various websites (requires Internet connection). -Displaying arrows for is-a relationships. - Coloring widgets that show meanings in the same color as meaning nodes on the scene.
version 0.1.1 - SQLite version of mysql wordnet (http://sourceforge.net/project/showfiles.php?group_id=135112&package_id=219735) database is used instead of native C interface.
Hi,
I try to recompile your project with QT 4.5.2...
I have succeded but I have a problem when typing a word and click on the button or type enter to search for it, the program blocks (not all the time) but for example with words like \'blood\' \'tearing\'...
Do you have an idea where I could search ?
Hello! First, your application is very good.
My question: where i can find some documents so i can start to do my own implementation of TGLayout algorithm to use inside my application?
Thanks.
Ratings & Comments
3 Comments
Hi, I try to recompile your project with QT 4.5.2... I have succeded but I have a problem when typing a word and click on the button or type enter to search for it, the program blocks (not all the time) but for example with words like \'blood\' \'tearing\'... Do you have an idea where I could search ?
Hello! First, your application is very good. My question: where i can find some documents so i can start to do my own implementation of TGLayout algorithm to use inside my application? Thanks.
The algorithms I used are of the family of Force-Directed algorithms http://en.wikipedia.org/wiki/Force-based_algorithms. TGLayout from http://sourceforge.net/projects/touchgraph is also a Force-Directed algorithm. TGLayout was performing better (faster), then my first implementation, so I adapted it to my project.