Re: More issues with RC2
markjmeans
Hi Andrew,
As for the remainder of your comment… Try developing two different programs, pascal and C, at the same time. The languages are so close in syntax you quickly get mired in the peculiarities of the two and spend a lot of time bug-fixing and referring to API docs. This is not efficient coding. Efficient coding is 100+ lines of debugged functioning code per hour per developer, not 700+ lines of code per month per developer. As an example, in the summer of 2005 I started writing a Windows XP application that was ready for deployment in 9 months. It had over 100,000 lines of code (comprising modules written in VB, C++, and 8051 assembler), not counting auto generated code from UI creation tools I used. And not counting the code from the early parts of the project that were deleted or replaced as it was being developed. There was only myself and one other developer working on this project. I produced 95+% of the VB code (the bulk of the application), perhaps 10-15% of the C++ code (high level USB driver interfaces, the other guy did the low level part). You need a singleness of mind and concentration to produce debugged code at that rate. My primary focus now is C# programming on multiple projects with a huge combined code base, and I am the only developer. I cannot afford to get distracted by a similar syntaxed and structured language. Now if PCGen had been written in Cobol, RPG, Fortran, LISP or ASSEMBLER (all of which I have programmed in), then that would be something else entirely as they are all completely different coding syntax and style and could never be confused with C++, C# or Java.
As for JIRA, I wanted to post on the forums first (specifically the null error message issue and the font issue) to see if anyone else (not developers) encountered the same problem. Anyone with JAVA SDK development tools checking it might not encounter the same error if the problem was related to the JRE set installed in windows installer version of PCGen. But I suppose there are so few Windows users who subscribe to the forums or perhaps all other Windows users just all the data sets (by default). I don’t know. Either way, a confirmation of an error on a non-JDK installed machine could have identified the problem. In my case, while the null error went away when I uninstalled and reinstalled (as I identified above) this is not confirmation of the cause since I have not again uninstalled and reinstalled without selecting _universal to confirm that the problem returns since it is completely irrelevant if _universal should not be able to be deselected in the first place.
Mark
From: main@pcgen.groups.io <main@pcgen.groups.io> On Behalf Of Andrew Maitland via Groups.Io
Sent: Saturday, December 15, 2018 5:05 PM To: main@pcgen.groups.io Subject: Re: [pcgen] More issues with RC2
Hi Mark, 1) Not being a program meant to be specific to a particular OS, I'm not overly concerned about this. A "critical" or "blocker" bug is classified as - Did it break the program or did we lose major core functionality? I wouldn't release an RC3 for a mere glitch for Windows not being able to figure out the program is an RC2 vs. RC1. I am going to do an RC3 for several fixes/features that were discovered missing that I feel should make the 6.08.00 release, but not because Windows has issues. If you felt this is important enough to warrant concern why haven't you opened a bug for it? 2) I don't control HOMEBREW sources, anything I cannot control is irrelevant to our release schedule. We have a support team on Discord and here to assist you update your out-of-date set. FEAT is an illegal tag, and should have been converted to ABILITY back in 6.06.00 if not sooner. The team focuses on things we control and manage. If you want support for your homebrew, ask for the help, and we will gladly tell you what you need to update/change/convert to be compliant with the current version. 3) As #1 states, we are an OS Neutral Program. Coding in OS specific settings requires folks who have the knowledge. I have *NEVER* had an issue creating PDFs nor printing them, and I have been using PCGen for 17 years. Merely set your paper settings in the preferences and you'll be fine. To tag onto Stefan's comment, if you won't do the code, at least point out a source that our team can reference to tackle the issue. I've always held to a principle of point out the problem and a potential solution if possible. I wasn't aware that cross-training in multiple languages was considered a detriment. And for actual bugs, we have a BUG tracker system located here --> https://pcgenorg.atlassian.net where all the issues can be discussed or solutions presented. Cheers, Andrew On 12/14/2018 10:30 AM, markjmeans wrote:
|
||
|