Curtis Clauson wrote:
Frank Sch�nheit - Sun Microsystems Germany wrote:
Sadly: yes, your right, and no, there is no other way :(
Feel feel to submit an request for enhancement in IssueZilla, requesting
introduction of an efficient index retrieval. Component "database
access", owner [EMAIL PROTECTED] (that's me).
Done. Issue #49908.
Uh. If we go to extend the event attaching API for form controls, I am
not sure I would continue using the XEventAttacherManager interface
(except for legacy reasons). It has some disadvantages (such as handling
attached scripts at the parent of an object, not at the object itself,
which imposes structural limitations), so I would probably like to get
rid of it.
Also, OOo's API features at least three different concepts of assigning
scripts to certain events on certain objects, and if we're going to
renew one of them, we should simply use (and perhaps improve) one of the
other ones, if appropriate.
(Uh, The rhythmic thumping sound you hear is me banging my head against
the monitor in abject frustration at Sun's inability to grasp even the
simplest concepts of proper, or even useful, documentation.)
According to the current 2.0 SDK Developers Guide (680m105), section
13.8 - Scripting and Events, the XEventAttacherManager *IS* the only
effective way we're supposed to use script to programmatically attach
script to component events. According to section 13.9.4, directly
creating and attaching Listeners creates too many problems with the
scripting environment. I've no idea what your third concept is.
Are you telling me that this newly documented procedure is now outdated
*legacy* code?? Then, please, what is the correct method, where is it
documented, and why is the current guide in error?
(Sorry if I sound frustrated, but trying to get anything to work
properly in the OOo data access arena has proven easily as bad as in MS.)
don't be frustrated, simply help us to improve the documentation.
Creating good developer documentation is always hard and we try to keep
the DevGuide up-to-date. And of course compared to other projects i
think we are not so bad ;-)
- if you find bugs -> submit an issue
- give general feedback for the documentation
- if you have find a solution for a common topic/problem -> prepare a
code snippet, document it and contribute it to our code snippet base,
this will help others to find a solution faster.
You can also prepare a 5 pager (or less) tutorial, explain what you have
done in detail and we will put it on api.openoffice.org. Spread your
knowledge and experience and help others.
don't be frustrated, start working with the community ;-)
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
