Closed jbadeau closed 8 years ago
thats cool
Thanks & Regards, Deepu
On Thu, Sep 29, 2016 at 10:50 AM, Jose Badeau notifications@github.com wrote:
Hello,
We are currently making a JDL editor for Eclipse, IDEA, WebStorm and web browsers. The Editor is based on xtext and will hopefully be ready soon.
https://github.com/jbadeau/jdl
The editor currently supports:
- Syntax Coloring
- Semantic Coloring
- Error Checking
- Auto-Completion
- Formatting
- Hover Information
- Mark Occurences
- Go To Declaration
- Rename Refactoring
- Debugging
- Toggle Comments
- Outline / Structure View
- Quick Fix Proposals
- Find References
- Call Hierarchy
- Type Hierarchy
- Folding
Hopefully this is a smoother experience for people who want to edit JDL locally.
β You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/25, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlFzgShZSz4Brjr0vR_-x7_ZQok2BWks5qu0qggaJpZM4KJltM .
since its not an issue im closing it but its really cool. let us know once its ready and released we will try to add it to our marketplace or docs cc @jdubois @MathieuAA
Yes that's really cool. In fact that's a project I had in mind for some new trainees (don't worry I have other things for them!!). As your project is Apache 2 licensed, would you be interested in migrating it to the "jhipster" organization? That would make it "official". Of course, you would keep full rights on the repo, I would create a specific team in our org for that.
Wow! That would really be awesome if it were a JHipster project! Great idea Jose!
@jdubois You always have ideas for trainees, don't you? :)
@jdubois I have no problem with moving to the jhipster organization. All the packages are already using 'io.github.jhipster.jdl' which means little to no refactoring. The editor is currently fully functional and can parse everything except for the new microservice related options.
When you move it then we can create the tasks for a alpha release:
Just let me know how you want to transfer the org. I can make u an admin?
I also don't have a problem with your trainee working on the editor as well.
I dont understand the webversion you mentioned? what does it do? do you have any screenshots or gif
and are you using a DSL of your own? I thought you were using the DSL we have at jhipster-core
screenshot editor in eclipse https://github.com/jbadeau/jdl/blob/master/screenshot.eclipse.png screenshot editor in browser https://github.com/jbadeau/jdl/blob/master/screenshot.web.png
The intellij and eclipse plugin looks great but the web version isnt that impressive so lets not do that. JDL studio would suffice for web and it has all the above mentioned features and more. so lets do only the IDE plugins
@deepu105 alrighty
@deepu105 I invited you, I will make you an admin and you can move the project to the jhipster org.
Thanks a lot!!! OK I will move the project, 2 things first:
@jbadeau I have a working POC using your xtext in a VS Code extension following this blog. Since it uses xtext v2.11 which is not released yet, I'll PR against a "vscode" branch if that's OK with you.
@cbornet of course π
That's really great guys. I will have time next week to take a closer look, migrate the repo to the JHipster org, etc...
Le 30 sept. 2016 11:27 PM, "Jose Badeau" notifications@github.com a Γ©crit :
@cbornet https://github.com/cbornet of course π
β You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/25#issuecomment-250856338, or mute the thread https://github.com/notifications/unsubscribe-auth/AATVoyqRnxSKjM7t_xl3CO6hVDl9ehU1ks5qvX6ogaJpZM4KJltM .
Teasing for VS Code !
@cbornet very nice. I will finsh the grammer this weekend.
I have completed the grammer and have added support for opening .jh and .jdl files.
If someone who has travis ci experience could have a look at why the build is failing it would be greatly appreciated. I just need someone to add the correct travis params to dump the logs
i have tried
after_failure:
and other variations but no joy
this problem is tracked by https://github.com/jbadeau/jdl/issues/12
once the build is woking I can continue to publish an alpha release
pinging our travis guy @pascalgrimaud
I can have a look this afternoon
@pascalgrimaud thanx allot? Was it the virtual frame buffer? I couldn't see the logs.
@jbadeau : I don't know, I simply launch mvn clean install
on my machine and I saw Eclipse launching + closing in 1sec => it means there are some GUI tests in your project, so xvbf (X Virtual Framebuffer) must be started in Travis build othewise these tests will fail
@colameo so you can join the thread
@jbadeau could you create a branch on which I can PR the VSCode extension ? I can't PR against an unexisting branch in gh...
@cbornet Sorry, I understood you would create a 'vscode' branch. I have added you as a collaborator now so feel free to create a branch. The intellij/idea code is under project 'io.github.jhipster.jdl.idea' so maybe a project like 'io.github.jhipster.jdl.vsc' would be good
@cbornet i just created your vscode branch
As soon as the repo has been moved to the jhipster org I will make a private release (not published) so people can test the eclipse, intellij and visualstudio code integration.
I have just create a diagram branch which will provide the diagram view of jdl files. Currently it will only be provided for eclipse
Soon :smile: !
Damn thats sexy
Thats awesome @cbornet I wanted to do this for JDL studio as well. Do you think its portable to code mirror?
:-) great !
@deepu105 xtext supports codemirror and orion http://www.eclipse.org/Xtext/documentation/330_web_support.html Havent looked into it much yet @colameo would probably know more
@cbornet orion would be our preffered framework because better feature support. but code mirror is also possible.
The feature support for code mirror looks good. If we can use the stuff @cbornet wrote for vscode on jdl studio it would be awesome. It already supports sublime shortcuts, auto complete etc, but the templating stuff is too good. I was thinking about adding that manually. @cbornet could you take a look if its possible to use it on the website?
Thanks & regards, Deepu
On 5 Oct 2016 21:03, "Serano Colameo" notifications@github.com wrote:
@cbornet https://github.com/cbornet orion would be our preffered framework because better feature support. but code mirror is also possible.
β You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jhipster/jdl-studio/issues/25#issuecomment-251710468, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlF5RXWxB23pr9Cd4vXsRjiwLeQPE8ks5qw8NAgaJpZM4KJltM .
VSC uses TextMate styled snippets. That's actually very easy to write. Do you think jdl-studio can use it ?
You can see the snippets in https://github.com/jhipster/jhipster-ide/pull/31
Hi, is this ready for IDEA ? as plugin?
currently we do not support IDEA but would love too. We are currently waiting for jetbrains to integrate LSP into intellij. Please vote if you would like to see it too.
https://youtrack.jetbrains.com/oauth?state=%2Fissue%2FIDEABKL-7409
Hello,
We are currently making a JDL editor for Eclipse, IDEA, WebStorm and web browsers. The Editor is based on xtext and will hopefully be ready soon.
https://github.com/jbadeau/jdl
The editor currently supports:
Hopefully this is a smoother experience for people who want to edit JDL locally.