Uniquely identifying a news item

Hi all,
I'm currently working on refining the RSS support in SC. One
issue
I've spotted is that the messages announcing new items are a
bit
bulky. After some discussions with Vincent we come up with
the
following solution: by default show a very brief title that
links to
the original page. If the user doesn't want to open a
separate browser
window, (s)he then types something like "update X"
(where X is a
unique identifier for the news in the feed) and the full
body (or at
least what is contained in the feed) is displayed, nicely
formatted.

One problem I see here and that I could get some help on (or
ideas),
is how to devise this unique identifier in order for it to
be friendly
for the user (no one would like to type a GUID just to see a
news body
in SC, although that's quite good for generating unique
identifiers).

So, any ideas are more than welcome.

TIA,
Mihai

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Mihai,

I confess that I never used RSS in SC and I don't know
exactly how you 
are handling it but I think that normal users (I mean not
geeks) are 
really repulsed by the idea of using anything which looks
like a 
terminal. Typing something is surely something really easy
to handle for 
you I think, but isn't it possible to put a button or a link
or 
something really more user friendly ? (this will also solve
your problem 
in the same time  )

Cheers,
Ben

Mihai Balan a écrit :
> Hi all,
> I'm currently working on refining the RSS support in
SC. One issue
> I've spotted is that the messages announcing new items
are a bit
> bulky. After some discussions with Vincent we come up
with the
> following solution: by default show a very brief title
that links to
> the original page. If the user doesn't want to open a
separate browser
> window, (s)he then types something like "update
X" (where X is a
> unique identifier for the news in the feed) and the
full body (or at
> least what is contained in the feed) is displayed,
nicely formatted.
>
> One problem I see here and that I could get some help
on (or ideas),
> is how to devise this unique identifier in order for it
to be friendly
> for the user (no one would like to type a GUID just to
see a news body
> in SC, although that's quite good for generating unique
identifiers).
>
> So, any ideas are more than welcome.
>
> TIA,
> Mihai
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Benoit,

Thanks for your good advice 
Effectively, it will be great to receives news with
something like this:

<a href="http://the_news
_page.com">The title of the news</a>
<sc_specific_tag>More info</sc_specific_tag>

Then, the user will just have to:
1) - click on the title to open the news into a browser.
2) - click on "More info" to get the abstract of
the news in the current 
SC dialog box.

The last question is:
- What tag can we use to get the action number 2) working
without 
changing the default behavior (or creating a new action
useful for all 
protocols) of the SC dialog box.

Cheers,
Vincent

Benoit Pradelle wrote:
> Hi Mihai,
>
> I confess that I never used RSS in SC and I don't know
exactly how you 
> are handling it but I think that normal users (I mean
not geeks) are 
> really repulsed by the idea of using anything which
looks like a 
> terminal. Typing something is surely something really
easy to handle 
> for you I think, but isn't it possible to put a button
or a link or 
> something really more user friendly ? (this will also
solve your 
> problem in the same time  )
>
> Cheers,
> Ben
>
> Mihai Balan a écrit :
>> Hi all,
>> I'm currently working on refining the RSS support
in SC. One issue
>> I've spotted is that the messages announcing new
items are a bit
>> bulky. After some discussions with Vincent we come
up with the
>> following solution: by default show a very brief
title that links to
>> the original page. If the user doesn't want to open
a separate browser
>> window, (s)he then types something like
"update X" (where X is a
>> unique identifier for the news in the feed) and the
full body (or at
>> least what is contained in the feed) is displayed,
nicely formatted.
>>
>> One problem I see here and that I could get some
help on (or ideas),
>> is how to devise this unique identifier in order
for it to be friendly
>> for the user (no one would like to type a GUID just
to see a news body
>> in SC, although that's quite good for generating
unique identifiers).
>>
>> So, any ideas are more than welcome.
>>
>> TIA,
>> Mihai
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

I don't know exactly how the main chat window deals with
*ALL* HTML
tags, but I would think of a little hack, that would include
using a
<form>, a <input type="button"> and
something else. But then again, I
think I'm overestimating the HTML rendering capabilities
included in
SC 

Cheers,
Mihai

