Okay, I simplified the language rules and such and I am posting them here in hopes that maybe some people who are interested will look at the file extensions and let me know if I got some extensions wrong for their language. The good news is that even if I get some completely wrong, I will allow the overriding of a languages extension rules via a config file (JSON).

This also will let you know what language syntax is supported.


It seems everything is working pretty well. IE9 is the only well supported IE, and there are still a few things that don't quite work well like they do on Chrome and Firefox. Since I use Chrome, everything works great for me. I am currently using it to help develop the next release.

For the first release of this feature, I plan on limiting the configurability to these settings:



So basically you can tweak the look and basic features. More complex feature controls may come in a later version. I am still figuring out how to work with the Ace API. But overall, you will have control over very common settings that people like to tweak. Oh, and remember this is a web browser editor, so don't expect it to behave like your main editor, but it is very useful with some handy features.

I still need to tweak the editor dialog and add a dialog for on the fly settings changes. Default settings will be handled via the config file though. A lot of under the hood changes are going on to, so it will still be a while before I am ready for an official release. I think this feature is big enough that I don't plan on sneaking in any other features (at least not currently).

Didn't realize I left out C/C++ and LaTeX language. They have been added above.

I also added basic accessibility for on the fly settings change. There will just be a settings button (I will probably style it to look different than it is now). It will bring up an overlay over the code with the settings.



So that completes the basic features. I now just need to decide on a lot of small details and clean up the code. I will probably also be doing some more under the hood stuff and possibly some restyling of some things.

So I am going to probably go quite here until I finish up, or unless anyone has questions, comments, or suggestions.

It is always tough to gauge interest on this forum since I mainly seem to talk to myself on this thread, but hopefully people are excited for this feature. I know I am pleased with it...though I guess that should be expected since ideas that I want is mainly what drives my development.

As I move forward, I am curious if anyone has any insight on this license question?

Tonido Shell is released under the GPLv2 because the PHP Shell core is released under GPLv2. Not my favorite choice, but that is the nature of GPL.

So the Ace editor is released under the Mozilla tri-license MPL/GPL/LGPL. Can these be released together? At first I thought maybe so, but now I have doubts.

Worse case scenario is that I will just add support for Ace but release it without Ace and release the Ace bundle separate. I think that would probably be safe.

Best case scenario I can bundle all this stuff together and things will continue as usual.

I just need to sort through the licensing stuff.

I am still working on some under the hood stuff, but this question will probably affect how I do some stuff internally.

The real answer: No one really knows.

Thanks for the honest answer. That is generally the impression I get .

I guess I will just bundle it all together then. If I am informed later that I am somehow violating the license or should do it anther way, I will change how I do things. Licensing stuff is one of the most confusing parts of development.

Most everything is in now. I am slowly working towards a release. Most of the under the hood stuff is done. I have separated things into better modules and now defer the loading of a number of modules until after the page loads. I also embed most of the graphics using data URI in the CSS now. What this means to the user... nothing really; the page loads faster, but then it loads the modules, so overall it still loads about the same.

I am working to get a clean build system because I plan on throwing this up on Github. That way I can just track issues there, and people can make request or even make changes and issue pull requests.

I am really tired of bundling the source inside the plugin, and this will also allow me to no longer do that, since the repo will be publicly available. And it will give the packing environment as well opposed to just source code.

So that is my main focus now...clean up the packing process. It will probably be handled mostly, if not entirely, by nodejs.

Once I get the repo up and going, I will release a beta.

is this ap useful for non-programmers...not sure what this is about.

Some people hate using the terminal. This app allows you to access a pseudo terminal to do things you can't do in the Tonido explorer. If you are the kind of person who doesn't use the terminal on your PC unless you have to, then maybe this app is not useful.

The text editing capabilities I think is useful to anyone who wants to edit files on their plug. The fancy new editor I am adding is very useful for programmers, but also has some good shortcuts and features for basic text editing.

So, yes it is useful to non-programmers, but only you can answer if it is useful to you.

Repository for TonidoShell is here https://github.com/facelessuser/TonidoShell

I will hopefully have a beta posted soon. For those who might be itching to try it out, you can build your own form the repository; just follow the instructions.

Beta 1 build for 1.4.0 http://www.4shared.com/zip/_RFH8vjj/ton ... _univ.html