Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #203081 > unrolled thread

librecad

Started byGene Heskett <gheskett@shentel.net>
First post2018-12-06 23:40 +0100
Last post2018-12-07 15:10 +0100
Articles 20 on this page of 47 — 11 participants

Back to article view | Back to linux.debian.user


Contents

  librecad Gene Heskett <gheskett@shentel.net> - 2018-12-06 23:40 +0100
    Re: librecad "hdv@gmail" <hdv.jadev@gmail.com> - 2018-12-06 23:50 +0100
      Re: librecad Yves <ydubeau@pm.me> - 2018-12-07 01:30 +0100
        Re: librecad Doug <dmcgarrett@optonline.net> - 2018-12-07 02:10 +0100
          Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 03:10 +0100
        Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 02:50 +0100
      Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 01:50 +0100
        Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-07 02:50 +0100
          Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 03:20 +0100
            Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-07 03:30 +0100
              Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 04:40 +0100
              Re: librecad Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-12-07 19:50 +0100
                Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-07 20:20 +0100
                  Re: librecad Greg Wooledge <wooledg@eeg.ccf.org> - 2018-12-07 20:30 +0100
                  Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 00:50 +0100
                    Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-08 02:00 +0100
                      Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 03:50 +0100
                        Re: librecad Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-12-08 05:20 +0100
                          Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 06:50 +0100
                            Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-08 14:40 +0100
                              Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 20:00 +0100
                                Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-08 20:50 +0100
                                  Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 21:10 +0100
                                    Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-08 21:30 +0100
                                      Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 22:00 +0100
                                    Unpacking a large zipfile, was Re: librecad David Wright <deblis@lionunicorn.co.uk> - 2018-12-09 00:20 +0100
                                Re: librecad "Jeremy Nicoll" <jn.ml.dbn.25@letterboxes.org> - 2018-12-09 00:10 +0100
                                  Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-09 01:50 +0100
                                  Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-09 02:50 +0100
                                    Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-09 03:20 +0100
                                      Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-09 03:30 +0100
                                    Re: librecad "Jeremy Nicoll" <jn.ml.dbn.25@letterboxes.org> - 2018-12-09 03:30 +0100
                Re: librecad (was) Gene Heskett <gheskett@shentel.net> - 2018-12-08 00:40 +0100
          Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 04:20 +0100
          Re: librecad Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2018-12-07 04:50 +0100
        Re: librecad "hdv@gmail" <hdv.jadev@gmail.com> - 2018-12-07 10:30 +0100
          Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 14:50 +0100
            Re: librecad "hdv@gmail" <hdv.jadev@gmail.com> - 2018-12-07 15:10 +0100
        Re: librecad Joe <joe@jretrading.com> - 2018-12-07 11:00 +0100
          Re: librecad "hdv@gmail" <hdv.jadev@gmail.com> - 2018-12-07 11:30 +0100
    Re: librecad "Jeremy Nicoll" <jn.ml.dbn.25@letterboxes.org> - 2018-12-07 07:50 +0100
      Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-07 14:50 +0100
        Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-07 16:20 +0100
          Re: librecad Erik Christiansen <dvalin@internode.on.net> - 2018-12-08 03:00 +0100
            Re: librecad Gene Heskett <gheskett@shentel.net> - 2018-12-08 04:30 +0100
          Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-08 04:50 +0100
      Re: librecad John Hasler <jhasler@newsguy.com> - 2018-12-07 15:10 +0100

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →


#203177

FromGene Heskett <gheskett@shentel.net>
Date2018-12-08 20:00 +0100
Message-ID<x2PZv-43D-1@gated-at.bofh.it>
In reply to#203165
On Saturday 08 December 2018 08:38:15 John Hasler wrote:

> Gene writes:
> > LinuxCNC depends on a low latency IRQ response.
> > ...
>
> We understand all that, and I understand and agree with the "If it
> aint broke don't fix it" philosophy that leads to running "obsolete"
> computers and software in machine controls.  What does it have to do
> with the machine you run your CAD software on?

