Interesting to see this thread spring up again.  Because it's been  
over a month that we've been using the new features so we have a  
little better idea how much these problems are due to needing to  
adjust to new ways, and how much they simply aren't better. The only  
thing I like more about the non-modal box is that you can resize it  
and see larger text entry fields (useful if you are replacing large  
blocks of text) and syntax coloring in the search fields, but I don't  
see why this couldn't be added to the modal version.  However these  
are pretty minor improvements and doesn't even begin to cover the loss  
of multi-file replace and no start at top feature.

I forced my self to use the new non-modal search, because I figured  
there was some big advantage to it I just wasn't seeing.  Think it's  
about time to switch back to the old way.  Or is there some advantage  
to the modal search I'm not seeing... I can't think of a single  
benefit to having search non-modal (devs must have liked something  
about it, right?).

The Make Backup Now feature is still sorely missed... I have no clue  
why they'd remove it and not have any kind of suitable replacement...  
still baffled by this one.

Why they don't bother to support Lasso still boggles my mind.

On a positive note... I like the new projects feature... makes it  
really easy to go pick up where I left off on a project (esp. after  
being pulled off it for awhile).

Greg


I've forced myself to use the modal search, because I figured I wasn't  
getting some aspect of it and that I would find some benefit to it  
after extended use.
On Oct 7, 2008, at 6:21 AM, hkrems wrote:

>
> Hi Errol, Adam and all other writers in this thread,
>
> thank you for pointing out some of the really annoying 'new features'
> in version 9.
>
> I am using BBedit as long as you do - and now it sucks. This isn't the
> first time an update made a good product less useable, putting in
> fancy features that cut down productivity instead of increasing it and
> gracefully ignoring any previously submitted bug reports or feature
> requests that were sent to them.
>
> Some examples I have not read above:
> • auto-completion isn't that helpful when trying to write text in
> english using a german keyboard. You only get the current system
> language.
>
> • why are (some of) the php functions suddenly coloured in green? The
> language module knows them, is it that complicated to paint words that
> come from the language in blue (like before) and paint words that were
> found in other sources as green? IMHO it's more important to color the
> keyword (function, constant...) in the color that has been chosen for
> that language  - and not in the color for this auto-complete-feature.
> turning off auto-completion doesn't help.
>
> • is it so difficult to check the php module to allow a php5 class
> definition using more than one interface without breaking the function
> hierarchy? since two years this is reported as bug, confirmed from
> bbedit and --- nada. ignored.
> example: class foo extends bar implements if_foo, if_bar {}
>
> • am I the only one who wants to turn off many of the languages in the
> language popup? I don't need to see the impressive list of language
> modules they have built in - choosing among the few that I use every
> day would be enough, faster, useful.
>
> • I'm certainly not the only one who wants to have an option like
> "File Path" to the filtering options of the Multi-File-Search options.
> Sometimes I have to find strings like 'require_once' in all my php
> files of a website. But I want to skip the whole 'libraries' - folder
> (where lots of foreign classes are stored in files and subfolders).
>
>> I completely and totally 100% agree with you. I love BBEdit's new
>> features. But, one thing that has made products like BBEdit,
>
> I don't love the (most of) new features. Today I'm gonna switch back
> to 8.7.2.
> The only feature that was nice was editing in the browser window.
>
>> Photoshop, etc., useful to so many people for so many years has been
>> the fact that while they do increase and improve their feature set,
>> they never forget their legacy users, who are now experts in “that
>> program”—and who are usually not willing to learn new keystrokes and
>> new ways of doing the same old thing.
>> As a UI dude, I believe that the UI should never, ever change its
>> functionality in a way that breaks the old method of operating, where
>> possible.
>
> I agree 100%.
>
>> So, while I do think that BBEdit 9 is a vast improvement, I'm hedging
>> my bets a bit. Yes, it has lost a bit of its identity to other
>> programs, but it is still (to me) vastly superior.
>>
>> I don't like the fact that the Find dialog, the thing I probably use
>> more than any other feature, consistently, now has absolutely no
>> similar keystrokes, and my productivity has dropped by about 20-45%
>> because of the delays in clicking and moving my mouse around when my
>> hands never had to leave the keyboard before.
>
> That new find dialogue was the first new feature I've switched off.
>
>> I like BBEdit, and will buy this new version. But I really do want to
>> see my keystrokes back, and I really want some of my favorite addons
>> to become available again (like automatic PHP function lookup, not
>> autocomplete!).
>
> I bought it - I'll update it - I'll try it - and I'll keep hoping that
> some day not too far from now BBedit 9 will be as good and useful as
> it was in the previous versions. Then it may wear the "It still
> doesn't suck" badge again and I'll use it for production.
>
> Harald (grumpy ol' man candidate)
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "BBEdit Talk" group.
To post to this group, send email to bbedit@googlegroups.com
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 specific feature request or would like to report a suspected (or 
confirmed) problem with the software, please email to "[EMAIL PROTECTED]" 
rather than posting to the group.
-~----------~----~----~----~------~----~------~--~---

Reply via email to