# Computeractive 699 (18 Dec 2024): mention of Gramps as "free but complicated"

**URL:** <https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634>\
**Category:** Genealogy\
**Tags:** articles\
**Created:** [December 21, 2024, 8:55pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634 "2024-12-21T20:55:06Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![yorkshire\_lad](https://avatars.discourse-cdn.com/v4/letter/y/ce73a5/32.png) [@yorkshire\_lad](https://gramps.discourse.group/u/yorkshire_lad)\
**Post date:** [December 21, 2024, 8:55pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/1 "2024-12-21T20:55:06Z")

</div>

Computeractive, 18 Dec 2024, Issue 699, p. 20. [https://getcomputeractive.co.uk/](https://getcomputeractive.co.uk/)

gramps gets a mention

 ![image](https://global.discourse-cdn.com/free1/uploads/gramps/original/2X/8/89e379d815cd6121259fa5bf2953771c041259cf.jpeg)

---

<div class="post-metadata">

**Author:** ![DaveSch](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davesch/32/40_2.png) [@DaveSch](https://gramps.discourse.group/u/DaveSch)\
**Post date:** [December 21, 2024, 10:36pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/2 "2024-12-21T22:36:09Z")

</div>

I was able to utilize Libby/Overdrive to read this issue of Computeractive (699) through my local library in Massachusetts.

But while on the library’s website, I checked its available online resources. One of the sites (which your library may also access) was Gale OneFile. Putting in “Gramps genealogy” as the search brought me to this article.

> Peers, Nick. “HOW TO Record your family history with Gramps: STEP-BY-STEP GUIDES TO IMPROVING YOUR PC.” _MaxPC US_, no. 222, Nov. 2023, pp. 61+. _Gale General OneFile_, [HOW TO Record your family history with Gramps: STEP-BY-STEP GUIDES TO IMPROVING YOUR PC. - Document - Gale General OneFile](http://link.gale.com/apps/doc/A769171200/ITOF?u=mlin_n_stevens&sid=bookmark-ITOF&xid=fb2f9560). Accessed 21 Dec. 2024.

Actually, a pretty good article for a new user to get started.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [December 22, 2024, 2:10am UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/3 "2024-12-22T02:10:40Z")

</div>

> [@DaveSch](#):
>
> Actually, a pretty good article for a new user to get started.

The November 2023 article shows [Nick Peers](https://uk.linkedin.com/in/nickpeerswriter) has dug into Gramps enough to grasp the pros and cons. And he seems well-versed on competing product interfaces. That gives the mildly deterring mention of Gramps in this month’s issue more weight.

Have we all acknowledged Gramps has a very steep learning curve for novices… and that might be too steep for a significant percentage? I think so.

Given that assumption the question becomes: is this something that the developer community _wants_ to change. Is there a desire to make Gramps more accessible to neophytes?

My assumption has been: “yes, but not if those changes make it harder to harness Gramps’ power.”

Is that incorrect?

---

<div class="post-metadata">

**Author:** ![anon44746896](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@anon44746896](https://gramps.discourse.group/u/anon44746896)\
**Post date:** [December 22, 2024, 2:41am UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/4 "2024-12-22T02:41:37Z")

</div>

> [@emyoulation](#):
>
> My assumption has been: “yes, but not if those changes make it harder to harness Gramps power.”

I’m guessing that is the intention and given that Gramps is so flexible a [simpler interface](https://github.com/cdhorn/CardView) could be provided with an option (or desktop shortcut) to switch to the normal interface that most of us have learnt.

On the main page of the Gramps website it states:

> We strive to produce a genealogy program that is both intuitive for hobbyists and feature-complete for professional genealogists.

So the project does not hide it is targeted at the proficient genealogy user, or anyone with a do-it-yourself attitude who is willing to read the documentation, and solve their own problems but the word **strive** does hide a lot in the promise that it be **intuitive** for the hobbyists which is one step up from a beginner! Gramps should not be recommended to a beginner in the current form!

Sure improve the flow of data entry for Gramps but please don’t reduce the program to the point of being useless!

---

<div class="post-metadata">

**Author:** ![comeng](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@comeng](https://gramps.discourse.group/u/comeng)\
**Post date:** [December 22, 2024, 7:00am UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/5 "2024-12-22T07:00:41Z")

</div>

Hi

I classify myself as a medium term user, hobbyist and code tweaker and I  
am very much in favour of the simple approach Kari’s Simple Sidebar  
being a perfect example.

I have recently installed a new operating system and clean version of  
5.2.3 and then started to get my interface back to how I like it as part  
of this I did an exercise of looking at the plug-ins/add-ons and found  
that there are over 400 built in/available/installed.  
For someone new to Family History this must be an assault on the senses.

I am totally against any form of “dumbing down” of GRAMPS because I  
suspect this is where most of the developers (present and future)  
interests focus.

So a starter configuration (basic/better/best or  
starter/experienced/pro)with suitable documentation would be a viable  
approach.  
phil  
PS whilst CardView is a super addon in my opinion it is not the base I  
would use because the configuration would involve an epic sized tome of  
documentation on it’s own.

---

<div class="post-metadata">

**Author:** ![Davesellers](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/davesellers/32/1457_2.png) [@Davesellers](https://gramps.discourse.group/u/Davesellers)\
**Post date:** [December 22, 2024, 2:37pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/6 "2024-12-22T14:37:49Z")

</div>

Thinking back when I first downloaded gramps, I was able to figure most of the basic features without reading any docs. I did stumble putting in the source/citation in the correct spot and it took me a while to figure out I needed the Long/Lat in the Place name before I could get the Map view to work.  
I think gramps passed the initial test with a 90% in that I could use the program without reading the docs.  
A couple of suggestions:  
When an Event is added, have the Sources tap (Label) colour RED until an entry is made.  
When a Place is added, have the Lat and Long fields RED (Labels) until there are entries.

This will draw the attention to these fields for the users that don’t read help pages. If there are any other “must have” fields then follow the same process.

---

<div class="post-metadata">

**Author:** ![GeorgeWilmes](https://avatars.discourse-cdn.com/v4/letter/g/c57346/32.png) [@GeorgeWilmes](https://gramps.discourse.group/u/GeorgeWilmes)\
**Post date:** [December 22, 2024, 4:59pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/7 "2024-12-22T16:59:08Z")

</div>

The development of Gramps Web has proven that the core of Gramps can be reused within an entirely new user interface. (In that case it’s web-based, but desktop versions could also be built.)

Ambitious developers could theoretically build independent interfaces of various complexity and platform support, yet all could use the same underlying database and logic.

A novice user could start on with a simplified GUI and later switch to a more complex one – or continue to use both. People already do this when switching from one genealogy program to another, but in this case, there would be no issues about converting their data.

All of that is easy for me to say, since I’m not a developer. I do appreciate that it’s a ton of work to do anything. I guess what I’m saying is, developers interested in significantly improving the interface shouldn’t feel that they have to work within the confines of the current one.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [December 22, 2024, 5:38pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/8 "2024-12-22T17:38:23Z")

</div>

> [@GeorgeWilmes](#):
>
> The development of Gramps Web has proven that the core of Gramps can be reused within an entirely new user interface. (In that case it’s web-based, but desktop versions could also be built.)

That’s true.

It would be very interesting to see special-purpose Gramps-engine Apps for smart phones and tablets as research assistants.

Like a Camera app for gravestone photos… with an OCR alternative looking up ancestors and auto-filing as a Burial Event gallery object. And logging the the gps metadata for plotting other known persons on a cemetery diagram.

Or collecting snapshots from pages referenced in a book in a repository. Where the researcher has Citation, Source and Repository gallery slots … like a cover/spine/ back, title page (with publisher/author data), card catalog page (physical or electrontic). So they are already organized for when you want to analyze the data or process with OCR tools.

And although I’m not a gamer, a tethered VR headset interface with Genealogy Fonds about specific ancestors or families for exploring complex data relationships.

---

<div class="post-metadata">

**Author:** ![stuck](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@stuck](https://gramps.discourse.group/u/stuck)\
**Post date:** [December 23, 2024, 7:33pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/9 "2024-12-23T19:33:25Z")

</div>

My experience is similar. I figured out the basics of building families without digging into the documentation. Having said that although I’d never used a genealogical db system of any flavour prior to using Grampes, I did come to Gramps with a lot of experience of being a middle man between a team of people using a business system db and the IT geeks that coded that system, i.e. I do understand a bit about relational dbs. Without that experience of a complex relational db though I’m not sure I’d have found Gramps all that welcoming.

Also, I’m a 100% Windows user but I do know a little bit about Linux so to discover certain Gramps add-ons have ‘dependencies’ is no surprise and didn’t bother me. I’m not sure your average Windows user would be as understanding. They’d expect an installer to install, not install but leave the user to learn something else must also be installed before what you installed works.

In other words, for your average Windows user, I don’t think Gramps is that accessible.

---

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [February 10, 2025, 11:31pm UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/11 "2025-02-10T23:31:41Z")

</div>



---

<div class="post-metadata">

**Author:** ![StoltHD](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@StoltHD](https://gramps.discourse.group/u/StoltHD)\
**Post date:** [February 11, 2025, 12:14am UTC](https://gramps.discourse.group/t/computeractive-699-18-dec-2024-mention-of-gramps-as-free-but-complicated/6634/12 "2025-02-11T00:14:04Z")

</div>

> [@emyoulation](#):
>
> Like a Camera app for gravestone photos… with an OCR alternative looking up ancestors and auto-filing as a Burial Event gallery object. And logging the the gps metadata for plotting other known persons on a cemetery diagram.
> 
> Or collecting snapshots from pages referenced in a book in a repository. Where the researcher has Citation, Source and Repository gallery slots … like a cover/spine/ back, title page (with publisher/author data), card catalog page (physical or electrontic). So they are already organized for when you want to analyze the data or process with OCR tools.

Hmmm… so, an integration with Zotero, Tropy, Digikam and OpenKM and maybe a little of Omeka? 😉
