New file types

[pjafrombbay]

Hi!

I would like to be able to change the order of file types that appear when you use the "New file" drop down list. In particular I would like "text file" to be the default. In addition there are many file type that I simply will never use so it would be nice to remove them from the list.

I have been able to change the order for the "File open" and "File save" dialogues using the "Preferences" settings.

Is this possible and if so how is it done?

Thanks in advance,
Peter

[Karlis]

You can set the default document type in Preferences by entering TXT extension. You can update the new doc menu by locating and changing the newdoc.ini file that comes with the application.

[pjafrombbay]

Karlis,

Thank you once again. Its quite easy when you know where to look.

RapidPHP is a really good editor/IDE; thanks for the work you put into it.

Regards,
Peter

[Karlis]

Thanks! Good that you have managed to get it configured.

The new document menu was not intended to be modified by regular users, hence no easy setting for that. But ini file still allows to do this for more demanding users. In fact many things can be changed by modifying ini and other files that come with the application.

[pjafrombbay]

Karlis,

Thanks again. Do you have any documentation on what can be changed? It does not have to be "professional level" documents.

Regards,
Peter

[Karlis]

No, this is undocumented because it is not to be changed by regular users. You can relatively easily tell what each file is for by looking at its contents.

[davenz]

The trick is to open all the ini files and have a look at how they are compiled. Just be sure to make all changes with the software closed because when closing, it will overwrite any changes you have made to the configuration files in the meantime.

Karlis is right; these files should only be tweaked by people who know how to backtrack if things go wrong and I don't see any advantage in having documentation available for something that can break the software. It is very much a case of 'tweaker beware'; if it works out fine, then great, but if things break, then at least be able to go back and put things right.

Dave.

[pjafrombbay]

The trick is to open all the ini files and have a look at how they are compiled... Karlis is right; these files should only be tweaked by people who know how to backtrack if things go wrong and I don't see any advantage in having documentation available for something that can break the software...

Dave,

Thanks for the advice. I have been a programmer for thirty years. I currently tweak Linux installations, PHP installations, other editors like EditPlus (on Windows), Scite (on Windows and Linux) and Greany (on Linux) and write my own WordPress themes. The technique that I have been using all these years is to re-name the original file "file_name.ext_ORIGINAL" then make the changes to "file_name.ext". If there is a screw up the I simply delete "file_name.ext" and re-name "file_name.ext_ORIGINAL" back. Do you think this technique will work with RapidPHP?

On the issue of not providing documentation, I find myself in disagreement with you. When one purchases the software it becomes theirs and they are free to do what ever they choose with it. That said, if they do "break the software" then they are responsible for fixing it. All the systems I mentioned above DO provide documentation for tweaking; its called making the best possible use of the software product.

Thanks for your interest,

Peter

[Karlis]

You must get out of Linux frame, when there is mostly no UI but config files This is Windows, there are dialog windows and ini files are not ment to be a features (except for multi-platform apps like php, apache), think about them like as specific exe files. They are not configuration files, they are parts of program.

I gave you this opportunity just because you needed it. 99.5% do not and should not mess with this. If I have to document how to change all ini files, dat files, registry settings and algorithms used in the software that might be of interest to 0.5% of users, I'd better kill myself first.

[davenz]

I think its about time I stopped 'helping' people here. You're damned if you do and damned if you don't.

[chrisjlocke]

Give me a kiss. I still love you.

When one purchases the software it becomes theirs and they are free to do what ever they choose with it.

Not quite true. You've only been given a licence to use the software. Technically, the software belongs to Karlis and its not 'yours'. Depends on the actual software licence, so this may not be quite true for Blumentals stuff.

[Karlis]

You're damned if you do and damned if you don't.

Don't even think about it. We love you! What is more, same applies to improving software

As for the licensing, I don't mind users modifying or destroying hardcoded settings, but I do not want to stimulate it and then receive bug reports on unexpected behavior. Peter has a valid point, but he is good with config files, not so with other users. Microsoft hides tons of features inside Windows registry too, you know

[piposek]

If I have to document how to change all ini files, dat files, registry settings and algorithms used in the software that might be of interest to 0.5% of users, I'd better kill myself first.

Hopefully NOT