Quick way to update source files of an article
-
It would be nice if the author of an article could update the download links. This could be usefull when you have some minor bug fixes and you don't need to change the article contents for example. That will also reduce the work of the editors.
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
It would be nice if the author of an article could update the download links. This could be usefull when you have some minor bug fixes and you don't need to change the article contents for example. That will also reduce the work of the editors.
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
Hi Chris, I am afraid I don't like the idea. if the sources get changed, it MUST be reflected in the history paragraph inside the article text. How else would the interested reader/user be aware something has changed? At the bare minimum, you should add an automatic message to the history, but nothing would replace the author himself updating the history and explaining what he did and why. A way to subscribe to an article, so any modification creates an opt-in e-mail would be nice and useful, and might alleviate my above concerns. So maybe you should provide this first? :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
-
Hi Chris, I am afraid I don't like the idea. if the sources get changed, it MUST be reflected in the history paragraph inside the article text. How else would the interested reader/user be aware something has changed? At the bare minimum, you should add an automatic message to the history, but nothing would replace the author himself updating the history and explaining what he did and why. A way to subscribe to an article, so any modification creates an opt-in e-mail would be nice and useful, and might alleviate my above concerns. So maybe you should provide this first? :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
We can do even better than that, Luc. Give us some time and we'll put something valuable together.
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
Hi Chris, I am afraid I don't like the idea. if the sources get changed, it MUST be reflected in the history paragraph inside the article text. How else would the interested reader/user be aware something has changed? At the bare minimum, you should add an automatic message to the history, but nothing would replace the author himself updating the history and explaining what he did and why. A way to subscribe to an article, so any modification creates an opt-in e-mail would be nice and useful, and might alleviate my above concerns. So maybe you should provide this first? :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
I was mainly talking about problems like missing files in the archive, wrong archive uploaded,... For example, I updated my article last week and I saw that one of the download link was not up-to-date, so it would be easier that I could fix that myself. I also had the experience that I forgot to add some files in the archive and so, the first person that download the zip complains that the project can't compile. For those problems, there's no real point on having a history. But I agree with you on the fact that it would be really nice to have the history separated from the article contents (in any kind of way). So that you could specify some information when you update the code (a bit like a commit message for SVN).
Cédric Moonen Software developer
Charting control [v1.4 - Updated] -
We can do even better than that, Luc. Give us some time and we'll put something valuable together.
cheers, Chris Maunder
CodeProject.com : C++ MVP
Hi Chris, unfortunately I am not able to give time, but I trust you will be wise and take the time you need. :-D
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
-
I was mainly talking about problems like missing files in the archive, wrong archive uploaded,... For example, I updated my article last week and I saw that one of the download link was not up-to-date, so it would be easier that I could fix that myself. I also had the experience that I forgot to add some files in the archive and so, the first person that download the zip complains that the project can't compile. For those problems, there's no real point on having a history. But I agree with you on the fact that it would be really nice to have the history separated from the article contents (in any kind of way). So that you could specify some information when you update the code (a bit like a commit message for SVN).
Cédric Moonen Software developer
Charting control [v1.4 - Updated]Hi Cedric, I trust first intentions are good, but such a feature soon will get abused to sneak in some essential changes. The modified message now gets added automatically to forum posts, and that is good; if it is wanted for messages, it is even more useful for articles and their collateral. :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
-
Hi Chris, unfortunately I am not able to give time, but I trust you will be wise and take the time you need. :-D
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.