![]() Probably be handy to have for many other cases too. (calculating sums using the entries from lists, etc) that would Non-monospace fonts would probably need some additional functions SCAD module that converts a string into a union of svgpath() statements. write a simple perl/awk/whatever script that reads in an svg fontįile (they look like ), extracts all entities and spits out an implement a function that can convert a string into an array ofģ. Path (I probaly could reuse some code from for this).Ģ. implement an svgpath() statement that creates a 2d object from an svg My current plan for this is the following:ġ. > This is on the TODO list - we're just slighty short of developerĪfaik freetype does not support rendering to a vector backend but always > or a higher-level library on top of that if we can find smth. > The real solution for text would be to interface directly with freetype, ![]() We are Elektropeople for a better living. The code comments has potential for improvements, so if anything is unclear it means someone should add more comments. These might all be a bit hard to get started on but there are lots of small issues in the TODO list.ĭon't hesitate to fire off questions. O Improve DXF import (requires some refactoring) to support more entities O General GUI polishing, including beating the editor a bit into shape (although I expect external editing to be Unit testing would also be nice, but less important right now. O Establish some kind of regression test framework. So from the top of my head, this what I see as important tasks (again, my personal opinion): Personally, I'd love to see more contributions :)ĭoc/TODO.txt is the current wishlist, although without any priority. Clifford and me atm.) is always subject to arbitrary prioritization, so interest is not so much of an issue as available time is. ![]() What is actually done by 'the devs' (i.e. > anything that you would you like to me have a look at? > features that obviously 'the devs' are not that interested in. > I have been tinkering with openscad myself, submitting patches for On Mar 19, 2010, at 11:55 PM, Giles Bathgate wrote: I haven't made any real progress on that. Sizes under 5mm tall) made up of only SQUARE, LINE, and CIRCLEĮntities. Simple block font (suitable for printing on a Makerbot with letter Given that I'm not up to my elbows in OpenSCAD code, I thought I mightĪpproach the problem of text in OpenSCAD models by hammering out a Create a new font by drawing vector entities that are only Supports? (which are LINE, CIRCLE, and SQUARE, IIRC, not evenĮLLIPSE). SEQEND? Rewrite autotrace to only use DXF entities that OpenSCAD > WARNING: Unsupported DXF Entity `SEQEND' (17x) in `foo.dxf'.Īdd code to OpenSCAD that knows how to process VERTEX, POLYLINE, and > WARNING: Unsupported DXF Entity `POLYLINE' (17x) in `foo.dxf'. > WARNING: Unsupported DXF Entity `VERTEX' (2713x) in `foo.dxf'. > Unfortunately I ran into a problem, it seems openscad doesn't like the ![]() Limitations in OpenSCAD will make this more than slightly difficult. > that could then be extruded in OpenSCAD. > so I thought I'd try to figure out a way to create a DXF file There are no easy tools that I have found, either. > I couldn't find any tools to easily do this. I've been trying to figure out a way to programmatically turn text ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |