Joe Barnhart wrote:
> 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.
>   
Three very good points!
> 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."
>   
Absolutely!
> 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!
>
>   
Same as me + the administrative interface. Strike the 20 years 
experience :-(
I just gravitate towards Aptana on the Mac and the fantastic Ulipad on 
Windows.
And I keep hiting walls and taking a lot of time to do relatively simple 
things.

My point is a wiki is probably not the best investment for web2py. 
Though I must agree that this depends fundamentally on Massimos goals.

Miguel

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to