Kdevelop 3.2.2 - Quickopen disabled by default in

[Richard Dale]

On Saturday 01 April 2006 01:20, Jens Dagerbo wrote:
> Hi,
>
> After debating this with Alexander off and on for the last year, we finally
> agreed on how it should be solved:
>
> http://lists.kde.org/?l=kde-commits&m=114384520707416&w=2
>
> As of that commit, KDevelop-3.4 branch interprets the Disable List of the
> relevant profile.config file as the default plugin set to load for a new
> project. All the allowed plugins are still available, but the disabled ones
> are not loaded by default.
>
> In addition, the "Set as Default" button in Project->Project
> Options->Plugins config dialog, saves the selected set as the user prefered
> default for that profile, meaning the users preference will be used for the
> next new project (of that profile).
>
> I think this is what we intended all along. :)
Well, I just built and installed the 3.4 KDevelop branch, and I now when I 
open an existing Ruby project I have absolutely every plugin enabled whether 
appropriate for Ruby or not. Does the scheme you describe above only look at 
the Ruby profile for new projects?

I've tried 'Quick Open' with Ruby, and it works fine with Ruby classes and 
methods. The only slightly ugly thing is that it calls methods, 'functions'.

-- Richard

>
> On Friday 31 March 2006 10:34, Richard Dale wrote:
> > On Friday 31 March 2006 04:07, Tim Harper wrote:
> > > On Thursday 30 March 2006 11:05, Richard Dale wrote:
> > > > Well I just thought there were way too many tabs and options enabled
> > > > by default for Ruby development - I find the default KDevelop UI is
> > > > just too cluttered and confusing. So I started removing a few things
> > > > from the Ruby profile to clean it up - possibly the wrong things! As
> > > > you found out it isn't too difficult to put the features back,
> > > > though. So I can restore the quickopen option to be included by
> > > > default for the next release of KDevelop if most people think it
> > > > should be.
> > > >
> > > > I'm also very keen to get rid of the kate cut, copy, paste, font zoom
> > > > buttons in the toolbar. I've edited my local copy of my KDevelop menu
> > > > to clear them out, and think it looks a lot better. I would have
> > > > thought it should be easy to change the code to do that, but I
> > > > haven't found out how to do it.
> > > >
> > > > -- Richard
> > >
> > > I agree with you Richard.  Its really great to cleanup the plugins that
> > > are completely useless in Ruby :)  Thanks for taking this into
> > > consideration.
> > >
> > > My favorite and most selling feature of kdevelop is the awesome go to
> > > file/method/class which works beautifully in Ruby.  It really makes it
> > > easy to jump around the code for me.  Also, I really like the file
> > > groups because when programming in rails, there are three distinct
> > > types of files, and being able to classify the three i have found quite
> > > useful (though not absolutely necessary)
> > >
> > > Is there perhaps a way to simply tell ruby on rails to disable certain
> > > plugins by default when creating a new project?  And then, allow the
> > > user to enable ones that apply to the language they are developing in? 
> > > This may be the best way to tackle this.
> >
> > I think the File Groups plugin is useful for Rails, but not for an
> > ordinary Ruby project so much. So perhaps it would be nice to have a
> > different set of plugins enabled for Rails. I certainly want to do a
> > generator wizard plugin that would only be for Rails projects, and not
> > for ordinary Ruby ones.
> >
> > I can add 'File Groups' and 'Quick Open' back to the default Ruby
> > profile, and we're still not too cluttered. I think some things in 'Quick
> > Open' looked C++ specific, which was one of the reasons I disabled it.
> >
> > -- Richard
> >
> > -
> > to unsubscribe from this list send an email to
> > kdevelop-request at kdevelop.org with the following body: unsubscribe
> > »your-email-address«
>
> -
> to unsubscribe from this list send an email to
> kdevelop-request at kdevelop.org with the following body: unsubscribe
> »your-email-address«

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«