|
Hello,
I am not able to support the queries on one of my articles. I'd like to withdraw it for the time being. I am extremely busy on a project and I hate not responding to the queries. Please let me know how can I withdraw/remove my article. It has 16 votes.
Regards
Rahul Kumar
|
|
|
|
|
Sure Rahul.
Which one?
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
Article: "WPF Masala - The sliding and flying windows"
Thanks
Rahul
|
|
|
|
|
Done.
I have changed the article to composing status
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
Hi Sean,
Thanks! But how would I delete this article altogether, permanently please?
Regards
Rahul
|
|
|
|
|
Hi All,
So after all this site has done for me, I think it is time to give back a bit. I've been developing this TCP communication framework on and off for a couple years, and we use it here internally for all our projects. It is essentially on complete rewrite #3, which seems to be when I get everything exactly how I want it.
Brief overview: SLX Communication Framework lets you use a single modeling tool and framework to make all your .NET based apps talk to each other - full .NET Framework, Compact Framework, and Silverlight. The framework includes VS2008 code generators and visual designers. It has multiple levels of abstraction, each with their own suitable use cases:
- Command-based object exchange API, built on:
- Whole-Message exchange API, built on:
- platform-independent sockets API
I have at least 5 parts planned, possibly double that by the time I'm done...there is just a ton to talk about. So far on the drawing board for the content I want to cover:
- who should read what
- defining the problem
- current options and associated limitations
- my idea of an "ideal" communication framework, reasoning behind it
- architecural overview of the actual framework, how it overcomes limitations of current options
- explaining how each platform was abstracted to a common sockets API and related design decisions
- very basic sample client/server app using the common sockets API
- building the messaging API on top of the sockets API
- very basic sample client/server app using the messageing API
- building command-based generic object exchange API on top of the messaging API
- building a VS2008 C#/VB code generator that parses the communication definition language and spits out the base classes and "fill in the blanks" methods
- building VS2008 Client item template and Server item template
- building a visual designer to graphically build your communication definition file
- sample client/server application with silverlight, compact, and desktop clients that demonstrates how to implement ludicrous amounts of code sharing between all the projects
I bet I can think of a few more things to throw in there as well. Basically, the point is that it is a very extensive framework and there are lots of angles to tackle things. It is fairly feature-complete right up to visual designers, code generators, etc, so someone looking to develop a different framework, even entirely unrelated, could possibly get a lot of useful information. But there is a LOT of potential information.
So...question: based on the limited info above, do you agree that one article would be brutally overwhelming? If so, is there an upper limit on the number of parts a series should have? What would be your criteria for deciding what goes into article #1 and what should wait until article #2?
I was thinking of having an intro article that covers, say, the first 5 points. It would be a useful intro for everyone. In the "who should read this" section, I would recommend which parts are suitable for each audience. For example:
- "If you are just looking for an easy way to implement security, two-way object exchange...etc... in your project, you can safely skip to articles C, D, and E."
Another possible option: I was considering creating seperate series articles to cover things like the VS plugin stuff (code generator and item templates). But I'm not sure I like that since really it is very closely tied to the communication framework, and I sort of envisioned this series as a complete documentation of the making of this framework.
And one last question (for now): should I write and release all the articles at once, a few at a time, or one at a time?
Appreciate your input.
Thanks,
--Mike
|
|
|
|
|
5 parts sounds OK, but there is no upper limit.
I can tell you that in the past when users approach me with highly detailed, well-outlined plans like this, and ask how many sections it should be released in, or if it is of interest to our users, the results are always the same: The articles do very, very well.
An intro article sounds fine, and I'm sure however you decide to break it up, the articles will do, very, very well.
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
It is about time to get rid of email by go to directly to the source.
Steps are:
1) Have a program that will contact your sources.
2) Download what the source have for that day or week or email
your source.
3) If your sources want to get in touch with you, use your e-mail
provider or set a special time up for computer to computer
communication.
This will all so get rid of Spam, viruses or junk mail from your e-mail provider.
|
|
|
|
|
What?
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
Too much ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) .
"WPF has many lovers. It's a veritable porn star!" - Josh Smith As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
My blog | My articles | MoXAML PowerToys | Onyx
|
|
|
|
|
His aluminum hat fell off. 
|
|
|
|
|
joeyi wrote: It is about time to get rid of email
Yeah, brilliant! No more email, no more problems, no more spam, no more communication ... uh, just a moment 
joeyi wrote: 2) Download what the source have for that day or week or email
joeyi wrote: 3) If your sources want to get in touch with you, use your e-mail
So, after you get rid of email, how do you use email?
I don't know what you are smoking but I'll have some if it's not too expensive.
|
|
|
|
|
I suppose there's no solution to this, but I thought I would mention it any way.
About a year ago when I would publish an article it would do well and then some one would come along and give it a 1/5 vote without explanation. It seemed to be habitual and I thought it was being done by a univoter. I got confirmation when CodeProject made a change that required some one to leave a comment when they made a vote of one. When I got the next 1 vote I looked at the user's messages and saw that he was routinly going through articles that were doing well and giving one votes. I asked him why he was doing this and received no response.
Since then when ever I publish an article it starts off doing well then all at once I receive multiple 3/5 votes. 3/5 is significant because it is the lowest vote that one can give without disclosing their identity. With my latest article the first 21 votes were 5 out of 5 and then 6 votes showed up within a few minutes of each other with 3/5 votes. The low votes can really hurt ones score and lower it's visibility. I get the feeling that the vote is from the same person (but using multiple accounts) as the low votes cam in with rapid succession.
I was wondering if any one else ever encountered this same thing.
|
|
|
|
|
Sometimes some things can be done, especially when the patterns are clear.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
Wow, I guess something can be done! I see the votes that cam in with rapid succession are now gone. Thanks!
|
|
|
|
|
|
Hi all,
I've submitted an article and i would like to publish it but don't know how because is still in "composing" mode and when i look at the summary of my articles it results as "unfinished".
Help is appreciated 
Many thanks
|
|
|
|
|
Hi,
there is a little checkbox on top of the big text edit box, that is what you are looking for.
Luc Pattyn
Have a look at my entry for the lean-and-mean competition; please provide comments, feedback, discussion, and don’t forget to vote for it! Thank you.
Local announcement (Antwerp region): Lange Wapper? Neen!
|
|
|
|
|
|
you're welcome.
Luc Pattyn
Local announcement (Antwerp region): Lange Wapper? Neen!
|
|
|
|
|
I posted an article a while ago, got some great feedback from readers including some bug reports. I would like to edit the article, but don't know how. Help?
Thanks in advance.
|
|
|
|
|
Hi Bernardo,
Now that your article has been edited by our editors, the only way to update it is to submit the updated source code and HTML to us. You can use the “Get Article’s HTML” from the link in the upper right hand corner of your article, and send both updated HTML and zipped sourced code to us at either my email address, or submit@codeproject.com.
Please let me know if you have any questions about the process.
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
Thanks Sean. Perfectly clear. I will submit the update shortly.
|
|
|
|
|
Hello,
How can I get automatic e-mail notifications when new messages are posted to my own articles?
|
|
|
|
|
Look for "My Settings" (top right of most CP pages), then "Settings" tab. There are two editboxes for entering an e-mail address, one for messages, one for articles.
Luc Pattyn
Have a look at my entry for the lean-and-mean competition; please provide comments, feedback, discussion, and don’t forget to vote for it! Thank you.
Local announcement (Antwerp region): Lange Wapper? Neen!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
