In case you're curious ...
Currently (after 71 votes) "workshop" is leading with 35 votes. After that is studio (11), showcase (11), project (6), presentation (4), and gallery (3).
I'll leave it open for another week or so.
Martin Dougiamas
Mensagens colocadas por Martin Dougiamas
Moodle in English -> General developer forum -> Files area for students (for presentations, portfolios etc) -> Re: Gallery module
por Martin Dougiamas -
Why not English, in that case? 
I think there is enough trouble finding a name already without opening the field this way.
Bear in mind this name is NOT necessarily the name that will appear on the page (even in English). It is just a short module name that can be used for directories, URLs etc. Of course it would be better if the module-name and the displayed English name were the same.
The French translation may very well display "Atelier" if that is the best translation.
I think there is enough trouble finding a name already without opening the field this way.
Bear in mind this name is NOT necessarily the name that will appear on the page (even in English). It is just a short module name that can be used for directories, URLs etc. Of course it would be better if the module-name and the displayed English name were the same.
The French translation may very well display "Atelier" if that is the best translation.
Moodle in English -> General developer forum -> Files area for students (for presentations, portfolios etc) -> Re: Gallery module
por Martin Dougiamas -
In fact Ray has previously made another module called "Peer Graded Assignment" (pgassignment) which has an even more structured method of assessment. You can try it out in the Demo 103 course if you like.
I'm wondering if there's going to be some confusion here between these two modules - they are similar in many ways.
I'm wondering if there's going to be some confusion here between these two modules - they are similar in many ways.
Moodle in English -> General developer forum -> Moodle 2 - XML / XSLT Eh? -> Re: XHMTL vs. HTML
por Martin Dougiamas -
Well, basically, since I have to design templates for every page then I might as well use the current standard XHTML. I'd be very interested to see what arguments you've found against XHTML, as I haven't come across any yet...
If you really didn't like XHTML then you could always design a HTML 4.0 theme
If you really didn't like XHTML then you could always design a HTML 4.0 theme
Moodle in English -> General developer forum -> Moodle 2 - XML / XSLT Eh? -> Re: Moodle 2 - XML / XSLT Eh?
por Martin Dougiamas -
Note the age of some of the posts. I really like the idea of XML/XSLT - theoretically it's very clean and solves a lot of problems. And it's widely accepted as a standard.
However, this templating standard simply isn't PRACTICAL yet. Support is minimal, it's complicated to set up with PHP, there are performance issues, etc. Since I have no time to start on Moodle 2 at this stage, my current thinking is to keep an eye on XSLT-related technology. IF it hasn't matured enough by the end of the year, THEN I'll most likely use Smarty instead (for speed, simplicity, robustness etc). I'm not aware of any way that Smarty and XLST can be used together (they are competitors really).
While doing this major conversion (either way), all the current old HTML will be cleaned up into XHTML with more complete CSS control. XHTML isn't really innovative but it is more standard than the "quirks mode" HTML most sites use now. This CAN still be done in a way that retains backward compatibility with old browsers (eg using TABLE instead of DIV), but I think by the end of this year it's going to be hard to argue for the need to be fully compatible with Netscape 4 and IE 4.
Does that make sense?
However, this templating standard simply isn't PRACTICAL yet. Support is minimal, it's complicated to set up with PHP, there are performance issues, etc. Since I have no time to start on Moodle 2 at this stage, my current thinking is to keep an eye on XSLT-related technology. IF it hasn't matured enough by the end of the year, THEN I'll most likely use Smarty instead (for speed, simplicity, robustness etc). I'm not aware of any way that Smarty and XLST can be used together (they are competitors really).
While doing this major conversion (either way), all the current old HTML will be cleaned up into XHTML with more complete CSS control. XHTML isn't really innovative but it is more standard than the "quirks mode" HTML most sites use now. This CAN still be done in a way that retains backward compatibility with old browsers (eg using TABLE instead of DIV), but I think by the end of this year it's going to be hard to argue for the need to be fully compatible with Netscape 4 and IE 4.
Does that make sense?