On 7/8/07, Vincent Lucas <lucasclarinet.u-strasbg.fr>
wrote:
> Hi Benoit,
>
> Thanks for your good advice 
> Effectively, it will be great to receives news with
something like this:
>
> <a href="http://the_news
_page.com">The title of the news</a>
> <sc_specific_tag>More
info</sc_specific_tag>
>
> Then, the user will just have to:
> 1) - click on the title to open the news into a
browser.
> 2) - click on "More info" to get the abstract
of the news in the current
> SC dialog box.
>
> The last question is:
> - What tag can we use to get the action number 2)
working without
> changing the default behavior (or creating a new action
useful for all
> protocols) of the SC dialog box.
>
> Cheers,
> Vincent
>
> Benoit Pradelle wrote:
> > Hi Mihai,
> >
> > I confess that I never used RSS in SC and I don't
know exactly how you
> > are handling it but I think that normal users (I
mean not geeks) are
> > really repulsed by the idea of using anything
which looks like a
> > terminal. Typing something is surely something
really easy to handle
> > for you I think, but isn't it possible to put a
button or a link or
> > something really more user friendly ? (this will
also solve your
> > problem in the same time  )
> >
> > Cheers,
> > Ben
> >
> > Mihai Balan a écrit :
> >> Hi all,
> >> I'm currently working on refining the RSS
support in SC. One issue
> >> I've spotted is that the messages announcing
new items are a bit
> >> bulky. After some discussions with Vincent we
come up with the
> >> following solution: by default show a very
brief title that links to
> >> the original page. If the user doesn't want to
open a separate browser
> >> window, (s)he then types something like
"update X" (where X is a
> >> unique identifier for the news in the feed)
and the full body (or at
> >> least what is contained in the feed) is
displayed, nicely formatted.
> >>
> >> One problem I see here and that I could get
some help on (or ideas),
> >> is how to devise this unique identifier in
order for it to be friendly
> >> for the user (no one would like to type a GUID
just to see a news body
> >> in SC, although that's quite good for
generating unique identifiers).
> >>
> >> So, any ideas are more than welcome.
> >>
> >> TIA,
> >> Mihai
> >>
> >>
------------------------------------------------------------
---------
> >> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> >> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> >>
> >>
> >
> >
------------------------------------------------------------
---------
> > To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> > For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> >
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

So, the good news is that the chat window HTML panel knows
how to
handle <form> and <input> tags, so I managed to
display a pushable
button. The bad news is that, unsurprisingly it does not
support
JavaScript (I was initially thinking about making the news
body
visible on demand, upon a button press using Javascript).

So, if anyone could give me a hint on how HTML forms event
are handled
in SC (if they are) it would be of great help 

Thanks in advance,
Mihai

On 7/8/07, Mihai Balan <mihai.balangmail.com> wrote:
> I don't know exactly how the main chat window deals
with *ALL* HTML
> tags, but I would think of a little hack, that would
include using a
> <form>, a <input type="button">
and something else. But then again, I
> think I'm overestimating the HTML rendering
capabilities included in
> SC 
>
> Cheers,
> Mihai
>
> On 7/8/07, Vincent Lucas <lucasclarinet.u-strasbg.fr> wrote:
> > Hi Benoit,
> >
> > Thanks for your good advice 
> > Effectively, it will be great to receives news
with something like this:
> >
> > <a href="http://the_news
_page.com">The title of the news</a>
> > <sc_specific_tag>More
info</sc_specific_tag>
> >
> > Then, the user will just have to:
> > 1) - click on the title to open the news into a
browser.
> > 2) - click on "More info" to get the
abstract of the news in the current
> > SC dialog box.
> >
> > The last question is:
> > - What tag can we use to get the action number 2)
working without
> > changing the default behavior (or creating a new
action useful for all
> > protocols) of the SC dialog box.
> >
> > Cheers,
> > Vincent
> >
> > Benoit Pradelle wrote:
> > > Hi Mihai,
> > >
> > > I confess that I never used RSS in SC and I
don't know exactly how you
> > > are handling it but I think that normal users
(I mean not geeks) are
> > > really repulsed by the idea of using anything
which looks like a
> > > terminal. Typing something is surely
something really easy to handle
> > > for you I think, but isn't it possible to put
a button or a link or
> > > something really more user friendly ? (this
will also solve your
> > > problem in the same time  )
> > >
> > > Cheers,
> > > Ben
> > >
> > > Mihai Balan a écrit :
> > >> Hi all,
> > >> I'm currently working on refining the RSS
support in SC. One issue
> > >> I've spotted is that the messages
announcing new items are a bit
> > >> bulky. After some discussions with
Vincent we come up with the
> > >> following solution: by default show a
very brief title that links to
> > >> the original page. If the user doesn't
want to open a separate browser
> > >> window, (s)he then types something like
"update X" (where X is a
> > >> unique identifier for the news in the
feed) and the full body (or at
> > >> least what is contained in the feed) is
displayed, nicely formatted.
> > >>
> > >> One problem I see here and that I could
get some help on (or ideas),
> > >> is how to devise this unique identifier
in order for it to be friendly
> > >> for the user (no one would like to type a
GUID just to see a news body
> > >> in SC, although that's quite good for
generating unique identifiers).
> > >>
> > >> So, any ideas are more than welcome.
> > >>
> > >> TIA,
> > >> Mihai
> > >>
> > >>
------------------------------------------------------------
---------
> > >> To unsubscribe, e-mail:
dev-unsubscribesip-communicator.dev.java.net
> > >> For additional commands, e-mail:
dev-helpsip-communicator.dev.java.net
> > >>
> > >>
> > >
> > >
------------------------------------------------------------
---------
> > > To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> > > For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> > >
> >
> >
------------------------------------------------------------
---------
> > To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> > For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> >
> >
>

