Location of App-Templates in KDevelop4
roberto at kdevelop.org
Thu Sep 15 10:15:06 UTC 2005
Scrive Sascha Cunz <sascha.cunz at tiscali.de>:
> Hi Roberto, hi all
> in early stages of KDevelop3 all application templates were located in a
> directory hierarchy below the appwizard part. Some time later they were moved
> below the coresponding language-part.
yeah I remember
> Where should they reside in kdevelop 4?
> Putting all application templates below a language part has the advantage,
> that moving a complete support for a language to playground/extragear could
> be easier. Also, i.e. installing no PHP-Templates if the system got no PHP
> could be posibile.
yeah that's cool :)
> Though, last year i had to change each and every template as we nuked perl.
> Damn, can anyone imagine how much you have to type into the shell when you
> have to feed each and ever cvs command with a `find -path`? :-) That was no
I know but it's not only for the apptemplates. It will happen everytime we
change something in the programming language support. We have way to many
(unmaintained) language support in out core base. I remember to pain porting
the *fortran* support when I introduced the CodeModel :-)
> Having them all together at a global repository might have more benefits:
> - working on the templates becomes easier
> - keeping track of the templates becomes easier
hmm, I'm not sure
> What about the posibility to only ship a few very basic templates with
> kdevelop itself. We could then utilize KNewHotStuff to install new templates
> or update outdated ones.
I'M ALL FOR IT! we should try to keep our code base simple. Only maintainable
code should be part of the KDevelop core distribution. The other stuff should
be *supported* by KDevelop using KHotstuff and adv on the KDevelop website
This message was sent using IMP, the Internet Messaging Program.
More information about the KDevelop-devel