web page x4

[Charles Moir]

The installer sometimes fails to register the HTML export dll. This will be fixed for the release next week.

[Odat]

Just making a quick page, somehow the text and the graphic got saved together and messed up. Has anyone else seen this ....

I think that happens if you accidentally group the text together with an image. According to the release notes the export makes one image for every group, and one per non-text object that's not in a group.

[ss-kalm]

It wasn't grouped Odat. I didn't save the original xar, but will try to recreate it and post the xar.

[ss-kalm]

OK it recreated quite easily .... Enclosed .xar and the relevant jpg

[BQ]

Tao,

THANKS for the example.

In my opinion, with this new upgrade to allow creation of html pages in Xara makes it increasingly important to add a spell-checker in a future release.

Thanks Xara Team for all the great features in the new release.

[ss-kalm]

OK.

I've done some more testing. If the images are jpg's and they are 3D and angled. The HTML conversion will ALWAYS make the result square, even if the text intrudes into this space.

I have used Lorem Ipsum text, but I suspect that the resulting text would probably be meaningless.

I think that it's something that could be considered a "bug" and may need some more looking at.

[BobInce]

If the images are jpg's and they are 3D and angled. The HTML conversion will ALWAYS make the result square, even if the text intrudes into this space.

Seems to me there's little Xtreme can actually do about this. JPEGs can't do transparency, so if you've got text laid out behind them they're always going to obscure the text. It could work if the image was put behind the text, but then as it stands, 'repel text' on works on text behind an object.

The only real alternative would be to export *all* graphics as transparent PNG. Which would improve output, but vastly increase the size of pages using photos which is a very common use case.

It's true, but 90% of people using Xtreme won't care.

That's the problem! If a non-expert thinks they're making proper web sites using this, they'll have a rude awakening. It's a quick'n'dirty WYSImolWYG rapid prototyping tool, which is why it's great to have it there in the Export formats list, but it shouldn't really be pushed as a major application area.

[stlewis]

Where this feature will be great for me is in the shortlist-design to mockup stage - where you want a functional page but where the CSS can be clunky.

I suspect that it will be worth putting just a few words of text where you want text to be on the page - this will be enough to put in a div. The other trick I will try is where you want a rounded corner box, breaking the box into top, bottom, left and right pieces - Xtreme hopefully then will do something which each of these - rather than creating one huge box. It's not Einstein after all!

I'll post when I have a go at this over the weekend.

[handrawn]

WYSImolWYG ! !

and for those of use who need very quick non commercial websites it will be useful I am sure...

[Charles Moir]

Bob is correct, JPEG have to be square because they do not support transparency, and so if there things around the edge on the page they will get rendered into the background of the JPEG.

The only answer to this is that the object be made into a PNG, which we do for most graphics, but not photos (assuming they are JPEGs already).

But there's a simple fix to force an image to be a PNG - and that's to give it a name 'PNG' (using Name 'tag' icon on the Selector Tool Infobar). Simple as that.

BTW the rule is that all graphics are exported as transparent PNGs except JPEG images which are kept as JPEG (although re-sampled to web resolution). In this case it's an extruded JPEG and so we could perhaps always make them PNGs as well, but keep in mind that PNGs take a lot more space than JPEGs, and not ideal for photos, even extruded ones.