TEMPLOT 3D PLUG TRACK - To get up to speed with this experimental project click here.
To watch an introductory video click here.
See the User Guide at Bexhill West.
Templot5 - To join this open-source project on GitHub click here.
For news of the latest on-going developments click here.
Templot5 is now included with Templot2 - download.
The Plug Track functions are experimental and still being developed. Some of the earlier pages of this topic are now out-of-date.
For an updated overview of this project see this topic. For some practical modelling aspects of using Plug Track see Building 3D Track.
The assumption is that you have your own machines on which to experiment, or helpful friends with machines. Please do not send Templot files to commercial laser cutting or 3D printing firms while this project is still experimental, because the results are unpredictable and possibly wasteful.
The Plug Track functions are experimental and still being developed.
For an updated overview of this project see this topic. For some practical modelling aspects of using Plug Track see Building 3D Track.
The assumption is that you have your own machines on which to experiment, or helpful friends with machines. Please do not send Templot files to commercial laser cutting or 3D printing firms while this project is still experimental, because the results are unpredictable and possibly wasteful.
Obviously it won't work without Nils's dtp units, but I'm posting it because it contains the sb_draw function which is also used for image and metafile exports.
I made a big mistake with 227 in leaving too long a gap from the previous update, almost 12 months. There was a reason for that -- the urgent need to swap to a new server and a new Templot Club forum software. But I allowed that to distract me too much from the unfinished 227 work. By the time I got back to it I had completely forgotten where I had got to, which bits were finished, which still had loose ends, and which I had barely started. I scribble notes in my notebook, but nowadays they become meaningless within hours. As a result of all that it has taken me 4 updates to fix the bugs in 227a and I still haven't finished.
I should have known better, because I made the same mistake 10 years ago with a long gap going from TemplotZero to Templot2. And at that time I could still remember what I had for breakfast.
I originally added the auto-updating function so that I could make future updates little and often. Small incremental changes which don't leave unfinished loose ends for months, by which time I have forgotten all about them. And which allow easy back-tracking if I mess up. I intend to stick to that plan from now on, making frequent update releases even if they don't contain very much.
How that fits in with posting the updated files here isn't too clear, but the first task is to get every file posted in its current state. I'm working through them alphabetically and so far I have got only as far as D, so even that is going to take a while. After that we can decide how best to feed future changes from Templot2 into T3.
This is the export function for DXF files for CAD. Also STL files when exporting in 3D.
This file includes a lot of my unfinished experimental stuff for 3D chairing. I'm not sure how you want to deal with that for T3? A lot of it may never see the light of day. On the other hand, going through it to create a fully functional redacted version would take me several hours.
p.s. large chunks of this file haven't changed for 25 years. Probably I would do things differently now.
You have my sympathy there. My memory has never been the best (I have NEVER been able to remember what I had for breakfast!) and leaving any kind of gap in development work never ends well for me.
... future updates little and often.... I intend to stick to that plan from now on, making frequent update releases even if they don't contain very much.... the first task is to get every file posted in its current state.....
Actually, we have not yet started to bring them together. Obviously it is going to be a fairly major job, and it may well be that the best strategy is a merge of the two. Whether we can automate any of it will only be clearer once we have pretty much a full set of files in T1.
I think I have been guided by cowardice so far. In the worst case, it will be a manual effort, probably based on functions, rather than files, which is another reason to leave it until we have them at least mostly in place.
Given the amount of work done on T2 in the interim, it may turn out that it is easier to layer our changes on top of these T1 sources rather than the other way round.
@Alistair Ward - have you had any brainwaves in this area?
Given the amount of work done on T2 in the interim, it may turn out that it is easier to layer our changes on top of these T1 sources rather than the other way round.
Bear in mind that I did a lot of work to make the first T3 compile in Lazarus, so if you use T1 as the basis you would need to do all that again.
For example, writing Parent:=pad_form; doesn't work, Lazarus has a different approach to child forms. Also EMF metafiles are not supported, so I replaced the Delphi code with direct calls to Windows API. Which remains non-portable to other platforms of course.
3 more.
keep_select.pas is a large file, contains the storage box and .box file handling.
That thought was the reasoning behind my earlier question about basing T1 on the earlier version that T3 was based on. That would have given us a common base from which both branches were derived, but that turned out to be impractical, so I think it will be a case of comparing T1 with the original (2019) T3 to ferret out those Lazarussian changes.
Hopefully they will be easily distinguished from the changes you have made for T2.
After that .... hmmmm .... well it will depend to some extent on what comes out of that process, I suppose.
At least it is a one-off exercise. Things should be easier after that.
Sorry about the delay in posting these files. Alphabetically I have reached the math_unit. It contains a lot of changes in 228, so there didn't seem much point in posting it until I have 228a released. Which will hopefully be in the next few days.
Here after a long gap (sorry) is math_unit.pas as at T2 version 233a released yesterday.
It changes almost daily while I'm working on the experimental chairing, but if I wait until it's finished it never will get posted. If anything is unclear, just ask.
Also the form math_unit.dfm, although there are no significant (or any) changes to that from previous versions. It's just a general utility form.
The small print:
Unless stated otherwise, all the material submitted to this web site is copyright and the property of the respective contributor.
You are welcome to use it for your own personal non-commercial purposes, link to it from other web sites, and use it in your own contributions to this web site.
If you want to publish any of this material elsewhere or use it commercially, you must first obtain the owner's permission to do so.
By submitting material to this web site you acknowledge that you are granting the owner of this web site
a non-exclusive, permanent, irrevocable, unlimited licence to use, publish, or re-publish the material on this web site,
and that you are also granting any user of this web site permission to use the material for their own personal non-commercial purposes and link to it from other web sites,
and that you accept full responsibility for the material submitted. If you do not agree to these terms, please do not register as a member
of Templot Club or make any use of this web site. The owner of this web site is not responsible for any content displayed on this web site other than his own contributions. The owner of this
web site may edit, modify or remove any content at any time without giving notice or reason.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Search
TEMPLOT is Martin's hobby project. Everyone is welcome to use it and join in the ongoing developments. Thanks for visiting Templot Club.
Thanks.
