ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
603
|
Wed Jul 14 22:52:18 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | Possible Formatting bug: Summary view |
I've run into a situation where the SUMMARY view of a logbook will extend
beyond the righthand border, thus requiring the user to scroll right. This
does not occur in FULL or THREAD mode. Long lines in the TEXT attribute
appear to be "pushing" the display too far to the right. Limiting the
number of displayed summary lines works unless the first line is too long.
A temporary fix for this is to set summary lines = 0 |
604
|
Wed Jul 14 22:54:43 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | Re: Wishlist: TOOLTIP for ATTRIBUTES |
> > Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> > is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
>
> Where should the tooltip appear? In the entry form or when an entry is
> displayed, or even in the tabular listing? I can put a title arround the
> attribut names such as
>
> <div title="Please enter some subject here">Subject:</div>
>
> which gets interpreted by most browsers as a tooltip. However it's not
> apparent to the user that leaving the cursor on top of "Subject" opens a
> tooltip, especially since the cursor is displayed as the text cursor (vertical
> bar), not as an arrow over the attribute. Do you have a link to a public web
> page which uses tooltips?
>
> > For a complex entry form it is desireable to try and have everything in a
> > single window and this, I think, would help.
>
> Aiming for running elog on you PDA? Let me know if you succeed...
In the Entry form I am thinking, as this is when most people need some help.
Perhaps the user could be clued in with a "Mouse-over each attribute for Help"
COMMENT at the top.
As for the PDA, no, it's just that some people around here get confused if they
have to scroll down. Not a big thing . . . ;-> Hmmm, PDA . . . |
605
|
Wed Jul 14 22:59:05 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
> Just have a look at elog:571 which should answer your question. Also look at
> elog:Config+Examples/4 which is the configuration of this Forum (which as you can
> see has all attributes in a single line, even using different fonts).
Ok, I think I see now. I was assuming it applied to the entry form as well.
Thanks! |
610
|
Fri Jul 16 04:36:51 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
> > Ok, I think I see now. I was assuming it applied to the entry form as well.
>
> Well, good idea. I implemented that. Have a look at this forum (just hit reply to this
> entry) and you'll see it. I'm not completely happy with it (at least on small 1024x768
> screens), but it's configurable anyhow. New version under CVS.
Now that creates an interesting display - especially with the icons and radio buttons.
But it works!
Thanks. |
611
|
Fri Jul 16 04:37:47 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | Re: Possible Formatting bug: Summary view |
> > A temporary fix for this is to set summary lines = 0
>
> Right, that's the only way. I would call this "permanent fix" (;-)
I would too - and it actually produces the output that I wanted to see anyway.
Thanks! |
613
|
Fri Jul 16 16:53:01 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | Date format problem in "Thread display = " |
I have an attributes defined as:
- Attributes = Author, PlannedDate, FunctionalArea, Operation, Category,
HardwareName, Significance, EmailNotify, LastRevision, Subject
I have PlannedDate defined as:
- Type PlannedDate = date
When I use the following statement:
- Thread display = $subject, planned for $PlannedDate. Last revised:
$lastrevision
I get the following in my THREADED logbook view:
"Adding new services, planned for 1090519200. Last revised: Thu Jul 15
18:03:52 2004"
Note that the ATTRIBUTE $PlannedDate prints as a (I am guessing) serialized
date and is not formatted.
I'm not sure if this is manifested elsewhere. |
614
|
Fri Jul 16 17:51:52 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | WISHLIST: Type <attribute> = user |
Something to add to the wishlist:
- Type <attribute> = user
This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line.
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames. |
615
|
Fri Jul 16 19:06:35 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | BUG?: Preset text = causes replication of text when re-editing a logbook entry. |
With the "Preset text = " specified, when re-editing a logbook entry (say to
correct a spelling error) the text of the "Message" is replicated and placed
directly below the original text.
Commenting out the "Preset text = " line prevents this behavior. this
occurs under both FireFox and IE6.0 clients. |