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

List:       quanta-devel
Subject:    Re: [quanta-devel] CSS ideas
From:       Paulo Moura Guedes <moura () kdewebdev ! org>
Date:       2005-04-27 15:08:28
Message-ID: 200504271608.28506.moura () kdewebdev ! org
[Download RAW message or body]

On Wednesday 27 April 2005 02:09, Jens Herden wrote:
> > I'm thinking of improving the CSS support in Quanta a little:
>
> Yes, Quanta definitely needs attention there.
>
> > 1. Preview of CSS documents. The user would be asked to choose the
> > HTML/XML file to show against the current CSS doc. We also could supply a
> > default example file (based on the CSS) when no HTML document is chosen.
>
> I would say the best preview would be the file I am working with but an
> option to show something else is good.

I don't understand. You are working with the CSS file, what do you mean?

> My dreamed CSS editor will be in a toolview and you will see the results
> directly in the main editor area, either in code or in a KHTML part.

You mean a splited view with the CSS code and a html preview? It's not very 
clear to me what a toolview is, sorry :)
>
> > 2. Provide the option of linking a CSS doc to several HTML files. This
> > should be project oriented.
>
> I don't get this? You mean during editing of an CSS file you want to assign
> it to an HTML and they should be automaticly linked in the head section? 

Yes, you make a CSS to apply in at least one file. If this can be more 
automated, the better.

> If 
> you really want this be carefull because order is important. If you link
> two or more CSS files you can get different results if they are in
> different order! This makes it complicated because you will have to be able
> to define the position in the HTML file. I do not know if it worse to make
> this.

We simply wouldn't allow importing more than one stylesheet and could hava a 
checkbox to doesn't change files that already link to some CSS. 
I think that as you are so aware of details you find concerns in everything 
but one have to be optimistic and creative in order to implement anything :)
>
> > 3. Add support for choosing between several style definitions (CSS1,
> > CSS2) including the browsers compatibility. This would allow making a
> > report of the stylesheet saying which rules would be problematic and only
> > display the available attributes within the current style definition.
>
> I do not see a need for this yet.

OK, Luciano has the same opinion and I think sooner or later the browsers will 
converge to full support.

> > 4. Add a "style editor/inspector" similar to the attribute editor when
> > editing CSS files.
> >
> > 5. Also add a style editor in HTML/XML files, updating the stylesheet
> > that the document imports and, eventually, the current style block
> > (though I don't like this idea much).
>
> I would love to have a integrated approach tag/file/linked CSS in one place
> in a toolview.
>
> > I didn't start to implement this already so you people can rant at will
> > ;)
>
> I like this kind of cooperation, thank you.

So do I, thank you for your insight.

-- 
Paulo Moura Guedes

Linux Caixa Mágica  - http://caixamagica.org
KDE Web Development - http://kdewebdev.org
_______________________________________________
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]