project settings

Currently project-specific settings such as qmakemanager
and
makebuilder doesn't work. It shows proper widget via
kcmodule
but all the input widgets are disabled.

Does the project setting is disabled now?

Also some additional question. What is the meaning of
ProjectKCModule::setDeveloperTempFile(),
setProjectFileUrl(),
and setDeveloperFileUrl()? I guess its for remote project
but what does the namings, especially *develop* suggest?

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 25.05.07 14:14:04, dukju ahn wrote:
> Currently project-specific settings such as
qmakemanager and
> makebuilder doesn't work. It shows proper widget via
kcmodule
> but all the input widgets are disabled.

Yes I know, this is going to be fixed on monday.

> Also some additional question. What is the meaning of
> ProjectKCModule::setDeveloperTempFile(),
setProjectFileUrl(),
> and setDeveloperFileUrl()? I guess its for remote
project
> but what does the namings, especially *develop*
suggest?

This is needed to have two things:

a) remote projects
b) developer-specific settings in a separate file, so the
.kdev4 project
file can be checked into VCS.

See projectconfigskeleton for what they do, the arguments
come from the
creation of the KSettings:ialog in
projectcontrollerprivate.

Andreas

-- 
Alimony and bribes will engage a large share of your
wealth.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

2007/5/25, Andreas Pakulat <apakugmx.de>:
> On 25.05.07 14:14:04, dukju ahn wrote:
> > Also some additional question. What is the meaning
of
> > ProjectKCModule::setDeveloperTempFile(),
setProjectFileUrl(),
> > and setDeveloperFileUrl()? I guess its for remote
project
> > but what does the namings, especially *develop*
suggest?
>
> This is needed to have two things:
>
> a) remote projects
> b) developer-specific settings in a separate file, so
the .kdev4 project
> file can be checked into VCS.

So What is the meaning and difference between
developer-specific
settings and VCS checked-in settings? Do I understand
correctly below?

Suppose that certain project community decided to use
kdev4.
They use C++ as their language. Such common items reside on
kdev4
project file directly.
OTW, each developer may have difference taste on MakeBuilder
output
so such private reside in .kdev4/ subdir

Am I right?

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 25.05.07 14:40:51, dukju ahn wrote:
> 2007/5/25, Andreas Pakulat <apakugmx.de>:
> > On 25.05.07 14:14:04, dukju ahn wrote:
> > > Also some additional question. What is the
meaning of
> > > ProjectKCModule::setDeveloperTempFile(),
setProjectFileUrl(),
> > > and setDeveloperFileUrl()? I guess its for
remote project
> > > but what does the namings, especially
*develop* suggest?
> >
> > This is needed to have two things:
> >
> > a) remote projects
> > b) developer-specific settings in a separate file,
so the .kdev4 project
> > file can be checked into VCS.
> 
> So What is the meaning and difference between
developer-specific
> settings and VCS checked-in settings? Do I understand
correctly below?
> 
> Suppose that certain project community decided to use
kdev4.
> They use C++ as their language.

language doesn't matter. I know there's still a Language
setting in the
kdevelop.kdev4 file in KDevelop4 svn and maybe even in the
.kdev4 file
in the template, but languages are not set on a
project-base. Rather the
language plugins are loaded on a file-base, so if a C++ file
is opened
C++ language plugin is created, if a python file is opened
the python
support is loaded.

> Such common items reside on kdev4 project file
directly.
> OTW, each developer may have difference taste on
MakeBuilder output
> so such private reside in .kdev4/ subdir

Right, thats the idea. With our current features I think the
project
name, the project manager (i.e. cmake, qmake, custom
makefiles) and the
vcs plugin are the only items stored in the project-kdev4
file.
Everything else would go into the developer specific file.

Andreas

