TWiki has a small library of utility functions. The global namespace is called, unsurprisingly,
twiki
. For example:
twiki.String = {
// code
}
Plus all files inside
pub/TWikiJavascripts
are named:
twiki_edit.js
twiki_renamebase.js
twiki.compressed.js
twiki.js
twikiArray.js
twikiCSS.js
twikiEvent.js
twikiForm.js
twikiFunction.js
twikiHTML.js
twikilib.js
twikiPref.js
twikiString.js
twikiStringUnicodeChars.js
twikiStyles.js
twikiuiToggle.js
twikiWindow.js
The plan
- Create a new location for the library. So
pub/JavascriptFiles
- Rename the files to
foswikiXXX.js
- Rename the js classes to
foswiki.String
, etc.
- Update all references in extensions
- Update documentation
--
ArthurClemens - 08 Nov 2008 - 18:24
Suggestion: don't wait for newName decision, use
system
or
engine
or something else neutral, don't brand yourself a second time if not absolutely necessary. Just my 2c.
--
FranzJosefGigler - 08 Nov 2008
I need a namespace that won't clash with other js libs. If we are to get a namespace for CPAN, I might as well use that. But the file
twikiString.js
might as well be named
String.js
--
ArthurClemens - 08 Nov 2008 - 21:07
dont' think just CPAN - remember
JSAN too
--
SvenDowideit - 10 Nov 2008 - 01:56
Wikipedia reports: "Due to social reasons Casey West left the project, the master website was lost so people couldn't upload modules, and for other reasons JSAN has had several limitations in its development."
Result:
I would not pick this open source project.
--
ArthurClemens - 19 Nov 2008 - 11:15