Web Application VS Windows Application
-
i think this framework will make things complex for me, right now i'm using ajax and json to retrieve data from my DB without refreshing the page, i think i'm ok with my current method, cuz this framwork will take time from me to learn
-
I've never really been able to get my head wrapped around the MVC model of programming -- at least not as most of the Frameworks operate.
-
@scottalanmiller said:
@IT-ADMIN said:
ok thanks, i will take a look over CakePHP,
so no need to use OOP right ??Use what is common to the framework you choose
I'm not recommending CakePHP, I'm not a PHP guy so don't know what is the good options versus the names that I know. CakePHP is relatively popular in the space and a place to look. But don't choose it because I mentioned it, just start investigating there. PHP has a lot of frameworks that are good. Ruby and Python have one main framework that dominates their space and becomes the obvious thing to learn (Rails and Django) but even there it is not a foregone conclusion. PHP lacks this and has lots of smaller potential players.
This is an advantage to Ruby, most people simply choose Ruby on Rails and convention dictates everything that they do.
For PHP, there are several... CakePHP and Symfony are two that I am aware of.
-
ah, here you are @dafyre, where are you man, i'm looking for you
tell me how do you work with PHP, are you adopting OOP?? or maybe a framework ??
please i need your advice, i'm working on a PHP project right now, -
@IT-ADMIN said:
ah, here you are @dafyre, where are you man, i'm looking for you
tell me how do you work with PHP, are you adopting OOP?? or maybe a framework ??
please i need your advice, i'm working on a PHP project right now,I tend to write my code.. I'll have a php file for functions that I use a lot, and a library that I can use for handling various things like databases, etc.
Then I write the logic (PHP) and HTML in one file. So if I have a form that writes to a database, the form will be an HTML file, and will be styled with CSS, jQuery for Javascript stuff... Then the bits that actually write to the database will be just a PHP page that only writes to the database.
-
-
An HR payroll application
-
What library are you using??
-
@IT-ADMIN said:
An HR payroll application
Oh, fun! Last time I built one of those was in Access 97, lol. (Whatever the one before Office 2003 was).
-
For database connection , did you connect each time to DB or you using a persistance framework ??
-
I haven't used a MySQL library like that in a while, so I'm going to assume that it was a connection each time. If I'm not mistaken, PHP will keep MySQL sessions open briefly after your query is done.
-
@IT-ADMIN said:
For database connection , did you connect each time to DB or you using a persistance framework ??
Are you going to cache database information on the client?
-
@IT-ADMIN said:
For database connection , did you connect each time to DB or you using a persistance framework ??
I am, however, using ReadBeanPHP (http://www.redbeanphp.com/) as my Database library these days... It seems to work well, and from what I can gather it does not use Persistent connections either.
-
@scottalanmiller said:
@IT-ADMIN said:
For database connection , did you connect each time to DB or you using a persistance framework ??
Are you going to cache database information on the client?
Doesn't this lead to conflicts?
-
@wirestyle22 said:
@scottalanmiller said:
@IT-ADMIN said:
For database connection , did you connect each time to DB or you using a persistance framework ??
Are you going to cache database information on the client?
Doesn't this lead to conflicts?
Not if done correctly.
-
@wirestyle22 said:
@scottalanmiller said:
@IT-ADMIN said:
For database connection , did you connect each time to DB or you using a persistance framework ??
Are you going to cache database information on the client?
Doesn't this lead to conflicts?
We are using it right now to have this conversation.
-
i'm very sorry guys, i was in a meeting regarding this project,
actually i was informed that this project will not be only a payroll application but it should be kind of a small ERP that include all modules that our enterprise is working on, it is the best news i heard today, because we will migrate from VB.net to a whole PHP application, because we faced a limitation with .net because the boss want to access the portal from his mobile, so the decision was made to start a web application from scratch, i think it was the best decision ever made in my company,
-
now i have to prepare myself and start the project using the right tools from the begining and be able to expand the project in the future,
we will be 2 in this project, the other guy is considered the boss of the project, but i can still propose the right tools and framework to work with -
so what do you think guys of SQL Server VS MySQL?? because my collegue told me that we gonna use SQL server because MySQL is not reliable and supposed to manage small size databases
-
so he planned to use SQL SERVER ? i told him that we may install separably apach and MySQL and phpmyadmin in a linux server, at least it will be better that easyphp or wamp (designed for personnel use) but i cannot persuade him
