diff --git a/de/de_Create-Skeleton-Sketch.md b/de/de_Create-Skeleton-Sketch.md index 053ec95..eaadcc9 100644 --- a/de/de_Create-Skeleton-Sketch.md +++ b/de/de_Create-Skeleton-Sketch.md @@ -6,12 +6,12 @@ we are going to build a skeleton sketch as follow, [[images/linkage-dimensioned.png]] -* Switch to Assembly3 workbench -* Create an empty assembly container +* Zum Arbeitsbereich Assembly3 wechseln +* Einen leeren Baugruppen-Container erstellen * Select the newly create assembly object, and click ![AddWorkplane](../raw/master/freecad/asm3/Gui/Resources/icons/Assembly_Add_Workplane.svg?sanitize=true) to add a work plane. Note that you can use any other object with planar edge or face to define the sketch plane. The Assembly3 work plane is just a convenience. * This is an optional step, change the plane `Width` and `Length` to 100mm, and then scale and position the 3D view to put the entire plane in the center. Then hide the plane to not interfere with the draft object editing. The sizing of the plane is to give you a rough idea of how long the lines should be. It is suggested to draw the initial sketch close to the final structure to avoid confusing the solver. * Select the new work plane, and click ![AddSketchPlane](../raw/master/freecad/asm3/Gui/Resources/icons/constraints/Assembly_ConstraintSketchPlane.svg?sanitize=true) to add a `sketchPlane` constraint -* Now, switch to Draft workbench +* Jetzt zum Arbeitsbereich Draft wechseln * Add a few wires according to the above picture. You can add one wire for each colored lines, or you can use multi-segment wires as much as possible to reduce the number of point coincidence constraints needed later. * This is an optional step. For two point line segment, you can set the `Length` property of the draft wire to define the length now. For multi-point poly-lines, you can set the length in later step. * Drag all draft wires into the assembly container. diff --git a/de/de_Home.md b/de/de_Home.md index 73d8795..391d66b 100644 --- a/de/de_Home.md +++ b/de/de_Home.md @@ -1,16 +1,16 @@ -Welcome to the FreeCAD Assembly3 wiki! +Willkommen zum FreeCAD-Assembly3-Wiki! * [[Build Instruction]] -* [[Concepts]] +* [[Konzepte]] * [[Navigation]] -* Tutorials +* Anleitungen * [[Common Operations]] * [[Replacing Part]] * [[Create Skeleton Sketch]] * [[How to Handle Large Scale Assembly]] * [[Modeling using Assembly]] - * [[Constraint with Expressions]] -* [[Constraints and Solvers]] + * [[Randbedingung mit Ausdrücken]] +* [[Randbedingungen und Löser]] * [[Lock]] * [[Plane Alignment]] * [[Plane Coincident]] @@ -25,7 +25,7 @@ Welcome to the FreeCAD Assembly3 wiki! * [[Points Plane Distance]] * [[Point Line Distance]] * [[Symmetric]] -* Release Notes +* Versionshinweise * [0.11](wiki/Release-Notes-0.11) * [0.10](wiki/Release-Notes-0.10) * [0.9](wiki/Release-Notes-0.9) @@ -35,4 +35,4 @@ Welcome to the FreeCAD Assembly3 wiki! * [0.4](wiki/Release-Notes-0.4) * [0.3](wiki/Release-Notes-0.3) * [0.2](wiki/Release-Notes-0.2) - * 0.1 - Initial preview release + * 0.1 - Erste Vorschauversion diff --git a/pl/pl_Common-Operations.md b/pl/pl_Common-Operations.md index 5771e84..1ae048d 100644 --- a/pl/pl_Common-Operations.md +++ b/pl/pl_Common-Operations.md @@ -22,7 +22,7 @@ Teraz zapisz ten dokument pod dowolną nazwą. Zamierzamy zbudować _rzecz_ z wieloma połączeniami, używając powyższego zespołu jako części podstawowej. -* Create a new document, and save it to whatever name you like. Yes, you need to save both the link and linked document at least once for external linking to work, because `PropertyXLink` need the file path information of both document to calculate relative path. +* Utwórz nowy dokument i zapisz go pod dowolną nazwą. Yes, you need to save both the link and linked document at least once for external linking to work, because `PropertyXLink` need the file path information of both document to calculate relative path. * Make sure the current active 3D view is the new empty document. Now, in the tree view, select the assembly we just created previously, and then hold on `CTRL` key and right click the new document item in the tree view, and select `Link actions -> Make link`. A `Link` will be created that brings the assembly into the new document. You probably need to click `Fit content` button (or press `V,F` in 3D view) to see the assembly. * Select the link in the tree view, and change the `ElementCount` property to four. Now you have four identical assemblies. * Create a new assembly, and then drag the link object into it. diff --git a/pl/pl_Concepts.md b/pl/pl_Concepts.md index ca234ee..bdb4e8b 100644 --- a/pl/pl_Concepts.md +++ b/pl/pl_Concepts.md @@ -6,15 +6,15 @@ There is an existing container, `App::Part`, in upstream FreeCAD, which is a gro Środowisko pracy Złożenie3 nie ma takiego ograniczenia. Po dodaniu do środowiska pracy Złożenie3 dane wizualne obiektu są po prostu wielokrotnie wykorzystywane i wstawiane do grafu sceny, co oznacza, że obiekt faktycznie istnieje jednocześnie w wielu układach współrzędnych. To ma nieco nieoczekiwany efekt uboczny. When an object is added to an assembly with some placement, the object is seemingly jumping into a new place (Update: there is a new feature to auto adjust placement when dropping object across different coordinate system. To activate it, right click anywhere in tree view, and select `Tree options -> Sync placement`). This is expected, because the object enters a new coordinate system, and it seems to have the same behavior as `App::Part`. But what actually happened is that the original object inside the global coordinate system is simply made invisible before adding to the assembly container. You can verify this by manually toggle the `Visibility` property to reveal the object in its original placement. Every object's `Visibility` property controls its own visibility in the global coordinate system only. Each assembly container has the `VisibilityList` property to control the visibilities of its children. -# Link +# Łącza The forked FreeCAD core introduced a new type of object, called _Link_. A _Link_ type object (not to be confused with a _link property_) often does not have geometry data of its own, but instead, link to other objects (using link property) for geometry data sharing. Its companion view provider, `Gui::ViewProviderLink`, links to the linked object's view provider for visual data sharing. It is the most efficient way of duplicating the same object in different places, with optional scale/mirror and material override. The core provides an extension, `App::LinkBaseExtension`, as a flexible way to help users extend their own object into a link type object. The extension utilize a so called _property design pattern_, meaning that the extension itself does not define any property, but has a bunch of predefined property place holders. The extension activates part of its function depending on what properties are defined in the object. This design pattern allows the object to choose their own property names and types. -The core provides two ready-to-use link type objects, `App::Link` and `App::LinkGroup`, which expose different parts of `LinkBaseExtension's` functionality. `App::Link` supports linking to an object, either in the same or external document, and has built-in support of array (through property `ElementCount`) for efficient duplicating of the same object. `LinkGroup` acts like a group type object with local coordinate system. It relies on `LinkBaseExtension` and `ViewProviderLink` to provide advanced features like, adding external child object, adding the same object multiple times, etc. All of the Assembly3 containers are in fact customized `LinkGroup`. +The core provides two ready-to-use link type objects, `App::Link` and `App::LinkGroup`, which expose different parts of `LinkBaseExtension's` functionality. `App::Link` supports linking to an object, either in the same or external document, and has built-in support of array (through property `ElementCount`) for efficient duplicating of the same object. `LinkGroup` acts like a group type object with local coordinate system. It relies on `LinkBaseExtension` and `ViewProviderLink` to provide advanced features like, adding external child object, adding the same object multiple times, etc. Wszystkie z kontenerów Assembly3 są w rzeczywistości dostosowanymi `LinkGroup`. # Element -`Element` is a brand new concept introduced by Assembly3. It is used to minimize the dreadful consequences of geometry topological name changing, and also brings the object-oriented concept in the programming world into CAD assembling. `Element` can be considered as a declaration of connection interface of the owner assembly, so that other parent assembly can know which part of this assembly can be joined with others. +`Element` to zupełnie nowa koncepcja wprowadzona przez Złożenie 3. It is used to minimize the dreadful consequences of geometry topological name changing, and also brings the object-oriented concept in the programming world into CAD assembling. `Element` can be considered as a declaration of connection interface of the owner assembly, so that other parent assembly can know which part of this assembly can be joined with others. For a geometry constraint based system, each constraint defines some relationship among geometry elements of some features. Conventionally, the constraint refers to those geometry elements by their topological names, such as `Fusion001.Face1`, `Cut002.Edge2`, etc. The problem with this simple approach is that the topological name is volatile. Faces or edges may be added/removed after the geometry model is modified. More sophisticated algorithm can be applied to reduce the topological name changing, but there will never be guarantee of fixed topological names. Imagine a simple but yet extreme case where the user simply wants to replace an entire child feature, say, changing the type of some screw. The two features are totally different geometry objects with different topological naming. The user has to manually find and amend geometry element references to the original child feature in multiple constraints, which may exists in multiple assembly hierarchies, across multiple documents.