[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [corona-dev] Shared Bug View
|
I was thinking of something similar some time ago. My "code name" for
this was "shared bookmarks".
Marcin
Everitt, Glenn wrote:
I think the next logical step would be to allow a Team Members to
create Shared Resource Lists. The Shared Resource List would contain
the Resource URI and the Resource Type URI.
We need to create a registry to map Resource Types to Resource
Editors. We could then use the Resource Type URI in the Shared
Resource List launch the correct Resource Editor and specify the
Resource URI from the Shared Resource List.
I think we could then share lists of any resources with an available
resource editor…
------------------------------------------------------------------------
*From:* corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Everitt, Glenn
*Sent:* Friday, April 20, 2007 12:46 PM
*To:* Corona development
*Subject:* RE: [corona-dev] Shared Bug View
Why don’t we enter it as an enhancement bug and leave it until later.
Do want to enter it or should I?
Glenn
------------------------------------------------------------------------
*From:* corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Wright, Jim
*Sent:* Friday, April 20, 2007 12:43 PM
*To:* Corona development
*Subject:* RE: [corona-dev] Shared Bug View
It would be better if the bug could be clicked on from the chat text,
and a browse window shows up with the bug.
While the chat display window is not a browser window. I think the
code does support the linking from chat text.
I will look at this
I will also look at making the chat window a browser window
JimW
------------------------------------------------------------------------
*From:* corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Everitt, Glenn
*Sent:* Friday, April 20, 2007 12:38 PM
*To:* Corona development
*Subject:* [corona-dev] Shared Bug View
As we were using Chat in Corona today, people were referencing bugs in
bugzilla that I had to keep looking up. I was just thinking it would
be great if Corona supported a shared bug view. The idea is something
like:
Each person in Team in a Context can create list of bugs they want to
talk about because they are fixed or have a problem
During Chat when a person decides it is time to discuss their bug
list, he then clicks on the Share Bug List button. (I don’t know where
this button goes.)
All active participants in the chat room have their Bugzilla View
updated with the Shared Bug List.
Then it is easy to tab between chat and the bug view.
Just an idea. - Glenn Everitt
You can enter a comma separated list of bug numbers in Actions text
entry box and click find to get a specific list:
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
------------------------------------------------------------------------
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
