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

List:       quanta
Subject:    Re: [Quanta] Future of Quanta
From:       Alan C Whiteman <acwhiteman () visualis ! us>
Date:       2012-01-01 18:01:55
Message-ID: 4F009F93.6020600 () visualis ! us
[Download RAW message or body]

On 01/01/2012 04:00 AM, quanta-request@postbox.kde.org wrote:
> Send Quanta mailing list submissions to
> 	quanta@mail.kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mail.kde.org/mailman/listinfo/quanta
> or, via email, send a message with subject or body 'help' to
> 	quanta-request@mail.kde.org
>
> You can reach the person managing the list at
> 	quanta-owner@mail.kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Quanta digest..."
>
>
> Today's Topics:
>
>     1.  Future of Quanta (Dr. Robert Marmorstein)
>     2. Re: KDevelop vs Aptana3 (Brandon Sussman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 31 Dec 2011 14:17:06 -0500 (EST)
> From: "Dr. Robert Marmorstein"<robert@narnia.homeunix.com>
> To: Quanta users list<quanta@mail.kde.org>
> Subject: [Quanta]  Future of Quanta
> Message-ID:
> 	<alpine.LNX.2.02.1112311344360.25993@hyaline.narnia.homeunix.com>
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
>
> Given the thread about alternatives to Quanta, I wanted to talk to open up
> a discussion about moving Quanta forward.

I'm afraid that this may not be a realistic endeavor to undertake. See 
below...

>
> As I understand it, Quanta is essentially being maintained now by Milian
> Wolff who is involved in many other KDE projects and is a pretty busy guy.
> That means that the project is badly in need of developers to help him out
> and get things back on track.  Even if you have no programming experience,
> there are many ways you can contribute (creating templates, testing,
> writing documentation, submitting bug reports), but the project definitely
> needs more people who can update the C++ code.
>
> The decision to switch Quanta 4 to a think skin on top of kdevplatform had
> some interesting consequences for the GUI layout.  It's essentially now an
> entirely different program from Quanta3.  I've tried to submit some
> patches that make it more usable for my HTML design workflow, but I've had
> difficulty understanding the differences between a "file template" and a
> "project template" in the new Quanta.
>
> I also looked into porting Quanta 3 directly to Qt4 and KDE4 (under a new
> name), but it relies heavily on several GUI classes that were removed from
> Qt4 and have no direct equivalents.  I will continue this effort, simply
> because I think it's worthwhile just to have an alternative stream of
> development, but I'd also like to help push the ball down the road further
> on the new Quanta.
>
> I have very limited time (I have a day job and also contribute to KOffice
> and a few other tools),

... and that's why.

Successfully carrying a project like Q+ requires a community of 
developers: A cohesive group that has well defined goals for the project 
and are dedicated to its success. One developer, or two, with a day job 
will find it impossible to race against a well formed community to 
complete features and reach milestones.

I'm a web designer, not a programmer. I have to dedicate my time to 
creating websites for clients, and therefore I'm afraid that there isn't 
much of value that I can contribute to Q+.

I think the only other person, besides yourself, keeping Q+ alive is 
Milian Wolf. And his primary interest is advancing Kdevelop (I may be 
wrong here.)

> but I'd like to ask the current Quanta developers
> to take a few minutes and post a list of tasks where they could most use
> help.  I figure there are probably enough on this list with SOME
> programming experience (even if only in PHP) that we can help get
> development kickstarted again.

No question that we all loved Q+, but in the mundane necessities of 
everyday work, most of us need a solution that evolves with modern 
requirements. While I may continue to fire up Q+ for old projects, 
Aptana will have to be the IDE of choice for everything else.

I applaud your efforts to keep Q+ alive. Perhaps a better route would be 
for you to contribute your talents to the Kdevelop community and make 
Kdevelop a Q+ replacement, with HTML5 and CSS3 support.

Regards.

>
> Thanks!
>
> Robert
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 31 Dec 2011 14:47:43 -0600
> From: Brandon Sussman<brandon@wrweb.net>
> To:<quanta@postbox.kde.org>
> Subject: Re: [Quanta] KDevelop vs Aptana3
> Message-ID:<38f9219becbd57416239afee59b601f8@wrweb.net>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> On 31.12.2011 11:24, Alan C Whiteman wrote:
>
>> Because Aptana tries to be a universal IDE for programming code,
>> scripting, and mark up, it has a somewhat more complex interface than
>> QP. So there's some learning to do, some adjustments, and some
>> annoyances (for instance, Aptana will not save your file when
>> uploading; you need to save, then upload.)
> It warns/saves 'em for me...  Proves your next point :)
>
>    But once you get it
>> configured to your own working habits, it is quite good. The
>> application has an astonishing flexibility to be configured in just
>> about any way.
>>
>> In addition, documentation and community support for Aptana is very
>> extensive.
> I miss Q+ but am grudgingly getting used to Aptana.  Since I am using a
> build discipline now for at least some work (html5boilerplate), the
> timing, switching to Aptana seems right.


["acwhiteman.vcf" (text/x-vcard)]

_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta


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