My latest project
-
Thought I'd share my latest project here to get some feedback. It's for visualizing how wikipedia articles are connected.
Explanation here: https://github.com/The-Penultimate-Defenestrator/wikipedia-map
And it's live and working here: http://luke.deentaylor.com/wikipedia/Please visit on a desktop browser, it's horrendous on mobile.
-
@Webmaster4o , nice. I have not had a chance to try it yet. Internet for the last 3 days for me has been so bad you can't believe. Multiple providers. Never mind.
But I did see it in my flipboard feed today, was from your Twitter post. But it still felt like you had been published. Nice.
I look fwd to view it when I have some bandwidth. I tried a few times in the browser, but gave up. But genuinely interested
-
I rewrote this recently to use the MediaWiki API instead of dynamically loading the full HTML for Wikipedia pages, which was actually illegal. It's also faster, and now the Python code is all PEP8 compliant (@ccc :) )
-
The "Back" button overlaps the text in the about and controls sections as shown here. I'm pretty sure it shouldn't be this way :) Also it would be nicer to position the text in the said button at the same level as the arrow. But overall, looks great!
EDIT: Better :p
-
Position the text in the button at the same level of the text
Could you elaborate on this? What do you mean?
-
So smth like this instead of this (Awfully sorry for my horrible Paint skills :D)
EDIT: Oh, I'm sorry. I wrote total nonsense in the previous message and didn't even notice)
-
@Leva7 Right. I think I meant for it to be like that, but CSS didn't like me. I'll try to fix both of these later when I have less homework. Thanks for the feedback :)
-
@Webmaster4o , just to scare yourself. Put on a marketing hat and look at some products. Or another hat for any other specific item one might want to research in business. All I am saying is maybe you are on to something here. Is a great idea. Maybe others have done it, I don't know. But combined with other information in my mind could be a great tool. Also same concept applied to other datasets.
For my crappy advise, I would say pull it off everywhere. Try to see if you have the start of something revolutionary. Maybe not. As I say, I am not sure. But maybe you are a little egar to share. I am not thinking about code, more the ideaMy 2 cents worth
-
@Phuket2 The mapping part itself is not much of my work. I've written the code that binds the click events and adds the other nodes, as well as the code that queries the wikipedia API, but I haven't written the visualization code, that's from vis.js. My use of this is unique, but the algorithms for physics and layout and such are not original. If you look through the code for about 10 minutes, you can read the comments and see exactly what I've implemented, and what is not mine.
-
Nuther thing I found. When pressing the "random" button, it displays correct, readable text under the node and in the text input window the special chars are replaced with %. However, on the press of the "Go" button, the text under the node also changes to the % format.
-
@Leva7 Right, sorry. This is just an inconsistency. In the background, all special characters are transmitted with percent codes. This is because you can't put non-ascii characters through a URL. It also helps with handling unicode on the Python side of things. The labels are automatically converted under the nodes, but I forgot to do it for the text box. Thanks :)
-
@Webmaster4o , I understand. It's so hard to say in a few words. But just because something is there already, does not mean it has been leveraged. Anyway, I just say to open your mind up to maybe you are on to something. And while all the elements are already there maybe maybe they have not been visualized the way you have or could have.
Coding is great, but understanding business and their needs is basically wood for the coder in a way
-
@Leva7 I fixed this second thing with the random button. The first issue was that I wasn't using the JavaScript function
decodeURI
on the text box input. The second was that I was usingdecodeURI
instead ofdecodeURIComponent
, which I didn't know were different, but now I see that they are.
-
Did you update the changes? To me, the issue is still there
-
@Leva7 The issue with the random button is fixed for me. It's not pushed to github yet, though. Try refreshing the page.
-
Yeah, now it's all good. Here is a slight aesthetic issue (text overlapping the node), but honestly I don't think it's something worth editing the code. if it's an easy fix, move the text a bit down. If it's not, just let it be)
-
@Leva7 Yeah, that'd have to be a change in vis.js, I think. I don't really have control over that beyond filing an issue on the vis.js repo. Thanks anyway.