I agree with Peter. I believe some examples are better than none. A few weeks back, I was trying to fix some of the examples, but got side tracked on other issues. I'll try to get back to them ASAP. I would like to know what people think we should do. Should we create a single large "show case" that contains all examples? In some ways this is best, but I could see people wanting to just look at a simple example with only 20 lines of code, if they are trying to learn something.
On Monday, August 13, 2012 8:39:55 AM UTC-5, peter.bittner wrote: > > Anthony, > > I've opened an issue on that very task: > https://github.com/pyjs/pyjs.org/issues/9 > > Basically, I compiled what we have already discussed about the > "examples index" and "broken examples" roughly in May this year. > > 2012/8/13 C Anthony Risinger <[email protected] <javascript:>>: > > yes quite a few examples are either crappy, outdated, or completely > botched. > > > > ... this is just one of the many maintenance issues that has arisen > > from a former "add add add everything anywhere" approach. > > > > i will probably be axing many examples in good time, or publishing > > only a select few on the website. > > We shouldn't be repetitively condemning the past. I believe "no > examples" are still worse than some that "usually work", or work > partly. One task of examples still is giving an idea of what it is > like using the technology in question. The several code pieces give an > idea, and if they are from different people, we may see different > approaches or coding styles, and learn from it. We should be careful > on which efforts to throw away. > > Yes, I do agree on consolidating! What needs to be done is find out > which examples roughly cover one and the same topic, and turn them > into ultimately "great examples" that look great in both, presentation > and source code. To start with we could cluster the existing examples > to get a better overview of what is out there already. > > Peter > --
