Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation #13

Open
rdytogokev opened this issue Mar 18, 2017 · 10 comments
Open

Documentation #13

rdytogokev opened this issue Mar 18, 2017 · 10 comments

Comments

@rdytogokev
Copy link

rdytogokev commented Mar 18, 2017

One of my favorite features of Sublime Text is the ability to have multiple editing cursors.
If you have not seen it before, Sublime's website has an animation of it on their homepage.
https://www.sublimetext.com/ It's a major selling point.

Recently, I found out that the ACE editor is already capable of doing the same thing. Here is the default keybindings documentation. https://github.com/ajaxorg/ace/wiki/Default-Keyboard-Shortcuts Soon as I learned the keyboard bindings I started using it right away.

That is when it hit me, AceIDE could use some basic documentation. I propose two things:

  1. Develop the Ace IDE Wiki pages https://github.com/AceIDE/editor/wiki. The first page I would add is the keybindings. I would be willing to contribute some basic content to the wiki if needed.

  2. Create a simple icon in the app interface to direct people to the wiki for help.
    documentation-idea

What do you think?

@shanept
Copy link
Member

shanept commented Mar 18, 2017

I like the idea of having it built into the app. However I'll be moving settings to its own page so putting documentation on its own page wouldn't be a bad idea

@rdytogokev
Copy link
Author

Gravity Forms has a built-in help page like you are suggesting. I think it looks pretty nice.
screen shot 2017-03-17 at 11 59 23 pm

The way it works with Gravity Forms is:
When a link is clicked, it opens a page on the Gravity Forms website that has the content.

Is this how you would like it to work?

@shanept
Copy link
Member

shanept commented Mar 18, 2017

Hmm
We could point it to wiki pages here on github. That would work.

But for things like shortcuts, that could be built into the plugin itself, I think.

@rdytogokev
Copy link
Author

Sounds good. Do you need help with making the documentation admin page?

@shanept
Copy link
Member

shanept commented Apr 1, 2017 via email

@shanept
Copy link
Member

shanept commented Apr 2, 2017

So as far as I can currently see, topics for documentation are as follows:

General Ace editor shortcuts
AceIDE programming/filter advice

Can you think of any more subjects?

@rdytogokev
Copy link
Author

Four main area's need to be addressed:

  • AceIDE Basics: Opening, Modifying and Saving Files, Opening Directories.
  • AceIDE Shortcuts: Text Selection, Editing and Deleting Text, Find and Replace, Code Folding.
  • AceIDE Settings: Theme, Adjusting Tabs, Gutters, Scrollbars, Font Size, Guidelines, Invisible Characters.
  • AceIDE Development: Contributing, Coding Standards, Programming/Filter advice, Submitting Bug Reports and Feature Requests.

What do you think?

@shanept
Copy link
Member

shanept commented Apr 3, 2017

I like that. Very nicely structured.
I'll start to create the wikis

@rdytogokev
Copy link
Author

Have you created those wikis?

@shanept
Copy link
Member

shanept commented Jan 6, 2018

Not as of yet. I've been very busy past few months and haven't even given it any thought, unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants