Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of yojibee@gmail.com designates
 209.85.219.213 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=KfIhzuT/ZWiD5nnPMeP1QoU0vu+kI6wtMJlgCtlfWkTCxqVNNDIJtpY4DkryjNae/n
         8fh2U1yegxsizJ8VNElzGIlJXbLjyuWGkt6TV+lOFE64zxj4e/INlNqabRc9lwue/1yU
         ecQd1wxnAbUiPaLmvUAsL719MKuiewRPzoCEM=
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: Text wrapping in timeline and popular message/links (ESME-112 and
 ESME-186)
From: =?iso-8859-1?Q?Anne_Kathrine_Petter=F8e?= <yojibee@gmail.com>
In-Reply-To: <x2sfa2d9f451004022333l5936ce92yffde42a62591f21d@mail.gmail.com>
Date: Sat, 3 Apr 2010 09:54:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA5170B3-B141-4C46-A2E4-2609912C72EF@gmail.com>
References: <t2r68f4a0e81004011600qdff984e5v45955ba7aa062d25@mail.gmail.com>
 <t2gfa2d9f451004012327j63673595h5cc0ffe65b784de9@mail.gmail.com>
 <FA86CC26-B9C8-4227-AC1B-204FF50331F9@gmail.com>
 <x2sfa2d9f451004022333l5936ce92yffde42a62591f21d@mail.gmail.com>
To: esme-dev@incubator.apache.org

It works on the perf stax instance.
Which revision is deployed there?

On 3. apr. 2010, at 08.33, Richard Hirsch wrote:

