[wiki-standards] Hello - request comments on Creole

[Mike Haseler]

Marc Laporte wrote:
 >
>> 9. Games
> 
> Again? :-)
> 
> Above, you mentioned:
> http://doc.tikiwiki.org/Inter-User+Messages
> http://doc.tikiwiki.org/Blog
> 
> 
> And hundreds of other features and options. More than you'll ever need :-)
> http://doc.tikiwiki.org/Features
>

Marc it sounds superb, and thanks for the input! I can't say I was 
overjoyed, because I've downloaded so many different applications only 
to find that they don't quite do what I need and are not compatible with 
the rest of what I am doing to the extent that they are unusable.

As you say tikiwiki looks like it does more than anyone could possibly 
want ... just as all the micro$oft software always tell you they do 
everything you could possibly want ... unless you want something different.

Does it include grass tycoon? And I quote from my email:-

> 
>> THEN AGAIN, ONE OF MY FIRST APPLICATIONS WILL BE A VIRTUAL GRASS 
>> GROWING APPLICATION, WHERE YOU WATCH VIRTUAL GRASS GROWING (NO I AM 
>> NOT KIDDING - AND YES IT IS ADDICTIVE AND I'VE GOT SHEEP EATING 
>> THE GRASS, AND PLANS TO INCLUDE WOLVES EATING THE SHEEP, AND PERHAPS 
>> MEMBERS WILL BE ABLE TO SEND MESSAGES TO EACH OTHER AND POST ADVERTS, 
>> AND GUESS WHAT - THEY'LL BE USING MARKUP!!
> 

When my own application is complete, I will be able to add to the top of 
the webpage a huge quantity of code:

<? include ('protect.php')
$user = new session('Scouts') ?>

and as if by magic, not only the page will be protected unless you 
access the password (and are a scout), but I'll have a suite of 
functions that sterilise user input, give access to the database without 
having to know what actual database is being used on the server. Indeed, 
the page will be given a header giving links to the rest of the site.

I will then have access to the userID, name etc. of the current user so 
that the grass growing is in their field.

And unlike PHPBB, I won't have to have an entire website in the PHPBB 
directory if anything is to work.

MODEL for "PHPPassWord"

USER1 <=>             <=> Application 1 (e.g. Grass-tycoon)
USER2 <=> PHPPassWord <=> Application 2 (e.g. email lists)
USER3 <=>             <=> Application 3 (e.g. PHPBB)
USER4 <=>             <=> Application 4 (PMwiki, PHPwiki, Wikimedia)


Where "PHPPassWord" consists of:

1. Password authentication
2. User ID
3. Input filtering
4. Database interface
5. Common Textual markup interface
6. Inter-application signalling
7. New application Installation
8. Database backup
9. Admin of passwords, users, authentication
10. Inter-user messaging
11. Common smilies
12. user banning.
13. Anti-spam features (e.g. authentication required to post URLs)

Having examined the code of a few applications, it seems that perhaps 
75% of most application's code is covered by the above meaning that if I 
get this thing working I could produce applications in 1/4 the time it 
takes most people.

Indeed, when an application is simply a page where the photos are only 
visible to signed on users:-

<? $user->insert_protected_image("children_party.jpg", "children 
enjoying the party"); ?>

anyway,

so much for the ambition!

Mike