Icon Source: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Links) |
||
| (20 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Hint|Page in active development. Protocol was defined in 2015, and it is useful to create machine, module, part, and many other icons that can be used as graphical representation for machine and system design. Project Lead - [[Jean-Baptiste Vervaeck]]}} | |||
'''See Instruction Blog Post for how this development process works - [http://opensourceecology.org/pattern-language-icons-2/] ''' | '''See Instruction Blog Post for how this development process works - [http://opensourceecology.org/pattern-language-icons-2/] ''' | ||
=OSE Icons= | |||
See [[OSE Icons]] | |||
=Introduction= | |||
The OSE Icons are used to facilitate [[Open Source Product Development]]. OSE is a tribe of developers, and a tribe needs a common language. That common language inlcludes the wiki, icons, and a common set of development tools in the form of [[OSE Linux]]. These 3 elements (+ others) form a development ecology, where each element reinforces the other: | |||
*The wiki is a large database, and navigation logic needs to be clear to the OSE developer tribe. | |||
*Icons can be used to represent machines, the development process, enterprise development steps, etc - all the aspects of Open Source Product Development. | |||
*Icons can be used to distinguish the type of content, such as CAD or an email list. | |||
*How to find something on the wiki? First, understand that there are different content types (such as CAD assets, email lists, diagrams, etc). Each should be findable by using an '''official content type word''', such as CAD or Diagram, or Email List. | |||
*The icons should correspond to official content type words - such that the icons reinforce the organization of the wiki - together with the content type words. | |||
*As such, all [[Development Template]] items should have a corresponding icons, and so should all mahchines and their parts - ie, the [[GVCS Modules]]. Other icons should include those that are used in creating instructionals - such as safety or tool icons. All in all, any concept or item that is an established [[OSPD]] step should have an associated icon. | |||
*The goal is to have the OSE development tribe understand a common language of development, such that anyone can find anything on the wiki - even in the absence of good wiki indexing. In development work, good organization follows product release - so understanding how to find something on the wiki prior to product release is an important skill that [[OSE Developers]] must develop. Icons can help in this understanding to help people navigate visually. | |||
=Intro Blog Post= | |||
<html><iframe src="https://opensourceecology.org/pattern-language-icons-2/" height=600 width=800></iframe></html> | |||
=Completion Statistics= | =Completion Statistics= | ||
*Goal of 1000 in 6 months | *Goal of 1000 in 6 months | ||
*Week | *Week 2 - 67 first cuts of icons | ||
*Link to numbers - [https://docs.google.com/a/opensourceecology.org/spreadsheets/d/1GazGxVqioNdkOT_FpKyySj5VlHPoenv7bTiW6SeaUDA/edit#gid=0] | *Link to numbers - [https://docs.google.com/a/opensourceecology.org/spreadsheets/d/1GazGxVqioNdkOT_FpKyySj5VlHPoenv7bTiW6SeaUDA/edit#gid=0] | ||
*List of Icons being developed - [https://docs.google.com/a/opensourceecology.org/spreadsheets/d/1tsGoDkciot1CNBaCRnxN4Knk_UYkg9fji5LsMVn6ChQ/edit#gid=0] | *List of Icons being developed - [https://docs.google.com/a/opensourceecology.org/spreadsheets/d/1tsGoDkciot1CNBaCRnxN4Knk_UYkg9fji5LsMVn6ChQ/edit#gid=0] | ||
*See also - [[Graphics Working Team]] | *See also - [[Graphics Working Team]] | ||
=Repository= | =Repository= | ||
| Line 15: | Line 36: | ||
[https://docs.google.com/a/opensourceecology.org/forms/d/1J-mkpPzNxGhpbs-FIO84OQ71ubuelIg_Yd9taWKgwDM/edit edit] [https://docs.google.com/a/opensourceecology.org/spreadsheets/d/1jJv9aBgchmKMZTfpmhrwkIc2vpUVTJqTqIkiGujmJvA/edit#gid=749757977 results] | [https://docs.google.com/a/opensourceecology.org/forms/d/1J-mkpPzNxGhpbs-FIO84OQ71ubuelIg_Yd9taWKgwDM/edit edit] [https://docs.google.com/a/opensourceecology.org/spreadsheets/d/1jJv9aBgchmKMZTfpmhrwkIc2vpUVTJqTqIkiGujmJvA/edit#gid=749757977 results] | ||
== | ==500 Modules== | ||
==50 Machines== | |||
See [[GVCS Icons]] | |||
==Fab Tool Icons== | |||
See [[Fab Tool Icons]] | |||
==As-Built Icons + Style Guidelines== | |||
Note that the original 50 icons have only a few of the machines from OSE's work - such as the tractor, CEB Press, and universal rotor, and microtrac. The rest are either CAD models, or representative pictures from the internet. It would be useful to keep a repository of Genealogy icons corresponding to the original stylistics of the 50 icons - grey, cutout, with a few colored parts. See the [[GVCS_Images#Images]] for the style. | |||
Thus, a visual [[Genealogy]] could be created from all the versions built to date, thus enhancing the clarity of the project. | |||
= | =Links= | ||
*'''Main page - [[Icons]]''' | |||
*[[Fab Tool Icons]] | |||
*[[GVCS Icons]] | |||
*[[FreeCAD Icon Guidelines]] | |||
*[[OSE FreeCAD Icons]] | |||
*[[OSE Module Icons]] | |||
Latest revision as of 21:24, 26 February 2021
Hint: Page in active development. Protocol was defined in 2015, and it is useful to create machine, module, part, and many other icons that can be used as graphical representation for machine and system design. Project Lead - Jean-Baptiste Vervaeck
See Instruction Blog Post for how this development process works - [1]
OSE Icons
See OSE Icons
Introduction
The OSE Icons are used to facilitate Open Source Product Development. OSE is a tribe of developers, and a tribe needs a common language. That common language inlcludes the wiki, icons, and a common set of development tools in the form of OSE Linux. These 3 elements (+ others) form a development ecology, where each element reinforces the other:
- The wiki is a large database, and navigation logic needs to be clear to the OSE developer tribe.
- Icons can be used to represent machines, the development process, enterprise development steps, etc - all the aspects of Open Source Product Development.
- Icons can be used to distinguish the type of content, such as CAD or an email list.
- How to find something on the wiki? First, understand that there are different content types (such as CAD assets, email lists, diagrams, etc). Each should be findable by using an official content type word, such as CAD or Diagram, or Email List.
- The icons should correspond to official content type words - such that the icons reinforce the organization of the wiki - together with the content type words.
- As such, all Development Template items should have a corresponding icons, and so should all mahchines and their parts - ie, the GVCS Modules. Other icons should include those that are used in creating instructionals - such as safety or tool icons. All in all, any concept or item that is an established OSPD step should have an associated icon.
- The goal is to have the OSE development tribe understand a common language of development, such that anyone can find anything on the wiki - even in the absence of good wiki indexing. In development work, good organization follows product release - so understanding how to find something on the wiki prior to product release is an important skill that OSE Developers must develop. Icons can help in this understanding to help people navigate visually.
Intro Blog Post
Completion Statistics
- Goal of 1000 in 6 months
- Week 2 - 67 first cuts of icons
- Link to numbers - [2]
- List of Icons being developed - [3]
- See also - Graphics Working Team
Repository
This is the source repository for OSE's icon library - which includes the source Inkscape files for every icon. You are free to improve these icons by downloading the source and uploading a new version of the file using Wiki Version Control. Write down your change notes. To receive credit for your work, note your contribution in our contributor log:
500 Modules
50 Machines
See GVCS Icons
Fab Tool Icons
See Fab Tool Icons
As-Built Icons + Style Guidelines
Note that the original 50 icons have only a few of the machines from OSE's work - such as the tractor, CEB Press, and universal rotor, and microtrac. The rest are either CAD models, or representative pictures from the internet. It would be useful to keep a repository of Genealogy icons corresponding to the original stylistics of the 50 icons - grey, cutout, with a few colored parts. See the GVCS_Images#Images for the style.
Thus, a visual Genealogy could be created from all the versions built to date, thus enhancing the clarity of the project.