[ 
https://issues.apache.org/jira/browse/BROOKLYN-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940565#comment-14940565
 ] 

ASF GitHub Bot commented on BROOKLYN-177:
-----------------------------------------

Github user azbarcea commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/930#issuecomment-144869789
  
    
    * drag
    
![brooklyn-drag-01](https://cloud.githubusercontent.com/assets/661912/10235625/317249d4-689e-11e5-8484-558210a4538a.png)
    
    * drop
    
![brooklyn-drag-02](https://cloud.githubusercontent.com/assets/661912/10235623/316f0580-689e-11e5-8019-028d35a5b861.jpg)
    
    * the _code editor view_ is now persistent 
    
![brooklyn-drag-03](https://cloud.githubusercontent.com/assets/661912/10235624/317129a0-689e-11e5-985a-15e49e6f00b3.jpg)
    
    The following known issues:
    * the drop event will paste the JSON format and not the YAML. The current 
text is:
    
    is:
    ```javascript
    services: [{ type: 
org.apache.brooklyn.entity.brooklynnode.BrooklynEntityMirror }]
    ```
    should be:
    ```yaml
    - type: org.apache.brooklyn.entity.brooklynnode.BrooklynEntityMirror
    ```
    or even:
    ```yaml
    services:
    - type: org.apache.brooklyn.entity.brooklynnode.BrooklynEntityMirror
    ```
    
    To make the drop event context dependent (exists or not the *services:*), 
then, a javascript yaml (blueprint) parser should be created (like [1]). It 
should understand CAMP syntax.
    
    References:
    [1] - http://www.json2yaml.com/ 


> Support for drag and drop when editing Blueprints
> -------------------------------------------------
>
>                 Key: BROOKLYN-177
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-177
>             Project: Brooklyn
>          Issue Type: New Feature
>    Affects Versions: 0.8.0
>            Reporter: Alex Zbarcea
>
> Applications in Brooklyn are built via composing services. As services are 
> available in the catalog, yaml could be constructed much faster if a 
> drag'n'drop feature would be available allowing a user to select and drop the 
> required entities. Further editing of the yaml would still be necessary, but 
> such a feature would also provide basic guidance to the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to