How can I block some pages from being calculated by xara for output to the web. I just want to work on the one page I have and not have to wait minutes for all the pages to be converted for export.
Printable View
How can I block some pages from being calculated by xara for output to the web. I just want to work on the one page I have and not have to wait minutes for all the pages to be converted for export.
There are two things you can do: Preview page instead of Preview whole website (File/Preview Web Page or Shft+F5) and Fast Publish (go to Utilities/Web Properties/Publish and tick Fast Publish). The first option is only for local previewing and the second is for publishing/uploading only those files that have been modified.
Thank you Boy, tried both, they are still slow, problem being low memory on laptop and large pages. I am waiting to add 8G to my system and will try soon. Meanwhile I am doing pages on their own and once finalized adding it to the main website that is slow.
Eight G extra might just do the job.
Hide all the Layers of the Pages you are not working on.
Acorn
Thanks, Acorn did that, not sure if it really helps. Do you know this for a fact?
Possibly by selecting Publish / Settings / Fast Publish (Only changed Files).Quote:
How can I block some pages from being calculated by Xara for output to the web.
Copy the content of that single page & publish it to a sub-directory.Quote:
I just want to work on the one page I have and not have to wait minutes for all the pages to be converted for export
Thanks Egg. I am now doing one page at a time and once finished and approved copying everything on that page and pasting it to the main file. The layers will no work nor the fast publishing. Xara happens to calculate everything on all pages regardless of just exporting that one page.
Installed memory 8G and the pages render 3 minutes faster than previously.
3 minutes? Wow, that must be a relief!
Yes, it was a shocker. But I learned now to work on a page by itself and once finished copy and paste into the larger site.
Doesn't sound ideal but better than having to go for a coffee every time you make an edit.... :(
Well, during rendering calculations for output to the web, I checked the cpu usage and it is at 30% and free memory is almost 6G, So I wonder even a faster machine with more memory will still bear the same results. I do not think Xara is optimized to use full CPU power.
Here is a screen shot of when converting document for export and what cpu and memory it uses.
Attachment 124563
[QUOTE=behzad;612260]Well, during rendering calculations for output to the web, I checked the cpu usage and it is at 30% and free memory is almost 6G, So I wonder even a faster machine with more memory will still bear the same results. I do not think Xara is optimized to use full CPU power.[/QUOTE
How many pages are being rendered at a time and how long does it take?
Here is the info. Pages are long and full of text and some images. Click here for an example of one of the pages.
Attachment 124564
But how long does it take to publish the site?
5:40 min. All the pages.
We had a PM: get rid of Xara NavBars; be wary of Smart Tables; filename repeating images.; never group text; avoid shapes that are just for display unless they are pure solid rectangles with curved corners and a modest line width; avoid Transparencies that are not Flat. Effectively. anything to keep you design vector and text.
Acorn
Dear Acorn, I think one of those recommendations implies to this website that I am designing. The cpu is not even using full potential and it is rendering at max 30%. This is a problem with Xara at processing level. They are using engine that was originally designed for rendering vector graphics for screen and print not for web.
Until Xara offers a test file for checking performance, there is not a lot we can do.Quote:
Originally Posted by behzad
Acorn
I really think if they allowed for one page only (page that is being worked on) to be processed, would speed things up. For now I am making a separate page on its own, once final I import it into the larger site.