Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mobile-iwg] Status of Pulsar Eclipse Galileo package 
Hi David,
Thanks for the explanation - this is actually looking better than my "worst case" assumption I had.
One more question: When you talk about "install a selected SDK", can you explain this process?
- Are you assuming a "standard HTTP" style password protection of the P2 repository? (HTTP Basic or Digest authentication over HTTP or HTTPS) - Is the IDE using P2 authentication dialogs, or were you able to replace those? 

further more:
What is the packaging format of the "SDK"?
- is the SDK contained in an executable format? (which host Operating Systems does your plugin support) - after the SDK is downloaded and installed, do you use the new "MTJ device registration" APIs? 
-- How will Eclipse know the path of the SDK?
-- Do you assume UEI compliance.
- Would this technically also support an SDK like RIM, which is currently distributed as a set of multiple Eclipse Plugins (and not a stand alone UEI executable) 

Thanks again!

-Christian


David.Dubrow@xxxxxxxxx wrote:

Hi Christian,
I just wanted to clarify the status of the “quick install view.” You are correct that there is not enough time to implement the full visually appealing version shown in the use case discussion wiki page, however, I am planning a pulsar specific view that will unfortunately be a lot more utilitarian and less flashy given the amount of time I have to implement it. 

    * It will be an eclipse view with a table tree showing
      repositories, optional categories and sdks in a multiple root
      tree in one column and sdks’ installed status on the other column.
    * Top-level nodes denoting sdk repositories will be able to have
      icons but they need to be limited to 16x16 so they look
      reasonable in a tree view.
    * Since only install is supported, there will be one view action
      (toolbar and menu) to install a selected sdk.
    * Sdks will show installed status, but will not be prevented from
      being installed multiple times because we are not supporting nor
      tracking uninstalling in this release due to lack of development
      time.
    * The view’s install action will open a standard p2 install wizard
      with support for EULA acceptance if the EULA is provided with
      the metadata.



--David


On 5/4/09 10:45 PM, "ext Christian Kurzke" <christian@xxxxxxxxxxxx> wrote:

    As I explained in the email last week, we had today the "official"
    code-freeze for the Eclipse Galileo build.

    For MTJ/pulsar, I have been granted a 2 week extension for our
    code, but
    - i think we have a very good idea now what the final package will
    look
    like, and engineering is working hard to make the final deliveries.

    In this weeks meeting I would like to go over the current status
    of the
    work. Hopefully Diego (Motorola) and David (Nokia) can give a brief
    status report.

    My understanding is that due to the lack of a official Pulsar "quick
    install view", we will not be able to have a "friendly" guided SDK
    discovery and download UI, as initially planned. (see here for initial
    proposal:
    http://wiki.eclipse.org/EMIWG/MADKQuickStartUseCasesDiscussion)

    Instead we will only be able to deliver a "P2" user experience with
    preconfigured links to the individual company repositories.
    For an overview of this UI flow, see:
    http://wiki.eclipse.org/Equinox_p2_UM_workflows (note, this is
    Equinox, but the Galileo will be very similar)

    One of the biggest deficiencies will be the handling of "user account
    creation". If a user is not already signed up at any of the
    participating "Developer Programms", and the P2 URL is password
    protected, then the download will fail, and there is no option
    given for
    the user to sign in.
    It may in fact not even be clear to the user WHICH password he is
    prompted for. (the P2 Log-In Dialogs are very sparse)


    Please bring creative ideas to the meeting on Thursady how we can
    address this issue.

    -Christian


    _______________________________________________
    mobile-iwg mailing list
    mobile-iwg@xxxxxxxxxxx
    https://dev.eclipse.org/mailman/listinfo/mobile-iwg

------------------------------------------------------------------------

_______________________________________________
mobile-iwg mailing list
mobile-iwg@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mobile-iwg

Back to the top