> honestly spoken, this is not the best strategy for everyone... Obviously. But we have limited resources (no-one is paid for working on Wicket), so it is hard to cater to everyone. We have tried to attract writers (for a reference guide) from the very early start (even offered some money) but it just doesn't seem to be a task many people seem to be interested in doing.
> moreover, > I think you are speaking of examples coming with the download; this > dowload was again rather confusing (see my site problem); I am looking > first at the exampleson the website, and there I could not find any of > the examples you were mentioning. What I don't get - as a regular user of open source software - what is so difficult about just getting it from source control or creating a quick maven based project for that? I typically dive into several projects I didn't know before a month, and I just start with getting it from the repo, looking at the test cases and examples and Javadocs (which unfortunately is something most open source projects do a lot worse at than Wicket). > btw. this is I see now one of the real issues with the wicket docs; it > seems, that there is actually lot available, but very cluttered, not > properly linked and partly redundant in different versions... We really depend on our users helping us out with that (and they have been quite a help already). The framework is in constant development, so this is something that needs constant attention. Help is very welcome. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
