Documenting CSS Dependencies in Closure-Library

46 views
Skip to first unread message

David Sankel

unread,
Mar 10, 2015, 1:49:11 PM3/10/15
to closure-lib...@googlegroups.com
When incorporating closure components into a project, it can sometimes be a hassle to figure out which css files, included in closure, are required to view a widget as it shows up in the demo html files. Would a patch that adds, to a component's documentation, which demo CSS files are required be objectionable?

-- David Sankel

Stanimir Mladenov

unread,
Mar 11, 2015, 2:07:29 AM3/11/15
to closure-lib...@googlegroups.com
Closure goog.ui components and demos are kind of abandoned from some time already.
Though the hassle that you have, to fetch the css, doesn't seem to be big to me.
While in the demo page, use Chrome Dev Tools in the Resources tab and save the css files that you need.



2015-03-10 19:40 GMT+02:00 David Sankel <cam...@gmail.com>:
When incorporating closure components into a project, it can sometimes be a hassle to figure out which css files, included in closure, are required to view a widget as it shows up in the demo html files. Would a patch that adds, to a component's documentation, which demo CSS files are required be objectionable?

-- David Sankel

--

---
You received this message because you are subscribed to the Google Groups "Closure Library Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to closure-library-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Sankel

unread,
Mar 11, 2015, 9:36:54 AM3/11/15
to closure-lib...@googlegroups.com
Oh interesting. Is there some kind of replacement for the goog.ui components available?

Stanimir Mladenov

unread,
Mar 11, 2015, 11:27:32 AM3/11/15
to closure-lib...@googlegroups.com
Closure library can be considered as a Standard Javascript Library that can be used for anything you like.
It just happens that the authors did create sophisticated UI part in the library too, which is not supported or improved anymore.

I am keeping in use this UI part of the library without any problems (even supports the old IE8 browser).
Others use different frameworks like Angular, Polymer or React for their UI.

Johannes Nel

unread,
Mar 11, 2015, 11:38:33 AM3/11/15
to closure-lib...@googlegroups.com
Are you saying the goog.ui.* is not supported anymore?

Stanimir Mladenov

unread,
Mar 11, 2015, 12:09:14 PM3/11/15
to closure-lib...@googlegroups.com
These are just my observations, because I am NOT from Google.
And yet, as I stated, the goog.ui.* is pretty good, because I develop everything based on it, since the opening of the closure tools.

Nathan Naze

unread,
Mar 11, 2015, 1:01:53 PM3/11/15
to closure-library
The goog.ui.* library is widely used, but is increasingly not the
focus of development on Closure. It is still supported as it has many
users within Google, but it many teams use Closure Library but do not
use goog.ui.

Nathan

Johannes Nel

unread,
Mar 11, 2015, 2:01:39 PM3/11/15
to closure-lib...@googlegroups.com
Is there a UI system which is gaining adoption within google?

Nathan Naze

unread,
Mar 11, 2015, 2:03:28 PM3/11/15
to closure-library
closure-templates are widely used
angular{1,2} has uptake
various other internal and external technologies are also in use.

Nathan
Reply all
Reply to author
Forward
0 new messages