Framework

[microliance]

Opinion anyone.

I started an application for a client and used the Foxpro Framework (version 7.0) as the basis for this app.

I added a number of my own methods and forms to the class library in order to have it work with the sql database and other custom forms.

A second consultant visited my work and said that the framwork that comes with foxpro is not recommend as it is limited and not scallable. The consultant believes that starting from scratch is recommended.

I have not come accross issues with the framework that is build from the application wizard, especially when one uses it for the starting point to builds on.

Anyones feedback would be well appreciated. Thank You.

 

[ramani]

Hi

The question is so generic, that a concrete answer is not possible.

1. The size of the project
2. The requirements
3. The scalability required.. meaning.. to be used in one terminal.. to be used in one office.. to be used in one country.. to be used from many countries.. all these change the strategy very much.
4. The number of develpment team and their skills also matters in my view.

a. So if the project started with VFP frame work does the job and generates the required reports, it is fine. A simple comment that it needs to be built fom scratch is meaningless.
b. If the requirements are likely to grow as the users now working on the current application demand more in the near future.. you need to think about it.

The consultants views or criticism should be taken positively for your own growth. Often the criticisers pave the way for your better growth unaware of them, even if they are competitors.

I for one use my own classes and OOPS methods for developments in various scenarious. That doesnt mean every one need to go for that. That will work out very costly in terms of development time cost. But looking at the larger benefits.. they work out economical at the end.

Again a framework for all situation is difficult to make or to be found. Frameworks could be limitations also. VFPs oen built wizards have limitations. Now all these at what stage of the users or at what requirements is the question. Thay are very easy and good at smaller requirements. They are very economical.

So you can see no concrete answers. There are pros and cons. Benefits and limitations. A start from the scratch with your own fundamental classes.. going to cost you more. You have to go thru reinvention of wheels.. wheels made to your own required size and versatility. The ready mnade ones are of standard features and could fit your requirement as well.

SO decision has to be from you

ramani
(Subramanian.G),FoxAcc, ramani_g@yahoo.com

 

[microliance]

thank u ramani,

 

[Mike Gagnon]

A second consultant visited my work and said that the framwork that comes with foxpro is not recommend as it is limited and not scallable. The consultant believes that starting from scratch is recommended.

I cannot see that using a simple framework like the VFP wizard framework can be limited or not scalable, compared to starting from scratch. They are two different things. Be a framework (any framework), gets you started with the basic functions already pre-established, where as starting from scratch, where you would have to also write the basic functions.
Its a personnal choice, I never used a framework, yet some other programmers are more comfortable using one.
Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[microliance]

Thank you Mike, what you say makes sense, only the programmer can limit its scallability based on what they do with the framework.