Nothing John, except the vertical, even seemingly leaning toward the 
beginner, learning curve to really put that software to productive use. 
I've started to do something in freecad several times, I don't have it 
here anymore, but the lack of a plainly marked, multiple step undo gets 
me into a dead end box that results in a quit w/o save every time. Maybe 
its there, but I've not found it. If I build a tool changer for the 
biggest mill I have, I expect that I'll need to use its facility to 
couple moving parts to see if there's any interference between stuff 
just to remove the mistakes I'll no doubt make if I just write the gcode 
to generate the thing one part at a time.

Unfortunately, even the src.zip has disappeared from github.
But poking around I did find FreeCAD-master.zip, and its copying to ~/src 
right now. Looks like a pretty long list of dependencies from the wiki 
on building it. Couple pages if printed.  So we'll see if its still 
buildable on wheezy. And this is probably going to be a long process. So 
I'll send this and advise success/fail later.

Thanks John.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203179

FromJohn Hasler <jhasler@newsguy.com>
Date2018-12-08 20:50 +0100
Message-ID<x2QLT-4zF-1@gated-at.bofh.it>
In reply to#203177
Gene writes:
> I've started to do something in freecad several times, I don't have it
> here anymore, but the lack of a plainly marked, multiple step undo
> gets me into a dead end box that results in a quit w/o save every
> time.

I find that undoing one action at a time almost always suffices.  To
save myself when I get hopelessly befuddled I do checkpoint saves from
time to time.

Older releases of Freecad are here:

https://github.com/FreeCAD/FreeCAD/releases

But why not build from source?

https://www.freecadweb.org/wiki/CompileOnUnix

I've found in the past that it builds quite easily on Debian.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]


#203180

FromGene Heskett <gheskett@shentel.net>
Date2018-12-08 21:10 +0100
Message-ID<x2R5g-4W8-9@gated-at.bofh.it>
In reply to#203179
On Saturday 08 December 2018 14:42:06 John Hasler wrote:

> Gene writes:
> > I've started to do something in freecad several times, I don't have
> > it here anymore, but the lack of a plainly marked, multiple step
> > undo gets me into a dead end box that results in a quit w/o save
> > every time.
>
> I find that undoing one action at a time almost always suffices.  To
> save myself when I get hopelessly befuddled I do checkpoint saves from
> time to time.
>
> Older releases of Freecad are here:
>
> https://github.com/FreeCAD/FreeCAD/releases
>
> But why not build from source?
>
> https://www.freecadweb.org/wiki/CompileOnUnix
>
> I've found in the past that it builds quite easily on Debian.

Thats what I'm embarking on doing, building master from src. but the zip 
seems to be a problem, mc is unpacking it and copying to ~/src, doubling 
the 180 some megs of the zip, but with mc piping both, its watch paint 
dry slow, about 40 kilobytes/sec of 360+ megs of src. So its not yet 
done creating a source tree from the zip.  About 85% done when I last 
took a peek a minute ago.

Thanks John.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203181

FromJohn Hasler <jhasler@newsguy.com>
Date2018-12-08 21:30 +0100
Message-ID<x2RoB-52Q-1@gated-at.bofh.it>
In reply to#203180
Gene writes:
> Thats what I'm embarking on doing, building master from src. but the
> zip seems to be a problem

That's doing it the hard way.  Use git as suggested here:

https://www.freecadweb.org/wiki/CompileOnUnix#Getting_the_source

It works.

-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]


#203182

FromGene Heskett <gheskett@shentel.net>
Date2018-12-08 22:00 +0100
Message-ID<x2RRE-5cI-3@gated-at.bofh.it>
In reply to#203181
On Saturday 08 December 2018 15:22:36 John Hasler wrote:

> Gene writes:
> > Thats what I'm embarking on doing, building master from src. but the
> > zip seems to be a problem
>
> That's doing it the hard way.  Use git as suggested here:
>
> https://www.freecadweb.org/wiki/CompileOnUnix#Getting_the_source
>
> It works.

