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

List:       quanta-devel
Subject:    Re: [quanta-devel] my tool would be like this...
From:       Paulo Moura Guedes <moura () kdewebdev ! org>
Date:       2005-04-08 13:57:12
Message-ID: 200504081457.13144.moura () kdewebdev ! org
[Download RAW message or body]

On Friday 08 April 2005 06:09, Jens Herden wrote:
> > and the style would be manipulated in
> > two ways: using direct HTML or in an external (CSS) stylesheet, by
> > clicking on the tag name box.
>
> A CSS editor in a toolview would be smart. But there are unlimited
> positions for CSS information:
> 1. tag
> 2. file
> 3...n external files
>
> To make a real good CSS editor is a challenge I guess.

I think it's impossible to consider all this options. We should restrict to 
edit in external files. It's the responsibility of the user to make sure 
there's nothing overriding the external CSS file settings. I think it's the 
only way to go.

> > I don't know if it's feasible to show the style of inline text nodes and
> > the arrangement of elements after been processed by CSS, at least I don't
> > know how. Displaying just plain text would be enough (what about
> > images...)? BTW, how to implement this? :) Maybe we need to have our own
> > canvas where we would draw the block node structure and insert KHTML
> > render fragments inside the block nodes scope (in case we didn't have
> > just plain text)? This is a little crazy I know :)
>
> I also was thinking about using KHTML to render the textboxes too. Reading
> you text lets me think if we could switch between preview mode (KHTML) and
> edit mode. Edit mode would be text only and additional indicators for the
> tags.

I like that.

> Images are inline elements so we have to show them somehow, maybe just as
> thumbnail or an icon with tooltip that shows the image? And a doubleclick
> could open a dialog with the original size and ways to change the
> attributes. But the size can also be in CSS and I don't know if it is a
> good idea to offer a way to resize an image and adjust the CSS accordingly?

We could have a checkbox asking wether the changes should be written in CSS or 
HTML.

> > So, this approach has the advantage of easy manipulating the structure
> > and having a more intuitive display, but at the same time is difficult to
> > imagine how the document will display. It would be a complement view, as
> > we also need things like dragging absolute positioned div elements and
> > resizing images.
>
> As I wrote, I do not see the need for being close to the result. Just hit
> F6 and you know. Or let us make a live preview in a toolview that can be
> seen during editing.

It's a little like latex editors isn't it?

> > I would say this is kind of a merge between the kafka part and the
> > document structure. It's hard for me as a user to imagine how good such a
> > tool could be but I would like to further discuss this ideas. I think
> > we're heading in the right way and will take good conclusions out of all
> > this.
>
> Sure it is different from VPL and I think this is something we can
> implement when we made the switch to KDevelop framework.

When this move are expected do you know?

> I would like to 
> see many different plugins that all together create the functionality of
> the current Quanta. So adding a new edit mode would be writing a new plugin
> and the users have the choice what to use.

So this should only be started then.

Good work Jens, this is an excellent idea!

BTW, I'm studying the chance of adding MathML support in Quanta. It seems that 
KHTML supports it. I didn't start to think about this in depth yet but I 
though maybe you people have something to say :)
-- 
Paulo Moura Guedes

http://caixamagica.org
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] 

Configure | About | News | Add a list | Sponsored by KoreLogic