WO1998004978A1 - Draw-based editor for web pages - Google Patents

Draw-based editor for web pages Download PDF

Info

Publication number
WO1998004978A1
WO1998004978A1 PCT/US1997/012817 US9712817W WO9804978A1 WO 1998004978 A1 WO1998004978 A1 WO 1998004978A1 US 9712817 W US9712817 W US 9712817W WO 9804978 A1 WO9804978 A1 WO 9804978A1
Authority
WO
WIPO (PCT)
Prior art keywords
page
user
html
draw
void
Prior art date
Application number
PCT/US1997/012817
Other languages
French (fr)
Inventor
Samir Arora
Gagan Arora
Rajagopal Lakshminarayan
Gregory Brown
Martin Frid-Nielsen
Original Assignee
Rae Technology, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Rae Technology, Inc. filed Critical Rae Technology, Inc.
Priority to AU38082/97A priority Critical patent/AU3808297A/en
Publication of WO1998004978A1 publication Critical patent/WO1998004978A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/12—Use of codes for handling textual entities
    • G06F40/137—Hierarchical processing, e.g. outlines
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/12—Use of codes for handling textual entities
    • G06F40/14—Tree-structured documents
    • G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting

Definitions

  • This application relates to the World Wide Web and, in particular, to a method and apparatus for easily generating web pages on a "What You See is What You Get" (WYSIWYG) basis.
  • the Web is built around a network of "server” computers, which exchange requests and data with each other using the hypertext transfer protocol ("http").
  • http hypertext transfer protocol
  • a human designer designs the layout of a Web page, which is then
  • HTML Hypertext Markup Language
  • HTTP Uniform Resource Locator
  • Web pages can also be linked graphically to each other.
  • HTML HTML to describe a Web page is often created by hand by a human being. If the design of the page changes, the corresponding HTML must be rewritten, which is an exacting process.
  • HTML- editors exist, these editors only allow the user to specify certain elements of a page and frequently still require the user to physically enter HTML code.
  • Conventional HTML editors allow the user to specify the page content and general layout, but do
  • a Web "site” consists of a "homepage” and several other related pages. Each page has corresponding HTML that describes the appearance and function of the page.
  • the HTML for the homepage usually contains links to one or more of the other pages and the other pages often contain respective links back to the homepage.
  • the browser requests and displays the linked-to page.
  • Each link must be designed and coded into the HTML for the page.
  • the HTML for the homepage must be changed to reflect the removed link.
  • the present invention overcomes the problems and disadvantages of the prior art by using a drag and drop interface to allow a user to easily design a Web page.
  • the user moves display elements to define the appearance of a web page.
  • HTML code is automatically generated.
  • a preferred embodiment of the invention generates an HTML table in
  • the number and size of cells in the HTML table reflects the number and placement of display elements on the page, yielding a true WYSIWYG Web page. Because the generated HTML code is in the form of a table, the HTML will cause most browsers to display a page that has substantially the same layout, proportionality, coloring, and spacing as the layout of the page displayed by the page draw editor software. Initially, the present invention automatically generates a layout that is used for each page unless overridden by the user. Each page is initially generated in
  • the invention is a method of allowing a user to define a World Wide Web page comprising the steps, performed by a data processing system, of: displaying a plurality of page display elements on a display device, the display elements forming a page layout on the display device; receiving an indication that the user wants to add a new display element to the page at a first position on the page, adding a new draw data structure in a memory of the data processing system for the new display element to a plurality of other draw data structures, the steps, performed by a data processing system, of: displaying a plurality of page display elements on a display device, the display elements forming a page layout on the display device; receiving an indication that the user wants to add a new display element to the page at a first position on the page, adding a new draw data structure in a memory of the data processing system for the new display element to a plurality of other draw data structures, the
  • the new draw data structure includes data representing the first position, and generating HTML that substantially reflects the displayed page layout on a pixel by pixel basis in accordance with the draw data structures
  • FIG. 1 is a block diagram of a computer system in accordance with a preferred embodiment of the present invention
  • Fig 2 is a block diagram showing input and output to and from page draw
  • Fig 3 shows an example of display view before the user has created any
  • Fig. 4 shows the display of Fig. 3, including a banner, navigator buttons,
  • Fig. 5 shows the display of Fig. 4 after the user has dragged and dropped an image and some text into the layout.
  • Fig. 6 shows a preview display of the layout of Fig. 5.
  • Fig. 7 shows the display of Fig. 5 after the user has dragged and dropped the text to a different location on the page.
  • Fig. 8 shows a preview display of the layout of Fig. 7.
  • Fig. 9(a) shows a detail of a tool window of Fig. 3.
  • Fig. 9(b) shows a portion of the tool window displayed in connection with an Image tool.
  • Fig. 9(c) shows a portion of the tool window displayed in connection with a Forms tool.
  • Fig. 9(d) shows a portion of the tool window displayed in connection with a Draw tool.
  • Fig. 10(a) shows a Page tab in a Properties window of Fig. 3.
  • Fig. 10(b) shows a Layout tab in the Properties window of Fig. 3.
  • Fig. 10(c) shows a Rectangle tab in the Properties window of Fig. 3.
  • Fig. 10(d) shows a Text tab in the Properties window of Fig. 3.
  • Fig. 10(e) shows an ActiveX tab in the Properties window of Fig. 3.
  • Fig. 10(f) shows a Java APPLET tab in the Properties window of Fig. 3.
  • Fig. 10(g) shows a Shockwave tab in the Properties window of Fig. 3.
  • Fig. 10(h) shows a Table tab in the Properties window of Fig. 3.
  • Fig. 11 (a) shows a first pull-down menu.
  • Fig. 11(b) shows a second pull-down menu.
  • Fig. 11 (c) shows a third pull-down menu.
  • 5 Fig. 12 is a flow chart showing steps performed by the page draw editor software to define a page layout.
  • Fig. 13 is an example showing an initial internal representation stored in a memory of objects automatically generated on the page by the page draw editor software for the layout of Fig. 4.
  • ⁇ o Fig. 14 is an example showing the internal representation after some display elements have been added by the user.
  • Fig. 15 is an example showing the internal representation after a display element has been moved by the user.
  • Fig. 16(a) is an example of a draw object for a page banner.
  • Fig. 16(b) is an example of a first draw object for a navigator button.
  • Fig. 16(c) is an example of a first draw object for a navigator button.
  • Fig. 16(d) is an example of a draw object for a text button.
  • Fig. 17 shows an example of a display used to allow the user to publish the pages of a site.
  • Fig. 18 shows an example of a display used to allow the user to specify details of how to publish a site.
  • Fig. 19 is a flow chart showing steps performed by the page editor software
  • Fig. 20 a flow chart showing steps performed by the page editor software 25 to publish a normal page.
  • Fig. 21 is a flow chart showing steps performed by the page editor software to publish a stacked page.
  • Fig. 22 is a flow chart showing steps performed by the page editor software to generate initial HTML for a page.
  • Fig. 23 is a flow chart showing further steps performed by the page editor
  • header body, and footer.
  • Fig. 24 is a flow chart showing steps performed by the page editor software
  • Fig. 25 is an example of steps performed by the page editor to generate final HTML for a page.
  • Fig. 26 is an example of first steps involved in determining an HTML table
  • Fig. 27 is an example of second steps involved in determining an HTML
  • Fig. 28 is an example of a matrix generated by the steps of Figs. 26 and
  • Fig. 29 is a block diagram of how the matrix of Fig. 28 is used to generate
  • Fig. 30 shows an example of a Style display.
  • Fig. 31 shows an example of an Assets Display.
  • Fig. 32 shows an example of a plurality of link dialog boxes, showing a structural link, an internal link, and an external link.
  • Fig. 33 is a flow chart showing updating of structural links for a page.
  • Fig. 34 shows an example of a dialog box used to create a data object.
  • Fig. 35 shows a block diagram of an example of a stacked page and a
  • Fig. 36 shows an example of an icon for a stacked page.
  • Fig. 37 shows an example in which a user has opened the Tool window and selected the DataList tool.
  • Fig. 38 shows a Properties window with a DataList tab opened for the DataList tool and the DataList window.
  • Fig. 39 shows a further example of a Properties window with a DataList tab.
  • Fig. 40 shows an example in which a user has opened the Tool window and selected the DataField tool.
  • Fig. 41 shows a Properties window with a DataField tab opened for the DataList tool.
  • Fig. 1 is a block diagram of a computer system 100 in accordance with a
  • Computer system 100 includes a
  • CPU 102 central processing unit 102
  • memory 104 memory 104
  • input/output lines 105 input/output lines 105
  • an input device 150 such as a keyboard or mouse
  • a display device 160 such as a display terminal.
  • Computer 100 also includes an input device 161 , such as a floppy disk drive or CD
  • Memory 104 includes page-
  • draw editor software 120 draw objects 130, HTML 140, and image files 140, etc., as described in further detail below.
  • memory 104 also includes
  • computer system 100 contains additional information, such as application programs, operating systems, data, etc., which are not shown in the figure for the sake of clarity. It also will be understood that computer system 100 can also include numerous elements not shown in the Figure for the sake of clarity, such as disk drives, keyboards, display devices, network connections, additional memory, additional CPUs, LANs, internet connections, input/output lines, etc. In the following discussion, it will be understood that the steps of methods and flow charts discussed preferably are performed by processor 102 executing
  • Fig. 2 is a block diagram showing input and output to page draw editor software 120 of Fig. 1.
  • Page draw editor 120 includes a portion 202 that creates and manages a page layout and a portion 204 that publishes the page 140. The
  • Pages can include new text and images or preexisting text and images.
  • the user initiates publish portion 204 by clicking on a "publish" button displayed by the editor 120, as
  • Publish portion 204 generates HTML for the page, as also
  • the page is translated into an HTML table that yields a WYSIWYG Web page when displayed by a browser.
  • Fig. 3 shows an example of a page view displayed on display device 160 before the user has created any display elements on the page.
  • the display of Fig. 3 shows an example of a page view displayed on display device 160 before the user has created any display elements on the page. The display of Fig.
  • FIG. 3 is opened when the user indicates (using a pull-down menu or the like) that he wishes to create a new page.
  • the page draw editor allows the user to
  • the user can then rearrange display elements by dragging and dropping them to a new location, placing the display elements exactly where they will eventually appear with pixel level accuracy.
  • Fig. 3 includes a grid of lines. These lines are shown as dotted lines, but can also be solid lines. In the described embodiment, the grid also can be turned off so that no grid is displayed. The grid preferably is not included in the generated HTML. In Fig. 3, the grid has a granularity of 24 x 24 pixels in accordance with a default width as shown in a Properties window 350, as discussed below.
  • the display of Fig. 3 includes a plurality of buttons: a "Site” button 302, "Page” button 304, a “Style” button 306, an “Assets” button 308, and a “Publish” button 310.
  • the display also includes a "Preview” button 312, a "New Page” button 314, a "Goto” button 316, and a "Last” button 318.
  • Site button 302 causes execution of a "site editor”. Style button 306 and Assets button 308 are discussed below.
  • New Page button 314 causes a page such as the page of Fig. 3 to be
  • Goto and Last buttons 316, 318 transfer control to a most recent display or a user-selected previous display, in a manner known to persons of ordinary skill in the art.
  • the described embodiment keeps a "history" of execution of page draw editor 120 in order to implement the Goto and Last buttons.
  • the display of Fig. 3 further includes a Secondary navigator bar 365, including a "Layout View” button 320 and an "HTML Source” button 322.
  • Figs. 3-8 is displayed.
  • HTML Source button 322 When the user clicks on HTML Source button 322, a display (not shown) shows the HTML that is generated for the current page layout.
  • buttons 322 is omitted in an alternate embodiment.
  • Other views have other buttons and
  • Secondary navigator bar 365 contains a dotted line extending vertically downward from a currently clicked button (e.g., Page button 304) to a selected one of the
  • buttons on secondary navigator bar 365 As the user selects different buttons on
  • the dotted line is redrawn to connect the currently selected buttons. This feature makes it easy for a user to see which buttons are currently selected and to mentally connect the functions of the primary
  • Fig. 3 also shows "Properties” window 350 in which a "View” tab is selected.
  • Properties window 350 includes three tabs: a "View” tab 352, a "Page” tab 354, and a "Layout” tab 356.
  • the values shown in Properties window 350 are values for the current page.
  • Properties window 350 currently shows view properties because View tab 352 is selected.
  • Figs. 10(a) and 10(b) show examples of the Page and Layout tabs, respectively.
  • a fourth tab (see, e.g., Fig. 10(c)) is a context sensitive tab and represents various properties, depending on the tool being used. Other tabs may appear in other implementations.
  • Properties window 350 of Fig. 3 are the default values for viewing a newly created page.
  • Properties window 350 includes a "Measurement Unit” area 360, a "Element border” flag area 362, “Grid Width” and “Grid Height” areas” 364, 366, a "Show Grid” flag 365, font size areas 368, 370, a "Color” area 372, a "Horizontal Splitter” flag area 374, and a "Snap to Grid” flag
  • the grid is measured in units of pixels.
  • a grid of 24 x 24 pixels is displayed.
  • the specified fonts are used.
  • the page uses
  • the display of Fig. 3 further includes a "Tools" window 324. As shown in
  • Tools window 324 includes a "cursor” tool 380, a “zoom in” tool 381 , and a “zoom out” tool 382. These three tools have an outward operation similar to “cursor,” “zoom in,” and “zoom out” tools known in the art.
  • control tools are collectively known as “control tools.”
  • Tools window 324 also contains a "Text” tool 383, an "Image” tool 384, a “Draw” tool 385, a “Table” tool 386, an "Audio” tool 387, a “Video” tool 388, a “Java” tool 389, an "ActiveX” tool 390, a Shockwave tool 391 , a "Form” tool 392, a “DataList” tool 393, and a “DataField” tool 394.
  • Tools window 324 also includes a plurality of buttons 395
  • Fig. 4 shows the display of Fig. 3, including a banner, navigator buttons, and text buttons automatically created by a preferred embodiment of the present invention.
  • the example of Fig. 4 is displayed after the user indicates that he wants
  • the automatically created draw objects reflect links between pages of the site, as described below in the copending application.
  • the user can easily create and move display elements on the page, which causes changes to corresponding draw objects in memory 104.
  • Horizontal splitters such as 380 and 382 are displayed.
  • the display of Fig. 4 creates a page having three parts: a header 402, a body 404, and a footer 406.
  • the user can move the dividers 380, 382 between the header, body and footer as is known in the art. Moving the dividers adjusts the
  • the page of Fig. 4 is entered from the site view, and automatically creates display elements of header 402 and footer 406 reflecting the logical connection of the current page to other pages.
  • Header 402 automatically contains a banner 410 and a plurality of navigator buttons 412.
  • the banner contains the name of the selected page ("Products")
  • Navigator buttons 412 include buttons for a homepage ("Home button 4), a "Welcome” page (“Welcome” button 416), and a “Private” page (“Private” button 418).
  • Navigator buttons 412 preferably include an image, such as
  • This image may be predefined or defined by
  • buttons 412 automatically include buttons corresponding to the home page and to the previous hierarchical level of the page.
  • Alternate implementations of the present invention automatically display navigator buttons for one or more of the home page, the parent page, sibling pages, and children pages.
  • the user chooses which navigator buttons are generated automatically by way of a pop-up site window. The user may add or
  • Footer 406 automatically contains a plurality of text buttons 428. These text buttons preferably correspond to the navigator buttons 412. Thus, text buttons
  • buttons for the homepage (“Home text button 430), the Welcome page 452 ("Welcome” text button 432), and the "Private” page 454 (“Private” text button 434).
  • the user may add or delete additional buttons and may move buttons, as described below.
  • the internal memory representation of banner 410 and of buttons 412 and 430 are discussed in detail below.
  • Figs. 5-8 show an example of creation of display element in a page layout and also show an example of a modification to the page layout using a drag and drop interface in accordance with the described embodiment of the preferred
  • Fig. 5 shows the display of Fig. 4 after the user has dragged and dropped an image 502 and some text 504 into the layout. Specifically, as discussed in detail below, the user creates image 502 using Image tool 382 and creates text 504 using Text tool 383.
  • image 502 is a 324 x 216 pixel image originally stored in memory or on a storage device attached to computer system 100.
  • Fig. 6 shows a preview display of the layout of Fig. 5.
  • Fig. 5 is displayed when the user clicks on Preview button 312 of Fig. 3 (or selects "Preview" from a pull-down menu).
  • page draw editor 120 In order to preview a site, page draw editor 120 actually generates HTML for the current layout of the page and stores it at a predetermined (or user-defined) location. The editor then invokes a browser program (such as the-
  • Fig. 7 shows the display of Fig. 5 after the user has dragged and dropped the text to a different location on the page. Specifically, as discussed in detail
  • the user places a cursor on text 504 using input device 150 (such as a mouse) and drags the text to a new position using input device 150.
  • input device 150 such as a mouse
  • Movement of a display element on a display device in accordance with cursor input is known in the art and will not be described herein.
  • the draw object associated with text 504 is changed to reflect this movement as described below.
  • Fig. 7 also shows Properties window 350 in which "Layout" tab is selected.
  • the values shown in Properties window 350 are values for the current page.
  • Properties window 350 (with a Layout tab) includes a "Layout Name" area 702, a
  • Layout of Fig. 7 is currently untitled.
  • the layout is of the specified height and width.
  • the page uses the type of background described in areas 708-712 (i.e., a predetermined "Site style background", such as a picture of a marbled surface) instead of a solid background or a image background provided by the user.
  • Site style background such as a picture of a marbled surface
  • Fig. 8 shows a preview display of the layout of Fig. 7. As shown in Fig. 7,
  • the Preview function causes new HTML for the changed page layout to be generated and the new HTML to be displayed by the browser in window 602.
  • the HTML generated for the page causes a browser to display a page that is pixel-per-pixel the same as the display elements on the display screen, assuming that the browser supports Netscape version 3.X.
  • the user can design a page layout and expect the page to look exactly as it was designed when the page is displayed by a
  • Tag 802 is an optional line resulting from HTML generated in the described embodiment of the present invention. 1. The Pull Down Menus
  • Figs. 11 (a) through 11 (c) show examples of pull-down menus for the described embodiment of draw page editor 120.
  • Fig. 11 (a) shows an Edit menu having an Undo function, a Cut function, a Copy function, a Paste function, a Paste Special function, a Delete Page function (A delete display element function is not shown), an Options function, a Preferences section, and a Duplicate Layout
  • Fig. 11(b) shows a View pull-down menu, which includes a Page Properties function that opens, e.g., Properties window 350 with a page tab selected, and Tools Palette function that opens, e.g., Tools window 324.
  • Page Properties function that opens, e.g., Properties window 350 with a page tab selected
  • Tools Palette function that opens, e.g., Tools window 324.
  • Fig. 11(c) shows a Layout pull-down menu, which includes an Align Objects function that horizontally, vertically, or centrally aligns display elements, a Center Objects function that centers display elements, a Size Objects function that sizes display elements, an Element Script function, and a Layout script function.
  • Figs. 9(a) through 9(d) show examples of Tool window 324 and show various icons that are displayed in area 395, depending on which tool is being used.
  • Some of the tools of the described embodiment can be thought of as a Swiss army knife; when you select one, a secondary group of tools appears in area 395, each secondary tool performing a different function on the same kind of display element.
  • page draw editor 120 allows the user to enter a text display element.
  • the user uses the cursor to create and size a text box on the display and then types text inside it.
  • a Text tab shown in Fig. 10(d) is displayed in the Properties window 350.
  • This Properties window allows the user to enter properties of the text display element. These properties include whether the text is bold, italic, or has a strike-out bar, the font, the font size, paragraph alignment, and whether to use a bullet.
  • the properties further include whether to use a predetermined "site style" for the text (i.e. , a
  • the user may also specify a fill color for the text box. If the user indicates that the text box is also a link, he may also fill in the name of an associated script (e.g., a CGI script).
  • the location of the link is added to a list of hotspot locations stored in memory and values are stored in the text draw object to indicate that the text contains a hot spot and its URL.
  • a text draw object is added to the list of draw objects.
  • page draw editor 120 allows the user to specify an image display element. Unlike the text boundary, the image i o boundary resizes to fit a user-specified image. Once the image has been added to the display, the user can create a link on all or part of the image or select one color in the image as transparent. The user can also change the size of the image using the cursor.
  • This Properties window allows the user to enter a name of an existing image and various properties of the
  • the image such as whether the image is transparent, whether a fill background should be added to the image, and whether the image contains a link (e.g., a URL).
  • a link e.g., a URL
  • Tool 3050 allows the user to draw a boundary in which to place the image file.
  • Tool 3052 allows the user to click on a color of the image that he wants to be transparent. When the image is displayed, pixels of that color in the image will be suppressed so that the background will show through. (This means that a new image with a transparent
  • a flag in the Image draw object is set to indicate transparency.
  • Tools 3054-3056 allow the user to specify a "hotspot" on the image having different shapes.
  • the user can create a rectangular, circular, or polygon hotspot.
  • the user draws and sizes the hotspot on the display using the cursor and identifies the link/URL for the hotspot using a pop-up window (hot shown). Once the hotspot
  • the hotspot is added to a list of hotspot locations stored in memory
  • the image is displayed (e g ,
  • the Draw tool has five secondary tools 395,
  • the Polygon tool allows the user to draw a polygon using the cursor, as
  • Properties window 350 allows the user to enter properties
  • the rectangle such as the color of the rectangle, the border color and size of the rectangle, any text inside the rectangle (and its properties), whether a fill
  • each type of draw element has a different type of draw object.
  • Table tool 386 When the user clicks on Table tool 386, the page editor 120 allows the user to enter a table in the display.
  • the Table tool causes a table window to be opened (see Fig. 10(h)).
  • the page draw editor displays a "table" tab in Properties window 350 of Fig. 10(h).
  • the user can then specify the dimensions of the table. For example, the user can specify the number of columns, the number of rows, and the type of object that goes in each cell of the table.
  • the table is displayed on the screen and a table draw object is added to the list of draw objects.
  • a table layout element cause a table to be generated inside a table when HTML is generated for the page.
  • page draw editor 120 allows the user to draw a boundary in which to place an icon as a visual placeholder for an
  • the audio file is specified through a Properties tab (not shown).
  • the audio icon is
  • Video tool 388 page draw editor 120 allows the user to draw a boundary in which to place an icon as a visual placeholder for a video file.
  • the video file is specified through a Properties tab (not shown).
  • users can click the icon to see the video.
  • the Java Tool has specified the video icon and an associated video file, the video icon is displayed on the screen and a sound draw object is added to the list of draw objects.
  • page draw editor 120 allows the user to specify a Java applet and an address for the applet.
  • the Java tool, the ActiveX tool, and the Shockwave tool all specify display elements that are exemplary of a type of display element called a "plug-in.”
  • Java applets are small programs that can be downloaded over the web and run on most computer platforms.
  • the described embodiment allows the user to specify an icon for a Java applet and the location of the Java applet similarly to how the user specifies a sound or video icon and file.
  • Java applet icon clicks on the Java applet icon, the Java applet will be downloaded and executed.
  • the user specifies a Java applet and icon through use of a Java tab in
  • the Java icon is displayed on the screen
  • page draw editor 120 allows the user to specify an ActiveX file and an address for the file.
  • ActiveX files are small programs that can be downloaded over the web and run on most computer platforms.
  • the described embodiment allows the user to specify an icon for an ActiveX file and the location of the ActiveX file similarly to how the user specifies a
  • the user specifies an ActiveX applet.
  • the user has specified the ActiveX icon and an associated address, the ActiveX icon is displayed on the screen and an ActiveX draw object is added to the list of draw objects.
  • the Shockwave Tool The user specifies a Shockwave video file through use of a Shockwave tab in Properties window 350 (see Fig. 10(g)). This Properties window allows the user to browse a plurality of file names, to specify an alternate tag. Once the user has specified the Shockwave file, a predetermined Shockwave icon is displayed on the screen and a Shockwave draw object is added to the list of draw objects.
  • forms are an interactive
  • Web component They allow a user to send data to a server, either as request for
  • the Forms tool has six secondary tools 395, shown in Fig. 9(c): button
  • the user can then choose a secondary draw tool. If, for example, the user selects
  • buttons 1950 and clicks in the display window for the page a button display element is added to the page.
  • a button tab (not shown) appears in Properties window 350 in addition to the tabs shown in Fig. 3. Similar tabs appear when the other secondary draw tools are selected.
  • Properties window 350 allows the user to enter properties of the button, such as the color, any text inside the button (and its properties), and whether a fill background should be added to the button. In addition, the user decided whether the button is Submit button or a reset button.
  • a submit button sends the contents of all the form objects to a server.
  • a reset button allows the user to clear the form and start over.
  • Each of the forms elements described below is an element of a type that is currently included in conventional hand-coded HTML forms. Other embodiments may include still other form elements not described herein.
  • a check box is used to let users select one or
  • Editor 120 allows the user to specify what these
  • a radio button behaves just like a check box, except that only one
  • radio button in a group an be checked at once.
  • a single-line text provides an area
  • a multi-line text provides an area
  • a list box takes the form of
  • Editor 120 allows the user to specify the form of a list box. Once the user has specified a form element, the video icon is displayed on the screen and a form element draw object is added to the list of draw objects. In the described embodiment, each type of form element has a different type of draw object. The described embodiment allows one form in the header,
  • elements do not contain an identifier as to which form they belong to.
  • Other implementations may contain such an identifier and may allow multiple forms in the header, body, or footer.
  • FIG. 31 shows an example of an Assets display 3100 that displays all current files, links, and data objects for a data processing system.
  • the display 3100 is generated when the user clicks on Assets button 308 of Fig. 3. (Note that a dotted line extends from the Assets button to the Secondary navigator bar 365.)
  • the Assets view shows all files, hyperlinks, or data objects associated with the current system, depending on whether the user clicks secondary button 3102,
  • Fig. 31 shows an example of all data objects for the page of Fig. 5. It will be understood that the Assets view reflects files, links, and data objects stored in memory 104. Newly created files, links, and data objects are stored in memory 104 as well.
  • the File view shows information about all files in the site, such as: whether the file has a type of navigation bar images, pictures, sound, video, Java applets and other plug-ins.
  • the user can change, e.g., the name and location of files and can add and delete files through user of a dialog box (not shown).
  • the Links view shows information about all links in the site, such as: whether a link is internal, external, or structural.
  • a structural link reflects a hierarchical link shown in the site view.
  • changing a structural link in the Assets view changes the link in the site view and between
  • the Data Objects shows information about all DataObjects in the system.
  • Data objects can be internal data objects or can be ODBC (Object Data Binding
  • Fig. 34 shows an example of a dialog box 3400 used to create a data object.
  • Dialog box 3400 is displayed when the user clicks on a "new object” button (not shown) or clicks on a "new object” pull-down menu (not shown).
  • Box 3400
  • index field button 3412 a set button 3414, and move up/down buttons 3416,
  • dialog 3418 To create a data object in memory 104, the user enters information in dialog
  • a stacked page which is made up of “data pages.”
  • Fig. 35 shows a block diagram of an example of a stacked page 3502 and a series of pages 3504 displayed when a browser views the HTML pages created from the stacked page.
  • a data object such as a data base object (as described above). The user then
  • Page draw editor 120 allows the user to specify a list of fields to be displayed on a stacked page.
  • DataField tool 394 page draw editor 120 allows the user to specify the layout of the fields in the data list.
  • Fig. 36 shows an example of an icon for a stacked page that is displayed by the site level editor described in the co-pending application of Arora et al.
  • a page includes a DataList and a DataField object, it is classified as a stacked page.
  • a page is a stacked page, it is displayed at the site level as overlapping pages icon 3602. Stacked pages are moved at the site level in substantially the same manner as normal pages. However, multiple HTML pages are generated for
  • Fig. 37 shows an example in which a user has opened Tool window 324 and selected DataList tool 393. The user has then specified a rectangle 3704.
  • Fig. 38 shows a Properties window 350 with a DataList tab 3802 opened
  • Fig. 38 also shows a DataList window 3802. The user specifies, in the DataList window 3803, fields of the list that can be displayed on
  • DataList fields to select which fields of the data object will be included in the stacked page.
  • the properties of the DataList are displayed in Properties window 350.
  • DataList window 3803 the user optionally specifies a sort field 3806 in
  • Fig. 40 shows "Data List Tab" in Properties window 350.
  • Fig. 40 shows an example in which a user has opened Tool window 324 and selected DataField tool 394. The user has then specified a rectangle 4004.
  • the user names the data list ("Headline List”) and defines an appearance of the fields selected in Fig. 38. An area for each field can be sized and dragged to define the layout of each data page in the stacked page.
  • Secondary navigator bar 365 includes a button bar 4006 that has four buttons for managing data pages within a stacked page. These four buttons
  • a "back” button which displays the contents of a previous data page
  • a "forward” button which displays the contents of a next data page.
  • the user can create as many data pages as there are
  • Each data page will automatically contain display elements to a first, next, and previous data page.
  • a stacked page has a list
  • draw elements may have a structural link
  • Fig. 12 is a flow chart showing steps performed by page draw editor software 120 to edit a page layout during execution of the page draw editor.
  • the page draw editor determines whether the page is a new page. If it is an existing page, in step 1204, the current page layout for the page is displayed in accordance with the already existing draw objects for the page.
  • the page layout will include the automatically generated banner, navigator buttons, and text buttons, unless the user has previously deleted them.
  • step 1206 the editor displays the default page layout in accordance with the draw objects for the page.
  • the user exits the page draw editor by, e.g., clicking on Site button 302, Style button 306, Assets button 308, or Publish button 310 (or by selecting "exit" from a pull-down menu).
  • the editor displays the default page layout in accordance with the draw objects for the page.
  • the user exits the page draw editor by, e.g., clicking on Site button 302, Style button 306, Assets button 308, or Publish button 310 (or by selecting "exit" from a pull-down menu).
  • the user has edited a page, he can still move the page around in the site
  • Fig. 13 is an example showing an internal memory representation of draw
  • the internal representation includes a list of draw objects, representing each display element of the page of Fig. 4.
  • the list of draw objects includes a banner draw object 1302 (corresponding to banner 410), a navigator buttons draw object 1304 (corresponding to navigator buttons 412), and a text buttons draw object 1306 (corresponding to text buttons 428).
  • all draw objects of the header 402 are stored together and a pointer points to the beginning of this list.
  • all objects of the footer 406 are stored together and
  • a pointer points to the beginning of this list.
  • the user has not entered any elements into the body 404 and a pointer to body elements points to a null list.
  • Fig. 14 is an example showing the internal representation of Fig. 13 after some display elements have been added by the user.
  • the list now contains an image draw object for image 502 and a text draw object for text 504 (see Fig. 5).
  • Each draw object contains data specifying its location on the page as shown in Fig.
  • Fig. 15 is an example showing the internal representation after text display element 504 has been moved by the user. Note that the position of the text draw
  • paragraphs include a screen position field (indicating the X and Y coordinates of
  • Flags include whether the object has a frame drawn around it, whether the object may be
  • Draw objects can be of a variety of types or classes. It will be understood that the present invention does not necessarily include any specific types of draw objects and may include more or fewer types of draw objects than are discussed
  • hotspot polygon hotspot ellipse
  • each type of draw object has associated
  • Fig. 16(a) is an example of information associated with a draw object for a page banner. It includes a bitmap of the banner and the name of the page (e.g., "Products").
  • Fig. 16(b) is a first example of information associated with a draw
  • Fig. 16(c) is a second example of information associated with a draw object for a navigator button.
  • the link in the second example is a structural link, i.e., it represents a link according to relationships between the pages/nodes.
  • Fig. 16(c) includes a smart link to another node, which is specified by relationship, and an image. The identity of the link is determined (updated) when the page is
  • Fig. 16(d) is an example of a draw object for a text object. It includes a node number to which it will link when displayed by a browser, a name of the linked to page, and a string displayed in the text button.
  • each draw object contains its type, its X position, Y position, width, and height.
  • An example of a draw object of text and a draw object for an image is shown elsewhere in this document. It will be understood that each
  • type of display element in a page e.g., text, image, button, etc.
  • a type of display element in a page e.g., text, image, button, etc.
  • each draw object contains its type, its X
  • object contains information associated with its corresponding dialog box in which
  • Fig. 17 shows an example of a display used to allow the user to publish one or more pages. In the described embodiment, this display actually allows the user to publish all pages in a Web site.
  • Fig. 17 shows a screen displayed when the user clicks on "Publish” button 310 of Fig. 3.
  • the screen includes three buttons “Settings” 1702, “Stage” 1704, and "Publish” 1706.
  • the user can either "stage” or “publish” his site. Generally, staging is performed first and publishing is performed once the site is debugged. Staging and publishing are substantially the same, differing in when they are performed during the site development process. The user can also set configuration parameters to control the publishing or staging process. Clicking on either "publish" button 1706 or “Stage” button 1704 causes the described embodiment to generate HTML code for each page in the site (or only for pages indicated by the publish flag or by the user). This process is
  • Fig. 19 is a flow chart showing steps performed by page draw editor software 120 to publish a page of a site. It will be understood that the steps of Fig. 19 are performed by processor 102 executing instructions in page draw editor
  • step 1904 if the stacked flag of the current page object indicates that the current page is a stacked page, then processor 102 creates HTML for a plurality of pages. If the current page is not a stacked page then, in step 1908, processor 102 builds HTML for a "normal" page. In either case, the HTML for the page is then written to a storage medium of the system.
  • each page object has a corresponding list of draw objects describing the elements of the page layout, and that processor 102 generates HTML in accordance with the lists of draw objects.
  • each list of draw objects automatically includes draw objects representing automatically generated banners and links (e.g., to the home, parent, sibling, and/or children pages of that page). These automatic links may be structural links.
  • the draw objects of a page may also represent other, additional links added by the user that are not a part of the site hierarchy.
  • the user can use the page draw editor to remove some of the automatically generated draw objects links if he so desires. Unless the user explicitly removes them, however, these automatically generated links are present in each page layout.
  • each page will contain links to the home, parents, siblings, and/or children pages for each page of the site view.
  • Fig. 20 is a flow chart showing steps performed by the structure editor software to publish a normal page.
  • Fig. 21 is a flow chart showing steps performed by the structure editor software to publish a stacked page. The steps of Figs. 20 and 21 are similar, except that the steps of Fig. 21 generates multiple HTML pages
  • step 2002 creates initial HTML for the page as shown in Fig. 22. This step creates the beginning of an HTML page.
  • Steps 2004- 2008 create HTML tables for each of the header, body, and footer as shown in Figs. 23 and 24.
  • Step 2010 creates final HTML for the end of the page as shown
  • the preferred embodiment generates Netscape HTML version 3.X.
  • Fig. 21 shows the creation of a plurality of HTML pages for a stacked page.
  • Each HTML contains, for example, data for one record of a database associated with the stacked page.
  • Each of the plurality of HTML pages has a common format including the same fields of the database and the same layout of the fields.
  • Each page of the plurality of pages has the same format, but different data.
  • Step 2214 of Fig. 22 shows that the HTML for a page includes a tag
  • Fig. 23 is a flow chart showing steps to build an HTML table.
  • an HTML table is generated for the header, body, and footer of each page.
  • Steps 2302-2308 generate a matrix in memory 104 as discussed below in connection with Figs. 26-29.
  • Step 2312 create the HTML table in accordance with the matrix as shown in Fig. 24.
  • Fig. 24 shows steps that create an HTML table.
  • Step 2402 writes a table tag including a border of zero width and cellpadding and cellspacing of zero.
  • Step 2404 generates a table header including column and width definitions for the HTML table
  • Steps 2406-2418 go through each row and column of the matrix to generate a plurality of cells in the HTML table
  • Some of the cells in the HTML table can be several columns wide and/or several rows high
  • Step 2420 generates an end of table tag.
  • Fig. 26 is an example of first steps involved in determining an HTML table size for a layout element of a header, body, or footer
  • the layout element has four display elements Each display element corresponds to one draw
  • each draw object has an X position (a start row) and a length
  • Each draw object also has a Y position (a start column) and a height
  • a first column edge is the X start position and a second column edge is the X start position plus the length
  • a first row edge is the Y start position and a second row edge is the Y start position plus the height
  • Processor 102 finds the row edges and columns edges for a current page, yielding data 2602 and 2604
  • Fig 27 is an example of second steps involved in determining an HTML
  • the objects have six column edges and seven row edges Once the unique row edges and column edges are determined, the column widths and row heights for each column and row are determined
  • Fig. 28 is an example of a matrix 2802 generated in accordance with the edges and draw objects
  • Matrix 2802 has a number of rows equal to the number of row edges plus one.
  • the matrix has a number of columns equal to the number of column edges plus one.
  • the matrix has seven columns and
  • Each element 2804 of the matrix has a pointer field and an occupied
  • Fig. 29 is a block diagram of how the matrix 2802 is used to generate an
  • the HTML table is used by a browser to display a portion of a page on display device 160 (such as a header, body, or a footer. (An alternate embodiment of the present invention creates a single table for each page of the site).
  • Each element of the matrix is used to generate a cell in an HTML table (although some cells occupy more than one row or more than one column). For example, the matrix element in row 1 , column 1 causes an empty table cell to be generated.
  • Each row in the HTML table has a height in pixels that is equal to the
  • Each cell in the HTML table has a width that is equal to
  • column 5 causes generates of a cell that spans four
  • Fig. 30 shows an example of a Style display.
  • the display of Fig. 30 is shown when the user selects Style button 306.
  • the Style button display allows the user to select an overall default appearance of all pages in the site. The user can
  • the values shown in Fig. 30 are stored in locations of memory 104.
  • the automatic generation of banners, navigation buttons, and text buttons is performed in accordance with user-specified style values.
  • Fig. 31 shows an example of an Assets Display.
  • the Assets display shows i s the files, links, and objects in the data processing system.
  • the assets shown in Fig. 31 are the draw objects for the "Products" page of Fig. 5.
  • Fig. 32 shows an example of a plurality of link dialog boxes, showing a structural link, an internal link, and an external link.
  • Fig. 33 is a flow chart showing identification of structural links for a page.
  • the links preferably are identified when the page is displayed, previewed or
  • the processor finds the URL
  • present invention automatically creates draw objects for each page that reflects the user-defined layout.
  • the described embodiment When the user "publishes" a page, the described embodiment- generates HTML code for the page.
  • a page can also be a "stacked page.”
  • a single stacked page causes generation of a plurality of HTML pages. The page defaults to a user-specified "style,” which can be changed by the user.
  • BOOL Changed(void) void SetStretch( ⁇ INT) ; UINT GetStretch() ; virtual CRect GetlmagePosition(CRect *position NULL) ; virtual CRect GetImageSize() ; void SizeToI age(CLayoutView *p) .
  • BOOL HasPicture() ⁇ return m_pDIB ! NULL;) void mGenerateHTML(CPDBuffer* theBuffer) ; protected: int m_ImageHandle ; char * m_pDIB;
  • IDD IDD_PICTURE_ALIGNMENT ⁇
  • TJTEXT 0, // Dummy token just use to communicate that its a text token
  • T_UNDERLINEON // underline T_UNDERLINEOFF, T_STRIKE0UT0N, // strikeout T_STRIKEOUTOFF,
  • T_DUMMY1 // Raw html code. Used to insert HTML code directly into the token stream
  • T_FACE // Font face stored as T_FACE ⁇ name>
  • T_SIZE // Size of font; stored as T_SIZE [size]
  • T_C0L0R // Change to COLORREF color; stored as T__C0LOR ⁇ C0L0RREF> T_COLOR
  • T_HEADING // Heading marker; stored as T_HEADING [heading id] T_HEADING - should follow ⁇ P>
  • TJPARAFMT // Formatting belonging to T_PARAGRAPH - stored as T_PARAFMT ⁇ ParaFormat> T_PARAFMT
  • T_SYMB0L // Stores a symbol ⁇ T_SYMBOL> symbol value (int) ⁇ T_SYMBOL> TJHTMLT ⁇ G, // A HTML tag stored
  • T_PARAGRAPH // New paragraph T_SOFT EWLINE , // Soft end of line - autowrap symbol
  • T INKNAME // Link name stored as T_LINKNAME ⁇ di ⁇ play text T_LINKNAME2
  • T_LINKURL // Link URL stored as T_LINKURL ⁇ url>
  • BOOL bColorOverride i; // Is the color currently overridden short isize : 7; // 4 b
  • BOOL bltalic 1;
  • BOOL bstrikeout 1;
  • TALIGN_LEFT 0x01 ⁇ define TALIGN_CENTER 0x02 ⁇ define TALIGN_RIGHT 0x04 struct FindReplaceData ⁇ int iIndex;
  • BOOL getlndex // is index valid, if not then pos is valid - calc index in UpdateCaret int index; // index into m_text;
  • FontAttrib fa // FontAttrib for the start of the line after all heading and aling have been applied int iStyleldx; // Index of the style used int fFlags; // Flags for the line
  • MAX_FONT_LENGTH 256 Max size for a font face name
  • MAXJTEXT (65536 * 4)
  • MAX TEXT EDIT (MAXJTEXT - 1000)
  • WR ⁇ P_FIRSTLINE ⁇ define WRAP_LASTLINE
  • MAX_TEXT ⁇ define WRAP_UNDEFINED -1 extern BOOL I ⁇ Char( char c) ; extern BOOL IsToken( char c) ; extern BOOL WordDelimiter( char c) ; extern BOOL HardLineDelimiter( char c) ; extern BOOL LineDelimiter( char c) ; extern BOOL ParaDelimiter( char c) ?
  • BOOL bSelectAnchor // Are we currently selecting using achor point static CStringArray *m_FontFaceArray; // Font face list private: int m_needsWrap;
  • LinelnfoStruct * m_lineInfo // display lines int m_nLines; // used lines in above int m_maxLines; // ma no lines int m_hMar ; int m_vMarg; static CTextStyle *m_pTextProp; //property sheet belonging to object static BOOL bReturnFirstPara; //return a ⁇ P> at start of data
  • BOOL bRecordUndo // wheater to record or not in : :Insert and : :Delete CaretStruct m_caret[2]; //cursor/block location, if postions are the same, no marking
  • ExtFontAttrib mJFontSet // Settings set while gettextsegment traverses text ExtFontAttrib m__01dFontSet; // Compare copy for SelectFont int JTrueHeight; //true height of text, different than size when m_Locked is TRUE private: static COLORREF m_TextColor; static COLORREF JTextLinkColor; protected:
  • BOOL SetJavaEvent( int iJavaEventld); // External access methods COLORREF GetBackColor( void) ; void SetBackColor( COLORREF c) ; BOOL GetTransparent( void) ; void SetTransparent( BOOL t) ; BOOL GetLockedSize( void) ; void SetLockedSize( BOOL Is); BOOL IsStyleUsed( CString *psStyleName) ; void ResizeToOneLine( CLayoutView *pView, int ilndex 0); void Resize ⁇ bject( CLayoutView *pView, int ix, int iY) ; void GetWordCounts( int *pLine, int *pPara, int *pWord, int *pChars) ;
  • BOOL SelectFont ExtFontAttrib* fs, CDC *pDC) ; void AsciiSelectAll( void); void MouseSelectWord(CLayoutView* pView, UINT nFlags, const CPoint* point) ; void MouseSelectParagraph(CLayoutView* pView, UINT nFlags, const CPoint* point) ; void UpdateCarets( CLayoutView *pView) ; BOOL IsEmpty(); char NextChar(int* iStart) ; char PrevChar(int& iStart) ;
  • BOOL DeleteSelection( void) int ExtractAsciiToBuffer( char *pText, int ilndexl, int ilndex2 , int iLen) ; public: void Delete( int index, int count) ; private:
  • BOOL SkipJunk ( int* index, BOOL bForward) ; void UpdateCaret(char token, int iC, int nL, int iStart, int nChars, CPoint gpos, CDC *pDC) ; void UpdateSelectRegion( CLayoutView* pView) ; void RemoveSelectRegion( CLayoutView* pView) ; void FreeSelectRegion( void) ; void InvertSelectRegion( CDC *pDC) ;

Abstract

A method and apparatus for a draw-based Web page editor in which the user uses a 'drag and drop' interface to add, delete, and move display elements to define the layout of a Web page. The present invention automatically generates an initial layout for each page. This initial layout contains display elements that represent the links between pages of the site. After the user has defined the layout of the Web page, the user 'publishes' the page. The publish function automatically generates HTML for the page in accordance with the display elements of the page, yielding a true WYSIWYG page.

Description

DRAW-BASED EDITOR FOR WEB PAGES
FIELD OF THE INVENTION
This application relates to the World Wide Web and, in particular, to a method and apparatus for easily generating web pages on a "What You See is What You Get" (WYSIWYG) basis.
BACKGROUND OF THE INVENTION
The past several years have seen an explosive growth of the World Wide Web ("the Web"). The Web is built around a network of "server" computers, which exchange requests and data with each other using the hypertext transfer protocol ("http"). A human designer designs the layout of a Web page, which is then
specified using HTML ("Hypertext Markup Language"). Several versions of HTML are currently in existence. Examples include HTML versions 2.0 and 3.0, as specified by the WWW Consortium of MIT. Netscape Communications Corp. has specified additional HTML features that extend HTML forms and tables. A user views a Web page using one of a number of commercially available
"browser" programs. The browser submits an appropriate http request to establish a communications link with a Web server of the network. A typical http request references a Web page by its unique Uniform Resource Locator ("URL"). A URL identifies the Web server hosting that Web page, so that an http request for access to the Web page can be routed to the appropriate Web server for handling. Web pages can also be linked graphically to each other.
The HTML to describe a Web page is often created by hand by a human being. If the design of the page changes, the corresponding HTML must be rewritten, which is an exacting process. Although several conventional HTML- editors exist, these editors only allow the user to specify certain elements of a page and frequently still require the user to physically enter HTML code. Conventional HTML editors allow the user to specify the page content and general layout, but do
not provide the user with "What You See Is What You Get" (WYSIWYG) capability. Thus, the pages generated by conventional HTML editors look different when viewed by different browsers.
A Web "site" consists of a "homepage" and several other related pages. Each page has corresponding HTML that describes the appearance and function of the page. For example, the HTML for the homepage usually contains links to one or more of the other pages and the other pages often contain respective links back to the homepage. When the user clicks on a link of the displayed homepage, the browser requests and displays the linked-to page. Each link must be designed and coded into the HTML for the page. Thus, for example, when a human designer decides to remove a link between the homepage and another page, the HTML for the homepage must be changed to reflect the removed link. This
process is exacting and requires that the user manually change the link. Moreover,
if the linked-to page has another link back to the homepage, that link may also
need to be changed.
It is a common problem that not all browsers interpret HTML code in the
same way. For example, some browsers will automatically center a page title,
while others may left justify a page title. Similarly, horizontal and vertical spacing
may vary between browsers made by different companies.
It is usually desirable to have a consistent style for all pages of a site. When the user hand codes the HTML for each page of a site, it is difficult for the user to remember to use a consistent style. In addition, if the user decides to change the style of a site, each page must be changed individually. SUMMARY OF THE INVENTION
The present invention overcomes the problems and disadvantages of the prior art by using a drag and drop interface to allow a user to easily design a Web page. The user moves display elements to define the appearance of a web page. When the user clicks/selects a "publish" button, HTML code is automatically generated. A preferred embodiment of the invention generates an HTML table in
accordance with the display elements. The number and size of cells in the HTML table reflects the number and placement of display elements on the page, yielding a true WYSIWYG Web page. Because the generated HTML code is in the form of a table, the HTML will cause most browsers to display a page that has substantially the same layout, proportionality, coloring, and spacing as the layout of the page displayed by the page draw editor software. Initially, the present invention automatically generates a layout that is used for each page unless overridden by the user. Each page is initially generated in
accordance with "style" parameters chosen by the user.
In accordance with the purpose of the invention, as embodied and broadly described herein the invention is a method of allowing a user to define a World Wide Web page comprising the steps, performed by a data processing system, of: displaying a plurality of page display elements on a display device, the display elements forming a page layout on the display device; receiving an indication that the user wants to add a new display element to the page at a first position on the page, adding a new draw data structure in a memory of the data processing system for the new display element to a plurality of other draw data structures, the
draw data structures corresponding to the plurality of page display elements, where
the new draw data structure includes data representing the first position, and generating HTML that substantially reflects the displayed page layout on a pixel by pixel basis in accordance with the draw data structures
Advantages of the invention will be set forth in part in the description which follows and in part will be obvious from the descπption or may be learned by practice of the invention The advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims and equivalents
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are in and constitute a part of this specification, illustrate several embodiments of the invention and, together with the description, serve to explain the principles of the invention Fig. 1 is a block diagram of a computer system in accordance with a preferred embodiment of the present invention
Fig 2 is a block diagram showing input and output to and from page draw
editor software of Fig. 1.
Fig 3 shows an example of display view before the user has created any
display elements on the page.
Fig. 4 shows the display of Fig. 3, including a banner, navigator buttons,
and text buttons automatically created by a preferred embodiment of the present
invention. Fig. 5 shows the display of Fig. 4 after the user has dragged and dropped an image and some text into the layout.
Fig. 6 shows a preview display of the layout of Fig. 5.
Fig. 7 shows the display of Fig. 5 after the user has dragged and dropped the text to a different location on the page.
Fig. 8 shows a preview display of the layout of Fig. 7.
Fig. 9(a) shows a detail of a tool window of Fig. 3.
Fig. 9(b) shows a portion of the tool window displayed in connection with an Image tool.
Fig. 9(c) shows a portion of the tool window displayed in connection with a Forms tool.
Fig. 9(d) shows a portion of the tool window displayed in connection with a Draw tool.
Fig. 10(a) shows a Page tab in a Properties window of Fig. 3.
Fig. 10(b) shows a Layout tab in the Properties window of Fig. 3.
Fig. 10(c) shows a Rectangle tab in the Properties window of Fig. 3.
Fig. 10(d) shows a Text tab in the Properties window of Fig. 3.
Fig. 10(e) shows an ActiveX tab in the Properties window of Fig. 3.
Fig. 10(f) shows a Java APPLET tab in the Properties window of Fig. 3.
Fig. 10(g) shows a Shockwave tab in the Properties window of Fig. 3.
Fig. 10(h) shows a Table tab in the Properties window of Fig. 3.
Fig. 11 (a) shows a first pull-down menu.
Fig. 11(b) shows a second pull-down menu.
Fig. 11 (c) shows a third pull-down menu. 5 Fig. 12 is a flow chart showing steps performed by the page draw editor software to define a page layout.
Fig. 13 is an example showing an initial internal representation stored in a memory of objects automatically generated on the page by the page draw editor software for the layout of Fig. 4. ι o Fig. 14 is an example showing the internal representation after some display elements have been added by the user.
Fig. 15 is an example showing the internal representation after a display element has been moved by the user.
Fig. 16(a) is an example of a draw object for a page banner.
15 Fig. 16(b) is an example of a first draw object for a navigator button.
Fig. 16(c) is an example of a first draw object for a navigator button. Fig. 16(d) is an example of a draw object for a text button. Fig. 17 shows an example of a display used to allow the user to publish the pages of a site. 20 Fig. 18 shows an example of a display used to allow the user to specify details of how to publish a site.
Fig. 19 is a flow chart showing steps performed by the page editor software
to publish a page.
Fig. 20 a flow chart showing steps performed by the page editor software 25 to publish a normal page.
Fig. 21 is a flow chart showing steps performed by the page editor software to publish a stacked page.
Fig. 22 is a flow chart showing steps performed by the page editor software to generate initial HTML for a page.
Fig. 23 is a flow chart showing further steps performed by the page editor
software to generate an HTML table for layout elements of a page, such as a
header, body, and footer.
Fig. 24 is a flow chart showing steps performed by the page editor software
to generate an HTML table.
Fig. 25 is an example of steps performed by the page editor to generate final HTML for a page.
Fig. 26 is an example of first steps involved in determining an HTML table
size. Fig. 27 is an example of second steps involved in determining an HTML
table size.
Fig. 28 is an example of a matrix generated by the steps of Figs. 26 and
27.
Fig. 29 is a block diagram of how the matrix of Fig. 28 is used to generate
an HTML table, which a browser uses to display a portion of a page.
Fig. 30 shows an example of a Style display.
Fig. 31 shows an example of an Assets Display.
Fig. 32 shows an example of a plurality of link dialog boxes, showing a structural link, an internal link, and an external link.
Fig. 33 is a flow chart showing updating of structural links for a page.
Fig. 34 shows an example of a dialog box used to create a data object.
Fig. 35 shows a block diagram of an example of a stacked page and a
series of data pages. Fig. 36 shows an example of an icon for a stacked page.
Fig. 37 shows an example in which a user has opened the Tool window and selected the DataList tool.
Fig. 38 shows a Properties window with a DataList tab opened for the DataList tool and the DataList window. Fig. 39 shows a further example of a Properties window with a DataList tab.
Fig. 40 shows an example in which a user has opened the Tool window and selected the DataField tool.
Fig. 41 shows a Properties window with a DataField tab opened for the DataList tool.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
Reference will now be made in detail to a preferred embodiment of the invention, an example of which is illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
I. System Overview
Fig. 1 is a block diagram of a computer system 100 in accordance with a
preferred embodiment of the present invention. Computer system 100 includes a
CPU 102; a memory 104; input/output lines 105; an input device 150, such as a keyboard or mouse; and a display device 160, such as a display terminal.
Computer 100 also includes an input device 161 , such as a floppy disk drive or CD
ROM reader, that reads computer instructions stored on computer readable medium 162, such as a floppy disk or a CD ROM. These computer instructions are the instructions of e.g., page draw editor software 120. Memory 104 includes page-
draw editor software 120, draw objects 130, HTML 140, and image files 140, etc., as described in further detail below.
A person of ordinary skill in the art will understand that memory 104 also
contains additional information, such as application programs, operating systems, data, etc., which are not shown in the figure for the sake of clarity. It also will be understood that computer system 100 can also include numerous elements not shown in the Figure for the sake of clarity, such as disk drives, keyboards, display devices, network connections, additional memory, additional CPUs, LANs, internet connections, input/output lines, etc. In the following discussion, it will be understood that the steps of methods and flow charts discussed preferably are performed by processor 102 executing
instructions stored in memory, such as instructions of editor software 120. Editor software 120 can be initially loaded into memory from computer readable medium 162. It will also be understood that, although the following paragraphs describe an implementation of the present invention using object-oriented programming techniques, the invention is not limited to any such techniques and may be implemented using any appropriate techniques for implementing the functionality described herein. The described embodiment is written in the C++ programming language and runs under the Windows 95 operating system, but the invention is
not limited to any particular programming language or operating system.
("Windows 95" is a trademark of Microsoft Corporation.) II. Creation and Manipulation of a Web Page Layout
Fig. 2 is a block diagram showing input and output to page draw editor software 120 of Fig. 1. Page draw editor 120 includes a portion 202 that creates and manages a page layout and a portion 204 that publishes the page 140. The
user uses a drag and drop interface to define the page layout. Pages can include new text and images or preexisting text and images. The user initiates publish portion 204 by clicking on a "publish" button displayed by the editor 120, as
described below. Publish portion 204 generates HTML for the page, as also
described below. The page is translated into an HTML table that yields a WYSIWYG Web page when displayed by a browser. A. Creating and Modifying Display Elements of a Page Layout
Fig. 3 shows an example of a page view displayed on display device 160 before the user has created any display elements on the page. The display of Fig.
3 is opened when the user indicates (using a pull-down menu or the like) that he wishes to create a new page. In the described embodiment, the user clicks on a "Page" button 304 in the navigator bar. The page draw editor allows the user to
design a page just as it will appear when viewed with a browser. The user uses the page draw editor to add text graphics, and other display elements to the page.
The user can then rearrange display elements by dragging and dropping them to a new location, placing the display elements exactly where they will eventually appear with pixel level accuracy.
A title 301 of the page defaults to "Untitled" if the user has not yet named the page. Fig. 3 includes a grid of lines. These lines are shown as dotted lines, but can also be solid lines. In the described embodiment, the grid also can be turned off so that no grid is displayed. The grid preferably is not included in the generated HTML. In Fig. 3, the grid has a granularity of 24 x 24 pixels in accordance with a default width as shown in a Properties window 350, as discussed below.
The display of Fig. 3 includes a plurality of buttons: a "Site" button 302, "Page" button 304, a "Style" button 306, an "Assets" button 308, and a "Publish" button 310. The display also includes a "Preview" button 312, a "New Page" button 314, a "Goto" button 316, and a "Last" button 318. Site button 302 causes execution of a "site editor". Style button 306 and Assets button 308 are discussed below. New Page button 314 causes a page such as the page of Fig. 3 to be
displayed.
Goto and Last buttons 316, 318 transfer control to a most recent display or a user-selected previous display, in a manner known to persons of ordinary skill in the art. The described embodiment keeps a "history" of execution of page draw editor 120 in order to implement the Goto and Last buttons.
The display of Fig. 3 further includes a Secondary navigator bar 365, including a "Layout View" button 320 and an "HTML Source" button 322. When the user clicks on Layout View button 320, a display having a format such as that of
Figs. 3-8 is displayed. When the user clicks on HTML Source button 322, a display (not shown) shows the HTML that is generated for the current page layout. Button
322 is omitted in an alternate embodiment. Other views have other buttons and
toggle switches on the secondary navigator bar, as required by the particular view.
Secondary navigator bar 365 contains a dotted line extending vertically downward from a currently clicked button (e.g., Page button 304) to a selected one of the
buttons on secondary navigator bar 365. As the user selects different buttons on
the primary and secondary navigator bars, the dotted line is redrawn to connect the currently selected buttons. This feature makes it easy for a user to see which buttons are currently selected and to mentally connect the functions of the primary
and secondary navigator bars.
Fig. 3 also shows "Properties" window 350 in which a "View" tab is selected. Properties window 350 includes three tabs: a "View" tab 352, a "Page" tab 354, and a "Layout" tab 356. The values shown in Properties window 350 are values for the current page. Properties window 350 currently shows view properties because View tab 352 is selected. Figs. 10(a) and 10(b) show examples of the Page and Layout tabs, respectively. A fourth tab (see, e.g., Fig. 10(c)) is a context sensitive tab and represents various properties, depending on the tool being used. Other tabs may appear in other implementations.
The values shown in Properties window 350 of Fig. 3 are the default values for viewing a newly created page. Properties window 350 includes a "Measurement Unit" area 360, a "Element border" flag area 362, "Grid Width" and "Grid Height" areas" 364, 366, a "Show Grid" flag 365, font size areas 368, 370, a "Color" area 372, a "Horizontal Splitter" flag area 374, and a "Snap to Grid" flag
area 376.
Thus, in the example, the grid is measured in units of pixels. Element
borders are drawn around each display element on the display device.
A grid of 24 x 24 pixels is displayed. The specified fonts are used. The page uses
the colors described in the colors area 372. The "Snap to Grid" property is turned
off. It will be understood by persons of ordinary skill in the art that page draw editor
software 120 stores values corresponding to this Property window and each
Property window discussed herein in memory 104. All values in Properties window 350 may be changed by the user. Values in memory 104 will be changed accordingly.
The display of Fig. 3 further includes a "Tools" window 324. As shown in
Fig. 9(a), Tools window 324 includes a "cursor" tool 380, a "zoom in" tool 381 , and a "zoom out" tool 382. These three tools have an outward operation similar to "cursor," "zoom in," and "zoom out" tools known in the art. The "cursor," "zoom in,"
and "zoom out" tools are collectively known as "control tools."
Tools window 324 also contains a "Text" tool 383, an "Image" tool 384, a "Draw" tool 385, a "Table" tool 386, an "Audio" tool 387, a "Video" tool 388, a "Java" tool 389, an "ActiveX" tool 390, a Shockwave tool 391 , a "Form" tool 392, a "DataList" tool 393, and a "DataField" tool 394. The Text, Image, Draw, Table,
Audio, Video, Java, ActiveX, Shockwave, Form, DataList, and DataField tools are collectively known as "content tools." (Java is a trademark of Sun Microsystems, Inc. Shockwave is a trademark of ShockWave Corp. ActiveX is a trademark of Microsoft Corporation.) Tools window 324 also includes a plurality of buttons 395
that contain various buttons at various time, as discussed below in connection with
various ones of the tools.
It will be understood that the empty page of Fig. 3 can be edited in the
same manner described below for an existing page.
Fig. 4 shows the display of Fig. 3, including a banner, navigator buttons, and text buttons automatically created by a preferred embodiment of the present invention. The example of Fig. 4 is displayed after the user indicates that he wants
to edit an existing page by preferably: 1) double clicking on an icon for the page
(not shown) or 2) selecting a page icon and clicking "Page" button 304 of Fig. 3 (not shown). The described embodiment of the present invention automatically
creates certain draw objects in memory for the page. The automatically created draw objects reflect links between pages of the site, as described below in the copending application. The user can easily create and move display elements on the page, which causes changes to corresponding draw objects in memory 104. Horizontal splitters such as 380 and 382 are displayed.
The display of Fig. 4 creates a page having three parts: a header 402, a body 404, and a footer 406. The user can move the dividers 380, 382 between the header, body and footer as is known in the art. Moving the dividers adjusts the
size of the header, body or footers on the finished page. The header, body and footers can also be scrolled. Page draw editor 120 allows individual scrolling in each of these parts. In the described embodiment, the page of Fig. 4 is entered from the site view, and automatically creates display elements of header 402 and footer 406 reflecting the logical connection of the current page to other pages.
Header 402 automatically contains a banner 410 and a plurality of navigator buttons 412. In the example, the banner contains the name of the selected page ("Products"), Navigator buttons 412 include buttons for a homepage ("Home button 4), a "Welcome" page ("Welcome" button 416), and a "Private" page ("Private" button 418). Navigator buttons 412 preferably include an image, such as
the 3D button image shown in Fig. 4. This image may be predefined or defined by
the user through use of a pop-up window.
Thus, in Fig. 4, the navigator buttons 412 automatically include buttons corresponding to the home page and to the previous hierarchical level of the page.
Alternate implementations of the present invention automatically display navigator buttons for one or more of the home page, the parent page, sibling pages, and children pages. In some embodiments, the user chooses which navigator buttons are generated automatically by way of a pop-up site window. The user may add or
delete additional buttons and may move buttons, as described below.
Footer 406 automatically contains a plurality of text buttons 428. These text buttons preferably correspond to the navigator buttons 412. Thus, text buttons
428 include buttons for the homepage ("Home text button 430), the Welcome page 452 ("Welcome" text button 432), and the "Private" page 454 ("Private" text button 434). The user may add or delete additional buttons and may move buttons, as described below. The internal memory representation of banner 410 and of buttons 412 and 430 are discussed in detail below.
Figs. 5-8 show an example of creation of display element in a page layout and also show an example of a modification to the page layout using a drag and drop interface in accordance with the described embodiment of the preferred
invention. Fig. 5 shows the display of Fig. 4 after the user has dragged and dropped an image 502 and some text 504 into the layout. Specifically, as discussed in detail below, the user creates image 502 using Image tool 382 and creates text 504 using Text tool 383. In the example, image 502 is a 324 x 216 pixel image originally stored in memory or on a storage device attached to computer system 100. Fig. 6 shows a preview display of the layout of Fig. 5. Fig. 5 is displayed when the user clicks on Preview button 312 of Fig. 3 (or selects "Preview" from a pull-down menu). In order to preview a site, page draw editor 120 actually generates HTML for the current layout of the page and stores it at a predetermined (or user-defined) location. The editor then invokes a browser program (such as the-
Netscape Navigator browser, version 3.x, manufactured by Netscape Communications Corp. of Mountain View, California). The browser displays a Web page 602 described by the generated HTML. Note that no HTML is generated for
dividers 380, 382 and that no HTML is generated for the outlines around the text
and image.
Fig. 7 shows the display of Fig. 5 after the user has dragged and dropped the text to a different location on the page. Specifically, as discussed in detail
below, the user places a cursor on text 504 using input device 150 (such as a mouse) and drags the text to a new position using input device 150. Movement of a display element on a display device in accordance with cursor input is known in the art and will not be described herein. The draw object associated with text 504 is changed to reflect this movement as described below.
Fig. 7 also shows Properties window 350 in which "Layout" tab is selected. The values shown in Properties window 350 are values for the current page. Properties window 350 (with a Layout tab) includes a "Layout Name" area 702, a
"Width" area 704, a "Height" area" 706, a "Site Style Background" 708, a "Solid Color" area 710, a "Picture" area 712, a "Head Name" area 714, and a "Footer Name" area 716.
Thus, in the example, Layout of Fig. 7 is currently untitled. The layout is of the specified height and width. The page uses the type of background described in areas 708-712 (i.e., a predetermined "Site style background", such as a picture of a marbled surface) instead of a solid background or a image background provided by the user. It will be understood by persons of ordinary skill in the art that page draw editor software 120 stores values corresponding to this Property window and each
Property window discussed herein in memory 104. All values in the Properties window 350 of Fig. 7 may be changed by the user. Values in memory 104 will be changed accordingly.
Fig. 8 shows a preview display of the layout of Fig. 7. As shown in Fig. 7,
the user has dragged and dropped text 504 to a new location, thus changing the page layout. The Preview function causes new HTML for the changed page layout to be generated and the new HTML to be displayed by the browser in window 602.
It will be understood that, in the Preview views of both Figs. 6 and 8, the HTML generated for the page causes a browser to display a page that is pixel-per-pixel the same as the display elements on the display screen, assuming that the browser supports Netscape version 3.X. Thus, the user can design a page layout and expect the page to look exactly as it was designed when the page is displayed by a
browser. Tag 802 is an optional line resulting from HTML generated in the described embodiment of the present invention. 1. The Pull Down Menus
Figs. 11 (a) through 11 (c) show examples of pull-down menus for the described embodiment of draw page editor 120. Fig. 11 (a) shows an Edit menu having an Undo function, a Cut function, a Copy function, a Paste function, a Paste Special function, a Delete Page function (A delete display element function is not shown), an Options function, a Preferences section, and a Duplicate Layout
function, which duplicates a current page layout (and its associated draw object data structures) for a new page.
Fig. 11(b) shows a View pull-down menu, which includes a Page Properties function that opens, e.g., Properties window 350 with a page tab selected, and Tools Palette function that opens, e.g., Tools window 324.
Fig. 11(c) shows a Layout pull-down menu, which includes an Align Objects function that horizontally, vertically, or centrally aligns display elements, a Center Objects function that centers display elements, a Size Objects function that sizes display elements, an Element Script function, and a Layout script function.
2. The Tools Window
Figs. 9(a) through 9(d) show examples of Tool window 324 and show various icons that are displayed in area 395, depending on which tool is being used. Some of the tools of the described embodiment can be thought of as a Swiss army knife; when you select one, a secondary group of tools appears in area 395, each secondary tool performing a different function on the same kind of display element.
3. The Text Tool
When the user clicks on Text tool 383, page draw editor 120 allows the user to enter a text display element. The user uses the cursor to create and size a text box on the display and then types text inside it. When text is created, a Text tab shown in Fig. 10(d) is displayed in the Properties window 350. This Properties window allows the user to enter properties of the text display element. These properties include whether the text is bold, italic, or has a strike-out bar, the font, the font size, paragraph alignment, and whether to use a bullet. The properties further include whether to use a predetermined "site style" for the text (i.e. , a
predetermined font, color, size, etc. stored in memory 104 under a "site style name") or whether to use a user-specified text color. The user may also specify a fill color for the text box. If the user indicates that the text box is also a link, he may also fill in the name of an associated script (e.g., a CGI script). Once the link is
created, the location of the link is added to a list of hotspot locations stored in memory and values are stored in the text draw object to indicate that the text contains a hot spot and its URL. Once the user has specified the text, a text draw object is added to the list of draw objects. Currently, not all browsers support 5 custom fonts. Netscape Navigator 3.0, however, supports such custom fonts and other browsers are expected to do so in the future.
4. The Image Tool
When the user clicks on Image tool 384, page draw editor 120 allows the user to specify an image display element. Unlike the text boundary, the image i o boundary resizes to fit a user-specified image. Once the image has been added to the display, the user can create a link on all or part of the image or select one color in the image as transparent. The user can also change the size of the image using the cursor.
When the user clicks on Image tool 384, page draw editor 120 displays a
15 Draw tab (not shown) in properties window 350 in addition to the tabs shown in Fig.
3 and alters the Tool Window 324 as shown in Fig. 9(b). This Properties window allows the user to enter a name of an existing image and various properties of the
image, such as whether the image is transparent, whether a fill background should be added to the image, and whether the image contains a link (e.g., a URL).The
20 image tool has five secondary tools, shown in Fig. 9(b). Tool 3050 allows the user to draw a boundary in which to place the image file. Tool 3052 allows the user to click on a color of the image that he wants to be transparent. When the image is displayed, pixels of that color in the image will be suppressed so that the background will show through. (This means that a new image with a transparent
25 color must be generated when the HTML is generated). A flag in the Image draw object is set to indicate transparency.
Tools 3054-3056 allow the user to specify a "hotspot" on the image having different shapes. The user can create a rectangular, circular, or polygon hotspot. The user draws and sizes the hotspot on the display using the cursor and identifies the link/URL for the hotspot using a pop-up window (hot shown). Once the hotspot
is created, it is represented in the display by slightly distorting the image in the hotspot area The hotspot is added to a list of hotspot locations stored in memory
and values are stored in the object to indicate that the image contains a hot spot
and its URL Once the user has specified the image, the image is displayed (e g ,
image 502 of Fig 5) and an image draw object is added to the list of draw objects
5. The Draw Tool
When the user clicks on Draw tool 385, page draw editor 120 allows the
user to enter a Draw display element The Draw tool has five secondary tools 395,
shown in Fig 9(d). rectangle 1950, round rectangle 1952, ellipse 1953, line 1954, and polygon 1955 When the user clicks on Draw tool 385, the page draw editor displays the secondary draw tools 395 of Fig 9(d) The user can then choose a
secondary draw tool If, for example, the user selects rectangle 1950, a rectangle
Draw tab (see Fig 10(c)) appears in Properties window 350 in addition to the tabs
shown in Fig 3 Similar tabs appear when the other secondary draw tools are
selected The Polygon tool allows the user to draw a polygon using the cursor, as
is known.
In the example, Properties window 350 allows the user to enter properties
of the rectangle, such as the color of the rectangle, the border color and size of the rectangle, any text inside the rectangle (and its properties), whether a fill
background should be added to the image, and whether the image contains a link
(e g , a URL) Once the user has specified the shape, the shape is displayed on
the screen and an image draw object is added to the list of draw objects In the described embodiment, each type of draw element has a different type of draw object.
6. The Table Tool
When the user clicks on Table tool 386, the page editor 120 allows the user to enter a table in the display. The Table tool causes a table window to be opened (see Fig. 10(h)). When the user clicks on Table tool 386, the page draw editor displays a "table" tab in Properties window 350 of Fig. 10(h). The user can then specify the dimensions of the table. For example, the user can specify the number of columns, the number of rows, and the type of object that goes in each cell of the table. Once the user has specified the table, the table is displayed on the screen and a table draw object is added to the list of draw objects. A table layout element cause a table to be generated inside a table when HTML is generated for the page.
7. The Sound Tool
When the user clicks on Sound tool 387, page draw editor 120 allows the user to draw a boundary in which to place an icon as a visual placeholder for an
audio file. The audio file is specified through a Properties tab (not shown). In the
final published Web page, users can click the icon to hear the audio. Once the
user has specified the audio icon and an associated sound file, the audio icon is
displayed on the screen and a sound draw object is added to the list of draw
objects.
8. The Video Tool
When the user clicks on Video tool 388, page draw editor 120 allows the user to draw a boundary in which to place an icon as a visual placeholder for a video file. The video file is specified through a Properties tab (not shown). In the- final published Web page, users can click the icon to see the video. Once the user
has specified the video icon and an associated video file, the video icon is displayed on the screen and a sound draw object is added to the list of draw objects. 9. The Java Tool
When the user clicks on Java tool 389, page draw editor 120 allows the user to specify a Java applet and an address for the applet. The Java tool, the ActiveX tool, and the Shockwave tool all specify display elements that are exemplary of a type of display element called a "plug-in." Java applets are small programs that can be downloaded over the web and run on most computer platforms. The described embodiment allows the user to specify an icon for a Java applet and the location of the Java applet similarly to how the user specifies a sound or video icon and file. When page is displayed by a browser and the user
clicks on the Java applet icon, the Java applet will be downloaded and executed. The user specifies a Java applet and icon through use of a Java tab in
Properties window 350 (see Fig. 10(f)). This Properties window allows the user to
specify a class of applet, to browse through a plurality of predefined applet names,
to review parameter information for the selected applet name, to specify an alternate tag for the Java icon, and to specify a script. Once the user has specified
the Java icon and an associated address, the Java icon is displayed on the screen
and a Java draw object is added to the list of draw objects.
10. The ActiveX Tool
When the user clicks on ActiveX tool 390, page draw editor 120 allows the user to specify an ActiveX file and an address for the file. ActiveX files are small programs that can be downloaded over the web and run on most computer platforms. The described embodiment allows the user to specify an icon for an ActiveX file and the location of the ActiveX file similarly to how the user specifies a
sound or video icon and file. When page is displayed by a browser and the user clicks on the ActiveX file icon, the ActiveX file will be downloaded and executed.
The user specifies an ActiveX applet. The user has specified the ActiveX icon and an associated address, the ActiveX icon is displayed on the screen and an ActiveX draw object is added to the list of draw objects. 11. The Shockwave Tool The user specifies a Shockwave video file through use of a Shockwave tab in Properties window 350 (see Fig. 10(g)). This Properties window allows the user to browse a plurality of file names, to specify an alternate tag. Once the user has specified the Shockwave file, a predetermined Shockwave icon is displayed on the screen and a Shockwave draw object is added to the list of draw objects.
12. The Forms Tool
When the user clicks on Forms tool 392, page draw editor 120 allows the
user to specify elements of an HTML form. As is known, forms are an interactive
Web component. They allow a user to send data to a server, either as request for
more data or as a submission of information to the server. As is known, forms are
controlled by CGI scripts.
The Forms tool has six secondary tools 395, shown in Fig. 9(c): button
1950, checkbox 1952, radio button 1953, single line text 1954, multi-line text 1955,
and list box 1956 (also called a "pull-down menu"). When the user clicks on Forms tool 392, the page draw editor displays the secondary draw tools 395 of Fig. 9(c).
The user can then choose a secondary draw tool. If, for example, the user selects
button 1950 and clicks in the display window for the page, a button display element is added to the page. In addition, a button tab (not shown) appears in Properties window 350 in addition to the tabs shown in Fig. 3. Similar tabs appear when the other secondary draw tools are selected.
Using the example of a forms button, Properties window 350 allows the user to enter properties of the button, such as the color, any text inside the button (and its properties), and whether a fill background should be added to the button. In addition, the user decided whether the button is Submit button or a reset button.
During display, a submit button sends the contents of all the form objects to a server. A reset button allows the user to clear the form and start over.
The following paragraph describes, without limitation, other examples of
the various forms elements that can be specified by the user. Each of the forms elements described below is an element of a type that is currently included in conventional hand-coded HTML forms. Other embodiments may include still other form elements not described herein. A check box is used to let users select one or
more items from a group. (Editor 120 allows the user to specify what these
elements are.) A radio button behaves just like a check box, except that only one
radio button in a group an be checked at once. A single-line text provides an area
where the user can enter a single line of text. A multi-line text provides an area
where the user can enter a more than one line of text. A list box takes the form of
a pop-up menu or a box with a scroll bar. Editor 120 allows the user to specify the form of a list box. Once the user has specified a form element, the video icon is displayed on the screen and a form element draw object is added to the list of draw objects. In the described embodiment, each type of form element has a different type of draw object. The described embodiment allows one form in the header,
one form in the body, and one form in the footer. This is because the form layout
elements do not contain an identifier as to which form they belong to. Other implementations may contain such an identifier and may allow multiple forms in the header, body, or footer.
13. Managing Assets (Files, Links, and Data Objects) Fig. 31 shows an example of an Assets display 3100 that displays all current files, links, and data objects for a data processing system. The display 3100 is generated when the user clicks on Assets button 308 of Fig. 3. (Note that a dotted line extends from the Assets button to the Secondary navigator bar 365.) The Assets view shows all files, hyperlinks, or data objects associated with the current system, depending on whether the user clicks secondary button 3102,
3104, or 3106. Fig. 31 shows an example of all data objects for the page of Fig. 5. It will be understood that the Assets view reflects files, links, and data objects stored in memory 104. Newly created files, links, and data objects are stored in memory 104 as well.
The File view shows information about all files in the site, such as: whether the file has a type of navigation bar images, pictures, sound, video, Java applets and other plug-ins. The user can change, e.g., the name and location of files and can add and delete files through user of a dialog box (not shown).
The Links view shows information about all links in the site, such as: whether a link is internal, external, or structural. A structural link reflects a hierarchical link shown in the site view. In a preferred embodiment changing a structural link in the Assets view changes the link in the site view and between
page objects in the memory. The user can change links and can add and delete links through use of a dialog box (not shown).
The Data Objects shows information about all DataObjects in the system.
Data objects can be internal data objects or can be ODBC (Object Data Binding
Convention) objects implementing Microsoft's standard for web page/database
binding. Before creating a stacked page, as discussed below, the user should first
create an internal object or ODBC object for the data that is to be included in the
stacked page.
Fig. 34 shows an example of a dialog box 3400 used to create a data object. Dialog box 3400 is displayed when the user clicks on a "new object" button (not shown) or clicks on a "new object" pull-down menu (not shown). Box 3400
includes a data object name area 3402, a data object delete button 3404, an add
field button 3408, an area 3410 listing the current fields of the data object, a "get
index field" button 3412, a set button 3414, and move up/down buttons 3416,
3418. To create a data object in memory 104, the user enters information in dialog
box 3400.
14. Creation of Stacked Pages
The described embodiment allows the user to create a special type of page
called a "stacked page," which is made up of "data pages." A stacked page
causes the described embodiment to generate a plurality of HTML pages
displaying a series of information, such as a the values in a series of records from a database. Fig. 35 shows a block diagram of an example of a stacked page 3502 and a series of pages 3504 displayed when a browser views the HTML pages created from the stacked page. To create a stacked page, the user first creates a data object, such as a data base object (as described above). The user then
creates a DataList draw object and a DataField draw object for the stacked page.
To create a DataList draw object, the user clicks on DataList tool 393 of Fig. 3. Page draw editor 120 allows the user to specify a list of fields to be displayed on a stacked page. When the user clicks on DataField tool 394, page draw editor 120 allows the user to specify the layout of the fields in the data list. Once the user has specified a DataList and a DataField, an appropriate display element is displayed on the screen and a DataList draw object or a DataField draw object, respectively, is added to the list of draw objects for the page.
The following paragraphs describe an example of creation of a stacked
page. Fig. 36 shows an example of an icon for a stacked page that is displayed by the site level editor described in the co-pending application of Arora et al. Once a page includes a DataList and a DataField object, it is classified as a stacked page. When a page is a stacked page, it is displayed at the site level as overlapping pages icon 3602. Stacked pages are moved at the site level in substantially the same manner as normal pages. However, multiple HTML pages are generated for
each stacked page.
Fig. 37 shows an example in which a user has opened Tool window 324 and selected DataList tool 393. The user has then specified a rectangle 3704.
Fig. 38 shows a Properties window 350 with a DataList tab 3802 opened
for DataList tool 393. Fig. 38 also shows a DataList window 3802. The user specifies, in the DataList window 3803, fields of the list that can be displayed on
2 P the stacked page (for example, "Headline List"). The user then clicks on the listed-
DataList fields to select which fields of the data object will be included in the stacked page. The properties of the DataList are displayed in Properties window 350.
In DataList window 3803, the user optionally specifies a sort field 3806 in
the data object, and optionally sets a filter 3808 (e.g., product = "xxx," not shown).
Only values in the specified fields having the filtered value will be part of the stacked page. The user may also specify whether any of the fields will be linked to other pages. Fig. 40 shows "Data List Tab" in Properties window 350.
Fig. 40 shows an example in which a user has opened Tool window 324 and selected DataField tool 394. The user has then specified a rectangle 4004.
The user names the data list ("Headline List") and defines an appearance of the fields selected in Fig. 38. An area for each field can be sized and dragged to define the layout of each data page in the stacked page.
Secondary navigator bar 365 includes a button bar 4006 that has four buttons for managing data pages within a stacked page. These four buttons
include: a "+" button, which creates a new data page, a "-" button, which deletes
the current data page, a "back" button which displays the contents of a previous data page, and a "forward" button, which displays the contents of a next data page.
In, for example, a data base, the user can create as many data pages as there are
records in the data base. Each data page will automatically contain display elements to a first, next, and previous data page. Thus, a stacked page has a list
of draw elements. An example of such as draw element may have a structural link
to the "next" or "previous" data page. If the page is a stacked page, a flag in 5 memory is set to indicate this fact, since multiple HTML pages can be generated for a single stacked page (i.e., one HTML page for each data page). B. Creation of Draw Objects for the Display Elements
Fig. 12 is a flow chart showing steps performed by page draw editor software 120 to edit a page layout during execution of the page draw editor. In l o step 1202, the page draw editor determines whether the page is a new page. If it is an existing page, in step 1204, the current page layout for the page is displayed in accordance with the already existing draw objects for the page. The page layout will include the automatically generated banner, navigator buttons, and text buttons, unless the user has previously deleted them.
is If the page is a new page, in step 1206, the editor displays the default page layout in accordance with the draw objects for the page. The user exits the page draw editor by, e.g., clicking on Site button 302, Style button 306, Assets button 308, or Publish button 310 (or by selecting "exit" from a pull-down menu). After the user has edited a page, he can still move the page around in the site
20 hierarchy by using the structure/site editor, as described in the co-pending application of Arora et al.
Fig. 13 is an example showing an internal memory representation of draw
objects automatically generated by page draw editor software 120. The draw
objects are generated when a page is created and are modified when the page is
25 modified. The internal representation includes a list of draw objects, representing each display element of the page of Fig. 4. Thus, the list of draw objects includes a banner draw object 1302 (corresponding to banner 410), a navigator buttons draw object 1304 (corresponding to navigator buttons 412), and a text buttons draw object 1306 (corresponding to text buttons 428). In the described embodiment, all draw objects of the header 402 are stored together and a pointer points to the beginning of this list. Similarly, all objects of the footer 406 are stored together and
a pointer points to the beginning of this list. In the described embodiment, the user has not entered any elements into the body 404 and a pointer to body elements points to a null list. There are other elements in the layout elements list (such as border elements) that are not shown for the sake of ease of explanation.
Fig. 14 is an example showing the internal representation of Fig. 13 after some display elements have been added by the user. The list now contains an image draw object for image 502 and a text draw object for text 504 (see Fig. 5). Each draw object contains data specifying its location on the page as shown in Fig.
5. If the image or text is also a hotspot, information identifying the URL of the link is also contained in the object.
Fig. 15 is an example showing the internal representation after text display element 504 has been moved by the user. Note that the position of the text draw
object does not change in the list of draw objects. However, the position data in the text object does change to reflect the object's new position in the page layout. Similar changes are made to other page objects whenever the user alters the
position, appearance, or function of the corresponding display element with the
page editor 120.
It will be understood that all draw objects discussed in the following
paragraphs include a screen position field (indicating the X and Y coordinates of
the objects' current position on the screen), the height and width of each draw
object on the screen, and various flags associated with display of the object. Flags include whether the object has a frame drawn around it, whether the object may be
resized to zero width or height, whether the object itself handles mouse commands internally, whether the object is currently selected, the color of the object, whether the object is transparent, whether the object contains text, etc. It will be
understood that the specific flags stored in an object may vary from implementation
to implementation. The position, height, width and flag values are not shown for
the sake of clarity. It will also be understood that each type of draw object contains
the data required to describe the appearance and function of the corresponding
display element.
Draw objects can be of a variety of types or classes. It will be understood that the present invention does not necessarily include any specific types of draw objects and may include more or fewer types of draw objects than are discussed
herein. The draw objects in a preferred embodiment include, without limitation:
rectangle,
round rectangle,
line,
ellipse,
text, picture/image,
polygon,
OLEobject,
JavaScript,
database list,
database field, form button,
form radio button,
form checkbox,
form edit, form combobox, form clear button,
zoomin,
zoomout, grid,
graphic,
hotspot rectangle,
hotspot polygon, hotspot ellipse,
background picker,
Shockwave object,
Sound,
Video,
ActiveX,
Form Multi edit, and
MAX SHAPE
In the described embodiment, each type of draw object has associated
information that, in general, allows the draw object to be displayed on display
device 150 in accordance with user draw commands. This information is also used to generate HTML for the object (including links and anchors). The following paragraphs describe some examples of draw objects.
Fig. 16(a) is an example of information associated with a draw object for a page banner. It includes a bitmap of the banner and the name of the page (e.g., "Products"). Fig. 16(b) is a first example of information associated with a draw
object for a navigator button object. It includes a node number to which it will link when displayed by a browser, a name of the linked to page, and an image of the navigator button (e.g., an image using the GIF, JPEG, BMP, TIFF, EPS, or PCX file formats). Fig. 16(c) is a second example of information associated with a draw object for a navigator button. The link in the second example is a structural link, i.e., it represents a link according to relationships between the pages/nodes. Fig. 16(c) includes a smart link to another node, which is specified by relationship, and an image. The identity of the link is determined (updated) when the page is
displayed, previewed, or published. Fig. 16(d) is an example of a draw object for a text object. It includes a node number to which it will link when displayed by a browser, a name of the linked to page, and a string displayed in the text button. In the described embodiment, each draw object contains its type, its X position, Y position, width, and height. An example of a draw object of text and a draw object for an image is shown elsewhere in this document. It will be understood that each
type of display element in a page (e.g., text, image, button, etc.) has a
corresponding type of draw object.
In the described embodiment, each draw object contains its type, its X
position, Y position, width, and height and display flags. In general, each draw
object contains information associated with its corresponding dialog box in which
the user views properties of the display element on the page. III. Publishing a Page
Once the user has created a layout for a Web page as described above, the user needs to be able to create HTML for the page in accordance with the draw objects of the page. Fig. 17 shows an example of a display used to allow the user to publish one or more pages. In the described embodiment, this display actually allows the user to publish all pages in a Web site.
Fig. 17 shows a screen displayed when the user clicks on "Publish" button 310 of Fig. 3. The screen includes three buttons "Settings" 1702, "Stage" 1704, and "Publish" 1706. Once the display of Fig. 17 is displayed, the user can either "stage" or "publish" his site. Generally, staging is performed first and publishing is performed once the site is debugged. Staging and publishing are substantially the same, differing in when they are performed during the site development process. The user can also set configuration parameters to control the publishing or staging process. Clicking on either "publish" button 1706 or "Stage" button 1704 causes the described embodiment to generate HTML code for each page in the site (or only for pages indicated by the publish flag or by the user). This process is
described below.
Clicking on "Settings" button 1702 causes a pop-up window 1708 to be displayed. Clicking on "Stage" tab 1710 or "Publish" tab 1712 will display a window, which allows the user to specify a storage location for the staged or published site. Clicking on a "Modify" tab 1808 causes the pop-up window 1802 of Fig. 18 to be displayed. Window 1802 allows the user to indicate certain attributes of the HTML to be generated for the site (e.g., text only, black and white (grey scale), or low-res). Fig. 19 is a flow chart showing steps performed by page draw editor software 120 to publish a page of a site. It will be understood that the steps of Fig. 19 are performed by processor 102 executing instructions in page draw editor
software 120. In step 1904, if the stacked flag of the current page object indicates that the current page is a stacked page, then processor 102 creates HTML for a plurality of pages. If the current page is not a stacked page then, in step 1908, processor 102 builds HTML for a "normal" page. In either case, the HTML for the page is then written to a storage medium of the system.
It will be understood that, generally, each page object has a corresponding list of draw objects describing the elements of the page layout, and that processor 102 generates HTML in accordance with the lists of draw objects. As described above, each list of draw objects automatically includes draw objects representing automatically generated banners and links (e.g., to the home, parent, sibling, and/or children pages of that page). These automatic links may be structural links. The draw objects of a page may also represent other, additional links added by the user that are not a part of the site hierarchy. Moreover, the user can use the page draw editor to remove some of the automatically generated draw objects links if he so desires. Unless the user explicitly removes them, however, these automatically generated links are present in each page layout. Thus, the generated HTML for
each page will contain links to the home, parents, siblings, and/or children pages for each page of the site view.
IV. HTML Generation for a Page
Fig. 20 is a flow chart showing steps performed by the structure editor software to publish a normal page. Fig. 21 is a flow chart showing steps performed by the structure editor software to publish a stacked page. The steps of Figs. 20 and 21 are similar, except that the steps of Fig. 21 generates multiple HTML pages
for the stacked page. In Fig. 20 step 2002 creates initial HTML for the page as shown in Fig. 22. This step creates the beginning of an HTML page. Steps 2004- 2008 create HTML tables for each of the header, body, and footer as shown in Figs. 23 and 24. Step 2010 creates final HTML for the end of the page as shown
in Fig. 25. The preferred embodiment generates Netscape HTML version 3.X.
Fig. 21 shows the creation of a plurality of HTML pages for a stacked page.
Each HTML contains, for example, data for one record of a database associated with the stacked page. Each of the plurality of HTML pages has a common format including the same fields of the database and the same layout of the fields. Each page of the plurality of pages has the same format, but different data.
Step 2214 of Fig. 22 shows that the HTML for a page includes a tag
specifying the colors that a browser will use to display regular, visited, and active
links. Other embodiments specify other HTML tags that specify other attributes common to the page.
Fig. 23 is a flow chart showing steps to build an HTML table. In the described embodiment, an HTML table is generated for the header, body, and footer of each page. Steps 2302-2308 generate a matrix in memory 104 as discussed below in connection with Figs. 26-29. Step 2312 create the HTML table in accordance with the matrix as shown in Fig. 24.
Fig. 24 shows steps that create an HTML table. Step 2402 writes a table tag including a border of zero width and cellpadding and cellspacing of zero. Step 2404 generates a table header including column and width definitions for the HTML table Steps 2406-2418 go through each row and column of the matrix to generate a plurality of cells in the HTML table Some of the cells in the HTML table can be several columns wide and/or several rows high Step 2420 generates an end of table tag.
Fig. 26 is an example of first steps involved in determining an HTML table size for a layout element of a header, body, or footer In the example, the layout element has four display elements Each display element corresponds to one draw
object of the page As discussed above, each draw object has an X position (a start row) and a length Each draw object also has a Y position (a start column) and a height For each object, a first column edge is the X start position and a second column edge is the X start position plus the length In addition, for each object, a first row edge is the Y start position and a second row edge is the Y start position plus the height Processor 102 finds the row edges and columns edges for a current page, yielding data 2602 and 2604
Fig 27 is an example of second steps involved in determining an HTML
table size for a layout element Once the column and row edges of the draw objects are determined, the edges are sorted, duplicate edges are removed from the sorted list, yielding unique row edges and unique column edges (steps 2304
and 2306 of Fig. 23). The unique rows edges and column edges are then counted
In the example, the objects have six column edges and seven row edges Once the unique row edges and column edges are determined, the column widths and row heights for each column and row are determined
Fig. 28 is an example of a matrix 2802 generated in accordance with the edges and draw objects Matrix 2802 has a number of rows equal to the number of row edges plus one. The matrix has a number of columns equal to the number of column edges plus one. Thus, in the example, the matrix has seven columns and
eight rows. Each element 2804 of the matrix has a pointer field and an occupied
flag. The element of row 7, column 2 of the matrix points to object number 1 and is marked as occupied. The next four elements in row 2 are also marked as occupied. The element of row 3, column 3 points to object number 2 and is marked as occupied. The element of row 2, column 5 points to object number 3 and is marked as occupied. The next four elements in column 5 are also marked as occupied. The element of row 5, column 3 points to object number 4 and is marked as occupied. Fig. 29 is a block diagram of how the matrix 2802 is used to generate an
HTML table. The HTML table is used by a browser to display a portion of a page on display device 160 (such as a header, body, or a footer. (An alternate embodiment of the present invention creates a single table for each page of the site). Each element of the matrix is used to generate a cell in an HTML table (although some cells occupy more than one row or more than one column). For example, the matrix element in row 1 , column 1 causes an empty table cell to be generated. Each row in the HTML table has a height in pixels that is equal to the
height for that matrix row. Each cell in the HTML table has a width that is equal to
the width of the matrix for that column.
As is known to persons of ordinary skill in the art, the cells in the table can
be of varying sizes (i.e., can use the HTML tags "ROWSPAN" and COLSPAN").
The matrix element in row 2, column 5 causes generates of a cell that spans four
rows (ROWSPAN=4). The matrix element in row 7, column 2 causes generation of 5 a cell that spans five column (C0LSPAN=5).
Fig. 30 shows an example of a Style display. The display of Fig. 30 is shown when the user selects Style button 306. The Style button display allows the user to select an overall default appearance of all pages in the site. The user can
override the style for a given page by defining a different style for the page (not
lo shown). In the described embodiment, the values shown in Fig. 30 are stored in locations of memory 104. The automatic generation of banners, navigation buttons, and text buttons is performed in accordance with user-specified style values.
Fig. 31 shows an example of an Assets Display. The Assets display shows i s the files, links, and objects in the data processing system. For example, the assets shown in Fig. 31 are the draw objects for the "Products" page of Fig. 5.
Fig. 32 shows an example of a plurality of link dialog boxes, showing a structural link, an internal link, and an external link.
Fig. 33 is a flow chart showing identification of structural links for a page.
20 The links preferably are identified when the page is displayed, previewed or
published. Internal and external links are "absolute" links. Structural links are identified only as "next sibling link," "next child link", etc. For each link, the node- that-is-linked-to is identified (updated) by looking at the page hierarchy specified by
the page layout tree. After the node is identified, the processor finds the URL,
25 name, etc of the node and generates the display or HTML for the structural link.
In summary, the described embodiment of the present invention allows a
user to define a layout of a Web page. A draw-based editor in accordance with the
present invention automatically creates draw objects for each page that reflects the user-defined layout. When the user "publishes" a page, the described embodiment- generates HTML code for the page. A page can also be a "stacked page." A single stacked page causes generation of a plurality of HTML pages. The page defaults to a user-specified "style," which can be changed by the user.
Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed hereinlt is intended that the specification and examples be considered as exemplary only,
with a true scope of the invention being indicated by the following claims and equivalents.
/* NetObjects
definition of piture object */ tifndef PICTOBJ_H ♦define "PICTOBJ H
#include "drawobj .h" #include "resource.h" ♦include "DOFile.h" ♦include "dlgbase.h" class CModelessInsp; class CHotSpot; class CPictureGeneral ; class CDrawRect;
// flags for picture class ♦define DRAW NATURAL 1 //object not stretched ♦define DRAW*STRETCHED 2 //object stretched to fit ♦define DRAW TILED 4 //objecxt tiled ♦define DRAW- HOTSPOTON 16 // object has hot spots turned on ♦define DRAW" H__ALIGN_LEFT 32 // alignment ♦define DRAW* Η_ALIGN_CENTER 64 // alignment ♦define DRAW" "H_ALIGN_RIGHT 128 // alignment ♦define DRAW- V_ALIGN_TOP 256 // alignment ♦define DRAW- V ALIGN_CENTER 512 // alignment ♦define DRAW' V~ALIGN_BOTTOM 1024 // alignment ♦define DRAW* "GΪF_SOURCE 2048 ♦define DRAW- 'JPEG_S0URCE 4096 ♦define DRAW* ~UN NOWN_SOURCE 8192 ♦define DRAW" "GENERATEALWAYS 16384 // always rename and generate this gif ♦define DRAW DATAOBJECT 32768 // this is a data object
// 'list1 class for hot spots (requires afxtempl.h) typedef CTγpedPtrList<CObList, CHotSpot*> CHotSpotList? class CDrawPicture : public CDrawRect
I protected:
DECLARE_SERIAL(CDrawPicture) ; BOOL LoadBitmap( ) ; CDrawPicture ( ) public:
CDrawPicture(const CRect& position) ; -CDrawPicture () ; virtual void Serialize(CArchive tar)
//virtual void Serialize(Cλrchivet ar) ; virtual void Draw(CDC* pDC,CLayoutView* pView,BOOL bXorOutline = FALSE, CRect *pDrawRect = NULL) ; void TileBackGround(CDC* pDC,CLayoutView* pView, CRect *pRect) ; virtual BOOL SetBitmap(const CPDStringfc aFileType = cFILE_IMAGE_TYPE) ; //does the file dialog etc.
BOOL Changed(void) void SetStretch(ϋINT) ; UINT GetStretch() ; virtual CRect GetlmagePosition(CRect *position = NULL) ; virtual CRect GetImageSize() ; void SizeToI age(CLayoutView *p) . int GetlmageHandle(void) {return m_ImageHandle; ) ; long ConvertImage(CPDString *theFileName, CPDString * theFilePath) ;
BOOL SetBitmap(const char *pStr, const CPDStringi aFileType = cFILE_IMAGE_TYPE) ; virtual int GetsourceType(void) ; virtual void OnOpen(CLayoutView* pView) ;
CHotSpotList* GetHotSpotsO { return 6m_objects; } virtual CDrawObj *RemoveChild(CDrawObj *obj); virtual void AddChild(CDrawObj *obj) ;
CHotSpot* HotSpotAt(const CPointfc point, CLayoutView * pView) ;
CHotSpot* HotSpotAt(const CRectfi rect, CLayoutView * pView) ; void DeleteHotSpots(void) ; void MakeChildrenFit(CRect *newPosition *= NULL) ; virtual void EndMove(CLayoutView* pView = NULL) ; virtual void MoveChildren(CRect *lastPoistion = NULL, CRect *newPosition = NULL) ; // offsets all childern difference of last to new position void MoveChildren(CPoint point) ; // offsets all children using point coords virtual CDrawObj* FindChild(int id); virtual BOOL mAutoGenerated() ; virtual int HitTest(CPoint point, CLayoutView* pView, BOOL bSelected) ; void SetHotSpotsOn(BOOL) ; BOOL GetHotSpotsOn(void) ; void SetDataObjectOn(void) {m_PictureFlags }= DRAW_DATAOBJEC ; ) virtual CDrawObj* Intersects (const CRectt rect, CLayoutView ♦pView) ; virtual void AddPropPage(CObLiβti) ; virtual void AddProperties(CMenu *pPopup) ; virtual BOOL IsParent(void) {return TRUE;); virtual CDrawObj* GetSelectedChild(void) ; virtual void SetSelectedChild(CDrawObj *pObj , BOOL εet=TRUE) ; virtual void SaveUndo(CArchive& ar, PROPERTYJTYPE ,CLayoutView *pView) ; virtual void LoadUndo(CArchive& ar , PROPERTYJTYPE,CLayoutView *pView) ; virtual void SetAssetInfo(PROPERTYJTYPE type = DRAWOBJ) ; virtual void SetObjectData(void) ; virtual CDrawObj* Clone (CLayoutData *pLayoutData) ; virtual void SetlnitialValue (CLayoutView*) ; virtual BOOL DrawImageToMemory(CDC *) ; CString m_csName; int m_PictureFlags ;
CHotSpotList m_objects; void SetGenerateAlways(BOOL b = TRUE); void SetVAlignFlag (int) ; void SetHAlignFlag(int) ;
BOOL HasPicture() {return m_pDIB != NULL;) void mGenerateHTML(CPDBuffer* theBuffer) ; protected: int m_ImageHandle ; char * m_pDIB;
BITMAPINFO * m_biInfo; int m_bi idth; int m_biHeight; char * m_biBits; private: static CPictureGeneral *m_pPictureProp; protected:
// { (AFX_MSG (CDrawPicture) afx_msg void onPictureProperty () ; afx_msg void OnEditClear() ; //)}AFX_MSG 44 DECLARE_MESSAGE_HAP()
// PictureAlignment dialog class PictureAlignment : public CT2Dialog
(
// Construction public:
PictureAlignment(CWnd* pParent = NULL) ; // standard constructor
CWnd *parentWnd; BOOL m_Cancel; UINT v; UINT h; DrawShape user; void SetUser(DrawShape d) { user = d;}
// Dialog Data
//{ {AFX_DATA(PictureAlignment) enum { IDD = IDD_PICTURE_ALIGNMENT };
// NOTE: the ClassWizard will add data members here //})AFX_DATA
// Overrides
// ClassWizard generated virtual function overrides //{ {AFX_VIRTUAL(PictureAlignment) protected: virtual void DoDataExchange(CDataExchange* pDX) ; //
DDX/DDV support
//)}AFX_VIRTUAL
// Implementation protected:
// Generated message map functions //{ (AFX_MSG(PictureAlignment) virtual void OnOK() ; //})AFX_MSG DECLARE_MESSAGE MAP()
#endif //
_PICTOBJ_H//////////////////////////////////////////////////////
/////////////////////// // CDravText - Text Object fifndef _CRICHTEXT_H__. ♦define _CRICHTEXT_H_ //l
#include "drawobj .h"
// General stuff
/////////////////////////////////////////////////////////////////
////////////
// Tokens that we store in the token steam
// After a token there is potential more bytes and other tokens
// If this is the case then it is noted in the comments after the token
// All token take up 1 byte, Each item noted in [] take one byte
// Note that all that contain data have a end token to enable backwards searching typedef enu (
TJTEXT = 0, // Dummy token just use to communicate that its a text token
T_NULL, // Place holder to break up findtoken
// Text formatting tokens turn on/off T_BOLDON, // Bold T_BOLDOFF,
T_ITALIC0N, // Italics
T_ITALICOFF,
T_UNDERLINEON, // underline T_UNDERLINEOFF, T_STRIKE0UT0N, // strikeout T_STRIKEOUTOFF,
T_BLINK0N, // Blinking
T_BLINOFF,
T_FIXEDON, // Fixed pitch font
T_FIXEDOFF,
T_DUMMY1, // Raw html code. Used to insert HTML code directly into the token stream
// Text formatting with extra data
T_FACE, // Font face stored as T_FACE <name>
T_FACE
T_SIZE, // Size of font; stored as T_SIZE [size]
T_SIZE
T_C0L0R, // Change to COLORREF color; stored as T__C0LOR <C0L0RREF> T_COLOR
T_HEADING, // Heading marker; stored as T_HEADING [heading id] T_HEADING - should follow <P>
TJPARAFMT, // Formatting belonging to T_PARAGRAPH - stored as T_PARAFMT <ParaFormat> T_PARAFMT
T_SYMB0L, // Stores a symbol <T_SYMBOL> symbol value (int) <T_SYMBOL> TJHTMLTΛG, // A HTML tag stored
// String flow control T_END, // End of text object
T_NEWLINE, // New line - still inside the paragraph
T_PARAGRAPH, // New paragraph T_SOFT EWLINE , // Soft end of line - autowrap symbol
// Support for html links
T INKNAME, // Link name stored as T_LINKNAME <diεplay text T_LINKNAME2
T_LINKNAME2 ,
T_LINKURL, // Link URL stored as T_LINKURL <url>
T_LINKURL2
T_LINKURL2 ) TokenTypes;
// Notes:
// T_COLOR:
// The COLORREF is stored as 4 bytes. The maximum byte that is normally 0x00 will be
// 0x00 when the color is reset back to the default color defined for the view, In this case
// the rest of the color is unused. When a color ride is in effect the byte is 0x00. \
// T_PARAGRAPH: The line number is stored in the paragraph as
<px#χp>
// T_SOFTNEWLINE: Only used for return in FindToken
// Link should be stored as
// <T_LINK1> tokens <T_LINK2> URLStruct <T_LINK3>
♦define 0VERRIDE_0F( CR) * ( ( (char*) &(CR) )+3 ) ♦define MAX_INDENT 31
// Alignment settings as they apply to one paragraph typedef enum {
AlignLeft = 0,
AlignCenter,
AlignRight
);
// Builit types typedef enum (
Bull_None = 0,
Bull_Bullit,
Bull_Square,
Bull_Disc,
Bull_ABC,
Bull_abc,
Bull_III,
Bull_iii,
Bull_123, Bull_UnUsed, // Used when promoting and demoting paragraphs ) t
// Pitchtype, used to select between the proportional and fixed type font typedef enum (
Proportional,
Fixed, } PITCHTYPE;
// T_PARAFMT <ParagraphFormat> T_PARAFMT, size = 4 bytes struct ParaFormat { unsigned short aAlign : 2; unsigned short Undent : 5; // [ 0 .. 31 ] levels unsigned short iBullit : 4; unsigned short iOrder : 10; // Order item number [0..1024[ unsigned short bStart : 1; // Special start value for ordered lists ) i
// Usage of the Font list
♦define FONTINDEX_AUTOMATIC 0 // position of the Automatic font
♦define FONTINDEX_MAX 127
// The complete set of font settings as will be treated for text object.
// These settings are at any given location applied to the current setting
// in the global font setting. struct FontAttrib {
BYTE rgbRed; // b
BYTE rgbGreen; // 2 b
BYTE rgbBlue ; // 3b
BOOL bColorOverride : i; // Is the color currently overridden short isize : 7; // 4 b
BOOL bBold : 1;
PITCHTYPE ptPitch : 3 ;
BOOL bltalic : 1;
BOOL bUnderline : 1;
BOOL bstrikeout : 1;
BOOL bBlink : 1; // 5 b
BOOL bURL : 1; // Are we inside an URL display string unsigned short iFontlndex : 7; // 6 b
ParaFormat pf ; // 10 b
};
// URL control structure
/////////////////////////////////////////////////////// // The URLStruct is stored between the LINK and URL struct URLStruct
{ int iJavaEventl ;
}? class ExtFontAttrib{
// Current attribute; public:
// Utility information
CString sHeading; int istyleldx;
URLStruct urllnfo;
FontAttrib fAttrib;
// Functions int operator= (ExtFontAttrib &fs) ; ExtFontAttrib Jιoperator= (ExtFontAttrib &fs) ;
>
// Search commands to the FindText function
♦define FIND_HOME 1
♦define FIND_END 2
♦define FIND_PREVCHAR 3
♦define FIND_NEXTCHAR 4
♦define FIND_PREVWORD 5
♦define FIND_NEXTWORD 6
♦define FIND_PREVPARA 7
♦define FIND_NEXTPARA 8
♦define FIND_PREVLINE 9
♦define FIND_NEXTLINE 10 class CLayoutView;
♦define TALIGN_LEFT 0x01 ♦define TALIGN_CENTER 0x02 ♦define TALIGN_RIGHT 0x04 struct FindReplaceData { int iIndex;
CFindReplaceDialog *pFRDlg; int iFoun 1; int iFound2 ; int caretO, caretl;
BOOL bRewrapped; )f
// CDrawText
///////////////////////////////////////////////////////////////// //////////// struct CaretStruct
{
BOOL getlndex; // is index valid, if not then pos is valid - calc index in UpdateCaret int index; // index into m_text;
BOOL valid; // if index set - status if its OK
CPoint pos; // mouse pos, not maintained if valid is TRUE int height; // height of character at caret position - if
CPoint mousePos;
BOOL xset;
} struct LinelnfoStruct
{ public: int width; // width of text excl. the space needed for indent or bullit int height; int base;
CPoint ul; // Top left corner of the text box, if bullit then its before the text box int idxLine; // Index into the text stream of line, either point to <P> <BR> or to char that is first on softbreak line
FontAttrib fa; // FontAttrib for the start of the line after all heading and aling have been applied int iStyleldx; // Index of the style used int fFlags; // Flags for the line
)
// Line flags
♦define LINE_PARAGRAPH 0x0001 // Line is start of new paragraph
.// Different hardcoded sizes that HTML assumes ♦define INDENT_SIZE 40 //700 // Total indent size
♦define BULLIT_SIZE 30 //300 // Space for bullit
♦define BULLIT_SPACE 6 //50 // Space after bullit and before text
// Minimum Wrap width accepted ♦define MIN_WIDTH 10
// Edit mode flags
♦define EDIT_READONLY 0x00000001 // Field is read-only - user may not change ny content - inspector is disabled
♦define EDIT_ASCIIFIELD 0x00000002 // Field may only contain ascii string
♦define EDIT_SINGLELINE 0x00000004 // User must not be able to insert line break or paragraph
// Undo information enum UndoOp (
Oplnsert, // Insert bytes into buffer
OpDelete, // Delete bytes from buffer
OpCaretβ, // Position carets
OpAssign, // assign single byte in buffer
OpSetT_NULL, // assign range to T_NULL
OpMoveBytes, // move range inside buffer
OpAssignBytes, // assign range of bytes in buffer
OpRewrapAll, // whole object should be rewrapped )? struct UndoRecord { char nOpType; union {
// Used when inserting (Oplnsert) or deleting (OpDelete) bytes in the stream
// and when setting bytes to T_NULL (OpSetT_NULL)
// and when assigning a range of bytes (OpAssignBytes)
// and used for OpMoveBytes
// When OpDelete it is followed by bytes deleted struct { unsigned short iNoBytes; unsigned short ilndex; } insdel ;
// Used when position the carets struct { unsigned short indexO; unsigned short indexl; } caret;
// Used when []= assigning a single byte struct { unsigned short ilndex; char cOldByte; ) assign;
) data;
♦define UNDOBUFFER_INCREMENT 256 // increase buffer increment
♦define UNDOBUFFER MINSIZE UNDOBUFFER INCREMENT
♦define MAX_FONT_LENGTH 256 // Max size for a font face name
♦define PRIVATE_KEYSTATE
♦define MAXJTEXT (65536 * 4) ♦define MAX TEXT EDIT (MAXJTEXT - 1000) ♦define WRλP_FIRSTLINE ♦define WRAP_LASTLINE MAX_TEXT ♦define WRAP_UNDEFINED -1 extern BOOL IεChar( char c) ; extern BOOL IsToken( char c) ; extern BOOL WordDelimiter( char c) ; extern BOOL HardLineDelimiter( char c) ; extern BOOL LineDelimiter( char c) ; extern BOOL ParaDelimiter( char c) ? extern BOOL ParaFor atting( char c) ; extern BOOL IsFormatToken( char c) ; extern BOOL IsNonNormalizeToken( char c) ; extern BOOL IsOrdered( int iType) ; extern BOOL IsUnordered( int iType) ; extern int TokenSize( int token, BOOL bForward); extern int iT2clipbordFormat; extern int iRTFclipboardFormat; extern int m[] ; extern int d[ ) ; class CTextStyle;
/ / Cl.d.ss CDi&wTGxt
///////////////////////////////////////////////////////////////
//class CTextHTMLGenerator; class CDrawText : public CDrawRect
( friend class CTextHTMLGenerator; public: char *m_tex ; int m_nText;
BOOL bSelectAnchor; // Are we currently selecting using achor point static CStringArray *m_FontFaceArray; // Font face list private: int m_needsWrap;
CPoint m~LeftMargin;
CPoint m_RightMargin; int m clickCount; //dont start edit mode until second click
CFont *m_oldCFont; CFont m_CFont; //Active font, setup during calls to gettextsegment int m_iWrapIdxl ; int m_iWrapIdx2 ; int m_maxText; ///maximum allocated text int m_insertlndex? int m_haveCaretAndHeight; int m_iCaretWidth;
CRgn *m_pRgnCaret; //marked block
BOOL m_setMouseXPoε;
// For mouse selection static CaretStruct *m_pDblClick_Caretε; // containε dbl marked selection while mouse is still down static CaretStruct *m_pTriClick_Carets; // contains tri marked selection while mouse is still down static CaretStruct *m_pClick_Carets; // contains mouse marked selection while mouse is still down static BOOL m_bMDragOverride; // Override that we must
NOT do word extension in single click draw select
LinelnfoStruct * m_lineInfo; // display lines int m_nLines; // used lines in above int m_maxLines; // ma no lines int m_hMar ; int m_vMarg; static CTextStyle *m_pTextProp; //property sheet belonging to object static BOOL bReturnFirstPara; //return a <P> at start of data
FindReplaceData
*m_FindReplace;
BOOL JTransparent; // Is the control transparent
BOOL m_LockedSize; // Is the text size locked
CSize m_sizeLockSize; // The locked size
UINT m_EditMode; // Edit mode flags
COLORREF m_BackGroundColor; // Background color when not transparent char *m_pUndo; // Undo record buffer int m_nUndoLen; // length of under buffer int m_iϋndo; // Next location in undo buffer
BOOL bRecordUndo; // wheater to record or not in : :Insert and : :Delete CaretStruct m_caret[2]; //cursor/block location, if postions are the same, no marking
ExtFontAttrib mJFontSet; // Settings set while gettextsegment traverses text ExtFontAttrib m__01dFontSet; // Compare copy for SelectFont int JTrueHeight; //true height of text, different than size when m_Locked is TRUE private: static COLORREF m_TextColor; static COLORREF JTextLinkColor; protected:
DECLARE_SERIAL(CDrawText) ; CDrawTextO ; public:
CDrawText(const CRectfc position) ; -CDrawTex () ; virtual void Serialize(CArchive iar) ; virtual void AddProperties(CMenu *pPopup) ; virtual void Draw(CDC *pDC,CLayoutView* pView,BOOL bXorOutline - FALSE, CRect *pDrawRect » NULL) ; virtual void MoveTo(const CRectfc positon, CLayoutView* pView *= NULL, BOOL fAutosize = TRUE,BOOL fOutline = TRUE) ;
//property sheet support virtual void AddPropPage(CObListi) ; virtual void Select(CPoint pl, CPoint p2) ; virtual void KeyDown(UINT nChar, UINT nRepCnt, UINT nFlags) ; virtual void CharDown(UINT nChar, UINT nRepCnt, UINT nFlags) ; virtual void SysKeyUp(UINT nChar, UINT nRepCnt, UINT nFlags) ; virtual void StartMove( void); virtual void EndMove( CLayoutView *pView) ; virtual void OnLButtonDown(CLayoutView* pView, UINT nFlags, const CPoint& point) ; virtual void OnLButtonUp(CLayoutView* pView, UINT nFlags, const CPoint* point) ; virtual void OnMouseMove(CLayoutView* pView, UINT nFlags, const CPoint& point) ; virtual void OnLButtonDblClk(CLayoutView* pView, UINT nFlags, const CPointfc point) ; virtual void SavβUndo(CArchivβt ar, PROPERTYJTYPE,CLayoutView ♦pView) ; virtual void LoadUndo(CArchive& ar, PROPERTYJTYPE,CLayoutView *pView) ; virtual void mSynchronizeAssetNumbers() ;
BOOL virtual FindReplace( frOperations frOp, void *pData) ; void Activate( TrackerState tsNewState «= tsNormal); void Deactivate( TrackerState tsNewState = tsNormal); virtual void SetFocus( void) ; virtual void KillFocus( void); void GetText(char ** data, int * nData); void SetText(char * data, int nData) ; void SetAsciiText(char *pString, BOOL bKeepFormat) ; char *GetAsciiText( void); void mGenerateHTML(CPDBuffer* theBuffer) ; void GetFont(ExtFontAttrib &fs, int iCaretldx = -2) ; void SetFont(TokenTypes t_type) ; void SetFontAlignment( int iAlign) ; void SetFontBullit( int iBullit) ; void SetFontSize( int iSize) ; void SetFontColor( COLORREF *pColor) ; void SetFontFace( char *pFontFace) ; void Changelndent( int iChange) ; void SetSizeList( CComboBox *pComboBox, ExtFontAttribfc fs) ; void SetBulletList( CComboBox *pComboBox, ExtFontAttribS. fs) ; int FindFontIndex( char *pFontFace) ; static void lnitFontFaceArray( void) ; static void SetFontFaceList( CComboBox *pComboBox) ; void SetStyle( CString *psStyle) ; void ApplyURL(CString& sDisp, CStringfc sURL, char lToken, char rToken,int iJavaEventld « 0) ; void SetURL( CStringϋ sDisp, CString& sURL, BOOL bAddSpaces = FALSE, int iJavaEventld = 0) ;
BOOL GetURL( CStringt sDisp, CString* sURL, int& linkl, intfc link2, intSc urll, int& url2, int& iJava) ; void UpdateURL( CStringδ sURL, int il, int i2) ; void Unlink( int il, int i2, int 11, int 12);
BOOL GetSelectedText( CStringfi sText, int& il, int& i2) ;
// Java event access functions int GetJavaEvent( void);
BOOL SetJavaEvent( int iJavaEventld); // External access methods COLORREF GetBackColor( void) ; void SetBackColor( COLORREF c) ; BOOL GetTransparent( void) ; void SetTransparent( BOOL t) ; BOOL GetLockedSize( void) ; void SetLockedSize( BOOL Is); BOOL IsStyleUsed( CString *psStyleName) ; void ResizeToOneLine( CLayoutView *pView, int ilndex = 0); void Resizeθbject( CLayoutView *pView, int ix, int iY) ; void GetWordCounts( int *pLine, int *pPara, int *pWord, int *pChars) ;
UINT GetEditMode( void) {return m_EditMode; ) ; void SetEditMode( UINT fFlags) (m_EditMode «= fFlags;); static void GetMinRect(CRect*) ; int GetTrueHeight() ; private: void CalcFontSizes( PITCHTYPE pt, int *pFontSizes) ; virtual BOOL HasFont( ) {return TRUE; )
BOOL CreateFont( CFont* font, ExtFontAttrib* fs) ; void InitSelectFont( CDC *pDC) ;
BOOL SelectFont(ExtFontAttrib* fs, CDC *pDC) ; void AsciiSelectAll( void); void MouseSelectWord(CLayoutView* pView, UINT nFlags, const CPoint* point) ; void MouseSelectParagraph(CLayoutView* pView, UINT nFlags, const CPoint* point) ; void UpdateCarets( CLayoutView *pView) ; BOOL IsEmpty(); char NextChar(int* iStart) ; char PrevChar(int& iStart) ;
BOOL FindStream( int* index, int where) ; void GetFontAtIndex(ExtFontAttrib *fs, int index) ; int GetParaFor at( int iLine) ; int FindFirstLineAtLevel ( int iLine, int iLevel); void RewrapLevelAtLine( int iLine, int iLevel) ; void ApplyBulletToParagraphLevel ( int iLine, int iBulletType) ; void ApplyParaFormat( int iKind, int iValue) ; void ApplylndentToParagrap ( int iLine, int iChange) ; int ApplyStyleToPara( CString *psStyle, int iPara, BOOL bRemoveFormatting) ; void ApplyStyle( CString *psstyle, BOOL bRemoveFormatting) ; void SetSimpleType( char *tokenl, char *token2 , int iTokenSizel, int iTokenSize2, BOOL bSymetric ~ TRUE); void Linelnfoϋpdate( int iLocation, int nData) ; void Insert(int ilndex, const char * data, int nData) ; void Insert(int ilndex, char token) ; void Delete(int nData) ; void DelText(int indβxl, int index2, BOOL bPreβerveTokenβ «= TRUE) ; void EnsureURLforDelete( int* idxl, int* idx2) ;
BOOL DeleteSelection( void) ; int ExtractAsciiToBuffer( char *pText, int ilndexl, int ilndex2 , int iLen) ; public: void Delete( int index, int count) ; private:
BOOL SkipJunk( int* index, BOOL bForward) ; void UpdateCaret(char token, int iC, int nL, int iStart, int nChars, CPoint gpos, CDC *pDC) ; void UpdateSelectRegion( CLayoutView* pView) ; void RemoveSelectRegion( CLayoutView* pView) ; void FreeSelectRegion( void) ; void InvertSelectRegion( CDC *pDC) ;
CRgn *GetSelectRegion( void) ; void ScrollCaretIntoView( CLayoutView* pView, int icaret) ; void UpdateWndCaret( CLayoutView* pView) ; void FreeWndCaret( CLayoutView* pView) ; void UpdateMarking( CLayoutView *pView) ; void UpdateTextObject( CLayoutView *pView = NULL) ; int FindMatchToken( char token, int* isize, int istart, int iEnd) ; int CopressTokens ( int idxl, int idx2) ; int NormalizeStream( int idxl, int idx2, int *piNewEnd) ; void Normalize( int idxl, int idx2) ; void Normalize( void) ; void InitFontSet( ExtFontAttrib* fs) ; void InitFontSettings ( void) ; void InitFindToken( BOOL bRetumFirstParagraph = FALSE) ; int FindToken( int* iStart, int *iText = NULL, int *iTextLen = NULL, int iLineBreak «= 0) ; BOOL FindTex (int where) ; void Realloc(int reqSize) ;
// Wrap functions void AllWrapped( void); void RewrapParagraph( int iParaldx) ; void Rewrap( int idxl, int idx2) ; void RewrapLines( int iLine1, int iLine2) ; void RewrapAll ( void) ; void Wrap( CLayoutView *pView, CDC *pDCin = NULL) ; void SkipLineDelimiter( int* idx) ; void SkipRTFO ; void SelectText( CPoint pl, CPoint p2 ); void PositionIndex( int* index) ; void PositionCaret( int idx) ; void PositionCarets( void) ; int DocToClientToDoc( CDC *pDC, int iY) ; void DisplayBackground(CLayoutView* pView, CDC *pDC, CRect *pDrawRect) ; void Display(CLayoutView* pView, CDC *pDC, CRect *pDrawRect) ; void DisplayText(CDC *pDC, BOOL extentOnly, BOOL drawItAll) ;
void Co monlnitializationO ; int EnsureCorrectForCopy( int* idxl, int* idx2) ; void EnsureCorrectStartMarking( int* si, int* ei) ; int GetSelection( int* si, int* ei) ; int InsertColorSize( FontAttrib* fa) ; int InsertSettings( FontAttrib* fa) ; char *MakeθnSettings( FontAttrib &fa, int *pLen, BOOL bOnlyColorSize - FALSE) ; int CompressTNULLs ( char *pTokens, int len, int idxl, int idx2 , BOOL bUpdateCaret) ; void CompressTNULLs( void) ; void ClearRegion( int* idxl, int* idx2) ; void EnsureURLforCopy( int* idxl, int* idx2) ; void RemoveURLs( char *pToken, int len) ; void InvalidateLines( int iFirstLine, int iLastLine) ; void InvalidateLine( int iLine) ; int GetLineFromlndex( int index) ; void InvalidateRangetj int idxl, int idx2) ; void InvalidateSelection( void) ; void InvalObjAndParent( CLayoutView *pView, BOOL bErase = TRUE) ;
// Undo buffer functions void InitUndo( void) ; void AllocUndo( int iNeeded) ; void RecordUndo( UndoOp opcode, int ilntl, int ilnt2 , void *pBytes = NULL) ; void FreeUndo( void) ; void EmptyUndo( void) ; void MarkUndo( void) ; void Undo( void) ; void RecordCarets( void) ; void RecordRewrapAll ( void) ; void AssignTokenUndoable( int ilndex, char cNewValue) ; void AssignTokensUndoable( int ilndex, int iNoBytes, char *pData) ; void SetT_NULLundoable( int ilndex, int iNoBytes) ; void MoveTokensUndoable( int iDest, int iSrc, int iSize) ; void OnPreUndo(void *pθbj) ; private: void MoveDelete( int iKind) ; BOOL FindMatch( BOOL bCaseSensitive, int iStart, int iLen, LPCSTR pTarget, int fciNext) ;
BOOL Find( void) ;
BOOL Replace( void) ;
BOOL nextFindReplace(CLayoutView *pView, frOperations frOp, int* iReplace) ; protected:
//({AFX_ MSG(CDrawText) afx_msg void OnTextProperty() ; afx_msg void OnEditCut() ; afx_msg void OnEditCopy() ; afx_msg void OnEditPaste() ; afx_msg void OnEditSeleσtAHO ; afx_msg void OnEditClear( ) ; afx_msg void OnToolsPromote() ; fx_msg void OnToolsDemote() ; afx_msg void OnToolsWordCount() ; afx_msg void OnToolsInsertSymbolO ; afx_msg void OnToolsListStart() ; afx_msg void OnϋpdateToolsListStart(CCmdUI* pCmdϋl) afx_msg void OnUpdateEditCut(CCmdUI* pCmdUI) ; afx_msg void OnUpdateEditCopy(CCmdUI* pCmdUI) ; afx_msg void OnUpdateEditPaste(CCmdUI* pCmdUI) ; afx_msg void OnUpdateEditSelectAll(CCmdUI* pCmdUI) ; afx_msg void OnUpdateEditClear(CCmdUI* pCmdUI) ; afx_msg void OnStyleChanged(void *pObj) ; afx_msg void OnRecalc(void *pObj); afx_msg void OnInitialUpdate(void *pObj);
//})AFX MSG
DECLARE "MESSAGE_MAPO
);
//♦define COLOR_LINK RGB(0,0,255) //♦define COLOR_RAWHTML RGB(255, 0, 0) ♦endif

Claims

WHAT IS CLAIMED IS:
1. A method of allowing a user to define a World Wide Web page comprising the steps, performed by a data processing system, of:
displaying a plurality of page display elements on a display device, the display elements forming a page layout on the display device; receiving an indication that the user wants to add a new display element to the page at a first position on the page;
adding a new draw data structure in a memory of the data processing system for the new display element to a plurality of other draw data structures, the draw data structures corresponding to the plurality of page display elements, where the new draw data structure includes data representing the first position; and generating HTML that substantially reflects the displayed page layout on a pixel by pixel basis in accordance with the draw data structures. --2. A method of allowing a user to define a World Wide Web page comprising the steps, performed by a data processing system, of: displaying a plurality of page display elements on a display device, the display elements forming a page layout on the display device; receiving an indication that the user wants to add a new display element to the page at a first position on the page; adding a new draw data structure in a memory of the data processing system for the new display element to a plurality of other draw data structures, the draw data structures corresponding to the plurality of page display elements, where the new draw data structure includes data representing the first position; and generating an HTML table that substantially reflects the displayed page layout on a pixel by pixel basis in accordance with the draw data structures.
3. The method of claim 1 , where the page display elements displayed on the display device are created via a tools menu displayed on the display screen.
4. The method of claim 1 , where the page display elements displayed on
the display device include at least one of the group drawn images, audio, and video display elements.
5. The method of claim 1 , where the page display elements displayed on
the display device represents a plug-in.
6. The method of claim 1 , where the page display elements displayed on the display device include at least one of the group: form, datalist, and datafield
display elements.
7. The method of claim 1 , further comprising the step of creating a page layout on the display device and a corresponding plurality of draw objects in the memory, where the page layout includes a header, a body, and a footer.
8. The method of claim 7, where the header includes a banner and a plurality of navigator buttons.
9. The method of claim 7, where the footer includes a plurality of text
buttons.
10. The method of claim 1 , wherein the HTML generating step is performed in response to the user activating a PREVIEW button on the display.
11. The method of claim 1 , wherein the generating step is performed in response to the user activating a PUBLISH button on the display.
12. The method of claim 1 , further comprising the step of creating a page layout on the display device and a corresponding plurality of draw objects in the memory, where the page layout includes at least one of a header and a footer, the size of which can be adjusted by the user.
13. The method of claim 1 , wherein the step of receiving an indication that the user wants to add a new display element to the page at a first position on the page includes a step of: receiving an indication that the user has indicated a drawing tool on a tools menu on the display device.
14. The method of claim 1 , wherein the step of generating HTML includes
the steps of: creating HTML for the page header; creating HTML for the page body; and creating HTML for the page footer.
15. The method of claim 14, further comprising the step of: creating initial HTML for the page.
16. The method of claim 14, further comprising the step of: creating final HTML for the page.
17 The method of claim 1 , wherein the generating step includes the step of generating HTML for a normal page.
18. The method of claim 1 , wherein the generating step includes the step of generating HTML for a plurality of stacked pages.
19. The method of claim 1 , wherein the generating step includes the step
of generating an HTML table, which includes the substeps of:
finding row edges of display elements on the page;
finding column edges of display elements on the page;
creating a matrix in a memory of the data processing system, where the matrix cells point to the draw data structures;
finding the height and width of each column in the matrix; and
generating the HTML table in accordance with the height and width of each column in the matrix and the draw data structures.
20. The method of claim 1, wherein the generating step includes the steps of: generating a matrix representing the size and layout of the display elements; and generating an HTML table in accordance with the matrix.
21. The method of claim 1 , further including the steps of:
viewing the HTML via a web browser, where the page displayed by the browser corresponds to the displayed page layout on a pixel by pixel
basis.
22. The method of claim 1, further including the steps of: receiving input by the user indicating a page style definition; and wherein the generating step includes the step of generating HTML in accordance with the page style input by the user.
23. The method of claim 1 , further including the steps of: allowing the user to specify a hotspot on the display layout; and allowing the user to specify an address associated with the hotspot, wherein the generating step includes the step of generating an
HTML link in accordance with a location of the hotspot on the display layout and the address.
24. The method of claim 1 , further including the steps of: allowing the user to specify a link location on the display layout; and allowing the user to specify another page associated with the link; wherein the generating step includes the step of generating an
HTML in accordance with a location of the link on the lease layout and with the page specified by the user.
25. The method of claim 1 , further comprising the steps of: allowing the user to specify a link type that is one of a structural link, an internal link, or an external link; and allowing the user to specify a link location, wherein the generating step includes the step of generating an HTML link in accordance with the link type and location.
26. An apparatus allowing a user to define a World Wide Web page,
comprising:
a memory;
a portion configured to display a plurality of page display elements
on a display device, the display elements forming a page layout on the display
device;
a portion configured to receive an indication that the user wants to
add a new display element to the page at a first position on the page;
a portion configured to add a new draw data structure in the memory for the new display element to a plurality of other draw data structures, the draw data structures corresponding to the plurality of page display elements, where the
new draw data structure includes data representing the first position; and
a portion configured to generate HTML that substantially reflects the
displayed page layout on a pixel by pixel basis in accordance with the draw data
structures.
27. A computer program product, comprising: a computer usable medium having computer readable code embodied therein for allowing a user to define a World Wide Web page, the computer program product comprising: computer readable program code devices configured to cause a computer to effect displaying a plurality of page display elements on a display
device, the display elements forming a page layout on the display device; computer readable program code devices configured to cause a computer to effect receiving an indication that the user wants to add a new display element to the page at a first position on the page; computer readable program code devices configured to cause a computer to effect adding a new draw data structure in the memory for the new display element to a plurality of other draw data structures, the draw data structures corresponding to the plurality of page display elements, where the new draw data structure includes data representing the first position; and computer readable program code devices configured to cause a computer to effect generating HTML that substantially reflects the displayed page layout on a pixel by pixel basis in accordance with the draw data structures. -
PCT/US1997/012817 1996-07-29 1997-07-25 Draw-based editor for web pages WO1998004978A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU38082/97A AU3808297A (en) 1996-07-29 1997-07-25 Draw-based editor for web pages

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/687,974 US5845299A (en) 1996-07-29 1996-07-29 Draw-based editor for web pages
US08/687,974 1996-07-29

Publications (1)

Publication Number Publication Date
WO1998004978A1 true WO1998004978A1 (en) 1998-02-05

Family

ID=24762600

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1997/012817 WO1998004978A1 (en) 1996-07-29 1997-07-25 Draw-based editor for web pages

Country Status (3)

Country Link
US (2) US5845299A (en)
AU (1) AU3808297A (en)
WO (1) WO1998004978A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999066433A1 (en) * 1998-06-16 1999-12-23 Easysite Australia Pty Ltd Real-time document management system
DE10053475A1 (en) * 2000-10-24 2002-05-02 Textmodule Gmbh Method for automated preparation of multilingual Internet presentations follows three steps to offer a computer novice text modules to be combined with individual data in a user's data file and written in a foreign language version.
KR100787714B1 (en) * 1998-09-25 2007-12-21 후지쯔 가부시끼가이샤 Information processor, information processing method and medium
EP2840511A4 (en) * 2012-04-16 2016-06-22 Oh Suk Kwon System and method for dynamically converting webpage, and computer-readable recording medium

Families Citing this family (272)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6340981B1 (en) * 1997-06-30 2002-01-22 Sun Microsystems, Inc. Method and apparatus for stroke substitution
US5758324A (en) 1995-12-15 1998-05-26 Hartman; Richard L. Resume storage and retrieval system
US6003046A (en) * 1996-04-15 1999-12-14 Sun Microsystems, Inc. Automatic development and display of context information in structured documents on the world wide web
US5911145A (en) * 1996-07-29 1999-06-08 Rae Technology, Inc. Hierarchical structure editor for web sites
US6189019B1 (en) * 1996-08-14 2001-02-13 Microsoft Corporation Computer system and computer-implemented process for presenting document connectivity
SG70025A1 (en) * 1996-08-14 2000-01-25 Nippon Telegraph & Telephone Method and system for preparing and registering homepages interactive input apparatus for multimedia informations and recording medium including interactive input programs of the multimedia informations
US6584498B2 (en) 1996-09-13 2003-06-24 Planet Web, Inc. Dynamic preloading of web pages
US6377978B1 (en) 1996-09-13 2002-04-23 Planetweb, Inc. Dynamic downloading of hypertext electronic mail messages
US6101509A (en) * 1996-09-27 2000-08-08 Apple Computer, Inc. Method and apparatus for transmitting documents over a network
US6268851B1 (en) * 1996-09-30 2001-07-31 Trellix Corporation Hypermedia authoring and publishing system
US5983245A (en) * 1996-12-27 1999-11-09 Apple Computer, Inc. Method and apparatus for implementing universal resource locator menus
US6377255B1 (en) * 1997-01-24 2002-04-23 Sony Corporation Pattern data generator, pattern data generating method and its medium
EP0895194A1 (en) * 1997-01-24 1999-02-03 Sony Corporation Pattern data generator, pattern data generating method and its medium
US6092081A (en) 1997-03-05 2000-07-18 International Business Machines Corporation System and method for taggable digital portfolio creation and report generation
US6785865B1 (en) * 1997-03-06 2004-08-31 Microsoft Corporation Discoverability and navigation of hyperlinks via tabs
US7278098B1 (en) 1997-04-09 2007-10-02 Adobe Systems Incorporated Method and apparatus for implementing web pages having smart tables
US6684369B1 (en) * 1997-06-19 2004-01-27 International Business Machines, Corporation Web site creator using templates
US6282548B1 (en) * 1997-06-21 2001-08-28 Alexa Internet Automatically generate and displaying metadata as supplemental information concurrently with the web page, there being no link between web page and metadata
US6061686A (en) * 1997-06-26 2000-05-09 Digital Equipment Corporation Updating a copy of a remote document stored in a local computer system
US20020007493A1 (en) * 1997-07-29 2002-01-17 Laura J. Butler Providing enhanced content with broadcast video
US6542923B2 (en) * 1997-08-21 2003-04-01 Planet Web, Inc. Active electronic mail
US6564250B1 (en) 1997-08-21 2003-05-13 Planetweb, Inc. Miniclient for internet appliance
US7325077B1 (en) 1997-08-21 2008-01-29 Beryl Technical Assays Llc Miniclient for internet appliance
US6313851B1 (en) * 1997-08-27 2001-11-06 Microsoft Corporation User friendly remote system interface
US6138150A (en) * 1997-09-03 2000-10-24 International Business Machines Corporation Method for remotely controlling computer resources via the internet with a web browser
US5987482A (en) 1997-09-08 1999-11-16 International Business Machines Corporation Computer system and method of displaying hypertext documents with internal hypertext link definitions
US6163779A (en) * 1997-09-29 2000-12-19 International Business Machines Corporation Method of saving a web page to a local hard drive to enable client-side browsing
US6026371A (en) * 1997-11-25 2000-02-15 International Business Machines Corp. Method and apparatus for allowing online directory producers to preview advertisement in online directory listings
US6247011B1 (en) * 1997-12-02 2001-06-12 Digital-Net, Inc. Computerized prepress authoring for document creation
GB2332348A (en) * 1997-12-09 1999-06-16 Zyris Plc Graphic image design
US6002874A (en) * 1997-12-22 1999-12-14 International Business Machines Corporation Method and system for translating goto-oriented procedural languages into goto-free object oriented languages
US6380950B1 (en) * 1998-01-20 2002-04-30 Globalstreams, Inc. Low bandwidth television
US6108675A (en) * 1998-01-22 2000-08-22 International Business Machines Corporation Positioning of transmitted document pages in receiving display station windows for maximum visibility of information on pages
US5945993A (en) * 1998-01-30 1999-08-31 Hewlett-Packard Company Pictograph-based method and apparatus for controlling a plurality of lighting loads
US6366923B1 (en) * 1998-03-23 2002-04-02 Webivore Research, Llc Gathering selected information from the world wide web
US6684211B1 (en) 1998-04-01 2004-01-27 Planetweb, Inc. Multimedia communication and presentation
US6292185B1 (en) * 1998-04-27 2001-09-18 C.C.R., Inc. Method and apparatus for tailoring the appearance of a graphical user interface
US6473100B1 (en) * 1998-05-20 2002-10-29 Microsoft Corporation Hosting controls in a window via an interface for controlling the window
US6496203B1 (en) * 1998-05-27 2002-12-17 Microsoft Corporation Standardized and application-independent graphical user interface components implemented with web technology
US6374273B1 (en) * 1998-06-05 2002-04-16 International Business Machines Corporation Reformatting a first single-column markup document into a multi-column document, and formatting second markup document in the background, while displaying the first reformatted document
US6959449B1 (en) * 1998-06-08 2005-10-25 Sony Corporation System and method for simultaneously accessing video data and internet page data
US6185589B1 (en) * 1998-07-31 2001-02-06 Hewlett-Packard Company Automatic banner resizing for variable-width web pages using variable width cells of HTML table
US6558431B1 (en) * 1998-09-11 2003-05-06 Macromedia, Inc. Storing valid and invalid markup language in strict and relaxed tables respectively
US7117433B1 (en) * 1998-09-29 2006-10-03 International Business Machines Corporation HTML mapping substitution graphical user interface for display of elements mapped to HTML files
US8418131B2 (en) * 1998-11-25 2013-04-09 Helmut Emmelmann Interactive server side components
US7213202B1 (en) 1998-12-11 2007-05-01 Microsoft Corporation Simplified design for HTML
US6779153B1 (en) 1998-12-11 2004-08-17 Microsoft Corporation Creation of web pages through synchronization
US6549878B1 (en) * 1998-12-31 2003-04-15 Microsoft Corporation System and method for editing a spreadsheet via an improved editing and cell selection model
US7284193B1 (en) 1998-12-31 2007-10-16 Microsoft Corporation Page object model
US6889379B1 (en) * 1998-12-31 2005-05-03 Microsoft Corporation Transporting objects between a client and a server
US6714219B2 (en) * 1998-12-31 2004-03-30 Microsoft Corporation Drag and drop creation and editing of a page incorporating scripts
US6981215B1 (en) * 1998-12-31 2005-12-27 Microsoft Corp. System for converting event-driven code into serially executed code
US6895557B1 (en) 1999-07-21 2005-05-17 Ipix Corporation Web-based media submission tool
AU6520500A (en) * 1999-08-06 2001-03-05 David M. Bridgeland Automated product designer system and method
US7278094B1 (en) 2000-05-03 2007-10-02 R. R. Donnelley & Sons Co. Variable text processing for an electronic press
US6434745B1 (en) 1999-09-15 2002-08-13 Direct Business Technologies, Inc. Customized web browsing and marketing software with local events statistics database
US7934149B1 (en) * 1999-09-30 2011-04-26 Instantis, Inc. Automated creation and maintenance of programs to process internet form related submissions
US20100145794A1 (en) * 1999-10-21 2010-06-10 Sean Barnes Barger Media Processing Engine and Ad-Per-View
US6792575B1 (en) 1999-10-21 2004-09-14 Equilibrium Technologies Automated processing and delivery of media to web servers
US20060265476A1 (en) * 1999-10-21 2006-11-23 Sean Barger Automated media delivery system
US7779352B1 (en) 1999-11-05 2010-08-17 John Underwood Method and apparatus for generating a website using a multi-dimensional description of the website
US7152207B1 (en) * 1999-11-05 2006-12-19 Decentrix Inc. Method and apparatus for providing conditional customization for generating a web site
US7120863B1 (en) 1999-11-15 2006-10-10 International Business Machines Corporation Method, system, and program for interfacing with elements in a document
US6732162B1 (en) 1999-11-15 2004-05-04 Internet Pictures Corporation Method of providing preprocessed images for a plurality of internet web sites
US6823330B1 (en) 1999-11-16 2004-11-23 Gateway, Inc. Site home navigation control
US6720981B1 (en) 1999-12-08 2004-04-13 International Business Machines Corporation Method, system and program product for animated web page construction and display
KR20000012553A (en) * 1999-12-11 2000-03-06 김창곤 Active Browser
US20010032090A1 (en) * 1999-12-14 2001-10-18 Ahmed Moneim One-line registration
US6639611B1 (en) * 1999-12-15 2003-10-28 Sun Microsystems, Inc. System and method for efficient layout of a display table
US6690396B1 (en) * 1999-12-27 2004-02-10 Gateway, Inc. Scannable design of an executable
GB2357945A (en) * 1999-12-30 2001-07-04 Nokia Corp Navigating a focus around a display device
US7237002B1 (en) * 2000-01-04 2007-06-26 International Business Machines Corporation System and method for dynamic browser management of web site
FR2804231B1 (en) 2000-01-25 2002-11-08 Vistaprint Usa Inc CENTRALIZED PRINTING OF LOW-VOLUME COMMERCIAL DOCUMENTS ON MACHINES PREVIOUSLY LIMITED TO VERY LARGE PRINTS
EP1259887A4 (en) * 2000-01-25 2003-08-13 Vistaprint Usa Inc Managing print jobs
JP5465819B2 (en) * 2000-02-12 2014-04-09 アドビ システムズ， インコーポレイテッド Text grid creation tool
US7305617B2 (en) * 2000-02-12 2007-12-04 Adobe Systems Incorporated Method for aligning text to baseline grids and to CJK character grids
US20030115546A1 (en) * 2000-02-17 2003-06-19 Dubey Stuart P. Method and apparatus for integrating digital media assets into documents
WO2001067304A1 (en) * 2000-03-07 2001-09-13 Hotlens.Com Inc. Server-side web browsing and multiple lens system, method and apparatus
US20010047477A1 (en) * 2000-03-20 2001-11-29 Hiang-Swee Chiang Transparent user and session management for web applications
WO2001073560A1 (en) * 2000-03-31 2001-10-04 Kyocera Communication Systems, Co., Ltd. Contents providing system
US7454695B1 (en) 2000-05-19 2008-11-18 Renderx, Inc. Methods for rendering tables
US7024621B1 (en) * 2000-05-19 2006-04-04 Renderx Methods and systems for rendering electronic data
US6971062B1 (en) 2000-05-19 2005-11-29 Renderx Methods for rendering footnotes
US20020138843A1 (en) * 2000-05-19 2002-09-26 Andrew Samaan Video distribution method and system
US9436667B2 (en) 2000-05-19 2016-09-06 Renderx, Inc. Techniques for rendering media as layers
AU2001274901A1 (en) * 2000-05-24 2001-12-03 Nttx Corporation Graphical weg page editor
US6845273B1 (en) 2000-05-26 2005-01-18 Newsstand, Inc. Method and system for replacing content in a digital version of a mass-produced printed paper
US7181679B1 (en) 2000-05-26 2007-02-20 Newsstand, Inc. Method and system for translating a digital version of a paper
US6850260B1 (en) 2000-05-26 2005-02-01 Newsstand, Inc. Method and system for identifying a selectable portion of a digital version of a mass-produced printed paper
US8055994B1 (en) 2000-05-26 2011-11-08 Libredigital, Inc. Method, system and computer program product for displaying a version of a paper
GB2381350B (en) * 2000-05-26 2005-01-12 Newsstand Inc Method, system, and computer program product for providing a digital version of a mass-produced printed paper
US10878178B2 (en) * 2000-06-07 2020-12-29 Pt 291, Llc Modifying web pages to be served by computer server system
US6771291B1 (en) * 2000-06-07 2004-08-03 The Perfect Web Corporation Method for developing electronic documents employing multiple display regions
FR2810131B1 (en) * 2000-06-08 2005-04-08 Stg Interactive SYSTEM FOR PUBLICATION OF MULTIMEDIA DATA
US7028268B1 (en) 2000-06-15 2006-04-11 Conley Jr Ralph F Multiple destination banners
EP1168160A1 (en) * 2000-06-19 2002-01-02 Hewlett-Packard Company, A Delaware Corporation Process for automatically displaying graphical objects such as buttons in a web page
US7624356B1 (en) * 2000-06-21 2009-11-24 Microsoft Corporation Task-sensitive methods and systems for displaying command sets
US7346848B1 (en) * 2000-06-21 2008-03-18 Microsoft Corporation Single window navigation methods and systems
US7000230B1 (en) 2000-06-21 2006-02-14 Microsoft Corporation Network-based software extensions
US6883168B1 (en) 2000-06-21 2005-04-19 Microsoft Corporation Methods, systems, architectures and data structures for delivering software via a network
US6493733B1 (en) * 2000-06-23 2002-12-10 Microsoft Corporation Method for inserting interactive HTML objects into an electronic file
US6632249B2 (en) * 2000-06-23 2003-10-14 Microsoft Corporation Method for providing web-based services to an application program module
US20020194267A1 (en) * 2000-06-23 2002-12-19 Daniel Flesner Portal server that provides modification of user interfaces for access to computer networks
FR2812420A1 (en) * 2000-07-28 2002-02-01 Baptiste Vermes AUTOMATIC PROCESS FOR FORMING DYNAMIC PAGES ON A WEBSITE
US7779359B2 (en) * 2000-08-08 2010-08-17 The United States Of America As Represented By The Secretary Of The Army Multifunction display design tool
US7069192B1 (en) * 2000-08-25 2006-06-27 Hewlett-Packard Company CAD system
US20020026521A1 (en) * 2000-08-31 2002-02-28 Sharfman Joshua Dov Joseph System and method for managing and distributing associated assets in various formats
US6839059B1 (en) 2000-08-31 2005-01-04 Interactive Video Technologies, Inc. System and method for manipulation and interaction of time-based mixed media formats
US6922702B1 (en) 2000-08-31 2005-07-26 Interactive Video Technologies, Inc. System and method for assembling discrete data files into an executable file and for processing the executable file
JP2002083309A (en) * 2000-09-07 2002-03-22 Hitachi Ltd Service offering method, its executing device, storage medium recording its processing program
SG96567A1 (en) * 2000-09-16 2003-06-16 Sang Nila Comm Method for preparing a document for electronic publication
KR20020022407A (en) * 2000-09-20 2002-03-27 주식회사 인포웨어 Method of generating a web site corporated with databases and program recording medium
US20020059280A1 (en) * 2000-09-25 2002-05-16 Brian Slesinsky Automated table installer for multiple heterogenous databases
TW525067B (en) * 2000-09-28 2003-03-21 Fatwire Corp System and method for in-context editing
AU2002236673A1 (en) * 2000-10-20 2002-05-21 Desknet, Inc. Method of constructing a composite image within an image space of a webpage
US7260777B2 (en) * 2001-08-17 2007-08-21 Desknet Inc. Apparatus, method and system for transforming data
US7240294B2 (en) * 2000-10-20 2007-07-03 Desknet Inc. Method of constructing a composite image
US7895530B2 (en) * 2000-11-09 2011-02-22 Change Tools, Inc. User definable interface system, method, support tools, and computer program product
US7191405B1 (en) * 2000-11-22 2007-03-13 Adobe Systems Incorporated System and method for editing information
US20060047781A1 (en) * 2000-11-22 2006-03-02 Ed Anuff Method and system for providing remote portal service modules
US20020091840A1 (en) * 2000-11-28 2002-07-11 Gregory Pulier Real-time optimization of streaming media from a plurality of media sources
JP2003050964A (en) * 2000-11-30 2003-02-21 Kokusai Zunou Sangyo Kk Web server system and web system for spread sheet
AU2002233991A1 (en) * 2000-12-06 2002-06-18 American Express Travel Related Services Company, Inc. Layout generator system and method
US7000220B1 (en) 2001-02-15 2006-02-14 Booth Thomas W Networked software development environment allowing simultaneous clients with combined run mode and design mode
US20060288212A1 (en) * 2001-03-20 2006-12-21 Gutenberg Printing Llc Transparent user and session management for web applications
JP3475186B2 (en) * 2001-03-21 2003-12-08 株式会社ニチベイ Blinds, blind slats, manufacturing method thereof and molding machine
US6771292B2 (en) * 2001-03-29 2004-08-03 International Business Machines Corporation Method and system for providing feedback concerning a content pane to be docked in a host window
US9256356B2 (en) * 2001-03-29 2016-02-09 International Business Machines Corporation Method and system for providing feedback for docking a content pane in a host window
US20020158902A1 (en) * 2001-04-30 2002-10-31 Hooker Bryce H. Method and apparatus for automatically publishing associate information
US20020180789A1 (en) * 2001-06-01 2002-12-05 Gregory Guttmann Framework for developing web-based and email-based collaborative programs
US7134084B1 (en) * 2001-06-18 2006-11-07 Siebel Systems, Inc. Configuration of displays for targeted user communities
AUPR580801A0 (en) * 2001-06-19 2001-07-12 Newbrain Technologies Pty Ltd A user interface for constructing web pages to build a website
WO2003003642A2 (en) * 2001-06-29 2003-01-09 Ve Enterprises Llc System and method for editing web pages in a client/server architecture
US20030023641A1 (en) * 2001-07-27 2003-01-30 Gorman William Phillip Web page authoring tool
US20040205553A1 (en) * 2001-08-15 2004-10-14 Hall David M. Page layout markup language
EP1288805A1 (en) * 2001-08-24 2003-03-05 Accenture Global Services GmbH eCommerce benchmarking
JP4344105B2 (en) * 2001-09-12 2009-10-14 セイコーエプソン株式会社 Source file generator
US8407353B2 (en) * 2001-09-17 2013-03-26 Open Text S.A. Method and system for sharing different web components between different web sites in a portal framework
US8606916B2 (en) 2001-09-17 2013-12-10 Open Text S.A. Graphical user interface for performing administration on web components of web sites in a portal framework
US20030079051A1 (en) * 2001-10-24 2003-04-24 Dean Moses Method and system for the internationalization of computer programs employing graphical user interface
US7225399B2 (en) * 2001-10-31 2007-05-29 Engineered Support System, Inc. Systems and methods for generating interactive electronic reference materials
US20030110449A1 (en) * 2001-12-11 2003-06-12 Wolfe Donald P. Method and system of editing web site
EP1331575A1 (en) * 2002-01-18 2003-07-30 Sap Ag Computer based creation of document in a markup language
ATE289433T1 (en) * 2002-05-17 2005-03-15 Sap Ag METHOD AND COMPUTER SYSTEM FOR PROCESSING BROWSER DOCUMENTS
US20030225632A1 (en) * 2002-05-30 2003-12-04 Vincent Tong Method and system for providing personalized online shopping service
US20030227481A1 (en) * 2002-06-05 2003-12-11 Udo Arend Creating user interfaces using generic tasks
US7461346B2 (en) * 2002-07-30 2008-12-02 Sap Ag Editing browser documents
US20060104511A1 (en) * 2002-08-20 2006-05-18 Guo Jinhong K Method, system and apparatus for generating structured document files
US8255814B2 (en) * 2002-09-06 2012-08-28 Autodesk, Inc. Temporary text and graphic feedback for object manipulators
US8234174B1 (en) 2002-09-10 2012-07-31 Eagon Grant A Method and apparatus for creating custom advertisements
US7209960B2 (en) * 2002-09-20 2007-04-24 Sun Microsystems, Inc. Loading and saving data from security sensitive applets to a local file system
DE10245528A1 (en) * 2002-09-30 2004-04-15 OCé PRINTING SYSTEMS GMBH Access to data objects using the network addresses assigned to the data objects
US7243098B2 (en) * 2002-12-19 2007-07-10 International Business Machines Corporation Method, system, and program for optimizing aggregate processing
US7124137B2 (en) 2002-12-19 2006-10-17 International Business Machines Corporation Method, system, and program for optimizing processing of nested functions
US7000184B2 (en) * 2003-01-24 2006-02-14 The Cobalt Group, Inc. Remote web site editing in a standard web browser without external software
US7415672B1 (en) 2003-03-24 2008-08-19 Microsoft Corporation System and method for designing electronic forms
US7275216B2 (en) * 2003-03-24 2007-09-25 Microsoft Corporation System and method for designing electronic forms and hierarchical schemas
US7370066B1 (en) * 2003-03-24 2008-05-06 Microsoft Corporation System and method for offline editing of data files
US7296017B2 (en) * 2003-03-28 2007-11-13 Microsoft Corporation Validation of XML data files
US7913159B2 (en) 2003-03-28 2011-03-22 Microsoft Corporation System and method for real-time validation of structured data files
US20040215719A1 (en) * 2003-04-09 2004-10-28 Altshuler Dennis Wayne Method and system for designing, editing and publishing web page content in a live internet session
US7086028B1 (en) * 2003-04-09 2006-08-01 Autodesk, Inc. Simplified generation of design change information on a drawing in a computer aided design (CAD) environment
US7421649B1 (en) * 2003-04-28 2008-09-02 Adobe Systems Incorporated Enhanced visual table editing
EP1484694A1 (en) * 2003-06-05 2004-12-08 Sap Ag Converting object structures for search engines
US7668888B2 (en) * 2003-06-05 2010-02-23 Sap Ag Converting object structures for search engines
US7111229B2 (en) * 2003-06-25 2006-09-19 Yahoo! Inc. System and method for providing a webpage
US7406660B1 (en) 2003-08-01 2008-07-29 Microsoft Corporation Mapping between structured data and a visual surface
US7334187B1 (en) * 2003-08-06 2008-02-19 Microsoft Corporation Electronic form aggregation
EP1508428A1 (en) * 2003-08-22 2005-02-23 Leister Process Technologies Device for welding flat plastic materials
US7581173B1 (en) 2003-09-25 2009-08-25 Google, Inc. Methods and apparatuses for formatting web pages
US7620896B2 (en) * 2004-01-08 2009-11-17 International Business Machines Corporation Intelligent agenda object for showing contextual location within a presentation application
US7120864B2 (en) 2004-01-27 2006-10-10 International Business Machines Corporation Eliminating superfluous namespace declarations and undeclaring default namespaces in XML serialization processing
US8819072B1 (en) 2004-02-02 2014-08-26 Microsoft Corporation Promoting data from structured data files
US7430711B2 (en) * 2004-02-17 2008-09-30 Microsoft Corporation Systems and methods for editing XML documents
US7610219B2 (en) * 2004-02-17 2009-10-27 Omar Farooq Sayed System and methods for assembly of a web site for an online store by a seller
DE602004020969D1 (en) * 2004-03-12 2009-06-18 Dassault Systemes Method for selecting and handling objects in a CAD system
WO2005109284A2 (en) * 2004-05-03 2005-11-17 Trintuition Llc Apparatus and method for creating and using documents in a distributed computing network
US7913163B1 (en) * 2004-09-22 2011-03-22 Google Inc. Determining semantically distinct regions of a document
US7707498B2 (en) * 2004-09-30 2010-04-27 Microsoft Corporation Specific type content manager in an electronic document
US7631290B1 (en) * 2004-10-27 2009-12-08 Adobe Systems Incorporated Enhanced navigation for visual design editing
KR20070049242A (en) * 2004-10-28 2007-05-10 노키아 코포레이션 Device menu
US8487879B2 (en) 2004-10-29 2013-07-16 Microsoft Corporation Systems and methods for interacting with a computer through handwriting to a screen
US20060095835A1 (en) * 2004-11-01 2006-05-04 William Kennedy System and method for the modular generation of markup language
US20060107205A1 (en) * 2004-11-12 2006-05-18 Nokia Corporation Determining a main content area of a page
US7945535B2 (en) * 2004-12-13 2011-05-17 Microsoft Corporation Automatic publishing of digital content
US7904801B2 (en) * 2004-12-15 2011-03-08 Microsoft Corporation Recursive sections in electronic forms
US7627592B2 (en) * 2004-12-16 2009-12-01 Microsoft Corporation Systems and methods for converting a formatted document to a web page
US7310771B2 (en) * 2004-12-20 2007-12-18 Microsoft Corporation Method and computer-readable medium for providing page and table formatting services
US7945590B2 (en) 2005-01-06 2011-05-17 Microsoft Corporation Programmability for binding data
US7730394B2 (en) 2005-01-06 2010-06-01 Microsoft Corporation Data binding in a word-processing application
US7617234B2 (en) 2005-01-06 2009-11-10 Microsoft Corporation XML schema for binding data
US7937651B2 (en) * 2005-01-14 2011-05-03 Microsoft Corporation Structural editing operations for network forms
US7752224B2 (en) 2005-02-25 2010-07-06 Microsoft Corporation Programmability for XML data store for documents
US7668873B2 (en) * 2005-02-25 2010-02-23 Microsoft Corporation Data store for software application documents
US20060212792A1 (en) * 2005-03-18 2006-09-21 Microsoft Corporation Synchronously publishing a web page and corresponding web page resources
US20060212806A1 (en) * 2005-03-18 2006-09-21 Microsoft Corporation Application of presentation styles to items on a web page
US7444597B2 (en) * 2005-03-18 2008-10-28 Microsoft Corporation Organizing elements on a web page via drag and drop operations
US8635548B2 (en) * 2005-03-18 2014-01-21 International Business Machines Corporation Configuring a page for drag and drop arrangement of content artifacts in a page development tool
US8010515B2 (en) * 2005-04-15 2011-08-30 Microsoft Corporation Query to an electronic form
WO2006138519A2 (en) * 2005-06-15 2006-12-28 Flimp Media Inc. System and method of creating and tracking rich media communications
US8200975B2 (en) * 2005-06-29 2012-06-12 Microsoft Corporation Digital signatures for network forms
EP1920468B1 (en) * 2005-09-01 2014-02-26 Merck Patent GmbH Photovoltaic cells integrated with bypass diode
US7953696B2 (en) 2005-09-09 2011-05-31 Microsoft Corporation Real-time synchronization of XML data between applications
US20070061467A1 (en) * 2005-09-15 2007-03-15 Microsoft Corporation Sessions and session states
JP4393444B2 (en) * 2005-11-02 2010-01-06 キヤノン株式会社 Information processing method and apparatus
US8001459B2 (en) 2005-12-05 2011-08-16 Microsoft Corporation Enabling electronic documents for limited-capability computing devices
TW200723049A (en) * 2005-12-07 2007-06-16 Era Digital Media Co Single page website organization method
US20070204220A1 (en) * 2006-02-27 2007-08-30 Microsoft Corporation Re-layout of network content
US8874692B2 (en) * 2006-03-27 2014-10-28 At&T Intellectual Property Ii, L.P. Method and apparatus for organizing information in a world wide web page format
US20070250783A1 (en) * 2006-04-24 2007-10-25 Ehealthinsurance Services, Inc. Method and system to provide online application forms
US20080172608A1 (en) * 2006-06-06 2008-07-17 Bellsouth Intellectual Property Corporation Site builder
US20080007788A1 (en) * 2006-06-30 2008-01-10 Good Frederick L Smart page photo sizing, composing and cropping tool
US7703038B1 (en) * 2006-09-26 2010-04-20 Adobe Systems Inc. Methods and apparatus for creating a quick canvas
US20080120538A1 (en) * 2006-11-22 2008-05-22 University Of New Brunswick Visual web page authoring tool for multi-context web pages
US8126766B2 (en) * 2006-11-29 2012-02-28 Yahoo! Inc. Interactive user interface for collecting and processing nomenclature and placement metrics for website design
US8020094B2 (en) 2006-12-06 2011-09-13 Microsoft Corporation Editing web pages via a web browser
US8381093B2 (en) * 2006-12-06 2013-02-19 Microsoft Corporation Editing web pages via a web browser
JP2008146225A (en) * 2006-12-07 2008-06-26 Canon Inc Editor, edit method, and edit program
US8086637B1 (en) 2006-12-22 2011-12-27 Emc Corporation Access control for business process data
US8212805B1 (en) 2007-01-05 2012-07-03 Kenneth Banschick System and method for parametric display of modular aesthetic designs
US10083184B2 (en) * 2007-01-07 2018-09-25 Apple Inc. Widget synchronization in accordance with synchronization preferences
US8239760B2 (en) * 2007-06-26 2012-08-07 Sap Ag Multi-user document editing system and method
US9594731B2 (en) * 2007-06-29 2017-03-14 Microsoft Technology Licensing, Llc WYSIWYG, browser-based XML editor
US8555200B2 (en) * 2007-08-21 2013-10-08 Wetpaint.Com, Inc. Representing editable attributes of embedded content
US8433999B2 (en) * 2007-08-21 2013-04-30 Wetpaint.Com, Inc. Method and apparatus for retrieving and editing dynamically generated content for editable web pages
CA2697347A1 (en) * 2007-08-22 2009-02-26 Proscape Technologies, Inc. Defining an interactive user interface
US7987428B2 (en) * 2007-10-23 2011-07-26 Microsoft Corporation Dashboard editor
US8095417B2 (en) * 2007-10-23 2012-01-10 Microsoft Corporation Key performance indicator scorecard editor
US8627192B2 (en) 2008-07-03 2014-01-07 Ebay Inc. System and methods for automatic media population of a style presentation
US10282391B2 (en) 2008-07-03 2019-05-07 Ebay Inc. Position editing tool of collage multi-media
US8893015B2 (en) 2008-07-03 2014-11-18 Ebay Inc. Multi-directional and variable speed navigation of collage multi-media
US8200578B2 (en) * 2008-07-09 2012-06-12 Hill Matthew D Methods and systems for account management and virtual agent design and implementation
US8171399B2 (en) * 2008-07-17 2012-05-01 International Business Machines Corporation Using an alternate user interface to a drag and drop interface for rearranging configurable web page components
US9026918B2 (en) * 2008-10-16 2015-05-05 Accenture Global Services Limited Enabling a user device to access enterprise data
US20100153866A1 (en) * 2008-12-11 2010-06-17 Accenture Global Services Gmbh Method and system for modifying the execution of a native application running on a portable electronic device
US20100235806A1 (en) * 2009-03-13 2010-09-16 Microsoft Corporation Rich Web Site Authoring And Design
US7770122B1 (en) 2010-04-29 2010-08-03 Cheman Shaik Codeless dynamic websites including general facilities
US9075854B2 (en) * 2010-11-05 2015-07-07 Apple Inc. Browser based database manipulation
CN102541904A (en) * 2010-12-25 2012-07-04 富泰华工业（深圳）有限公司 Webpage generation system
US10482475B2 (en) 2011-02-10 2019-11-19 Adp Dealer Services, Inc. Systems and methods for providing targeted advertising
IL221674B (en) * 2011-08-31 2018-10-31 Wix Com Ltd Adaptive user interface creation in multimedia creative design system
US20130298005A1 (en) * 2012-05-04 2013-11-07 Motorola Mobility, Inc. Drawing HTML Elements
US9367933B2 (en) 2012-06-26 2016-06-14 Google Technologies Holdings LLC Layering a line with multiple layers for rendering a soft brushstroke
US20140053060A1 (en) * 2012-08-17 2014-02-20 Launchbase, LLC Website development tool
US9046998B2 (en) * 2012-09-14 2015-06-02 Empire Technology Development Llc Cloud-based trash-can
WO2014055492A2 (en) * 2012-10-02 2014-04-10 Percussion Software, Inc. Lossless application of new information architecture to existing websites, web pages, and online content
US9280523B2 (en) * 2013-01-23 2016-03-08 Go Daddy Operating Company, LLC System for conversion of website content
CN103995662A (en) * 2013-02-19 2014-08-20 上海鼎讯电子有限公司 Touch operation processing method
US9535887B2 (en) * 2013-02-26 2017-01-03 Google Inc. Creation of a content display area on a web page
US9524273B2 (en) * 2013-03-11 2016-12-20 Oracle International Corporation Method and system for generating a web page layout using nested drop zone widgets having different software functionalities
US11205036B2 (en) 2013-03-11 2021-12-21 Oracle International Corporation Method and system for implementing contextual widgets
US9201977B2 (en) 2013-03-12 2015-12-01 Andrew K. Lukes Automatic flowchart-based webpage generation for troubleshooting or task completion without manual programming
US20140267380A1 (en) * 2013-03-13 2014-09-18 Corel Corporation System and method for efficiently viewing a style
US20140282139A1 (en) * 2013-03-13 2014-09-18 Outright, Inc. System for mobile content management
US11080734B2 (en) 2013-03-15 2021-08-03 Cdk Global, Llc Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities
SG11201601713WA (en) * 2013-09-06 2016-04-28 Mars Flag Corp Information processing apparatus, search server, web server, and computer program
US9672276B2 (en) 2013-09-30 2017-06-06 Microsoft Technology Licensing, Llc Multi-act creation user interface element
US10332068B2 (en) 2016-04-21 2019-06-25 Cdk Global, Llc Systems and methods for stocking an automobile
US10867285B2 (en) 2016-04-21 2020-12-15 Cdk Global, Llc Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes
US10853769B2 (en) 2016-04-21 2020-12-01 Cdk Global Llc Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes
US10326858B2 (en) 2017-05-23 2019-06-18 Cdk Global, Llc System and method for dynamically generating personalized websites
JP6766779B2 (en) * 2017-08-25 2020-10-14 オムロン株式会社 User interface development support device, user interface development support method, and user interface development support program
US11501351B2 (en) 2018-03-21 2022-11-15 Cdk Global, Llc Servers, systems, and methods for single sign-on of an automotive commerce exchange
US11190608B2 (en) 2018-03-21 2021-11-30 Cdk Global Llc Systems and methods for an automotive commerce exchange
CN112740161A (en) * 2018-09-20 2021-04-30 株式会社因爱宝哇呜 Terminal, method for controlling terminal, and recording medium having recorded therein program for implementing the method
BR112021023257A2 (en) 2019-05-20 2022-02-08 Wix Com Ltd Website building system and method for a website building system
US11403960B2 (en) * 2019-08-06 2022-08-02 Adp, Inc. Product demonstration creation toolset that provides for entry of persistent data during use of the demonstration
US11216602B2 (en) * 2019-12-20 2022-01-04 Accenture Global Solutions Limited Micro frontends with model-based state
US11080105B1 (en) 2020-11-18 2021-08-03 Cdk Global, Llc Systems, methods, and apparatuses for routing API calls
US11514021B2 (en) 2021-01-22 2022-11-29 Cdk Global, Llc Systems, methods, and apparatuses for scanning a legacy database
US11803535B2 (en) 2021-05-24 2023-10-31 Cdk Global, Llc Systems, methods, and apparatuses for simultaneously running parallel databases
TR2021021789A2 (en) * 2021-12-30 2022-01-21 Turkcell Technology Research And Development Co CREATING A FACEPLATE SYSTEM

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1994028480A1 (en) * 1993-05-24 1994-12-08 Media Station, Inc. Interactive multimedia development system and method
JP2906949B2 (en) * 1993-10-27 1999-06-21 富士ゼロックス株式会社 Hypertext device
JP2692782B2 (en) * 1993-12-13 1997-12-17 インターナショナル・ビジネス・マシーンズ・コーポレイション How to link objects

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CRESPO A ET AL: "WebWriter: A browser-based editor for constructing Web applications", COMPUTER NETWORKS AND ISDN SYSTEMS, vol. 28, no. 11, May 1996 (1996-05-01), pages 1291-1306, XP004018228 *
DRAKOS N: "From text to hypertext: A post-hoc rationalisation of LaTeX2HTML", COMPUTER NETWORKS AND ISDN SYSTEMS, vol. 27, no. 2, November 1994 (1994-11-01), pages 215-224, XP004037992 *
HERB BETHONEY: "PageMill helps novice users create Web pages", ZIFF-DAVIS ONLINE PUBLICATIONS, 4 December 1995 (1995-12-04), pages 1 - 2, XP002046494 *
JURVIS J: "WYSIWYG Web design NetObjects Fusion", INFORMATIONWEEK, 28 OCT. 1996, CMP PUBLICATIONS, USA, no. 603, ISSN 8750-6874, pages 64, 66, XP002046492 *
K. RAMANI: "A smarter way to build Web sites : NetObjects Fusion software addresses critical need of Web site builders", NETOBJECTS PRESS RELEASE, 29 July 1996 (1996-07-29), pages 1 - 3, XP002046493 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999066433A1 (en) * 1998-06-16 1999-12-23 Easysite Australia Pty Ltd Real-time document management system
KR100787714B1 (en) * 1998-09-25 2007-12-21 후지쯔 가부시끼가이샤 Information processor, information processing method and medium
DE10053475A1 (en) * 2000-10-24 2002-05-02 Textmodule Gmbh Method for automated preparation of multilingual Internet presentations follows three steps to offer a computer novice text modules to be combined with individual data in a user's data file and written in a foreign language version.
EP2840511A4 (en) * 2012-04-16 2016-06-22 Oh Suk Kwon System and method for dynamically converting webpage, and computer-readable recording medium

Also Published As

Publication number Publication date
US20020023111A1 (en) 2002-02-21
US5845299A (en) 1998-12-01
AU3808297A (en) 1998-02-20

Similar Documents

Publication Publication Date Title
WO1998004978A1 (en) Draw-based editor for web pages
WO1998004983A1 (en) Hierarchical structure editor for web sites
US6826727B1 (en) Apparatus, methods, programming for automatically laying out documents
US9552331B2 (en) Method and apparatus for implementing web pages having smart tables
US6799299B1 (en) Method and apparatus for creating stylesheets in a data processing system
JP4344693B2 (en) System and method for browser document editing
US7246305B2 (en) Method and system for previewing and printing customized forms
US20060174199A1 (en) Web-based design system
US6986105B2 (en) Methods employing multiple clipboards for storing and pasting textbook components
US5860073A (en) Style sheets for publishing system
US7107522B1 (en) System and method for creating extensible content
US7191405B1 (en) System and method for editing information
US6311196B1 (en) Method and apparatus for implementing web pages having master borders
US20030079177A1 (en) Automatic layout of content in a design for a medium
JP2002189595A (en) Integrated method for creating refreshable web query
CA2337758A1 (en) System and method for processing and displaying product information on a computer
US20150161079A1 (en) File formats and methods for representing documents
US7685229B1 (en) System and method for displaying server side code results in an application program
Brooks Guide to HTML, JavaScript and PHP: for scientists and engineers
US20140215297A1 (en) File formats and methods for representing documents
US20100269036A1 (en) System and method for designing and generating online stationery
EP0843266A2 (en) Dynamic incremental updating of electronic documents
Brooks Programming in HTML and PHP Coding for Scientists and Engineers
EP0971295A1 (en) System for automatically organizing digital contents and recording medium on which automatically organized digital contents are recorded
US20050039122A1 (en) Methodology and system for rendering dynamic images

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AU BR CA CN IL JP KP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 1998508930

Format of ref document f/p: F

NENP Non-entry into the national phase

Ref country code: CA

122 Ep: pct application non-entry in european phase