From: webERP D. <web...@li...> - 2013-05-29 02:52:19
|
The demo DB is created automatically from the shell script build/make_release.sh this re xgettexts all the strings in the entire system into the en_GB.utf8/messages.pot and then remerges all the existing languages into their translation messages.po then creates the demo and new databases - using mysqldump - you can play with the logic to produce a chinese demo DB directly as an option from the installer! Yes some more error trapping - dare I say it maybe we should relent and bring in jQuery - have enjoyed playing with it myself and it is pretty small/only loaded once and irons out all the kinks with other browsers etc. Maybe time to get with the program and make our scripts use jQuery validation throughout - there is another 21k validation add on to jQuery which is very cool. Some choices for language COAs would be great if we could get submissions for other languages charts would be particularly great - we just need a dump of your chartmaster table - no balances or financial information. Phil On 29 May 2013 at 14:24 webERP Developers <web...@li...> wrote: > *Dear all:* > > Sorry for the late. > I'll try to close the file within 2 weeks. I think the basic spec > for this one is that: > > 1. We should detect if the environment meets webERP's > requirements. I found Tim has done some in his scripts. > 1.0: Client side: Cookie should be allowed, otherwise the session > cannot run properly, since we don't use URL to send the SID. > 1.1. PHP configuration: Php version; PHP safe mode( Is it allowed? > Shall we check it?); > recommend php extention: gettext; GD > 1.2. Server File system: Configure file writable; companies > directory writable; > 1.3 OS system. Maybe this part should be canceled. It can be > detected automatically. > 2 Users choices: > 2.1 Allow the user to select their language, COA(only those > available). > language validation for OS. If there is no locale > installed, throw out the warning that the language will not display > correctly. > 2.2 Allow users to input the administers mail address which > introduced by Richard. We should suggest the user to assign the mail here. > Or we just use currently mail address to record it in config.php? > 2.3 Install demo with production system together. Currently, > there is a bug that only one of them can be selected. > 2.4 User input mysql database information. Shall we test the > data here? There seems lots of problem for users to set their database. A > better idea maybe to verify their input. If they cannot input it correctly, > the installation should stop here. > 2.5 sql installation validation. It's better to throw out error > if there is database installation error. > > And I have another problem to prepare a Chinese version demo data. > There is only production used sql now. Is there any good idea to prepare a > demo quickly according to it? > > Any idea are welcome and highly appreciated! > > Thanks and best regards! > > Exson > > > > > > > > -- > View this message in context: > http://weberp-accounting.1478800.n4.nabble.com/Install-interface-internationalize-tp4656407p4656425.html > Sent from the web-ERP-developers mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers Phil Ph: +64 (0)275 567890 Skype: daintree http://www.logicworks.co.nz |