Thanks for the reply Steve. Much of this is really helpful. > The gear widget at the top-right of the editor fills in "common" attributes. > You can click it, or type Command-M to populate the list with them.
The gear widget brings up another point that I've noticed that's kind of a bummer. Maybe it's just my install, but the widget doesn't remember the setting I last used for it. So, for instance, I insert an image using it, click it to insert a class or ID (which I do a lot, inserting images that become controls for jQuery events). The next time I go to insert an image, it doesn't remember that I had expanded the widget to show the additional options, which does drive me a bit nutty since 95% of the time, I want to continue using the same settings. The modal windows were at least good in that they had all the options on them (although bad in that they were modal). At a minimum, I'd love to see that widget recall its last state; ideally, it would be wonderful to be able to set the attributes that the widget shows by default (so for an img, I could set ID as always there, for instance). > I'm not 100% sure how we handle dimensions if you type the image tag. If we > are not computing the dimensions, I can see an argument for doing so. I can > also see arguments against it. My vote (if you're taking them) is that it should calculate the image sizes. It's lazy as an HTML coder to leave them out and let the browser jump content all over the place during page load. The "old" BBEdit did it using the equivalent insert method (hitting Command- Contol-I), so I don't see why the new one shouldn't (unless, of course, the user manually overrides it and enters his/her own values). > > Can I ask why you set the file type to PHP? Setting it to HTML, then letting > BBEdit figure out which parts are PHP should work. > Force of habit, I guess? I did 95% of my work until recently in PHP/ XHTML, so I set the default to PHP. A subsequent comment also points out some XHTML glitches, but I don't honestly recall having those issues. I also liked the old code highlighting better (i.e. that the PHP open tag would highlight in red with the doc mode set to PHP, made it easier to track down included files in the middle of the code). Given all of this, I guess I'll try flipping the standard doc mode to HTML, and dragging and dropping images in, and see if I can adjust to that. But keep my vote in mind if you do want to make some more changes. :-) > > When I wrote that stuff, my expectation was that people would be using > autocomplete to get the attribute names, and only using the list of items if > they were unsure what the attribute they needed was called. Does that not > work for you? > Autocomplete does work, and is a good thing, but I think it makes sense to show the full list as well when clicking on the drop-down menu. It may come down to preference. My feeling is that if the full menu will fit on the screen, I'd rather see it, rather than have to scroll it, during those inevitable "what the heck is the name of that stupid attribute that I use all the time but now for the life of me can't remember" moments (often tied to early mornings or late nights). Especially with the move to add HTML5 elements into BBEdit (which, by the way, is awesome and I love), it's really helpful for me to reinforce some of the new syntax that I'm not yet 100% familiar with yet. > There are new key equivalents, which are documented in the manual, and can be > changed in the preferences. Stupid me, so they are. I thought I'd tried every combo of Modifier Keys-G, etc but apparently not. I got spoiled by the old interface showing the key commands when you held down command, I guess. > You would be astounded how many times we had to answer the question "I chose > replace all, but only some of the strings were replaced. WTF?" > > In the new windows (I hesitate to say "new", because they've been the default > windows for several years) Replace All does what it says it will. If you need > "Replace from here to the end", there's a command on the menu for that, which > has no key assigned by default. You can add one if you like. > > I typically have "Wrap Around" enabled, and that works for my needs. > I'm more worried about Finds than Replaces with Start at Top. I've tried working with wrap around, but I just find it annoying sometimes when I'm searching for something that I know is above the insertion point (for example, the first H1 in a header of a page), when there are subsequent identical tags below it (again, more H1s). It's annoying to have to tick through the later ones until the wrap around kicks in, which is why I always loved being able to just tick Command- T. If I could put in a vote, I'd love it if Start at Top returned as an explicitly set option, but I suppose I could learn to live without it. > Because they are "windows" and not "dialogs", you can have them both open at > once. If you type "Command-F", but find you really wanted multi file search, > just type "Command-Shift-F, and the other window will appear, pre-poulated > with the settings from the first window. Or, if that's too much cognitive > load (Seriously -- I'm not making fun of anyone), simply change the Find > multiple key equivalent to Command-M. It's an extra key shortcut, which bugs me, since it was accessible in the old modal interface. I guess I don't understand what necessitated the change (something in the rewrites requiring it, or was it deemed more usable this way?), but I find it less usable. Again, I guess it's something I could learn to live with. > If you had any existing key accelerators, we went out of our way to preserve > then, and _not_ commandeer keystrokes used by the system. If you want the > system defaults, you can either manually re-apply them, or do what I did, and > "Restore Defaults" in the Menus & Shortcuts pref pane, then add back the > customizations you use. Obviously, if you have a lot of customizations, > that's a drag. In my own case, I think I added or changed about half a dozen. Thanks, very helpful. Although again, I'm not sure if it's BBEdit that's having problems with full screen, or my particular Lion install (I've noticed some general wonkery around the edges), this will at least get me out of full screen. I'll give it another go. Like I said, there are things I'd vote differently on, but I also may find in a few days that I'm totally committed to the new way of doing things. Thanks again for the help, Steve. -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
