Hi Bernd, *, On Fri, Nov 24, 2006 at 07:43:14PM +0100, Bernd Eilers wrote: > Graham wrote: > >On Friday 24 November 2006 21:30, Kay Ramme - Sun Germany - Hamburg wrote: > >>John McCreesh wrote: > >>>On Thu, 2006-11-23 at 10:29 +0100, Kay Ramme - Sun Germany - Hamburg wrote: > > [UDK/URE] > What this basically means it that what we do have here is a "second > product" besides OpenOffice.org itself that is offered here and IMHO it > is a very valid request to make this second product visible on the MAIN > page. If we´d be a company "selling" two products we´d be stupid to not > show both of them on our companys main page; same thing should apply here.
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 > [...] > The user audiance for this "second product" and the user audiance for > the "main product" - OpenOffice.org itself do only overlap a little bit > and it´s not "simple application end users only" it´s developers of > extensions for OpenOffice.org and developers developing their own > software totally in no relationship with OpenOffice.org [...] This is rather an argument against putting it along with the OOo-products on the frontpage, since that clearly is end-user related. As written before: I don't oppose to adding another Development button in the toptabs or some similar prominent element on the frontpage. But for this to happen, there needs to be such a "overwiew" page first. A link-list is not very attractive. Neither is having 10+ buttons on the frontpage for every developing area. The frontpage is mainly for end-users. Those don't want technical details (what OOo module is responsible for what application component) or learn about how to write your own application. > [...] On the other hand our bricks > are very good bricks and other things than houses (OpenOffice.org and > OpenOffice.org extensions) can be build with it, that´s why we want to > sell them seperatly [ well of course we are not selling anything, we > give that away for free as well as anything else ;-) ] So you seem to agree that's not a good idea to place it along with the OOo-Subapps. > 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... ,---- | 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. 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. 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.... > [...] > 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) > 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. Having the documentation focus on java and c doesn't help there either. Doing things with the SDK is far harder than doing similar things in VBA for example. (You can almost "point and click" your VBA macro, doing this with basic is already hard. Doing the same as an extension is a hell lot more difficult) > [...] > 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). OOo is not only for geeks. It is a professional application. That's an important part of "the message"... > [more special user-groups] > Which we currently don´t do agressivly enough. Because IMHO the very > basic thing is missing: there´s not even a reference on the main page > that hints to it. Again: Chicken and egg problem. If there is nothing to point to, there will be no link. > 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. If you don't have extensions that "rock", nobody will believe that the second product "rocks". > [...] ciao Christian -- NP: Incubus - Redefine --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
