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

List:       quanta-devel
Subject:    Re: [quanta-devel] new template ideas
From:       "Samir M. Nassar" <quanta () steamedpenguin ! com>
Date:       2005-12-21 15:58:50
Message-ID: 200512211004.19984.quanta () steamedpenguin ! com
[Download RAW message or body]

On Wednesday 21 December 2005 09:07, Andras Mantia wrote:

> Until know we always suggested to use a scripting language (PHP) for
> such kind of templates. But people were demanding this kind of template
> support. ;-)

My understanding is that as a Project Quanta needs more developers. That there 
is a backlog of work to be done. In that environment is it prudent to be 
adding stuff to Quanta whose maintenance is going to add more work?

> What we want know will be an addition and you will not be forced to use
> it.

I know that.

> And we discussed to be able to merge the templates permanently, so
> instead of the above you will get the template. Or make it
> configurable, so when you insert a template you could:
> - add a mergepoint
> - merge permanently
> - add a mergepoint  in a scripting language.

Ok, I get this. My issue with this is the mechanism. One can always embed a 
simple scripting language into Quanta and have that do the work. Or a 
PHP/Perl/Python interpreter and basically bypass the need for a local 
webserver.

The question is: should this be a function that Quanta takes over?

As a user my answer to this is: I hope that other bugs get fixed before this 
gets added to Quanta.

> > It could turn out like VPL though. A subset of Quanta that is a great
> > idea but because a lot of Quanta users are advanced beyond those
> > features don't get as much testing or debugging. Especially when you
> > can do templating with PHP, Perl, Python, or other languages.
>
> Exactly.

Yes, but that is an issue that ought to be addressed. How many features do you 
intend to bring into Quanta Plus only to have them not be properly 
debugged/supported?

Let me not just be the grinch of christmas though. Templating within the 
editor would rock.

I just filed bug#118805 which gave me and idea.

If one stored text snippets in the templates directory how about being able to 
drag and drop them into Quanta?

In the project sidebar you drag and drop a file into the editor pane and it 
creates an anchor ( <a href="../../../COPYING"></a> ) or ( <img 
src="../../../images/S.png" width="32" height="32" border="0" /> ) based on 
the file type. That's a pretty slick mechanism.

What about if you could drag and drop template, or Objects as Jens calls them, 
into the editor pane and have their content show up there?

Couple that with showing a portion of the template on hovering over the 
template name in the template sidebar this would make for easy templating for 
web developers. Drag and Drop web development. Screw WYSIWYG.

I don't want to drag this out infinitely. If the decision has already been 
made then c'est la vie. If input can still be given then please put a lot of 
thought into how you want to do this. Repeating the VPL problem just adds to 
your and your users headaches.

-- 
Samir M. Nassar
SteamedPenguin - http://steamedpenguin.com/
_______________________________________________
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]