Ideas

This board is only for raising and voting on feature requests (Ideas / Suggestions).
Please raise any Bugs via "Get Help" button on your calendar admin dashboard.

More Prominent Display of Event Documents

Currently, at the very bottom of a calendar event, there is a space for hyperlinks for attached documents.  I would like to see this space positioned in the column of event details nicely displayed on the right side of the window frame.  Our organization heavily relies upon brochures, registration forms, and the like to conduct business, but with the links so small and far down the window, many times they are beyond the viewing area, and people are not generally inclined to realize they have to scroll.  A workaround could be adding a small box field area in this same Details pane to insert hyperlinks.  Thanks.

  • Guest
  • Apr 12 2017
  • Needs More Votes
  • Attach files
  • Admin
    Rik Logtenberg commented
    April 19, 2017 12:37

    Hello! Thanks for raising this idea!

    We will keep checking the votes for it, in order to prioritize the development.

    Thanks,
    Timely Dev Team

  • Guest commented
    April 19, 2017 13:48

    The reason that software features must be subject to 'votes' is not the fault of the user, directly, although I will admit that users are terrible in enunciating their needs clearly, given modern propensity for titillation over substance fueled by massively short attention spans.  No, the fundamental problem is that there has been no fundamental improvement in the approach to software development for the micro computer since its advent back in the late 1970s.

    Software application development is still a matter of line by line logic with minutia as the focus rather than real-world tasks, and software even in the year 2017 still shows a breathtaking immaturity in terms of comprehending the user experience.  Everything is developed specifically 

  • Guest commented
    April 19, 2017 13:49

    I see that your comments tool chopped off my comment without telling me.  Rude...and it makes my point.

  • Guest commented
    April 19, 2017 13:50

    ...rather than for a larger purpose.

    I shouldn't have to request something so specific as moving a hyperlink to a different cluster of pixels in a formatted layout.  Instead, the larger question should be:  if I am a user, how do I quickly and easily access attachments to calendar items?  If software development was managed by architects, rather than the developers themselves, tasks would be broken down in the form of a logical hierarchy which would guide the construction of features.  The question I posed above, then, would loom over a *host* of feature'/functions, not just one.  In other words, with the constraints set by use cases, developers would see that 'prioritization' of their work would simply fall into place.

    Developers have long complained that one person's desperate desire is another person's nonchalance, and therefore, for anyone to insist that *his/her* need should take precedence is to ignore that there are scores of others who feel the same way.  This is a disingenuous argument:  it comes (once again) from the notion that applications are merely random collections of features - all competing with one another for space and time, and developers have to develop systems (e.g., 'voting') in order to make sense of it all.

    Instead of disdaining the faculty of common sense as developers do, they should *embrace* it.  (I have to use asterisks now because the text formatting feature in this tool is broken.)  They should design their applications around the real world and not see them as simply collections of pokes and clicks.  They would ask hierarchical questions, arrange them in logical order, and the interface of their work would reflect this kind of intelligence.

    The first question here is:  why do humans use shared calendars?  Try to argue that inserting a photo is of the same logical importance than an event's Date, Time, and Location.  Yet...this is precisely how developers see software:  an un-prioritized, random collection of features.  No, someone had to step in and tell them, "Look, if we offer our customers *anything*, we have to make sure that they have the ability to enter and recall the Date, Time, and Location of events."

    Now that I have established that there indeed is a logical prioritization of the features in an application, the next question to ask is:  at what point does that construct end?  The answer:  only when the primary use case requirements have been fully satisfied.  (Ignoring this principle is not just the failure of Time.ly developers.  I can get a hideously expensive iPhone in a variety of different colors, but try keeping it attached to a network.)

    Use cases for events demonstrate clearly and unequivocally that there is much more detail to a typical event than a standard calendar interface can accommodate.  This is not the fault of the calendar application:  to design such an interface would require turning the calendar into a database, and one would require a monitor the size of a small television in order to see everything.  Yet...this 'secondary' information is vital to a user's ability to participate in the event.  For example, what good is it to tell a user when and where an event is taking place if s/he is also being asked to bring a dish to pass and register for a 50-50- charity drawing?

    This is where documents, such as flyers, registration forms, etc., come in.  They handle the rest of the details that the calendar interface does not and should not be expected to handle.  Yet...without this crucial information, great problems can arise for even organizers and guests.  The upshot is that this information is every bit as important in many use cases as Date, Time, and Location, yet the Time.ly application currently treats it as if it is simply just another feature, to be relegated to the very bottom of the popup window.

    I have use statistics to back up my request.  At our last meeting, which required additional documents to be read, filled out, and mailed, a full *third* of the constituency was unaware of them since the link for the documents was at the very bottom of the event window, off-screen.  Another 10-15 found out about the link to the documents only by word-of-mouth.  Had your developers understood the concept of event information, they would have realized that the information contained in the links to websites and documents is of vital importance to a successful meeting and would have included at least a way to workaround the issue, such as (as I suggested) the ability to include a text reference in the main detail area of the event to links located at the bottom of the page.

    As it stands now, I have to create a separate space on the calendar page for event documents, displayed prominently so that people can see them THEN they have to navigate to the associated item in the calendar.  This, in effect, makes the feature of embedded links in the calendar items moot, but it's the only thing I can think of to keep people from missing these documents.

    I have little confidence that my need will receive any votes.  Most people today have resigned themselves to bells and whistles, or hone in on narrowly specific features they'd like to see, which are then selected on the basis of pizzazz.  My request, however, is entirely fundamental with the spirit and intent of a shared calendar:  How can people use your application to learn *everything* they need to know about an event, quickly and easily, and without confusion?

    To me, this is part of the chart of a shared calendar tool.  Thank you.

  • Guest commented
    April 21, 2017 23:05

    P.S.  There are many suggestions I could make for feature-function improvements, such as being able to display the difference between and event that takes place over a range of days vs. an event that takes place on two separate days.  They appear the same, for me, at least, in posterboard view.. Being able to choose the colors of the event categories would be nice, as well, since some of them can clash with a site's general color scheme.  However, I understand that these things are not fundamental to the function of a calendar in the real world and am content to either submit suggestions or just wait until they become part of core.

    All I am interested in is people being able to get to an event being properly prepared with what they need to know in order to participate.  Anything else is gravy.

    Also, I didn't want to leave the impression that I believe the Time.ly product is inferior.  It is not.  It is a great product that I've received many compliments about.  This is why I hold it to a higher standard.