[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-26 16:30:05
Message-ID: e97636410706260930n5af5bbfflee067dcaf754ea3c () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 26/06/07, Andrew Lowe <andrew.lowe@manildra.com.au> wrote:
>
> On Mon, 25 Jun 2007 20:31:02 Peter Morgan wrote:
> > 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
> >
>
> With Quanta there is a significant difference than KDevelop for projects:
> Quanta projects are generally published as source (HTML, PHP, etc) whereas
> KDevelop projects are generally compiled.
> Most Quanta users would probably copy the whole project directory onto
> their
> webserver. If we go for option 2, users would have difficulty removing
> all
> project files prior to publishing - unless we have a publish option...
> Project files could potentially contain sensitive information (fish
> user/passwords?, or include files not for display by the webserver.)
>
> I am sure many users currently publish the whole directory, but some might
> remove the project file, and other sensitive files, before uploading. If
> we
> have many files, it would make it very hard for a user to manually remove
> files prior to publishing.
That's part of the problem. In which case might it be an idea to make the
project files .hidden ? THese can then be excluded from the project for
upload
Just my thoughts
>
> --
> Andrew Lowe
> System Administrator & Programmer
> Information Technology
> Manildra Group
>
> Email: andrew.lowe@manildra.com.au
> Phone: 02 4423 8270
> Mobile: 04 1323 8270
> Fax: 02 4421 7760
>
> _______________________________________________
> quanta-devel mailing list
> quanta-devel@kde.org
> https://mail.kde.org/mailman/listinfo/quanta-devel
>
>
>
[Attachment #5 (text/html)]
<br><br><div><span class="gmail_quote">On 26/06/07, <b \
class="gmail_sendername">Andrew Lowe</b> <<a \
href="mailto:andrew.lowe@manildra.com.au">andrew.lowe@manildra.com.au</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;"> On Mon, 25 Jun 2007 \
20:31:02 Peter Morgan wrote:<br>> Hi there,recently subscribed to this list, and \
been looking at the source<br>> 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<br>> directory eg \
~quanta/ <br>><br>> Pete<br>><br><br>With Quanta there is a significant \
difference than KDevelop for projects:<br>Quanta projects are generally published as \
source (HTML, PHP, etc) whereas<br>KDevelop projects are generally compiled. <br>Most \
Quanta users would probably copy the whole project directory onto \
their<br>webserver. If we go for option 2, users would have difficulty \
removing all<br>project files prior to publishing - unless we have a publish \
option... <br>Project files could potentially contain sensitive information \
(fish<br>user/passwords?, or include files not for display by the \
webserver.)<br><br>I am sure many users currently publish the whole directory, but \
some might <br>remove the project file, and other sensitive files, before \
uploading. If we<br>have many files, it would make it very hard for a user \
to manually remove<br>files prior to publishing.</blockquote><div><br>That's part \
of the problem. In which case might it be an idea to make the project files .hidden ? \
THese can then be excluded from the project for upload \
<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid \
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Just my \
thoughts<br><br>--<br>Andrew Lowe<br> System Administrator \
& Programmer <br> Information \
Technology<br> Manildra \
Group<br><br>Email: <a \
href="mailto:andrew.lowe@manildra.com.au">andrew.lowe@manildra.com.au</a><br>Phone: \
02 4423 8270<br>Mobile: 04 1323 8270<br>Fax: 02 \
4421 7760 <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><br><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