> Scid vs. PC surely has very few bugs now as i'm still working on it every > other day > for the last few years. My early efforts were a bit raw, but latest release > is very solid.
Having just installed Scid vs. PC (or rather Mac) a few days ago and having (attempted to) play(ed) around with a little bit, allow me to intervene at this point from both a user's and a developer's perspective. I've tried Scid before, but then quit playing seriously for a while. As a user, I must say the quote above seems a bit optimistic at best :-), because I have already run into a bug and several major annoyances when using Scid vs. Mac for playing on FICS. I've cursed Scid many times since (and the Apple Mighty Mouse for pulling forward / rewind tricks on me while playing). But hey, I'm a developer myself, and I know this isn't anything any developer involved in the project ever got paid for, so this doesn't come as a surprise to me. But the quote also displays an issue I find many developers fall victim to, and that is the focus on the code and functionality. The no. 1 problem I have with Scid so far is its (lack of) documentation. I know, this is a little unfair for reasons mentioned above, but compare this ... http://www.hiarcs.com/hce-manual/mac/HIARCS%20Chess%20Explorer.html ... to this ... http://scidvspc.sourceforge.net/doc/Contents.htm Right now, I'm pretty close to shelling out the € 100,- for Hiarcs just for the sake of having sane documentation. (That Hiarcs also sports the better GUI, another often neglected area, is another factor.) Now please don't get me wrong, like I said, I appreciate all the work that people have put into Scid and its derivatives. I'm just saying that just maybe, the focus should be put towards improving stuff that isn't code (at least if people don't agree what part of the code needs fixing the most). :-) > I *am* interested in the state of mainline Scid (i appreciate the popularity > of dockable > windows), but am not interested in debugging Fulvio and Gerds code. It is > tough work, and > something they should really be doing - or a new dev. Pascal cared about bugs > but he has not responded in years. > > I've recently tried to contact Alex, Pascal and Joost to add me as a dev, but > received no reply. > Perhaps they just ignore me which is fair enough, or perhaps they have > switched off. > They have been very quiet for a while now. This is another issue I think is a major problem with Scid: No one REALLY seems to care about it. They are (competing?) spin-offs that once shared a common code base, a GUI that leaves much to be desired, and no _up-to-date_ documentation to speak of. Add the rather peculiar choice of technology to the mix, and then it doesn't come as a surprise to me that Scid development appears to be more or less stalled. And no one is leading the way to say how to fix this. > Sorry to be so morose :), but I'd like some of the devs to propose how the > bugs in svn will ever get fixed. Looking at it from a distance, it appears that Scid would need a major rewrite to merge the diverging code bases, support current technologies and make it easier for interested developers to contribute. I must admit I haven't looked at the code yet, but I imagine that this is a task that would require a huge investment of time. II can't even figure out who is "in charge" now with respect to Scid development, and it appears to me that this is what would be needed to get Scid moving forward again. Free Software is certainly good, but fragmentation isn't. Regards Matt ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
