[snip]

>>>How do you do that? Can you include other pages into a united page?
>>> 
>>>
>>>      
>>>
>>I think so.
>>    
>>
>
>Not yet, I think. So far you can only do single pages, but there seems
>to be some development on this plugin. But currently I'm moving away
>from that anyway, see my other mail.
>  
>
The WikiInclude macro handles it.  See: 
http://opensg.vrsource.org/trac/wiki/Test/IncludeMaster
for an example of it in use.

>>>>Examples, look into the doxygen example support.  May just want to 
>>>>document the examples source code using doxygen and then include those 
>>>>examples into the documentation so they can link into the reference guide.
>>>>        
>>>>
>>>Link into the ref guide or links to them from the ref guide?
>>>
>>>      
>>>
>>Links from the reference API to a possibly included page that has the 
>>source of the example.  I think doxygen supports this.
>>    
>>
>
>In a very simple manner (or a very painful one ;). For that to be useful
>we should probably add an even higher level than the SSM, to make the
>example code really minimal.
>  
>
If you think so, that would be fine.  As it stands right now I think the 
tutorials that use SSM are pretty good and that the SSM does get most of 
the internal details out of the way.

I tend to think any example should probably be coded in a way (ie. using 
tools) that you would want users to actually use in their applications.  
People are going to copy the examples as a way to start their 
applications so we might as well give them a good starting point from 
the beginning.

>>If only doxygen were multi-threaded. :)
>>    
>>
>
>I spent some time on the weekend looking into that. Profiling doxygen
>turned out to be a bigger problem than expected (valgrind segfaults...),
>and looking at the code: making that MT-safe is going to be harder than
>expected. Pretty much none of the classes can be copied, and there are
>quite a lot of global variables. :(
>  
>
You are very brave.

>>Related to this, I think we should setup a mailing list for 
>>notifications of all ticket adds and changes.  That would be much easier 
>>then visiting the tickets everyday. :)
>>    
>>
>
>Does Trac support that? I couldn't find anything. There is a patch to
>notify the owner, but how do you add a CC: to every ticket?
>  
>
Yes, I will setup trac to do it if you setup a mailing list to send the 
e-mails to.  I was thinking something like "opensg-trac-notify" or 
something like that.

>>See WikiInclude: http://trac.edgewall.org/wiki/MacroBazaar
>>    
>>
>
>Not sure how that helps. 
>
>  
>
Seee above.

>>See PageToPdfPlugin: http://trac-hacks.org/wiki/PageToPdfPlugin
>>    
>>
>
>That's just for a single page, though.
>  
>
Unless you use the WikiInclude macro to pull all the pages together.  
Then use the pdf plugin on that unified page.  (see above)

-Allen

>Yours
>
>       Dirk
>
>
>
>-------------------------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Opensg-users mailing list
>Opensg-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/opensg-users
>
>  
>


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to