What do you find most difficult about JNode

The goal is unclear to me
10% (1 vote)
I cannot find architecture documentation
60% (6 votes)
I don't know where to begin in the sources, it is too big
0% (0 votes)
I would like to contribute, but what is needed
0% (0 votes)
How the boot image build process works
0% (0 votes)
Other (please comment and be specific)
30% (3 votes)
Total votes: 10

More NIC drivers

Submitted by enriquer9 on Wed, 04/13/2005 - 23:26.

I would work more with JNode if I could get it to run on hardware I have, in particular I need the Intel eepro NIC driver. Unfortunately, I am working on other OSS projects and my skillset is not driver development, so I found it too hard to get started writing an eepro NIC. Running JNode emulated was a bit slow and I would be more excited if I could actually test over my LAN.

checking out all sources from CVS

Submitted by Fabien D on Sat, 04/09/2005 - 09:56.

Event under eclipse, it is not easy to extract all sources from CVS.
I did it about 3 times but it was not really easier (but not harder) after the first time.

One of the reasons:
There are many projects : JNode-Core, JNode-Build, ...) but there directory are respectively core, builder, ...
So, under eclipse, we have to do a checkout for each sub project and explicitly specify the appropriate project name (JNode-Core for example).

I tried doing a single checkout on base directory (named jnode on CVS) but it not better.

I think all of this can slowdown and worse discourage some new developers.

What do you think about adding a simple zip archive (with ant libs and a build.xml file, and 2 scripts for linux and windows) to checkout all the sources from CVS ? Then in 3 easy steps we can do the checkout : download archive, extract archive, run the script.

Fabien

Eclipse Howto

Submitted by admin on Mon, 04/11/2005 - 10:35.

I've added an Eclipse Howto page, that describes this process.

In Eclipse 3.1 it is all pretty easy.

Ewout

The plugin mechanism is a little frustrating

Submitted by Fabien D on Wed, 04/06/2005 - 18:16.

Many times I got problems with the plugins.

Under eclipse and any other modern easy IDE, it is easy to do refactoring and automatically add "import" for a class that is in the classpath and that we want to use.

But, all of this don't show the necessity to configure the plugins to add some kind of imports in xml files.

I think of an ant task to automatically (at compile time) check and maybe create/update the xml files to have config files synchronized with the java source.

Fabien

My Option

Submitted by redany on Wed, 04/06/2005 - 11:21.

the bootstrap process regard to which code is currently executing

All of the options are really the obstacle for starting up user, too. So detailing all of the above is very helpful. in addition :
Describing in detail the full bootstrap process accompanied by the outline:which packages/codes involved in the given step. This can help newbies slightly fast to establish the whole structure of the system and to gain the first impression.
It help someone out of hot water when he happen to read unknowable things, which cause him lose his head.(like me in the first experience with jnode)