HELLO EVERYONE,

I MUST SAY THAT I AGREE WITH BEN ON THIS ISSUE. FURTHERMORE,
I THINK THAT 
THERE MIGHT BE SOME PROBLEMS WITH THE INTERNATIONALIZATION
('UPDATE' IS NOT 
THAT USED OUTSIDE THE ENGLISH-SPEAKING COUNTRIES) AND THE
HISTORY (YOU COULD 
OPEN A HISTORY WINDOW AND MAKE 'UPDATE'-S FOR ALL ENTRIES
YOU NEED MORE 
INFORMATION, BUT HONESTLY, IF I HAVE TO DO SOMETHING LIKE
THIS, I WOULD FIND 
MYSELF ANOTHER RSS CLIENT).

IN FACT I'M WONDERING IF YOUR CODE, BEING A PROTOCOL
PROVIDER IMPLEMENTATION, 
SHOULD WORRY AT ALL ON HOW DATA IS DISPLAYED. SURE, IT'S NOT
VERY 
EYE-PLEASING TO SEE TONS OF TEXT SCROLL ON THE SCREEN WITH
NO APPARENT 
STRUCTURE, BUT I THINK THAT THIS PROBLEM SHOULD BE RESOLVED
BY THE GUI.

I'M NOT VERY FAMILIAR WITH HOW THE GUI IS CURRENTLY
RENDERING THE TEXT IN THE 
MESSAGE WINDOW, BUT I THINK THAT IT WOULD BE NICE FOR A
PROTOCOL 
IMPLEMENTATION TO BE ABLE TO SAY "OK, I HAVE A NEW
MESSAGE + SOME ADDITIONAL 
INFORMATION ATTACHED (DESCRIPTION, ETC.)" AND LEAVE THE
GUI DECIDE HOW 
EXACTLY THIS ALL SHOULD BE LAYED OFF (TEXT+ "MORE"
BUTTON, TEXT+TOOLTIP, 
BULKY TEXT, ETC).

ON THE OTHER HAND I'M NOT SURE IF THIS IS NOT GOING TO BE
VERY DIFFICULT, SO 
FOR NOW YOU MAY WANT TO TRY TRIMMING A LITTLE BIT THE
DESCRIPTION (LIKE 
SHOWING JUST THE LINK + 1-2 LINES OF DESCRIPTION + ...).
BEING ABLE TO 
SPECIFY TOOLTIPS OVER THE LINKS MAY ALSO SOLVE THE PROBLEM
(THE TOOLTIP 
CONTAINING SEVERAL LINES OF THE DESCRIPTION).

WHAT DO YOU THINK ON ALL THIS? DO YOU THINK THAT FURTHER
COMPLICATION OF THE 
GUI FOR THE SAKE OF SIMPLIFIED,IMPROVED AND MORE CONSISTENT
PROTOCOL 
IMPLEMENTATION BEHAVIOR IS WORTH IT AT THIS STAGE OF THE
DEVELOPMENT?

