From: Gillian W. <gil...@at...> - 2004-11-05 16:45:26
|
Hi, I think that's an excellent idea, and probably necessary if we want openev to move forward rather than sideways in many different directions. I'm not sure yet how much time I could commit, but I should be able to find at least an hour or two a week. I don't know if that would be enough to be useful for what you have in mind though. Was the 6-month time frame a random choice, or do you have a particular reason for it (eg. a conference to present it at)? Do you have any funding mechanisms in mind or were you seeing this more as a consolidation of many people doing little bits consistently on their own time? If it is the latter, I suggest we focus mainly on design and what we would like to use openev for, then write the new application once those ideas are in place. I like the wiki documentation idea. If we develop a common idea of what openev should contain in the future and agree on how it should be implemented from a user perspective, then people can do the actual development in contracts/projects where they make sense. I wonder if it would be worthwhile to throw this out to the gdal-dev list and see if anyone from other projects (ossim, vtp, etc.) is interested in providing some suggestions. Gillian Paul Spencer wrote: > All, > > as you may be aware, there is a perception out there that OpenEV is > somewhat unfriendly to users. I think this is primarily because new > users think that the OpenEV front end is the full application rather > than a demonstration of how the OpenEV toolkit can be used to build an > application. At least, that's my understanding of OpenEV (perhaps > because that's how I use it ;)) > > If this is the case, I think OpenEV is suffering from a case of 'bad > press' because the user interface is not really intended to make it > friendly to people who don't know how to use it. It is, instead, > functional for those that know how to use it. > > I would like to champion a project to build a new OpenEV application > that would become the default that new users would see. By > 'champion', I am thinking more of getting it organized than of doing > all the work myself ;) > > To this end, I would like to solicit comments about this idea and > suggestions on how we should organize such an effort. If the idea is > not entirely shot down, then I would suggest that we move on to gather > some requirements for the user interface and functionality to be > included. The final phase would then be actually coding up the new > application, which in my experience would be a lot of cut and paste > from existing code rather than a lot of new development. > > Obviously I can't do this all by myself in this timeframe and would > hope to have some contributions from the main developers and other > openev users for all sorts of tasks, including: > > * requirements > * design > * coding > * documentation > * testing > * packaging > * art work (seriously, the current graphics are somewhat old-fashioned) > > I have a tentative timeline of 6 months in mind, from this email to a > formal announcement of a releaseable version of the interface. I'll > need some idea of who can commit to helping out within this timeframe. > > Comments and suggestions welcome (even suggestions that this is not > needed are ok :)) > > Cheers, > > Paul > > BTW I am thinking of finding or setting up a 'wiki' somewhere that we > can use for developing requirements and design. Any suggestions? I > can probably get one set up on MapTools if there is no other more > suitable spot ... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Openev-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openev-discuss |