To-Do List Plugin

[Aviv -]

Thanks for your reply.
I'll start implementing your notes on the weekend.

Aviv

On Tue, Oct 6, 2009 at 5:27 PM, Milian Wolff <mail at milianw.de> wrote:

> On Friday, 2. October 2009 13:37:48 Aviv wrote:
> > Hello,
> >
> > I'm Aviv and I'm new to KDevelop development.
> >
> > To start understanding how things work, I developed the attached plugin,
> > which adds a to-list for each project, and saves the changes in the
> > project file.
> >
> > I'd appreciate your feedbacks!
>
> So, finally got around to test it.
>
> 1) You CMakeLists.txt needs the following stuff prepended so you can
> properly
> build it from outside kdevplatform:
>
> project(todolist)
>
> find_package(KDE4 REQUIRED)
>
> find_package(KDevPlatform REQUIRED)
>
> include_directories(
>    ${KDEVPLATFORM_INCLUDE_DIR}
>    ${KDE4_INCLUDES}
>    ${CMAKE_CURRENT_BINARY_DIR}
>    ${CMAKE_CURRENT_SOURCE_DIR}
> )
>
> add_definitions( -DKDE_DEFAULT_DEBUG_AREA=9532 )
> ...
>
> The project is optional though afaik good practice.
>
> 2) Remove the value from exec= in your .desktop file, setting it to blablub
> is
> just not correct (though doesn't hurt either) ;-)
>
> 3) The interface can need a bit of work:
> - make the list not too wide, I have a horiz. scroll bar
> - when selecting an entry and hitting DEL I'd expect the entry to get
> deleted,
> not only it's contents
> - context menu (new/delete/set status...)
> - filter by status, maybe even search in todo?
> - toggling the status by clicking is imo not so nice, maybe just show a
> little
> tooltip with all available stati and let the user select one
> - I cannot set the status of the new entry
> - new entry always at the top? or with context menu / button so I don't
> have
> to scroll to bottom for a new entry
> - sort by status / severity?
>
> 4) Some advanced features I'd personally like to see:
> - show TODO from inside the source (we had that already at some point,
> didn't
> we?), maybe create some kind of framework, similar to the problem reporter:
> That way we can add TODO's from inside the language plugin (since that one
> already parses the files and can report TODOs when it comes across e.g.
> #warning or ///TODO stuff). Though maybe we can/should just use the problem
> reporter for this, and let the TODO stuff be user-input only? dunno
> - let me click URLs in the TODO, that way I can e.g. insert bug-urls, or
> pastebins
> - let me insert newlines for longer TODOs
>
> But a good start for now :) Thanks, welcome to KDevelop'ing!
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20091007/498731ff/attachment.html>