extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-10-05 09:42:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update strings

Browse Source
This commit is contained in:
Miles Lott 2003-12-28 16:45:19 +00:00
parent 867a40667c
commit 9382d27026
5 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
setup/doc/setup3-1.html
View File

@ -7,11 +7,11 @@
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.59"><LINK
REL="HOME"
TITLE=" phpGroupWare Setup
TITLE=" eGroupWare Setup
"
HREF="setup3.html"><LINK
REL="PREVIOUS"
TITLE=" phpGroupWare Setup
TITLE=" eGroupWare Setup
"
HREF="setup3.html"><LINK
REL="NEXT"
@ -31,7 +31,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
>phpGroupWare Setup</TH
>eGroupWare Setup</TH
></TR
><TR
><TD
@ -111,7 +111,7 @@ $setup_info['addressbook']['enable'] = 1;
></TR
></TABLE
><P
> 'name' is used throughout phpgroupware, typically in $phpgw_info flags such as 'currentapp' or as the 'app_name' almost everywhere else.
> 'name' is used throughout egroupware, typically in $phpgw_info flags such as 'currentapp' or as the 'app_name' almost everywhere else.
</P
><P
> 'title' would be used in the navbar, admin, preferences, as well as in the application itself.
@ -123,7 +123,7 @@ $setup_info['addressbook']['enable'] = 1;
> 'app_order' determines the order of applications in the navbar. If the number you set here is the same as is set for another app, the app whose 'name' is first in the English alphabet would appear first. Smaller numbers show closer to the top or left end of the navbar, depending upon the layout.
</P
><P
> The 'enable' string is used by the phpgroupware API to determine whether an application is disabled, enabled, or enabled but hidden from the navbar. Most applications will want this set to a value of 1 (enabled). The notifywindow app sets this to 2, which keeps it off the navbar. An enable of 0 would disable the app by default. There is one other special case, 3, which is used primarily by the API itself. From the perspective of setup3, the API is an application just like any other application. By setting the 'enable' flag to 3, the API is still enabled, but will not be assignable to a user as a real application. It will thereby be hidden from the admin for application and user/group editing.
> The 'enable' string is used by the egroupware API to determine whether an application is disabled, enabled, or enabled but hidden from the navbar. Most applications will want this set to a value of 1 (enabled). The notifywindow app sets this to 2, which keeps it off the navbar. An enable of 0 would disable the app by default. There is one other special case, 3, which is used primarily by the API itself. From the perspective of setup3, the API is an application just like any other application. By setting the 'enable' flag to 3, the API is still enabled, but will not be assignable to a user as a real application. It will thereby be hidden from the admin for application and user/group editing.
</P
></DIV
><DIV
@ -245,7 +245,7 @@ CLASS="PROGRAMLISTING"
></TR
></TABLE
><P
> This is the standard dependency array for all phpgroupware applications. It states that this application requires the phpgwapi, and lists the versions with which versions this app is compatible. This list would need to be appended upon each new API release, assuming your application is compatible with this new API version. You may list other applications here, e.g. your app might depend upon 'email' in order to work properly.
> This is the standard dependency array for all egroupware applications. It states that this application requires the phpgwapi, and lists the versions with which versions this app is compatible. This list would need to be appended upon each new API release, assuming your application is compatible with this new API version. You may list other applications here, e.g. your app might depend upon 'email' in order to work properly.
</P
><P
> Do NOT list applications here without considering this: If you do list an application here, and your app does not really require it, your application will not install unless that other application is already installed. This is handled normally within the install/upgrade process loops, which will install only applications whose dependencies are satisfied. Using a multipass function, the applications are installed in the correct order to ensure that dependencies are resolved. In all cases, the API would be installed first in every new install or upgrade, since all applications depend on the API.
@ -346,7 +346,7 @@ NAME="AEN74"
>Any application which requires an upgrade to a previous version's tables will need this file.</A
></H3
><P
> This file will be the most complex of all setup-oriented files with which you will be working. It will contain all upgrade functions capable of upgrading any possible version of your phpgroupware app. These upgrade routines roughly match the old setup program's upgrade functions, but the use of objects and the methods have changed dramatically. The simplest version upgrade routine would look like:
> This file will be the most complex of all setup-oriented files with which you will be working. It will contain all upgrade functions capable of upgrading any possible version of your egroupware app. These upgrade routines roughly match the old setup program's upgrade functions, but the use of objects and the methods have changed dramatically. The simplest version upgrade routine would look like:
</P
><TABLE
BORDER="0"
@ -785,7 +785,7 @@ HREF="setup3-2.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>phpGroupWare Setup</TD
>eGroupWare Setup</TD
><TD
WIDTH="34%"
ALIGN="center"

