Levels of Source - Revision history

Marcin: /* CAD */

2022-06-04T23:36:03Z

CAD

← Older revision		Revision as of 23:36, 4 June 2022
Line 12:		Line 12:
	For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.		For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.

	'''Reconciling Levels of Source:''' For FreeCAD files, it may be thus useful to combine some levels of source in a single file in order to simplify file management, but the disadvantage is that this adds a step of extracting the right part in the OSE [[Merge Workflow]]. For example, this file has all the parts hidden, and a final clone of simple copy (one part and uneditable) shown at the ~~end~~.		'''Reconciling Levels of Source:''' For FreeCAD files, it may be thus useful to combine some levels of source in a single file in order to simplify file management, but the disadvantage is that this adds a step of extracting the right part in the OSE [[Merge Workflow]]. For example, this file has all the editable source parts hidden, and a final clone of simple copy (one part and uneditable) is shown as the last item in the part tree.

	[[File:levelofsource.png\|400px]]		[[File:levelofsource.png\|400px]]

Marcin: /* CAD */

2022-06-04T23:34:47Z

CAD

← Older revision		Revision as of 23:34, 4 June 2022
Line 12:		Line 12:
	For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.		For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.

	'''Reconciling Levels of Source:''' For FreeCAD files, it may be thus useful to combine some levels of source in a single file in order to simplify file management, but the disadvantage is that this adds a step of extracting the right part in the OSE [[Merge Workflow]].		'''Reconciling Levels of Source:''' For FreeCAD files, it may be thus useful to combine some levels of source in a single file in order to simplify file management, but the disadvantage is that this adds a step of extracting the right part in the OSE [[Merge Workflow]]. For example, this file has all the parts hidden, and a final clone of simple copy (one part and uneditable) shown at the end.

			[[File:levelofsource.png\|400px]]

Marcin at 23:30, 4 June 2022

2022-06-04T23:30:04Z

← Older revision		Revision as of 23:30, 4 June 2022
Line 11:		Line 11:

	For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.		For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.

			'''Reconciling Levels of Source:''' For FreeCAD files, it may be thus useful to combine some levels of source in a single file in order to simplify file management, but the disadvantage is that this adds a step of extracting the right part in the OSE [[Merge Workflow]].

Marcin: /* CAD */

2022-06-04T21:46:52Z

CAD

← Older revision		Revision as of 21:46, 4 June 2022
Line 8:		Line 8:

	=CAD=		=CAD=
	#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.		#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. But this complicates the file management process in a version history. For novices, the general principle is upload early and often, and label your uploads in the version history comments on the wiki.

			For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.

Marcin: /* CAD */

2022-06-04T21:45:29Z

CAD

← Older revision		Revision as of 21:45, 4 June 2022
Line 8:		Line 8:

	=CAD=		=CAD=
	#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept.		#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept, as we could have many different versions of a file optimized for various purposes: from documentation, to rendering, to analysis, to visualization, to range of motion analysis, etc.

Marcin at 21:44, 4 June 2022

2022-06-04T21:44:37Z

← Older revision		Revision as of 21:44, 4 June 2022
Line 7:		Line 7:
	For practical considerations, let's define levels of source as multiple ways of defining hardware, with more or less detail - which depends on what tools are used in the development process. Let's take a look at some of these tools:		For practical considerations, let's define levels of source as multiple ways of defining hardware, with more or less detail - which depends on what tools are used in the development process. Let's take a look at some of these tools:

	#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file. Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]].		=CAD=
			#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file because it can be represented more simply in the part tree and is more easily manipulable (while being less editable). Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]]. Thus, we may define different levels of source as 2 main levels: fully editable detail with multiple editable sketches, or a final dumb, monolithic, inseparable, uneditable object. And everything in between. CAD mastery means that we formally label these in the version history to make it easier for others to collaborate with us. This is an advanced CAD concept.

Marcin at 21:41, 4 June 2022

2022-06-04T21:41:41Z

← Older revision		Revision as of 21:41, 4 June 2022
Line 3:		Line 3:
	In hardware, another concept arises: levels of source.		In hardware, another concept arises: levels of source.

	Because [[There is No Uniform Compiler]]		Because [[There is No Uniform Compiler]], a more complex source code structure prevents simple tools like git from being sufficient to address all documentation needs. Point being - it is not crystal clear what source code is required to define open hardware in a deterministic way. It may easily turn out that the source code is imcomplete, in that it is missing certain 'compilation instructions' - metaphorically speaking. This is a much longer discussion and a can of worms.

			For practical considerations, let's define levels of source as multiple ways of defining hardware, with more or less detail - which depends on what tools are used in the development process. Let's take a look at some of these tools:

			#CAD - what is the ultimate source? The flexibility of [[FreeCAD]] allows for different ways of expressing designs. For example, you can have a file that has editable sketches, and a file that contains dumb objects. All of these files should be available, as they can serve different purposes. For example, editable sketches should be kept whenever possible. But a final design, such as a Clone (dumb object) may be more useful in a large file. Or, one may choose a different workflow, such as a workflow other than [[Merge Workflow]].

Marcin: Created page with "Source code is clear for software. Source code, if using the term as a metaphor - can apply to hardware design. Such as a house. In hardware, another concept arises: levels o..."

2022-06-04T21:14:55Z

Created page with "Source code is clear for software. Source code, if using the term as a metaphor - can apply to hardware design. Such as a house. In hardware, another concept arises: levels o..."

New page

Source code is clear for software. Source code, if using the term as a metaphor - can apply to hardware design. Such as a house.

In hardware, another concept arises: levels of source.

Because [[There is No Uniform Compiler]]