Re: Amaya 1.4a report

In-reply-to: Your message of Fri, 16 Apr 1999 20:15:58 -0400."
             <Pine.WNT.3.95.990416190317.150A-100000@w34.ic-public.utoronto.ca>

> 
> Tested on:
> ==========
> 
> Build: Windows 95 executable
> OS: Windows 95 OSR 2
> 
> Bugs
> ====
> 
> Browsing
> --------
> 
> Even with 16-bit colour modes, Amaya displays badly dithered 256-colour
> images.

That should work better on next release.
 
> Structure view window does not wrap long texts, and the scroll handle is
> not properly designed for horizontal scrolling under structure view.

It's a choice.

> When Amaya is looking up a remote host, I cannot abort the process.

The lock is due to the system call. We should work with processes to avoid the
lock.

> Does not support automatic URL completions.

It's a choice too.

> Floating object alignment is not properly supported.  For example, <IMG
> align="right" src="http://foo.com/animage.gif" alt="my boat"> will not
> align the image to the right margin of formatted view window.

It's not implemented yet.

> Editing
> -------
> 
> Sometimes typing 'h' in formatted view will not enter 'h' into the text. 
> Instead it shows the 'About Amaya' dialog box. 

It seems that 
> 
> Loading a file automatically closes all windows, except the formatted view
> windows. 

Yes. When you replace a document by another Amaya close extra windows.

> Clipping behaviours are horribly designed.  For example:
> 
> <P>
>   <I>
>     text
>   </I>
> </P>
> 
> If I try to clip the inner level of text (lines 2, 3, 4), Amaya
> automatically puts the outer tag level (all 5 lines) into the clipboard.

If you select the text only, Amaya will copy the text, but if you select the P
element, Amaya will copy the whole structure.
> 
> Contents between different views of a document is poorly synchronized. 
> For example, if I type some new texts into the structure view window,
> texts in formatted view window are not automatically updated even when I
> click on formatted view window, unless I modify the line within structure
> view twice.  This can result loss of data. 

It's a feature. We want to avoid to redraw all opened views for each new 
entered character. It makes Amaya more reactive.

> There is no way to 'demote' HTML tag levels.  For example:
> 
> <P>
>   <I>
>     text
>   </I>
> </P>
>
> If I choose all 5 lines, I cannot remove the <P>...</P> bracket easily.

Removing the <P>...</P> will make the structure invalid. Amaya won't allow you
to do that.
But when it's valid the entry Transform in menu Edit allows you to do this 
kind of things.

> Others
> ------
> 
> Even though I tell Amaya to relocate temporary directory, it always create
> temporary files on C:\TEMP.  The allocated directory is not removed after
> proper exit. 

Directories are not removed but it's the case of files within these 
directories.
The next release will allow you to locate directories in another place.

> Suggestions
> ===========
> 
> Browsing
> --------
> 
> An option to save window locations and view settings automatically between
> sessions. 

We're implementing a preference menu which will allow you to register the
current window sizes as default sizes.

> A read-only mode to prevent accidental key presses.

It's available yet. The pen button swiches to browser<->editor mode.

> Editing
> -------
> 
> A option to specify startup directory.

We could use the directory where the startup file is located.
 
> An option to reveal hidden HTML codes under browser window, to allow
> easy and precise HTML entries within proper tag/stack levels.

The structure view could be used for that??

> View windows for showing available styles, as well as how style settings
> are inherited. 

It's not clear for me. The next release should allow you to disable and enable
CSS style sheets on documents. Is it what you want to do?

> Saving/loading
> --------------
> 
> When saving HTML, Amaya should allow saving in 'raw HTML' (ie HTML
> document that is not re-formatted by Amaya), to allow more advanced
> debugging not offered by Amaya. 

A document edited by Amaya is reformatted because Amaya works on a tree and not
on a linear representation of the document.
 
> When saving HTML, Amaya should offer following options: Strip optional end
> tags, converting entities, deprecated tag conversions.  In general,
> implement TIDY features to allow easy debugging of Amaya-generated code.

The future is XHTML and Amaya will be able to generate it in its next release.
With XHTML there is no optional end tags. But I agree Amaya has to offer a set
of options at saving time.

> Configuring
> -----------
> 
> There should be different local hotkey settings under different view
> windows.

What do you mean?

The next release 2.0 will be available soon (normally April 29). I guess it 
should solve
some the problems you mentioned but not all of them.

Regards and thanks for your report
  Irene.

Received on Monday, 19 April 1999 09:52:46 UTC