A lot of friends asked me recently to teach a little programming to their children. After a few occasions I've decided to start a video series on youtube about programming - for kids. I proudly present the first two episodes.
Do you have a super silent MacBook and sometimes you have no idea whether it is working or not? Or you just interested what tasks MacOS does in the background? Or you are a developer and you need to see what your application is doing in the background? MacOS Activity Indicator puts an icon in your menubar that switches it's led between green and red when activity happens. If you click on the icon a window appears where you can see the last 100 files touched by the operating system.
What's new in version 1.2 :
In addition to the OAPKA update I have released a new mac app called MacOS Activity Indicator.
It started with fswatch. It's a super handy command line utility installable with brew ( brew install fswatch ), you simply type "fswatch /" into the terminal and no file activity remains hidden on your computer. You can see what nasty things MacOS and any other app are doing in the background. I use it to generate header files for my c files automagically no matter where they are.
Then I realized that I can create a menu bar activity indicator for slow and silent machines - like the new MacBook - because sometimes they seem to be unresponsive and you don't know what is happening. As a plus, I've added an observation window - you can open/close it by clicking on the menu bar icon - that shows the last 100 changed files.
I've decided to add no filtering or external app option - it's just a comfy indicator/quick check app - if you want to do serious work then use fswatch instead.
The app is open source in the pulbic domain as always :
What's new in version 1.2 :
Do you use an optical audio cable or HDMI to connect your mac and your amplifier? Do you experience one second silences in high fidelity music, lost words and lost sounds in movies? Well, it's not your nor your hardware's fault - it's an energy saving feature of these audio interfaces. And Audio Keepalive is the solution for you!!!
The app generates an absolutely unhearable tone that prevents your audio output to shut down at short silences/musical breaks, so you can enjoy an uninterrupted hi-fi audio stream.
Audio Keepalive is a menu bar application. Just click on the menu bar icon and select "Quit" to quit.
"Works as advertised and the tone is really un-hearable (tested it on my headphones and speakers at full volume)." 5/5, Poland
In the past year I've created a few very nice wrappers for different platforms and operating systems that wrap the same controller file to simplify multi-platform C development for my stuff. For your edification and pleasure they are now yours on github!
TMMCP is a wrapper/project collection for C programmers who like it quick & simple & with total control. A TMMCP wrapper provides:
The wrappers are very simple, after a little reading you can easily extend them if you need some special functionality.
Everything in this repo is in the public domain. Take it use it learn from it.
Open "template/sources/controller.c" in your favorite editor and start coding. After you finished open the wanted platform's project file and build/compile/run/deploy. You may have to add newly created source files / include paths to the project settings.
The documentation is in-line in controller.c. If you don't get it check out the demo projects. demo_dragbox shows a draggable white box over a purple background - it shows off basic OpenGL/input handling and audio playing. demo_conference is an advanced demo, it creates a 3D conference room with video avatars using the wrapper's render video-to-texture functionality - even in html5!. But not on android, I'm still in the middle of the implementation, it will show blank avatars.
Windows and Linux wrappers/projects would be awesome for start but any platform is welcomed warmly!
I'm using some stuff in the demos from these beautiful people :
Check it out under https://github.com/milgra/tmmcp
I'm working on a multi-platform C and OpenGL based UI renderer and displaying things in 60 fps is essential.
It works well on desktop and mobile OS's and it looks good in WebGL on my non-retina Macbook Air but sadly on retina Macbook Pro's the framerate is dying in case of big browser windows ( ~more than 50% of the screen ).
After a few days of trial and research I figured out the following :
So what did I learn?
Anyway I rewrote my UI renderer to use as few function calls as possible, use as much glTexSubImage2D and glBufferSubData calls as possible instead of full uploads and now it uses bitmaps for text fields instead of individual textured quads for letters and I'm almost satisfied.
So you just take previously written C/OPENGL games/prototypes and you compile them for the BROWSER!!! It's madness!
I don't have the nerve for web programming, for tons of DOM elements and css, for different js vm implementations, for debugging hell and everything else modern web "gave" me as a developer. And now I don't have to deal with all these things, and still I can deploy for the browser!!! ( okay, I have to deal with them a little because it still is web development, but hey, I only need hours now to fix something strange, not days!!! )
IMHO Emscripten is the best technology of the 2010's so far.
Last week I badly wanted to see my face as a voxel cloud on the screen so I entered the 3D scanning territory. There are two ways for a mid-class person to do it in an affordable way : reconstruction from photo series or triangulation based on a laser line. The first method is quite inaccurate and needs complex algorithms ( Autodesk123D is the biggest free solution, ), the seconds one is dead simple, accurate but it is very hard to add texture data. So I chose the latter. It needs only two things : a line laser and my mobile's camera.
So I went to the local home improvement store and bought a Bosch Quigo laser level, set up a simple scene and started coding.
The theory : you know the distance between the laser emitter and the camera lens focus point, you know the angle between the laser and the camera axis and you also know the field of view of the camera. From these data you can link an angle to every pixel of an image created by the camera, and from that angle you can tell the distance from the camera.
The red line is the laser, the blue line is the camera axis. d1 is the distance between them, it is set by you. a1 is the angle of the camera axis, it is also set by you. The black line is the line between the camera and the touch point of the laser on an object. The yellow line is the projection plane of the camera, the green lines are the field of view of the camera. The field of view is also known, you can check it up at your phones vendor or calculate it based on the focus length and sensor size ( in case of my iPhone 6s they are 4.15mm and 4.5mm so the focal angle is atan( ( 4.5/2.0 ) / 4.15 ) * 2 so roughly 56 degrees when you hold it horizontally ) or put down a one meter width something on the ground and take a picture of it from 2 meters away and do the math based on the image.
So the point is that the black line will have a corresponding pixel on the image, you know angle a2 ( which is the field of view divided by two ) so you can calculate angle a3 since they have a linear correlation to the pixel count. So ( image width / 2 ) / ( FOV / 2 ) = ( black dot pixel distance from center / wanted angle ). And after you have angle a3 you know the angle between the red line and the black line and a cosine function will give you the length of the black line : cos(angle) = d1/ wanted length.
This is my actual state, check it out here.
The next steps will be to make it freely movable, and possibly transforming the actual scan based on the motion sensor data to get a full scan of anything. Yaaay.
I've been learning to wheelie for 6 months now. I always wanted to do it but never took it too seriously before.
I started with my bicycle. It's a nice trek 7.3 with a massive frame, very easy to pull up the front in the first gear. After a few weeks I could do 4-5 meters so it felt the right time to switch to the motorbike.
I have a quite used KTM 640 LC4 used by an experienced supermoto biker before.
I bought it in this state on purpose because I didn't have the heart to hurt my previous shiny DRZ 400. Having it for two years now I have to say it is far superior to the DRZ in every aspect IMHO.
I watched a few videos on youtube about wheelieing and decided to start practicing on an uphill.
The best uphill around Szeged with a decent surface is in the Oil Fields of Algyő, Hungary's biggest and only oil field with a lot of service roads, it's a paradise for cyclist and bikers in the summer. There are a few overpasses over the M40 highway, the one with the less traffic is the closest one to the Tisza Bridge.
So I started there in May. It is super frightening. Your body is prepared to fall back and jump off and it's pretty hard at the beginning to force your hands to throw the clutch out. ( after a few near-fallback experiences ).
I pulled too small throttle at the beginning and the engine always stopped. Then I pulled too much and had to jump off the bike. Surprisingly the motorbike never fell over, I could always keep it standing ( I have quite long hands ) but it stayed standing on it's tail a lot of times ( thanks to the genius of the KTM frame engineers, they prepared the bike for clowns like me :) ). The rear lamp immediately broke off and also the frame for the license plate.
After a month and hitting the first wheel a lot of times to the road ( which kills the wheel and the steering bearing quite quickly ) I realized that I have to use much more throttle and I have to fine tune the whole process with the clutch so I can control the wheel height much easier.
So from month to month pulling up the first wheel became more and more controlled. The first milestone came after three months. I was still in the same fear every time I started to practice and I got fed up with it, I decided to force calmness to myself, don't think about anything and to stay in the moment. And it worked. I could do 4-5 meters in balance position and I realized what did I do wrong before : my head was moving together with the bike, I was staring at the handlebars and didn't have a fix balancing point. The solution is to watch the horizon all the time so the head stays in a fix horizontal position and your balancing improves big time.
After I carved the horizon staring in my brain things went much-much smoother, after a month I mastered the clutch and gas handling, I could pull up the wheel in any height I wanted. But I couldn't go more than 4-5 meters, so the balancing/balance position is the next step.
The next milestone came last weekend when I felt that I can finally put my legs up on the footpegs and keep the right on the brakes for safety, because in the previous five months I did it with the legs down on the road and helping balancing by pushing up myself and the bike with me. It went quite easy, it wasn't frightening any more, from the previous experiences I could handle the balance point quite well and emergency braking with the right leg works quite well. But the wheeling distance was the same, I couldn't keep the balance point. And then I calmed myself again, stayed in the moment and realized that while I'm looking at the horizon I can improve balancing by pushing my upper body closer to and farther from the steering bars so I can keep the bike vertical much longer. Sometimes I do 8-10 meters with this technique, it's very exciting.
So that's where I am now and I won't leave the path to a succesful infinite wheelie! :)