[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aperi-dev] V0.3 GUI install
|
Unless I misread the intent of q1, I dont think anyone is opposing a
separate install for the GUI on a different machine. I thought it referred
to a completely separate download + installation method independent of
cfgAperi. Moreover, I dont think TPC has a separate download + separate
installer for the GUI - its an option to the main installer, something we
could reasonably achieve with a yes to q2.
Prasenjit Sarkar
Almaden Research
Sumant
Padbidri/San
Jose/IBM@IBMUS To
Sent by: Aperi Development
aperi-dev-bounces <aperi-dev@xxxxxxxxxxx>
@eclipse.org cc
Subject
01/31/2007 03:52 Re: [aperi-dev] V0.3 GUI install
PM
Please respond
to
Development
<aperi-dev@eclips
e.org>
Khan explained to me what the "legacy GUI' meant. I'm changing my vote for
#3 to "yes". So my votes match Khan's.
- Sumant
Khan M Tasinga/San Jose/IBM@IBMUS
Sent by: To
aperi-dev-bounces@xxxxxxxxxxx Aperi Development
<aperi-dev@xxxxxxxxxxx>
cc
01/31/2007 02:55 PM
Subject
Re: [aperi-dev] V0.3 GUI
Please respond to
Development
<aperi-dev@xxxxxxxxxxx>
1. Yes. As Sumant pointed out, people may want to use the GUI independently
of the server. For example, a storage administrator might install the GUI
on his laptop so that he can manage his environment while he's on the road.
2. Yes. It should be possible to install the GUI at the same time as
everything else (i.e., Data Server, Device Server, etc.). However, it
should not be required. I don't remember... Is that what we do today with
ConfigureAperi?
3. Yes. I think we start moving away from the legacy GUI as soon as
possible, in favor of the RCP GUI. Given that the legacy GUI is embedded in
the RCP GUI, I don't think we lose anything. And, the more reps our RCP
stuff gets, the better.
Regards,
Khan Tasinga
284-5142 | T/L: 8-953-5142
Dave Wolfe/Portland/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx
To
01/31/2007 12:17 PM aperi-dev@eclip
se.org
cc
Please respond to
<aperi-dev@xxxxxxxxxxx> Subject
[aperi-dev]
V0.3 GUI
install
I realize I have been kind of fuzzily assuming that the V0.3 GUI would have
an independent install. That is, it wouldn't be installed as part of the
current zip file or configured with cfgaperi. My visions is you would
install the server in one step then install the GUI (where ever you liked)
in a separate step. I doubt that's what others expect.
My reasoning being that it is indeed an independent RCP application that
gets bundled into its own little zip file by the PDE build tools and then
gets installed like any other Eclipse RCP like app.
That is, you download a zip or tar file and just expand it into a
directory, then launch the executable.
Assuming we get organized, the components could be installed via Java Web
Start and maintained via the Eclipse Update Center capability (we get this
more or less for free as an RCP app).
At this time it is an independent build (not part of the regular Aperi
build) although I expect for convenience we will run the server and new GUI
nightly builds at the same time(stamp).
In order to make the new GUI part of the server bundle we could run it as
sub-build and package it into the base bundle then cfgaperi could unzip it
for us.
One more little spin: the legacy (Swing based) GUI is still built and
installable as before. If we include the new GUI is the standard bundle we
should eliminate the legacy GUI.
So, the questions are:
1) Should the new GUI have an independent install capability (y/n)?
2) Should the new GUI be bundled with the server and installed along with
everything else (y/n)?
3) Should we eliminate the legacy GUI from the server install bundle (y/n)?
Dave Wolfe/Portland/IBM (dwolfe@xxxxxxxxxx) TL: 775-3376 Office:
503-578-3376 Personal: 503-329-3960
GUI Technical Lead, Aperi Open Source Storage Management
http://www.eclipse.org/aperi http://www.ibm.com.
If all of your problems look like nails you should invest in a good hammer
- Unknown_______________________________________________
list
https://dev.eclipse.org/mailman/listinfo/aperi-dev_______________________________________________
aperi-dev mailing list
https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
list
https://dev.eclipse.org/mailman/listinfo/aperi-dev
