UNO wrapper project

Jürgen Schmidt schrieb:

>
> The biggest problems with the current API are missing
examples, 
> documentation and maybe tools support. When you compare
our API with 
> the MS API you will see that our API is not so bad . But for
MS you 
> can find thousands of books, examples and you have
great tools/IDE 
> support making the development easier.

 Make the BASIC IDE much better and more intelligent, then
software
will come. The software model is (from the view of the IT
concept) ok,
but for users .... no.


 Marten

-- 
Marten Feldtmann - Germany - Software Development
Information regarding VA Smalltalk and DMS-system
"MSK - Mien Schrievkrom" at: www.schrievkrom.de


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Hello together,

>> The biggest problems with the current API are
missing examples,
>> documentation and maybe tools support. When you
compare our API with
>> the MS API you will see that our API is not so bad
.
But for MS you
>> can find thousands of books, examples and you have
great tools/IDE
>> support making the development easier.
> 
> 
> Make the BASIC IDE much better and more intelligent,
then software
> will come. The software model is (from the view of the
IT concept) ok,
> but for users .... no.

I know ads are not good, but there exists a UNO Wrapper. But
it is
commercial: www.riess.de

Greetings, Tobias

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

On Wed, 19 Apr 2006 13:34:14 -0400, Marten Feldtmann  
<m.feldtmannt-online.de> wrote:

> Jürgen Schmidt schrieb:
>
>>
>> The biggest problems with the current API are
missing examples,  
>> documentation and maybe tools support. When you
compare our API with  
>> the MS API you will see that our API is not so bad
.
But for MS you  
>> can find thousands of books, examples and you have
great tools/IDE  
>> support making the development easier.
>
>  Make the BASIC IDE much better and more intelligent,
then software
> will come. The software model is (from the view of the
IT concept) ok,
> but for users .... no.
>
>
>  Marten
>

I agree with Jurgen statement however the API newsletter is
constanstly  
asking for new contributors for documentation. The issue
here is a  
technical gap, if I have time to build documentation but
lack the  
knowledge to build it, I cant contribute. And if I am a
developer usually  
I am too busy to mind about documentation.

Yes snippets of code, a deframented developer guide and more
blogging  
about the code that is being currently develop might make
this easier for  
someone who want to document. Andrew Pitonyak for example
has done an  
incredible job documenting the Macros / Basic framework. So
has Ian  
Laurenson and Laurent Gogard. David on the other side has
builded good  
resources regarding the XML schema of OpenDocument and how
to hack it  
including perl snippets and XSLT.

However the API has not been so thoroughly documented (at
least that I am  
aware of) and some things get just acumulated on the
developer guide which  
really needs to be better supported. AFAIK the novell guys
have documented  
a bit more and had ported all the docuemntation to the wiki.
However most  
of this documents dwell more on the building process.

A feature that might make IDE better is integrated to Xray
or PyXray on a  
way that can autocomplete the methods however basic itself
is limited  
within the UNO framework. Java and C++ is the way to go to
true hack the  
UNO space, this makes it a bit away from their range for the
Basic IDE  
since is not made to handle java or C++ code. Cedric was
working on a  
eclipse module but I am not sure if it was specifically for
UNO  
developemnt.

Finally the place to really get all this information and
documentation is  
on discussion form at the OOoForum and this mailing list
where there has  
been some technical discussions about the API, IDL and the
rest.

-- 
Alexandro Colorado
CoLeader of OpenOffice.org ES
http://es.openoffice.org

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Hi Alexandro,

Alexandro Colorado a écrit :

> A feature that might make IDE better is integrated to
Xray or PyXray on
> a way that can autocomplete the methods however basic
itself is limited
> within the UNO framework. Java and C++ is the way to go
to true hack the
> UNO space, this makes it a bit away from their range
for the Basic IDE
> since is not made to handle java or C++ code. Cedric
was working on a
> eclipse module but I am not sure if it was specifically
for UNO
> developemnt.

I was and am still working on the Eclipse plugin. I'm now
making it
understandable by other developers to let people help me ;)
Its aim is
to support UNO development and includes:
  + UNO-IDL editor
  + Some UNO types creation wizards (still has to be
completed to
support every main type)
  + build from .idl file to .class file in Java

What still needs to be done:
  + Adding an export wizard for Java in order to create a
package
  + Adding C++ support (using Eclipse CDT)
  + Adding Python support (using pyDev plugin)
  + Supporting URE applications
  + Writing some more documentation for the plugin
(developer's guide)
  + Migrating the wiki pages on my own wiki to the OOo one.

I hope that my work is clearer to you now ;)

Cedric

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org

Alexandro Colorado wrote:

> A feature that might make IDE better is integrated to
Xray or PyXray on a  
> way that can autocomplete the methods however basic
itself is limited  
> within the UNO framework. 

This is an oversimplification and an overcomplication at the
same time.

Wether you can have autocompletion or not is not a matter of
the
language or their binding to UNO or not, it's a matter of
the type system.

Autocompletion needs static typing, means: you must know the
type of an
object to be able to autocomplete written code to the
methods of the object.

So if you want autocompletion in a programming language you
must
integrate static typing into it. This is possible with
*every*
programming language, even with OpenOffice.org Basic.

OTOH exactly Basic programmers don't like static typing
(means: they
don't like typing their variables at all ), so you
have to make a
choice.

As I already suggested in devextensions: offering
*optional* static
typing would allow us to implementing autocompletion in the
BasicIDE for
all developers that take this option, means something like

dim doc as com.sun.star.textTextDocument
doc = StarDesktop.loadComponentFomURL(...)

instead of

dim doc
doc = StarDesktop.loadComponentFomURL(...)

would enable the IDE to autocomplete the code if the user
starts to type
"doc."

Best regards,
Mathias

-- 
Mathias Bauer - OpenOffice.org Application Framework Project
Lead
Please reply to the list only, nospamforMBAgmx.de is
a spam sink.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeapi.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org