I will be happy with whatever form that helps the users quickly identify/understand what a sample does.
Thanks, Raymond From: Simon Laws Sent: Saturday, January 24, 2009 4:20 AM To: [email protected] Subject: Re: Samples structure On Sat, Jan 24, 2009 at 2:17 AM, Luciano Resende <[email protected]> wrote: What are the main issue we are trying to solve with sample folder structure ? I believe that, by having more granular distributions, the amount of samples in a given distribution will be very small, and very aligned with the purpose of the distribution. Also note that in the past, our svn was structured as a folder hierarchy which cause confusion to users and new-developers, hence we moved to a flat module structure. Hi Luciano Let's not get too caught up in the word structure. Maybe I was trying to be too helpful in my previous post by explaining that I had started looking at physical folder structure but had backed that out based on the discussions on this list. However I think that we do need to "structure" the samples so that our users can identify their purpose more easily than is the case with the 1.x release. So let me focus the mind and the conversation a little. What I'm doing is renaming samples to have the following the form... implementation-java-calculator binding-ws-calulator host-webapp-calculator. So that, in my opinion, it's clearer what extension or feature the sample is intended to demonstrate. I am not changing their location in svn. Simon
