[Ktechlab-devel] Porting to Qt 4 --> I'd like to help

[Richard Rondu]

On Mon, Feb 9, 2009 at 4:02 PM, Julian Bäume <julian at svg4all.de> wrote:
> On Monday 09 February 2009 16:35:48 P Zoltan wrote:
>> On Sun, 08 Feb 2009 22:11:41 +0100, Julian Bäume <julian at svg4all.de> wrote:
>> >> The idea of integrating it with kdevelop to a greater extent is
>> >> interesting and has a great deal of potential... (wonder if you could
>> >> flowpart a C program or something. =P)
>> >
>> > It won't integrate directly into kdevelop, just use some of their
>> > infrastructure. But basically your right, of course.
>>
>>   Does this mean that besides kdelibs, kdevelop will also be a dependency
>> of ktechlab? That won't make non-kde users happy.
> Nope, not KDevelop. It would be KDevPlatform, which is a quite small lib used
> by programms that provide IDE-like functionality. I'm not sure, if it's really
> needed, or we should ship the needed parts from the lib ourselfes. I'm playing
> around with it to find out.
>
>> >> But it is good dicipline to keep to the smallest number of incremental
>> >> changes at a time, even if the intermediate results aren't optimal.
>> >
>> > True, but hard to manage if each change you need to do is a quite large
>> > step
>> > in the project.
>>
>>   Base on what I've seen in the code, I prefer a rewrite. (an the KDE guy
>> also did the same :)) ). But first, we need a _design_, instead of
>> starting coding directly.
> +1 ;)

+1
>
>> >> Right now the tree is frozen for release. I'm not sure what the best
>> >> practices are with SVN, but I hope the SVN administrator will create a
>> >> 0.4 fork as soon as possible so that the multitude of efforts at the 4.x
>> >> port can be integrated and testing can begin.
>> > There already is a branch in SVN containing the next stable release.
>>   Since the release-candidate version is branched separately, we could mess
>> up the trunk, right? :D
> Before we do that, I suggest to create another branch for a new feature
> release for the KDE3 version. This should be 0.4 and the last larger
> development branch for KDE3. ATM trunk is tagged as 0.4, so it would only mean
> to copy/move the trunk.
>
>>   My opinion is that we should start a new "trunk" for the kde4 port from
>> zero, and when it reaches the level of functionalty of the 0.3 versions,
>> that should become the new trunk version.
> We can do that, also this would mean, that trunk will be unuseable for some
> time. But well, this will IMHO push the development of a KDE4 version.
>
> bye then
> julian
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code to
> build responsive, highly engaging applications that combine the power of local
> resources and data with the reach of the web. Download the Adobe AIR SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Ktechlab-devel mailing list
> Ktechlab-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
>