4
setup/doc/setup3-2.html
View File

@ -7,7 +7,7 @@
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.59"><LINK
REL="HOME"
TITLE=" phpGroupWare Setup
TITLE=" eGroupWare Setup
"
HREF="setup3.html"><LINK
REL="PREVIOUS"
@ -31,7 +31,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
>phpGroupWare Setup</TH
>eGroupWare Setup</TH
></TR
><TR
><TD

4
setup/doc/setup3-3.html
View File

@ -7,7 +7,7 @@
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.59"><LINK
REL="HOME"
TITLE=" phpGroupWare Setup
TITLE=" eGroupWare Setup
"
HREF="setup3.html"><LINK
REL="PREVIOUS"
@ -31,7 +31,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
>phpGroupWare Setup</TH
>eGroupWare Setup</TH
></TR
><TR
><TD

4
setup/doc/setup3-4.html
View File

@ -7,7 +7,7 @@
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.59"><LINK
REL="HOME"
TITLE=" phpGroupWare Setup
TITLE=" eGroupWare Setup
"
HREF="setup3.html"><LINK
REL="PREVIOUS"
@ -27,7 +27,7 @@ CELLSPACING="0"
><TH
COLSPAN="3"
ALIGN="center"
>phpGroupWare Setup</TH
>eGroupWare Setup</TH
></TR
><TR
><TD

10
setup/doc/setup3.html
View File

@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
> phpGroupWare Setup
> eGroupWare Setup
</TITLE
><META
NAME="GENERATOR"
@ -20,7 +20,7 @@ CLASS="TITLEPAGE"
CLASS="TITLE"
><A
NAME="AEN2"
>phpGroupWare Setup</A
>eGroupWare Setup</A
></H1
><H3
CLASS="AUTHOR"
@ -37,7 +37,7 @@ NAME="AEN8"
><P
></P
><P
> A developer introduction to using the next generation setup application for phpgroupware.
> A developer introduction to using the next generation setup application for egroupware.
</P
><P
></P
@ -61,7 +61,7 @@ NAME="AEN12"
>Welcome</A
></H2
><P
> Thanks for taking the time to look over this document. If you are a developer who is new to phpgroupware, this document will be invaluable to your success during the life of your application. This is in addition to the other fine documentation available in the phpgwapi/doc directory in your install. Even long-time phpgw developers should benefit this document. Herein, I will attempt to outline the critical steps required in order to get along with setup3, setup-TNG, or whatever we end up calling it (Hey, how about 'setup'?)
> Thanks for taking the time to look over this document. If you are a developer who is new to egroupware, this document will be invaluable to your success during the life of your application. This is in addition to the other fine documentation available in the phpgwapi/doc directory in your install. Even long-time phpgw developers should benefit this document. Herein, I will attempt to outline the critical steps required in order to get along with setup3, setup-TNG, or whatever we end up calling it (Hey, how about 'setup'?)
</P
></DIV
><DIV
@ -82,7 +82,7 @@ NAME="AEN15"
> Setup3 adds multi-language support for the setup application, a long missed feature, I would imagine.
</P
><P
> Setup3 gives each application developer control over their application install and upgrade processes, while giving them access to work within a realm formerly owned by only the former core phpgroupware applications. Yes, this is extra work for the developer. But it is hoped that setup3 is also viewed as a tool that can truly enhance the development process.
> Setup3 gives each application developer control over their application install and upgrade processes, while giving them access to work within a realm formerly owned by only the former core egroupware applications. Yes, this is extra work for the developer. But it is hoped that setup3 is also viewed as a tool that can truly enhance the development process.
</P
><P
> OK. Let's dive right in...