> Have you tried it on perf stax instance?
>=20
> On Fri, Apr 2, 2010 at 5:25 PM, Anne Kathrine Petter=F8e =
<yojibee@gmail.com>wrote:
>=20
>> I wanted to test in IE7, but I cannot sign up for a new account on my
>> machine (localhost:8080).
>> Is the signup page broken or is it only me?
>>=20
>> /Anne
>>=20
>>=20
>> On 2. apr. 2010, at 08.27, Richard Hirsch wrote:
>>=20
>>> Thanks for the UI-related work. It is great that others are doing UI =
work
>> as
>>> well.
>>>=20
>>> Unfortunately, I'm on vacation and can't do a stax deployment until
>> Tuesday.
>>> :-<
>>>=20
>>> D.
>>>=20
>>> On Fri, Apr 2, 2010 at 1:00 AM, Ethan Jewett <esjewett@gmail.com> =
wrote:
>>>=20
>>>> I just checked in word-wrap based fixes for both the timeline and =
the
>>>> popular messages/links. Word on the street is that this actually
>>>> should work in IE as well. Can someone build trunk and test, at =
least
>>>> on IE7? Any really long link with only normal characters in it (not =
-)
>>>> should trigger the issue.
>>>>=20
>>>> Thanks,
>>>> Ethan
>>>>=20
>>>> On Mon, Mar 29, 2010 at 12:09 AM, Anne Kathrine Petter=F8e
>>>> <yojibee@gmail.com> wrote:
>>>>> OK, so we need to find a way to deal with text wrapping.
>>>>> We should probably decide which browsers to support in release 1.1 =
and
>>>> take it from there.
>>>>>=20
>>>>>=20
>>>>> On 28. mars 2010, at 19.22, Ethan Jewett wrote:
>>>>>=20
>>>>>> Yup, understood re. big companies still using IE6. I was just
>>>>>> wondering if any of our specific users (Siemens, at least) still
>>>>>> consider it supported internally. If not, then it might make =
sense to
>>>>>> consider not supporting it if it is a lot of extra work.
>>>>>>=20
>>>>>> On the messages front, it's just messages with long links, or =
other
>>>>>> long unbroken text strings that suffer the wrapping problem.
>>>>>>=20
>>>>>> Ethan
>>>>>>=20
>>>>>> On Sun, Mar 28, 2010 at 8:35 AM, Anne Kathrine Petter=F8e
>>>>>> <yojibee@gmail.com> wrote:
>>>>>>> Is the wrapping problem for messages for all messages or just =
those
>>>> containing long links?
>>>>>>>=20
>>>>>>> The problem is that many big companies still use IE6 and won't =
care
>>>> about end-of-life dates.
>>>>>>> @Dick: IE6 support is still important for Siemens right?
>>>>>>>=20
>>>>>>>=20
>>>>>>> On 28. mars 2010, at 16.28, Ethan Jewett wrote:
>>>>>>>=20
>>>>>>>> Sounds like a good approach to me, but keep in mind that we =
still
>> have
>>>>>>>> the wrapping problem for messages themselves.
>>>>>>>>=20
>>>>>>>> What is the situation with IE6 support at places that have this
>>>>>>>> deployed currently? I'm thinking since IE6 and most IE7 =
versions
>>>>>>>> end-of-life is July 13th, those working on the UI might not =
want to
>>>>>>>> put too much effort into it.
>>>>>>>>=20
>>>>>>>> Ethan
>>>>>>>>=20
>>>>>>>> On Sun, Mar 28, 2010 at 4:52 AM, Anne Kathrine Petter=F8e
>>>>>>>> <yojibee@gmail.com> wrote:
>>>>>>>>> I am just afraid that text wrapping is something which will =
take a
>>>> significant amount of time to get right.
>>>>>>>>> Remember we have support the following browsers:
>>>>>>>>> IE6
>>>>>>>>> IE7
>>>>>>>>> IE8
>>>>>>>>> Safari
>>>>>>>>> Firefox
>>>>>>>>>=20
>>>>>>>>> I think we should put it in the backlog for now and remove =
these
>>>> features from the UI for the 1.1 release.
>>>>>>>>> What say you?
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> On 27. mars 2010, at 15.42, Ethan Jewett wrote:
>>>>>>>>>=20
>>>>>>>>>> Whoops! I just created ESME-186 and attached it there:
>>>>>>>>>> https://issues.apache.org/jira/browse/ESME-186
>>>>>>>>>>=20
>>>>>>>>>> Ethan
>>>>>>>>>>=20
>>>>>>>>>> On Sat, Mar 27, 2010 at 8:32 AM, Richard Hirsch <
>>>> hirsch.dick@gmail.com> wrote:
>>>>>>>>>>> On Sat, Mar 27, 2010 at 3:20 PM, Ethan Jewett <
>> esjewett@gmail.com>
>>>> wrote:
>>>>>>>>>>>=20
>>>>>>>>>>>> On Sat, Mar 27, 2010 at 4:58 AM, Richard Hirsch <
>>>> hirsch.dick@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> What I'd like to do is use JQuery tool tips to display the
>> help.
>>>> I just
>>>>>>>>>>>>> finished converting the action page and just deleted the =
help.
>>>>>>>>>>>>=20
>>>>>>>>>>>> That sounds just about perfect!
>>>>>>>>>>>>=20
>>>>>>>>>>>>> Good luck.  Do you have suggestion of how to display a =
long
>> url?
>>>> Maybe
>>>>>>>>>>>> with
>>>>>>>>>>>>> a mouse-over that displays the fulltext.
>>>>>>>>>>>>=20
>>>>>>>>>>>> I think for starters we could drop the # of clicks and get =
away
>>>> from a
>>>>>>>>>>>> table-based model to a list-based model in the html. That =
helps
>>>>>>>>>>>> compact things a bit and gives us more ability to use CSS =
for
>>>> managing
>>>>>>>>>>>> text display. The next step is to force wrapping, which to =
the
>>>> best of
>>>>>>>>>>>> my knowledge is not really possible in CSS2. Fortunately =
CSS3
>> has
>>>> the
>>>>>>>>>>>> "word-wrap:break-word" style, which does exactly what we =
want.
>>>>>>>>>>>>=20
>>>>>>>>>>>> I've attached a mock-up done using CSS3 using this =
approach.
>> What
>>>> do you
>>>>>>>>>>>> think?
>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>> Email it to me directly, since the esme-dev mailing deamon
>> usually
>>>> kills
>>>>>>>>>>> attachments.
>>>>>>>>>>> Or attach it to JIRA-100 item.
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>> As a last resort, if we can't find a way to extend this to
>>>> non-CSS3
>>>>>>>>>>>> browsers, we could probably do some fancy JS or something =
to
>>>> insert
>>>>>>>>>>>> spaces into the text representation of the link, allowing =
it to
>>>> wrap.
>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> What about creating dialogs but not modal dialogs.
>>>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>> I think modal dialogs and normal dialogs suffer from the =
same
>>>>>>>>>>>> disadvantages in this situation.
>>>>>>>>>>>>=20
>>>>>>>>>>>> Ethan
>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>=20
>>=20