REGARDS,
ALEX

ON SUNDAY 08 JULY 2007 14:11:02 BENOIT PRADELLE WROTE:
> HI MIHAI,
>
> I CONFESS THAT I NEVER USED RSS IN SC AND I DON'T KNOW
EXACTLY HOW YOU
> ARE HANDLING IT BUT I THINK THAT NORMAL USERS (I MEAN
NOT GEEKS) ARE
> REALLY REPULSED BY THE IDEA OF USING ANYTHING WHICH
LOOKS LIKE A
> TERMINAL. TYPING SOMETHING IS SURELY SOMETHING REALLY
EASY TO HANDLE FOR
> YOU I THINK, BUT ISN'T IT POSSIBLE TO PUT A BUTTON OR A
LINK OR
> SOMETHING REALLY MORE USER FRIENDLY ? (THIS WILL ALSO
SOLVE YOUR PROBLEM
> IN THE SAME TIME  )
>
> CHEERS,
> BEN
>
> MIHAI BALAN A éCRIT :
> > HI ALL,
> > I'M CURRENTLY WORKING ON REFINING THE RSS SUPPORT
IN SC. ONE ISSUE
> > I'VE SPOTTED IS THAT THE MESSAGES ANNOUNCING NEW
ITEMS ARE A BIT
> > BULKY. AFTER SOME DISCUSSIONS WITH VINCENT WE COME
UP WITH THE
> > FOLLOWING SOLUTION: BY DEFAULT SHOW A VERY BRIEF
TITLE THAT LINKS TO
> > THE ORIGINAL PAGE. IF THE USER DOESN'T WANT TO
OPEN A SEPARATE BROWSER
> > WINDOW, (S)HE THEN TYPES SOMETHING LIKE
"UPDATE X" (WHERE X IS A
> > UNIQUE IDENTIFIER FOR THE NEWS IN THE FEED) AND
THE FULL BODY (OR AT
> > LEAST WHAT IS CONTAINED IN THE FEED) IS DISPLAYED,
NICELY FORMATTED.
> >
> > ONE PROBLEM I SEE HERE AND THAT I COULD GET SOME
HELP ON (OR IDEAS),
> > IS HOW TO DEVISE THIS UNIQUE IDENTIFIER IN ORDER
FOR IT TO BE FRIENDLY
> > FOR THE USER (NO ONE WOULD LIKE TO TYPE A GUID
JUST TO SEE A NEWS BODY
> > IN SC, ALTHOUGH THAT'S QUITE GOOD FOR GENERATING
UNIQUE IDENTIFIERS).
> >
> > SO, ANY IDEAS ARE MORE THAN WELCOME.
> >
> > TIA,
> > MIHAI
> >
> >
------------------------------------------------------------
---------
> > TO UNSUBSCRIBE, E-MAIL: DEV-UNSUBSCRIBESIP-COMMUNICATOR.DEV.JAVA.NET
> > FOR ADDITIONAL COMMANDS, E-MAIL: DEV-HELPSIP-COMMUNICATOR.DEV.JAVA.NET
>
>
------------------------------------------------------------
---------
> TO UNSUBSCRIBE, E-MAIL: DEV-UNSUBSCRIBESIP-COMMUNICATOR.DEV.JAVA.NET
> FOR ADDITIONAL COMMANDS, E-MAIL: DEV-HELPSIP-COMMUNICATOR.DEV.JAVA.NET


------------------------------------------------------------
---------
TO UNSUBSCRIBE, E-MAIL: DEV-UNSUBSCRIBESIP-COMMUNICATOR.DEV.JAVA.NET
FOR ADDITIONAL COMMANDS, E-MAIL: DEV-HELPSIP-COMMUNICATOR.DEV.JAVA.NET

Hi Mihai,

we don't handle HTML form events for now. The only event
that we handle 
is the HyperlinkEvent. I've had a quick tour in some forums
treating the 
subject and I think it could be done without using
JavaScript. You could 
have a look and see if it could be implemented easily using
a 
JEditorPane and HTMLEditorKit (that's what we use to
visualize HTML) and 
if it's not so easy you could use a simple link for now.

Yana

Mihai Balan wrote:
> So, the good news is that the chat window HTML panel
knows how to
> handle <form> and <input> tags, so I
managed to display a pushable
> button. The bad news is that, unsurprisingly it does
not support
> JavaScript (I was initially thinking about making the
news body
> visible on demand, upon a button press using
Javascript).
> 
> So, if anyone could give me a hint on how HTML forms
event are handled
> in SC (if they are) it would be of great help 
> 
> Thanks in advance,
> Mihai
> 
> On 7/8/07, Mihai Balan <mihai.balangmail.com> wrote:
>> I don't know exactly how the main chat window deals
with *ALL* HTML
>> tags, but I would think of a little hack, that
would include using a
>> <form>, a <input
type="button"> and something else. But then
again, I
>> think I'm overestimating the HTML rendering
capabilities included in
>> SC 
>>
>> Cheers,
>> Mihai
>>
>> On 7/8/07, Vincent Lucas <lucasclarinet.u-strasbg.fr> wrote:
>> > Hi Benoit,
>> >
>> > Thanks for your good advice 
>> > Effectively, it will be great to receives news
with something like 
>> this:
>> >
>> > <a href="http://the_news
_page.com">The title of the news</a>
>> > <sc_specific_tag>More
info</sc_specific_tag>
>> >
>> > Then, the user will just have to:
>> > 1) - click on the title to open the news into
a browser.
>> > 2) - click on "More info" to get the
abstract of the news in the 
>> current
>> > SC dialog box.
>> >
>> > The last question is:
>> > - What tag can we use to get the action number
2) working without
>> > changing the default behavior (or creating a
new action useful for all
>> > protocols) of the SC dialog box.
>> >
>> > Cheers,
>> > Vincent
>> >
>> > Benoit Pradelle wrote:
>> > > Hi Mihai,
>> > >
>> > > I confess that I never used RSS in SC and
I don't know exactly how 
>> you
>> > > are handling it but I think that normal
users (I mean not geeks) are
>> > > really repulsed by the idea of using
anything which looks like a
>> > > terminal. Typing something is surely
something really easy to handle
>> > > for you I think, but isn't it possible to
put a button or a link or
>> > > something really more user friendly ?
(this will also solve your
>> > > problem in the same time  )
>> > >
>> > > Cheers,
>> > > Ben
>> > >
>> > > Mihai Balan a écrit :
>> > >> Hi all,
>> > >> I'm currently working on refining the
RSS support in SC. One issue
>> > >> I've spotted is that the messages
announcing new items are a bit
>> > >> bulky. After some discussions with
Vincent we come up with the
>> > >> following solution: by default show a
very brief title that links to
>> > >> the original page. If the user
doesn't want to open a separate 
>> browser
>> > >> window, (s)he then types something
like "update X" (where X is a
>> > >> unique identifier for the news in the
feed) and the full body (or at
>> > >> least what is contained in the feed)
is displayed, nicely formatted.
>> > >>
>> > >> One problem I see here and that I
could get some help on (or ideas),
>> > >> is how to devise this unique
identifier in order for it to be 
>> friendly
>> > >> for the user (no one would like to
type a GUID just to see a news 
>> body
>> > >> in SC, although that's quite good for
generating unique 
>> identifiers).
>> > >>
>> > >> So, any ideas are more than welcome.
>> > >>
>> > >> TIA,
>> > >> Mihai
>> > >>
>> > >> 
>>
------------------------------------------------------------
---------
>> > >> To unsubscribe, e-mail: 
>> dev-unsubscribesip-communicator.dev.java.net
>> > >> For additional commands, e-mail: 
>> dev-helpsip-communicator.dev.java.net
>> > >>
>> > >>
>> > >
>> > >
------------------------------------------------------------
---------
>> > > To unsubscribe, e-mail:
dev-unsubscribesip-communicator.dev.java.net
>> > > For additional commands, e-mail: 
>> dev-helpsip-communicator.dev.java.net
>> > >
>> >
>> >
------------------------------------------------------------
---------
>> > To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> > For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>> >
>> >
>>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hey all,

My personal opinion is that we're complicating things more
than we have
to. I definitely like the idea of not showing the link
itself and
associating it with the title instead.

However, I think that if there is an abstract, we should
simply be
showing it right from the start. We could of course use a
different font
and size so that it won't take much space but still, it
should be
available for the user to read it if they want to.

