|
would that qualify as recovery time? I'd try and get away from myself when I need recovery...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
And miss the Sean-mankini-body-oil-scented-bubble-bath-calendar shoot? Not on your life
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
That's the first post in a long time that's made me laugh out loud. I'm talking guffaw level laugh. Oh Sean, if only I could award you 500 for that.
|
|
|
|
|
That's fine for you to say, but you try working with someone who takes Casual Friday a little too far.
Avert your eyes, children.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Yes I do. I think it goes for all MVP's back then, but I got two certificates last year, and was asked to shred one of them; there has been a severe misprint but things got straightened out in the end. I should have kept it around though, so I could just adjust the year...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Luc Pattyn wrote: Just send Aimee over to investigate in person. Or Elina, or Lisa, or... you get the picture.
Yes!!
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
Chris Maunder wrote: Really??
Same here.
Maybe time to change printers?
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
And here. Mind you, I didn't get mine last year either.
|
|
|
|
|
OK. Thank you very mush for your replies.
|
|
|
|
|
|
Looks like others have helped nuke the account. Thanks!
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Just like Doodles?
It would be awesome!
Based on discussions here[^] and here[^].
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
|
Perhaps he can be animated running in the hamster wheel. 
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
If I can make a gif that showed my avatar as a flying turkey monkey, Chris has the technology to make Bob bob.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
as in WPFified? Silverlit?
remember, we don't do flash!
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
The animated Google doodle doesn't either.
|
|
|
|
|
Sure, al he needs is a table and some animosity, formalized through an interface, wait, here it is[^].
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
In fact, it's worse than that, but that's all you can say on this forum.
The basic problem is that you have multiple alternates - interspersed with multiple comment/replies - on one page.
My solution: treat each Alternate as a separate sub-Tip. Each sub-Tip will have its own page. When you're looking at a list of Tips, what you will see is the original Tip, and indented beneath it, a list of sub-Tips (Alternates). Each Tip and sub-Tip will be displayed with its rating, so you can quickly go to the highest-rated Tip in that group. Currently, if you look at the list of Tips, only the rating of the original Tip is displayed, even though one of the Alternates might have a kazillion 5's.
Benefits:
1. List of Tips will show ratings for original Tip and sub-Tips (it doesn't now).
2. Comments for each Tip and sub-Tip will be on that Tip's page; less chance for confusion.
3. Same approach could be extended to Articles; there could be sub-Articles, for extensions, etc., and this would be very handy for "abandoned" Articles. Having the comments on the sub-Article page would also eliminate confusion about which version of the Article was being discussed.
4. There would only ever be one "approval menu flag" per page, and that would always be at the top of the page for the Tip/Article (not in the middle of the page for Alternates like it is now).
Comments?
|
|
|
|
|
yes, showing everything at once sometimes is too much, it is true for some tips, as well as for some Q&A (which I will not elaborate on here). On the other hand, splitting it up over multiple pages would not be my preference, as it involves even more paging and clicking.
I probably would consider an approach based on something that is or resembles a TabControl: the first (initially the only) TabPage would hold the original tip (with its own comments and discussions), the other (optional) TabPages would each hold one alternative (with its comments and discussions). The TabPages should have a fixed and simple order: chronological. The tabs themselves should show a text ("tip", "alternative 1", "alternative 2", ...), the original author, and some indication of appreciation (score, maybe also "most appreciated"). The number of TabPages might be unlimited in which case one needs to allow for multiple rows of tabs, or it could be limited to say 6, which means no more than 5 alternatives can be added, which would be fine by me.
While entering a new alternative, I would like to be able to see everything that is already present, so the entire TabControl should be available and operational.
While entering a comment/reply/... to an existing tip or alternative, it would be nice to also be able to see any part one chooses (i.e. the original tip or any of the available alts), however this would probably be harder to achieve, unless the editor itself would be on the relevant TabPage, which then has the disadvantage one can temporarily tab it away, while it contains unfinished input.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
What would you suggest for linking to the alternate tips on the original tips' page?
Luc's idea of tabs is interesting but I think would be too cluttered.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: I think would be too cluttered.
why is that? it probably would only take an half-inch band, see what you now have for articles[^] ("Article", "Browse Code", ...).
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Your original idea was to have text with "tip", "alternative 1", "alternative 2", etc, the original author, and some indication of appreciation (score, maybe also "most appreciated").
That's a lot of stuff to stick into a tab.
How about just having a floating box at the top right of the tip with a list of alternate tips as an unordered list:
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
your example kind of proves adding author and score on a second line does not really widen the tabs (except for some extreme member names, like JSOP); it mainly adds some height, that is why I said half-an-inch, not quarter-of-an-inch, and "a TabControl or similar".
I trust you could find a way to use a little panel as the tab content instead of a simple string, and stuff whatever it is you like in there? So far I never tried that myself...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code. modified on Tuesday, May 10, 2011 11:15 PM
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
