Revision [2073]
This is an old revision of NilsLindenberg made by NilsLindenberg on 2004-11-03 17:15:45.
Userpage of Nils Lindenberg
About me
I am a student of socail science at the university of Goettingen, Germany (currently on exchange in Bologna, Italy). You can find me also at WackoWiki, Wikipedia and http://www.openformats.org . I neither have a computer with the ability to code and test something in php, nor the skill to programm anything as complex as i would like, but someday... :-)Links
http://www.joelonsoftware.com/articles/APIWar.html - about the necessity of backward compatibilityhttp://www.joelonsoftware.com/articles/fog0000000054.html - the chicken and egg problem
http://www.joelonsoftware.com/articles/fog0000000020.html - against the myth of bload programms
http://phpwiki.sourceforge.net/phpwiki/WikiAsPim - about using Wiki for personal information management
http://www.cooper.com/articles/art_goal_directed_design.htm - designing for users, not for programmers
http://www.joelonsoftware.com/uibook/chapters/fog0000000059.html - choose which choises you give to users
My Wishlist for Wikka
- I18n, L10n=> WikkaInternalisation, HandlingUTF8
- a better System for Categorys => CategorySystemOverhaul
- E-Mail (see below for some thoughts) and => WikkaEmail
- Toc (Table of Content) -> already implementet in WackoWiki
- Usermanagement -> UserAdmin
- Acces to the Config.php through a wikka-interface
- Smilys (ok, in some sort of "when everything else is done" ;-)
Idea and Features
So le'ts think about the things which are necessary for this:- should be able to get the necessary information from the user (e-mailserver, username, passwort,...)
- establish/close a connection to the server
- get the mail from the server (pop3, imap4)
- store the mail in the database
- show the mail (one mail, one page?, a list of mails which can be sorted after date, sender, from, size...?)
- deal with attachments
- asend mails (smtp)
- final goal would be: I type a name in the search and get a list of the last e-mails sended to and recieved from him
- should be able to be linked with an adressbook and the calendar
- question: store the connection information for every user in the user-settings page? Perhaps allow only some users to use the e-mail action?
Links
- https://sourceforge.net/projects/poppawid/ popper_mod-wid is a free, full featured web based email client written in PHP. It is an extension of the now abandoned \"popper_mod\" project which was an extension of the origional popper. It runs on any server that can run PHP and mySQL. Uses POP and S
- php/MySQL based webmail program. Currently only supports pop3, IMAP is in the works. Has a notebook, a favorites organizer and an addressbook.
- http://de.wikipedia.org/wiki/Imap, http://de.wikipedia.org/wiki/POP3, http://de.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol, http://de.wikipedia.org/wiki/Simple_Mail_Access_Protocol, http://de.wikipedia.org/wiki/E-Mail
RFCs
- old standard: 822
- new standard: 2822
- "envelope" (transmission and delivery) -> 2821 (old standard: 821)
- MIME document series [RFC2045, RFC2046, RFC2047, RFC2048, RFC2049] for non ascii-messages (and audio, video,etc.?)
RFC2822
- only standard for messages, not for audio, images etc.
- This specification is intended as a definition of what message content format is to be passed between systems.
- local storage is outside of the scope of this standard.
- Note: This standard specifies that messages are made up of characters in the US-ASCII range of 1 through 127.
Length
- length of a line without CRLF: 998 char. max, 78 char. recommended (2822)
Header
- name of header, followed by a colon (":"), followed by a field body and terminated by CRLF (2822)
- body: US-ASCII (2822) except colon
- header can be spread about multiple lines (folding white space after CRLF) -> should be unfolded (simply removing any CRLF
To do
read all the rtfslook what oother free php e-mail programms do and who
look up php-sendmail
whait till Javawomen has finished WikkaEmail and see what could be used :-)
Isue-based Calendar
Possible features
- markup of events in wikkapages
- events could be repeated daily, weekly, monthly and yearly
- events could also have a time
- events could have a time/date/month... when they begin and when they and, making it possible to have periods
- events could be marked up in different categorys
- the view could be shifted between weekly, monthly, yearly and a "current day-based view"
- it should be possible to move to a week/month into the future/past easily
- events should be userbased (user, group, public)
- events should be deletetable by unmarking them on the page
- there should be configurable items like: first day of the week, etc.
- days should be shown colored (like sundays, past days etc.)
Markup for events
There has to be a markup for events on a wikkapage. The normal style for markup is a pair of a char around the text which should be marked up. It is replaced through a <span ="markup"> in the html page.- So the first step is to find a char which isn't used yet and which does not interfere with other things.
- The save action for a page has to check if the markup has the right style and then enter the event with the text in the event-database
- At the html page something like (calendar:24.12)X-Mas"!(/calendar) should appear
- the save function has to check on every change of the page if one of the events has changed or is "de-evented" (I like that word :) -> by deleting all events attached to the page and write the new version in the event-database (note that deleted (hopefully) would appear in the history of a page, therefore events should be saved only when the page is saved, not when it is viewed)
- The database needs the following information: date (day, [weekday, week] month, year), time (hour, minute), user, category [of the event], repeat[how?], [unsure about stop_date & stop_time]
The calendar itself
Monthly view
Mostly based on the version of GmBowenCalendar. The calendar is included to a page as an action and has- to get the currend date and time
- to build a table with the dates [the "current day-based view", weekly and yearly view could come later]
- to provide links to one week/month in the future/past
- has to look up, which day is the first in the week
- to mark days with different colors (like Sundays in red, days past by in gray, days with events in blue, current day in green [and the background with another color for periods of events?])
- to look up, which days have events and link them.
Yearly view
[for the yearly view something like: http://freshmeat.net/projects/activecalendar/ (picture!) (phpclasses.org:1870)]The view of the events
GmBowen had a very good idea for his event action, he is actually working on. Showing them in a box near the calendar (more simple then my approach which wasn?t a real one :-) . With every click on a day linked to events, the box has to be "reloaded" ;-) to show the events of the selected day.- the function has to look up
- the function for showing events has to look up, if the user has the right to see an event
repeatable events
events could be repeated the following way:- no (one - time event)
- daily (at the same time)
- weekly (at the same weekday)
- monthly (at the same day)
- yearly (at the same day and month)
- [there are thingss like "every two weeks" ore "every workday"]
The Database
The database in which the events are stored, has to have the following things:- event_id as a counter
- time, date, [weekday, week], month and year of an event
- the page_id it belongs to
- the user which are able to see it
- the text from the wikipage
- the category an event belongs to
Problems:
- what about periods and repeatable events? [perhaps another table with the relation between events?]
...more in the next days, when I have the time to type the hand-written pages with my thoughts...
CategoryUsers