Michael Butler wrote:
> >>
> >> Just learn HTML,
>
> Absolutely. Even if MetalWeb worked perfectly, I would still recomend
> learning at least the basics.
There you go. If you learn a little HTML, you'll soon discover alle the
things that MetalWeb does wrong.
> >> [HTML 4.0]
On the manual of AWeb II 3.3 is says 'HTML 4.0 compatible', although I doubt
it has a full 4.0 implementation. I'll give it a try with some layers soon.
> >> [Edit in a text editor]
> >
> > Does that allow you to transfer files to your website
> without altering
> > the pathways for the pics (hotlinks, etc.)?
> >
>
> To change your paths you would have to deliberately retype
> them. I find
> MetalWeb has the nasty habit of changing my paths whether I want them
> changed or not.
Again I agree. I do not understand how, why and when MetalWeb decides these
things should change. But unless I tell it to do so, it shouldn't touch
them.
If any of you are thinking 'why is he complaining so much about MetalWeb',
just go to the Vapor bug report site, and check out a few of the 15 or 20
bug reports I entered. Apart from the bugs, there are too many things
MetalWeb just doesn't do.
A little example: try and make two frames, one with fixed width, the other
taking the rest. Not percentages. That means you have to use something like
"200, *" instead of "15%, 85%". If you use the first annotation and load it
into MetalWeb, it will change it to percentages. Always. There are a lot
more things like this, which do not allow you to use MetalWeb after you made
a certain change.
I've put more than enough time into finding their bugs for them. If I want
to produce something, MetalWeb in it's current state is the last tool I will
use. But the fact remains that I paid for it and would like to see some
decent support. I have registered many many Amiga programs and regularly
contact authors about their products but (as much as I hate to say it) never
have I encountered a product as extremely buggy and badly supported as this
one.
Wouter Lamee
