[prev in list] [next in list] [prev in thread] [next in thread]
List: quanta-devel
Subject: Re: [quanta-devel] Quanta4 project support progress
From: "Peter Morgan" <pedromorgan () gmail ! com>
Date: 2007-06-25 10:31:02
Message-ID: e97636410706250331p1f3951bbm508e5c0740a7877e () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi there,recently subscribed to this list, and been looking at the source as
a Quanta user..
For this thread I have one comment, if it helps..
>>>
Now about the possibilities:
1) big file in toplevel directory: nice because everything is in one
place. Not so nice as it doesn't follow the style of other languages, thus
it is a little bit harder to load (see my mail on the KDevelop list). But
this isn't a big issue.
2) one file/directory. Fits the KDevelop's style, but means hand editing
and copying only the project file(s) a little bit harder.
<<
Option 2) - I dont like at all
Option 1) - is ok, as is at the moment...
However I would like another option, storing the project file in another
directory eg ~quanta/
Pete
On 23/06/07, Andras Mantia <amantia@kdewebdev.org> wrote:
>
> Hi,
>
> > Here it does look for test.kdev4.webprj ;-)
>
> Strange, because this happened for me while I was working, but I fixed it.
> I hope I committed the latest changes...
>
> > You are aware that you are using the project name which could also be
> > defined
> > inside of the project file? The filename is only the default but you
> could
> > get another name from inside of the project file. I am not sure if we
> want
> > this?
>
> I didn't know it. Actually we could change this and maybe we should. See
> also below.
> >
> >> The .webprj file is a Quanta3 project file. I didn't want to change the
> >> syntax of it and probably won't change until it is absolutely needed.
> >
> > OK, but we use it only to find out which files are in the project,
> right?
>
> Yes, all the other options should come from the .kdev4 file.
>
> > Unfortunately this will bind us to one project must have a common root
> > folder.
> > I remember that some people complained about this and KDevelop is moving
> > away
> > from this too.
>
> So we might discuss how we want to proceed with the project file.
> I think we agree the that project wide settings are stored in the .kdev4
> file.
> The question is how do we store which file is in the project.
> We have several possibilities:
> 1) We store the list of the files in a file in the toplevel directory as
> we do right now.
> 2) We store the list of the files in a file in each directory, similar to
> how cmake and automake does.
>
> There is also the question in what format should we store:
> 1) XML as it is now
> 2) KConfig (INI) style (I think we already started something like this in
> the past). In such case each filename would be a group, the attributes of
> the file are key-value pairs.
>
> Obviously the most easiest way was to just reuse the existing project
> file, but this isn't mandatory, as probably we need anyway an importer
> class for the old projects.
>
> Now about the possibilities:
> 1) big file in toplevel directory: nice because everything is in one
> place. Not so nice as it doesn't follow the style of other languages, thus
> it is a little bit harder to load (see my mail on the KDevelop list). But
> this isn't a big issue.
> 2) one file/directory. Fits the KDevelop's style, but means hand editing
> and copying only the project file(s) a little bit harder.
>
> Regarding the format, I have no idea which one is better/faster. XML looks
> for me more "professional" and probably would use less lines. INI style
> would mean we could store everything in the .kdev4 file.
>
> > I have one file in my project but it does not show up in the tree. But I
> > have
> > not time yet to investigate.
>
> I will check if I really committed it soon. The problem is that we had a
> storm in the morning and there is no electricity here since then. I;m at
> my parents now, so I can mail, but cannot work.
>
> Andras
>
> _______________________________________________
> quanta-devel mailing list
> quanta-devel@kde.org
> https://mail.kde.org/mailman/listinfo/quanta-devel
>
[Attachment #5 (text/html)]
Hi there,recently subscribed to this list, and been looking at the source as a Quanta \
user..<br><br>For this thread I have one comment, if it \
helps..<br><br>>>><br>Now about the possibilities:<br>1) big file in \
toplevel directory: nice because everything is in one <br>place. Not so nice as it \
doesn't follow the style of other languages, thus<br>it is a little bit harder to \
load (see my mail on the KDevelop list). But<br>this isn't a big issue.<br>2) one \
file/directory. Fits the KDevelop's style, but means hand editing <br>and copying \
only the project file(s) a little bit harder.<br><<<br><br>Option 2) - I \
dont like at all<br><br>Option 1) - is ok, as is at the \
moment...<br><br>However I would like another option, storing the project file in \
another directory eg ~quanta/ <br><br>Pete<br><br><br><br><br><div><span \
class="gmail_quote">On 23/06/07, <b class="gmail_sendername">Andras Mantia</b> <<a \
href="mailto:amantia@kdewebdev.org">amantia@kdewebdev.org</a>> \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi,<br><br>> Here it \
does look for test.kdev4.webprj ;-)<br><br>Strange, because this happened for me \
while I was working, but I fixed it.<br>I hope I committed the latest \
changes...<br><br>> You are aware that you are using the project name which could \
also be <br>> defined<br>> inside of the project file? The filename is only the \
default but you could<br>> get another name from inside of the project file. I am \
not sure if we want<br>> this?<br><br>I didn't know it. Actually we could \
change this and maybe we should. See <br>also below.<br>><br>>> The .webprj \
file is a Quanta3 project file. I didn't want to change the<br>>> syntax of \
it and probably won't change until it is absolutely needed.<br>><br>> OK, \
but we use it only to find out which files are in the project, right? <br><br>Yes, \
all the other options should come from the .kdev4 file.<br><br>> Unfortunately \
this will bind us to one project must have a common root<br>> folder.<br>> I \
remember that some people complained about this and KDevelop is moving <br>> \
away<br>> from this too.<br><br>So we might discuss how we want to proceed with \
the project file.<br>I think we agree the that project wide settings are stored in \
the .kdev4<br>file.<br>The question is how do we store which file is in the project. \
<br>We have several possibilities:<br>1) We store the list of the files in a file in \
the toplevel directory as<br>we do right now.<br>2) We store the list of the files in \
a file in each directory, similar to<br>how cmake and automake does. <br><br>There is \
also the question in what format should we store:<br>1) XML as it is now<br>2) \
KConfig (INI) style (I think we already started something like this in<br>the past). \
In such case each filename would be a group, the attributes of <br>the file are \
key-value pairs.<br><br>Obviously the most easiest way was to just reuse the existing \
project<br>file, but this isn't mandatory, as probably we need anyway an \
importer<br>class for the old projects.<br> <br>Now about the possibilities:<br>1) \
big file in toplevel directory: nice because everything is in one<br>place. Not so \
nice as it doesn't follow the style of other languages, thus<br>it is a little \
bit harder to load (see my mail on the KDevelop list). But <br>this isn't a big \
issue.<br>2) one file/directory. Fits the KDevelop's style, but means hand \
editing<br>and copying only the project file(s) a little bit harder.<br><br>Regarding \
the format, I have no idea which one is better/faster. XML looks <br>for me more \
"professional" and probably would use less lines. INI style<br>would mean \
we could store everything in the .kdev4 file.<br><br>> I have one file in my \
project but it does not show up in the tree. But I <br>> have<br>> not time yet \
to investigate.<br><br>I will check if I really committed it soon. The problem is \
that we had a<br>storm in the morning and there is no electricity here since then. \
I;m at<br>my parents now, so I can mail, but cannot work. \
<br><br>Andras<br><br>_______________________________________________<br>quanta-devel \
mailing list<br><a href="mailto:quanta-devel@kde.org">quanta-devel@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/quanta-devel"> \
https://mail.kde.org/mailman/listinfo/quanta-devel</a><br></blockquote></div><br>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic