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

List:       quanta
Subject:    Re: [Quanta] Documentation on toolbars
From:       Eric Laffoon <sequitur () kde ! org>
Date:       2007-03-08 22:59:05
Message-ID: 200703081459.05774.sequitur () kde ! org
[Download RAW message or body]

On Thursday 08 March 2007 1:40 pm, Børge Holen wrote:
> Would't this be a LOT of buttons, each statement has its own button.
> This is similar to the very bad idea of having a complete rundown on all
> the options to insert to a stylesheet. Imagine that! And for what it's
> worth, this last one would probably be more useful.
>
> OK maby I am a little negative on this whole subject, but there has to be a
> better reason for a php specific toolbar than statements. I'm only talking
> about the statements not the debug stuff.
>
> What about some sort of pulldown with pick the statement... or even like
> this _BEAUTIFUL_ table editor. preset a complete order of whats needed
> like:
>
> if{
> }else{
> }
>
> press insert and were at it.

This is aready easily done even by users...

1) Every PHP tag in the DTEP is actually the same basic tagxml as the HTML 
tags. The only difference is that no attribute dialog is specified. You can 
edit them and create attribute dialogs like the HTML has.

2) It's also quite easy to create insertion dialogs with Kommander and then 
create an action on a toolbar to call up the dialog. Now you can do insertion 
into the document as well as complex dialog design not possible with the 
tagxml.

3) It's possible to take Kommander dialogs a step further using DCOP and 
extract information from the page. I've used this to manage PHP functions 
where it takes the line under the cursor, parses it and drops the parameter 
values into the dialog fields.

Finally all of this can easily be shared with the community with KNewStuff.

Maybe I'll make up some of these as examples and put them in the NewStuff 
respository.

Eric
>
> On the CSS editor you see how things should be done. two buttons to control
> and pulldowns appear at apropriate times.
>
> The concept of toolbars is to ease the _construction_ of web design, witch
> it already does in an outstanding way. The only tool better is Illustrator,
> but this nifty and heavyduty thing can only take care of the design.
>
> On Thursday 08 March 2007 15:48, Bèr Kessels wrote:
> > Hello,
> >
> > It migth be that my brain is fried. But I fail to understand the concept
> > of toolbars.
> >
> > What I want to achieve is the following:
> > * Whenever I open a pure PHP file (.inc, .php) most of the HTML toolbars
> > should be removed, instead, I want to show PHP specific toolbars (a debug
> > toolbar; a drupal toolbar; a clausules toolbar -if-else-case-foreach etc)
> >
> > * Whenever I open a template file (in contrary to pure PHP this is a tiny
> > bit of PHP embedded in HTML) I want to show the HTML toolbars in addition
> > to the php toolbars.
> >
> > Can anyone explain me how to achieve this, without abusing projects (I
> > have hundreds of projects) but by setting toolbars to load on the type of
> > file and/or the extension?
> >
> > Bèr

-- 
Eric Laffoon - Quanta+ Team Leader 
http://quanta.kdewebdev.org
_______________________________________________
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]