| A web interface is also needed [message #3064] |
Sun, 09 March 2008 13:52  |
|
[Jochen Krause said]
Does everybody that wants to specify requirements need an Eclipse
installation? If yes, I think that this is highly problematic.
[Harm Sluiman said]
An Eclipse or RCP based client is a great start, but a browser client
is equally if not more valuable long term. I hate to say Web 2.0 and
Ajax but you know what I mean.
[Michael Fox said]
I believe you'll need a web client, as well as an Eclipse based client
for this to be really useful. Many people who would use it are not
"Eclipse knowledgeable", and even providing an RCP version could be
hard to use. From my experience, most non-programmers these days want
web based tools. They are simpler to use and require no local install.
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: A web interface is also needed [message #4054 is a reply to message #3064] |
Sun, 09 March 2008 14:08  |
|
On 2008-03-09 13:52:17 +0000, Joel Rosi-Schwartz
<Joel.Rosi-Schwartz@Etish.org> said:
> [Jochen Krause said]
> Does everybody that wants to specify requirements need an Eclipse
> installation? If yes, I think that this is highly problematic.
>
> [Harm Sluiman said]
> An Eclipse or RCP based client is a great start, but a browser client
> is equally if not more valuable long term. I hate to say Web 2.0 and
> Ajax but you know what I mean.
>
> [Michael Fox said]
> I believe you'll need a web client, as well as an Eclipse based client
> for this to be really useful. Many people who would use it are not
> "Eclipse knowledgeable", and even providing an RCP version could be
> hard to use. From my experience, most non-programmers these days want
> web based tools. They are simpler to use and require no local install.
We agree with these comments but we also have considerations. As we see
it, ORMF and tools that are built on top of it have a complex job to
perform. The goal is to massage the complexity away so that the users
can concentrate on the requirements. If in the process we trivialise
the problem to force it to fit into the web paradigm then we do not
believe that we have succeeded in solving the problem at hand.
That said we do appreciate that the potential audience is considerably
broadened by offering a web interface. We have already, in fact,
explored the utilisation of RAP for this purpose, but we hit a show
stopper early on when learned that Styled Text is not supported. Since
the current GUI uses Styled Text to back the support for essential
features, it would require a major rethink to use RAP. Possibly this
RAP will remove that deficiency or perhaps we can find a way to live
with it.
One of our goals at EclipseCon it pursue this issue by learning more
about RAP and speaking with the RAP team about how to work around our
problem.
B. and Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: A web interface is also needed [message #561525 is a reply to message #3064] |
Sun, 09 March 2008 14:08 |
|
On 2008-03-09 13:52:17 +0000, Joel Rosi-Schwartz
<Joel.Rosi-Schwartz@Etish.org> said:
> [Jochen Krause said]
> Does everybody that wants to specify requirements need an Eclipse
> installation? If yes, I think that this is highly problematic.
>
> [Harm Sluiman said]
> An Eclipse or RCP based client is a great start, but a browser client
> is equally if not more valuable long term. I hate to say Web 2.0 and
> Ajax but you know what I mean.
>
> [Michael Fox said]
> I believe you'll need a web client, as well as an Eclipse based client
> for this to be really useful. Many people who would use it are not
> "Eclipse knowledgeable", and even providing an RCP version could be
> hard to use. From my experience, most non-programmers these days want
> web based tools. They are simpler to use and require no local install.
We agree with these comments but we also have considerations. As we see
it, ORMF and tools that are built on top of it have a complex job to
perform. The goal is to massage the complexity away so that the users
can concentrate on the requirements. If in the process we trivialise
the problem to force it to fit into the web paradigm then we do not
believe that we have succeeded in solving the problem at hand.
That said we do appreciate that the potential audience is considerably
broadened by offering a web interface. We have already, in fact,
explored the utilisation of RAP for this purpose, but we hit a show
stopper early on when learned that Styled Text is not supported. Since
the current GUI uses Styled Text to back the support for essential
features, it would require a major rethink to use RAP. Possibly this
RAP will remove that deficiency or perhaps we can find a way to live
with it.
One of our goals at EclipseCon it pursue this issue by learning more
about RAP and speaking with the RAP team about how to work around our
problem.
B. and Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
Powered by
FUDForum. Page generated in 0.03233 seconds
] 
Search
Help
Register
Login
Home
