Dirk Reiners wrote: > Hi Allen, > >Allen Bierbaum wrote: > > >>It is that place where FlexLexer.h is still included directly in the >>file that is not autogenerated. I just need to know if we can change >>the file to point at the FlexLexer that we copy into the source tree. >> >> >> >Ah! The problem with is that it will break the configure build, that's >why I haven;t committed it. I was waiting for you to test it and tell me >that it works and then we could make the move to scons. Did you try it? > > I will give it a try today. I think it should work. I think it may actually still work with configure as long as we check in the file.
>>These sound more like tutorials to me. I guess what I want for examples >>may be closer to demos then what you want. I would like to see examples >>that show how to use the code in the realworld and can show off the >>capabilities of why you would want to use this feature. I don't think >>that pulls along that much extra code. >> >> >> >Real world is a vague concept (some even argue whether it exists at all >;). I see examples as less extensively documented tutorials. My goal >would be for features to be simple enough to use that you can put them >on a screen of code (roughly), so example programs shouldn't be much >longer than that. I don't think that's going to need a lot of code >either, but I would see it as a goal to make it minimal, so that we can >just include the example code in the docs. > > What do you think about using them as demos? To me it is key to the future success of OpenSG to create demonstrations of OpenSG capabilities that can be used to promote the system. When you say "goal to make it minimal" it makes me worry that we won't actually show the capabilities of OpenSG with these examples. If we can't use them to show off OpenSG then I don't think we have really succeeded. >I see example apps as a starting point for people who want to write >their own apps, sort of a cut-n-paste source. That's what I initially >wanted the SceneViewer for, but it didn' get enough care to grow into >that. I would be interested in having something like it based on >different GUI toolkits, explicitly for people to use as a starting point >for their own apps. > > Understood. I don't see this as absolutely requiring overly simplistic applications though. I would rather see how the code is used to really accomplish something then just see and small method that calls some functions in the API. If we only do that, then we are just back at having test applications aren't we? >It sounds like you want a mixture, where you have an actual app that >uses a specific feature. I'd prefer splitting that and keep them >separate. If need be we could come up with some simple plugin scheme for >the skeleton app and write the examples in a way that makes them pluggable. > > I would be interested in hearing your ideas here. To be clear though, I am not proposing a complex application. I just want something that really shows off the feature and shows people how to use it in non-trivial ways. >>As far as "I don't want to have to wade through tons of code to find out >>how", I don't either. I want to look at the documentation for the class >>and see it described right there. :) >> >> >> >Me too, but I don't want to write (and update) the example code twice, >so it better be short and sweet to not clutter the docs. :) > > So you want to pull the examples inline into the class docs? Or could we just do something like Qt where we refer to the full applications. Doxygen would even let use have the code for that full application example be syntax highlighted with links back to the documentation of the classes and methods being used. I guess I would rather see full examples that show how to fully use the system, then see trivial examples that still sound like tutorials to me. -Allen > Dirk > > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >Opensg-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/opensg-users > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
