Feature Requests item #1680933, was opened at 2007-03-14 12:11 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=352439&aid=1680933&group_id=2439
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: SciTE Group: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: SciTE Directory Structure Initial Comment: Sorry for the double post, i thought this place more appropriate than Neil's email address.. ================= Hello, I was wondering if you could tidy up scite’s directory layout for windows? After getting over 1 or 2 dozen different language properties pages and the help files and the global configuration files, scite’s main folder directory is much of a mess with over 80 files in the directory. I suggest a directory scheme like this: $(SciteDefaultHome)/APIs $(SciteDefaultHome)/lua $(SciteDefaultHome)/lang, config, properties, or whatever appropriate name <- folder for different property files $(SciteDefaultHome)/help <- for SciTE.html and accompanying help files This way you only have 5-10 files in the scite main directory: scite global config, scite executable, license.txt, and the scite dll. The only change you would have to make here would be to add a $(ScitePropertiesLocation) or similar variable to the global configuration file. Then just add all .properties files in the config directory. Another idea I have is a little more complex to implement, but makes more logical sense. $(SciteDefaultHome)/configs/ <- recursively look for .properties files… $(SciteDefaultHome)/configs/fortran/fortran.properties $(SciteDefaultHome)/configs/fortran/fortran.lua $(SciteDefaultHome)/configs/fortran/fortran.api $(SciteDefaultHome)/configs/fortran/fotranhelper.exe <- extra apps that could be bound to ctrl+1 or something Etc. etc. If you implement it this way, people could package language packages that would be self contained in itself… It would be also nice if you add a $(LanguagePackDirectory) binding to $(SciteConfigPath)/fortran/ so they could just use $(LanguagePackDirectory)/fortran.lua when loading properties files. I know you might not want to implement the 2nd option because it takes some extra coding of a recursive config file search, but I think this would be great to advance Scite’s usage… People could package SciTE language highlighting+api+lua scripts into one package and all the end user would have to do is copy the directory to his config directory and the whole thing would configure itself. At least implement my 1st suggestion as SciTE’s main directory structure is a mess. Thanks, Jonathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=352439&aid=1680933&group_id=2439 _______________________________________________ Scintilla-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scintilla-interest
