You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by cloverhearts <gi...@git.apache.org> on 2016/11/28 07:53:07 UTC

[GitHub] zeppelin pull request #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

GitHub user cloverhearts opened a pull request:

    https://github.com/apache/zeppelin/pull/1692

    [ZEPPELIN-1710 - WIP] Ace Editor upgrade

    ### What is this PR for?
    The current version of the ace editor is too old.
    You should also fix a bug that improperly typed non-English typing in Chrome.
    The latest ace editor has been modified.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    - [x]  import ui-ace
    - [x] 1.25 version of conformity check and paragraph form correction.
    - [ ]  import ace editor new version. (v 1.26)
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1710
    
    ### Screenshots (if appropriate)
    ![aceeditor-125](https://cloud.githubusercontent.com/assets/10525473/20660120/192cecf4-b58b-11e6-8f95-a5912b5a2cbf.png)
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloverhearts/zeppelin improve/ace-upgrade

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1692.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1692
    
----
commit 122a7f587224da4476c9a64eab89d87f0a97b34a
Author: CloverHearts <cl...@gmail.com>
Date:   2016-11-28T07:47:52Z

    ace 1.25 import

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    After checking, the automatic save will actually work.
    However, it can not be expressed only on the UI.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    Tested and LGTM. Thanks @cloverhearts for the fix!
    Could you resolve the conflict?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    fixed conflict with master branch.
    but, i found bug. does not work auto save for paragraphs.
    I'll fix this problem.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by tae-jun <gi...@git.apache.org>.
Github user tae-jun commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    @cloverhearts Nice! Hope the new version will be released soon :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
GitHub user cloverhearts reopened a pull request:

    https://github.com/apache/zeppelin/pull/1692

    [ZEPPELIN-1710 - WIP] Ace Editor upgrade

    ### What is this PR for?
    The current version of the ace editor is too old.
    You should also fix a bug that improperly typed non-English typing in Chrome.
    The latest ace editor has been modified.
    
    ### What type of PR is it?
    Improvement
    
    ### Todos
    - [x]  import ui-ace
    - [x] 1.25 version of conformity check and paragraph form correction.
    - [ ]  import ace editor new version. (v 1.26)
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-1710
    
    ### Screenshots (if appropriate)
    ![aceeditor-125](https://cloud.githubusercontent.com/assets/10525473/20660120/192cecf4-b58b-11e6-8f95-a5912b5a2cbf.png)
    
    ### Questions:
    * Does the licenses files need update? no
    * Is there breaking changes for older versions? no
    * Does this needs documentation? no
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cloverhearts/zeppelin improve/ace-upgrade

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1692.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1692
    
----
commit 122a7f587224da4476c9a64eab89d87f0a97b34a
Author: CloverHearts <cl...@gmail.com>
Date:   2016-11-28T07:47:52Z

    ace 1.25 import

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    LGTM and merge to master if there're no more discussions.
    Great work @cloverhearts !


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by tae-jun <gi...@git.apache.org>.
Github user tae-jun commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    Cool! LGTM \U0001f44d Korean Zeppelin community will love this :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    Thank you very much, @tae-jun


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    ace editor 1.2.6 upgrade done.
    resolved korean typing issue.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    There is an input problem other than English, such as Japanese and Korean.
    To solve this problem, Zeppelin needs to upgrade the Ace editor.
    We have responded to the latest ace editor first.
    Actually the version for troubleshooting is currently awaiting release from the ace community.
    This PR is completed when a new version is released from the ace community.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts closed the pull request at:

    https://github.com/apache/zeppelin/pull/1692


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    ![typing](https://cloud.githubusercontent.com/assets/10525473/20868134/45c89004-ba97-11e6-870c-d12272cb5f69.gif)
    
    Fix and upgrade done.
    
    please, review


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1692: [ZEPPELIN-1710] Ace Editor upgrade

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/zeppelin/pull/1692


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1692: [ZEPPELIN-1710 - WIP] Ace Editor upgrade

Posted by cloverhearts <gi...@git.apache.org>.
Github user cloverhearts commented on the issue:

    https://github.com/apache/zeppelin/pull/1692
  
    ![fix-ui](https://cloud.githubusercontent.com/assets/10525473/20872579/0c9b831c-bae3-11e6-9d9a-718900ef833c.gif)
    
    i was resolved UI problem.
    :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---