Compile and Archive what we learned

[VillageHubertChen]

• Compile What we learned
• @LukasChen Proofread What we learned
• Find the right places on where to Archive the Know How in What we learned
  • Then move it to there

[VillageHubertChen]

What we learned

Efficiency of just one gh-pages branch

At the beginning of development in this repository we have only one branch: gh-pages. It fulfills the following purposes:

• Hosting of web site with demo
• Repository of distribution code
• Development Environment

This is very efficient, but has of course shortcomings:

• During Development the distribution code may be corrupt
• During Development the demo may be corrupt

For a side project or for kicking off a project this is OK. For a project that has subscribers this will not longer be OK. Then we need to use the 3 Branch System

3 Branch System

• Master Branch Contains distribution code
• Feature Branch(es): Each feature in development has its own branch. Once the feature works it will be merged into the Master Branch and deleted.
• gh-pages Branch Demo and Documentation

Use MIT dual license for small projects

By adding the MIT license in addition to the CC-BY license more developer will be motivated to use our code. As such we will get more contributors. → MIT & CC-BY Dual License

Create a repository for small independent projects / products

Qualification Criteria

• It is possible to demo the code. Examples are:
  • v2-Tabs
  • v2-Tips
• The product has a sharply outlined function, which can be expressed in a feature list
• We will use this product in several places over an extended period of time
• More than one person develops on it. Documentation counts as development.

Benefits

• Expressing function of Product in README.md sharpens focus of development
• Communication is more efficient due to better documentation
• management is more precise by using GitHub Issues
• It is easier and more likely to get help on stackoverflow

Method Dual Demos

In case that a feature can not be successfully implemented it is useful to have one working and one not working demo in gh-pages. The working demo is developed as far as possible until hitting the problem that we can not solve. This demo shows that we know how to build working product. The not working demo goes the one step further that breaks. Then we ask for help to fix this.

Deeper Understanding on Dynamic HTML

►►►??? This chapter needs to be completed by LC. Then you need to trigger HC for proof reading???◄◄◄

Using ng-repeat creates a Dynamic HTML page

This should be clear, but not all consequences were understood by all team members.

Evaluate

Use ready events when accessing dynamic DOM objects

Use break points to understand timing of building DOM

Two loaded events

1. Build Static HTML
2. Complete building the Dynamic HTML