Not that I want to push this more than necessary but I made a mistake. https://mdp.cti.depaul.edu/wiki
Even if you were able to register, I did not make you member of the 'developer' group thus most of the functions of the wiki were disabled for you. That is why you thought this looks like a blog and not a wiki. If you have registered already now you are a member of the 'developer' group. Whether we use this or not I could use your feedback. Please give it one more try. Massimo On Feb 26, 2:31 pm, Joe Barnhart <joe.barnh...@gmail.com> wrote: > It is an improvement, but to me it still has more of a "blog" feel > than a wiki. > > Most wiki will automatically create stub pages for key words > referenced in an article. They don't usually have "comments" unless > they are on a separate discussion page (like Wikipedia). The revision > history and diff are key features of a wiki and are prominent and easy > to access. > > I have no doubt that web2py can create a world-class wiki platform. I > just wonder if that is where you want to focus your energies right > now. It's going to take a long time and a lot of effort to duplicate > the features of a wiki engine. If you grow more developers who > understand the nuances of web2py, you can get more shoulders to push > that wheel of progress instead of you having to do everything > yourself. > > I visited the Ruby wiki which is done on Rails. It also feels more > like a blog. I hit three errors in five minutes of browsing, > including an application error for the "history" page and dead links > on the front page. It gave me more of a feeling of, "I'm glad I don't > use rails" instead of "gee this is cool." > > Would I help development? Sure, if I knew anything about web2py. I > don't! I can scratch the surface, but any deeper and I'm lost. I am > not alone in this. You track your membership numbers here, can you > tell how many people come to the site and stay? There's your core. > That's how many people are actually using web2py. We need to make > web2py accessible to the masses and that takes documentation. I'm not > sure another appliance development is the best way to achieve the goal > of getting web2py to the masses. > > -- Joe B. > > P.S. Not to blow my horn, but I code for a living and have been > developing in Smalltalk for 20 years. I also know Python pretty > well. I'm a web site newbie, tho, and I still find web2py daunting to > use. When I'm programming in web2py I keep open four windows -- the > application I'm working on, the web2py manual PDF, a browser to this > newsgroup, and a Komodo window open on the source. We need docs. > Lots of docs! > > On Feb 25, 11:06 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > Point taken. Try this: > > >https://mdp.cti.depaul.edu/wiki > > > I can complete the TODO tasks tomorrow but before I do I could use > > some usability tests. Does it feel more like a wiki? What is missing? > > Want to help with development? > > > Massimo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
