Do you like fully featured development environments for user interface controls? oneye has always had one, but that’s just hidden in the darkness of our version control system.
That one has been developed by Jose Carlos Norte from the prior eyeos Team, nowadays CTO at eyeos Company. Let’s say it’s been a very good step, but didn’t continue any way sadly.
I personally (!) like to write UI code on my own, but I guess there are a lot around, that’d like to try it. You can now get more information on eyeDesigner and grab the original eyeDesigner installer package from its wiki page.
PS: Just hover the “Downloads” menu entry and take a closer look at translations, eyeSync or what ever you want.
There are two things developers need to care about while developing: Writing code and… backing up the current state of development. This is regularly done using code repositories in the networks (e.g. svn, git or csv). But you might not be as safe as you might think of right now. Let me explain what has happened to me last weekend.
What has happened…
Instead of others I am using a local svn server – just on the same disk as my development repository. Normally this is just fine and I back up things each month, but this month the was some chaos, ’cause of the movement to another city. Everything worked fine and I planned to backup things on Monday. But just on Saturday my MSI notebook just crashed (seems TortoiseSVN did some crazy things…). As every Windows user I just rebootet and… and… and… cry! No more partitions available.
Finally my solution ended in…
Downloading demo of the recovery live cd from www.livecd.com and checking for lost files through the file recovery application. This allowed me to get back files smaller than 65kb. Sadly the oneye 0.9 files aren’t necessarily smaller than 65kb, so I just needed to create a disk image on an external drive.
Later I could download and install Active@ File Recovery (“Standard” costs about 25€) to read such disk images and get back my data.
I am back up…
During the next days I will probably go and create a first video showing some UI elements of oneye 0.9 and maybe even some things in the background. What’d you like to see?
I was glad to see in the forum that there are some people who would like to start developing oneye applications (or maybe even integrate new functions in the OS or fix some bugs), so I want to suggest you the first step to become an oneye developer:
- Download and read the eyeOS 1.x Developer Manual. It’s quite old, so it misses a lot of the new functions available to developers, but it’s extremely useful for a newbie to understand the oneye structure, essential to start programming;
- I strongly suggest you to use the Firefox browser with the Firebug plugin. In order to see the applications error messages directly in Firebug, you have to set the EYEOS_DEBUG_MODE to 3 in /eyeOSxxxxxxx/system/conf/system.xml;
- Start trying to modify the HelloWorld app, included in all oneye releases;
- While you program, never forget to always have a look at the greatest friend of the oneye developer: the eyeOS 1.x Documentation Center. Also, you could find useful the eyeOS 1.x Wiki. Remember that both have not been updated for some releases, so you’re not going to find all the functions…. But you can find the largest part! For the others, while you’ll become a better oneye programmer, you’ll learn to look by yourself into the code to find the functions. TIP: all the widgets are in the /eyeOSxxxxxxx/system/lib/eyeWidgets/widgets folder;
- For question, always use the current oneye Development Forum. Also keep in mind that you can find a lot of useful resources on the old eyeos Development Forum (always check that the question refers to eyeOS 1.x and not eyeOS 2.x, since the latter has a completely different structure).
- If you’re thinking about writing an application starting from zero….please check that there is not another one in the eyeOS 1.x Application Repository. If there is one similar, maybe you can try to improve it, instead of writing one from scratch!
- Hey, all here is open-source….if you manage to write a good application, please publish it on the Repository!
So….have fun writing apps! 🙂
PS = Updating the documentations is a huge work, but it makes life easier for all the developers interested in contributing to the project. If you’d like to help updating it, please reply to this topic on the forum.