![]() ![]() Definitely two different mindsets, though. I get my share of issues when I do things I probably shouldn’t, like change something that other things are dependent on, and then have to work my way back through and fix everything that broke, but I still think it’s well worth the effort to learn. Some of the add-on modules are amazing – like the one for bending sheet metal. I also invested quite a bit of time watching tutorials and learning FreeCAD, and I’m generally very pleased with it. I just wish there was a way to go back and insert intermediate operations after the fact without the whole thing blowing up in your face half the time. I grew up with DOS apps, so the appearance didn’t really put me off. It’s extremely efficiently built (I mean – come on – it uses ONE single executable file!) and it’s pretty easy to learn. I started out with SolveSpace a couple of years ago, and I concur with your assessment. Posted in 3d Printer hacks Tagged 3d modeling, cad, freecad, solvespace Post navigation And we’ve talked a lot about FreeCAD, too. So, generally, we reach for FreeCAD but it is mostly because of habit. We haven’t used it as much, though, and FreeCAD integrates nicely with OpenSCAD which we use a lot, too. Our choice? We often use FreeCAD although we like how SolveSpace handles certain things. Being able to see the differences between the two tools might convince you to learn one or the other or maybe even switch. You probably don’t need this particular design, but watching over someone’s shoulder while they do a complex design can be very valuable. There are many tools that can do that, including FreeCAD and SolveSpace, two programs that uses to create a complex compressor blade and it really shows the differences and similarities between the two tools. For example, you can create a vertical line and constrain other lines to be parallel, perpendicular, or form a given angle with that line. Serious modern designs tend to use parametric modeling where you don’t necessarily set dimensions and positions of everything but instead constrain the design by describing the relationship between different elements. this would be a treamendous effort with IMHO little chance of success.When you are ready to design real things, you’ll find simple CAD programs can be pretty limiting. You need to port FreeCAD objects and its property system over to a QObject based one. IMHO if you want to grand QML access to FreeCAD objects and allow manipulation you will have a hard time. The disadvantage of course was that QML did not have access to any freecad object, so one could not create a real new UI widget. ![]() The advantage for that is that all the complicated UI code did not to be redone. Then in QML I arranged them, added headers for control etc. That means I reused all the widgets, the tree, property editor etc.: I exposed them as QML types and only changed them slightly to fit visually in. ![]() My approach was to not rebuild the UI functionality, just use QML for the layout. It depends on how you want to interact with the system. Like QWidget, QtQuick is based on QObject and does everything through signals and slots, so all should be well. ![]() Perhaps if you get started studying some of ickby's work using the old pyside to create the proof of concept that is demonstrated in the first post of this thread? And start asking questions ?Īnd, hopefully, the FreeCad API will help me talking to the non-qtquick sections of the application through a QObject-API. In other words, you'll be navigating some undocumented waters in this process, most likely. As I was reading in a recent thread doxygen is better suited for c++ where as something like sphinx is better suited for python. The issue also to is that we're in the midst of deciding the best way to document FreeCAD since the codebase is a mixture between c++ and python. Mentors aren't hand-holders 's more like: ' if you take the time to ask a question that your researched well (which we'll be able to tell by the quality of the question) then we'd enjoy trying to provide a direction on how to solve it' The way I've seen it work is people start to dig and then they ask questions or help with solving a bug or they ask specific technical questions. What I need: guidance as to where my efforts would be best spent What I want: learn FreeCAD and be able to improve it Well, I see lot of people complaining about FreeCad ui in general, I'm a qtquick-for-cad specialist, this layout project is the only qtquick inroad i know of, si here I am. ![]()
0 Comments
Leave a Reply. |