Docs

[angular-ui]

Docs

[shaungrady]

Sounds good. And yes, no more dependencies.

[douglasduteil]

I'm going to help here too, if you don't mind.

[ProLoser]

Be my guest

Dean Sofer
DeanSofer.com
714.900.2254

On Thursday, May 2, 2013 at 3:54 PM, Douglas Duteil wrote:

I'm going to help here too, if you don't mind.

—
Reply to this email directly or view it on GitHub (#4 (comment)).

[douglasduteil]

Hum... I'm stuck :)

I manage to do a lot.

• Some clean up and unifications of Karma and Travis
• I made a tiny task to concat all the dependances the main module ui.utils
• I hierarchized the concatenation tasks to always have the main module ui.utils defined at the end in the builded files.
• I fixed the banner of the builded files.
• And I add a jsHint task...

repo : https://github.com/douglasduteil/ui-utils/tree/Tons_of_Damage
current travis : https://travis-ci.org/douglasduteil/ui-utils/builds/6837205

It is all we needed to do before dealing with the jQuery suppression here ?

[ProLoser]

What do you mean jquery suppression?

Also as a side-note, keep in mind that angular-ui.github.com will no longer contain demos. The demos for the parts of the old AngularUI that are not inside of ui-utils can be put onto github.com/angular-ui/angular-ui (aka angular-ui.github.io/angular-ui)

[douglasduteil]

By no dependencies. Didn't you mean that you want jQuery out of there? So ui.utils is in pure angular?

[ProLoser]

It is. jQuery is only used for tests to create events.
On May 2, 2013 11:24 PM, "Douglas Duteil" [email protected] wrote:

By no dependencies. Didn't you mean that you want jQuery out of there? So
ui.utils is in pure angular?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-17380157
.

[douglasduteil]

Ok my bad.

[ProLoser]

I mean I might very well be wrong, but yes we ultimately would like to no longer have jQuery-specific code in this project. I've already taken some time to remove it from the src as much as I can, and if you encounter more, feel free to remove it. However, it is very tedious to create event objects without jQuery (which is done in tests) so we made it a development dependency (and not a production-dependency).

[ProLoser]

@douglasduteil take a look at the demos branch I just pushed. I had a friend help us out by breaking apart the demo page for us but I haven't had time to properly integrate it. Perhaps it will help you move the doc-generator process along?

[douglasduteil]

Hum...
And you want the demos to be in the doc ? Or to BE the doc ?

[douglasduteil]

And for you where must be the doc-generator process?
Do we generate a doc for each repo (with a gh-page branch per repo). Or we have a one repo « to rule them all »?

[ProLoser]

I think one per repo is the best thing for right now, but I have been
toying with the idea of having a redundant unified demo on angular-ui.
On May 3, 2013 2:46 AM, "Douglas Duteil" [email protected] wrote:

And for you where must be the doc-generator process?
Do we generate a doc for each repo (with a gh-page branch per repo). Or we
have a one repo « to rule them all »?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-17386407
.

[ProLoser]

As for docs vs demos, I don't know (or care) right now so do what you think
is best or is more convenient.
On May 3, 2013 2:13 AM, "Douglas Duteil" [email protected] wrote:

Hum...
And you want the demos to be in the doc ? Or to BE the doc ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-17385178
.

[douglasduteil]

K. I fork my last test.
I'll try to make Travis commit on the gh-page branch, no opposition ?

[ProLoser]

I'm a little confused. Travis is going to create a commit?

Anything on gh-pages should have docs in the root of the repo, if you check out how angular-ui/bootstrap does it they relocate the docs subfolder to the root using grunt.

[douglasduteil]

Yep Travis can commit on GitHub

[douglasduteil]

I made it.

I make grunt concat all the demos index.html https://github.com/douglasduteil/ui-utils/blob/demos/gruntFile.js#L62
And I ask Angular to include that file to the site. And with a little magic it works.

To build the Git Page, I just followed this article
Look at the end of the Travis build : https://travis-ci.org/douglasduteil/ui-utils/builds/6885097#L738

Here is a demo : http://douglasduteil.github.io/ui-utils/
angular-ui-utils.js and others are available like so.

For Bower, like we generally don't need all the repo, I propose to make Travis commit the build on a separated branch and add tags there (not on the master branch )

What you think ?

[ProLoser]

Don't create any tags on the build or demo branch. Also, this will for the
time being be the only repo from AngularUI that needs a build file.

The bower team is going to switch to using snapshots that developers
publish to their servers so tagging a build branch will be unnecessary.
On May 4, 2013 12:35 PM, "Douglas Duteil" [email protected] wrote:

I made it.

I make grunt concat all the demos index.html
https://github.com/douglasduteil/ui-utils/blob/ft-doc-generator/gruntFile.js#L52
And I ask Angular to include that file to the site. And with a little
magic it works.

To build the Git Page, I just followed this articlehttp://sleepycoders.blogspot.se/2013/03/sharing-travis-ci-generated-files.html
Look at the end of the Travis build :
https://travis-ci.org/douglasduteil/ui-utils/builds/6885097#L738

Here is a demo : http://douglasduteil.github.io/ui-utils/
angular-ui-utils.js and others are available like sohttp://douglasduteil.github.io/ui-utils/build/angular-ui-utils.js
.

For Bower, like we generally don't need all the repo, I propose to make
Travis commit the build on a separated branch and add tags there (not on
the master branch )

What you think ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-17440193
.

[douglasduteil]

K.

PS : I'm still looking for a way to have an OAuth token accessible to the team through the GitHub API...

[ProLoser]

I think you could just whitelist the travis server's ssh id_rsa.pub or something.

Dean Sofer
DeanSofer.com
714.900.2254

On Monday, May 6, 2013 at 1:45 AM, Douglas Duteil wrote:

K.
PS : I'm still looking for a way to have an OAuth token accessible to the team through the GitHub API (http://developer.github.com/v3/oauth/)...

—
Reply to this email directly or view it on GitHub (#4 (comment)).

[douglasduteil]

Yep... Seems like it not supported yet...
https://twitter.com/fernandezpablo/status/312389762017263617

[douglasduteil]

K good news I succeed in using Git SSH authentication in Travis without divulging the deploy key...
Following this article.

Before connecting Travis to the gh-page branch I will try out my system on a ft-travis-ssh branch.

Stay tuned.

[douglasduteil]

K I don't know if it's saying too much...
Here is the Travis build
And the result branch...

I don't know if it's useful to have git saying so much things...
If it's not I can add a --quiet option.

[ProLoser]

Looks good. I don't see any secure information that needs to be suppressed.

[douglasduteil]

Yep. At the end I feel like only ui-utils needs this kind of treatment...
The other modules haven't much content in fact...

[douglasduteil]

I feel like renaming the angular-ui-docs repo into a angular-ui-show-off cause we just want to say ::
"See that, it works with Angular, go get the doc and use it !"
What you think ?

[ProLoser]

I think 'show-off' is a synonym for 'demo'. That said, we probably don't need the full angular-ui- prefix (except in the bower component if we ever register it).

Why not just rename the repo to demos or demo-generator or something more concise? This specific discussion should also probably be on that repo lol

[douglasduteil]

Alright.