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

List:       kdevelop-devel
Subject:    Relative URLs in KDevelop interfaces
From:       Alexander Dymo <cloudtemple () mksat ! net>
Date:       2004-01-14 22:38:28
Message-ID: 200401150038.29003.cloudtemple () mksat ! net
[Download RAW message or body]

KDevelop is very close to the release and I'm starting to think about
the future:)
Looking at our kdevproject and other interfaces I've remembered about
our TODO item which says about introducing KURLs everywhere in
kdevelop source and interfaces when it comes to handling files.
KURL's are good, but project managers can not effectivelly work
with them (I've tried and failed). So I set down and wrote a small
convenience library to handle relative urls to files and directories
which I'm happy to introduce. 

The library introduces four classes:
Relative::Name - only the name in form dir/file.ext or dir/
Relative::URL - class which holds not only the relative name
but also a "base". For example, consider base as projectDirectory()
and name as subproject1/file.ext or subproject1/.
Relative::File - the same as Relative::URL but works with files only
Relative::Directory - the same as Relative::URL but works with dirs only

I propose to use the classes from
this library in our kdevproject interfaces - replace QString fileName
by Relative::URL (or Relative::Name or Relative::File) fileName.
I'm not sure which will fit.
Awaiting for comments.

-- 
Alexander Dymo
Ukrainian State Maritime Technical University, IT Department



["rurl_lib.tar.bz2" (application/x-tbz)]
_______________________________________________
Kdevelop-devel mailing list
Kdevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel

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