View mode: basic / threaded / horizontal-split · Log in · Help
February 23, 2006
Re: Helix and CanDyDOC release
"Victor Nakoryakov" <Victor_member@pathlink.com> wrote in message 
news:dti0su$2b9i$1@digitaldaemon.com...
> Hi all.
>
> I've upload something named Helix recently. Actualy this is two projects. 
> First
> is Helix itself - applied mathematics routines library. It's small right 
> now,
> but will grow with time.
>
> The second thing is something that I hope will be intresting for biger 
> audience:
> CanDyDOC. It is a set of .ddoc, .js and other files that provides ability 
> to
> generate advanced documentation htmls.
>
> Learn more at http://trac.dsource.org/projects/helix/wiki and
> http://trac.dsource.org/projects/helix/wiki/CandyDoc
>
> There are few bugs in CanDyDOC and there are not all features I planned to 
> do
> are done. So for now CanDyDOC is my first priority. Any ideas and 
> proposals are
> welcome in project's forum.
>

Cool, Victor.
And I like word AJAX these days :)

Andrew.


> --
> Victor (aka nail) Nakoryakov
> nail-mail[at]mail.ru
>
> Krasnoznamensk, Moscow, Russi
February 23, 2006
Re: Helix and CanDyDOC release
Jari-Matti Mäkelä wrote:
> 
> 
> Maybe Walter could help here. It's pretty trivial task to do when you
> have all the symbol tables, etc. at hand when generating the
> documentation code. Otherwise you're going to end up doing a separate
> frontend for docs.
> 

Looks like it is an only simple (for us, not Walter :)) way to acomplish 
this. So it is necessary to have some implicit macro:

1) $(DDOC_LOOKUP MyFunction) should be expanded to something like 
mypackage.mymodule.MyTemplate.MyType.MyFunction.N where this path is 
full path to symbol passed as argument in current context and N is 
number of overload.

2) There should be redefinable macro $(DDOC_BACKQUOTE arg) which should 
be expanded when we enclose some expression (arg) in backuotes.

3) All types that are used in declarations should be implictly backuoted.

Realising this 3 requests will lead to our problem solving. But for now 
full-featured cross references is realy big task.

-- 
Victor (aka nail) Nakoryakov
nail-mail [at] mail.ru

Krasnoznamensk, Moscow, Russia
February 23, 2006
Re: Helix and CanDyDOC release
John Demme wrote:
> Victor Nakoryakov wrote:
> 
>>>Looks great!  Does it do class dependancy charts
>>
>>No charts yet. I think class dependancy graphs is some heritage of
>>C++/doxygen past, but module dependance charts could be useful, I'll
>>think about. Anyway there are foreground tasks, so this thing can be
>>done in versions after 1.0 release.
>>
>>
>>>and links to type
>>>definitions yet?
>>
>>Ammm... what did you mean exactly?
>>
> 
> 
> Essentially what I'm looking for is the ability to click my way around. 
> That is, say you've got the following two classes:
> 
> class A
> {
> }
> 
> class B: A
> {
>         void foo(A bar);
> }
> 
> In the documentation for class B, I want the text saying that it inherits
> from A to be a link to the documentation for A.  In the documentation for
> the method foo, I want a link to the documentation for A in the description
> of the parameter bar... doxygen does this, and it's infinitely valuable
> when looking through the Mango docs.
> 
> ~John


Aha,... See neighbour discussion branch.

-- 
Victor (aka nail) Nakoryakov
nail-mail [at] mail.ru

Krasnoznamensk, Moscow, Russia
Next ›   Last »
1 2
Top | Discussion index | About this forum | D home