Axo Editor with Electron

#1

Hi, axo developers.

I have started to make axo editor with Electron.
It is simple concept, "separate XML and C++".

if you intereseted in, please test it.

https://github.com/2bbb/axo_editor

#2

Cool

But, given Axoloti is open source, is it not more 'efficient' to use the effort to help improve the existing editor in the axoloti UI?
( still lots of room for improvements)

Personally I use the object editor of the axo patcher for most editing. since it's integrated into patching/testing. I can't see why I'd change that.

On the rare occasions I edit externally, it's because I want to edit the raw text , using my favourite code editor. (Sublime)

Is there something specifically you don't like about the object editor? And why you would prefer a new/different external editor?

Anyway just my personal thoughts, good luck with your project - it's good to see off shoot projects, choice is always good :slight_smile:

#3

thanks for comment.

I think It is correct what you say.
axoloti object editor is good for WYSIWYG.
but, sometime I feel I want simple suggestion.
(I use sublime too. but it has no syntax rule.)

I very agree to 'efficient'.
but I don't know Java deeply (and sublime plugin)...
and I think I can write Electron (Node.js).

I feel happy if my motivation is conveyed to Java developers...

#4

There's no description on your git page. What does it do that was not in the java editor, syntax highlight and potentially auto complete? That is the only obvious thing to me.

#5

But, given Axoloti is open source, is it not more 'efficient' to use the effort to help improve the existing editor in the axoloti UI?

2 good reasons I can think of
1. Everyone who codes already has a preferred editor that's undergone a lot of iterations on improvement
2. Everyone who codes prefers the things their editor does, and there'll be a lot of push and pull in desired behavior.

Honestly, this wheel has been overly re-invented.

However with the Language Server Protocol gaining traction, that's one thing that I feel might be worth implementing in the Axoloti Patcher code. I'm sure if no one else takes up the challenge, I will shortly, as I am really uncomfortable with the object editor.