In the case of sip-communicator, we'd be using RSS as a
notification
mechanism. All that users would need would be a message
telling them
that a new rss item has become available for a particular
flow, and a
quick way for them to determine whether they want to read
the
corresponding article or not. I am afraid that adding an
extra step,
like clicking on a button in order to get the abstract,
would only add
unnecessary complexity to the whole process.

I'd suggest that we first try the following display:

<a href="
http://news.google.com/latest_news.html">SIP
Communicator
becomes the most widely used IM client!</a> - Multiple
agencies are
reporting an unseen uptake in the usage of the SIP
Communicator client
during the last few months ...

If we decide that we want extra features later, we'd have
all the time
to add them, but I don't think that the basic use case
should be any
more complicated than this.

What do you think?

Emil

Yana Stamcheva wrote:
> Hi Mihai,
> 
> we don't handle HTML form events for now. The only
event that we handle 
> is the HyperlinkEvent. I've had a quick tour in some
forums treating the 
> subject and I think it could be done without using
JavaScript. You could 
> have a look and see if it could be implemented easily
using a 
> JEditorPane and HTMLEditorKit (that's what we use to
visualize HTML) and 
> if it's not so easy you could use a simple link for
now.
> 
> Yana
> 
> Mihai Balan wrote:
>> So, the good news is that the chat window HTML
panel knows how to
>> handle <form> and <input> tags, so I
managed to display a pushable
>> button. The bad news is that, unsurprisingly it
does not support
>> JavaScript (I was initially thinking about making
the news body
>> visible on demand, upon a button press using
Javascript).
>>
>> So, if anyone could give me a hint on how HTML
forms event are handled
>> in SC (if they are) it would be of great help 
>>
>> Thanks in advance,
>> Mihai
>>
>> On 7/8/07, Mihai Balan <mihai.balangmail.com> wrote:
>>> I don't know exactly how the main chat window
deals with *ALL* HTML
>>> tags, but I would think of a little hack, that
would include using a
>>> <form>, a <input
type="button"> and something else. But then
again, I
>>> think I'm overestimating the HTML rendering
capabilities included in
>>> SC 
>>>
>>> Cheers,
>>> Mihai
>>>
>>> On 7/8/07, Vincent Lucas <lucasclarinet.u-strasbg.fr> wrote:
>>>> Hi Benoit,
>>>>
>>>> Thanks for your good advice 
>>>> Effectively, it will be great to receives
news with something like 
>>> this:
>>>> <a href="http://the_news
_page.com">The title of the news</a>
>>>> <sc_specific_tag>More
info</sc_specific_tag>
>>>>
>>>> Then, the user will just have to:
>>>> 1) - click on the title to open the news
into a browser.
>>>> 2) - click on "More info" to get
the abstract of the news in the 
>>> current
>>>> SC dialog box.
>>>>
>>>> The last question is:
>>>> - What tag can we use to get the action
number 2) working without
>>>> changing the default behavior (or creating
a new action useful for all
>>>> protocols) of the SC dialog box.
>>>>
>>>> Cheers,
>>>> Vincent
>>>>
>>>> Benoit Pradelle wrote:
>>>>> Hi Mihai,
>>>>>
>>>>> I confess that I never used RSS in SC
and I don't know exactly how 
>>> you
>>>>> are handling it but I think that normal
users (I mean not geeks) are
>>>>> really repulsed by the idea of using
anything which looks like a
>>>>> terminal. Typing something is surely
something really easy to handle
>>>>> for you I think, but isn't it possible
to put a button or a link or
>>>>> something really more user friendly ?
(this will also solve your
>>>>> problem in the same time  )
>>>>>
>>>>> Cheers,
>>>>> Ben
>>>>>
>>>>> Mihai Balan a écrit :
>>>>>> Hi all,
>>>>>> I'm currently working on refining
the RSS support in SC. One issue
>>>>>> I've spotted is that the messages
announcing new items are a bit
>>>>>> bulky. After some discussions with
Vincent we come up with the
>>>>>> following solution: by default show
a very brief title that links to
>>>>>> the original page. If the user
doesn't want to open a separate 
>>> browser
>>>>>> window, (s)he then types something
like "update X" (where X is a
>>>>>> unique identifier for the news in
the feed) and the full body (or at
>>>>>> least what is contained in the
feed) is displayed, nicely formatted.
>>>>>>
>>>>>> One problem I see here and that I
could get some help on (or ideas),
>>>>>> is how to devise this unique
identifier in order for it to be 
>>> friendly
>>>>>> for the user (no one would like to
type a GUID just to see a news 
>>> body
>>>>>> in SC, although that's quite good
for generating unique 
>>> identifiers).
>>>>>> So, any ideas are more than
welcome.
>>>>>>
>>>>>> TIA,
>>>>>> Mihai
>>>>>>
>>>>>>
>>>
------------------------------------------------------------
---------
>>>>>> To unsubscribe, e-mail: 
>>> dev-unsubscribesip-communicator.dev.java.net
>>>>>> For additional commands, e-mail: 
>>> dev-helpsip-communicator.dev.java.net
>>>>>>
>>>>>
------------------------------------------------------------
---------
>>>>> To unsubscribe, e-mail:
dev-unsubscribesip-communicator.dev.java.net
>>>>> For additional commands, e-mail: 
>>> dev-helpsip-communicator.dev.java.net
>>>>
------------------------------------------------------------
---------
>>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>>> For additional commands, e-mail:
dev-helpsip-communicator.dev.java.net
>>>>
>>>>
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Emil,

