Christian Lohmaier wrote:
Hi Bernd, *,
Hi Christian,
But again: There is no page for the UDK or the URE yet. So adding a link
to "nowhere" or a developer-page doesn't make sense.
You (well, I at least) surely don't want to point people from the front
page to http://udk.openoffice.org/ for example
Well as long as we don´t have something better I indeed would want to
point people from the front page to http://udk.openoffice.org.
Something better to point to would be nicer of course.
[...]
We want others to develop and offer extensions for OpenOffice.org and we
do also want to allow that technology to spread into other software.
Basically what´s being asked here for is to get those bricks which are
our "second product" on the main-page. Can we do that please?
Show me a page that is "attractive" enough to be linked... That has some
marketing bla introduction to quickly tell the visitor what that thing
is about...
http://udk.openoffice.org is all we currently have. It may not seem very
attractive. But that we currently don´t have something more attractive
doesn´t mean that we shouldn´t start to create it and doesn´t mean we
shouldn´t show what we have.
,----
| UNO (Universal Network Objects) is the interface-based component model
| of OpenOffice.org. UNO offers interoperability between different
| programming languages, different object models, different machine
| architectures and different processes; either in a local network or even
| via the Internet. UNO components can be implemented in and accessed from
| any programming language for which a UNO language binding exists.
`----
Is far less attractive than starting with "The bricks to build your
application" or something.
Depends on matter of taste (you know not everybody likes the same type
of girl) as a techie terms like "component model", "interoperability"
and "any programming language" DO sound quite sexy to me.
As in your words: You want to "sell" something. In these days, if you
want to sell something to somebody, that things must be shiny/sexy.
Right! Any volunters around to get new clothes and a little bit of
makeup for that web page ;-) ?
Text only pages with a hell lot of links aren't attractive or sexy.
[...]
The think is people don´t even know about the "second product". And why
not => because it´s not present on the main page.
I don't think so. Sure, people don't know about it. But (most) are not
even interested....
And that´s just the thing we want to change. That´s all that marketing
is about getting people interested in things isn´t it?
[...]
Basically the "second product" to download is here:
http://api.openoffice.org/SDK/index.html
See - already spread across → One needs an overview page... (clear paths
to the target-pages)
Well, to be precise SDK and UDK are two seperate things with the later
being part of the former. And yes I do agree we need an overview page
clearifing technical terms and presenting sexy products.
That´s probably because you´ve probably never had the need to enhance
documents with Basic Macros or tried to enhance them using other
programming languages or wanted to offer extensions for OpenOffice.org
but maybe it could also be that you didn´t know that you could do that
because we do have a lack of "marketing" for our "second product".
Honestly: For using that second product, one needs to read quite a but
of information and has to be a good understanding of the whole concept.
Understanding this is not easy at all.
Yep, that´s why we need some markting and documentation people to talk
with development people about how to make it easier.
[...]
1.) Developers ( OpenSource as well as commercial ISVs ) which do want
to create extensions.
Those are been served once extensions.openoffice.org is ready. Having a
link like "Create your own extension" makes more sense there... (and
linking to extensions.ooo from the frontpage makes more sense than
linking to the devel-pages directly).
+1
I am all for such an "Create your own extension" link.
But this would not address potential customers/developers which we might
get interested into using UNO for their own not OpenOffice.org related
software.
So somewhere we still need http://udk.openoffice.org or (well) something
more sexy about UNO.
OOo is not only for geeks. It is a professional application. That's an
important part of "the message"...
Right it´s a professional application. But it´s also this much
professional enough that it makes sense for professional software
vendors and well geeks also of course :-P to find ways to integrate
their solutions with it or to create extensions for it (some already do
this). Those must also be capable to find the information they need.
Again: Chicken and egg problem. If there is nothing to point to, there
will be no link.
http://udk.openoffice.org
Let´s just start by showing the things we currently have and than try to
make them more sexy.
As Kay said part of the success of a competitors product is a wide range
of available extensions for it. To be able to compete we should more
agressivley market our "second product" which is the enabler for the
future availibility of more OpenOffice.org extensions. Availibilty of
specialized extensions is a benefit to OOo end-users.
You won't successfully present the second product by its technical
merits, but only by the products created with it.
As Kay pointed out in one of the previous mails we already know about
people using UNO just because of technical merits compared to competing
technology. It DOES have value on it´s own.
If you don't have
extensions that "rock", nobody will believe that the second product
"rocks".
Now if that would be true that would also be a Chicken and egg problem.
But I don´t believe it is. We do have an Office product that rocks and
it´s large user base alone should be able to attract potential extension
developers. And well in this case we do have Chickens and we do have
eggs, there is the SDK and there are already a few OOo extensions available.
[...]
ciao
Christian
ciao,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
