From: "Timo Müller" <mail@timomueller.eu>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Timo Mueller <timo.mueller@bmw-carit.de>
Subject: Re: [RFC 0/8] Integrate yocto documentation into eclipse
Date: Fri, 20 Jul 2012 08:41:19 +0200 [thread overview]
Message-ID: <5008FD8F.6090706@timomueller.eu> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A4408B@ORSMSX101.amr.corp.intel.com>
Hi,
Rifenbark, Scott M wrote, On 19.07.2012 16:39:
> Very nice... thanks
>
> -----Original Message-----
> From: Timo Müller [mailto:mail@timomueller.eu]
> Sent: Wednesday, July 18, 2012 11:57 PM
> To: Rifenbark, Scott M
> Cc: yocto@yoctoproject.org; Timo Mueller
> Subject: Re: [yocto] [RFC 0/8] Integrate yocto documentation into eclipse
>
> Hi,
>
> Rifenbark, Scott M wrote, On 18.07.2012 17:03:
>> Hi,
>>
>> This seems like a very cool idea. What about when things change
> > structurally for the Yocto Docs? For example, right now I am
> > restructuring much of the Eclipse information that is in the ADT
> > manual to move it to the development manual as part of an application
> > development flow. It looks like your patch here includes the ADT
> > manual and the Quick Start. The changes I am working on will
> > eventually require the YP development manual as well.
>
> I wanted to make sure that it is possible to generate eclipse help from
> the documentation and integrate it into eclipse. Starting with the
> development manual and the quick start guide was the obvious choice.
> But, as I didn't encounter any problems using the docbook eclipse
> stylesheet on the documentation, I suspect that integrating the other
> documents is also possible.
> I will give it a try and let you know about the results.
>
As I suspected I didn't encounter any problems generating eclipse help
documentation from all documentation parts (dev-manual, kernel-manual,
...). So it will be straight-forward and easy to add them to the eclipse
plugin as well.
>>
>> Scott
<snip>
Regards,
Timo
next prev parent reply other threads:[~2012-07-20 6:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 13:02 [RFC 0/8] Integrate yocto documentation into eclipse mail
2012-07-18 13:02 ` [RFC 1/8] plugins/sdk.doc.user: Added plugin for the yocto project documentation mail
2012-07-18 13:02 ` [RFC 2/8] plugins/sdk.doc.user: Added empty table of contents mail
2012-07-18 13:02 ` [RFC 3/8] feature/sdk.doc: Added feature containing yocto documentation plugins mail
2012-07-18 13:02 ` [RFC 4/8] feature/sdk.doc: Added org.yocto.sdk.doc.user plugin mail
2012-07-18 13:02 ` [RFC 5/8] plugins/sdk.doc.user: Added yocto quick start guide mail
2012-07-18 13:02 ` [RFC 6/8] feature/sdk: Added org.yocto.sdk.doc feature mail
2012-07-18 13:02 ` [RFC 7/8] features/sdk.site: Added eclipse help feature to update site mail
2012-07-18 13:02 ` [RFC 8/8] plugins/sdk.doc.user: Added yocto adt manual mail
2012-07-18 15:03 ` [RFC 0/8] Integrate yocto documentation into eclipse Rifenbark, Scott M
2012-07-19 6:56 ` Timo Müller
2012-07-19 14:39 ` Rifenbark, Scott M
2012-07-20 6:41 ` Timo Müller [this message]
2012-07-20 15:02 ` Rifenbark, Scott M
2012-07-18 17:36 ` Zhang, Jessica
2012-07-19 6:37 ` Timo Müller
2012-07-22 18:26 ` Zhang, Jessica
2012-07-23 15:55 ` Timo Müller
2012-07-23 23:48 ` Zhang, Jessica
2012-07-26 6:21 ` Timo Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5008FD8F.6090706@timomueller.eu \
--to=mail@timomueller.eu \
--cc=scott.m.rifenbark@intel.com \
--cc=timo.mueller@bmw-carit.de \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.