Topics - daddydave [ switch to compact view ]

Pages: prev1 ... 9 10 11 12 13 [14] 15 16next
66
Clipboard Help+Spell / Any screencast for Clipboard Help+Spell?
« on: June 03, 2010, 09:07 AM »
I'm figuring it wouldn't hurt to ask if there is any screencast for CHS, since I see screencasts for other things. I have this installed but can't get in too much of a flow with it. I find the help file a bit confusing.

67
Mainly I am trying to get a feel for how many closet AutoIt3 scripters are lurking out there (hence I didn't ask about WSH, Perl, or any number of other scripting languages). From appearances this looks like an All-Autohotkey shop, but appearances can be deceiving.  I know I've seen one or two of you in the AutoIt3 forums.  Make yourself known! Are there coding snacks that will never be written because the person who has an interest in writing it is more comfortable with AutoIt3? (And it is respectfully requested if possible that this is not turned into a debate as to which is better, that seems to have been covered in previous threads)

68
What's the Best? / What's the best: Wiki Host?
« on: May 26, 2010, 05:13 PM »
What's the most flexible wiki-specific hosting site, for people not wanting to host it themselves? (e.g.., PBWiki etc.)

Some characteristics to think about (I'm sure I've forgotten some):

- Is it ad supported or can you put your own ads?
- Wiki software used (MediaWiki or Proprietary)
- Cost if any
- Ease of editing (do non-technical people feel comfortable with it?)
- Spam prevention features
- Moderation features
- Types of content supported

69
OK, people these days like their applications to be portable, and store their configuration in the same folder as the exe.

But Windows Vista and 7 really don't like it if you have to save your configuration file back into any subfolder of Program Files, so normally you as a developer would just put in in %APPDATA%\program name, right?

All right, so when you are writing the installer (not every user wants to bother with zips), it seems you have a couple of choices:

1. Ask the user if (s)he wants a portable install or a regular install. If it is a portable install, store the settings in the same folder as the program. Otherwise, store the settings in the registry and %APPDATA%\program name

2. Just make the default install location C:\Tools\program name and store the settings in the same folder always. Keep things simple. Make it easy to copy to USB stick later if needed.

Either way, of course, the user can change the default install folder. I'm probably the only one with a folder called C:\Tools so an attentive user may want to change it to C:\Utilities or something. Or back to C:\Program Files which breaks my plan.

I've been leaning toward #2 for a while. Microsoft doesn't try to stop anyone from saving to C:\Tools so that bit of security by obscurity is bypassed. When I as a user install a program, if it's a zip file, C:\Tools is where it goes. If it's some random program and I suspect that the program uses an INI file instead of the registry, C:\Tools is where it goes.

This is learned behavior. Before Vista, I was conditioned to put everything in Program Files, even if the app came to me as a zip file. In Vista, if I tried this, the first time I needed to save settings back to an INI file inside a subfolder of C:\Program Files, it didn't even give a UAC prompt, it simply did one of these two things:

a. It would simply fail.

b. It would appear to work, but it was actually saving to file to a redirected location within my user profile. So I and seemingly the programs themselves had trouble finding the program settings because we had to look in both the real Program Files folder and the virtual Program Files folder within my user profile.

So what I used to do in Vista was
1. Make a note of the folder name the installer created
2. Uninstall the program
3. Make sure the program folder was still there and set the permissions so that I had permissions to write to it
4. Reinstall the program

This seems to be less of an issue with Windows 7, which is around the time I decided to install more programs in C:\Tools. If I put a file in one of the forbidden locations, I usually get a UAC prompt and it lets me continue. I haven't thought much about folder redirection since moving on to Windows 7, so either it has become more transparent, or it's because this is around the time I started installing things to the Tools folder more frequently. I'm curious now, I'll see if I can find the redirected folders on my main box (which runs Windows 7) when I get a chance. It's strange that I don't remember ever even seeing them in Windows 7.

(And yes, I know UAC and folder redirection can be turned off, but I never felt good about doing that.)

This is my most rambling post ever; basically I want to know what you folks think about install locations, should the installer ask the user if he wants it to be portable, or just install it somewhere like C:\Tools where it won't matter. Or is there a third (or fourth, or fifth) way?

70
Developer's Corner / Double quoted command line arguments
« on: May 24, 2010, 07:03 PM »
You know how command line arguments with spaces have to be in double quotes in Windows for pretty much any program?

taskdaddy "@@Errand Go to the market"


Are the double quotes locale dependent, i.e.
taskdaddy «@@Errand Allez à la marché»


or do "English" double quotes work in every region?

The formal second person when talking to yourself is probably wrong grammatically, but you get the idea.






Pages: prev1 ... 9 10 11 12 13 [14] 15 16next
Go to full version