But its list of requires includes a bunch of 64 bit stuff. The wiki has 
an apt command to install all the dependencies, and I can't get that 
to work on a 32 bit install. It first can't find libvtk6.dev, remove 
that from the list and still get this bailout:
================================
The following packages have unmet dependencies:
 libsimage-dev : Depends: libsndfile1-dev but it is not going to be installed
 libxerces-c-dev : Depends: libxerces-c3.1 (= 3.1.1-3+deb7u2) but 3.1.1-3+deb7u5 is to be installed
 qt4-dev-tools : Depends: libqt4-declarative (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqt4-help (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqt4-network (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqt4-sql (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqt4-xml (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqt4-xmlpatterns (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqtcore4 (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqtdbus4 (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
                 Depends: libqtgui4 (= 4:4.8.2+dfsg-11) but 4:4.8.6+git64-g5dc8b2b+dfsg-3~bpo70+1 is to be installed
 qtchooser : Breaks: qt4-dev-tools (<= 4:4.8.4+dfsg-1~) but 4:4.8.2+dfsg-11 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

It will take a bit of effort to resolve all that. Some of which may not be resolvable.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203184 — Unpacking a large zipfile, was Re: librecad

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2018-12-09 00:20 +0100
SubjectUnpacking a large zipfile, was Re: librecad
Message-ID<x2U37-6Gq-1@gated-at.bofh.it>
In reply to#203180
On Sat 08 Dec 2018 at 15:01:11 (-0500), Gene Heskett wrote:
> Thats what I'm embarking on doing, building master from src. but the zip 
> seems to be a problem, mc is unpacking it and copying to ~/src, doubling 
> the 180 some megs of the zip, but with mc piping both, its watch paint 
> dry slow, about 40 kilobytes/sec of 360+ megs of src. So its not yet 
> done creating a source tree from the zip.  About 85% done when I last 
> took a peek a minute ago.

Unpacking a zipfile containing a large number of files with mc is a
really bad idea. For example, a 5245 file zip with 199 subdirectories
took unzip about 34 seconds to unpack. mc took over 16 minutes.
Why? Because it ran over 5245 uzip processes, one after the other.
Stick to using it to inspect zipfiles and perhaps unzipping just the
odd file or two.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#203183

From"Jeremy Nicoll" <jn.ml.dbn.25@letterboxes.org>
Date2018-12-09 00:10 +0100
Message-ID<x2TTs-6Dd-7@gated-at.bofh.it>
In reply to#203177
On Sat, 8 Dec 2018, at 18:59, Gene Heskett wrote:

> ... but the lack of a plainly marked, multiple step undo gets 
> me into a dead end box that results in a quit w/o save every time. 

I had a similar problem with a music-typesetting package under
Windows.

I guess a versioning file system (as discussed here fairly recently)
would help, but I don't have one.

Eventually I solved it with a script which examines a set of files 
(I specify a pattern for those) in the folder I'm working in.   When 
it starts and every few seconds (eg 10 secs) afterwards, it looks at
the files whose name matches that pattern.

For every file it finds for which there is not a corresponding backup
copy, it makes one.  A backup copy of a file has

    (svd@yyyymmdd-hhmmss)

appended to its extensionless leafname, where the date & time 
correspond to the time the backed-up file was last saved (not 
the time that this script saved the backup). 

So as soon as the script starts it makes a copy of each matching 
file (assuming none of those had prior backup copies) then 
whenever such a file changes and is written to disk again, another
backup is made.    So eg 

    Some song or other.pqr                   could yield:
                                                     
    Some song or other (svd@20120716-184500).pqr         
    Some song or other (svd@20120716-190723).pqr   etc   


I experimented with the monitor delay, and found (on a modern 
PC) when not using a filename pattern that matched huge numbers
of files, that there was no performance hit at all whether I looked at
the files every second or two or a good deal less often.  I made the
script pop-up a message box though when it had successfully made
a copy, and got into the habit of waiting for that confirmation every
time I'd just saved a file.

Rather than writing the script, what took longest to do was getting 
used to remembering to save the file(s) I was working on so often.
I used to keep detailed notes about I was doing to the musical score, 
as well, and stored the incrementally changing backup filenames in
the notes so it was easy to go back to previous points.

Not only was this useful for undoing my mistakes, it proved useful
for finding bugs in the typesetter AND being able to send the author
of that test files and 'what to do to recreate the problem' notes.  It
was quite often a day or two after I made some change to a file that
I found repercussions of that change, so notes (to help me find the
key files) were really important.


The script itself would run until stopped.  I controlled that by 
having each script generate a carefully-named flagfile and as soon
as that was deleted the corresponding script would stop.    I could 
have multiple instances of the script running at once, and both the 
flagfiles and the typesetter (or whatever else) files were kept in folders 
visible from other machines/userids (all me though).  So flagfiles had 
in them

   - a representation of the monitored filename pattern
   - the monitor time interval
   - the machine name
   - the userid name
   - the time the script started
   - the pid under it was running

The pid was there so that when writing and testing the script
I could tell which was which in taskmanager, which saw them 
all as the same thing - an instance of the script language's 
interpreter being run.


The script is written in ooREXX; anyone who wants it can have
a copy.  I expect somethig similar could be written in loads of 
other langages, but it's the one I know best.

-- 
Jeremy Nicoll - my opinions are my own.

[toc] | [prev] | [next] | [standalone]


#203188

FromJohn Hasler <jhasler@newsguy.com>
Date2018-12-09 01:50 +0100
Message-ID<x2Vse-7oT-9@gated-at.bofh.it>
In reply to#203183
The latest Freecad version claims to have a robust undo-redo stack.  I
haven't really put it to the test yet, though.

Even infinite undo does not always suffice.  You may not remember
exactly when and how you went off the rails, or you may have other
reasons to want to look back.  version control is the answer, and I just
discovered that there is an add-on for exactly that:

https://www.freecadweb.org/wiki/Arch_Git
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]


#203193

FromGene Heskett <gheskett@shentel.net>
Date2018-12-09 02:50 +0100
Message-ID<x2Woh-7Xp-7@gated-at.bofh.it>
In reply to#203183
On Saturday 08 December 2018 17:53:01 Jeremy Nicoll wrote:
[...]
> The pid was there so that when writing and testing the script
> I could tell which was which in taskmanager, which saw them
> all as the same thing - an instance of the script language's
> interpreter being run.
>
I can see where that could, if you "got your head" around it, be pretty 
handy. But half or more of my gcode mistakes are typu's. And the rs274D 
interpretor is very VERY good at recommending you learn to type. ;-)

> The script is written in ooREXX; anyone who wants it can have
> a copy.  I expect somethig similar could be written in loads of
> other langages, but it's the one I know best.

Back when we did most of our scripting on amiga's, ARexx was the language 
to top all the rest, but then when we got tired of the instability, and 
I went to linux, where I found that neither Rexx nor Regina could get 
past line 2 of any of my utilities without barfing all over itself as 
neither of the "next gen" rexx's weren't anything like ARexx, which Bill 
Hawes never got a damned dime from commode door for writing it, but it 
had calls into every facility amigados had, so there weren't any fences 
between what you wanted it to do, and what you could do. So I fell back 
to bash. And while the bash docs are at least 250 pages, its not ARexx. 
But it handles the coupling between fetchmail/procmail and kmail, so I 
have virtually nothing to but reply and send, and hit the plus key to 
read the next message. Computers are to reduce one's work, not multiply 
it times 15. Call me lazy, but it "works for me".. 

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203194

FromJohn Hasler <jhasler@newsguy.com>
Date2018-12-09 03:20 +0100
Message-ID<x2WRj-8lX-1@gated-at.bofh.it>
In reply to#203193
If you want to move on from REXX look at Tcl.
-- 
John Hasler 
jhasler@newsguy.com
Elmwood, WI USA

[toc] | [prev] | [next] | [standalone]


#203195

FromGene Heskett <gheskett@shentel.net>
Date2018-12-09 03:30 +0100
Message-ID<x2X0Z-8pa-1@gated-at.bofh.it>
In reply to#203194
On Saturday 08 December 2018 21:10:13 John Hasler wrote:

> If you want to move on from REXX look at Tcl.

Linuxcnc uses a bunch of that in its gui's, which it has several flavors 
of,



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203196

From"Jeremy Nicoll" <jn.ml.dbn.25@letterboxes.org>
Date2018-12-09 03:30 +0100
Message-ID<x2X10-8pa-5@gated-at.bofh.it>
In reply to#203193
On Sun, 9 Dec 2018, at 01:47, Gene Heskett wrote:
> On Saturday 08 December 2018 17:53:01 Jeremy Nicoll wrote:
> [...]
> > The pid was there so that when writing and testing the script
> > I could tell which was which in taskmanager, which saw them
> > all as the same thing - an instance of the script language's
> > interpreter being run.
> >
> I can see where that could, if you "got your head" around it, be pretty 
> handy. But half or more of my gcode mistakes are typu's. And the rs274D 
> interpretor is very VERY good at recommending you learn to type. ;-)

In the music typesetting thing, one of the BIG problems was that a
sequence of things done via its GUI (obviously) changed the file, but
apart from my errors, bugs in the software meant that a session 
reloaded from a previously-saved file didn't always behave as the 
edit session where one had made the changes behaved.

I haven't used it for a while but I'm sorely tempted to learn how to use
another system [Philip Hazel (of Exim & PCRE)'s PMW], where plain text
files are interpreted to create PostScript scores.   I think that the non-
GUI approach suits me better.


> > The script is written in ooREXX

> Back when we did most of our scripting on amiga's, ARexx was the language 
> to top all the rest...

Most of my REXX was written on MVS (now z/OS) systems and was what's 
commonly called 'Classic REXX', somewhat predating even ANSI REXX.  On
a PC, I use ooREXX but nearly none of its oo capabilities - one can write 
code that's very similar to Classic non-oo REXX.    

> Computers are to reduce one's work, not multiply  it times 15. Call me 
> lazy, but it "works for me"..

I'm no longer wholly enthusiastic about learning completely new things
(because of chronic illness) but I keep meaning to try to get to grips with 
Linux... which is why I lurk here.   If and when I do, I expect to keep using 
ooREXX.

-- 
Jeremy Nicoll - my opinions are my own.

[toc] | [prev] | [next] | [standalone]


#203143 — Re: librecad (was)

FromGene Heskett <gheskett@shentel.net>
Date2018-12-08 00:40 +0100
SubjectRe: librecad (was)
Message-ID<x2xSV-1wL-11@gated-at.bofh.it>
In reply to#203133
And except for fine tuning the locations of a couple db25 cutouts, which 
I'll have to carve a test piece in wood to check and drilling a hole for 
the line cord packing gland, its done.

 I guess I'll have to wait, and measure for hole size when they arrive 
since the mounting hole is specified as 15.2mm or .5". Now really what 
size is it since 15.2 is maybe 4 thou smaller than .6". Something tells 
me that was a badly un-calibrated eyeball that measured it.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203098

FromGene Heskett <gheskett@shentel.net>
Date2018-12-07 04:20 +0100
Message-ID<x2eQh-6Sn-3@gated-at.bofh.it>
In reply to#203094
On Thursday 06 December 2018 20:41:43 John Hasler wrote:

> Have you looked at Freecad and Solvespace?
solvespace won't build here, git error maybe? I'll try some more in the 
morning.

Thanks John.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203103

FromJoe Pfeiffer <pfeiffer@cs.nmsu.edu>
Date2018-12-07 04:50 +0100
Message-ID<x2fjj-72h-1@gated-at.bofh.it>
In reply to#203094
John Hasler <jhasler@newsguy.com> writes:

> Have you looked at Freecad and Solvespace?

Note freecad is 3D, and his needs are apparently 2D.

Though I will relate that my (brief) acquaintance with freecad led me to
decide to just write Python scripts using python-occ to generate my
models.

[toc] | [prev] | [next] | [standalone]


#203111

From"hdv@gmail" <hdv.jadev@gmail.com>
Date2018-12-07 10:30 +0100
Message-ID<x2kCl-1Rz-5@gated-at.bofh.it>
In reply to#203088
On 12/7/18 1:46 AM, Gene Heskett wrote:
> On Thursday 06 December 2018 17:48:21 hdv@gmail wrote:
> 
>> On 12/6/18 11:31 PM, Gene Heskett wrote:
>>> Greetings all;
>>>
>>> The librecad in the debian repos for wheezy is nearly a decade old,
>>> v-1.02. There are V2-* stuff that still runs on QT4 some of which is
>>> already installed.
>>>
>>> Is there a repo where I can source a newer version than 1.02 without
>>> destroying my system?
>>>
>>> 1.02 is so old the u-tube tuts are nearly worthless, yet it shows
>>> promise of being able to lay out a boxes rear panel with 13
>>> connections thru it. which is what I am trying to do.
>>>
>>> Or is there an even better 2d app for such?
>>>
>>> Thanks everybody.
>>
>> Hai Gene,
>>
>> Some time ago I tried LibreCAD as well and soon had to conclude there
>> were too many issues with it to proceed. Meanwhile I've adopted QCAD
>> (the Pro version) 
> 
> And that I'd assume is not in the repo's for wheezy.  I have looked at 
> the earlier version that is in the repos and found it much more 
> confusing, to the point I'd be doomed from the gitgo. And I'd still have 
> to write the gcode to make it.
> 
> I have all the measurements written out, so if a decent libreCAD can't be 
> had, I'll just write it in gcode and feed it direct to LinuxCNC. With 
> measurements in hand I can probably have working code by the time I get 
> a good lens in front of the left eye. I've had cataract surgery in both 
> eyes now, and am basically waiting for a stable glaucoma pressure 
> reading so a script for a lens won't have to be done 2 or 3 times before 
> its long term usable.
> 
> Thanks for the observations about qcad.  Is the pro version offered 
> commercially?

It is. But the price is real good. If I remember correctly I paid €33 for it.
And it comes with a CAM module, so you can easily have your designs CNC'ed. I
only once needed support, but that time it was outstanding. Installation on my
system went without any hitch at all. Best of all, it is contained, so you don't
have to hunt for files all over your system if you decide it isn't the right
solution for you. There is a community edition that is free. So before spending
your money you can first test it to find out if you like it.

You can use command line instructions or just click on the associated buttons to
draw what you want. Whatever fits you drawing style best. I find myself using
both styles to be honest (I used to be a command line only type, but I got lazy
along the way, it seems  ;-) ).

I am not sure how familiar you are with the AutoCAD-type of interfaces, but if
you would need some "help", there is a book available. The application has
built-in help, but that is about the available commands and how to use them. The
book is more about how to draw in QCAD.

P.S. I am not in any way associated with them (except for being a customer).

Grx HdV

[toc] | [prev] | [next] | [standalone]


#203120

FromGene Heskett <gheskett@shentel.net>
Date2018-12-07 14:50 +0100
Message-ID<x2oFY-4dn-11@gated-at.bofh.it>
In reply to#203111
On Friday 07 December 2018 04:27:23 hdv@gmail wrote:

> On 12/7/18 1:46 AM, Gene Heskett wrote:
> > On Thursday 06 December 2018 17:48:21 hdv@gmail wrote:
> >> On 12/6/18 11:31 PM, Gene Heskett wrote:
> >>> Greetings all;
> >>>
> >>> The librecad in the debian repos for wheezy is nearly a decade
> >>> old, v-1.02. There are V2-* stuff that still runs on QT4 some of
> >>> which is already installed.
> >>>
> >>> Is there a repo where I can source a newer version than 1.02
> >>> without destroying my system?
> >>>
> >>> 1.02 is so old the u-tube tuts are nearly worthless, yet it shows
> >>> promise of being able to lay out a boxes rear panel with 13
> >>> connections thru it. which is what I am trying to do.
> >>>
> >>> Or is there an even better 2d app for such?
> >>>
> >>> Thanks everybody.
> >>
> >> Hai Gene,
> >>
> >> Some time ago I tried LibreCAD as well and soon had to conclude
> >> there were too many issues with it to proceed. Meanwhile I've
> >> adopted QCAD (the Pro version)
> >
> > And that I'd assume is not in the repo's for wheezy.  I have looked
> > at the earlier version that is in the repos and found it much more
> > confusing, to the point I'd be doomed from the gitgo. And I'd still
> > have to write the gcode to make it.
> >
> > I have all the measurements written out, so if a decent libreCAD
> > can't be had, I'll just write it in gcode and feed it direct to
> > LinuxCNC. With measurements in hand I can probably have working code
> > by the time I get a good lens in front of the left eye. I've had
> > cataract surgery in both eyes now, and am basically waiting for a
> > stable glaucoma pressure reading so a script for a lens won't have
> > to be done 2 or 3 times before its long term usable.
> >
> > Thanks for the observations about qcad.  Is the pro version offered
> > commercially?
>
> It is. But the price is real good. If I remember correctly I paid €33
> for it. And it comes with a CAM module, so you can easily have your
> designs CNC'ed. I only once needed support, but that time it was
> outstanding. Installation on my system went without any hitch at all.
> Best of all, it is contained, so you don't have to hunt for files all
> over your system if you decide it isn't the right solution for you.
> There is a community edition that is free. So before spending your
> money you can first test it to find out if you like it.
>
> You can use command line instructions or just click on the associated
> buttons to draw what you want. Whatever fits you drawing style best. I
> find myself using both styles to be honest (I used to be a command
> line only type, but I got lazy along the way, it seems  ;-) ).
>
> I am not sure how familiar you are with the AutoCAD-type of
> interfaces, but if you would need some "help", there is a book
> available. The application has built-in help, but that is about the
> available commands and how to use them. The book is more about how to
> draw in QCAD.
>
> P.S. I am not in any way associated with them (except for being a
> customer).
>
> Grx HdV

All very encouraging. But in about 4 hours, I've written and tested about 
90 LOC which is about 75% of what I need to have this do. :) So I think 
I'll continue on this path. :)

Thank you.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#203122

From"hdv@gmail" <hdv.jadev@gmail.com>
Date2018-12-07 15:10 +0100
Message-ID<x2oZl-4ze-23@gated-at.bofh.it>
In reply to#203120
On 12/7/18 2:45 PM, Gene Heskett wrote:

> All very encouraging. But in about 4 hours, I've written and tested about 
> 90 LOC which is about 75% of what I need to have this do. :) So I think 
> I'll continue on this path. :)

There's always more than one way to scratch an itch...  ;-)

> Thank you.

You're welcome.

Grx HdV

[toc] | [prev] | [next] | [standalone]


#203112

FromJoe <joe@jretrading.com>
Date2018-12-07 11:00 +0100
Message-ID<x2l5o-21m-3@gated-at.bofh.it>
In reply to#203088
On Thu, 6 Dec 2018 19:46:42 -0500
Gene Heskett <gheskett@shentel.net> wrote:

> On Thursday 06 December 2018 17:48:21 hdv@gmail wrote:
> 

> >
> > Some time ago I tried LibreCAD as well and soon had to conclude
> > there were too many issues with it to proceed. Meanwhile I've
> > adopted QCAD (the Pro version)   

I've found a couple of things that aren't quite right in LibreCAD, but
not serious ones. I used the free QCAD up to the point of the fork, and
it was really quite buggy for a long time. The zoom went wild at some
magnifications, among other things. I jumped to LibreCAD when it
appeared and I'm reasonably happy with it. All the bad QCAD bugs were
fixed long ago, and I would assume they are fixed in QCAD now, if only
by porting from LibreCAD. I do only use it occasionally, maybe twelve
hours a year, so it may be much more irritating to a heavy user.

> 
> And that I'd assume is not in the repo's for wheezy.  I have looked
> at the earlier version that is in the repos and found it much more 
> confusing, to the point I'd be doomed from the gitgo. And I'd still
> have to write the gcode to make it.
> 

Is there no way you can get hold of, say, an old laptop and run unstable
just for this? Version 2.1.3 currently. My poor little nine-year-old
netbook was just about useable for this when hooked up to a large
screen, though it's got stretch on it at the moment. Stretch apparently
has 2.1.2 and I don't recall much major happening in the last year or
two, well, let's say I haven't noticed anything new or fixed. (edit)
looking at the changelog, there doesn't seem like anything that I would
notice, I'm on Qt 5.11 but I wouldn't build from source.

-- 
Joe
-- 
Joe

[toc] | [prev] | [next] | [standalone]


#203115

From"hdv@gmail" <hdv.jadev@gmail.com>
Date2018-12-07 11:30 +0100
Message-ID<x2lyp-2qj-1@gated-at.bofh.it>
In reply to#203112
On 12/7/18 10:50 AM, Joe wrote:
> On Thu, 6 Dec 2018 19:46:42 -0500
> Gene Heskett <gheskett@shentel.net> wrote:
> 
>> On Thursday 06 December 2018 17:48:21 hdv@gmail wrote:
>>
> 
>>>
>>> Some time ago I tried LibreCAD as well and soon had to conclude
>>> there were too many issues with it to proceed. Meanwhile I've
>>> adopted QCAD (the Pro version)   
> 
> I've found a couple of things that aren't quite right in LibreCAD, but
> not serious ones. I used the free QCAD up to the point of the fork, and
> it was really quite buggy for a long time. The zoom went wild at some
> magnifications, among other things. I jumped to LibreCAD when it
> appeared and I'm reasonably happy with it. All the bad QCAD bugs were
> fixed long ago, and I would assume they are fixed in QCAD now, if only
> by porting from LibreCAD. I do only use it occasionally, maybe twelve
> hours a year, so it may be much more irritating to a heavy user.

I am happy that I managed to escape that.  ;-)

I've been using QCAD for almost 2 years now (started with 3.16). The fork was a
long time before that. Maybe that was time enough to resolve a lot of the
issues? My impression was/is that development on LibreCAD has somewhat stalled.
I might be mistaken on that. Anyway, when I tested it it had a fair share of
issues that made me look for an alternative.

QCAD has been improving steadily during the time I've used it. On the other
hand, I am no "power user", thus it might be that I just didn't encounter the
things you've had to deal with. In the end it could be a matter of tastes if you
prefer LibreCAD over QCAD or the other way around. Some people like the latter
more, and others the first. For example, I prefer the UI of QCAD over that of
LibreCAD (even if both of them are derived from the same AutoCAD-type of
interface). I don't think it matters a lot. The problems using LibreCAD and the
lack thereof when I tried QCAD made me switch, because that mattered to me. I
needed to crank out some drawings and didn't want to struggle to do it. I am
sure there will be people that had the exact opposite experience and choose
LibreCAD.

If I had to make an estimate I think I might have spent about 250 hours using it
to draw aerospace and industrial machinery parts. Lately I've started using it
more for myself (to draw plans for woodworking projects). There were some minor
quirks, but nothing major. Luckily. However, I haven't tried the CAM stuff yet.
So I can't vouch for that, as I simply don't know how good it is.

Grx HdV

[toc] | [prev] | [next] | [standalone]


Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | linux.debian.user


csiph-web