Martin Dougiamas

OK I'll nuke the tags file, and add a tags.txt instead. MDL-19728

I used this invocation to avoid some problems that we had in the past with some of the newer PHP code:


ctags -R --languages=php --exclude="CVS" --php-kinds=f --regex-PHP='/abstract class ([^ ]*)/\1/c/' --regex-PHP='/interface ([^ ]*)/\1/c/' --regex-PHP='/(public |static |abstract |protected |private )+function ([^ (]*)/\2/f/'


This (and any of the other ctags strings above) don't work on the BSD ctags which comes with Mac OS X so we need a different solution there.

Tags are useful for sysadmins looking at code too, not just developers.

We do need to improve the updating. Anyone can do this, but we should probably make moodle.org do it daily or so.

There are so many application profiles ...

http://en.wikipedia.org/wiki/Learning_object_metadata

But some Moodlers have defined one called MoodleCore:

http://docs.moodle.org/en/Development:Metadata

Shall we go with that?

I'm just a bit worried that a form with all those fields will just be way too confusing for ordinary teachers to use.

Yes, +1 for Tim's idea here.

We have some dilemmas with an interface here in Moodle 2.0 for managing media files within HTML documents.

I would really like your feedback and extension to the ideas here to help us decide the best path:

http://docs.moodle.org/en/Development:Editor_file_management

Feel free to add new ideas to the document or just reply to this discussion.

Thanks!