-- 
You single-handedly fought your way into this hopeless
mess.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Friday 25 May 2007 22:02:25 Andreas Pakulat wrote:
> Right, thats the idea. With our current features I
think the project
> name, the project manager (i.e. cmake, qmake, custom
makefiles) and the
> vcs plugin are the only items stored in the
project-kdev4 file.
> Everything else would go into the developer specific
file.
>
> Andreas

Not to forget some project teamwork-servers and such. 

greetings, David


_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Friday 25 May 2007 15:10, David Nolden wrote:
> On Friday 25 May 2007 22:02:25 Andreas Pakulat wrote:
> > Right, thats the idea. With our current features I
think the project
> > name, the project manager (i.e. cmake, qmake,
custom makefiles) and the
> > vcs plugin are the only items stored in the
project-kdev4 file.
> > Everything else would go into the developer
specific file.
> >
> > Andreas
>
> Not to forget some project teamwork-servers and such.

>
> greetings, David

teamwork servers are developer specific and will not be put
into the 
project-kdev4 file. They will be put into the
developer-specific file 
instead.
-- 
Matt

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Saturday 26 May 2007 06:10:41 Matt Rogers wrote:
> On Friday 25 May 2007 15:10, David Nolden wrote:
> teamwork servers are developer specific and will not be
put into the
> project-kdev4 file. They will be put into the
developer-specific file
> instead.

I don't mean custom added teamwork servers, I mean
project-wide ones. Those 
should go into the global file, as they are not
developer-specific. That way 
you idelly could check out an arbitrary project from svn,
open it with 
kdevelop, click "collaborate", and start
collaborating with other developers 
who work on the same project. 
That's much easier than getting the collaboration-server
from websites etc.

greetings, David


_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Saturday 26 May 2007 04:22, David Nolden wrote:
> On Saturday 26 May 2007 06:10:41 Matt Rogers wrote:
> > On Friday 25 May 2007 15:10, David Nolden wrote:
> > teamwork servers are developer specific and will
not be put into the
> > project-kdev4 file. They will be put into the
developer-specific file
> > instead.
>
> I don't mean custom added teamwork servers, I mean
project-wide ones. Those
> should go into the global file, as they are not
developer-specific. That
> way you idelly could check out an arbitrary project
from svn, open it with
> kdevelop, click "collaborate", and start
collaborating with other
> developers who work on the same project.
> That's much easier than getting the
collaboration-server from websites etc.
>
> greetings, David
>

I know what you meant. I'm not ready to commit to having
that yet though. The 
idea was to keep the project-kdev4 file as minimal as
possible in order to 
keep it sharable. So, while this is something that's
probably just fine being 
in there, my current thought at this point in time is to
just shove 
everything except for the bare necessities into the
developer specifc file, 
and then move it into the project-kdev4 file at a later
time. IIRC, this is 
perfectly do-able with our config system.
-- 
Matt

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

2007/5/25, Andreas Pakulat <apakugmx.de>:
> On 25.05.07 14:14:04, dukju ahn wrote:
> > Currently project-specific settings such as
qmakemanager and
> > makebuilder doesn't work. It shows proper widget
via kcmodule
> > but all the input widgets are disabled.
>
> Yes I know, this is going to be fixed on monday.

The project setting page widget is still disabled as before,
though
I saw some commits related with project settings.
Is setting still disabled?

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 09.06.07 05:43:52, dukju ahn wrote:
> 2007/5/25, Andreas Pakulat <apakugmx.de>:
> > On 25.05.07 14:14:04, dukju ahn wrote:
> > > Currently project-specific settings such as
qmakemanager and
> > > makebuilder doesn't work. It shows proper
widget via kcmodule
> > > but all the input widgets are disabled.
> >
> > Yes I know, this is going to be fixed on monday.
> 
> The project setting page widget is still disabled as
before, though
> I saw some commits related with project settings.
> Is setting still disabled?

I didn't yet look into why its disabled. That needs some
extra time and
at the moment I'm working on the VCS stuff. If you want to
you can have
a look.

Andreas

-- 
You are deeply attached to your friends and acquaintances.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel