What website features would you like to see in the future?

[pauland]

Please try to keep the suggestions sensible.

If it didn't make you smile, even slightly, then I feel sad about that. TG is a place that needs a few smiles.

[Chris M]

Acorn set me on the detachable Window path and the more I thought about it the better it seemed.

1) Detachable Windows so we could, for instance, have one variant on one screen and another on a second or third screen.
2) In house forms, not a link to an online service, but like CoffeeCup.
3) A Header and Footer section like Word. Anything in a resizable area would repeat on all pages and be sticky.

[Rob-Xar]

If it didn't make you smile, even slightly, then I feel sad about that. TG is a place that needs a few smiles.

Ah were you playing? lol I was taking it seriously like... does he really want that? lol

Acorn set me on the detachable Window path and the more I thought about it the better it seemed.

1) Detachable Windows so we could, for instance, have one variant on one screen and another on a second or third screen.
2) In house forms, not a link to an online service, but like CoffeeCup.
3) A Header and Footer section like Word. Anything in a resizable area would repeat on all pages and be sticky.

1) I'll check on the feasibility on this with the developers. I'm not sure how easy this would be or not.
2) This is kinda on the list but has been rejected a few times due to the amount of work and ongoing maintenance that would be required. I could suggest a very simple form as starters I suppose.
3) I think I know what you mean, although you could group everything and then if you want to make a change, simply open and edit the group and apply sticky / stretchy to it.

[Chris M]

3) I think I know what you mean, although you could group everything and then if you want to make a change, simply open and edit the group and apply sticky / stretchy to it.

Yes, this is how I do it currently but I was inspired by the smart photo grids, which can also be replicated, but they work so well and make work faster and easier. I think it would be nice to e able to drop things in the 'zone' to have the item pick up the same attributes as it's fellow zone members, like the photo grids.

[gwpriester]

I would be happy to see the existing web animation features revisited and an option to reverse an action. e.g. fade in, fade out.

And the UI for web animations really needs to be revisited. Maybe windows so the use can specify a time in seconds instead of trying to figure out the sliders.

[Rob-Xar]

I would be happy to see the existing web animation features revisited and an option to reverse an action. e.g. fade in, fade out.

And the UI for web animations really needs to be revisited. Maybe windows so the use can specify a time in seconds instead of trying to figure out the sliders.

Ya that's high on my list to push for. UI work may be hard to get implemented, especially the preview screen but the animate out I should think be easy.

[Acorn]

Rob, no particular order but others can vote for any as they like.

Acorn#:

1. Replace NavBar graphics with graphic button with font for button text. Keep text as text.
2. Replace NavBar graphic with CSS shape.
3. Replace NavBar with CSS3 solution instead.
4. Add/allow a class of 'layername' to all elements that changes according to the Layer the object is on; possibly selected through Utilities > Names.
5. Publish Variants to subfolders based on the name of the Variant. In other words, separate the lumping of all Variants into one page HTML file.
6. Reflect the Page & Layer gallery object name in the Names gallery.
7. In a Supersite, allow different stretch images as background, based on the page in focus.
8. Ditto, reflect the correct address for the page in focus.
9. Retain image filenames as filename="..." in the Names gallery; augment with any transformations or scaling but keep the hard-thought out name.
10. Allow EXIF information to appear in a drop down for Pop-up Title and Alt and Web Animation Title.
11. Sort out the fault when adding a Name to text.
12. Include 'htmlblocktext' as a value in Names.
13. Render text with a Line width properly. Easy with CSS; do not change the text to an image.
14. c.f., shadows. Note, while a Line width does not render, its shadow equivalent does.
15. Lazy-loading for IE9- images. Lazy-loading in general.
16. A table solution that is screen reader aligned and based on HTML tables.
17. Usable table export to MS Word.
18. Correct Preview rendering of pages with a '%' (RFC 3986).
19. Proper ease-in and ease-out of web animations.
20. Update failed Widgets: QR Code, WebRSS; general widget review. Publish Widget API.
21. Reinstatement of Xara Slideshow Widget into v12.
22. eBook publishing.
23. Add text along Smart Lines.
24. Generation of concordance list to allow built-in searching.
25. General improvements to slideshows to allow editable text; again not images.
26. Promised CSV data import for tables.
27. Locking Pages from being published.
28. Printable output from a website page.
29. Correct text alignments for justified text vs. SPANs. The WYSIWYG dilemma.
30. Ditto HTML issues when embedding into Text Inside shapes.

Acorn

[Rob-Xar]

Rob, no particular order but others can vote for any as they like.

Acorn#:

