Skip to main content
Participant
October 26, 2006
Question

File sizes when publishing

  • October 26, 2006
  • 2 replies
  • 249 views
Our IT department has imposed a file size standard on courses that we publish to our LMS. They say that the largest file we can have users download is 480k. This is because we still have slow conections at some sites which do not accomodate large file sizes. Is there a way put the main published.swf file into multiple smaller chunks? If not, how do you recommend we deploy to sites with slow connections?
    This topic has been closed for replies.

    2 replies

    CatBandit
    Inspiring
    October 26, 2006
    Forgot, Don - Welcome to the Captivate User Community!!!
    .
    CatBandit
    Inspiring
    October 26, 2006
    I recommend you get together with your IT people and point out that this is late in 2006, and the dial-up is rapidly becoming a thing of the past. I'm not being a wise guy, I'm deadly serious. A meeting is needed, to explain your position to the IT folks. The IT people often DO make decisions about the networks they are supposed to maintain without having the facts about how those decisions affect network users.

    It is not up to you to conform to their arbirtary commands ... it is up to them to find a way to provide you the services you require from the network (note, I didn't say "their" network, I said "the" network). If IT people had their way, nothing would ever be added or subtracted to/from the network, and no one would be allowed access - that's their "perfect world".

    Okasy, I've had my say on It people, now to your problem. There is no way to chop up a published SWF file. Can't be done. But therre are ways to minimize the SWF size, like avoiding images and reducing project size (in pixels), and eliminating audio, and so on.

    You can also chop the project into sections by breaking up the *.CP file. Keep in mind that when you do so, you will also be changing the configuration of your testing flow (scoring objects like buttons, click-boxes, and Question slides), and may find that you have screwed your efforts at training your end-users.

    Captivate 2 has worked for me on a 56KBps connection and I've used files (SWF) in the 2-4 Mb range. Sure it's slower than on a T1. The "fix" for that is to get a faster connection, not to give up - unless your employer wishes to go back to the days when "testing" required bringing everyone to a central location and putting them in a room equipped with tables, chairs, a live "proctor", a large clock on the wall ... then givng each a paper test sheet and a #2 lead pencil. Ah, the good ole days.