Quick Questionnaire for monoEdit users
Forum > monoEdit
MilesPosts: 128 |
10/03/2006 23:40 pm | |
| To help with the development of monoEdit 2.0, I have a few questions that I would like to ask anyone who is currently using the script. If anyone could answer them I would grately appreciate it! 1. What is your main use of monoEdit? 2. What is the thing you like the most about it? 3. If anything could be changed or improved upon what would it be? 4. How did you find out about monoEdit? E.g. which web site were you referred from? Thank you! |
||
PhorboxPosts: 3 |
16/03/2006 09:13 am | |
| 1. I use it as archive system for my main project. I store some documents on the website and monoEdit helps me and other people to access these materials. 2. monoEdit is MONO which is 1 file only)) Thats really cool) 3. Maybe design could be improved.. the one that we have today is sooo plain.. 4. I don't remeber, some website with links to File Management Systems.. |
||
MoosPosts: 2 |
16/03/2006 16:35 pm | |
| 1. someone to be able to edit simple text html files without knowledge of html, so a wysiwyg would be perfect. 2. It is simple. 3. User cannot change to another directory. 4. Found it by Google |
||
iamgriffinPosts: 2 |
27/03/2006 01:22 am | |
| 1. I use monoEdit to allow my friends to easily set up and manage personal web sites on my Linux web server without them having to learn to use Unix or an FTP program. Plus, they can access it from any machine with a web browser, without having to install any software. 2. I don't know what I like the most about it, but some of the reasons that I like it is that it is is self contained (1 file), open source, easily customizable, and does not require the user to install any software on the client side. 3. I would like it to be able to handle directories better, such as deleting a dirrectory and all of it's contents (I am currently working on implementing this safely). 4. I may have read about it initially somewhere, but probably found it through a Google search. |
||
MilesPosts: 128 |
02/06/2006 18:17 pm | |
| Thanks for all the replies so far! |
||
anoxiaPosts: 3 |
04/06/2006 11:11 am | |
| 1. What is your main use of monoEdit? I use it to quickly edit and debug sites, if I'm away from my stationary computer. 2. What is the thing you like the most about it? It's all in one file, and doesn't require any big databases. 3. If anything could be changed or improved upon what would it be? Not have to chmod the root, too big a security risk. 4. How did you find out about monoEdit? E.g. which web site were you referred from? I think hotscripts.com Other: I like the design, it's simple and easy to customize. Keep up the good work. |
||
MartinPosts: 5 |
25/01/2008 08:09 am | |
| 1. What is your main use of monoEdit? - I incorporated a WYSIWYG editor in 1.32 (HTMLarea) and it works perfectly as online editor for web sites. 2. What is the thing you like the most about it? - Simplicuty, for sure. Please keep it simple and straightforward! The web is full of too complex and heavy crap. Don't be tempted to add "extras" to your great software. It's just great the way it is. 3. If anything could be changed or improved upon what would it be? I think it would be a good idea to have the possibility to disallow viewing and access to some directories, just the way some file types can be disallowed. 4. How did you find out about monoEdit? E.g. which web site were you referred from? Don't remember. Sorry :-) |
||
MilesPosts: 128 |
26/01/2008 21:32 pm | |
| Hi Martin, Thanks for your feedback. The idea of disallowing some directories is definitely a good suggestion. How would you want to control this? They could be set like the file extensions or maybe even per user so you can limit a user's access to some files. Oh, and don't worry -- monoEdit is staying simple, which I hope you will recognise in using 2.0. Thanks! |
||
MartinPosts: 5 |
26/01/2008 22:18 pm | |
| Hi Miles, As for the directories, without being a PHP programmer (sorry for the unprofessional suggestion), things maybe could be done in a similar way the files are disallowed. Stuff like: ------------------- $disallowDirectories = array('/dir1','/dir2','/dir3' ....); ------------------- I hear that in ver 2.0 you can disallow moving to an upper level directory. This is generally a very good idea. However, in my opinion it would be best of we could define the level the user could get to a higher level. Here is the reason: Sometimes it is a good idea to setup the Monoedit to a separate dir (say /admin). Then, if the user cannot move to the upper dir, he has a problem :-). Thanks again for the wonderful piece of software. P.S. Oh, and please don't forget to send me a download link for the ver 2.0. I still haven't received it :-) P.P.S. I think that disallowing directories at "per user" level would be too much programming hassle and a too complex approach. Keep it simple ;-) |
||
MilesPosts: 128 |
27/01/2008 01:10 am | |
| I suppose we could go down one or two routes with this -- either set it up so you can choose to allow specific directories to be accessed or choose to disallow. I would probably favour the former. In 2.0 there is a so-called minimum access depth so you can't view or edit files that exist above it. I could make an option to allow this depth to be modified to allow certain directories to be modified above it. I think that would probably be the simplest solution. For example, your minimum depth is set to the same level as where monoEdit resides. This could be /path/to/admin/index.php so by default you can only edit files that exist in /path/to/admin/ or any sub-directories within that. Taking your suggestion, if you wanted to modify files in /path/to/, path/to/images/ or even /path/ you would have to explicitly define that. Do you think that would solve the problem? P.S. You now have access, as per my note in the beta topic. |
||


