You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(20) |
Aug
(21) |
Sep
(12) |
Oct
(2) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(3) |
Feb
(46) |
Mar
(65) |
Apr
(49) |
May
(33) |
Jun
(5) |
Jul
(79) |
Aug
(228) |
Sep
(347) |
Oct
(272) |
Nov
(270) |
Dec
(424) |
2005 |
Jan
(549) |
Feb
(232) |
Mar
(134) |
Apr
(103) |
May
(57) |
Jun
(74) |
Jul
(67) |
Aug
(45) |
Sep
(99) |
Oct
(187) |
Nov
(238) |
Dec
(127) |
2006 |
Jan
(81) |
Feb
(137) |
Mar
(46) |
Apr
(55) |
May
(62) |
Jun
(152) |
Jul
(137) |
Aug
(154) |
Sep
(176) |
Oct
(104) |
Nov
(65) |
Dec
(64) |
2007 |
Jan
(56) |
Feb
(303) |
Mar
(88) |
Apr
(80) |
May
(72) |
Jun
(20) |
Jul
(47) |
Aug
(28) |
Sep
(113) |
Oct
(49) |
Nov
(89) |
Dec
(24) |
2008 |
Jan
(24) |
Feb
(61) |
Mar
(43) |
Apr
(51) |
May
(12) |
Jun
(10) |
Jul
(49) |
Aug
(26) |
Sep
(7) |
Oct
(50) |
Nov
(19) |
Dec
(15) |
2009 |
Jan
(87) |
Feb
(144) |
Mar
(54) |
Apr
(72) |
May
(32) |
Jun
(23) |
Jul
(27) |
Aug
(90) |
Sep
(349) |
Oct
(174) |
Nov
(320) |
Dec
(110) |
2010 |
Jan
(162) |
Feb
(39) |
Mar
(80) |
Apr
(126) |
May
(45) |
Jun
(44) |
Jul
(75) |
Aug
(32) |
Sep
(100) |
Oct
(57) |
Nov
(49) |
Dec
(125) |
2011 |
Jan
(72) |
Feb
(41) |
Mar
(63) |
Apr
(18) |
May
(123) |
Jun
(100) |
Jul
(96) |
Aug
(84) |
Sep
(83) |
Oct
(39) |
Nov
(166) |
Dec
(103) |
2012 |
Jan
(158) |
Feb
(148) |
Mar
(77) |
Apr
(43) |
May
(126) |
Jun
(82) |
Jul
(67) |
Aug
(28) |
Sep
(109) |
Oct
(30) |
Nov
(23) |
Dec
(34) |
2013 |
Jan
(14) |
Feb
(16) |
Mar
(7) |
Apr
(79) |
May
(76) |
Jun
(13) |
Jul
(76) |
Aug
(36) |
Sep
(22) |
Oct
(35) |
Nov
(167) |
Dec
(93) |
2014 |
Jan
(64) |
Feb
(14) |
Mar
(57) |
Apr
(63) |
May
(60) |
Jun
(15) |
Jul
(24) |
Aug
(19) |
Sep
(56) |
Oct
(70) |
Nov
(45) |
Dec
(52) |
2015 |
Jan
(56) |
Feb
(73) |
Mar
(34) |
Apr
(11) |
May
(24) |
Jun
(19) |
Jul
(11) |
Aug
(8) |
Sep
(25) |
Oct
(22) |
Nov
(38) |
Dec
(7) |
2016 |
Jan
(7) |
Feb
(34) |
Mar
(17) |
Apr
(10) |
May
(17) |
Jun
(7) |
Jul
(17) |
Aug
(31) |
Sep
(3) |
Oct
(34) |
Nov
(5) |
Dec
(2) |
2017 |
Jan
|
Feb
(4) |
Mar
(18) |
Apr
(6) |
May
(10) |
Jun
(13) |
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
2018 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
(10) |
May
(5) |
Jun
|
Jul
(7) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(2) |
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(6) |
Aug
(2) |
Sep
(4) |
Oct
|
Nov
|
Dec
(3) |
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
2022 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(30) |
Nov
|
Dec
(2) |
From: skaill <sk...@ro...> - 2004-09-20 21:39:54
|
Here's another, Jake...it's about only translating boolean when displayed, not when set or tested... ----- Original Message ----- From: "skaill" <sk...@ro...> To: <web...@li...> Sent: Friday, September 03, 2004 8:01 AM Subject: Re: [Web-erp-developers] Translation > I would agree. It is a fairly simple conversion and would introduxe an > error as opposed to screwing up the logic. We are only putting in . and ' > and _ ( ). The only added concern is the possible booleans which will be > fine if everyone understands to translate them only when displayed. The > booleans will be obvious because they will all have a 'Y' or 'N' hard coded > in an if statement. That's what they're meant for. > > If you see a 'Y' or 'N' then if you are not sure then DON'T change them. > > Steve > > ----- Original Message ----- > From: "Phil Daintree" <we...@pa...> > To: <web...@li...> > Sent: Friday, September 03, 2004 6:57 AM > Subject: Re: [Web-erp-developers] Translation > > > > This is quite a serious concern with this project. It would be most > > upsetting to introduce more problems than we resolve - I am very keen to > > keep the code stable. I am fairly confident (I think) that these changes > > will cause parsing errors if there is a mistake in the code ie missed > > out a . or closing ' or something so I am thinking that the page will be > > ok or it wont actually run. If it runs then there is a good chance that > > no logic errors will be introduced. The only area of concern is the use > > of submit buttons where I have tested for a returned value. In most > > cases these can be changed to isset. > > > > Phil > > > > On Thu, 2004-09-02 at 23:22, skaill wrote: > > > Sure, I think I can do those pages but I can only superficially test > them as > > > I'm honestly not that familiar with those areas and may not know if I've > > > introduced an error. Unfortunately you may need to do some extended > testing > > > if you want to have good confidence in all the translation code changes. > > > > > > After we do each section we should get someone who is using webERP and > wants > > > translation to use it for a week or two to make sure there are no errors > > > with what we've done. After that, proceed to the next set. > > > > > > The types of changes we are making theoretically should not get us into > much > > > trouble though. > > > > > > Although the value gets changed in the Submit (and other inputs) the > name > > > should remain the same to keep the code all in one language (English). > > > > > > One tricky circumstance is if 'Y' and 'N' have been used for boolean. > > > These values get stored as data. The data cannot be translated from Y > or N > > > as stored or the logic test of if TestFlag == "Y" wouldn't work when you > > > changed languages. It would work if you changed the right half but only > for > > > one language! The best solution is to translate when displayed. > > > > > > It all has to do with display time as opposed to code logic. > > > > > > Steve > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by BEA Weblogic Workshop > > FREE Java Enterprise J2EE developer tools! > > Get your free copy of BEA WebLogic Workshop 8.1 today. > > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > > _______________________________________________ > > Web-erp-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: skaill <sk...@ro...> - 2004-09-20 21:34:52
|
Here's another about moving $title... below session.inc but above header.inc... ----- Original Message ----- From: "Phil Daintree" <we...@pa...> To: <web...@li...> Sent: Thursday, September 09, 2004 6:28 AM Subject: Re: [Web-erp-developers] Multilanguage - includes > That makes sense Steve. > > I think it may be more interesting with PDF report scripts (not that > they will work in multi-language) since the LanguageSetup.php is > included in PDFStarter_ros.php and we need to handle errors with html so > header.inc gets included before any html output. > > Phil > > On Thu, 2004-09-09 at 21:53, skaill wrote: > > I've noticed this type of thing in some scripts... > > > > $title = 'Receive Controlled Items'; > > $PageSecurity = 11; > > > > /* Session started in header.inc for password checking and > > authorisation level check */ > > include('includes/DefinePOClass.php'); > > include('includes/DefineSerialItems.php'); > > include('includes/session.inc'); > > include('includes/header.inc'); > > > > If $title was moved below session.inc and above header.inc that would > > be good for $title. However, DefineSerialItems.php has a string in it > > which means it also needs to be after session.inc. > > > > session.inc never uses any includes before it and verifies access so > > I'm thinking session.inc should always be the first include anyway. > > Can you confirm this Phil? > > > > Steve > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: skaill <sk...@ro...> - 2004-09-20 21:32:53
|
Here's one note, Jake... ----- Original Message -----=20 From: skaill=20 To: web...@li...=20 Sent: Thursday, September 09, 2004 8:25 AM Subject: [Web-erp-developers] Multilanguage - note Select/Option statements in html may create confusion while doing the = Multilanguage. The way to handle them is to not change the if tests or = the values of the options, only change what is displayed. e.g. echo '<SELECT NAME=3D"Ostg_or_All">'; if ($_POST["Ostg_or_All"]=3D=3D'All'){ echo '<OPTION SELECTED Value=3D"All">' . _('Show All') . ' ' . $Type . = ' ' . _('in the date range'); echo '<OPTION Value=3D"Ostdg">' . _('Show Only Un-matched') . ' ' . = $Type; } else { echo '<OPTION Value=3D"All">' . _('Show All') . ' ' . $Type . ' ' . = _('in the date range'); echo '<OPTION SELECTED Value=3D"Ostdg">' . _('Show Only Un-matched') . = ' ' . $Type; } echo '</SELECT></TD></TR>'; Notice the if is still 'All' and so is the Value for the option. Steve |
From: skaill <sk...@ro...> - 2004-09-20 21:30:39
|
Phil's in charge of who's doing which scripts for Multilanguage. I'll try to dig out that info... Steve ----- Original Message ----- From: "Jake Stride" <ns...@us...> To: <web...@li...> Sent: Monday, September 20, 2004 5:25 PM Subject: Re: [Web-erp-developers] wegs-erp > Yes I have just read the original thread. If you give me say 5 to kick > off with, i'll see get them done asap. > > Jake > > skaill wrote: > > >There are a few additional things to watch out for, Jake. We would need to > >dig up some info that was in one of these emails detailing what to do. It's > >not tough but you need to be aware of them. > > > >Steve > > > >----- Original Message ----- > >From: "Jake Stride" <ns...@us...> > >To: <web...@li...> > >Sent: Monday, September 20, 2004 4:59 PM > >Subject: Re: [Web-erp-developers] wegs-erp > > > > > > > > > >>I can help do some scripts, if it is simply a case of putting _() around > >>echo statements, then I am sure if you send me a batch of scripts (ie > >>there names) to do I could find some time this week to convert some. > >> > >>Jake > >> > >>skaill wrote: > >> > >> > >> > >>>We need everyone including myself to dive back into getting the > >>>Multilanguage done. I could do at least 20 scripts in a day but I might > >>> > >>> > >be > > > > > >>>crazy by the end of it! > >>> > >>>Steve > >>> > >>>----- Original Message ----- > >>>From: "Daintrees" <p.d...@pa...> > >>>To: <web...@li...> > >>>Sent: Monday, September 20, 2004 4:24 PM > >>>Subject: Re: [Web-erp-developers] wegs-erp > >>> > >>> > >>> > >>> > >>> > >>> > >>>>I dont think it will be that big a problem to get webERP to work with > >>>>Postgres. > >>>>I also think choice is a good thing and at this stage webERP is tied to > >>>>MySQL. > >>>>If the multi-language is finished, if the serial items is finished then > >>>> > >>>> > >I > > > > > >>>>could get fired up in a different direction. I don't like half done > >>>> > >>>> > >jobs, > > > > > >>>> > >>>> > >>>so > >>> > >>> > >>> > >>> > >>>>I'll go gettextify another script! > >>>> > >>>>Phil > >>>> > >>>>----- Original Message ----- > >>>>From: "skaill" <sk...@ro...> > >>>>To: <web...@li...> > >>>>Sent: Tuesday, September 21, 2004 2:07 AM > >>>>Subject: Re: [Web-erp-developers] wegs-erp > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>Before doing extensive work you may want to check with Phil. With the > >>>>>Multilanguage going on almost all of the files have some sort of > >>>>> > >>>>> > >changes > > > > > >>>>>being done to them. > >>>>> > >>>>>Sounds like the two biggest challenges are: > >>>>> > >>>>>1) Getting to a place of one common DBMS. Personally, I would choose > >>>>> > >>>>> > >>>>> > >>>>> > >>>>mysql > >>>> > >>>> > >>>> > >>>> > >>>>>because you get two benefits: You can then offer postgres and mysql > >>>>>versions of your product and the two products would then be much better > >>>>> > >>>>> > >>>>> > >>>>> > >>>>and > >>>> > >>>> > >>>> > >>>> > >>>>>easier to integrate. I guess you could move webERP onto postgres but it > >>>>>wouldn't be my first choice. > >>>>> > >>>>>2) Identifying all of the common database tables and seeing how they > >>>>> > >>>>> > >>>>> > >>>>> > >>>vary > >>> > >>> > >>> > >>> > >>>>>from one product to another. If there are parts where it varies > >>>> > >>>> > >>>>>substantially then deciding whether to bring it to one common ground or > >>>>> > >>>>> > >>>>> > >>>>> > >>>>have > >>>> > >>>> > >>>> > >>>> > >>>>>some duplication and providing interfaces between. Sort of an > >>>>> > >>>>> > >automated > > > > > >>>>>referential integrity thing but this is probably not that wise. I > >>>>> > >>>>> > >doubt > > > > > >>>>> > >>>>> > >>>>the > >>>> > >>>> > >>>> > >>>> > >>>>>common tables will present that great a challenge in combining. > >>>>> > >>>>>Also, it would be good to identify which operations they have in common > >>>>> > >>>>> > >>>>> > >>>>> > >>>to > >>> > >>> > >>> > >>> > >>>>>figure out the best way to resolve it so one does not negatively affect > >>>>> > >>>>> > >>>>> > >>>>> > >>>>the > >>>> > >>>> > >>>> > >>>> > >>>>>other. > >>>>> > >>>>>Just some thinking out loud... > >>>>> > >>>>>One thing is for sure. Combining both products would be a more > >>>>> > >>>>> > >powerful > > > > > >>>>> > >>>>> > >>>>all > >>>> > >>>> > >>>> > >>>> > >>>>>round solution ;) Combining teams makes all of us much more powerful > >>>>> > >>>>> > >as > > > > > >>>>>well. > >>>>> > >>>>>Steve > >>>>> > >>>>>----- Original Message ----- > >>>>>From: "Jake Stride" <ns...@us...> > >>>>>To: <web...@li...> > >>>>>Sent: Monday, September 20, 2004 8:01 AM > >>>>>Subject: [Web-erp-developers] wegs-erp > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>As Dick Stins mentioned in one of hs previous email : > >>>>>> > >>>>>>"The design of these issues should be loosely connected or we should > >>>>>>create one big project (wegs-erp?)." > >>>>>> > >>>>>>Is this something that people would be interested in? > >>>>>> > >>>>>>I for one have little knowledge of ERP, but from a coding and > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>CRM/project > >>>> > >>>> > >>>> > >>>> > >>>>>management side of things, I am fairly well versed and have enough > >>>>> > >>>>> > >>>>> > >>>>> > >>>>knowledge > >>>> > >>>> > >>>> > >>>> > >>>>>of ERP to see how the two systems could work together to form a pretty > >>>>>comprehensive business tool. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>I am now in a position to start working on integrating EGS/weberp but > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>would like to know peoples views on the situation and the best way to > >>>>>proceed. For example the address book for EGS is a core component to > >>>>> > >>>>> > >the > > > > > >>>>>entire system and indeed the CRM functionality runs from it so perhaps > >>>>> > >>>>> > >>>>> > >>>>> > >>>the > >>> > >>> > >>> > >>> > >>>>>first issue i have is now to over come the integration of the two > >>>>> > >>>>> > >>>>> > >>>>> > >>>address > >>> > >>> > >>> > >>> > >>>>>books. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>Thanks > >>>>>> > >>>>>>Jake > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>------------------------------------------------------- > >>>>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>>>>Project Admins to receive an Apple iPod Mini FREE for your judgement > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>on > >>> > >>> > >>> > >>> > >>>>>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>>>>_______________________________________________ > >>>>>>Web-erp-developers mailing list > >>>>>>Web...@li... > >>>>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>------------------------------------------------------- > >>>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>>>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>>>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>>>_______________________________________________ > >>>>>Web-erp-developers mailing list > >>>>>Web...@li... > >>>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>------------------------------------------------------- > >>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>>_______________________________________________ > >>>>Web-erp-developers mailing list > >>>>Web...@li... > >>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>>> > >>>> > >>>> > >>>> > >>> > >>>------------------------------------------------------- > >>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>_______________________________________________ > >>>Web-erp-developers mailing list > >>>Web...@li... > >>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>> > >>> > >>> > >>> > >> > >>------------------------------------------------------- > >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>who ports your project to Linux PPC the best. Sponsored by IBM. > >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>_______________________________________________ > >>Web-erp-developers mailing list > >>Web...@li... > >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >> > >> > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > >who ports your project to Linux PPC the best. Sponsored by IBM. > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >_______________________________________________ > >Web-erp-developers mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: Jake S. <ns...@us...> - 2004-09-20 21:25:27
|
Yes I have just read the original thread. If you give me say 5 to kick off with, i'll see get them done asap. Jake skaill wrote: >There are a few additional things to watch out for, Jake. We would need to >dig up some info that was in one of these emails detailing what to do. It's >not tough but you need to be aware of them. > >Steve > >----- Original Message ----- >From: "Jake Stride" <ns...@us...> >To: <web...@li...> >Sent: Monday, September 20, 2004 4:59 PM >Subject: Re: [Web-erp-developers] wegs-erp > > > > >>I can help do some scripts, if it is simply a case of putting _() around >>echo statements, then I am sure if you send me a batch of scripts (ie >>there names) to do I could find some time this week to convert some. >> >>Jake >> >>skaill wrote: >> >> >> >>>We need everyone including myself to dive back into getting the >>>Multilanguage done. I could do at least 20 scripts in a day but I might >>> >>> >be > > >>>crazy by the end of it! >>> >>>Steve >>> >>>----- Original Message ----- >>>From: "Daintrees" <p.d...@pa...> >>>To: <web...@li...> >>>Sent: Monday, September 20, 2004 4:24 PM >>>Subject: Re: [Web-erp-developers] wegs-erp >>> >>> >>> >>> >>> >>> >>>>I dont think it will be that big a problem to get webERP to work with >>>>Postgres. >>>>I also think choice is a good thing and at this stage webERP is tied to >>>>MySQL. >>>>If the multi-language is finished, if the serial items is finished then >>>> >>>> >I > > >>>>could get fired up in a different direction. I don't like half done >>>> >>>> >jobs, > > >>>> >>>> >>>so >>> >>> >>> >>> >>>>I'll go gettextify another script! >>>> >>>>Phil >>>> >>>>----- Original Message ----- >>>>From: "skaill" <sk...@ro...> >>>>To: <web...@li...> >>>>Sent: Tuesday, September 21, 2004 2:07 AM >>>>Subject: Re: [Web-erp-developers] wegs-erp >>>> >>>> >>>> >>>> >>>> >>>> >>>>>Before doing extensive work you may want to check with Phil. With the >>>>>Multilanguage going on almost all of the files have some sort of >>>>> >>>>> >changes > > >>>>>being done to them. >>>>> >>>>>Sounds like the two biggest challenges are: >>>>> >>>>>1) Getting to a place of one common DBMS. Personally, I would choose >>>>> >>>>> >>>>> >>>>> >>>>mysql >>>> >>>> >>>> >>>> >>>>>because you get two benefits: You can then offer postgres and mysql >>>>>versions of your product and the two products would then be much better >>>>> >>>>> >>>>> >>>>> >>>>and >>>> >>>> >>>> >>>> >>>>>easier to integrate. I guess you could move webERP onto postgres but it >>>>>wouldn't be my first choice. >>>>> >>>>>2) Identifying all of the common database tables and seeing how they >>>>> >>>>> >>>>> >>>>> >>>vary >>> >>> >>> >>> >>>>>from one product to another. If there are parts where it varies >>>> >>>> >>>>>substantially then deciding whether to bring it to one common ground or >>>>> >>>>> >>>>> >>>>> >>>>have >>>> >>>> >>>> >>>> >>>>>some duplication and providing interfaces between. Sort of an >>>>> >>>>> >automated > > >>>>>referential integrity thing but this is probably not that wise. I >>>>> >>>>> >doubt > > >>>>> >>>>> >>>>the >>>> >>>> >>>> >>>> >>>>>common tables will present that great a challenge in combining. >>>>> >>>>>Also, it would be good to identify which operations they have in common >>>>> >>>>> >>>>> >>>>> >>>to >>> >>> >>> >>> >>>>>figure out the best way to resolve it so one does not negatively affect >>>>> >>>>> >>>>> >>>>> >>>>the >>>> >>>> >>>> >>>> >>>>>other. >>>>> >>>>>Just some thinking out loud... >>>>> >>>>>One thing is for sure. Combining both products would be a more >>>>> >>>>> >powerful > > >>>>> >>>>> >>>>all >>>> >>>> >>>> >>>> >>>>>round solution ;) Combining teams makes all of us much more powerful >>>>> >>>>> >as > > >>>>>well. >>>>> >>>>>Steve >>>>> >>>>>----- Original Message ----- >>>>>From: "Jake Stride" <ns...@us...> >>>>>To: <web...@li...> >>>>>Sent: Monday, September 20, 2004 8:01 AM >>>>>Subject: [Web-erp-developers] wegs-erp >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>As Dick Stins mentioned in one of hs previous email : >>>>>> >>>>>>"The design of these issues should be loosely connected or we should >>>>>>create one big project (wegs-erp?)." >>>>>> >>>>>>Is this something that people would be interested in? >>>>>> >>>>>>I for one have little knowledge of ERP, but from a coding and >>>>>> >>>>>> >>>>>> >>>>>> >>>>CRM/project >>>> >>>> >>>> >>>> >>>>>management side of things, I am fairly well versed and have enough >>>>> >>>>> >>>>> >>>>> >>>>knowledge >>>> >>>> >>>> >>>> >>>>>of ERP to see how the two systems could work together to form a pretty >>>>>comprehensive business tool. >>>>> >>>>> >>>>> >>>>> >>>>>>I am now in a position to start working on integrating EGS/weberp but >>>>>> >>>>>> >>>>>> >>>>>> >>>>>would like to know peoples views on the situation and the best way to >>>>>proceed. For example the address book for EGS is a core component to >>>>> >>>>> >the > > >>>>>entire system and indeed the CRM functionality runs from it so perhaps >>>>> >>>>> >>>>> >>>>> >>>the >>> >>> >>> >>> >>>>>first issue i have is now to over come the integration of the two >>>>> >>>>> >>>>> >>>>> >>>address >>> >>> >>> >>> >>>>>books. >>>>> >>>>> >>>>> >>>>> >>>>>>Thanks >>>>>> >>>>>>Jake >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>------------------------------------------------------- >>>>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>>>>Project Admins to receive an Apple iPod Mini FREE for your judgement >>>>>> >>>>>> >>>>>> >>>>>> >>>on >>> >>> >>> >>> >>>>>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>>>>_______________________________________________ >>>>>>Web-erp-developers mailing list >>>>>>Web...@li... >>>>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>>>>> >>>>>> >>>>>> >>>>>> >>>>>------------------------------------------------------- >>>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>>>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>>>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>>>_______________________________________________ >>>>>Web-erp-developers mailing list >>>>>Web...@li... >>>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>>>> >>>>> >>>>> >>>>> >>>>> >>>>------------------------------------------------------- >>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>>_______________________________________________ >>>>Web-erp-developers mailing list >>>>Web...@li... >>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>>> >>>> >>>> >>>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>_______________________________________________ >>>Web-erp-developers mailing list >>>Web...@li... >>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>> >>> >>> >>> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>who ports your project to Linux PPC the best. Sponsored by IBM. >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>_______________________________________________ >>Web-erp-developers mailing list >>Web...@li... >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > |
From: Stins, D. <DR...@Zi...> - 2004-09-20 21:17:25
|
Steve, When mysql releases with stored procedures and triggers are commonly used, then it will be a piece of a cake to convince some one that this will improve the data integrity dramatically. And that's all accountants wants: reliable data. For now, I think it will be a great improvement when we isolate the business rules in classes when we do maintenance at scripts or when we develop new scripts for new functionality. Like you mentioned: improve things slowly, so web-erp will improve instead of be unstable. with best regards, Dick Stins ----- Original Message ----- From: "skaill" <sk...@ro...> To: <web...@li...> Sent: Monday, September 20, 2004 10:54 PM Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > In theory 3-tier is a great idea, however it has some drawbacks too. I > don't know of a system anywhere as near as complete as webERP that has true > 3-tier separation. An accounting system in particular is critical to a > business. It must be very, very reliable. For this reason, typically you > will see less than state of the art at banks and government for instance. > Someone's neck would be on the line if things got out of control and they > can very easily. > > There are some other important reasons for carefully considering the > approach. Many who will put their attention toward webERP will be > accountants who may not be computer experts like us. Going too extreme can > alienate them from contributing even though they are the ones who more > likely understand the full extent of deeper accounting problems. > > What I'm saying here is I think it's a fine line and a line that, in the > interest of keeping the product stable, bringing more people on board and > keeping people onboard, needs to be moved slowly. > > Side note: While I do believe in isolating the business rules, I do not > believe planting business rules in the triggers of a database or in stored > procedures is beneficial, I would keep them in code. Triggers and stored > procedures lead to bits and pieces everywhere. > > Steve > > ----- Original Message ----- > From: "Stins, Dick" <DR...@Zi...> > To: <web...@li...> > Sent: Monday, September 20, 2004 4:29 PM > Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > Yes, any technical database layer is not that interesting, although it's > > always handy when it is not too much work to move to another database > > engine, but I see no need to change from mysql to another database engine > at > > the moment. Solution like pear:db seems only to slow things down and hide > > the real code and creates more trouble when in pear:DB (or any other > > wrapper) are some bugs. > > > > When I talk about a database layer, it's functional. Like you have a > > function to delete a customer. > > This functions checks all business constraints before deleting: > > - are there any transaction related? > > - are there any open orders? > > - are there any companies related to this customer? > > - is it an active customer? > > - is it bankrupt? > > - ... > > > > When one or more checks fail, then the function returns an understandable > > error and refuses to continue. > > > > When you have this function, then you are able to call it from any script, > > like a delete script, or a batch script which deletes lot's of customers, > or > > a webservices which tries to process delete the customer. > > > > The same for a create customer function. When all attributes (credit > check, > > address, chamber of commerce number, tax number, telephone number, > > bankaccount number, ...) of the customer are properly set, then the status > > of this customer will be valid. > > > > When you have one set of functions/methods to set all these items, then > you > > again can reuse this code (CLASS METHODS) of lot's of places. > > > > When you have a problem with creation of customers, then you know you > where > > to find the one and only place where it was coded: in the data layer > > (customer class). > > > > Where all rules are coded is not that important. You can use php classes, > > php functions, sql, database triggers, stored procedures or foreign keys, > > column constraints, table constraints, ... > > Just collect everything for manipulating customers and put them in the > same > > place where you can call it from everywhere, so you need not to code it > > twice and test it twice and debug it twice or more. > > > > Use this principle for every object (table or combination of tables or > ..). > > Every developer would know where to look when there is a problem with the > > process creating or deleting or updating a customer. > > > > When someone still would like to port the software package to another > > database system, then he has only to port the database layer and is not > > disturbed by the presentation layer and ... > > > > Resume: the above principle/architecture is based at two ideas: > > 1. you always knows where to find object (table) related functions, so you > > are not attracted to code same functions again and again but just calls > them > > again > > 2. you only code once the business rules and are able to reuse them > several > > times by calling them from several php scripts, batch scripts, > webservices, > > .... > > > > With best regards, > > > > Dick Stins > > > > ----- Original Message ----- > > From: "Daintrees" <p.d...@pa...> > > To: <web...@li...> > > Sent: Monday, September 20, 2004 9:24 AM > > Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > You'll have to excuse my naievety (and poor spelling) since most of the > > > native functions are similar in function but different in name for > > differing > > > DBs why does one need such a lavish abstraction layer why won't a > > > ConnectDB.inc calling the native C calls to connect directly for other > DBs > > > do the trick? This way we have ultimate performance minimum overhead! > > > > > > I really don't understand why such lengths are necessary - the function > > > calls are virtually one to one and even most of the parameters are the > > same. > > > > > > MS SQL Server > > > > > > mssql_connect > > > mssql_fetch_array > > > mssql_fetch_row > > > mssql_data_seek > > > > > > > > > MySql > > > > > > mysql_connect > > > mysql_query > > > mysql_fetch_array > > > mysql_fetch_row > > > mysql_data_seek > > > > > > Postgres > > > > > > pg_connect > > > pg_query > > > pg_fetch_array > > > pg_fetch_row > > > pg_data_seek > > > > > > > > > Firebird/interbase > > > > > > ibase_connect > > > ibase_query > > > ibase_fetch_assoc > > > ibase_fetch_row > > > > > > whoops there is no > > > ibase_data_seek > > > > > > maybe I'm answering my own question! > > > > > > > > > Phil > > > > > > > > > ----- Original Message ----- > > > From: "Jake Stride" <ns...@us...> > > > To: <web...@li...> > > > Sent: Monday, September 20, 2004 5:58 PM > > > Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > > Stins, Dick wrote: > > > > > > > > >Jake, > > > > > > > > > >Thanks for your comments. > > > > > > > > > >I am not a fan of pear:db. I prefer to use standard sql. That is > > already > > > a > > > > >big step for portability + the clean and mean weberp script > > > ConnectDB.inc. > > > > >So it should not be too hard to port web-erp to another db engine. > > > > > > > > > > > > > > No to be honest neither am I, for reasons I won't bore you with it was > > > > chosen at the start of the project and has persited through. Have you > > > > had a look at > > > > > > > > http://creole.phpdb.org/ > > > > http://propel.phpdb.org/wiki/ > > > > > > > > >Smarty might be interesting, but I am already glad when css is > optimal > > > used. > > > > > > > > > > > > > > This is the case with EGS, it just allows all of the presentation > logic > > > > to be removed from the code base and allows people to be a lot more > > > > flexible with the layout without having to trawl through the PHP code. > > > > > > > > >Multiple company support is interesting. > > > > > > > > > > > > > > Yes this was one of the distinctions that was used to justify it over > > > > simply contributing to an exisitng project since non of the others do > > > > it. For this reason I am not sure if one of the Application Frameworks > > > > would have worked due to its authentication system. > > > > > > > > Have you looked at http://www.binarycloud.com/ > > > > > > > > >Does it also support ldap (nds)? > > > > > > > > > > > > > > Not at present. My knowledge of ldap consists of the following: > > > > > > > > It exists > > > > It is adirectory server > > > > > > > > I have always thought that it would be good to have it working with > ldap > > > > but unfortunately I have not had the time to look into it. However > with > > > > the present system I believe you can use PEAR:DB to connect to ldap so > > > > may be possible. > > > > > > > > Thanks > > > > > > > > Jake > > > > > > > > >with best regards, > > > > > > > > > >Dick Stins > > > > > > > > > >----- Original Message ----- > > > > >From: "Jake Stride" <ns...@us...> > > > > >To: <web...@li...> > > > > >Sent: Sunday, September 19, 2004 7:41 PM > > > > >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > > > > > > > > > > > > > > > > >>Stins, Dick wrote: > > > > >> > > > > >> > > > > >> > > > > >>>Jake, > > > > >>> > > > > >>>I think that common functions which are needed in weberp and in > your > > > crm > > > > >>>software should be encapsulated in classes, so you do not need to > > know > > > > >>> > > > > >>> > > > > >where > > > > > > > > > > > > > > >>>the information is comming from (postgres or mysql). > > > > >>> > > > > >>> > > > > >>> > > > > >>At the moment it kind of should be in that it uses PEAR:DB for > > > > >> > > > > >> > > > > >abstraction. > > > > > > > > > > > > > > >>>When you want to > > > > >>>integrate web-erp and your crm software, you still need to > integrate > > > the > > > > >>>authentication and the address books processing and .... > > > > >>>The design of these issues should be loosely connected or we should > > > > >>> > > > > >>> > > > > >create > > > > > > > > > > > > > > >>>one big project (wegs-erp?). > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>That could be interesting and worthwhile, is it something people may > > be > > > > >>interested in? > > > > >> > > > > >> > > > > >> > > > > >>>The same for all your code which needs views. Those should be > > > > >>> > > > > >>> > > > > >encapsulated > > > > > > > > > > > > > > >>>in classes, so it's easy to write an alternative for mysql > > > > >>>(allthough when you are able to run mysql with maxdb, then > probably > > > you > > > > >>> > > > > >>> > > > > >can > > > > > > > > > > > > > > >>>use views). > > > > >>> > > > > >>>I even recommend to develop an architecture with: > > > > >>>- front end layer > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>Smarty for templating > > > > >> > > > > >> > > > > >> > > > > >>>- business rule layer > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>System is written as classes > > > > >> > > > > >> > > > > >> > > > > >>>- database trigger layer > > > > >>>- database layer > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>PEAR > > > > >> > > > > >> > > > > >> > > > > >>>This helps to be in control of you own code, reuse of code, > increase > > > > >>>portability for you code (like porting to other databases: sql > > server, > > > > >>>firebird, oracle). > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>EGS should work in oracle without much trouble because of PEAR:DB > > > > >> > > > > >> > > > > >> > > > > >>>An example of an architecture like this is: > > > > >>>http://sourceforge.net/projects/seagull/ > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >>I did have a look at these, the problem is that EGS authentication > is > > > > >>more complicated that this. It is written as an ASP application so > > that > > > > >>several companies can use the same server/DB etc. > > > > >> > > > > >>IE in egs one company can login and create there own users and > groups > > > > >>and insert data etc that another company cannot see. > > > > >> > > > > >>Jake > > > > >> > > > > >> > > > > >> > > > > >>>With best regards, > > > > >>> > > > > >>>Dick Stins > > > > >>> > > > > >>> > > > > >>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >------------------------------------------------------- > > > > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > > > >Project Admins to receive an Apple iPod Mini FREE for your judgement > on > > > > >who ports your project to Linux PPC the best. Sponsored by IBM. > > > > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > > > >_______________________________________________ > > > > >Web-erp-developers mailing list > > > > >Web...@li... > > > > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > > > Project Admins to receive an Apple iPod Mini FREE for your judgement > on > > > > who ports your project to Linux PPC the best. Sponsored by IBM. > > > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > > > _______________________________________________ > > > > Web-erp-developers mailing list > > > > Web...@li... > > > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > > who ports your project to Linux PPC the best. Sponsored by IBM. > > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > > _______________________________________________ > > > Web-erp-developers mailing list > > > Web...@li... > > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > who ports your project to Linux PPC the best. Sponsored by IBM. > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > _______________________________________________ > > Web-erp-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: skaill <sk...@ro...> - 2004-09-20 21:02:52
|
There are a few additional things to watch out for, Jake. We would need to dig up some info that was in one of these emails detailing what to do. It's not tough but you need to be aware of them. Steve ----- Original Message ----- From: "Jake Stride" <ns...@us...> To: <web...@li...> Sent: Monday, September 20, 2004 4:59 PM Subject: Re: [Web-erp-developers] wegs-erp > I can help do some scripts, if it is simply a case of putting _() around > echo statements, then I am sure if you send me a batch of scripts (ie > there names) to do I could find some time this week to convert some. > > Jake > > skaill wrote: > > >We need everyone including myself to dive back into getting the > >Multilanguage done. I could do at least 20 scripts in a day but I might be > >crazy by the end of it! > > > >Steve > > > >----- Original Message ----- > >From: "Daintrees" <p.d...@pa...> > >To: <web...@li...> > >Sent: Monday, September 20, 2004 4:24 PM > >Subject: Re: [Web-erp-developers] wegs-erp > > > > > > > > > >>I dont think it will be that big a problem to get webERP to work with > >>Postgres. > >>I also think choice is a good thing and at this stage webERP is tied to > >>MySQL. > >>If the multi-language is finished, if the serial items is finished then I > >>could get fired up in a different direction. I don't like half done jobs, > >> > >> > >so > > > > > >>I'll go gettextify another script! > >> > >>Phil > >> > >>----- Original Message ----- > >>From: "skaill" <sk...@ro...> > >>To: <web...@li...> > >>Sent: Tuesday, September 21, 2004 2:07 AM > >>Subject: Re: [Web-erp-developers] wegs-erp > >> > >> > >> > >> > >>>Before doing extensive work you may want to check with Phil. With the > >>>Multilanguage going on almost all of the files have some sort of changes > >>>being done to them. > >>> > >>>Sounds like the two biggest challenges are: > >>> > >>>1) Getting to a place of one common DBMS. Personally, I would choose > >>> > >>> > >>mysql > >> > >> > >>>because you get two benefits: You can then offer postgres and mysql > >>>versions of your product and the two products would then be much better > >>> > >>> > >>and > >> > >> > >>>easier to integrate. I guess you could move webERP onto postgres but it > >>>wouldn't be my first choice. > >>> > >>>2) Identifying all of the common database tables and seeing how they > >>> > >>> > >vary > > > > > >>>from one product to another. If there are parts where it varies > >>>substantially then deciding whether to bring it to one common ground or > >>> > >>> > >>have > >> > >> > >>>some duplication and providing interfaces between. Sort of an automated > >>>referential integrity thing but this is probably not that wise. I doubt > >>> > >>> > >>the > >> > >> > >>>common tables will present that great a challenge in combining. > >>> > >>>Also, it would be good to identify which operations they have in common > >>> > >>> > >to > > > > > >>>figure out the best way to resolve it so one does not negatively affect > >>> > >>> > >>the > >> > >> > >>>other. > >>> > >>>Just some thinking out loud... > >>> > >>>One thing is for sure. Combining both products would be a more powerful > >>> > >>> > >>all > >> > >> > >>>round solution ;) Combining teams makes all of us much more powerful as > >>>well. > >>> > >>>Steve > >>> > >>>----- Original Message ----- > >>>From: "Jake Stride" <ns...@us...> > >>>To: <web...@li...> > >>>Sent: Monday, September 20, 2004 8:01 AM > >>>Subject: [Web-erp-developers] wegs-erp > >>> > >>> > >>> > >>> > >>>>As Dick Stins mentioned in one of hs previous email : > >>>> > >>>>"The design of these issues should be loosely connected or we should > >>>>create one big project (wegs-erp?)." > >>>> > >>>>Is this something that people would be interested in? > >>>> > >>>>I for one have little knowledge of ERP, but from a coding and > >>>> > >>>> > >>CRM/project > >> > >> > >>>management side of things, I am fairly well versed and have enough > >>> > >>> > >>knowledge > >> > >> > >>>of ERP to see how the two systems could work together to form a pretty > >>>comprehensive business tool. > >>> > >>> > >>>>I am now in a position to start working on integrating EGS/weberp but > >>>> > >>>> > >>>would like to know peoples views on the situation and the best way to > >>>proceed. For example the address book for EGS is a core component to the > >>>entire system and indeed the CRM functionality runs from it so perhaps > >>> > >>> > >the > > > > > >>>first issue i have is now to over come the integration of the two > >>> > >>> > >address > > > > > >>>books. > >>> > >>> > >>>>Thanks > >>>> > >>>>Jake > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>------------------------------------------------------- > >>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>>Project Admins to receive an Apple iPod Mini FREE for your judgement > >>>> > >>>> > >on > > > > > >>>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>>_______________________________________________ > >>>>Web-erp-developers mailing list > >>>>Web...@li... > >>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>>> > >>>> > >>> > >>>------------------------------------------------------- > >>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>_______________________________________________ > >>>Web-erp-developers mailing list > >>>Web...@li... > >>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>> > >>> > >>> > >> > >>------------------------------------------------------- > >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>who ports your project to Linux PPC the best. Sponsored by IBM. > >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>_______________________________________________ > >>Web-erp-developers mailing list > >>Web...@li... > >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >> > >> > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > >who ports your project to Linux PPC the best. Sponsored by IBM. > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >_______________________________________________ > >Web-erp-developers mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: skaill <sk...@ro...> - 2004-09-20 21:00:25
|
Chris, you around? Possibly you're buried in code. Those graphics were = great. I've used the blue banner on a revamp of the website but it's = nowhere near complete yet. I was hoping I could get the individual pics that went into that banner. = It is through the repetition of people seeing those same images in = various places that will help them realize webERP is, of course, their = choice ;) Steve |
From: Jake S. <ns...@us...> - 2004-09-20 20:59:15
|
I can help do some scripts, if it is simply a case of putting _() around echo statements, then I am sure if you send me a batch of scripts (ie there names) to do I could find some time this week to convert some. Jake skaill wrote: >We need everyone including myself to dive back into getting the >Multilanguage done. I could do at least 20 scripts in a day but I might be >crazy by the end of it! > >Steve > >----- Original Message ----- >From: "Daintrees" <p.d...@pa...> >To: <web...@li...> >Sent: Monday, September 20, 2004 4:24 PM >Subject: Re: [Web-erp-developers] wegs-erp > > > > >>I dont think it will be that big a problem to get webERP to work with >>Postgres. >>I also think choice is a good thing and at this stage webERP is tied to >>MySQL. >>If the multi-language is finished, if the serial items is finished then I >>could get fired up in a different direction. I don't like half done jobs, >> >> >so > > >>I'll go gettextify another script! >> >>Phil >> >>----- Original Message ----- >>From: "skaill" <sk...@ro...> >>To: <web...@li...> >>Sent: Tuesday, September 21, 2004 2:07 AM >>Subject: Re: [Web-erp-developers] wegs-erp >> >> >> >> >>>Before doing extensive work you may want to check with Phil. With the >>>Multilanguage going on almost all of the files have some sort of changes >>>being done to them. >>> >>>Sounds like the two biggest challenges are: >>> >>>1) Getting to a place of one common DBMS. Personally, I would choose >>> >>> >>mysql >> >> >>>because you get two benefits: You can then offer postgres and mysql >>>versions of your product and the two products would then be much better >>> >>> >>and >> >> >>>easier to integrate. I guess you could move webERP onto postgres but it >>>wouldn't be my first choice. >>> >>>2) Identifying all of the common database tables and seeing how they >>> >>> >vary > > >>>from one product to another. If there are parts where it varies >>>substantially then deciding whether to bring it to one common ground or >>> >>> >>have >> >> >>>some duplication and providing interfaces between. Sort of an automated >>>referential integrity thing but this is probably not that wise. I doubt >>> >>> >>the >> >> >>>common tables will present that great a challenge in combining. >>> >>>Also, it would be good to identify which operations they have in common >>> >>> >to > > >>>figure out the best way to resolve it so one does not negatively affect >>> >>> >>the >> >> >>>other. >>> >>>Just some thinking out loud... >>> >>>One thing is for sure. Combining both products would be a more powerful >>> >>> >>all >> >> >>>round solution ;) Combining teams makes all of us much more powerful as >>>well. >>> >>>Steve >>> >>>----- Original Message ----- >>>From: "Jake Stride" <ns...@us...> >>>To: <web...@li...> >>>Sent: Monday, September 20, 2004 8:01 AM >>>Subject: [Web-erp-developers] wegs-erp >>> >>> >>> >>> >>>>As Dick Stins mentioned in one of hs previous email : >>>> >>>>"The design of these issues should be loosely connected or we should >>>>create one big project (wegs-erp?)." >>>> >>>>Is this something that people would be interested in? >>>> >>>>I for one have little knowledge of ERP, but from a coding and >>>> >>>> >>CRM/project >> >> >>>management side of things, I am fairly well versed and have enough >>> >>> >>knowledge >> >> >>>of ERP to see how the two systems could work together to form a pretty >>>comprehensive business tool. >>> >>> >>>>I am now in a position to start working on integrating EGS/weberp but >>>> >>>> >>>would like to know peoples views on the situation and the best way to >>>proceed. For example the address book for EGS is a core component to the >>>entire system and indeed the CRM functionality runs from it so perhaps >>> >>> >the > > >>>first issue i have is now to over come the integration of the two >>> >>> >address > > >>>books. >>> >>> >>>>Thanks >>>> >>>>Jake >>>> >>>> >>>> >>>> >>>> >>>>------------------------------------------------------- >>>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>>Project Admins to receive an Apple iPod Mini FREE for your judgement >>>> >>>> >on > > >>>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>>_______________________________________________ >>>>Web-erp-developers mailing list >>>>Web...@li... >>>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>>> >>>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>_______________________________________________ >>>Web-erp-developers mailing list >>>Web...@li... >>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>> >>> >>> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>who ports your project to Linux PPC the best. Sponsored by IBM. >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>_______________________________________________ >>Web-erp-developers mailing list >>Web...@li... >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > |
From: skaill <sk...@ro...> - 2004-09-20 20:53:20
|
In theory 3-tier is a great idea, however it has some drawbacks too. I don't know of a system anywhere as near as complete as webERP that has true 3-tier separation. An accounting system in particular is critical to a business. It must be very, very reliable. For this reason, typically you will see less than state of the art at banks and government for instance. Someone's neck would be on the line if things got out of control and they can very easily. There are some other important reasons for carefully considering the approach. Many who will put their attention toward webERP will be accountants who may not be computer experts like us. Going too extreme can alienate them from contributing even though they are the ones who more likely understand the full extent of deeper accounting problems. What I'm saying here is I think it's a fine line and a line that, in the interest of keeping the product stable, bringing more people on board and keeping people onboard, needs to be moved slowly. Side note: While I do believe in isolating the business rules, I do not believe planting business rules in the triggers of a database or in stored procedures is beneficial, I would keep them in code. Triggers and stored procedures lead to bits and pieces everywhere. Steve ----- Original Message ----- From: "Stins, Dick" <DR...@Zi...> To: <web...@li...> Sent: Monday, September 20, 2004 4:29 PM Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > Yes, any technical database layer is not that interesting, although it's > always handy when it is not too much work to move to another database > engine, but I see no need to change from mysql to another database engine at > the moment. Solution like pear:db seems only to slow things down and hide > the real code and creates more trouble when in pear:DB (or any other > wrapper) are some bugs. > > When I talk about a database layer, it's functional. Like you have a > function to delete a customer. > This functions checks all business constraints before deleting: > - are there any transaction related? > - are there any open orders? > - are there any companies related to this customer? > - is it an active customer? > - is it bankrupt? > - ... > > When one or more checks fail, then the function returns an understandable > error and refuses to continue. > > When you have this function, then you are able to call it from any script, > like a delete script, or a batch script which deletes lot's of customers, or > a webservices which tries to process delete the customer. > > The same for a create customer function. When all attributes (credit check, > address, chamber of commerce number, tax number, telephone number, > bankaccount number, ...) of the customer are properly set, then the status > of this customer will be valid. > > When you have one set of functions/methods to set all these items, then you > again can reuse this code (CLASS METHODS) of lot's of places. > > When you have a problem with creation of customers, then you know you where > to find the one and only place where it was coded: in the data layer > (customer class). > > Where all rules are coded is not that important. You can use php classes, > php functions, sql, database triggers, stored procedures or foreign keys, > column constraints, table constraints, ... > Just collect everything for manipulating customers and put them in the same > place where you can call it from everywhere, so you need not to code it > twice and test it twice and debug it twice or more. > > Use this principle for every object (table or combination of tables or ..). > Every developer would know where to look when there is a problem with the > process creating or deleting or updating a customer. > > When someone still would like to port the software package to another > database system, then he has only to port the database layer and is not > disturbed by the presentation layer and ... > > Resume: the above principle/architecture is based at two ideas: > 1. you always knows where to find object (table) related functions, so you > are not attracted to code same functions again and again but just calls them > again > 2. you only code once the business rules and are able to reuse them several > times by calling them from several php scripts, batch scripts, webservices, > .... > > With best regards, > > Dick Stins > > ----- Original Message ----- > From: "Daintrees" <p.d...@pa...> > To: <web...@li...> > Sent: Monday, September 20, 2004 9:24 AM > Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > You'll have to excuse my naievety (and poor spelling) since most of the > > native functions are similar in function but different in name for > differing > > DBs why does one need such a lavish abstraction layer why won't a > > ConnectDB.inc calling the native C calls to connect directly for other DBs > > do the trick? This way we have ultimate performance minimum overhead! > > > > I really don't understand why such lengths are necessary - the function > > calls are virtually one to one and even most of the parameters are the > same. > > > > MS SQL Server > > > > mssql_connect > > mssql_fetch_array > > mssql_fetch_row > > mssql_data_seek > > > > > > MySql > > > > mysql_connect > > mysql_query > > mysql_fetch_array > > mysql_fetch_row > > mysql_data_seek > > > > Postgres > > > > pg_connect > > pg_query > > pg_fetch_array > > pg_fetch_row > > pg_data_seek > > > > > > Firebird/interbase > > > > ibase_connect > > ibase_query > > ibase_fetch_assoc > > ibase_fetch_row > > > > whoops there is no > > ibase_data_seek > > > > maybe I'm answering my own question! > > > > > > Phil > > > > > > ----- Original Message ----- > > From: "Jake Stride" <ns...@us...> > > To: <web...@li...> > > Sent: Monday, September 20, 2004 5:58 PM > > Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > Stins, Dick wrote: > > > > > > >Jake, > > > > > > > >Thanks for your comments. > > > > > > > >I am not a fan of pear:db. I prefer to use standard sql. That is > already > > a > > > >big step for portability + the clean and mean weberp script > > ConnectDB.inc. > > > >So it should not be too hard to port web-erp to another db engine. > > > > > > > > > > > No to be honest neither am I, for reasons I won't bore you with it was > > > chosen at the start of the project and has persited through. Have you > > > had a look at > > > > > > http://creole.phpdb.org/ > > > http://propel.phpdb.org/wiki/ > > > > > > >Smarty might be interesting, but I am already glad when css is optimal > > used. > > > > > > > > > > > This is the case with EGS, it just allows all of the presentation logic > > > to be removed from the code base and allows people to be a lot more > > > flexible with the layout without having to trawl through the PHP code. > > > > > > >Multiple company support is interesting. > > > > > > > > > > > Yes this was one of the distinctions that was used to justify it over > > > simply contributing to an exisitng project since non of the others do > > > it. For this reason I am not sure if one of the Application Frameworks > > > would have worked due to its authentication system. > > > > > > Have you looked at http://www.binarycloud.com/ > > > > > > >Does it also support ldap (nds)? > > > > > > > > > > > Not at present. My knowledge of ldap consists of the following: > > > > > > It exists > > > It is adirectory server > > > > > > I have always thought that it would be good to have it working with ldap > > > but unfortunately I have not had the time to look into it. However with > > > the present system I believe you can use PEAR:DB to connect to ldap so > > > may be possible. > > > > > > Thanks > > > > > > Jake > > > > > > >with best regards, > > > > > > > >Dick Stins > > > > > > > >----- Original Message ----- > > > >From: "Jake Stride" <ns...@us...> > > > >To: <web...@li...> > > > >Sent: Sunday, September 19, 2004 7:41 PM > > > >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > > > > > > > > > > > >>Stins, Dick wrote: > > > >> > > > >> > > > >> > > > >>>Jake, > > > >>> > > > >>>I think that common functions which are needed in weberp and in your > > crm > > > >>>software should be encapsulated in classes, so you do not need to > know > > > >>> > > > >>> > > > >where > > > > > > > > > > > >>>the information is comming from (postgres or mysql). > > > >>> > > > >>> > > > >>> > > > >>At the moment it kind of should be in that it uses PEAR:DB for > > > >> > > > >> > > > >abstraction. > > > > > > > > > > > >>>When you want to > > > >>>integrate web-erp and your crm software, you still need to integrate > > the > > > >>>authentication and the address books processing and .... > > > >>>The design of these issues should be loosely connected or we should > > > >>> > > > >>> > > > >create > > > > > > > > > > > >>>one big project (wegs-erp?). > > > >>> > > > >>> > > > >>> > > > >>> > > > >>That could be interesting and worthwhile, is it something people may > be > > > >>interested in? > > > >> > > > >> > > > >> > > > >>>The same for all your code which needs views. Those should be > > > >>> > > > >>> > > > >encapsulated > > > > > > > > > > > >>>in classes, so it's easy to write an alternative for mysql > > > >>>(allthough when you are able to run mysql with maxdb, then probably > > you > > > >>> > > > >>> > > > >can > > > > > > > > > > > >>>use views). > > > >>> > > > >>>I even recommend to develop an architecture with: > > > >>>- front end layer > > > >>> > > > >>> > > > >>> > > > >>> > > > >>Smarty for templating > > > >> > > > >> > > > >> > > > >>>- business rule layer > > > >>> > > > >>> > > > >>> > > > >>> > > > >>System is written as classes > > > >> > > > >> > > > >> > > > >>>- database trigger layer > > > >>>- database layer > > > >>> > > > >>> > > > >>> > > > >>> > > > >>PEAR > > > >> > > > >> > > > >> > > > >>>This helps to be in control of you own code, reuse of code, increase > > > >>>portability for you code (like porting to other databases: sql > server, > > > >>>firebird, oracle). > > > >>> > > > >>> > > > >>> > > > >>> > > > >>EGS should work in oracle without much trouble because of PEAR:DB > > > >> > > > >> > > > >> > > > >>>An example of an architecture like this is: > > > >>>http://sourceforge.net/projects/seagull/ > > > >>> > > > >>> > > > >>> > > > >>> > > > >>I did have a look at these, the problem is that EGS authentication is > > > >>more complicated that this. It is written as an ASP application so > that > > > >>several companies can use the same server/DB etc. > > > >> > > > >>IE in egs one company can login and create there own users and groups > > > >>and insert data etc that another company cannot see. > > > >> > > > >>Jake > > > >> > > > >> > > > >> > > > >>>With best regards, > > > >>> > > > >>>Dick Stins > > > >>> > > > >>> > > > >>> > > > > > > > > > > > > > > > > > > > > > > > >------------------------------------------------------- > > > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > > > >who ports your project to Linux PPC the best. Sponsored by IBM. > > > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > > >_______________________________________________ > > > >Web-erp-developers mailing list > > > >Web...@li... > > > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > > who ports your project to Linux PPC the best. Sponsored by IBM. > > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > > _______________________________________________ > > > Web-erp-developers mailing list > > > Web...@li... > > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > who ports your project to Linux PPC the best. Sponsored by IBM. > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > _______________________________________________ > > Web-erp-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: skaill <sk...@ro...> - 2004-09-20 20:29:29
|
We need everyone including myself to dive back into getting the Multilanguage done. I could do at least 20 scripts in a day but I might be crazy by the end of it! Steve ----- Original Message ----- From: "Daintrees" <p.d...@pa...> To: <web...@li...> Sent: Monday, September 20, 2004 4:24 PM Subject: Re: [Web-erp-developers] wegs-erp > I dont think it will be that big a problem to get webERP to work with > Postgres. > I also think choice is a good thing and at this stage webERP is tied to > MySQL. > If the multi-language is finished, if the serial items is finished then I > could get fired up in a different direction. I don't like half done jobs, so > I'll go gettextify another script! > > Phil > > ----- Original Message ----- > From: "skaill" <sk...@ro...> > To: <web...@li...> > Sent: Tuesday, September 21, 2004 2:07 AM > Subject: Re: [Web-erp-developers] wegs-erp > > > > Before doing extensive work you may want to check with Phil. With the > > Multilanguage going on almost all of the files have some sort of changes > > being done to them. > > > > Sounds like the two biggest challenges are: > > > > 1) Getting to a place of one common DBMS. Personally, I would choose > mysql > > because you get two benefits: You can then offer postgres and mysql > > versions of your product and the two products would then be much better > and > > easier to integrate. I guess you could move webERP onto postgres but it > > wouldn't be my first choice. > > > > 2) Identifying all of the common database tables and seeing how they vary > > from one product to another. If there are parts where it varies > > substantially then deciding whether to bring it to one common ground or > have > > some duplication and providing interfaces between. Sort of an automated > > referential integrity thing but this is probably not that wise. I doubt > the > > common tables will present that great a challenge in combining. > > > > Also, it would be good to identify which operations they have in common to > > figure out the best way to resolve it so one does not negatively affect > the > > other. > > > > Just some thinking out loud... > > > > One thing is for sure. Combining both products would be a more powerful > all > > round solution ;) Combining teams makes all of us much more powerful as > > well. > > > > Steve > > > > ----- Original Message ----- > > From: "Jake Stride" <ns...@us...> > > To: <web...@li...> > > Sent: Monday, September 20, 2004 8:01 AM > > Subject: [Web-erp-developers] wegs-erp > > > > > > > As Dick Stins mentioned in one of hs previous email : > > > > > > "The design of these issues should be loosely connected or we should > > > create one big project (wegs-erp?)." > > > > > > Is this something that people would be interested in? > > > > > > I for one have little knowledge of ERP, but from a coding and > CRM/project > > management side of things, I am fairly well versed and have enough > knowledge > > of ERP to see how the two systems could work together to form a pretty > > comprehensive business tool. > > > > > > I am now in a position to start working on integrating EGS/weberp but > > would like to know peoples views on the situation and the best way to > > proceed. For example the address book for EGS is a core component to the > > entire system and indeed the CRM functionality runs from it so perhaps the > > first issue i have is now to over come the integration of the two address > > books. > > > > > > Thanks > > > > > > Jake > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > > who ports your project to Linux PPC the best. Sponsored by IBM. > > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > > _______________________________________________ > > > Web-erp-developers mailing list > > > Web...@li... > > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > who ports your project to Linux PPC the best. Sponsored by IBM. > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > _______________________________________________ > > Web-erp-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: Stins, D. <DR...@Zi...> - 2004-09-20 20:27:09
|
I suggest first to finish the current gettext coding and release it. After that, it we might evaluate and consider smarty. With best regards, Dick Stins ----- Original Message ----- From: "Hani Naguib" <ha...@na...> To: <web...@li...> Sent: Monday, September 20, 2004 1:55 AM Subject: Re: [Web-erp-developers] smarty multiple language > If you guys do decide to use Smarty you will get a nice feature relating > to translations. > With a little configuration you can get smarty to do translation when it > compiles the templates, > this means that for static text your code just translates it once (the > first time the template is compiled). > After a page has been accessed one time all the 'static' text will not > need to be translated. > > Having said this, using smarty properly you require quite a bit of > refactoring of weberps code. > > Hani > > Stins, Dick wrote: > > >*This message was transferred with a trial version of CommuniGate(tm) Pro* > >Language team, > > > >Please check smarty for transforming decimal point locator (. or ,) and > >thousands separator (, or .) and may be for more issues like dates formats. > >http://www.oxyscripts.com/manuals/smarty/language.modifier.string.format.ht m > >l > > > >When this helps, then we can setup a smarty template per language? > > > >With best regards, > > > >Dick Stins > >----- Original Message ----- > >From: "Stins, Dick" <DR...@Zi...> > >To: <web...@li...> > >Sent: Monday, September 20, 2004 1:03 AM > >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > >>Jake, > >> > >>Thanks for your comments. > >> > >>I am not a fan of pear:db. I prefer to use standard sql. That is already a > >>big step for portability + the clean and mean weberp script ConnectDB.inc. > >>So it should not be too hard to port web-erp to another db engine. > >> > >>Smarty might be interesting, but I am already glad when css is optimal > >> > >> > >used. > > > > > >>Multiple company support is interesting. > >> > >>Does it also support ldap (nds)? > >> > >>with best regards, > >> > >>Dick Stins > >> > >>----- Original Message ----- > >>From: "Jake Stride" <ns...@us...> > >>To: <web...@li...> > >>Sent: Sunday, September 19, 2004 7:41 PM > >>Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > >> > >> > >> > >> > >>>Stins, Dick wrote: > >>> > >>> > >>> > >>>>Jake, > >>>> > >>>>I think that common functions which are needed in weberp and in your > >>>> > >>>> > >crm > > > > > >>>>software should be encapsulated in classes, so you do not need to know > >>>> > >>>> > >>where > >> > >> > >>>>the information is comming from (postgres or mysql). > >>>> > >>>> > >>>> > >>>At the moment it kind of should be in that it uses PEAR:DB for > >>> > >>> > >>abstraction. > >> > >> > >>>>When you want to > >>>>integrate web-erp and your crm software, you still need to integrate > >>>> > >>>> > >the > > > > > >>>>authentication and the address books processing and .... > >>>>The design of these issues should be loosely connected or we should > >>>> > >>>> > >>create > >> > >> > >>>>one big project (wegs-erp?). > >>>> > >>>> > >>>> > >>>> > >>>That could be interesting and worthwhile, is it something people may be > >>>interested in? > >>> > >>> > >>> > >>>>The same for all your code which needs views. Those should be > >>>> > >>>> > >>encapsulated > >> > >> > >>>>in classes, so it's easy to write an alternative for mysql > >>>>(allthough when you are able to run mysql with maxdb, then probably > >>>> > >>>> > >you > > > > > >>can > >> > >> > >>>>use views). > >>>> > >>>>I even recommend to develop an architecture with: > >>>>- front end layer > >>>> > >>>> > >>>> > >>>> > >>>Smarty for templating > >>> > >>> > >>> > >>>>- business rule layer > >>>> > >>>> > >>>> > >>>> > >>>System is written as classes > >>> > >>> > >>> > >>>>- database trigger layer > >>>>- database layer > >>>> > >>>> > >>>> > >>>> > >>>PEAR > >>> > >>> > >>> > >>>>This helps to be in control of you own code, reuse of code, increase > >>>>portability for you code (like porting to other databases: sql server, > >>>>firebird, oracle). > >>>> > >>>> > >>>> > >>>> > >>>EGS should work in oracle without much trouble because of PEAR:DB > >>> > >>> > >>> > >>>>An example of an architecture like this is: > >>>>http://sourceforge.net/projects/seagull/ > >>>> > >>>> > >>>> > >>>> > >>>I did have a look at these, the problem is that EGS authentication is > >>>more complicated that this. It is written as an ASP application so that > >>>several companies can use the same server/DB etc. > >>> > >>>IE in egs one company can login and create there own users and groups > >>>and insert data etc that another company cannot see. > >>> > >>>Jake > >>> > >>> > >>> > >>>>With best regards, > >>>> > >>>>Dick Stins > >>>> > >>>> > >>>> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>who ports your project to Linux PPC the best. Sponsored by IBM. > >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>_______________________________________________ > >>Web-erp-developers mailing list > >>Web...@li... > >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >> > >> > > > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > >who ports your project to Linux PPC the best. Sponsored by IBM. > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >_______________________________________________ > >Web-erp-developers mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: Stins, D. <DR...@Zi...> - 2004-09-20 20:25:19
|
Yes, any technical database layer is not that interesting, although it's always handy when it is not too much work to move to another database engine, but I see no need to change from mysql to another database engine at the moment. Solution like pear:db seems only to slow things down and hide the real code and creates more trouble when in pear:DB (or any other wrapper) are some bugs. When I talk about a database layer, it's functional. Like you have a function to delete a customer. This functions checks all business constraints before deleting: - are there any transaction related? - are there any open orders? - are there any companies related to this customer? - is it an active customer? - is it bankrupt? - ... When one or more checks fail, then the function returns an understandable error and refuses to continue. When you have this function, then you are able to call it from any script, like a delete script, or a batch script which deletes lot's of customers, or a webservices which tries to process delete the customer. The same for a create customer function. When all attributes (credit check, address, chamber of commerce number, tax number, telephone number, bankaccount number, ...) of the customer are properly set, then the status of this customer will be valid. When you have one set of functions/methods to set all these items, then you again can reuse this code (CLASS METHODS) of lot's of places. When you have a problem with creation of customers, then you know you where to find the one and only place where it was coded: in the data layer (customer class). Where all rules are coded is not that important. You can use php classes, php functions, sql, database triggers, stored procedures or foreign keys, column constraints, table constraints, ... Just collect everything for manipulating customers and put them in the same place where you can call it from everywhere, so you need not to code it twice and test it twice and debug it twice or more. Use this principle for every object (table or combination of tables or ..). Every developer would know where to look when there is a problem with the process creating or deleting or updating a customer. When someone still would like to port the software package to another database system, then he has only to port the database layer and is not disturbed by the presentation layer and ... Resume: the above principle/architecture is based at two ideas: 1. you always knows where to find object (table) related functions, so you are not attracted to code same functions again and again but just calls them again 2. you only code once the business rules and are able to reuse them several times by calling them from several php scripts, batch scripts, webservices, .... With best regards, Dick Stins ----- Original Message ----- From: "Daintrees" <p.d...@pa...> To: <web...@li...> Sent: Monday, September 20, 2004 9:24 AM Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > You'll have to excuse my naievety (and poor spelling) since most of the > native functions are similar in function but different in name for differing > DBs why does one need such a lavish abstraction layer why won't a > ConnectDB.inc calling the native C calls to connect directly for other DBs > do the trick? This way we have ultimate performance minimum overhead! > > I really don't understand why such lengths are necessary - the function > calls are virtually one to one and even most of the parameters are the same. > > MS SQL Server > > mssql_connect > mssql_fetch_array > mssql_fetch_row > mssql_data_seek > > > MySql > > mysql_connect > mysql_query > mysql_fetch_array > mysql_fetch_row > mysql_data_seek > > Postgres > > pg_connect > pg_query > pg_fetch_array > pg_fetch_row > pg_data_seek > > > Firebird/interbase > > ibase_connect > ibase_query > ibase_fetch_assoc > ibase_fetch_row > > whoops there is no > ibase_data_seek > > maybe I'm answering my own question! > > > Phil > > > ----- Original Message ----- > From: "Jake Stride" <ns...@us...> > To: <web...@li...> > Sent: Monday, September 20, 2004 5:58 PM > Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > Stins, Dick wrote: > > > > >Jake, > > > > > >Thanks for your comments. > > > > > >I am not a fan of pear:db. I prefer to use standard sql. That is already > a > > >big step for portability + the clean and mean weberp script > ConnectDB.inc. > > >So it should not be too hard to port web-erp to another db engine. > > > > > > > > No to be honest neither am I, for reasons I won't bore you with it was > > chosen at the start of the project and has persited through. Have you > > had a look at > > > > http://creole.phpdb.org/ > > http://propel.phpdb.org/wiki/ > > > > >Smarty might be interesting, but I am already glad when css is optimal > used. > > > > > > > > This is the case with EGS, it just allows all of the presentation logic > > to be removed from the code base and allows people to be a lot more > > flexible with the layout without having to trawl through the PHP code. > > > > >Multiple company support is interesting. > > > > > > > > Yes this was one of the distinctions that was used to justify it over > > simply contributing to an exisitng project since non of the others do > > it. For this reason I am not sure if one of the Application Frameworks > > would have worked due to its authentication system. > > > > Have you looked at http://www.binarycloud.com/ > > > > >Does it also support ldap (nds)? > > > > > > > > Not at present. My knowledge of ldap consists of the following: > > > > It exists > > It is adirectory server > > > > I have always thought that it would be good to have it working with ldap > > but unfortunately I have not had the time to look into it. However with > > the present system I believe you can use PEAR:DB to connect to ldap so > > may be possible. > > > > Thanks > > > > Jake > > > > >with best regards, > > > > > >Dick Stins > > > > > >----- Original Message ----- > > >From: "Jake Stride" <ns...@us...> > > >To: <web...@li...> > > >Sent: Sunday, September 19, 2004 7:41 PM > > >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > > > > > > >>Stins, Dick wrote: > > >> > > >> > > >> > > >>>Jake, > > >>> > > >>>I think that common functions which are needed in weberp and in your > crm > > >>>software should be encapsulated in classes, so you do not need to know > > >>> > > >>> > > >where > > > > > > > > >>>the information is comming from (postgres or mysql). > > >>> > > >>> > > >>> > > >>At the moment it kind of should be in that it uses PEAR:DB for > > >> > > >> > > >abstraction. > > > > > > > > >>>When you want to > > >>>integrate web-erp and your crm software, you still need to integrate > the > > >>>authentication and the address books processing and .... > > >>>The design of these issues should be loosely connected or we should > > >>> > > >>> > > >create > > > > > > > > >>>one big project (wegs-erp?). > > >>> > > >>> > > >>> > > >>> > > >>That could be interesting and worthwhile, is it something people may be > > >>interested in? > > >> > > >> > > >> > > >>>The same for all your code which needs views. Those should be > > >>> > > >>> > > >encapsulated > > > > > > > > >>>in classes, so it's easy to write an alternative for mysql > > >>>(allthough when you are able to run mysql with maxdb, then probably > you > > >>> > > >>> > > >can > > > > > > > > >>>use views). > > >>> > > >>>I even recommend to develop an architecture with: > > >>>- front end layer > > >>> > > >>> > > >>> > > >>> > > >>Smarty for templating > > >> > > >> > > >> > > >>>- business rule layer > > >>> > > >>> > > >>> > > >>> > > >>System is written as classes > > >> > > >> > > >> > > >>>- database trigger layer > > >>>- database layer > > >>> > > >>> > > >>> > > >>> > > >>PEAR > > >> > > >> > > >> > > >>>This helps to be in control of you own code, reuse of code, increase > > >>>portability for you code (like porting to other databases: sql server, > > >>>firebird, oracle). > > >>> > > >>> > > >>> > > >>> > > >>EGS should work in oracle without much trouble because of PEAR:DB > > >> > > >> > > >> > > >>>An example of an architecture like this is: > > >>>http://sourceforge.net/projects/seagull/ > > >>> > > >>> > > >>> > > >>> > > >>I did have a look at these, the problem is that EGS authentication is > > >>more complicated that this. It is written as an ASP application so that > > >>several companies can use the same server/DB etc. > > >> > > >>IE in egs one company can login and create there own users and groups > > >>and insert data etc that another company cannot see. > > >> > > >>Jake > > >> > > >> > > >> > > >>>With best regards, > > >>> > > >>>Dick Stins > > >>> > > >>> > > >>> > > > > > > > > > > > > > > > > > >------------------------------------------------------- > > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > > >who ports your project to Linux PPC the best. Sponsored by IBM. > > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > >_______________________________________________ > > >Web-erp-developers mailing list > > >Web...@li... > > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > who ports your project to Linux PPC the best. Sponsored by IBM. > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > _______________________________________________ > > Web-erp-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: Daintrees <p.d...@pa...> - 2004-09-20 20:22:15
|
I dont think it will be that big a problem to get webERP to work with Postgres. I also think choice is a good thing and at this stage webERP is tied to MySQL. If the multi-language is finished, if the serial items is finished then I could get fired up in a different direction. I don't like half done jobs, so I'll go gettextify another script! Phil ----- Original Message ----- From: "skaill" <sk...@ro...> To: <web...@li...> Sent: Tuesday, September 21, 2004 2:07 AM Subject: Re: [Web-erp-developers] wegs-erp > Before doing extensive work you may want to check with Phil. With the > Multilanguage going on almost all of the files have some sort of changes > being done to them. > > Sounds like the two biggest challenges are: > > 1) Getting to a place of one common DBMS. Personally, I would choose mysql > because you get two benefits: You can then offer postgres and mysql > versions of your product and the two products would then be much better and > easier to integrate. I guess you could move webERP onto postgres but it > wouldn't be my first choice. > > 2) Identifying all of the common database tables and seeing how they vary > from one product to another. If there are parts where it varies > substantially then deciding whether to bring it to one common ground or have > some duplication and providing interfaces between. Sort of an automated > referential integrity thing but this is probably not that wise. I doubt the > common tables will present that great a challenge in combining. > > Also, it would be good to identify which operations they have in common to > figure out the best way to resolve it so one does not negatively affect the > other. > > Just some thinking out loud... > > One thing is for sure. Combining both products would be a more powerful all > round solution ;) Combining teams makes all of us much more powerful as > well. > > Steve > > ----- Original Message ----- > From: "Jake Stride" <ns...@us...> > To: <web...@li...> > Sent: Monday, September 20, 2004 8:01 AM > Subject: [Web-erp-developers] wegs-erp > > > > As Dick Stins mentioned in one of hs previous email : > > > > "The design of these issues should be loosely connected or we should > > create one big project (wegs-erp?)." > > > > Is this something that people would be interested in? > > > > I for one have little knowledge of ERP, but from a coding and CRM/project > management side of things, I am fairly well versed and have enough knowledge > of ERP to see how the two systems could work together to form a pretty > comprehensive business tool. > > > > I am now in a position to start working on integrating EGS/weberp but > would like to know peoples views on the situation and the best way to > proceed. For example the address book for EGS is a core component to the > entire system and indeed the CRM functionality runs from it so perhaps the > first issue i have is now to over come the integration of the two address > books. > > > > Thanks > > > > Jake > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > > Project Admins to receive an Apple iPod Mini FREE for your judgement on > > who ports your project to Linux PPC the best. Sponsored by IBM. > > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > > _______________________________________________ > > Web-erp-developers mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > |
From: Daintrees <p.d...@pa...> - 2004-09-20 20:18:14
|
Jake, The permissions in webERP are such that each page has a PageSecurity value and the user has a role variable which is an array of all the PageSecurity values that she has access to. If the PageSecurity value of the page is not in the role array then the user is blocked from going into the page. I think this kind of permission structure is a requirement of ERP software to properly divide duties for internal control purposes. There is no common address book in webERP - there are customers and their postal addresses in DebtorsMaster, there are customer branch delivery addresses in CustBranch, there are supplier addresses in Suppliers. There are Supplier contacts and email addresses. There are user email addresses in WWW_Users. There are warehouse addresses in Locations. So the addresses in webERP are quite miserably sprinkled around the place. A central repository offered by EGS would be good as a business tool. One possible approach for integration might be to build some extra SQL into the various scripts, Suppliers.php, SupplierContacts.php, Customers.php, Locations.php to fire the addresses into EGS address book. Just a few thoughts, Phil > > I for one have little knowledge of ERP, but from a coding and CRM/project management side of things, I am fairly well versed and have enough knowledge of ERP to see how the two systems could work together to form a pretty comprehensive business tool. > > I am now in a position to start working on integrating EGS/weberp but would like to know peoples views on the situation and the best way to proceed. For example the address book for EGS is a core component to the entire system and indeed the CRM functionality runs from it so perhaps the first issue i have is now to over come the integration of the two address books. > > Thanks > > Jake > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > |
From: Jake S. <ns...@us...> - 2004-09-20 14:27:01
|
skaill wrote: >Before doing extensive work you may want to check with Phil. With the >Multilanguage going on almost all of the files have some sort of changes >being done to them. > > Of course >Sounds like the two biggest challenges are: > >1) Getting to a place of one common DBMS. Personally, I would choose mysql >because you get two benefits: You can then offer postgres and mysql >versions of your product and the two products would then be much better and >easier to integrate. I guess you could move webERP onto postgres but it >wouldn't be my first choice. > > OK, my preference is postgresql, but I agree with what you say above, and if we all work on it then getting it to work on both DBMS (mysql/postgresql) would not be much extra work but ensures both get a reasonable amount of testing >2) Identifying all of the common database tables and seeing how they vary >from one product to another. If there are parts where it varies >substantially then deciding whether to bring it to one common ground or have >some duplication and providing interfaces between. Sort of an automated >referential integrity thing but this is probably not that wise. I doubt the >common tables will present that great a challenge in combining. > > This could be interesting and I wonder the best way to go about it. I'm not sure email would be the optimal method, perhaps IRC, but then there is the issue of time differences. I think it is mainly the contacts/address book and authentication tables that will have things in common. The main issue that I can see is that the authentication in EGS is quite powerful. With a contact for example you can assign the follow access: Restricted Read - can see contact details, people etc but no account data Read only - as above but can see account data Write Acceess- User can view all details and edit them This access applies to both users and groups. In addition, for example if a user is allocated to a group with write access, and also on an individual basis as a user with restricted read, the database view joins across the tables and ensures that the highest access prevails, in this case the user is given write access since it is higher than restricted read. I may be wrong but I don't believe this is the case with weberp so may need some additional coding in weberp. >Also, it would be good to identify which operations they have in common to >figure out the best way to resolve it so one does not negatively affect the >other. > >Just some thinking out loud... > >One thing is for sure. Combining both products would be a more powerful all >round solution ;) Combining teams makes all of us much more powerful as >well. > > My thoughts exactly Jake >Steve > >----- Original Message ----- >From: "Jake Stride" <ns...@us...> >To: <web...@li...> >Sent: Monday, September 20, 2004 8:01 AM >Subject: [Web-erp-developers] wegs-erp > > > > >>As Dick Stins mentioned in one of hs previous email : >> >>"The design of these issues should be loosely connected or we should >>create one big project (wegs-erp?)." >> >>Is this something that people would be interested in? >> >>I for one have little knowledge of ERP, but from a coding and CRM/project >> >> >management side of things, I am fairly well versed and have enough knowledge >of ERP to see how the two systems could work together to form a pretty >comprehensive business tool. > > >>I am now in a position to start working on integrating EGS/weberp but >> >> >would like to know peoples views on the situation and the best way to >proceed. For example the address book for EGS is a core component to the >entire system and indeed the CRM functionality runs from it so perhaps the >first issue i have is now to over come the integration of the two address >books. > > >>Thanks >> >>Jake >> >> >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>who ports your project to Linux PPC the best. Sponsored by IBM. >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>_______________________________________________ >>Web-erp-developers mailing list >>Web...@li... >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > |
From: skaill <sk...@ro...> - 2004-09-20 14:06:17
|
Before doing extensive work you may want to check with Phil. With the Multilanguage going on almost all of the files have some sort of changes being done to them. Sounds like the two biggest challenges are: 1) Getting to a place of one common DBMS. Personally, I would choose mysql because you get two benefits: You can then offer postgres and mysql versions of your product and the two products would then be much better and easier to integrate. I guess you could move webERP onto postgres but it wouldn't be my first choice. 2) Identifying all of the common database tables and seeing how they vary from one product to another. If there are parts where it varies substantially then deciding whether to bring it to one common ground or have some duplication and providing interfaces between. Sort of an automated referential integrity thing but this is probably not that wise. I doubt the common tables will present that great a challenge in combining. Also, it would be good to identify which operations they have in common to figure out the best way to resolve it so one does not negatively affect the other. Just some thinking out loud... One thing is for sure. Combining both products would be a more powerful all round solution ;) Combining teams makes all of us much more powerful as well. Steve ----- Original Message ----- From: "Jake Stride" <ns...@us...> To: <web...@li...> Sent: Monday, September 20, 2004 8:01 AM Subject: [Web-erp-developers] wegs-erp > As Dick Stins mentioned in one of hs previous email : > > "The design of these issues should be loosely connected or we should > create one big project (wegs-erp?)." > > Is this something that people would be interested in? > > I for one have little knowledge of ERP, but from a coding and CRM/project management side of things, I am fairly well versed and have enough knowledge of ERP to see how the two systems could work together to form a pretty comprehensive business tool. > > I am now in a position to start working on integrating EGS/weberp but would like to know peoples views on the situation and the best way to proceed. For example the address book for EGS is a core component to the entire system and indeed the CRM functionality runs from it so perhaps the first issue i have is now to over come the integration of the two address books. > > Thanks > > Jake > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: Jake S. <ns...@us...> - 2004-09-20 12:01:55
|
As Dick Stins mentioned in one of hs previous email : "The design of these issues should be loosely connected or we should create one big project (wegs-erp?)." Is this something that people would be interested in? I for one have little knowledge of ERP, but from a coding and CRM/project management side of things, I am fairly well versed and have enough knowledge of ERP to see how the two systems could work together to form a pretty comprehensive business tool. I am now in a position to start working on integrating EGS/weberp but would like to know peoples views on the situation and the best way to proceed. For example the address book for EGS is a core component to the entire system and indeed the CRM functionality runs from it so perhaps the first issue i have is now to over come the integration of the two address books. Thanks Jake |
From: Jake S. <ns...@us...> - 2004-09-20 11:57:34
|
I don't know if anyboy else has experience this but using the latest Firefox on OS X 10.3 when ever you try to select a customer or supplier you get a 404, hitting refresh brings up the page ok. Jake |
From: Phil D. <we...@pa...> - 2004-09-20 10:08:27
|
Brilliant Franck that will be most helpful. Many thanks Phil On Mon, 2004-09-20 at 11:20, Franck Martin wrote: > Ok, > > I have nearly finished to merge the quotation with the current CVS. I > will send you the complete tarball when done, so you can do a diff with > your CVS version and see the differences... > > Cheers > > Phil Daintree wrote: > > >Hi Franck, > > > >Many thanks for feeding back your work to the project. > > > >I see that you have re-used the existing sales order entry code > >SelectOrderItems with a quote option and there are some new tables - > >Please could you send me the sql for the new tables? > > > > > > |
From: skaill <sk...@ro...> - 2004-09-20 09:09:14
|
One less complication by using char = Y or N for boolean. Works will all databases and ready made for reports too ;) Ok, it wastes space (in some implementations) but who cares about that anymore?! ODBC (1992) met the challenges of differing DBMSs and was meant to be THE abstraction layer. In my mind it was ODBC that really pushed the way for a standard sql (sag sql) to become popular. Before this each DBMS had its proprietary language instead of sql so people were hungry for ODBC. The ODBC middle layer demanded everyone use a common set of commands and a standard sql. The problems with ODBC included slowness, which was resolved to a large extent over the years and having to install ODBC driver(s) for each type of database needed on every client machine. The database vendors had to write the ODBC driver for their product and make it work in the Microsoft hidden world of Windows. So why are these other abstraction layers cropping up when ODBC exists? Steve ----- Original Message ----- From: "Jake Stride" <ns...@us...> To: <web...@li...> Sent: Monday, September 20, 2004 3:40 AM Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > Daintrees wrote: > > >You'll have to excuse my naievety (and poor spelling) since most of the > >native functions are similar in function but different in name for differing > >DBs why does one need such a lavish abstraction layer why won't a > >ConnectDB.inc calling the native C calls to connect directly for other DBs > >do the trick? This way we have ultimate performance minimum overhead! > > > > > > I think the reason for it is that this works in principle but not in > pratice. > > > Take for example inserting booleans into a database, postgres represents > them as 't' and 'f' whilst I believe mysql represents them as '1' and > '0', so already you would have to wirte a function to deal with this, > and on it goes until you have your own abstraction layer. > > If you are using auto_incrementing/serial fields for ids a database > abstraction layer can use the native functions for those dbs that > support it but implement its own functionality for those that don't, > therefore using a database abstraction layer you can simply call > $db->nextId('tablename') > > I think it is 6 of one half a dozen of the other, if you do not plan on > using to many advanced db features then the ConnectDB method is fine, on > the other hand you can let somebody else deal with the abstraction who > has access to several DBs and a developer community that is working > solely on the task of database abstraction and not have to worry about > new features bugs etc yourself, simple upgrade the abstraction layer as > and when. > > I have taken some of my examples from > http://creole.phpdb.org/wiki/index.php?node=8 there point about quoting > is a good one too. > > Jake > > >I really don't understand why such lengths are necessary - the function > >calls are virtually one to one and even most of the parameters are the same. > > > >MS SQL Server > > > >mssql_connect > >mssql_fetch_array > >mssql_fetch_row > >mssql_data_seek > > > > > >MySql > > > >mysql_connect > >mysql_query > >mysql_fetch_array > >mysql_fetch_row > >mysql_data_seek > > > >Postgres > > > >pg_connect > >pg_query > >pg_fetch_array > >pg_fetch_row > >pg_data_seek > > > > > >Firebird/interbase > > > >ibase_connect > >ibase_query > >ibase_fetch_assoc > >ibase_fetch_row > > > >whoops there is no > >ibase_data_seek > > > >maybe I'm answering my own question! > > > > > >Phil > > > > > >----- Original Message ----- > >From: "Jake Stride" <ns...@us...> > >To: <web...@li...> > >Sent: Monday, September 20, 2004 5:58 PM > >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > >>Stins, Dick wrote: > >> > >> > >> > >>>Jake, > >>> > >>>Thanks for your comments. > >>> > >>>I am not a fan of pear:db. I prefer to use standard sql. That is already > >>> > >>> > >a > > > > > >>>big step for portability + the clean and mean weberp script > >>> > >>> > >ConnectDB.inc. > > > > > >>>So it should not be too hard to port web-erp to another db engine. > >>> > >>> > >>> > >>> > >>No to be honest neither am I, for reasons I won't bore you with it was > >>chosen at the start of the project and has persited through. Have you > >>had a look at > >> > >>http://creole.phpdb.org/ > >>http://propel.phpdb.org/wiki/ > >> > >> > >> > >>>Smarty might be interesting, but I am already glad when css is optimal > >>> > >>> > >used. > > > > > >>> > >>> > >>This is the case with EGS, it just allows all of the presentation logic > >>to be removed from the code base and allows people to be a lot more > >>flexible with the layout without having to trawl through the PHP code. > >> > >> > >> > >>>Multiple company support is interesting. > >>> > >>> > >>> > >>> > >>Yes this was one of the distinctions that was used to justify it over > >>simply contributing to an exisitng project since non of the others do > >>it. For this reason I am not sure if one of the Application Frameworks > >>would have worked due to its authentication system. > >> > >>Have you looked at http://www.binarycloud.com/ > >> > >> > >> > >>>Does it also support ldap (nds)? > >>> > >>> > >>> > >>> > >>Not at present. My knowledge of ldap consists of the following: > >> > >>It exists > >>It is adirectory server > >> > >>I have always thought that it would be good to have it working with ldap > >>but unfortunately I have not had the time to look into it. However with > >>the present system I believe you can use PEAR:DB to connect to ldap so > >>may be possible. > >> > >>Thanks > >> > >>Jake > >> > >> > >> > >>>with best regards, > >>> > >>>Dick Stins > >>> > >>>----- Original Message ----- > >>>From: "Jake Stride" <ns...@us...> > >>>To: <web...@li...> > >>>Sent: Sunday, September 19, 2004 7:41 PM > >>>Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > >>> > >>> > >>> > >>> > >>> > >>> > >>>>Stins, Dick wrote: > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>Jake, > >>>>> > >>>>>I think that common functions which are needed in weberp and in your > >>>>> > >>>>> > >crm > > > > > >>>>>software should be encapsulated in classes, so you do not need to know > >>>>> > >>>>> > >>>>> > >>>>> > >>>where > >>> > >>> > >>> > >>> > >>>>>the information is comming from (postgres or mysql). > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>At the moment it kind of should be in that it uses PEAR:DB for > >>>> > >>>> > >>>> > >>>> > >>>abstraction. > >>> > >>> > >>> > >>> > >>>>>When you want to > >>>>>integrate web-erp and your crm software, you still need to integrate > >>>>> > >>>>> > >the > > > > > >>>>>authentication and the address books processing and .... > >>>>>The design of these issues should be loosely connected or we should > >>>>> > >>>>> > >>>>> > >>>>> > >>>create > >>> > >>> > >>> > >>> > >>>>>one big project (wegs-erp?). > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>That could be interesting and worthwhile, is it something people may be > >>>>interested in? > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>The same for all your code which needs views. Those should be > >>>>> > >>>>> > >>>>> > >>>>> > >>>encapsulated > >>> > >>> > >>> > >>> > >>>>>in classes, so it's easy to write an alternative for mysql > >>>>>(allthough when you are able to run mysql with maxdb, then probably > >>>>> > >>>>> > >you > > > > > >>>>> > >>>>> > >>>can > >>> > >>> > >>> > >>> > >>>>>use views). > >>>>> > >>>>>I even recommend to develop an architecture with: > >>>>>- front end layer > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>Smarty for templating > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>- business rule layer > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>System is written as classes > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>- database trigger layer > >>>>>- database layer > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>PEAR > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>This helps to be in control of you own code, reuse of code, increase > >>>>>portability for you code (like porting to other databases: sql server, > >>>>>firebird, oracle). > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>EGS should work in oracle without much trouble because of PEAR:DB > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>An example of an architecture like this is: > >>>>>http://sourceforge.net/projects/seagull/ > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>I did have a look at these, the problem is that EGS authentication is > >>>>more complicated that this. It is written as an ASP application so that > >>>>several companies can use the same server/DB etc. > >>>> > >>>>IE in egs one company can login and create there own users and groups > >>>>and insert data etc that another company cannot see. > >>>> > >>>>Jake > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>With best regards, > >>>>> > >>>>>Dick Stins > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>> > >>> > >>> > >>>------------------------------------------------------- > >>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>>who ports your project to Linux PPC the best. Sponsored by IBM. > >>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>>_______________________________________________ > >>>Web-erp-developers mailing list > >>>Web...@li... > >>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >>> > >>> > >>> > >>> > >> > >>------------------------------------------------------- > >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >>Project Admins to receive an Apple iPod Mini FREE for your judgement on > >>who ports your project to Linux PPC the best. Sponsored by IBM. > >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >>_______________________________________________ > >>Web-erp-developers mailing list > >>Web...@li... > >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers > >> > >> > >> > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > >who ports your project to Linux PPC the best. Sponsored by IBM. > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >_______________________________________________ > >Web-erp-developers mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers |
From: Jake S. <ns...@us...> - 2004-09-20 07:40:22
|
Daintrees wrote: >You'll have to excuse my naievety (and poor spelling) since most of the >native functions are similar in function but different in name for differing >DBs why does one need such a lavish abstraction layer why won't a >ConnectDB.inc calling the native C calls to connect directly for other DBs >do the trick? This way we have ultimate performance minimum overhead! > > I think the reason for it is that this works in principle but not in pratice. Take for example inserting booleans into a database, postgres represents them as 't' and 'f' whilst I believe mysql represents them as '1' and '0', so already you would have to wirte a function to deal with this, and on it goes until you have your own abstraction layer. If you are using auto_incrementing/serial fields for ids a database abstraction layer can use the native functions for those dbs that support it but implement its own functionality for those that don't, therefore using a database abstraction layer you can simply call $db->nextId('tablename') I think it is 6 of one half a dozen of the other, if you do not plan on using to many advanced db features then the ConnectDB method is fine, on the other hand you can let somebody else deal with the abstraction who has access to several DBs and a developer community that is working solely on the task of database abstraction and not have to worry about new features bugs etc yourself, simple upgrade the abstraction layer as and when. I have taken some of my examples from http://creole.phpdb.org/wiki/index.php?node=8 there point about quoting is a good one too. Jake >I really don't understand why such lengths are necessary - the function >calls are virtually one to one and even most of the parameters are the same. > >MS SQL Server > >mssql_connect >mssql_fetch_array >mssql_fetch_row >mssql_data_seek > > >MySql > >mysql_connect >mysql_query >mysql_fetch_array >mysql_fetch_row >mysql_data_seek > >Postgres > >pg_connect >pg_query >pg_fetch_array >pg_fetch_row >pg_data_seek > > >Firebird/interbase > >ibase_connect >ibase_query >ibase_fetch_assoc >ibase_fetch_row > >whoops there is no >ibase_data_seek > >maybe I'm answering my own question! > > >Phil > > >----- Original Message ----- >From: "Jake Stride" <ns...@us...> >To: <web...@li...> >Sent: Monday, September 20, 2004 5:58 PM >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > >>Stins, Dick wrote: >> >> >> >>>Jake, >>> >>>Thanks for your comments. >>> >>>I am not a fan of pear:db. I prefer to use standard sql. That is already >>> >>> >a > > >>>big step for portability + the clean and mean weberp script >>> >>> >ConnectDB.inc. > > >>>So it should not be too hard to port web-erp to another db engine. >>> >>> >>> >>> >>No to be honest neither am I, for reasons I won't bore you with it was >>chosen at the start of the project and has persited through. Have you >>had a look at >> >>http://creole.phpdb.org/ >>http://propel.phpdb.org/wiki/ >> >> >> >>>Smarty might be interesting, but I am already glad when css is optimal >>> >>> >used. > > >>> >>> >>This is the case with EGS, it just allows all of the presentation logic >>to be removed from the code base and allows people to be a lot more >>flexible with the layout without having to trawl through the PHP code. >> >> >> >>>Multiple company support is interesting. >>> >>> >>> >>> >>Yes this was one of the distinctions that was used to justify it over >>simply contributing to an exisitng project since non of the others do >>it. For this reason I am not sure if one of the Application Frameworks >>would have worked due to its authentication system. >> >>Have you looked at http://www.binarycloud.com/ >> >> >> >>>Does it also support ldap (nds)? >>> >>> >>> >>> >>Not at present. My knowledge of ldap consists of the following: >> >>It exists >>It is adirectory server >> >>I have always thought that it would be good to have it working with ldap >>but unfortunately I have not had the time to look into it. However with >>the present system I believe you can use PEAR:DB to connect to ldap so >>may be possible. >> >>Thanks >> >>Jake >> >> >> >>>with best regards, >>> >>>Dick Stins >>> >>>----- Original Message ----- >>>From: "Jake Stride" <ns...@us...> >>>To: <web...@li...> >>>Sent: Sunday, September 19, 2004 7:41 PM >>>Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap >>> >>> >>> >>> >>> >>> >>>>Stins, Dick wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Jake, >>>>> >>>>>I think that common functions which are needed in weberp and in your >>>>> >>>>> >crm > > >>>>>software should be encapsulated in classes, so you do not need to know >>>>> >>>>> >>>>> >>>>> >>>where >>> >>> >>> >>> >>>>>the information is comming from (postgres or mysql). >>>>> >>>>> >>>>> >>>>> >>>>> >>>>At the moment it kind of should be in that it uses PEAR:DB for >>>> >>>> >>>> >>>> >>>abstraction. >>> >>> >>> >>> >>>>>When you want to >>>>>integrate web-erp and your crm software, you still need to integrate >>>>> >>>>> >the > > >>>>>authentication and the address books processing and .... >>>>>The design of these issues should be loosely connected or we should >>>>> >>>>> >>>>> >>>>> >>>create >>> >>> >>> >>> >>>>>one big project (wegs-erp?). >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>That could be interesting and worthwhile, is it something people may be >>>>interested in? >>>> >>>> >>>> >>>> >>>> >>>>>The same for all your code which needs views. Those should be >>>>> >>>>> >>>>> >>>>> >>>encapsulated >>> >>> >>> >>> >>>>>in classes, so it's easy to write an alternative for mysql >>>>>(allthough when you are able to run mysql with maxdb, then probably >>>>> >>>>> >you > > >>>>> >>>>> >>>can >>> >>> >>> >>> >>>>>use views). >>>>> >>>>>I even recommend to develop an architecture with: >>>>>- front end layer >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>Smarty for templating >>>> >>>> >>>> >>>> >>>> >>>>>- business rule layer >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>System is written as classes >>>> >>>> >>>> >>>> >>>> >>>>>- database trigger layer >>>>>- database layer >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>PEAR >>>> >>>> >>>> >>>> >>>> >>>>>This helps to be in control of you own code, reuse of code, increase >>>>>portability for you code (like porting to other databases: sql server, >>>>>firebird, oracle). >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>EGS should work in oracle without much trouble because of PEAR:DB >>>> >>>> >>>> >>>> >>>> >>>>>An example of an architecture like this is: >>>>>http://sourceforge.net/projects/seagull/ >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>I did have a look at these, the problem is that EGS authentication is >>>>more complicated that this. It is written as an ASP application so that >>>>several companies can use the same server/DB etc. >>>> >>>>IE in egs one company can login and create there own users and groups >>>>and insert data etc that another company cannot see. >>>> >>>>Jake >>>> >>>> >>>> >>>> >>>> >>>>>With best regards, >>>>> >>>>>Dick Stins >>>>> >>>>> >>>>> >>>>> >>>>> >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>>who ports your project to Linux PPC the best. Sponsored by IBM. >>>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>>_______________________________________________ >>>Web-erp-developers mailing list >>>Web...@li... >>>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >>> >>> >>> >>> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>who ports your project to Linux PPC the best. Sponsored by IBM. >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>_______________________________________________ >>Web-erp-developers mailing list >>Web...@li... >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > |
From: Daintrees <p.d...@pa...> - 2004-09-20 07:22:08
|
You'll have to excuse my naievety (and poor spelling) since most of the native functions are similar in function but different in name for differing DBs why does one need such a lavish abstraction layer why won't a ConnectDB.inc calling the native C calls to connect directly for other DBs do the trick? This way we have ultimate performance minimum overhead! I really don't understand why such lengths are necessary - the function calls are virtually one to one and even most of the parameters are the same. MS SQL Server mssql_connect mssql_fetch_array mssql_fetch_row mssql_data_seek MySql mysql_connect mysql_query mysql_fetch_array mysql_fetch_row mysql_data_seek Postgres pg_connect pg_query pg_fetch_array pg_fetch_row pg_data_seek Firebird/interbase ibase_connect ibase_query ibase_fetch_assoc ibase_fetch_row whoops there is no ibase_data_seek maybe I'm answering my own question! Phil ----- Original Message ----- From: "Jake Stride" <ns...@us...> To: <web...@li...> Sent: Monday, September 20, 2004 5:58 PM Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > Stins, Dick wrote: > > >Jake, > > > >Thanks for your comments. > > > >I am not a fan of pear:db. I prefer to use standard sql. That is already a > >big step for portability + the clean and mean weberp script ConnectDB.inc. > >So it should not be too hard to port web-erp to another db engine. > > > > > No to be honest neither am I, for reasons I won't bore you with it was > chosen at the start of the project and has persited through. Have you > had a look at > > http://creole.phpdb.org/ > http://propel.phpdb.org/wiki/ > > >Smarty might be interesting, but I am already glad when css is optimal used. > > > > > This is the case with EGS, it just allows all of the presentation logic > to be removed from the code base and allows people to be a lot more > flexible with the layout without having to trawl through the PHP code. > > >Multiple company support is interesting. > > > > > Yes this was one of the distinctions that was used to justify it over > simply contributing to an exisitng project since non of the others do > it. For this reason I am not sure if one of the Application Frameworks > would have worked due to its authentication system. > > Have you looked at http://www.binarycloud.com/ > > >Does it also support ldap (nds)? > > > > > Not at present. My knowledge of ldap consists of the following: > > It exists > It is adirectory server > > I have always thought that it would be good to have it working with ldap > but unfortunately I have not had the time to look into it. However with > the present system I believe you can use PEAR:DB to connect to ldap so > may be possible. > > Thanks > > Jake > > >with best regards, > > > >Dick Stins > > > >----- Original Message ----- > >From: "Jake Stride" <ns...@us...> > >To: <web...@li...> > >Sent: Sunday, September 19, 2004 7:41 PM > >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > > > > > > >>Stins, Dick wrote: > >> > >> > >> > >>>Jake, > >>> > >>>I think that common functions which are needed in weberp and in your crm > >>>software should be encapsulated in classes, so you do not need to know > >>> > >>> > >where > > > > > >>>the information is comming from (postgres or mysql). > >>> > >>> > >>> > >>At the moment it kind of should be in that it uses PEAR:DB for > >> > >> > >abstraction. > > > > > >>>When you want to > >>>integrate web-erp and your crm software, you still need to integrate the > >>>authentication and the address books processing and .... > >>>The design of these issues should be loosely connected or we should > >>> > >>> > >create > > > > > >>>one big project (wegs-erp?). > >>> > >>> > >>> > >>> > >>That could be interesting and worthwhile, is it something people may be > >>interested in? > >> > >> > >> > >>>The same for all your code which needs views. Those should be > >>> > >>> > >encapsulated > > > > > >>>in classes, so it's easy to write an alternative for mysql > >>>(allthough when you are able to run mysql with maxdb, then probably you > >>> > >>> > >can > > > > > >>>use views). > >>> > >>>I even recommend to develop an architecture with: > >>>- front end layer > >>> > >>> > >>> > >>> > >>Smarty for templating > >> > >> > >> > >>>- business rule layer > >>> > >>> > >>> > >>> > >>System is written as classes > >> > >> > >> > >>>- database trigger layer > >>>- database layer > >>> > >>> > >>> > >>> > >>PEAR > >> > >> > >> > >>>This helps to be in control of you own code, reuse of code, increase > >>>portability for you code (like porting to other databases: sql server, > >>>firebird, oracle). > >>> > >>> > >>> > >>> > >>EGS should work in oracle without much trouble because of PEAR:DB > >> > >> > >> > >>>An example of an architecture like this is: > >>>http://sourceforge.net/projects/seagull/ > >>> > >>> > >>> > >>> > >>I did have a look at these, the problem is that EGS authentication is > >>more complicated that this. It is written as an ASP application so that > >>several companies can use the same server/DB etc. > >> > >>IE in egs one company can login and create there own users and groups > >>and insert data etc that another company cannot see. > >> > >>Jake > >> > >> > >> > >>>With best regards, > >>> > >>>Dick Stins > >>> > >>> > >>> > > > > > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > >Project Admins to receive an Apple iPod Mini FREE for your judgement on > >who ports your project to Linux PPC the best. Sponsored by IBM. > >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > >_______________________________________________ > >Web-erp-developers mailing list > >Web...@li... > >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Web-erp-developers mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/web-erp-developers > |
From: Jake S. <ns...@us...> - 2004-09-20 05:58:59
|
Stins, Dick wrote: >Jake, > >Thanks for your comments. > >I am not a fan of pear:db. I prefer to use standard sql. That is already a >big step for portability + the clean and mean weberp script ConnectDB.inc. >So it should not be too hard to port web-erp to another db engine. > > No to be honest neither am I, for reasons I won't bore you with it was chosen at the start of the project and has persited through. Have you had a look at http://creole.phpdb.org/ http://propel.phpdb.org/wiki/ >Smarty might be interesting, but I am already glad when css is optimal used. > > This is the case with EGS, it just allows all of the presentation logic to be removed from the code base and allows people to be a lot more flexible with the layout without having to trawl through the PHP code. >Multiple company support is interesting. > > Yes this was one of the distinctions that was used to justify it over simply contributing to an exisitng project since non of the others do it. For this reason I am not sure if one of the Application Frameworks would have worked due to its authentication system. Have you looked at http://www.binarycloud.com/ >Does it also support ldap (nds)? > > Not at present. My knowledge of ldap consists of the following: It exists It is adirectory server I have always thought that it would be good to have it working with ldap but unfortunately I have not had the time to look into it. However with the present system I believe you can use PEAR:DB to connect to ldap so may be possible. Thanks Jake >with best regards, > >Dick Stins > >----- Original Message ----- >From: "Jake Stride" <ns...@us...> >To: <web...@li...> >Sent: Sunday, September 19, 2004 7:41 PM >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > >>Stins, Dick wrote: >> >> >> >>>Jake, >>> >>>I think that common functions which are needed in weberp and in your crm >>>software should be encapsulated in classes, so you do not need to know >>> >>> >where > > >>>the information is comming from (postgres or mysql). >>> >>> >>> >>At the moment it kind of should be in that it uses PEAR:DB for >> >> >abstraction. > > >>>When you want to >>>integrate web-erp and your crm software, you still need to integrate the >>>authentication and the address books processing and .... >>>The design of these issues should be loosely connected or we should >>> >>> >create > > >>>one big project (wegs-erp?). >>> >>> >>> >>> >>That could be interesting and worthwhile, is it something people may be >>interested in? >> >> >> >>>The same for all your code which needs views. Those should be >>> >>> >encapsulated > > >>>in classes, so it's easy to write an alternative for mysql >>>(allthough when you are able to run mysql with maxdb, then probably you >>> >>> >can > > >>>use views). >>> >>>I even recommend to develop an architecture with: >>>- front end layer >>> >>> >>> >>> >>Smarty for templating >> >> >> >>>- business rule layer >>> >>> >>> >>> >>System is written as classes >> >> >> >>>- database trigger layer >>>- database layer >>> >>> >>> >>> >>PEAR >> >> >> >>>This helps to be in control of you own code, reuse of code, increase >>>portability for you code (like porting to other databases: sql server, >>>firebird, oracle). >>> >>> >>> >>> >>EGS should work in oracle without much trouble because of PEAR:DB >> >> >> >>>An example of an architecture like this is: >>>http://sourceforge.net/projects/seagull/ >>> >>> >>> >>> >>I did have a look at these, the problem is that EGS authentication is >>more complicated that this. It is written as an ASP application so that >>several companies can use the same server/DB etc. >> >>IE in egs one company can login and create there own users and groups >>and insert data etc that another company cannot see. >> >>Jake >> >> >> >>>With best regards, >>> >>>Dick Stins >>> >>> >>> > > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > |
From: Hani N. <ha...@na...> - 2004-09-19 23:55:46
|
If you guys do decide to use Smarty you will get a nice feature relating to translations. With a little configuration you can get smarty to do translation when it compiles the templates, this means that for static text your code just translates it once (the first time the template is compiled). After a page has been accessed one time all the 'static' text will not need to be translated. Having said this, using smarty properly you require quite a bit of refactoring of weberps code. Hani Stins, Dick wrote: >*This message was transferred with a trial version of CommuniGate(tm) Pro* >Language team, > >Please check smarty for transforming decimal point locator (. or ,) and >thousands separator (, or .) and may be for more issues like dates formats. >http://www.oxyscripts.com/manuals/smarty/language.modifier.string.format.htm >l > >When this helps, then we can setup a smarty template per language? > >With best regards, > >Dick Stins >----- Original Message ----- >From: "Stins, Dick" <DR...@Zi...> >To: <web...@li...> >Sent: Monday, September 20, 2004 1:03 AM >Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap > > > > >>Jake, >> >>Thanks for your comments. >> >>I am not a fan of pear:db. I prefer to use standard sql. That is already a >>big step for portability + the clean and mean weberp script ConnectDB.inc. >>So it should not be too hard to port web-erp to another db engine. >> >>Smarty might be interesting, but I am already glad when css is optimal >> >> >used. > > >>Multiple company support is interesting. >> >>Does it also support ldap (nds)? >> >>with best regards, >> >>Dick Stins >> >>----- Original Message ----- >>From: "Jake Stride" <ns...@us...> >>To: <web...@li...> >>Sent: Sunday, September 19, 2004 7:41 PM >>Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap >> >> >> >> >>>Stins, Dick wrote: >>> >>> >>> >>>>Jake, >>>> >>>>I think that common functions which are needed in weberp and in your >>>> >>>> >crm > > >>>>software should be encapsulated in classes, so you do not need to know >>>> >>>> >>where >> >> >>>>the information is comming from (postgres or mysql). >>>> >>>> >>>> >>>At the moment it kind of should be in that it uses PEAR:DB for >>> >>> >>abstraction. >> >> >>>>When you want to >>>>integrate web-erp and your crm software, you still need to integrate >>>> >>>> >the > > >>>>authentication and the address books processing and .... >>>>The design of these issues should be loosely connected or we should >>>> >>>> >>create >> >> >>>>one big project (wegs-erp?). >>>> >>>> >>>> >>>> >>>That could be interesting and worthwhile, is it something people may be >>>interested in? >>> >>> >>> >>>>The same for all your code which needs views. Those should be >>>> >>>> >>encapsulated >> >> >>>>in classes, so it's easy to write an alternative for mysql >>>>(allthough when you are able to run mysql with maxdb, then probably >>>> >>>> >you > > >>can >> >> >>>>use views). >>>> >>>>I even recommend to develop an architecture with: >>>>- front end layer >>>> >>>> >>>> >>>> >>>Smarty for templating >>> >>> >>> >>>>- business rule layer >>>> >>>> >>>> >>>> >>>System is written as classes >>> >>> >>> >>>>- database trigger layer >>>>- database layer >>>> >>>> >>>> >>>> >>>PEAR >>> >>> >>> >>>>This helps to be in control of you own code, reuse of code, increase >>>>portability for you code (like porting to other databases: sql server, >>>>firebird, oracle). >>>> >>>> >>>> >>>> >>>EGS should work in oracle without much trouble because of PEAR:DB >>> >>> >>> >>>>An example of an architecture like this is: >>>>http://sourceforge.net/projects/seagull/ >>>> >>>> >>>> >>>> >>>I did have a look at these, the problem is that EGS authentication is >>>more complicated that this. It is written as an ASP application so that >>>several companies can use the same server/DB etc. >>> >>>IE in egs one company can login and create there own users and groups >>>and insert data etc that another company cannot see. >>> >>>Jake >>> >>> >>> >>>>With best regards, >>>> >>>>Dick Stins >>>> >>>> >>>> >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >>Project Admins to receive an Apple iPod Mini FREE for your judgement on >>who ports your project to Linux PPC the best. Sponsored by IBM. >>Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >>_______________________________________________ >>Web-erp-developers mailing list >>Web...@li... >>https://lists.sourceforge.net/lists/listinfo/web-erp-developers >> >> > > > > >------------------------------------------------------- >This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 >Project Admins to receive an Apple iPod Mini FREE for your judgement on >who ports your project to Linux PPC the best. Sponsored by IBM. >Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php >_______________________________________________ >Web-erp-developers mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/web-erp-developers > > > > |