Glossary of Internet Terms /text/shared/00/00000002.xhp
Internet glossary common terms;Internet glossary glossaries;Internet terms terminology;Internet glossary mw changed "Internet...". Glossary of Internet Terms If you are a newcomer to the Internet, you will be confronted with unfamiliar terms: browser, bookmark, e-mail, homepage, search engine, and many others. To make your first steps easier, this glossary explains some of the more important terminology you may find in the Internet, intranet, mail and news.
CMIS The Content Management Interoperability Services (CMIS) standard defines a domain model and Web Services and Restful AtomPub bindings that will enable greater interoperability of Enterprise Content Management (ECM) systems. CMIS uses Web services and Web 2.0 interfaces to enable rich information to be shared across Internet protocols in vendor-neutral formats, among document systems, publishers and repositories, within one enterprise and between companies.
WebDAV Short for Web-based Distributed Authoring and Versioning, an IETF standard set of platform-independent extensions to HTTP that allows users to collaboratively edit and manage files on remote Web servers. WebDAV features XML properties on metadata, locking - which prevents authors from overwriting each other's changes - namespace manipulation and remote file management. WebDav is sometimes referred to as DAV.
Frames Frames are useful for designing the layout of HTML pages. $[officename] uses floating frames into which you can place objects such as graphics, movie files and sound. The context menu of a frame shows the options for restoring or editing frame contents. Some of these commands are also listed in Edit - Object when the frame is selected.
FTP FTP stands for File Transfer Protocol and is the standard transfer protocol for files in the Internet. An FTP server is a program on a computer connected to the Internet which stores files to be transmitted with the aid of FTP. While FTP is responsible for transmitting and downloading Internet files, HTTP (Hypertext Transfer Protocol) provides the connection setup and data transfer between WWW servers and clients.
HTML; definition HTML HTML (Hypertext Markup Language) is a document code language, which is used as the file format for WWW documents. It is derived from SGML and integrates text, graphics, videos and sound. If you want to type HTML commands directly, for example when doing exercises from one of the many available HTML books, remember that HTML pages are pure text files. Save your document under the document type Text and give it the file name extension .HTML. Be sure there are no umlauts or other special characters of the extended character set. If you want to re-open this file in $[officename] and edit the HTML code, you must load it with the file type Text and not with the file type Web pages. There are several references on the Internet providing an introduction to the HTML language.
HTTP The Hypertext Transfer Protocol is a record of transmission of WWW documents between WWW servers (hosts) and browsers (clients).
ImageMap; definition ImageMap An ImageMap is a reference-sensitive graphic or text frame. You can click on defined areas of the graphic or text frame to go to a target (URL), which is linked with the area. The reference areas, along with the linked URLs and corresponding text displayed when resting the mouse pointer on these areas, are defined in the ImageMap Editor. There are two different types of ImageMaps. A Client Side ImageMap is evaluated on the client computer, which loaded the graphic from the Internet, while a Server Side ImageMap is evaluated on the server computer which provides the HTML page on the Internet. In server evaluation, clicking an ImageMap sends the relative coordinates of the cursor within the image to the server, and a dedicated program on the server responds. In the client evaluation, clicking a defined hotspot of the ImageMap activates the URL, as if it were a normal text link. The URL appears below the mouse pointer when passing across the ImageMap. As ImageMaps can be used in different ways, they can be stored in different formats. ImageMap Formats ImageMaps are basically divided between those that are analyzed on the server (i. e. your Internet provider) and those analyzed on the web browser of the reader's computer.
Server Side ImageMap Server Side ImageMaps Server Side ImageMaps appear for the reader as a picture or frame on the page. Click on the ImageMap with the mouse, and the coordinates of the relative position are sent to the server. Aided by an extra program, the server then determines the next step to take. There are several incompatible methods to define this process, the two most common being: W3C (CERN) HTTP Server (Format type: MAP - CERN) NCSA HTTP Server (Format type: MAP - NCSA) $[officename] creates ImageMaps for both methods. Select the format from the File type list in the Save As dialog in the ImageMap Editor. Separate Map Files are created which you must upload to the server. You will need to ask your provider or network administrator which type of ImageMaps are supported by the server and how to access the evaluation program.
Client Side ImageMap Client Side ImageMap The area of the picture or frame where the reader can click is indicated by the appearance of the linked URL when the mouse passes over the area. The ImageMap is stored in a layer below the picture and contains information about the referenced regions. The only disadvantage of Client Side ImageMaps is that older Web browsers cannot read them; a disadvantage that will, however, resolve itself in time. When saving the ImageMap, select the file type SIP - StarView ImageMap. This saves the ImageMap directly in a format which can be applied to every active picture or frame in your document. However, if you just want to use the ImageMap on the current picture or text frame, you do not have to save it in any special format. After defining the regions, simply click Apply. Nothing more is necessary. Client Side ImageMaps saved in HTML format are inserted directly into the page in HTML code.
Java; definition Java The Java programming language is a platform independent programming language that is especially suited for use in the Internet. Web pages and applications programmed with Java class files can be used on all modern operating systems. Programs using Java programming language are usually developed in a Java development environment and then compiled to a "byte code".
Proxy A proxy is a computer in the network acting as a kind of clipboard for data transfer. Whenever you access the Internet from a company network and request a Web page that has already been read by a colleague, the proxy will be able to display the page much quicker, as long as it's still in the memory. All that has to be checked in this case is that the page stored in the proxy is the latest version. If this is the case, the page won't have to be downloaded from the much slower Internet but can be loaded directly from the proxy.
SGML; definition SGML SGML stands for "Standard Generalized Markup Language". SGML is based on the idea that documents have structural and other semantic elements that can be described without reference to how such elements should be displayed. The actual display of such a document may vary, depending on the output medium and style preferences. In structured texts, SGML not only defines structures (in the DTD = Document Type Definition) but also ensures they are consistently used. HTML is a specialized application of SGML. This means that most Web browsers support only a limited range of SGML standards and that almost all SGML-enabled systems can produce attractive HTML pages.
search engines; definition Search Engines A search engine is a service in the Internet based on a software program used to explore a vast amount of information using key words.
tags; definition Tags HTML pages contain certain structural and formatting instructions called tags. Tags are code words enclosed by brackets in the document description language HTML. Many tags contain text or hyperlink references between the opening and closing brackets. For example, titles are marked by the tags <h1> at the beginning and </h1> at the end of the title. Some tags only appear on their own such as <br> for a line break or <img ...> to link a graphic.
URL; definition URL The Uniform Resource Locator (URL) displays the address of a document or a server in the Internet. The general structure of a URL varies according to type and is generally in the form Service://Hostname:Port/Path/Page#Mark although not all elements are always required. An URL can be a FTP address, a WWW (HTTP) address, a file address or an e-mail address.
e2 LibreOffice 核心代码仓库文档基金会
summaryrefslogtreecommitdiff
path: root/oovbaapi/ooo/vba/word
AgeCommit message (Collapse)Author
2019-01-24Add WordBasic.FileClose()Tor Lillqvist
Change-Id: Ifc48e5fbcc212f0e80cf6877e2781910e38e5e54
2019-01-22Found documentation for WordBasic.ToolsOptionsView()Tor Lillqvist
Change-Id: Ic049f78fddcaabafbe6be18b92a87b56352c1a4c
2019-01-21Add a couple of known parameters to WordBasic.ToolsOptionsViewTor Lillqvist
Change-Id: Ifd472f4ca79ab97a1d6d5c5007537375121f6f58
2019-01-21Add a (dummy) WordBasic.FileSave()Tor Lillqvist
Change-Id: I021d63c9d57f1e0435bcc5f97abc57bc39fece01
2019-01-21Add a dummy WordBasic.ToolsOptionsViewTor Lillqvist
Does nothing. Needed for customer application to proceed. Once we are further along in getting it to work, we can investigate what the parameters passed to this ToolsOptionsView method actually are. (This WordBasic thing is something that has been deprecated since last century, I suspect, so no wonder it is hard to find authoritative documentation on it.) Change-Id: I62a6d6d9abb9364afca110570fa341a2375a77a6
2019-01-21Add Documents.OpenOld() method and Application.CustomizationContext propertyTor Lillqvist
OpenOld() just forwards to the regular Open(), passing empty extra parameters. CustomizationContext is fully dummy for now. Change-Id: I167494700853768d971fe16afea35e90a647a00e
2018-06-13Add a MailMerge class and object to the Writer VBA APITor Lillqvist
Just a dummy implementation so far. Needed because customer Automation client software seems to access it (through the very obsolete WordBasic API, even). It remains to be seen whether any actual mail merge functionality is needed. Change-Id: I40419da544f61173e4bcf759b887997c7f233b02 Reviewed-on: https://gerrit.libreoffice.org/55727 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-06-12Add ExistingBookmark() to WordBasicTor Lillqvist
Change-Id: I8f433b1ae5cc23aaa08935e87fca7674064ce881 Reviewed-on: https://gerrit.libreoffice.org/55706 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-06-12Add ooo.vba.word.XWordBasic.WindowName() methodTor Lillqvist
Change-Id: I0ff24c3bc331d55212855d79060eaa6f8f3dc013 Reviewed-on: https://gerrit.libreoffice.org/55705 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-06-12Add ooo.vba.word.XWindow.Caption propertyTor Lillqvist
Change-Id: Ifa94b95d935975a87322afebfe604a4016f5a53f Reviewed-on: https://gerrit.libreoffice.org/55692 Reviewed-by: Tor Lillqvist <tml@collabora.com> Tested-by: Tor Lillqvist <tml@collabora.com>
2018-06-07Add ooo.vba.word.Application.StatusBar property for debug output from clientTor Lillqvist
In many cases you don't want to use a bunch of MessageBox() calls in a VB6 client you are developing against LibreOffice, as that disrupts the working of the client. The developer might not mind, but other people trying it will be bothered by having to click through a stream of message boxes. Also, it is hard to correctly interpret the chronological sequence of LibreOffice's own debug output lines and such MessageBox() windows. WScript.Echo calls from a VBScript client are a bit better as they don't require any click-through, but still there is the problem of correlating with LibreOffice's own debug output. Setting this StatusBar property causes LibreOffice to output a SAL_INFO line with the tag "extensions.olebridge". Thus they are automatically merged with LibreOffice's own output and displayed in correct order. Sure, the intent of some existing 3rd-party client that sets this property would be to actually display a message in the status bar (whatever that corresponds to in LibreOffice), but until some such need is actually encountered, it's enough to just use it for this debug output functionality. After all, this property was not implemented at all earlier, so adding it now with somewhat special semantics is not a regression. (Note that on the Calc side, ooo.vba.excel.XApplication did have a StatusBar property already, and setting that does seem to attempt to display the text in some way. Possibly it should be enhanced to also do the SAL_INFO thing, for consistency? And possibly we should also have the message being displayed in the same fashion on the Writer side?) Change-Id: I5bf1e776d6401adfc43a558a2d919bd675298e1a Reviewed-on: https://gerrit.libreoffice.org/55413 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-05-31Add WordBasic property and its FileOpen "command"Tor Lillqvist
Change-Id: I74aca823bb871040b15f35b92f961dfe48807843 Reviewed-on: https://gerrit.libreoffice.org/55136 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-05-31Add window geometry attributes, too, to ooo.vba.word.XApplicationTor Lillqvist
Like the other similar attributes and methods added lately, they just forward to the corresponding attributes of the "active window". Whether setting and retrieving such then actually does something useful or not I don't know. My main concern is that Automation and COM clients at least won't complain and abort because of unimplemented APIs. Change-Id: Ia8d22e3137d314268ac6771bb355e9f0686f52dc
2018-05-31Add Move() to ooo.vba.word.XApplicationTor Lillqvist
Change-Id: Ib230e730f68a30b82915ed6d7898bf1c02690b70
2018-05-31Add Resize() method to ooo.vba.word.XApplicationTor Lillqvist
Seems to be commonly called by 3rd-party Automation (and VB6) client code. Change-Id: I29ee5e7d95f3da2ffae0fac44151148be6e272ee
2018-05-31Add a WindowState attribute to ooo.vba.word.XApplication, tooTor Lillqvist
It seems to be something 3rd-party VB6 clients expect to be able to get and put. Change-Id: If5079da8ba99fde74b12b9590737d575f6636210
2018-05-31Can simplify, our IDL compiler is more clever nowadaysTor Lillqvist
Change-Id: I785c115ab7bcb7cfddc8e79bd5d31278f0c544dc
2018-05-31Add DocumentOpen and NewDocument to XApplicationOutgoing and emit suchTor Lillqvist
Change-Id: Ia2a0ade0af45f1ba99b0cfa860bd1986edcf272e
2018-05-31Add ooo::vba::word::XDocuments::OpenNoRepairDialog()Tor Lillqvist
Just call Open() with the same parameters. (Most of which are cheerfully ignored.) Change-Id: Ia9b980bf870bac04fab7e23843d29f66d5859037
2018-05-31Add ooo::vba::word::XApplicationOutgoing::DocumentBeforeClose() callbackTor Lillqvist
Change-Id: Iccdb7bc262b8f85caf7efb4407a1f00ff0cfb4a8
2018-05-31Add Document.Close event generationTor Lillqvist
Use a similar idea as for the Application events. Use the SwDocShell to keep the XSinkCaller. Call the Close event from SwXTextDocument::close(). Change-Id: Ie873238c5a966fc859d45b59f424ae0e9f4fbfc7 Reviewed-on: https://gerrit.libreoffice.org/55110 Reviewed-by: Tor Lillqvist <tml@collabora.com> Tested-by: Tor Lillqvist <tml@collabora.com>
2018-05-31Add ooo.vba.word.XDocumentOutgoingTor Lillqvist
Change-Id: I0243ee3e492d8445ebcc059293dcc4cb3c5c889b Reviewed-on: https://gerrit.libreoffice.org/55105 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-05-30Work in progress related to invoking events in Automation clientsTor Lillqvist
XConnectable interfaces need a second IID, for the interface "itself", not the coclass. (I am sure there is some catchy short term for that, I just can't find it right now.) Allow several simultaneous sinks for a SwVbaApplication. Not sure in what case such would be needed, but you never know about 3rd-party client code, and it's trivial to handle anyway, so why not. Lots of FIXMEs still. There is likely also a lot of leaks. But at least an event handler in a simple VBScript script does get invoked. Note that the changed and added code in extensions/source/ole is totally unaware of what outgoing ("event") interfaces Writer or Calc implements, it is all handled generically through the UNO interfaces I added recently. One particular thing that needs doing is to actually make Writer (and Calc) raise this kind of events when necessary. The current code to invoke events handlers in StarBasic (including StarBasic code running in "VBA" compaibility) is very much tied to having StarBasic running (not surprisingly), which of course is not at all the case when it is an Automation client that is manipulating a Writer or Calc instance and wants events. There is demonstration-only code in SwVbaApplication::Documents() to raise the "Quit" event. (I would have put that in the SwVbaApplication destructor but that doesn't seem to get called.) That should of course go away once we invoke other relevant events in appropriate places. And the "Quit" event needs to be invoked when the application is quitting. The whole callback mechanism with IConnectionPoint etc is still partly a mystery to me. It is entirely possible that even if this now works for a simple VBScript client, it won't work for (for instance) a VB6 client that might exercise the APIs of the COM interfaces we provide in a different way. Add XSinkCaller, for something that perhaps calls one or several XSinks. Change-Id: Ica03344010e374542f4aceff5ec032c78579f937 Reviewed-on: https://gerrit.libreoffice.org/55093 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>
2018-05-30Add a (dummy) ooo::vba::word::XApplication::ShowMe() implementationTor Lillqvist
Some customer VB6 code calls it. It doesn't seem to do anything interesting in Word either, so I don't feel that bad for it not doing anything in Writer. Change-Id: I81162fcdd0caa22b19760f8cb40266f7f571d8ce Reviewed-on: https://gerrit.libreoffice.org/55069 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Tor Lillqvist <tml@collabora.com>