Notes regarding this site

Things to do complete on this site:

• Finish documenting whatever has already been done...
• Implement Projects support... Herein follows the design plan:
  • Each user will have a projects subdir.
  • In their conf subdir, there will be a projects.conf with a format very similar to the toplevel blogs.conf file.
  • When adding a project to the system, all that's required is a shortname and a description -- the description can later be modified. It would write the appropriate line into projects.conf and create a dir projects/shortname where shortname would be whatever was provided.
  • I want there to be able to be multiple entries within a project (similar to how these news entries are treated.)
  • This file would contain... what... well, lets integrate revision control while we're at it...
    

            
    title=Concept Title        
    timestamp=200302261655        
    blah blah blah blah blah concept   
    blah blah idea blah vapourware        
    blah blah blah        
    ...        
    blah blah blah in conclusion blah   
    blah shown blah        
    
    timestamp=200202222200        
    blab blab blab nifty new blab blab concept   
    blab blab idea blab vapourware        
    blab blab        
    ...        
    blab blab in conclusion blab   
    blab shown blah        
    
    timestamp=199908042359       
    ... 
    

    And so on, with new versions simple taking precedence at the top, and only the top revision would show up when viewed normally, but there would be an option to view 'older versions' of this file. Title revisions wouldn't be saved, only content.

  • Well that was a bit longwinded... shall we have another go?
  • Still thinking about how one would handle the initial sorting of the page for layout purposes... Static index files coded by hand are bad, alphabetic entries are too difficult to arrange as desired. Enumerating (in this case) is also bad, since it makes it hard to insert an entry... perhaps the solution is in linked lists... which are a pain to program, but very nice to use once implemented.... potential looping issues there, so good error checking is in order...
• oh! found a bug! time to go fix it...
• Fixed! I can now enter ampersands into my content without worrying about them being converted when I modify the content later...
• TODO: move all references to the rotor key to the (near) top of file and set it apart nicely -- something like ROTORKEY='key' -- That way it would be easy for an install script to generate a unique PASSKEY for that system and prevent some potentially bad hacks. (this script would also be able to rewrite the admin password file and such) DONE!
• TODO: integrate mail sending (with spam prevention)... using a defined SMTP server to send messages (if recepient defined a mailbox) -- as well, some sort of mail-box/guestbook type dealy such that people can add a 'nice site, I appreciate the content.' brief message to a public guestbook. Of course, all of the above would have spam prevention built right in... who know, perhaps my code grows so large, it ends up being a web-based PIM *chuckles*...

Oh, and these modification timestamps are piling up at the bottom -- I'll remove a handful of them... it's fairly easy... two stamps within 2 minutes -- I'll just keep one of them -- and so on...

Modified: 2003 02/26 16:48

Modified: 2003 02/26 18:20

Modified: 2003 02/27 20:44

Modified: 2003 02/28 02:09