MICROSOFT OFFICE 2010 PROJECT STANDARD X86 SP1 [thethingy]

0 views
Skip to first unread message

Vaniria Setser

unread,
Jun 29, 2024, 10:22:43 AM6/29/24
to dapusinca

An alternative display for visualizing and managing group schedules Microsoft Outlook is one of the most widely used applications in the world but its calendar has frustrated many users who want to view several schedules at once. With Outlook you can view multiple calendars side by side but after you add a few calendars the information disappears into a forest of heavy gridlines and background colors.

-- Simon Shutter (email) Nice redesign in many ways. However, I have a few gripes about your article.First, the nitty gritty: --It's not relevant what size your monitor was--not that I can tell... maybe you can expand on this if is relevant.--The link ( ://www.w3.org/Graphics/SVG) is not valid. Looks like two links in one.Second, the subjective:--saying SVG is "a standard" is probably fair, but "the standard" changes the meaning entirely. I'd argue no one can view SVG and it's far from adopted as a standard in any way. Also, for the record, I see PNGs when I click the thumbnails. Again, if this is relevant or actually accurate, please correct me.Finally, to be fair, you might try including the same information that the Outlook screens have--namely, buttons that access other parts of the product. These can be toggled on/off but still. More questions:Also, I think the thingy you have in the top right corner might be really interesting, but from these images I'm not sure what it does. Can you zoom in and what portion of the entire set of data you're viewing?How do you propose handling even more information--like say there are more people in the team? And, any thoughts on ditching the whole legend?Despite my negative points I think it looks like great work. Thanks! -- Phillip Kerman (email)

Thanks Simon,The link to the product helps a lot because I didn't even realize it was available... the mention of "other off the shelf solutions" I guess referenced it--but I don't think mentioning this fact more clearly would have hurt. Some people might think it was a pitch--but whatever.I'm not trying to kill SVG--but note Adobe has sunset-ed that plugin. It's just sort of hard to get behind SVG when its performance is so lacking. Flash, while not nearly as open (though, for the record, is open in many ways) is a lot more appealing to my customers. The examples in that link ( ) are nice--they very effectively show so much of what you had to describe in words. However, I sure hope the actual product isn't in SVG! The performance makes it unusable. For example, upon clicking one of those demos my computer becomes unresponsive for a good 10-20 seconds while the page renders. I realize SVG vs. Flash isn't your point either, but I was just trying to touch the examples and this came out.Thanks! -- Phillip Kerman (email)

I really like your idea, I've come up against these problems often. I hope this makes its way to iCal and Google Calendar as well. Like any early effort, there's plenty of room for improvement, but overall a great idea. That you have a web demo up in addition to the application is impressive.Just a couple of opinions, the first being that a more maplike color palette would be nice. Personally, as someone who deals with several operating systems a day, I like the SVG idea over Flash. No need to introduce that heavy proprietary tool kit if you already solved the problem without it, and I have a sneaking suspicion there's some room to optimize this code still, eh?That, and I might put some sort of 'about' section on the site. It's nice to know who's behind the curtain.Keep charging,Niels -- Niels Olson (email)

Outlook's handling of multiple calendars definitely needs improvement, and I applaud how much better you've done it than Microsoft's version. I especially like the cloropleth design; it's dead-tree compatible, and accessible to the color-blind! Both are absolutely essential in my view. However, I experienced one difficulty reading your new version of the calendar (weekly view) -- I find it very hard to cope with the fact that time is displayed on both axes, hours vertically and days horizontally. I expect that when a manager looks at several calendars simultaneously, his objective is to find times when schedules conflict or when all employees are available (say, for a meeting). If I want to find time for a meeting on your weekly view, however, I strain to try and overlap all of the "Monday" calendars in my mind at once, then try the "Tuesdays", and so on.As a refinement, I would suggest putting people in the columns, and continuous time on the vertical axis. Use minor tick marks for hours and more prominent tickmarks or gridlines to separate days. That way, if a manager is looking for a good time to hold a meeting, she simply scans for a horizontal whitespace gap. If she wants to know who will be in the office at 3pm on Wednesday, she simply finds that hour on the vertical axis and looks to the right.Question: Could you perhaps post screenshots of how the same data looks in Google Calendar? -- Joseph Clark (email)

