The client sends a string to the server which than 1337ifies the string and sends it back. My implementation consists of a server and a client.
#Ejabberd sucks code#
I put the word small in quotation marks, because NIO blows up the code by a factor of at least 5. Speaking of tests – I created a “small” test app that utilizes NIO for non-blocking IO operations. I fixed the issue by replacing the ArrayList with a LinkedHashSet. This failed under certain circumstances (in my universities network) due to the properties of the set. Basically there were simultaneous insertions into an ArrayList and a HashSet with a subsequent comparison.
While testing, I found a small bug in the SOCKS5 Proxy tests of Smack. I hope to keep the code coverage of Smack at least on a constant level – already it dropped a little bit with my commits getting merged, but I’m working on correcting that again. Tests are tedious, but the results are worth the effort. Other than that integration test, I also worked on creating more junit tests for my Jingle classes and found some more bugs that way. Previously I had the issue, that the transfer was started as a new thread, which was then out of scope, so that the test had no way to tell if and when the transfer succeeded. This allowed me to bring the first integration test for basic Jingle File transfer to life.
Most functionality is yet to be implemented, but at least getting notified when the transfer has ended already works. Most notably I created a class FileTransferHandler, which the client can use to control the file transfer and get some information on its status etc. I than took some inspiration from the SI code to improve my Jingle implementation. I read the existing StreamInitialization code and found some typos which I fixed. This week I made some more progress working on the file transfer code. Message me or something if you ever want to talk.Time is flying by. Don’t take this the wrong way, you’re just annoying me more than you’re making me happy knowing about your life by having you on Facebook. So what am I going to do? Pretty simple and to the point, if your constant updates and feeds annoy me, I’m going to politely remove you off my Facebook profile. I could turn off all this sort of stuff by filtering most of it out, but, then again, (1) I can not be bothered setting up this stuff for every annoying feed type, and (2) I really do not care about this stuff (and most of the time, the people behind this stuff). I dont know who just played poker, I dont know who went to I dont know what event, someone just got bitten-axed-limbs-torn-up by I dont know who… That’s just silly. So whats the deal with people on Facebook having 65543 friends and whatnot? Well maybe not that much, but still, having a lot of friends.I have 61 friends, and I’m overwhelmed with all sorts of annoying feeds here and there and every-effin-where. The next major hurdle to jump over is going to be zooming in and out pretty fast (a problem that might be solved using mipmaps, but might require OpenGL, something I’m trying to avoid).UPDATE: Video here. Some of the major challenges at this point are being able to handle the vast amount of data thrown at the application, scrolling it around, loading / unloading images, etc. Right now, I’ve implemented the kinetic panning area, an LRU multi-layered cache system for the images, and the (huge) image grid widget that will hold those thousands and thousands of images. You can then zoom in and out, and pan around, until you find your target image, at which point you can pick it up and use it. So, naturally, you’d go to the blue area, use your mouse wheel to start zooming in and out, and “throw” the images around (using a kinetic energy panning approach) until you start finding something that resembles the image you’re looking for.
The end result is a big map of all your images, zoomed out, such that every corner of the image represents a color, and the closer you move from one corner to another, you see the colors converging into a gradient. How can you go about looking for it? You fire up Finder, let it loose on your system, and ask it to cluster images by color. Say you want to find an image on your system you know its mainly blue (of some sky), but you don’t remember its name, size, location, or when you got it. For lack of a better name, it’s called Finder for now. I’ve been working on a new concept for an image viewing / searching application.
0 kommentar(er)
