> Hmm, may be it is too late already, but I do not quite understand your idea. > So let me try to express it in my words: > > (1) The DevGuide, in particular with respect to presenting only code snippets > in Java, should remain as it is. > +1
> (2) Boxes with code snippets in the DevGuide should have a link to the one(!) > main examples page. So, starting from a code snippet in the DevGuide I click > one link to get to the main examples page. > +1 > (3) The main examples page contains a list of all examples available. On this > page I can click on another link to get to another page that discusses the > particular example in Java (or any other language) which contains the code > snippet from (1), where I started. (One page for every example or even one > page for every example _and_ every language?) From this page, I can again > navigate to other pages, giving me particulars about the project files for NB > or Eclipse or, ... On these pages I might also find links to download the > project files for the particular example for the respective IDE. > > If this is what you mean, where do I find the code? My idea was to start from > (1) and find a link to a page where I can read the code on-line. A very good > example about what I have in mind is [1]. > > When I learn something like UNO I don't have to build and run every example. > Very often it is enough to just read the code. So it would be great if I > could read it by just clicking some links -- refer to [1] again. > +1 > It would be cumbersome, if I had to download the example and install the > project in an IDE in order to just read the code. Even worse, what if I don't > use NB, and don't want to use it? If the examples are available only as NB > projects, chances are high, that I will not only get frustrated, but that I > will loose interest. > +1 ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