Maybe a better focus is to ask WHY one needs to look at Outlook calendars from multiple people.At my place of work, it is usually it is to find an open spot for a group meeting. Note-We do not use Outlook to schedule project work. That is the function for MS Project or a similar application.Having the calendar show the "open" times for the group would be a better display, rather than forcing the user to manually find the possible slots. At least one competitor to Microsoft Products does this very well. Meeting Maker adds a separate column to show the possible open "group" meeting times, much like the week-view alternative display proposed by the original thread. One may also make a list of names and ask for the next open time. (This often returns humourous results) Then the meeting coordinator can look at the individuals for any obvious conflicts (locations, vacations, etc). We also place meeting locations (conference rooms) with a schedule in the system and one adds this to the list of required attendees.Of course, heavily scheduled folks are often not available for the next ten years. And if an important executive wants everyone in at 6am (before scheduled work time), then that *will* show up on everyone's schedule. Computer applications have yet to solve those scenarios and instead we rely on actual human verbal communication for 'special' requirements.AAS -- Alice Skehan (email)

The problem here is the switch to using such technical language seems abrupt since tracking pixels and cookies are introduced after this paragraph in the next section (in "Use of info" / "Information We Collect"). (It seems as if the text text may have been re-ordered at some point.) I think just mentioning that they are "technical terms" helps alleviate this problem. I also think "some" over-estimates how many people know that stuff, so "only a few" would make less people feel inadequate. My attempt at improving this paragraph reads like this:

The old privacy policy contains 16.790 characters in its main text versus the 33.582 characters of this draft as of now. So a doubling. - Is this a good development? Where's the summary, where's listing of principles? - Isn't that what we should be discussing, and not some long winded explanation and elaboration (even with cute animals)? --Anjoe (talk) 08:36, 12 September 2013 (UTC)

I notice that in a couple of places the policy states that WMF will "seek to" do something: We seek to put requirements, such as confidentiality agreements, in place and we seek to put requirements, such as reasonable technical and contractual protections, in place to protect privacy. (The same language is used above by User:Mpaulson (WMF).) This is presumably intentional, and to the extent that it is intentional, unacceptably feeble. WMF policy must surely be to succeed in putting these measures in place to protect privacy, not merely to seek to do so. If WMF is unable to put measures in place to adequately protect private information in the hands of third parties, it should not be giving the information to those parties at all. Spectral sequence (talk) 21:24, 12 September 2013 (UTC)

Were the drafters of this policy given or did they look at any other policies as models of policies that do it right? Which ones? I don't recall the site names offhand, but do recall a few sites that had great policies. What privacy policies do folks think are exemplary? Perhaps some good ones to look at: EFF?, FSF?, Yelp just updated theirs; it's relatively good, ...? What makes for an exemplary policy, IMO? It's short. It's specific. In terms of language, if not meaning, it's the opposite of the typical privacy policy.--Elvey (talk) 22:32, 13 September 2013 (UTC)

: "A policy is a principle or protocol to guide decisions and achieve rational outcomes. A policy is a statement of intent.." :Policies_and_guidelines: "Policies explain and describe standards that all users should normally follow.."

Under the heading Use,the policy talks about what would be my data, or my experience and then continuesto how we ("we", WF Inc) would understand the aforementioned better.For the latter undertaking, the text fails to give legal or technical or economical reasons in most of this section (and others).The text does appeal, though, to readers' susceptibility to advertising by using phrases like

Logging IPs of logged in users is a tool of surveillance. It is unnecessary. This only opens the door to governments who will ask you to hand over these IPs in order to get more information about their target. Stop it now, before it is too late. Who cares about the 10000 sock puppets if you can protect the human right on anonymity for the rest(>1000000) users? That only "a few admins will have access to the IPs" does not help. Who controls the controler? Who controls what happens in secret with the data ? You might add it s not secret that we collect the data: "We stated it in the policy that the data would be collected". But it s secret (not viewable) who accesses the stored data and when it was accessed. Storing the IP of logged in users is against :Wikipedia_is_anonymous . You can derive too many things by the knowledge of the IP to say that the user stays anonymous. SO DO NOT STORE IT. IT IS NOT NECESSARY. --92.193.47.88 20:16, 16 September 2013 (UTC)

b1e95dc632
Reply all
Reply to author
Forward
0 new messages