Welcome to JNode.org, the website of the Java New Operating System Design Effort.
JNode is a simple to use & install Java operating system for personal use.
It runs on modern devices.
Any java application will run on it, fast & secure!
JNode is open source and uses the LGPL license.
We had a discussion on IRC about the forum, the documentation and comments.
I just picked a random example. If you have a look at it, many of it is very outdated and even wrong. So what I would like todo is to get the forum cleaned up a bit and for that I do not simply want to decide what to delete and what not.
At the moment if someone complains about the documentation I use to suggest the following: Post a comment with your desired updates to the node. If it gets accepted someone with appropriate permissions will add it to the node and delete the comment.
I would like to have that as a kind of rule.
Additionally I'd propose a simple procedure to delete old content:
Do a reply to the top-most comment you want to delete (and of course all subcomments). Wait one week for at least one other "ok" comment, then delete the comments including the delete-request. If there's a complaint/veto to deleting it, wait a week and delete the delete-request
For forum posts I'd propose basically the same as for comments, just that we move the entire forum post to a archive section (that we'd still have to create..).
Well after all the encouragement from Stephen, Fabien, Isantha, Peter and all others, I have finally set up a sandbox from the latest svn head.
But, i thought before i dive into building the ISO and then tinkering with the source code and bombarding all of you with questions which will make u tear ur hair apart, .... i decided that i will use the latest nightly-build ISO for some more testing ....
I used the 18 July ISO and made the following observations which may/maynot be helpful ....
My approach towards Jnode is more from a user point of view ... the user a beginner java developer must be able to do something with it, that is write and compile Java code using the OS written in JAVA. My VISION is that a person wanting to learn java must do it so on the Operating system written in JAVA.
So in my previous post titled Getting Started seriously i was able to learn how to set classpath and compile a simple text java program. All the errors in setting classpath mentioned in my previous post were solved after i used the latest 18 July ISO. So those bugs seem to be fixed.
I have downloaded and burnt a cd of 0.28 Jnode.
I have two questions.
1. After i boot from the CD, I see that Jnode mounts the partitions with NTFS filesystems on my hard disk containing windows XP automatically.
Are these partitions mounted readonly or read/write?
2. I wrote a small program HelloWorld from windows and save it on to C:\HelloWorld.java.
After i booted into Jnode and then cd /devices/hda0,
I used the command javac HelloWorld.java to compile the program.
It gave me and error.
So i compiled the program from windows and then again i tried to run the program java /devices/hda0/HelloWorld
It said class not fount.
Then i did cd /devices/hda0 and then java HelloWorld
It said exception in command.
How do i compile or run this simple HelloWorld program from Jnode?
How about including JavaDB with Jnode 0.3
It would run in the client server mode, start at the startup and the OS would have a native database.
How about a Jnode--->Accessories--->Addressbook menu entry and the application bundled with Jnode 0.3
Also can we study the feasibility of storing most OS settings in JavaDB instead of flat files like in linux or ini files in windows.
With the in memory database feature, I am sure this would be a very fast way to access all setings and the user interface would be very fast rather.
With 2 GB RAM being a standard nowdays and RAM prices in general falling down, I guess very soon 8-16 GB RAM could be possible on home desktops/laptops and thus caching settings data or any frequently accessed data using in memory database would greatly improve speed of the GUI and the OS as a whole.
would be interesting have the developer's guide in pdf for viewing.