[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quanta-devel
Subject:    Re: [quanta-devel] EBN Fixes
From:       Niko Sams <niko.sams () gmail ! com>
Date:       2009-05-22 6:23:52
Message-ID: 629542d40905212323y1e011b8dsafe91b06291af2f () mail ! gmail ! com
[Download RAW message or body]

Hi,

On Wed, May 20, 2009 at 9:22 PM, Mark A. Taff <mark@marktaff.com> wrote:
> Hi all.
>
> I think I just about have a KDE4 development environment set up again to do
> some hacking in spare time, between bouts of calculus, work, etc.
>
> I plan to start making fixes from EBN throughout the kdewebdev module, both
> because each task is small and easy to accomplish (and so fits the time
> available), and also as a way to help familiarize myself with the codebase.
If you want to waste your time with this - go ahead :D
I would however suggest more productive jobs - where you see an actual result...
I don't know your C++/Qt/KDE knowledge, but some ideas you might consider:
- HTML code completion
- CSS code completion
- hiding all build-related actions in the interface for web projects
- HTML documentation integration
- CSS documentation integration
(Speaking of Quanta only)


> I wanted to give you all this advance notice so I wouldn't step on any toes or
> screw up work in progress.
>
> Please do give me any hints, areas you want me to stay away from, areas that
> are deprecated ad shouldn't be worried about, etc.
>
> Also, should I jut make the fixes in trunk, or should I backport the fixes to
> 4.3 branch as well?
I think just trunk would be best. It's better to break stuff just in
trunk - and it's less
work for you...

Niko
_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel
[prev in list] [next in list] [prev in thread] [next in thread]