You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
objective / purpose
Demonstrable, can clone and publish test as addon; a basic sidebar and at least one function to demonstrate changes, workflow start and restart, placeholder menu items for intended demo list
completion checklist
Discovered in: v0.4.0
Resolved/introduced in: v0.5.0
Design Ready - labels, estimates
Development Ready - design and change list created, updated complexity label and estimates
Changes Listed (mark each member as completed update as needed)
Create overall icon and required promo tiles
Create menu function that sets menu based on calling context string: 'onInstall','onOpen', ....see private notes for scheme and functions, document design
@rcc create store listing trying out new store dashboard, publish to domain and test
@rcm create store listing, Publish to anyone with link and test
iwik do you need a separate script to publish as link, to group, to domain? if so well just test registering more than one to same stated domain code. likely separate is easiest but uses up listings...can same move from as link to domain to store?
Developer Tested - Test Copies (Disposable Alpha "DA!s" and Release Candidate)
POST LIVE:
Beta Tested - Live to controlled audience
Customer Experience - Live analytics reveal working for customers
full pipeline documentation
Overview - describe with history and related items
Nice article. I use DevFlow to resolve his item 1 but a nice article. I will point out his comment on material design is about android add-ons and NOT standard GSuite add-ons which have their own style guide -- see apps script add-ons style guide
Also, see comments in clasp issue on gs to js describing files approach for add-ons. In these notes, the contributor describes their file naming approach: "
Also about the client javascript, we currently have this sort of typical structure (locally):
─ main.gs
─ someLib.gs
─ sidebar/
└─ index.html
└─ clientCode.js.html
─ dialog/
└─ index.html
└─ clientCode.js.html
"
Review that against the 6 sin article and also see #5#29#28 but periods in file name is ok TODO:test
TODO:
Working...adding menu functions for start/restart and reuse by other demos into the namespace next.
Then will push as pre-release 0.5.0 static welcome, ready for first demo.
First will be translating the google example into our model
Will create a separate issue to design the example, will start sketch, see notes in sidebar now: @RobGoelz
objective / purpose
Demonstrable, can clone and publish test as addon; a basic sidebar and at least one function to demonstrate changes, workflow start and restart, placeholder menu items for intended demo list
completion checklist
POST LIVE:
full pipeline documentation
Overview - describe with history and related items
Nice article. I use DevFlow to resolve his item 1 but a nice article. I will point out his comment on material design is about android add-ons and NOT standard GSuite add-ons which have their own style guide -- see apps script add-ons style guide
See article on auth flow and file naming conventions for script separation "6 deadly sins"
Also, see comments in clasp issue on gs to js describing files approach for add-ons. In these notes, the contributor describes their file naming approach: "
Also about the client javascript, we currently have this sort of typical structure (locally):
─ main.gs
─ someLib.gs
─ sidebar/
└─ index.html
└─ clientCode.js.html
─ dialog/
└─ index.html
└─ clientCode.js.html
"
Review that against the 6 sin article and also see #5 #29 #28 but periods in file name is ok TODO:test
TODO:
SO RULE is not to use periods in the folder names BUT in file name is ok.
Solution Design
Final Folder, File, and Namespace organization
Only .gs And .html
These are the files that Gas GitHub Assistant will pull or push to hosted repo (currently GitHub)

All File Types

andPromotional Tiles
See also #49. Here, are the promo/marketing tiles and icon options for our top level addon.
Original files in G Drive
https://drive.google.com/a/redcrowmethods.com/file/d/17TqcXiqBniFhy4Tk3tb4Gcq3iHY-GPCy/view?usp=sharing
https://drive.google.com/a/redcrowmethods.com/file/d/1J8CL--1UWWcp5_MoYuafrDhbQaoiv-wQ/view?usp=sharing
https://drive.google.com/a/redcrowmethods.com/file/d/1fNTRacjyoAnuawbRyHRs-iZwMO2Lz_-u/view?usp=sharing
https://drive.google.com/a/redcrowmethods.com/file/d/1nh72Vvd2wt0hLuf9ls873PHwgqzDdaVr/view?usp=sharing
https://drive.google.com/a/redcrowmethods.com/file/d/1rP_t4Ehg7OMSWMeX2dH5Z_lg_8xP6Vw0/view?usp=sharing
https://drive.google.com/a/redcrowmethods.com/file/d/1tKXOw9q6lGitMrTQNZH4BH3q39XM7b4F/view?usp=sharing
Uploaded files with G Hub Links
What's New Entry
n/a yet
Solution Implementation Notes
Developer Testing- Disposable Alpha and Release Candidate
Live Testing - Beta live to controlled audience
Customer Experience - Re-open and append if issues for customers
The text was updated successfully, but these errors were encountered: