[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aperi-dev] V0.3 SWT Browser Widget on Linux Client Go/NoGo Decision
|
> I'm wondering if we have gotten any advice
or input from the Eclispe SWT project on the likelihood of fixing this
issue in a few days.
No. I want to verify we have a supported recipe, then
go for help.
> We think this is a bug in their code or an issue
with how we exploited their code?
I think we aren't sure (that's the real problem), I am
setting up a new Linux box with RedHat Enterprise Linux 3 AS which is listed
as one of the 'for sure' configurations.
> Do we actually have to remove code or do we put
this down as a known restriction for now?
We would replace the integrated browser window with a
browser launch. You would still select a menu item from the RCP GUI that
says 'View Reports', but instead of opening a panel within the GUI framework
it would launch an external browser with the right URL.
> I think you are suggesting we actually end up
continuing the work on r0.3 to sort this out but call r0.3 done with this
function removed?
Yes. One of the things other Eclipse
projects do is create 'Milestone Releases' which provide access to new
functionality while the rest of the release is developed. Thus, we could
have some milestones in V0.4 for adding in some additional report viewer
capabilities such as the SWT Browser (if we drop it), and the JNDI data
source (which is too risky to add this late in V0.3).
> I'd also comment that I think some of the vendors
participanting in Aperi are very interested in the idea of being able to
have a seamless interface that includes web based interface and a rich
client interface.
I agree. GUI integration is a cornerstone of our strategy and a major theme
for V0.3.
Dave Wolfe/Portland/IBM
(dwolfe@xxxxxxxxxx)
TL: 775-3376 Office: 503-578-3376 Personal: 503-329-3960
UI Technical Lead, Aperi Open Source Storage Management
http://www.eclipse.org/aperi
"A good composer does not imitate; he
steals." - Igor Stravinsky
Brenda Haynes/Raleigh/IBM@ibmus
Sent by: aperi-dev-bounces@xxxxxxxxxxx
04/25/2007 06:22 AM
|
Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx> |
|
|
To
| Aperi Development <aperi-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| Re: [aperi-dev] V0.3 SWT Browser Widget
on Linux Client Go/NoGo Decision |
|
Dave, thanks for clarifying the situation with the SWT
Browser widget. I'm wondering if we have gotten any advice or input from
the Eclispe SWT project on the likelihood of fixing this issue in a few
days. We think this is a bug in their code or an issue with how we exploited
their code?
Also a question on the NoGo recommendation: Do we actually have to remove
code or do we put this down as a known restriction for now? I think you
are suggesting we actually end up continuing the work on r0.3 to sort this
out but call r0.3 done with this function removed?
I'd also comment that I think some of the vendors participanting in Aperi
are very interested in the idea of being able to have a seamless interface
that includes web based interface and a rich client interface.
I'd personally probably tend toward trying to spend a few more days seeing
if we can sort this out. Open to other opinions and ideas.
Thanks Brenda
Brenda Haynes
Director, Aperi Open Source Project
zStorage SW Product Management
IBM Software Group
bhaynes@xxxxxxxxxx
877-328-8470 T/L (930)-5127_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev
