From: "Fritz Code" <codefritz@googlemail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez new website and graphics of its architecture
Date: Mon, 21 Jul 2008 08:43:59 +0200 [thread overview]
Message-ID: <3e9cdced0807202343n15a02109s23a86a4b22a5a129@mail.gmail.com> (raw)
In-Reply-To: <CE293552-DDEC-457D-849E-D77B7E0DA127@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1864 bytes --]
oh right I was confusing it with the wiki. But there's is now link from the
official page to the wiki so its hard to find the wiki.
Marcel, it sounds interesting to take part in the open source development by
supporting you with documentation. And at the same
time this is a good opportunity to get familiar with the bluez stack, but I
think I wont find the time at the moment to achieve that in a professional
level.
Fritz.
PS Concerning my original question to find a good linux tool for creating
diagrams, structure charts in order to visualize sources I found "Dia".
http://www.gnome.org/projects/dia/
Its more intuitive to handle than Xfig and has a lot of, so called shapes to
satisfy the needs of creating many different types of charts and diagrams.
On Fri, Jul 18, 2008 at 4:57 PM, Johan Hedberg <johan.hedberg@gmail.com>
wrote:
> Hi,
>
> On Jul 18, 2008, at 16:18, Fritz Code wrote:
> > E.g. Im missing these nice graphics of the architecture which
> > present on overview of the whole project
> > as a big picture. E.g. they visualized the dbus interfaces etc.
>
> Are you sure you aren't confusing between wiki.bluez.org and www.bluez.org
> ? AFAIK www.bluez.org has never had any diagrams of the D-Bus
> interfaces while wiki.bluez.org does have them.
>
> Johan
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
--
Regards,
--Codefritz
[-- Attachment #1.2: Type: text/html, Size: 2873 bytes --]
[-- Attachment #2: Type: text/plain, Size: 363 bytes --]
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-07-21 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 13:18 [Bluez-users] bluez new website and graphics of its architecture Fritz Code
2008-07-18 13:27 ` Marcel Holtmann
2008-07-18 14:57 ` Johan Hedberg
2008-07-21 6:43 ` Fritz Code [this message]
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=3e9cdced0807202343n15a02109s23a86a4b22a5a129@mail.gmail.com \
--to=codefritz@googlemail.com \
--cc=bluez-users@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox