The Builder Clause Samples
The Builder. (i) shall be liable to the Buyer for any damage to or loss of any Buyer's Supplies occurring or arising after their delivery by (or on behalf of) the Buyer under Clause 6.1 unless such damage or loss is caused by the inadequate packing or inherent vice of such Buyer's Supplies; and
(ii) shall notify the Supervisor as soon as practicable of any loss of, damage to, or deficiency in the supply or performance of, any of the Buyer's Supplies or any late delivery thereof in accordance with Clause 6.3.
The Builder. Any of the events specified in Clauses 11.1.5 to 11.1.12 of this Clause shall occur in respect of the Builder at any time prior to the Delivery Date.
The Builder. (i) acknowledges that the Buyer intends to arrange for the Ship’s maiden cruise with fare paying passengers to be held on the Ship’s relocation voyage from the Delivery Port; (ii) acknowledges that it is imperative for the Ship to be ready at the time, and in the condition, provided for in this Contract so as to enable the Buyer to fulfil its commitments in relation to the Ship’s maiden cruise; (iii) agrees to do all it can to assist the Buyer to fulfil its commitments in relation to the Ship’s maiden cruise; and (iv) acknowledges that if delivery of the Ship is not made on the Delivery Date, the Buyer will suffer loss and damage (including reputational damage) in amounts which are extremely difficult to quantify in advance and agrees that the per day sums set out in Clause 2.15 represent a genuine and reasonable pre-estimate of the Buyer’s loss and damage for each day of delay in delivery of the Ship beyond the Delivery Date.
The Builder. Any of the events specified in Clauses 11.1.5 to 11.1.12 of this Clause shall occur in respect of the Builder at any time prior to the Redelivery Date.
The Builder. 6.1 The Builder shall comply with the Construction EMP in respect of the works and protect the environment against environmental damage.
6.2 The Builder shall undertake the due and punctual performance of all obligations imposed on it in terms of or arising from this Agreement or any breach thereof.
6.3 The Builder shall undertake to co-operate fully with the ESO, Owner and HOA, and use its best endeavours to ensure that the objectives of this Agreement are fulfilled in the course of its execution of the works or relevant part thereof.
6.4 The Builder shall undertake to impose the obligations contained in this Agreement on each of its subcontractors and to use its best endeavours to ensure that such conditions are complied with by the subcontractors.
6.5 The Builder shall comply with all relevant Building regulations.
The Builder. JR NZ Group Ltd, a limited liability company having its registered office at ▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇▇▇, Upper Hutt 5018, Wellington.
The Builder. The third option of the main screen (see Figure 5) provides the user with the possibility to build her own app from scratch or using basic templates. The app builder allows teachers to create new apps to fit their needs without advanced programming or the help of an external programmer. The builder will enable teachers to create missing apps to support their learning scenarios. Most likely, the builder module of the app composer will only be used by a fraction of the teachers since creating an app from scratch will always be a rather complex process. There is a tradeoff: by making systems very simple, the system often becomes less powerful. If we want to create a general app builder, then it will probably require an investment of the teachers to learn how to operate this tool. Furthermore, approaches for non-programmers to adding advanced logic to apps, such as graphical programming, exist, but also often have a learning curve. Therefore, we regard the builder module as a tool for advanced, expert teachers. Due to the large scope of the builder module we will only discuss two mockups here. Figure 14 illustrates the ‘View’ module of the builder, which allows the user to draw and configure the user interface. In the center of the screen the app’s UI is shown. Such a UI can be assembled by dragging and dropping different components available in the panel on the left side. The column with icons next to the left panel provides some basic functionality to load and save your app and manipulate the graphical components of the app’s UI. On the right-side panel, one can set different properties of the component that is selected in the center part. In Figure 14, the user has selected the formula editor and has configured for instance its size to 100x20px. Application logic can be added to the UI components composed in the view module. One can configure this in the ‘Logic’ module, which is accessible through the tabs on top of the left-side panel. This logic module allows: (i) to define variables that can be used in the logic and view, (ii) to model progress and animations, (iii) to program the logic using the defined variables and (iv) to describe events and their effect. Figure 15 demonstrates the ‘Variables’ mod- ule that allows users to define the variables they want to use in the ‘Progress’, ‘Code’ and ‘Events’ modules. Furthermore, these variables can be used in the ‘View’ module as is illustrated in Figure 14. On the right panel of the view module one can confi...