Forum > FV/Textmode IDE
Is there any simple ENGLISH examples for Free Vision???
Zath:
--- Quote from: oliverhbailey on December 08, 2020, 11:28:23 pm ---Very interesting replies..
First, the excuse "it's an open source project" seems a little lame. Most open source projects lack good documentation because developer's either can't, or don't like to write. This tool is an excellent compiler and cross-development tool, but there is a lot of old information that needs to be removed and is no longer applicable to current or recent, prior versions.
Successful open source projects have well written documentation, and keep it updated. Some users are interested in using the tool, not writing it. Try buying a Jeep kit, yes an unassembled Jeep. They were crated and sold until the 1970's when they were all sold out. Would you rather drive or build your car.
I'm not into listening to you BS, an American English acronym, after 45 years of development so you're barking up the wrong tree boys.
I did download the TV manual. The current example crashes compiled with FPC 3.2.0 and Lazarus 2.10 due to a memory management problem. No, I'm not fixing it!!
And thank you for your responses, it gives great insight into why a lot of old, out of date information is posted. You're too busy defending yourselves. If you can't be helpful, STFU. You can look that one up on your own, it is well documented.
Cheers!
--- End quote ---
What a delightful soul you are. You start a thread criticising something and complaining about people not updating it or doing some sort of mega wiki, then delight in telling us you found an issue but categorically won't fix it. Perhaps if "you" can't be helpful....
PascalDragon:
--- Quote from: oliverhbailey on December 08, 2020, 11:28:23 pm ---First, the excuse "it's an open source project" seems a little lame. Most open source projects lack good documentation because developer's either can't, or don't like to write. This tool is an excellent compiler and cross-development tool, but there is a lot of old information that needs to be removed and is no longer applicable to current or recent, prior versions.
--- End quote ---
This being an open source project also means that we're working on this on our own, free time. There is no big company backing this like there is for e.g. LLVM. So if something isn't documented well enough it's because no one had the time and/or interest to do so.
--- Quote from: oliverhbailey on December 08, 2020, 11:28:23 pm ---Successful open source projects have well written documentation, and keep it updated. Some users are interested in using the tool, not writing it. Try buying a Jeep kit, yes an unassembled Jeep. They were crated and sold until the 1970's when they were all sold out. Would you rather drive or build your car.
--- End quote ---
The documentation for the language, the usage of the compiler and quite some of especially the core units is constantly kept up to date. We however have quite an amount of packaged units that we distribute and the main devs can't provide their time to document these. That's why community support for such thing is needed.
MarkMLl:
I'm going out on a limb here.
--- Quote from: oliverhbailey on December 08, 2020, 11:28:23 pm ---First, the excuse "it's an open source project" seems a little lame. Most open source projects lack good documentation because developer's either can't, or don't like to write. This tool is an excellent compiler and cross-development tool, but there is a lot of old information that needs to be removed and is no longer applicable to current or recent, prior versions.
--- End quote ---
I think that's fair. Over-reliance on wikis is a particular problem, because (a) the person who wrote an article might not in fact know what he's talking about and (b) there's no mechanism that ensures that information gets reviewed on a regular basis and older stuff at the very least marked as being problematic.
There's also the complementary problem that the FPC documentation conspicuously omits notes of when RTL functions etc. were introduced into the language.
--- Quote ---Successful open source projects have well written documentation, and keep it updated. Some users are interested in using the tool, not writing it. Try buying a Jeep kit, yes an unassembled Jeep. They were crated and sold until the 1970's when they were all sold out. Would you rather drive or build your car.
--- End quote ---
By that metric there are very few successful open source projects, or at least very few that are maintainable by anybody other than the original authors.
I'd suggest that comparison of just about anything with one of the classic jeeps is unfair, since design, documentation and production were underwritten by government resources.
--- Quote ---I'm not into listening to you BS, an American English acronym, after 45 years of development so you're barking up the wrong tree boys.
--- End quote ---
Reminding people of just how well qualified you are (and, hypothetically, that you're a count and KCMG) is never a profitable way to argue. If you're so good then find a way of being useful, or at least pleasant.
--- Quote ---I did download the TV manual. The current example crashes compiled with FPC 3.2.0 and Lazarus 2.10 due to a memory management problem. No, I'm not fixing it!!
--- End quote ---
In that case kindly raise a bug report for it, or at least tell us here in adequate detail what the problem is so that somebody who understands the innards can look at it.
To summarise, you make what are IMHO some good points. But I suggest that a bit more of the "H" is in order.
MarkMLl
Navigation
[0] Message Index
[*] Previous page