On Sat, 2011-09-10 at 10:19 +0530, Abhijit Kshirsagar wrote:
On Thu, Sep 8, 2011 at 22:20, Dan Roganti ragoo...@gmail.com wrote:
I wouldn't say wipeout, from looking at the current state of
documentation, there's been a huge amount of work done there. I would
suggest just making some
Hi all...
The problem is solved with the latest gnetlist (1.7.1). Thanks so much!
I will be documenting the library of bond graph elements (symbols and
definitions). Just wanted to know if anyone uses bond graphs for
simulation?
Regards,
~Abhijit
On Fri, Sep 9, 2011 at 18:08, Peter Clifton
On Sat, 2011-09-10 at 19:49 +0530, Abhijit Kshirsagar wrote:
Hi all...
The problem is solved with the latest gnetlist (1.7.1). Thanks so much!
I will be documenting the library of bond graph elements (symbols and
definitions). Just wanted to know if anyone uses bond graphs for
simulation?
On Sat, 2011-09-10 at 13:35 +0200, Stefan Salewski wrote:
A lot of documentation can be bad.
Consider the toys from the big company with the damaged fruit: A reason
for the success of the toys is that documentations seems to be not
needed.
A lot of documentation can make people think that
Very good point! and if I may add: ALL contained in ONE place,
sufficiently reviewed to make it 100% correct with the current version
of the tool(s) it is intended to be use with (and stated in the
document itself).
From my experience, ONE person is accepted as the book boss and
On Sat, Sep 10, 2011 at 4:35 AM, Stefan Salewski m...@ssalewski.de wrote:
Consider the toys from the big company with the damaged fruit: A reason
for the success of the toys is that documentations seems to be not
needed.
I agree with the idea, but the thing is, the Apple software that
doesn't
On 09/10/2011 10:35 AM, Jared Casper wrote:
A reason
for the success of the toys is that documentations seems to be not
needed.
I agree with the idea, but the thing is, the Apple software that
doesn't need documentation doesn't do a whole lot.
Yes, and the hobby CAD users want it to be
There is a problem that seems to occur often with open source software. Since
it is created by
programmers to scratch their particular itch, they are more concerned with
the programming and
getting it working to solve their problem. Other than bug fixes that affect
their use of the program,
A rating function for the documentations would be handy. I think this
feedback is very important and you get an overview what is good or
bad. Guess, the implemantation isn't tricky.
best regards
Felix
___
geda-user mailing list
On Sep 10, 2011, at 8:19 AM, Abhijit Kshirsagar wrote:
The problem is solved with the latest gnetlist (1.7.1). Thanks so much!
I will be documenting the library of bond graph elements (symbols and
definitions). Just wanted to know if anyone uses bond graphs for
simulation?
No, but I might
I agree with the idea, but the thing is, the Apple software that
doesn't need documentation doesn't do a whole lot.
Ahem, Hyper Card, people are still mourning for it.
-CN
___
geda-user mailing list
geda-user@moria.seul.org
Hello,
I'm using PCB from git master (9dde48253c..) and it segfaults
when the Route Styles button is clicked. Here's how to reproduce:
1. use PCB to make an empty pcb file
2. start PCB again and load the empty file with File - Load layout
3. choose Power route style, then click on the Route
Am 10.09.2011 um 13:35 schrieb Stefan Salewski:
A lot of documentation can be bad.
Ha! Now that's exactly the right answer to somebody offering writing
documentation.
Consider the toys from the big company with the damaged fruit: A
reason
for the success of the toys is that
On Sat, Sep 10, 2011 at 4:12 PM, Markus Hitter m...@jump-ing.de wrote:
Using a keyboard to do
anything but writing text is a thing of the past, to start with.
I couldn't disagree more. I only want to use the mouse for things
that absolutely require a mouse (drawing things mostly). If I have
On 09/10/2011 06:20 PM, Jared Casper wrote:
gEDA is as far away from Fritzing as Word is from NotePad.
Jared
But they both have many of the same low level primitive commands and actions.
I think you could base two apps on the same code and many of the users would
never know,
since some are
On Sat, Sep 10, 2011 at 6:09 PM, John Griessen j...@ecosensory.com wrote:
But they both have many of the same low level primitive commands and
actions.
I think you could base two apps on the same code and many of the users would
never know,
since some are so little into craft and so into
Ivan Stankovic wrote:
I'm using PCB from git master (9dde48253c..) and it segfaults
when the Route Styles button is clicked. Here's how to reproduce:
1. use PCB to make an empty pcb file
2. start PCB again and load the empty file with File - Load layout
3. choose Power route style, then
hi! im truly interest in this article... do you still have it? thanks for all
the info. My secondary e-mail is: droa.or...@gmail.com.
Bob Paddock wrote:
In the past (see list archives) I'd mentioned that I'd worked with a
LPKF ProtoMat S62 circuit board router. The owner of that
On 11/09/2011 9:13 AM, Markus Hitter [1]m...@jump-ing.de wrote:
But how close is gEDA here? To be honest, I think gEDA couldn't be
farther away. It can't even agree on an equivalent GUI design for both
major tools, gschem and pcb. Instead of doing something about that,
lots of
On Sat, Sep 10, 2011 at 04:20:27PM -0700, Jared Casper wrote:
On Sat, Sep 10, 2011 at 4:12 PM, Markus Hitter m...@jump-ing.de wrote:
Using a keyboard to do
anything but writing text is a thing of the past, to start with.
I couldn't disagree more. I only want to use the mouse for things
On Sun, Sep 11, 2011 at 04:53:08AM +0200, Kai-Martin Knaak wrote:
Ivan Stankovic wrote:
I'm using PCB from git master (9dde48253c..) and it segfaults
when the Route Styles button is clicked. Here's how to reproduce:
1. use PCB to make an empty pcb file
2. start PCB again and load the
On Sun, Sep 11, 2011 at 04:42, Markus Hitter m...@jump-ing.de wrote:
Am 10.09.2011 um 13:35 schrieb Stefan Salewski:
A lot of documentation can be bad.
Ha! Now that's exactly the right answer to somebody offering writing
documentation.
:)
I agree that too much documentation /can/ be bad -
On Sun, Sep 11, 2011 at 10:03:14AM +0530, Abhijit Kshirsagar wrote:
On Sun, Sep 11, 2011 at 04:42, Markus Hitter m...@jump-ing.de wrote:
Am 10.09.2011 um 13:35 schrieb Stefan Salewski:
A lot of documentation can be bad.
Ha! Now that's exactly the right answer to somebody offering
23 matches
Mail list logo
