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

Newbie questions! #2

Open
altaywtf opened this issue Oct 27, 2016 · 5 comments
Open

Newbie questions! #2

altaywtf opened this issue Oct 27, 2016 · 5 comments
Labels

Comments

@altaywtf
Copy link
Collaborator

Hi @hwclass! 👯

I've took a general look at the project and I think it'd be a useful tool for developers. I decided to gather my questions under this issue so we'd have an archive about these discussions.

  • I guess we are going to implement browsing through filesystem feature. I am not experienced with these kind of fs things. Do you recommend any resource so I can dig into it? (by the way, we can create or use a component like this for this feature.)
  • Are we going to implement a code editor (and also a rich text editor other than native contentEditable feature, I guess React doesn't like it much)? (btw I have some experience with Codemirror and react-rte)
  • If we are, how will be the decision process of types of editors we'll be using for various file types?
  • Are we going to show hidden files/folders? 😅
  • I'd be very happy to contribute this project, especially on the unit testing part 😈

We can discuss the roadmap and features we want to have on the first iteration under this issue or Telegram.

@hwclass
Copy link
Owner

hwclass commented Oct 28, 2016

Hi @altayaydemir,

Thanks for comments and these are the thoughts I have:

1- I am using only the official documentation of Node and so just check the specification from here: https://nodejs.org/api/fs.html. In the other habd, we will be using a method that provides us the client<->server communication by using Server-Sent Events. This means in around every second, we have got the actual state of the directory that we have opened. Additionally, thank you for the tree component and loved it. We only need a github issue to implement this ;)

2- In the first step, we can go on just with a div element but in the future, we will need for formatting and etc. Just keep it ;)

3-Keep it in mind again ;)

4- I do not think of importance in the first phase to provide showing/editing hidden files. We need to learn some OS specification at all.

5-Quality is our must ;) Of course. And I am very happy to work with you ;)

Maybe we need a roadmap now..

Thanks

Barış

@asarialtun
Copy link

My 2 questions not about development but about usage of Ziya:

  1. Which languages are supported (or planned) for syntax highlighting?
  2. Can I create a new document from scratch, or save my edits on an existing one? Or is it in read-only mode?

@hwclass
Copy link
Owner

hwclass commented Jan 25, 2017

Hi @asarialtun

Thanks for your question. At this time, since we have been using Codemirror for our inline editor, we are limited with that context but also since the list is really large (fortunately) for languages that are being supported by Codemirror and will be trying to integrate a basic file load management for the CSS files of the languages as well.

For the second one, currently we are not supporting for creating a new document but it would be great to implement. At this time, you can edit and save the existing ones.

@asarialtun
Copy link

Hi @hwclass
Thank you for your reply.
Is there a keyboard shortcut to save existing documents? I couldn't with ctrl+s

@hwclass
Copy link
Owner

hwclass commented Jan 25, 2017

Hmm, we have also supported CTRL + S on Windows but there may be a problem for that. Can you open a new bug issue, our dearest Q/A test specialist, Mr. @asarialtun 👍

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

No branches or pull requests

3 participants