- use Visibility/Graphic Overrides for Categories instead, or better yet, use View Templates
4. Paint a material on an object. (apply a material via a type, or to entire object)
---
### FreeCAD Specific
- Export IFC files very soon and very often, test them in [IFC++](https://ifcquery.com/) first, then in Revit. Detect issues early
- Use simple extrusions as much as possible (Arch Wall/Structures/Panels or Part Extrude)
- Objects exported as IFC structural elements (beams, columns) often give problems in Revit. If needed, use BuildingElement Proxies (Will come as generic models, Revit won't apply any transformation on them)
- Keep list of materials clean, merge duplicates, make sure all objects have a material
---
### Chat Channels
- Install https://element.io/get-started
- We use [Element.io](https://element.io/) as our main chat app. Each OpeningDesign project has it's own dedicated 'room'.
- examples of past projects
- http://openingdesign.com/communication/
- Majority of these rooms are public where past conversations can be reviewed by anyone, at anytime.
- There are private channels, however, as well.
- To install, go to https://element.io/get-started
- Element.io has apps for Web, Android, iOS, macOS, Windows & Linux
- Search and connect with ```@theoryshaw:matrix.org``` (Ryan Schultz)
### File Management on Windows
- download favorite text editor
- example: https://atom.io/
- run with [Admin](https://www.youtube.com/watch?v=nNVdaJXYCbA) rights
- example: [Atom.io](https://atom.io/)
- Right click on the .exe file, and 'Run as administrator'
- 
- Install Git for Windows
- Install **Git** for Windows
- Download from [git-scm.com/download](https://git-scm.com/download)
- Run the installation file with [Administrator](https://www.youtube.com/watch?v=nNVdaJXYCbA) rights
- Choose an appropriate installation location such as C:\_tools\git
- 'Run as adminitrator' as you did with the text editor above.
- Choose an appropriate installation location such as ```C:\Program Files\Git```
- Install the default components, including Git GUI Here and Git Bash Here
- Choose default location of 'start menu folder'
- Choose your preferred Git default editor.
- For example, choose Atom.io, if that's your preferred, and installed text editor.
- For example, choose Atom.io, if that's your preferred text editor
- Choose recommended 'path environment'
- use openSSL library
- Accept the default line ending conversion for Unix and Windows compatibility
@ -67,7 +46,7 @@
- A few Windows configurations...
- Set longpath on windows
- Long answer: https://www.youtube.com/watch?v=mAGQZ7RvKFk
- Long answer [here](https://www.youtube.com/watch?v=mAGQZ7RvKFk)
- Short answer: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
- Set LongPathsEnabled
- Value data: 1
@ -83,61 +62,125 @@
- choose defaults
- First startup wizard
- Language
- Point to git.exe (probably will default to the proper location)
- Point to git.exe (will probably default to the proper location)
- Configure user information
- add name and email
- Authentication and credential store
- choose defaults
- Install [gpg4win](https://www.gpg4win.org/download.html) with [administrator](https://www.youtube.com/watch?v=nNVdaJXYCbA) privileges
- choose default components
- Create accounts at...
- Github: https://github.com/join
- Gitlab: https://gitlab.com/users/sign_up
- Github: https://github.com/join
- Following the steps at the following link to create your private/public GPG keys
- [Windows - Creating New GPG Keys with Kleopatra]([encryption-test/README.md at master · OpeningDesign/encryption-test · GitHub](https://github.com/OpeningDesign/encryption-test/blob/master/README.md#windows---creating-new-gpg-keys-with-kleopatra))
<br>
---
<br>
### Cloning a Repo for the First Time
1. Copy the HTTPS address from either Github or Gitlab.
- 
- 
- From Gitlab...
- 
- From Github...
- 
2. Go to where you'd like to save the repo, and right click and 'Git Clone...'
- 
- The following fields should already be filed in and then hit 'okay'
<br>
---
<br>
### Pulling the latest changes down from the remote repo
1. Right click anywhere in the local folder and go to 'Git Sync'..
- 
- And then 'Pull' 
<br>
---
<br>
### Pushing a change
* right click anywhere in window to bring up the following context menu. go to ***Git Commit -> "master"...***
* Fill in the following below, and hit 'Commit & Push'
<br>
---
<br>
### Starting a Project
- Create a [blank project](https://gitlab.com/projects/new#blank_project) on Gitlab
- [Clone the repo](#cloning-a-repo-for-the-first-time)
- Copy in all the template folders located here: ```OD_Library\Project Folder Structure``` and [push](#pushing-a-change).
- Run [git-crypt init](https://github.com/OpeningDesign/encryption-test#windows)
- add users
- Tell collaborators to subscribe to Gitlab notifications.
- [one way](imgs/gitlab_notifications.png)
<br>
---
<br>
### Revit Specific
- Try not to use the following, if possible...
1. Dumb text notes. Prioritize the following instead.
- use Visibility/Graphic Overrides for Categories instead, or better yet, use View Templates
4. Paint a material on an object. (apply a material via a type, or to entire object)
<br>
---
<br>
### FreeCAD Specific
- Export IFC files very soon and very often, test them in [IFC++](https://ifcquery.com/) first, then in Revit. Detect issues early
- Use simple extrusions as much as possible (Arch Wall/Structures/Panels or Part Extrude)
- Objects exported as IFC structural elements (beams, columns) often give problems in Revit. If needed, use BuildingElement Proxies (Will come as generic models, Revit won't apply any transformation on them)
- Keep list of materials clean, merge duplicates, make sure all objects have a material
<br>
---
<br>
### Creating a New Revit Family
1. When creating a new revit family, one of the cardinal rules when making families is that the objects should be constained to reference planes.
2. There might be exceptions, but another cardinal rule is to start with a family template of the thing you're modeling... that is, use a window template for windows, door template for doors, etc.
<br>
---
<br>
### File too large to push to Github
If your file ever gets above 100mbs and you can't push to Github, try...
@ -146,8 +189,16 @@ If your file ever gets above 100mbs and you can't push to Github, try...
2. For whatever reason, if you do a 'save as' to a temporary file name, and do another 'save as' to overwrite the original file. it reduces the file size.
<br>
---
<br>
### Random
- connecting stackedit to gitlab: https://dev.to/maxwhite20062003/how-to-link-your-gitlab-account-to-stackedit-2pkc
### Random Errors
- If warnings..
@ -187,13 +238,9 @@ If your file ever gets above 100mbs and you can't push to Github, try...
- Usually:
- Record audio and mic on ShareX: https://softwarerecs.stackexchange.com/questions/42767/screen-recording-tool-that-records-both-speaker-o-p-as-well-as-mic-input/74728#74728