> My personal opinion is that we're complicating things
more than we have
> to. I definitely like the idea of not showing the link
itself and
> associating it with the title instead.
>
> However, I think that if there is an abstract, we
should simply be
> showing it right from the start. We could of course use
a different font
> and size so that it won't take much space but still, it
should be
> available for the user to read it if they want to.

As a matter of fact that's what I've been thinking about
that for a
couple of days. Offering a notification and a little
description
should be more than enough, as there are very few feeds that
offer the
full story in the feed.

> In the case of sip-communicator, we'd be using RSS as a
notification
> mechanism. All that users would need would be a message
telling them
> that a new rss item has become available for a
particular flow, and a
> quick way for them to determine whether they want to
read the
> corresponding article or not. I am afraid that adding
an extra step,
> like clicking on a button in order to get the abstract,
would only add
> unnecessary complexity to the whole process.

Totally agree 

> I'd suggest that we first try the following display:
>
> <a href="
http://news.google.com/latest_news.html">SIP
Communicator
> becomes the most widely used IM client!</a> -
Multiple agencies are
> reporting an unseen uptake in the usage of the SIP
Communicator client
> during the last few months ...

I'm working on this exact approach but for reasons totally
unknown to
me, the output in the chat window is totally messed up,
although the
Message is properly constructed (as I can see on the console
output).
For instance, for the following HTML:

<i>At Mon Jul 09 13:28:03 EEST
2007</i><br>Sony cuts price of
 PS3 on eve of E3 - San Francisco Chronicle <a
href="http://news.google.com/ne
ws
/url?sa=T&ct=us/4-0-0&fd=R&url=htt
p://www.sfgate.com/cgi-bin/article.cgi%3Ff%3D/
c/a/2007/07/09/BUGPUQSED41.DTL&cid=1117989844&ei=0xm
SRt7pLIKy0QHNy6yjDA">
Link</a><br>

I get something like:

At Mon Jul 09 13:28:03 EEST 2007 Sony cuts price of PS3 on
eve of E3 -
San Francisco Chronicle
news.google.com/news/url?sa=T&ct=us/4-0-0&fd=R&u
rl=http://www.sfgate.com/cgi-bin/
article.cgi%3Ff%3D/c/a/2007/07/09/BUGPUQSED41.DTL&cid=11
17989844&ei=HBuSRsv2EIiy0AGTl4mjDA">Link
At">http://news.google.c
om/news/url?sa=T&ct=us/4-0-0&fd=R&url=http://www
.sfgate.com/cgi-bin/article.cgi%3Ff%3D/c/a/2007/07/09/BUGPUQ
SED41.DTL&cid=1117989844&ei=HBuSRsv2EIiy0AGTl4mjDA&q
uot;>Link

that is all in italics and on a Orange background :(
Am I missing something? I set the content-type to
"text/html". Is
there anything else that I'm missing?

> If we decide that we want extra features later, we'd
have all the time
> to add them, but I don't think that the basic use case
should be any
> more complicated than this.
>
> What do you think?
It's OK 
> Emil

Thanks in advance,
Mihai

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net