[GSOC-2014] Newbie mode!

[Manasij Mukherjee]

On Mon, Mar 3, 2014 at 5:16 AM, Aleix Pol <aleixpol at kde.org> wrote:
>
>
> Maybe a question to ask yourself is why is it needed at all to use this at
> all. Maybe it should be easier to create a new project? What would you fix
> in the process?
>
> Aleix
>
Well, the first time I used kdevelop or eclipse-cdt or any large IDE, it
seemed counter-intuitive that when I'm not working on something which has
elaborate makefiles, it was rather difficult to just open a .cpp file,
build and run it.
I can't imagine any conflict with build systems to allow this.

Creating a new project is what I originally had in mind.
I will try to come up with some working code within this year and link it
here as proof of concept.
Would it be feasible to use some components that make kdevelop for this?
(..say kdevplatform ?)




On Mon, Mar 3, 2014 at 5:29 AM, Sven Brauch <svenbrauch at googlemail.com>wrote:

> This sounds a bit like you want to build a GUI-driven build system;
> something KDevelop does explicitly not do currently.
>
Why?

> Maybe the aim you want to achieve -- making it easier for new users to do
> simple things regarding the build system -- could better be achieved by
> integrating related features into cmake support?
>
Yes, that's what I had in mind.
(Generating plain Makefiles actually, but close enough)


On Mon, Mar 3, 2014 at 5:16 AM, Aleix Pol <aleixpol at kde.org> wrote:

> On Sun, Mar 2, 2014 at 1:33 PM, Manasij Mukherjee <manasij7479 at gmail.com>wrote:
>
>> Hi everyone,
>> I'm a student looking forward to participate in Google's Summer of Code
>> this year.
>> I have used kdevelop for a long time and it'll be great to contribute to
>> something I regularly use.
>> The title "Newbie mode" is a catchy one, by let me explain the idea in
>> detail.
>> A feature in kdevelop I like is the support for external scripts.
>> I use the quick compile script when not working on a project and just
>> need to test out a snippet. (for example, code copied from a pastebin link.)
>> I want this to be more integrated into the IDE.
>> (Consider things like clickable options to enable C++11, add libraries,
>> configure warnings, etc)
>>
>> Another feature that may be possible is more static analysis.
>> (I'm not sure how well clang works with kdevelop now, but I've seen
>> screenshots of  xcode providing great hints)
>> However this may be beyond my scope for now.
>> But I promise to try working on it if the original idea succeeds.
>>
>>
>> I want to know if it is feasible and whether anyone wants to mentor me
>> with this.
>> (As for my skill level, I am well versed in standard C++ but will need
>> some help with Qt.
>> Here is a link to my github profile:
>> https://github.com/manasij7479/  )
>> Manasij Mukherjee
>>
>> _______________________________________________
>> KDevelop-devel mailing list
>> KDevelop-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/kdevelop-devel
>>
>>
> Hi Manasij,
> I like that you're considering KDE and KDevelop as your summer stage. I'd
> recommend you to mature more your idea. I'm not very fond of having
> features targeting newbies, I would prefer simplify spots on the IDE
> overall than dumbing down some of it.
>
> Maybe a question to ask yourself is why is it needed at all to use this at
> all. Maybe it should be easier to create a new project? What would you fix
> in the process?
>
> Aleix
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20140303/c57a73ca/attachment.html>