I agree that a browser and a shell would be good, but the current browser doesn't use the API at all. It's completely separate and therefore not a sample for API features. But I'm fine with keeping it inside OpenCMIS. It's a handy tools sometimes.
@Nuxeo: Are you going to port your shell implementation to the OpenCMIS client API? Florian -----Original Message----- From: David Caruana [mailto:[email protected]] Sent: Dienstag, 4. Mai 2010 15:44 To: [email protected] Subject: Re: OpenCMIS Browser I'm not too keen on a misc project - other projects have a sandbox area for experimentation. Re: the browser, I do think it would be good to include an "official" browser as part of the OpenCMIS sub-project. I would also include the shell too. The reasons for this are: * ties the browser and shell to the opencmis release schedule * the browser and shell focus on breadth * the browser and shell act as samples for all api features * ... Dave On 4 May 2010, at 12:09, Klevenz, Stephan wrote: > Hi, > > What about to have a sub project "misc" for miscellaneous that can be used > for tools, utils, demo, proof of concept ... stuff? The sub project "misc" is > never intended to be released and will get limited support. I don't know if > this fits to Apache rules or is a common practice to keep such things like > OpenCMIS Browser. > > Regards, > Stephan > > BTW: This browser is useful and I am using it quite often. > > -----Original Message----- > From: Florian Müller [mailto:[email protected]] > Sent: Dienstag, 4. Mai 2010 12:52 > To: [email protected] > Subject: OpenCMIS Browser > > Hi, > > Do you have any opinions on where the OpenCMIS Browser should end up? > Currently, it is a module of OpenCMIS but it doesn't have any dependency on > the client or the server. Should we remove it from OpenCMIS and make it a > separate subproject of Chemistry? > > > Florian
