[jbosstools-issues] [JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application

Max Rydahl Andersen (JIRA) issues at jboss.org
Fri Jan 24 05:52:28 EST 2014


    [ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12938507#comment-12938507 ] 

Max Rydahl Andersen commented on JBIDE-14744:
---------------------------------------------

Here are some first reaction comments:

Title of first page says "choose application type" - it should say something like "choose new openshift application type or use existing application"

I'm wondering if we should call this wizard "New OpenShift Project" since it does not always create an OpenShift application...or maybe "Configure OpenShift Application" ? thinking out aloud.

On Page 1 there are three domains listed under existing applications, but on page 2 a domain is already selected when have the user chosen this domain ? From the initial login or ?

The source code field is filled out on page 2 in first usecase, is that expected ? (I think it is but not sure since it is not using a repo that looks like an openshift app ;)

Should we out Existing Applications on the top in the three ?

Can we show Featured ?

Should we maybe prepend this wizard with a binary choice: Create new OpenShift application or Use Existing application which would then change the rest of the wizard. I think that might simplify things but avoid the user to have to make that choice upfront from outside the wizard. 

One page 2 in second scenario the title just says "please configure your application" - Maybe make it "You chose 'myApplication' - review and press next to continue or press back to change the application.

I've asked [~crobson] to provide input too.







                
> Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14744
>                 URL: https://issues.jboss.org/browse/JBIDE-14744
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.1.0.Beta2
>            Reporter: Andre Dietisheim
>              Labels: application_wizard
>             Fix For: 4.2.0.Beta1
>
>         Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, openshift-quickstart.png
>
>
> The web ui offers a large set of quickstarts/templates:
> !openshift-quickstart.png!
> in a mail from clayton on the 4th of june:
> {quote}
> For QuickStarts, brokers may choose to 
> a) enable community quickstarts 
>    (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf)
> b) enable their own list of quickstarts 
>    (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json)
> c) disable the quickstarts link 
>    (delete /etc/openshift/quickstarts.json)
> To correctly fetch the quickstarts for a server, retrieve the API document
>   /broker/rest/api
> and look for the LIST_QUICKSTARTS link.  If it is present, you may retrieve quickstarts.  If it is absent, you should assume there are no quickstarts.
> Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
> * API versioning is not supported
> * Only JSON is supported
> * The body of the response is slightly different than standard REST API feed results
> * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not)
> The format of the JSON response (in either a) or b) above) is:
> {quote}
> {code}
> {
>   data: [
>     quickstart: {
>       id: "<string id>",
>       href: "<absolute URL to a display URL for the quickstart>",
>       name: "<name>",
>       updated: "<last update date in seconds from the epoch>",
>       summary: "<brief HTML body of the item>",
>       body: "<full HTML body of the item>",
>       cartridges: "<cartridge spec>",
>       website: "<URL of metadata about the source of the quickstart or the technology>",
>       tags: "<comma delimited list of tags>",
>       language: "<display name of the type of quickstart>",
>       initial_git_url: "<absolute URL or Git reference to source>",
>       provider: "openshift|reviewed|partner|community", # default is community
>     },
>   ]
> }
> {code}
> {quote}
> You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately.  You should also assume that the structure could be changed at any time.
> Cartridge spec:
> The cartridge spec is defined as either:
> a) a comma delimited list of cartridge name search conditions
> b) a string containing a JSON array
> If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field.
> Otherwise, 
> 1) split the string by "," into "segments"
> 2) trim whitespace from each segment
> 3) split each segment by "|" into "matches" - these represent logical ORs
> 4) strip leading and trailing "*" characters
> 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select.
> See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea80abf34ea8f6269/console/app/models/application_type.rb#L62
> and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea80abf34ea8f6269/console/app/models/application_type.rb#L173
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list