Hi Joe,

On Fri, Oct 9, 2009 at 05:22, Joe Barnhart <joe.barnh...@gmail.com> wrote:
> We could make the wiki even simpler...
>
> Get rid of "comments" on each page.  The wiki IS "comments" it doesn't need
> additional comments!

I agree.

> Get rid of tags.  Tags imply we know in advance what the structure of the
> wiki is.  We don't.  Instead the structure should evolve dynamically with
> wiki pages.

Hmmm, I'm not sure about this. If you were talking about categories,
ok, but the "tag concept" is more "free" then categories.
By the way, I think we need some way to categorize pages. I'm thinking
in namespaces (like in Dokuwiki).

> Generate a set of search keys for each page.  Filter out the punctuation and
> whitespace, then toss uninteresting words ('a', 'the', etc) and save the
> remaining words as a text field to help with full-text searching.

Good thing!

> Cache the generated HTML in the database to avoid re-processing the RST
> every time a page hit occurs.  Most entries are edited rarely but viewed
> often.

Yes, it was just in my ToDo list.

> Permission levels should have site administrators, site contributors
> (editors), and guests.  Admins can edit "immutable" pages, contributors can
> create and edit normal content, and guests can read anything but not edit.

I think it is simple but is what we need for now. Ok, added to ToDo list.

> The design goal should look more like MediaWiki and less like a blog, IMHO.
> Less space wasted for header and navigation and more area devoted to
> content.
>
> I've also been playing with ideas for the web2py wiki.  See my site at
> http://www.site51.net/wiki  for an unfinished prototype.

wiki2py - I liked this name!

> Try the editing feature and notice the AJAX call to process RST and preview
> your changes.  Just click at the bottom of the edit page to re-render the
> RST at any time.

Very good! Can you contribute with your code? We need more developers.

> Create a new page just by entering its WikiName in the URL and then hitting
> "edit".  Remember to edit the main page and add your new page to the list.

It is done this way in web2py wiki!
Enter in:
http://wiki.web2py.com/My_new_page
If the page exists, it'll show the page; else it'll redirect you to:
http://wiki.web2py.com/_create/My_new_page

> This wiki sample is unprotected by signon, so it'll probably get defaced
> quickly and I'll have to take it down.  But for awhile you can see the
> direction I am suggesting -- albeit in a very unfinished state!
>
> Joe B.

Thanks, Joe.


On Fri, Oct 9, 2009 at 17:22, Thadeus Burgess <thade...@thadeusb.com> wrote:
> Once we get the new wiki situated, we can start going through the google
> groups history and looking for questions that have been asked, and adding
> them to the wiki :)
>
> Little things such as
> http://www.mail-archive.com/web2py@googlegroups.com/msg16724.html
>
> would be awesome for learning the framework without too much searching.

Hi Thadeus,
Yes, it'll be very good! Unfortunately I can't do this for now since
I'm doing other things.
So, users, please help!


On Fri, Oct 9, 2009 at 20:01, Richard <richar...@gmail.com> wrote:
> uploaded to GAE here: http://web2py-wiki.appspot.com/wiki
> The first page I accessed threw an error but worked on a refresh.

Hi Richard, thinks for that.

> How do I create a developer user, apart from using appadmin?

This app doesn't provide an way to do it instead of using appadmin.
I think you can create a function, something like that:
def create_users():
    db.auth_user.insert(...)
    db.auth_membership.insert(...)

-- 
 Álvaro Justen
 Peta5 - Telecomunicações e Software Livre
 21 3021-6001 / 9898-0141
 http://www.peta5.com.br/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" 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