> >2) The fact that this debate has gone on for so long indicates that > > there > >obviously needs to be a clearer definition of what OpenBeOS R1 is > > aiming > >for... Is it to be an opensource implementation of BeOS R5, an > > opensource > >implementation of Dan0, or are we aiming for something more? > > This will be an endless debate. I think we shouldn't waste time in > debating about little extra features on existing applications. What I know and read on the OBOS-site is that OBOS should be the same as R5. This with some improvements ;). So we should keep on that. > > We all know we programmers like to put an extra features in an > application, but we should be aware that we may not do this all the time. Otherwise the release of R1 would take longer than normal. As long as the improvements are small and not that "new", we should not complain. Keep programming the things that should be programmed first. In R2 you will have the freedom to extend some applications with new features ;) Michael Phipps has set guidelines for features. Unless I don't remember correctly, R1 is to be an implementation of BeOS R5 with fixes for bugs in R5. Developers are permitted to add minor features provided that it does not take away from implementing the app and/or it is a useful feature which is a trifle to add. There are _no_ changes to public API. An example of all this would be the decorators which will be possible in R1 - they're a feature inherent in how the app_server has been designed. My *personal* opinion is that the extra features added to ShowImage are reasonable - simple features which are quite useful. However, I also think that adding anything else would be well above and beyond what one would expect a simple image viewer to do. --DarkWyrm