From: Luke-Jr <lu...@da...> - 2005-02-28 23:03:32
|
On Monday 28 February 2005 22:48, Jason Salaz wrote: > On Monday 28 February 2005 10:30, Don Allingham wrote: > > So, if I have a couple of hours to spend, I think the project will get > > more benefit from a new or enhanced report than from a different set of > > toolkit widgets. The report adds new functionality, the additional > > toolkit does not add new functionality. > > I would have to be the third person to agree with this statement. > Reinventing the wheel to make someone else happy isn't the primary goal of > the project. Providing functionality and ease of use is the top goal, even > for us people who only poke around for bugs in the program. This wouldn't *be* reinventing the wheel. It would be providing existing functionality to more users. > > Sometimes the comment comes up, "But if you supported XXX toolkit, you > > could run it under the YYY operating system." And as harsh as it sounds, > > my honest answer is, "I really don't care." I have no interest in > > supporting Windows, and I am not capable of supporting the Mac (Apple > > hasn't given me a free mini-Mac, and I'm not holding my breath :-) The > > goal of the GRAMPS project has been to supply a solid genealogy project > > for the un*xish operating systems using GNOME. Windows and OS X don't > > fit in with these goals. > > I would agree with Don's assessment. I could help with a port to KDE/Qt, > but why? I would not want to assist in maintaining that fork, since > there's really no need to change anything. And I also agree that providing > additional branches for different toolkits is going to make the whole thing > much worse in the end. How do you get the idea that branches will hurt anything? Branches are *designed* for things like this. > Porting rarely does any more good than what people think it will do. I > mean, you can still run Gramps under KDE. Not always. What if KDE isn't running under X11? > In the end, Linux will still run it, Linux doesn't 'run' GRAMPS at all, from what I can tell. Python runs GRAMPS, so long as GTK and parts of GNOME are present. > and getting things aligned with the end user is still happening. Only because the existing end user can already run it. However, *potential* end users cannot. > Porting it will do what? Allow GRAMPS to run on platforms without GTK/GNOME. There are many *nix systems (not to mention others like Windows) that do not support X11. > It will make it more confusing for the end user. How so? Default to GTK, and if PyGTK support isn't on the system, try the others. No user knowledge necessary. > We are here for the users, especially Aunt Martha, because of the fact that > many people are just moving over to Linux and having something familiar to > them, like a genealogical program is what matters to them. Making the > transition to Linux is hard, don't get me wrong. But we are making it one > step easier by not complicating the user's experience in their move. If the users need to change programs, it isn't helping the transition process. The existence of cross-OS programs allows users to change one program at a time, and while actually changing OS (dual-boot phase), run the same programs on both sharing the data. |