> IMHO, this should not be plural. That is, a getting started should
> decide for one work-flow and stick with it.
As John points out, there's more to geda than making circuit boards.
So, tutorials for schematics->pcb, schematics->sim, verilog->sim, etc.
Then, within each case, beginner vs advanc
DJ Delorie wrote:
>> I still have to decide, where to start. An overview? A getting
>> started? A HOWTO? A table of contents to be filled?
>
> Based on what kinds of questions I tend to answer in irc and email, I
> think the relative priority should be:
>
> * Introductory tutorials that demonstr
On Sep 12, 2011, at 8:05 AM, John Hudak wrote:
> So, the doc would have two sections:
There's nothing whatever preventing you from creating gEDA documentation and
publishing it on your own site (or gedasymbols.org: even us black sheep are
accepted there). That's what Stuart Brorson did when
My suggestion is to first create an outline. The first n sections
should be in tutorial form, using a small example, and focusing on the
main steps, beginning with installation of the tool(s), problem
statement (going from schematic to board layout to what needs to
shipped to a boar
> I still have to decide, where to start. An overview? A getting started?
> A HOWTO? A table of contents to be filled?
Based on what kinds of questions I tend to answer in irc and email, I
think the relative priority should be:
* Introductory tutorials that demonstrate the most common flows,
s
Abhijit Kshirsagar wrote:
> Somehow missed this thread and replied on the other one... Count me
> in for documentation. Please let me know what I can do.
I still have to decide, where to start. An overview? A getting started?
A HOWTO? A table of contents to be filled?
> Some of the documentati
Hey,
Somehow missed this thread and replied on the other one... Count me in
for documentation. Please let me know what I can do.
Some of the documentation I have written previously is here:
gEDA-Tutorials.pdf on https://sites.google.com/site/abhijit86k/linux/geda
~Abhijit
On Fri, Sep 9, 201
On Wed, Sep 07, 2011 at 10:51:31PM +0200, Kai-Martin Knaak wrote:
> I am close to start off a gEDA wikibook (http://en.wikibooks.org).
> Would you join the effort?
>
How about updating the existing wiki documentation?
- Gschem User Guide is outdated.
- PCB Manual is outdated.
- Circuit Simulatio
On Wed, Sep 7, 2011 at 4:51 PM, Kai-Martin Knaak
<[1]k...@familieknaak.de> wrote:
Dan Roganti wrote:
> I'll be glad to help anyone in this development group with this
> documentation work.
I am close to start off a gEDA wikibook
([2]http://en.wikibooks.org).
Would yo
On Wed, Sep 07, 2011 at 10:51:31PM +0200, Kai-Martin Knaak wrote:
> Dan Roganti wrote:
>
> > I'll be glad to help anyone in this development group with this
> > documentation work.
>
> I am close to start off a gEDA wikibook (http://en.wikibooks.org).
> Would you join the effort?
>
I'd be happy
Dan Roganti wrote:
> I'll be glad to help anyone in this development group with this
> documentation work.
I am close to start off a gEDA wikibook (http://en.wikibooks.org).
Would you join the effort?
---<)kaimartin(>---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
http://pool.sks-keyserver
On Mon, Sep 5, 2011 at 12:13 PM, John Griessen <[1]j...@ecosensory.com>
wrote:
I can see a core set of plugins shipping with the source, but not
all.
I don't see it as a big deal though, since if a feature is really
"core"
it will be in the core, so not shipping plug
Hi all,
> -Original Message-
> From: geda-user-boun...@moria.seul.org
> [mailto:geda-user-boun...@moria.seul.org] On Behalf Of DJ Delorie
> Sent: Wednesday, September 07, 2011 2:39 AM
> To: geda-u...@seul.org
> Subject: Re: gEDA-user: plugins (was: How can you help...)
> > https://github.com/bert/pcb-plugins.git
>
> This URL gives me "404 This is not the web page you are looking for."
It works fine once you realize you have to take the .git off to change
it from a repository to a web page. Seems a silly detail to me, but
that's how it's set up on github.
__
Bert Timmerman wrote:
>> Is there even a comprehensive list of plugins that are done
>> at a single place?
>
> https://github.com/bert/pcb-plugins.git
This URL gives me "404 This is not the web page you are looking for."
:-|
---<)kaimartin(>---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
h
Hi Bob,
> -Original Message-
> From: geda-user-boun...@moria.seul.org
> [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Bob Paddock
> Sent: Tuesday, September 06, 2011 2:38 AM
> To: gEDA user mailing list
> Subject: Re: gEDA-user: plugins (was
> Documenting them however is a big deal.
Is there even a comprehensive list of plugins that are done at a single place?
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
> I can see a core set of plugins shipping with the source, but not all.
I can see us breaking out some of the core actions into a plugins
directory, and importing some public plugins there too. Might be a
good way to manage our "library" of actions.
> I think it would help a lot if the scheme
On 09/05/2011 09:33 AM, Kai-Martin Knaak wrote:
Also, they tend to bit-rot and break
when the main source moves on.
That's why they are separate. There is not enough
coding/testing man-or-woman-power to pull all conceivable plugins along
with core changes. Seems obvious. The ones that are t
19 matches
Mail list logo
