SpecFilletChamfer - Revision history

Romain2Boss: Add category Proposals

2012-03-31T10:16:42Z

Add category Proposals

← Older revision		Revision as of 10:16, 31 March 2012
Line 51:		Line 51:

	* A: 2geom's filet-minion toy demonstrates how to implement this to compute 'Y'. A nice emergent property of using self-intersections on the offset curves is that you can remove all tight spots, not just those on control handles. However, the results aren't very visually pleasing to me. There are no obvious numerical problems, but some difficulty in detecting loops. If a student were to take on this project we could discuss techniques for accurately detecting the bad cases.		* A: 2geom's filet-minion toy demonstrates how to implement this to compute 'Y'. A nice emergent property of using self-intersections on the offset curves is that you can remove all tight spots, not just those on control handles. However, the results aren't very visually pleasing to me. There are no obvious numerical problems, but some difficulty in detecting loops. If a student were to take on this project we could discuss techniques for accurately detecting the bad cases.

			[[Category:Proposals]]

Njh: /* Existing Code? */

2009-04-02T05:59:20Z

Existing Code?

← Older revision		Revision as of 05:59, 2 April 2009
Line 49:		Line 49:

	* A: These kind of calculations is being widely used in CAD applications, eg. in Qcad (see: http://www.ribbonsoft.com/qcad.html ).		* A: These kind of calculations is being widely used in CAD applications, eg. in Qcad (see: http://www.ribbonsoft.com/qcad.html ).

			* A: 2geom's filet-minion toy demonstrates how to implement this to compute 'Y'. A nice emergent property of using self-intersections on the offset curves is that you can remove all tight spots, not just those on control handles. However, the results aren't very visually pleasing to me. There are no obvious numerical problems, but some difficulty in detecting loops. If a student were to take on this project we could discuss techniques for accurately detecting the bad cases.

Dopelover: /* Existing Code? */

2009-03-22T01:32:28Z

Existing Code?

← Older revision		Revision as of 01:32, 22 March 2009
Line 47:		Line 47:
	===Existing Code?===		===Existing Code?===
	* Q: Does anyone know of any existing code in the codebase that makes these sorts of calculations? So as to avoid reinventing the wheel and duplicating code?		* Q: Does anyone know of any existing code in the codebase that makes these sorts of calculations? So as to avoid reinventing the wheel and duplicating code?

			* A: These kind of calculations is being widely used in CAD applications, eg. in Qcad (see: http://www.ribbonsoft.com/qcad.html ).

Jfb: /* More ideas */

2008-03-17T22:35:39Z

More ideas

← Older revision		Revision as of 22:35, 17 March 2008
Line 37:		Line 37:
	=== More ideas ===		=== More ideas ===
	See [http://www.oberonplace.com/products/curveworks/index.htm]		See [http://www.oberonplace.com/products/curveworks/index.htm]

			Cale Gibbard proposed another technique [https://bugs.launchpad.net/inkscape/+bug/202751 here], with an excellent [http://launchpadlibrarian.net/12692602/rcp.svg diagram] to explain it.
			I think it's a very good solution, relatively easy to code and more "stable" under deformations of the original curve (in particular, there is always one and only one solution...). The output arc is not a perfect circle however, and it's radius is not explicitly controlled (depends on tangent angle at the corner). Maybe both option should be tested/implemented.
			--[[User:Jfb\|jfb]] 22:35, 17 March 2008 (UTC)

	== TODO ==		== TODO ==

Joelholdsworth: /* Design */

2008-02-06T23:23:26Z

Design

← Older revision		Revision as of 23:23, 6 February 2008
Line 16:		Line 16:
	In terms of implementation, the filleting tool must be implemented as a sub-feature within the node edit tool. With the node tool selected, the user will select a series of points in a path that they would like to fillet. The user will then click the fillet button in the node context toolbar.		In terms of implementation, the filleting tool must be implemented as a sub-feature within the node edit tool. With the node tool selected, the user will select a series of points in a path that they would like to fillet. The user will then click the fillet button in the node context toolbar.

	With this fillet-tool-button clicked, and the an interactive fillet mode is activated. The node edit context toolbar will change to a fillet context toolbar. The fillet-tool-button will remain present on this new toolbar, but will be shown depressed to indicate that the filleting mode is activated. An edit box with spinner will be placed in the bar so that the user can choose the radius numerically. At the same time handles will be shown on the canvas to allow the user to edit the radius interactively.		With this fillet-tool-button clicked, and the an interactive fillet mode is activated. The node edit context toolbar will change to a fillet context toolbar. The fillet-tool-button will remain present on this new toolbar, but will be shown depressed to indicate that the filleting mode is activated. An edit box with spinner will be placed in the bar so that the user can choose the radius numerically. At the same time handles will be shown on the canvas to allow the user to edit the radius interactively. Helper circles will give a preview of the end result.

	Once the user is happy with the fillet, the result can be committed by selecting a different tool or clicking fillet-tool-button on toolbar (so as to un-depress it). To cancel, the user can press Esc, or can apply the change then Undo.		Once the user is happy with the fillet, the result can be committed by selecting a different tool or clicking the fillet-tool-button on toolbar (so as to un-depress it). To cancel, the user can press Esc, or can apply the change then Undo.

	It might be helpful to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.		It might be helpful to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.

Joelholdsworth: /* Design */

2008-02-06T23:19:37Z

Design

← Older revision		Revision as of 23:19, 6 February 2008
Line 14:		Line 14:
	== Design ==		== Design ==
	=== User Interface ===		=== User Interface ===
	In terms of implementation, the filleting tool must be implemented as a sub-feature within the node edit tool. With the node tool selected, the user will select a series of points that they would like to fillet. The user will ~~the~~ click the fillet button in the node context toolbar.		In terms of implementation, the filleting tool must be implemented as a sub-feature within the node edit tool. With the node tool selected, the user will select a series of points in a path that they would like to fillet. The user will then click the fillet button in the node context toolbar.

	With this fillet-tool-button clicked, and the an ~~interractive~~ fillet mode activated. The node edit context toolbar will change to a fillet toolbar. The fillet-tool-button will remain present on ~~the~~ toolbar, but will be shown depressed ~~while in~~ the filleting in mode. An edit box with spinner will be placed in the ~~tool commands~~ bar so that the user can choose the radius ~~for the~~ numerically. At the same time a handles will be shown on the canvas to allow the user to edit the radius interactively.		With this fillet-tool-button clicked, and the an interactive fillet mode is activated. The node edit context toolbar will change to a fillet context toolbar. The fillet-tool-button will remain present on this new toolbar, but will be shown depressed to indicate that the filleting mode is activated. An edit box with spinner will be placed in the bar so that the user can choose the radius numerically. At the same time handles will be shown on the canvas to allow the user to edit the radius interactively.

	Once the user is happy with the fillet the result can be committed by selecting a different tool or clicking fillet-tool-button on toolbar so as to un-depress it. To cancel the user can press Esc, or can apply the change then Undo.		Once the user is happy with the fillet, the result can be committed by selecting a different tool or clicking fillet-tool-button on toolbar (so as to un-depress it). To cancel, the user can press Esc, or can apply the change then Undo.

	It might be helpful to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.		It might be helpful to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.

Joelholdsworth: /* User Interface */

2008-02-06T23:17:00Z

User Interface

← Older revision		Revision as of 23:17, 6 February 2008
Line 14:		Line 14:
	== Design ==		== Design ==
	=== User Interface ===		=== User Interface ===
	In terms of implementation, the filleting tool must be implemented as a ~~first class citizen along with~~ the ~~rest of~~ the ~~toolbox - having a~~ tool ~~commands toolbar~~, a ~~cursor, status messages etc., just~~ like ~~other tools~~. ~~In terms of~~ the ~~UI for activating~~ the ~~tool - this could be added as another icon~~ in the ~~toolbox, but it might be better to hide the tool away in a well chosen location (discuss), so as not to clutter the toolbox with a new tool that is really very specialist~~.		In terms of implementation, the filleting tool must be implemented as a sub-feature within the node edit tool. With the node tool selected, the user will select a series of points that they would like to fillet. The user will the click the fillet button in the node context toolbar.

	To fillet ~~a corner~~, the ~~user~~ will ~~first select the object~~ to ~~modify, then activate the~~ fillet tool~~, then click~~ on the ~~cusp point with~~ the ~~mouse~~. ~~It might~~ be ~~possible to show a preview of~~ the ~~fillet as~~ the user ~~hovers over~~ the ~~point with~~ the ~~mouse~~. ~~It might also~~ be ~~possible~~ to ~~add a button in~~ the ~~tool commands bar that fillets all~~ the ~~corners in a shape~~.		With this fillet-tool-button clicked, and the an interractive fillet mode activated. The node edit context toolbar will change to a fillet toolbar. The fillet-tool-button will remain present on the toolbar, but will be shown depressed while in the filleting in mode. An edit box with spinner will be placed in the tool commands bar so that the user can choose the radius for the numerically. At the same time a handles will be shown on the canvas to allow the user to edit the radius interactively.

	~~An edit box~~ with ~~spinner will~~ be ~~placed in the~~ tool ~~commands bar~~ so ~~that~~ the user can ~~choose~~ the ~~radius for the fillet~~.		Once the user is happy with the fillet the result can be committed by selecting a different tool or clicking fillet-tool-button on toolbar so as to un-depress it. To cancel the user can press Esc, or can apply the change then Undo.

	It might be helpful ~~(discuss)~~ to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.		It might be helpful to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.

	This tool ~~could~~ give the option to chamfer the corner - where instead smoothing the corner with an arc, the corner is smoothed with a straight line - simply snipping the tip off.		This tool will give the option to chamfer the corner - where instead smoothing the corner with an arc, the corner is smoothed with a straight line - simply snipping the tip off.

	A good starting point for this tool would be the code from the node editor tool, because it already has UI code for selecting of nodes in a path. Code from this tool can be used, to fillet when the user clicks on a point.

	=== Back End ===		=== Back End ===

Joelholdsworth: /* Discussion */

2008-02-06T23:08:51Z

Discussion

← Older revision		Revision as of 23:08, 6 February 2008
Line 45:		Line 45:
	===Existing Code?===		===Existing Code?===
	* Q: Does anyone know of any existing code in the codebase that makes these sorts of calculations? So as to avoid reinventing the wheel and duplicating code?		* Q: Does anyone know of any existing code in the codebase that makes these sorts of calculations? So as to avoid reinventing the wheel and duplicating code?
	~~===A good place in the UI for this tool?===~~
	* Q: Does anyone have any thoughts about a good place to put this rather specialist tool in the UI? I worry that this tool while useful would only be useful occasionally, and would clutter the toolbox unhelpfully. Does anyone have any thoughts on this?
	~~===Good way to make radius interactive?===~~
	* This may be more of a fillet-version-2.0 feature, but I'm trying to think of the best way of allowing the user to select a filleting radius interactively. Perhaps some way of allowing them to interactively select the radius before the fillet actually applied - at which time I suppose the path's geometry will be changed permanently. Any thoughts?

Joelholdsworth: /* Back End */

2008-02-05T23:46:57Z

Back End

← Older revision		Revision as of 23:46, 5 February 2008
Line 36:		Line 36:

	Finding point X is mathematically trivial. Finding Y is very much harder, and will require a numerical solution to a set of simultaneous equations. Note that there could potentially be more than one possible solution (as shown in fig 2a), so the closest solution to the cusp along the the length of bezier should be selected.		Finding point X is mathematically trivial. Finding Y is very much harder, and will require a numerical solution to a set of simultaneous equations. Note that there could potentially be more than one possible solution (as shown in fig 2a), so the closest solution to the cusp along the the length of bezier should be selected.

			=== More ideas ===
			See [http://www.oberonplace.com/products/curveworks/index.htm]

	== TODO ==		== TODO ==

Joelholdsworth: /* Good way of make radius interactive? */

2008-02-05T18:35:50Z

Good way of make radius interactive?

← Older revision		Revision as of 18:35, 5 February 2008
Line 44:		Line 44:
	===A good place in the UI for this tool?===		===A good place in the UI for this tool?===
	* Q: Does anyone have any thoughts about a good place to put this rather specialist tool in the UI? I worry that this tool while useful would only be useful occasionally, and would clutter the toolbox unhelpfully. Does anyone have any thoughts on this?		* Q: Does anyone have any thoughts about a good place to put this rather specialist tool in the UI? I worry that this tool while useful would only be useful occasionally, and would clutter the toolbox unhelpfully. Does anyone have any thoughts on this?
	===Good way of make radius interactive?===		===Good way to make radius interactive?===
	* This may be more of a fillet-version-2.0 feature, but I'm trying to think of the best way of allowing the user to select a filleting radius interactively. Perhaps some way of allowing them to interactively select the radius before the fillet actually applied - at which time I suppose the path's geometry will be changed permanently. Any thoughts?		* This may be more of a fillet-version-2.0 feature, but I'm trying to think of the best way of allowing the user to select a filleting radius interactively. Perhaps some way of allowing them to interactively select the radius before the fillet actually applied - at which time I suppose the path's geometry will be changed permanently. Any thoughts?