Re: Quanta4 project support progress

To add to this debate there is one thing also on my mind.

My favourite ftp client Filezilla now rins on linux. A alos like the
portablility of the xml file in the site manager.

Here's an excerpt
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<FileZilla3>
    <Servers>
        <Server>
            <Host>quanta-dev.org</Host>
            <Port>21</Port>
            <Protocol>0</Protocol>
            <Type>0</Type>
            <Logontype>1</Logontype>
            <User>ftpuser</User>
            <Pass>secret</Pass>
            <TimezoneOffset>0</TimezoneOffset>
            <PasvMode>MODE_PASSIVE</PasvMode>
            <MaximumMultipleConnections>0</MaximumMultipleConnections>
            <EncodingType>Auto</EncodingType>
            <Comments></Comments>
            <LocalDir>/home/bof/public_html/project</LocalDir>
            <RemoteDir></RemoteDir>This Servers Label
        </Server>
    </Servers>
<FileZilla3>

Neat..

Now all I need to figure out is how to import that into Quanta, Thats why I
prefer xml because a little python script would do the trick, and a menu
option


Pete

On 26/06/07, Peter Morgan <[email protected]> wrote:
>
>
>
> On 26/06/07, Andrew Lowe <[email protected]> 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:   [email protected]
> > Phone:   02 4423 8270
> > Mobile:  04 1323 8270
> > Fax:     02 4421 7760
> >
> > _______________________________________________
> > quanta-devel mailing list
> > [email protected]
> > https://mail.kde.org/mailman/listinfo/quanta-devel
> >
> >
> >
>

_______________________________________________
quanta-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/quanta-devel