|
Maybe firefox started one of it's epic battles[^] against it's enemies again.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
My boss just emailed me about a report I wrote a few weeks ago that has a problem.
It's a report on open logs in our Support system.
His words exactly, "It must be number of logs opened on that day, currently selections is of logs OPENED for that day"
What would the difference between ON and FOR be ?
|
|
|
|
|
If I am a dev I can open a support ticket on Monday, even though it was submitted on Friday of the previous week. That is a ticket FOR Friday that I opened ON Monday.
Perhaps it's that type of subtle difference ?
Elephant elephant elephant, sunshine sunshine sunshine
|
|
|
|
|
Okay that makes sense, but our system only save the date on which it was opened(sysdate).
|
|
|
|
|
Asgard25 wrote: Okay that makes sense, but our system only save the date on for which it was opened(sysdate).
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
|
In that case there is never any confusion, it's always ON
But it's more like: the kid is on the table, do something
the TV is on, sshhhhhh
why is the PC always on ... 
|
|
|
|
|
If you use FOR that day, you will being that only that day, if you're saying ON that day you're saying it will available on that day and maybe sometime later you can get it again.
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
That actually taught me a little bit better grammar, thanx
But I still don't see how there could be any difference between the two in this case of the open log dates
|
|
|
|
|
I would understand the two different meanings to be;
1) The logs which were created/opened on that date. i.e. they were raised on that day.
2) The other would be logs that were open or opened on that day and still not closed. i.e. if logs raised on monday were still not closed and it is now tuesday, include those.
If your report records both an open date and a close date, you could determine which ones were open for that given date.
|
|
|
|
|
I agree with Dave here; opened ON a given day were items created on that given day (e.g. How many reports were created and marked Open ON Tuesday).
Opened FOR a given day could be a day in the future or the past (e.g. How may reports were created FOR Tuesday).
The again, the original message could contain a typo, or an unclear meaning. Good luck!
"Things don't happen for a reason; things just happen, and then we reason them." - Joe Chizmas
|
|
|
|
|
two separate meanings. opened on is literal and opened for could be implied or past or future reference. I opened the report for the day 8/1/2014 on this current day of 8/15/2014
|
|
|
|
|
Asgard25 wrote: What would the difference between ON and FOR be ?
Why aren't you just asking him what he meant?
Jeremy Falcon
|
|
|
|
|
He doesn't want to open a can of worms for himself.
|
|
|
|
|
Employers aren't evil.
Jeremy Falcon
|
|
|
|
|
Mostly no, they're not. Was going to emphasize the usage of for, as a pun, but didn't.
|
|
|
|
|
Isn't the real differential 'open on' or 'opened on'? Open is a state and can apply for an extended time, opened is an action that happens pretty instantaneously (and probably moves it into an open state).
Regards, Stewart
|
|
|
|
|
This is due to a problem being reported after the fact -- a problem may occur on Monday night, but be reported on Tuesday morning. Such a report is reported FOR Monday ON Tuesday.
Your boss could ask two slightly different questions:
How many problems occured over the weekend?
How many problem reports did we receive on Monday morning?
And the related question that some have alluded to:
How many problem reports were in an Open state on Monday at noon?
It is to be hoped that your bug tracking software stores both values so you can create reports based on either.
modified 19-Aug-14 17:37pm.
|
|
|
|
|
Hi guys, I'm having trouble finding a topic that can be implemented in android dev for my sp. I already went to my adviser to get some help but he said that it would be better if I would come up with my own.
I'm thinking of developing an app that can be used by a student or a professor or something that can be useful inside a university. The first thing that I thought is a student record or a professor's handy kit app. However, it would not be much of an sp because it is too easy.
I'm also being careful in choosing a topic because in the past when I proposed a project proposal, I failed to finish the project.
Any suggestions? 
|
|
|
|
|
What are your assignment requirements?
|
|
|
|
|
No such requirements. I just really want to implement an android app for my sp because the field of android dev is what I want to master after I graduate.
|
|
|
|
|
GPS app to help new students find the right buildings?
Voice recognition app that transcribes a lecture?
|
|
|
|
|
Thanks bro, those are good ideas. But one of my friends already thought of doing the gps idea and the voice transcriber is a bit too light I think.
|
|
|
|
|
Something for professors that spots plagiarism?
Something for students that masks plagiarism?
You looking for sympathy?
You'll find it in the dictionary, between sympathomimetic and sympatric
(Page 1788, if it helps)
|
|
|
|
|
Gregg Gonzales wrote: in the past when I proposed a project proposal, I failed to finish the project.
Then you need to be sure you choose a) a subject that you fully understand, and b) a computer system and programming language that you are well above beginner level.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Badger | [badger,badger,badger,badger...]](https://codeproject.freetls.fastly.net/script/Forums/Images/badger.gif)