Description:
Welcome! Use this group to give feedback and discuss ways of improving Closure Library. Some suggested topics include ideas for new features, improvement of existing features and questions or comments around the high-level design of Closure Library.
|
|
|
Annotation Feature Wishes (Type Templates & Functions with Properties)
|
| |
Hi guys, here are two feature wishes regarding the Google Closure Library Annotation System. 1. Functions with properties function iReturnAFunctionWithAdditional Properties(a) { var x = a; var *f* = function(opt_b) { if(arguments.length == 0) return x; else x = opt_b; }; *f.hello* = function(text){alert(text); return x;};... more »
|
|
|
Setting up unit tests
|
| |
We are prospecting to port our project's JS unit tests to the google's
closure library jsUnit testing facilities.
Is there a way we can have unit testing on compiled code? Our
reasoning behind this is to test that the compiled API of our
application (website) works after compilation, so as to make sure no... more »
|
|
|
@preserveTry Annotation?
|
| |
I was reading the source of debug.js and noticed a /* @preserveTry */
annotation just before a try{} statement...
[link]
Is this annotation required? What are its effects? I could not find
any documentation about it...... more »
|
|
|
Strange behaviour overriding ComboBox.dispatchEvent
|
| |
Hi All, I'm trying to do my own ComboBox that extends goog.ui.ComboBox; just so I can keep track of the selected MenuItem rather than just work with the text captions. So I thought overriding the dispatchEvent method would be the best way to do this so I have: /** @inheritDoc */ my.MyComboBox.prototype.dispat chEvent = function(e) {... more »
|
|
|
soynode -- request for feedback
|
| |
Hey all,
Here at Obvious we're using the Closure Compiler (via Plovr<[link]>)
and parts of the Library on the web client. The frontend server is node.js
and we have no plans of using Closure there for the foreseeable future.
To date we've been using Hogan.js <[link]> for... more »
|
|
|
Add Style to button
|
| |
I am trying to implement button dynamically.
Here is my code:
.............
var button = new goog.ui.Button('Hello!');
button.render(goog.dom.getElem ent('buttonDiv')); // button div in
HTML
button.addClassName('className ');
button.setId('idName');
.............
the contents of my css file are:... more »
|
|
|
Style to a Button
|
| |
I am trying to implement button dynamically.
Here is my code:
.............
var button = new goog.ui.Button('Hello!');
button.render(goog.dom.getElem ent('buttonDiv')); // button div in
HTML
button.addClassName('className ');
button.setId('idName');
.............
the contents of my css file are:... more »
|
|
|
Closure UI package design goals under rendering
|
| |
I'm wondering why dom structure is created when render() method is
invoked ? Why dom structure is not created in ui widget constructor,
then we can operate on widget dom structure right away (even if it's
not in document). In google closure approach, when we have some widget
method (setTitle for example) we have to remember to handle situation... more »
|
|
|
goog.scope() is not meant to alias defining class itself, right?
|
| |
If I want to alias defining class using goog.scope, I should write like this: ============================== =================== goog.provide('app.MyClass'); /** * @constructor */ app.MyClass = function() { /** * @type {!app.SomeType} * @private */ this.f_ = new app.SomeType(); ...goog.scope(function() {... more »
|
|
|
