Article submission questions
-
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?
-
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?
Post it as a new article since it seems that the subject matter is different enough from the first article. You can reference the first article in the second.
-
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?
I'd go with a new article and reference the original from the new article to show the 'origin' and reference the new article from the old one to point to the 'radical update'. Derek Lakin. blog: Digital Thoughts bliki: Derek's Bliki
-
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?
J. Dunlap wrote: I want to prevent a single present. :-D Post it as a new one, IMO. Marc My website Traceract
-
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?
I've been trying to get an article updated for over a month now with nothing to show for it. USE THE WIZARD!
"Live long and prosper." - Spock
Jason Henderson
blog -
J. Dunlap wrote: I want to prevent a single present. :-D Post it as a new one, IMO. Marc My website Traceract
-
I've been trying to get an article updated for over a month now with nothing to show for it. USE THE WIZARD!
"Live long and prosper." - Spock
Jason Henderson
blog -
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?
-
I am shortly going to post two new articles here at CP. One of these articles sprang from a previous article I posted here, Floodfill Algorithms in C# and GDI+. However, it has changed significantly since then, including the focus of the code and new article. Instead of dicussing various floodfill algorithms, I want to prevent a single, highly efficient and highly optimized algorithm. I also want it to be a demonstration piece for another article I am writing, which introduces a new method of fast pixel manipulation. Therefore, I will have both a sample class using LockBits() and pointers, and another one using the new method. Now, my questions are: should I post it as an entirely new article, or shall I post it as an update to the existing one? And if I post it as a new article, what should be done with the old one?