Christopher Kampmeier wrote:
> Michal Pryc wrote:
>> Hello Indiana and Pkg communities,
>> I have blogged about Imagine, GUI tool for IPS, so you can try it out now:
>> http://blogs.sun.com/migi/entry/indiana_ips_and_imagine_prototype
> 
> Hi Michal,
> 
> We sync'd up our IPS bits for Ubuntu with those from OpenSolaris and we 
> were able to successfully use Imagine on Ubuntu to install GlassFish and 
> OpenDS.  See below for our experience and some recommendations.
Great to hear!
> 
> We'll be trying the same on Windows in the next several days.
Regarding running Imagine on Windows, you will need to install following 
parts:
- Python
- GTK+ runtime (http://www.gimp.org/~tml/gimp/win32/downloads.html)
- PyGTK (http://www.pygtk.org/downloads.html)
- PyGObj (http://www.pygtk.org/downloads.html)
- PyCairo (http://www.pygtk.org/downloads.html)


> We're also going to give John Hawk's IpsPkgTool a try on Ubuntu.
John is making effort to merge Imagine and IpsPkgTool :)


> FEEDBACK
> ========
> 
> 1) Running gui/pkgrepo.py
> 
> b) pkgrepo.py Script: It would be nice to call this script something 
> else since it's main role is to help manage images rather than repos. 
> However, since users won't need to execute it directly after you make 
> the start up enhancements, this change is not super important to us.
Right, what about imagemanager.py ?

> c) "Add" dialog of pkgrepo.py:
> 
> Fields and Field Names of pkgrepo GUI:
> * Name - it would be useful to rename this field to "Image Name" or name 
> the overall window to "Register Image" or something similar.
> * Local dir: would be useful to name this field "Image Location" or similar.
> * Remote url: I found by trial and error that the authority, e.g. 
> "sun.com=", is required to be part of this field in addition to a URL. 
> It would be helpful to do one or more of the following:
> ** split out the authority into a separate field
> ** rename the field and/or provide an example where the authority is 
> included
All those comments are fine for me. The pkgrepo.py was done without any 
designing effort, so I agree that those things should be changed.

> Adding an Image:  It's not clear from the user interaction that the tool 
> is actually creating a new image and directory (e.g. pkg image-create) 
> or simply trying to register one that already exists.  I understand now 
> that the result is the creation of an empty image. Besides, "Remove" 
> doesn't actually delete an image, it simply removes it from imagine's 
> config file.  I don't have great guidance here, but it seems awkward 
> that the tool isn't more explicit about the creation process.
Also here is very good feedback. I agree that adding image is confusing, 
but I don't actually know which use-case would be the best? If there is 
repository under folder, the one should be selected or some dialog if 
override existing repositories? Also I don't know how to behave during 
remove image. I didn't wanted the user to remove all the image with 
packages with one click, so that is why I am removing only entry in the 
  configuration file. This is the topic to discuss.

> d) "Image list" window:
> 
> * It would be very helpful to highlight the active image with a check 
> mark or similar.
What do you mean?


> * We'd rather not have the "Default" image listed if the image doesn't 
> actually exist.  The Default entry is noise on non-OpenSolaris platforms.
Yes it is, but I didn't implemented yet part of actually checking if the 
image is valid one, so I can't check if there is Default image, that is 
why it is hard - coded. This is the subject to change.

> 
> It would be nice to make it more explicit to the user that he/she is 
> working with a specific image.  Currently, the image name is in parens 
> at the top of the window.  That's too subtle when someone is working 
> with more than one image.  A much fancier approach would be a View 
> option that presents a navigation tree or list of images on the left. If 
> one image is registered, then the nav column wouldn't be present by 
> default.
Right, there will be change in desing of the IpsPkgTool + Imagine so 
most of those things will be changed in the nearest future :)

-- 
best
Michal Pryc
http://blogs.sun.com/migi

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to