Development talk:Text formats

Some points:

A- Fix places without "format"

a) inline format info (like trusttest -> Sam)

b) add formatxxx fields in all missing places. Naming schema "xxxformat" (exam. "descriptionformat").

- db new fields.

- upgrade

- forms modification (combined element)

- backup & restore

- Need conversion to HTML format (always enabled plugin) from all formats

- convert all the old format fields to use the new naming schema.

- backup and restore

- forms modification

B- Make them modular (pluggable. OOP) (lib/format and lib/formatlib.php, get_format()->do_stuff())

C- Enable at site/course levels?

D- Upgrade to detect formats should be clever (and will be heavy!)

E- Each format can have ONE and only ONE "especial editor" attached.

F- Can have "special" editors for other formats.

G- User preferences to a) Choose format and b) "Use special text editor if available" yes/no.

USED formats have precedence over USER settings, so editing existing texts won't change the format at all.

Only new texts can select (user setting) the format.

If the user voluntary has disabled "use text editor" above, format won't change when editing new fields.

If the user lacks the requirements of the editor => switch to FORMAT_MOODLE

H- Wiki format (mediawiki). Coming from nwiki hopefully.

I - Conflicts between formats and some filters sharing same syntax:

a) make filters to use prefixes and allow them to be automatically informed to the formats. Complex.

b) Use some alternate syntax (a safe one)

J- Filters: Any relation with formats? Enable/disable them by format?

K - Offtopic: Posibility to enable/disable filters by context.

L - Is a format the same than a parser (in nwiki slang)

--Eloy Lafuente (stronk7) 03:29, 15 October 2008 (CDT)