22
edits
No edit summary |
m (→API Naming: forgot sig again) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 30: | Line 30: | ||
[http://moofx.mad4milk.net/#introduction moo.fx]<br> | [http://moofx.mad4milk.net/#introduction moo.fx]<br> | ||
[http://script.aculo.us/ script.aculo.us]<br> | [http://script.aculo.us/ script.aculo.us]<br> | ||
== File I/O == | |||
This might be obvious (unless there's something I'm missing), but if someone develops a File I/O (which would be absolutely awesome and important), please make it Unicode-friendly... | |||
[[User:Brettz9|Brettz9]] 16:40, 24 May 2007 (PDT) | |||
== API Naming == | |||
Can I ask what practices are being used to determine the naming for the API? | |||
While I have little knowledge in this area, I'd like to offer the following: | |||
1) Try to follow standard JavaScript naming practices | |||
2) Where #1 is not defined, might it be considered to model after PHP function names? The library is large enough, the functionality useful, the naming simple (if sometimes argument order is inconsistent--which I hope FUEL can learn from--e.g., always put the string to be operated on as the first argument, etc.), the user base large, and the audience base perhaps similar to the audience base which would like to take advantage of FUEL (and would thus be familiar with its conventions). | |||
Another ignorant question: As far as File I/O, didn't Server-Side Javascript already have such functionality? Are you going to deliberately name similar to or different from SSJS? Why doesn't Firefox itself use the SSJS File I/O, etc.? | |||
I wonder also about whether the [http://davidkellogg.com/wiki/Main_Page?origin=moz_pow POW extension] could fit in with all of this somehow too. | |||
[[User:Brettz9|Brettz9]] 16:51, 24 May 2007 (PDT) |
edits