Css Outline Quickopen
Niko Sams
niko.sams at gmail.com
Mon Jan 25 17:58:02 UTC 2010
On Mon, Jan 25, 2010 at 14:15, Milian Wolff <mail at milianw.de> wrote:
> On Sunday, 24. January 2010 12:10:23 Niko Sams wrote:
>> Hi,
>>
>> In Css documents it would make sense to show Css selectors in the
>> Outline Quickopen.
>> Currently the Quickopen shows function declarations only.
>>
>> How should I implement this?
>> Create fake function declarations in Css?
>
> Yes, I'd do that. Esp. once you parse the CSS file anyways for errors, you
> should create a TopDUContext to save the status of the file, i.e. to not have
> to reparse everytime. Then adding declarations where required and you have
> nice outline.
I added a ParseJob yesterday, TopDUContext is there too.
But still, there are two options:
- create fake functions
- make DUChain and Outline Quick Open more general, So not only
functions are shown
> The question imo is more:
> What is the declaration:
>
> #someid .someclass sometag, #otherid .otherclass othertag {}
>
> - the whole selector? I.e.: "#someid .someclass sometag, #otherid .otherclass
> othertag"
> - only each whole selector, i.e.:
> "#someid .someclass sometag" and then "#otherid .otherclass othertag"
> - each use of a tag, class, this would be nice if you look for usages of a
> given ID / class...
As a first step I would take the whole selector. We can improve on
that later on.
>> And what about XML/HTML documents that could want to show a tree
>> structure in the Outline?
> [...]
> is displayed in the quickopen dialog as
> first::second::third
that sounds like a good idea.
Niko
More information about the KDevelop-devel
mailing list