Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

How to speedup Pubish to Local Webroot?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    How to speedup Pubish to Local Webroot?

    I have about 10 a5w's, 40 a5wcmp and when I publish ALL to local webroot it takes about one hour. Mind you, my Celeron 466 is not a speed demon but this is too long when I TESTING.

    I remember seeing something about speeding up the publish & html.

    If I go to a a5w and RIGHT click, I have 2 choices:"Publish" and "Publish to Local WebRoot" Which one should I be using for testing?

    When I am in the Publish window, I am unsure as to whether I shuld tick the "Publish new or modified files" and clear Publishing History.

    Any thoughts or ideas as to how I can get down the publshing time (other than buying a new computer) is appreciated.

    Thanks for the HELP to ALL A5 gurus.

    dewayne

    #2
    Re: How to speedup Pubish to Local Webroot?

    hi D.

    "Publish" and "Publish to Local WebRoot"
    in your case (assuming that you have no other destination
    setup to publish to) these are both the same thing


    clear Publishing History
    when you clear the puiblishing history - this has the effect of making
    all components and pages new - this means that they will be published
    if you select the "Publish new or modified files" checkbox

    you really dont need to publish anything except the NEW items

    so assuming that you have everything published and then you make a new
    page then you would only need to publish "Current file"
    this takes a few seconds leave the "Publish new or modified files" checkbox checked.
    regards

    martin
    www.jollygreenthumb.com

    Comment


      #3
      Re: How to speedup Pubish to Local Webroot?

      Thanks for the info.

      I have 1/2 dozen Linkers & Tabbed linkers. I am not sure what I should be published if I change ONE a5wcmp on a tabbed linker. Do I just publish the Tabbed Linker? Does it automatically publish the changed "children"
      grid.a5wcmp?

      dewayne

      Originally posted by martin horzempa View Post
      hi D.

      in your case (assuming that you have no other destination
      setup to publish to) these are both the same thing
      when you clear the puiblishing history - this has the effect of making
      all components and pages new - this means that they will be published
      if you select the "Publish new or modified files" checkbox
      you really dont need to publish anything except the NEW items

      so assuming that you have everything published and then you make a new
      page then you would only need to publish "Current file"
      this takes a few seconds leave the "Publish new or modified files" checkbox checked.

      Comment


        #4
        Re: How to speedup Pubish to Local Webroot?

        Hi D.

        sorry i cant speak definatively on your question
        if i change a component i will republish the grid linker that
        uses it - i am not certain that this is a must
        but it makes me feel better
        as a general rule i dont republish the pages that contain the
        changed component unless i have changed something that the page
        addresses such as the controls that might contain the filter or order
        data
        regards

        martin
        www.jollygreenthumb.com

        Comment


          #5
          Re: How to speedup Pubish to Local Webroot?

          Components are minuscule in size, it can't take an hour to publish unless you have a bunch of graphics embedded in the A5W pages. Are you publishing to localroot, or via LAN or FTP?

          You just need to publish the components you change, not the linker in the case you suggested below. It won't automatically publish any child files because the grid linker doesn't know about the children other than when launched in the browser.

          General note - the Publish New or Changed files.. doesn't always work and will skip changed files periodically.
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: How to speedup Pubish to Local Webroot?

            Thanks. I will now ONLY publish what I change.

            A few more details. I am publishing to my local WebRoot on my computer not on a network or via FTP. The a5w pages of which there are about 8 have a small title image at top. The components ONLY have the icon in the fields with lookups.

            As you mention, publishinig the "linker" does not publish the child files then what is it taking so long to do? Just curious.

            Still takes 1 hour on my celeron 466.

            DeWayne

            Originally posted by Steve Wood View Post
            Components are minuscule in size, it can't take an hour to publish unless you have a bunch of graphics embedded in the A5W pages. Are you publishing to localroot, or via LAN or FTP?

            You just need to publish the components you change, not the linker in the case you suggested below. It won't automatically publish any child files because the grid linker doesn't know about the children other than when launched in the browser.

            General note - the Publish New or Changed files.. doesn't always work and will skip changed files periodically.

            Comment


              #7
              Re: How to speedup Pubish to Local Webroot?

              Dewayne,

              I agree that it should not take an hour. I just tested my "kitchen sink" app (this is where I dump everything I deveop into one app.) It has 236 a5 pages, 25 html pages and 263 components, plus about a dozen images.

              I did a "publish all", unchecked the "publish only new" and cleared publishing history, so this included everything. It only took 15 minutes.

              My machine is not a speed demon either, but it is faster than yours: it's a PIII with 1 gig memory and XP Home.

              You said you were using a Celeron 466. How much ram and what operating system are you using? I think you may have to upgrade your hardware and/or operating system if you want more speed.

              Pat
              Pat Bremkamp
              MindKicks Consulting

              Comment


                #8
                Re: How to speedup Pubish to Local Webroot?

                ...and what is the total size of all files in your web projects folder (the files that are being published)? For a test, go to View / Settings / Preferences / Web Publishing and change the value of Show File to be Published to YES. This will list all files just before they are published. Look for files you did not expect.

                Another way to test the total size of all files is to rename your c:\A5Webroot folder to something else and republish all files. Then look at what was actually published to the new A5Webroot folder. Again, look for files you did not expect.

                For example, if you have selected a different Style for each component, it will have to load all the files for each Style.

                If everything is within normal ranges, then, as Pat said, you have to upgrade the computer or at least the RAM should be > 512.
                Steve Wood
                See my profile on IADN

                Comment


                  #9
                  Re: How to speedup Pubish to Local Webroot?

                  Thanks for the help.

                  All my components have one style. Size-wise the files I am publishing are apporx 5MB composed of 22 a5w (158KB) & 130 a5wcmp (at 4MB) & a gaggle of others. A breakdown of the a5wcmp gives 64 small files of 11kb each for report buttons & 28 files for Lookups (900kb total in size).

                  To me, a non-programmer there is not much meat there to take so long. I can see what files are being published & there arent' extra ones or ones I don't recognise.

                  I guess it is time to bump up the hardware (RAM to 1GB & faster CPU). Curious never been a prob with our desktop A5 application. But taking 1 hour to publish 5MB worth of WEB-files is frustrating!!!!!!

                  dewayne

                  Originally posted by Steve Wood View Post
                  ...and what is the total size of all files in your web projects folder (the files that are being published)? For a test, go to View / Settings / Preferences / Web Publishing and change the value of Show File to be Published to YES. This will list all files just before they are published. Look for files you did not expect.

                  Another way to test the total size of all files is to rename your c:\A5Webroot folder to something else and republish all files. Then look at what was actually published to the new A5Webroot folder. Again, look for files you did not expect.

                  For example, if you have selected a different Style for each component, it will have to load all the files for each Style.

                  If everything is within normal ranges, then, as Pat said, you have to upgrade the computer or at least the RAM should be > 512.

                  Comment

                  Working...
                  X