1. Replace NavBar graphics with graphic button with font for button text. Keep text as text.
2. Replace NavBar graphic with CSS shape.
3. Replace NavBar with CSS3 solution instead.
4. Add/allow a class of 'layername' to all elements that changes according to the Layer the object is on; possibly selected through Utilities > Names.
5. Publish Variants to subfolders based on the name of the Variant. In other words, separate the lumping of all Variants into one page HTML file.
6. Reflect the Page & Layer gallery object name in the Names gallery.
7. In a Supersite, allow different stretch images as background, based on the page in focus.
8. Ditto, reflect the correct address for the page in focus.
9. Retain image filenames as filename="..." in the Names gallery; augment with any transformations or scaling but keep the hard-thought out name.
10. Allow EXIF information to appear in a drop down for Pop-up Title and Alt and Web Animation Title.
11. Sort out the fault when adding a Name to text.
12. Include 'htmlblocktext' as a value in Names.
13. Render text with a Line width properly. Easy with CSS; do not change the text to an image.
14. c.f., shadows. Note, while a Line width does not render, its shadow equivalent does.
15. Lazy-loading for IE9- images. Lazy-loading in general.
16. A table solution that is screen reader aligned and based on HTML tables.
17. Usable table export to MS Word.
18. Correct Preview rendering of pages with a '%' (RFC 3986).
19. Proper ease-in and ease-out of web animations.
20. Update failed Widgets: QR Code, WebRSS; general widget review. Publish Widget API.
21. Reinstatement of Xara Slideshow Widget into v12.
22. eBook publishing.
23. Add text along Smart Lines.
24. Generation of concordance list to allow built-in searching.
25. General improvements to slideshows to allow editable text; again not images.
26. Promised CSV data import for tables.
27. Locking Pages from being published.
28. Printable output from a website page.
29. Correct text alignments for justified text vs. SPANs. The WYSIWYG dilemma.
30. Ditto HTML issues when embedding into Text Inside shapes.

Acorn

Thank you for your list, there were certainly a number of points there that I hadn't considered before:

1) This kinda was planned for 16.1 but we ran into into problems which will be fixed possibly after 16.1 release.
2) Can certainly suggest this as part of the NavBar redesign.
3) As above
4) Can you give me an example of how this would be used?
5) We have a couple of solutions to improve the handling of mobile variants, although I don't think splitting them into separate files with redirects is planned. We're also looking into possibly being fully RWD with smart layouts in the future that may do away with the whole variant concept, although this is early in its development
6) Could suggest this
7) as above
8) as above
9) I believe it's planned as part of the SEO work to keep filenames on export, will certainly push for it anyway.
10) Could suggest
11) Which fault is this?
12) Could suggest, although we generally discourage use of this name generally due to the fact we can't then guarantee the accurate positioning of text. I will try however to push for a cleanup of code so there aren't so many span tags, especially with fully justified.
13) Can suggest. I saw a lot of examples use webkit extensions so I guess the concern is cross-browser compatibility.
14) Can suggest.
15) As above
16) Tables are still heavily in the development works. There's a number of improvements that are going to come shortly but still loads more to do. Exporting tables to HTML is a wish-list item but not sure on it's possibility.
17) similar to above
18) Can you give me an example of what you mean? I've seen some users have '&' and '.' in page names which causes problems but not sure how you would resolve that other than through either a warning or letting them know what will happen.
19) Is on the consideration list
20) Widgets do need generally improving, it's just one of those things that we need sometime to spend time on and it's hard to find anyone with time.
21) They won't reinstate the slideshow widget in V12 I can tell you now. I can suggest it but pretty sure that would get shot down (as generally anything that involves earlier versions)
22) Can you elaborate on what you mean by ebook publishing? Like supporting .epub format?
23) Some early designs are coming in 16.1 with more on the way.
24) Do you mean something similar to the table of contents but for every word used?
25) Slideshow improvements is certainly on the list, still debating how to go about it.
26) Should be coming soon
27) Can suggest it.
28) This is something that was suggested before but generally we decided against it as printing from Web is hard to properly do, and is not a problem unique to Xara websites.
29) See 12
30) As above

Thanks
Rob

[Acorn]

Rob, positive and quick responses, thank you.

For Acorn#04, this is generally for searching down a problem object or alignment issues. It could be useful for documenting websites in PDF layer reveals.
For Acorn#11, the Name is set insides a pair of empty SPANs when it is added to the complete text area either a Select > Name or Text tool > Select All > Name. If a word is highlighted and a Name added, it works correctly.
For Acorn#18, create an index page and add another with '%' in the filename and simply Preview this second page --> Big red cross pop-up.
For Acorn#22, yep .epub would work as I think that is effectively a wrapper of content.
For Acorn#24, a concordance list of every word and its locations by page in the entire site.

Many thanks,
Acorn

[Rob-Xar]

Rob, positive and quick responses, thank you.

For Acorn#04, this is generally for searching down a problem object or alignment issues. It could be useful for documenting websites in PDF layer reveals.
For Acorn#11, the Name is set insides a pair of empty SPANs when it is added to the complete text area either a Select > Name or Text tool > Select All > Name. If a word is highlighted and a Name added, it works correctly.
For Acorn#18, create an index page and add another with '%' in the filename and simply Preview this second page --> Big red cross pop-up.
For Acorn#22, yep .epub would work as I think that is effectively a wrapper of content.
For Acorn#24, a concordance list of every word and its locations by page in the entire site.

Many thanks,
Acorn

4) Could suggest this as a registry key entry I suppose, similar to the FTP debugging options.
11) I see what you mean. I'll investigate and log it with the developers. There shouldn't be empty spans around.
18) Wow, first time I've seen anything like that. I'll get it logged with developers.
22) Can suggest that. I've only briefly looked into it but it looks just like XML? Shouldn't imagine it being too difficult but it really depends on the demand.
24) I suppose we already have the table of contents that does something similar, could suggest it as another text feature.