Progress_Guy
Member
Dear god give me strength - Although I suspect he has more pressing matters at the moment !!!
As a die hard Progress Developer I've always stood by the Progress App. Builder, but, its advantages are beginning to get fewer and fewer, i.e. the only advantage I can now see is :-
1. The ability to seamlessly integrate between the code (using Progerss 4GL) and the database.
Here endeth the advantages.
Now disadvanteges :-
1. Has this nasty habbit of corrupting an application whilst developing it - examples of this are too numerous to mention, but, I've just spent a morning rewriting a window because it somehow allowed me to resize the window and promptly resize and position all widgets and frame and so - nice !! Other examples include corrupt Smart Object procedures and an annoying message which pops and then if you save promptly corrupts all code. So mad I cannot 'member what it is off the top of my head.
2. Extremely 'twee' and old fashioned interface.
3. Colours - come on Progress I don't want to have to modify a config file to distribute these.
4. Its concept of MDI (Multiple Document Interface) is limited to say the least.
5. Some sort of repository for holding details about procesures so that when you type in a procedure name the parameters you need are automatically populated. This alone would save masses of development time, particularly with App. Server. - yeah, I know that .net use this, but, come on progress a little plagiarism wouldn't go amiss from time to time.
To top this I'm doing my MCAD and dot net interfaces are just so superior. Progress App. Builder now looks in excess of 10 years old.
I was even more dismayed upon glancing at OE 10 that it looks about the same !!!!
I suppose I could go to Progress and whinge, but, all that Progress are interested in these days is Dynamics - Yeah and how many are using this (in the UK not many - wonder why ?? ). I started off using ADM1 and the chances of me ever using a standard Progerss framework again are negative a zillion.
And if I replace all our front-ends with .net then what would my superiors be saying - well why don't we look at alternatives for the databases - say SQL Serevr or Oracle. Good questions - I may just take them up on that. At least it'd be easier to get a new job.
Come on Progress guys are you just giving up on it and letting everyone go the .net front-end !!
Can you tell I'm a little peeved. Maybe I should have had a brew and counted to 10 before writing this.
I need a lie down now.
As a die hard Progress Developer I've always stood by the Progress App. Builder, but, its advantages are beginning to get fewer and fewer, i.e. the only advantage I can now see is :-
1. The ability to seamlessly integrate between the code (using Progerss 4GL) and the database.
Here endeth the advantages.
Now disadvanteges :-
1. Has this nasty habbit of corrupting an application whilst developing it - examples of this are too numerous to mention, but, I've just spent a morning rewriting a window because it somehow allowed me to resize the window and promptly resize and position all widgets and frame and so - nice !! Other examples include corrupt Smart Object procedures and an annoying message which pops and then if you save promptly corrupts all code. So mad I cannot 'member what it is off the top of my head.
2. Extremely 'twee' and old fashioned interface.
3. Colours - come on Progress I don't want to have to modify a config file to distribute these.
4. Its concept of MDI (Multiple Document Interface) is limited to say the least.
5. Some sort of repository for holding details about procesures so that when you type in a procedure name the parameters you need are automatically populated. This alone would save masses of development time, particularly with App. Server. - yeah, I know that .net use this, but, come on progress a little plagiarism wouldn't go amiss from time to time.
To top this I'm doing my MCAD and dot net interfaces are just so superior. Progress App. Builder now looks in excess of 10 years old.
I was even more dismayed upon glancing at OE 10 that it looks about the same !!!!
I suppose I could go to Progress and whinge, but, all that Progress are interested in these days is Dynamics - Yeah and how many are using this (in the UK not many - wonder why ?? ). I started off using ADM1 and the chances of me ever using a standard Progerss framework again are negative a zillion.
And if I replace all our front-ends with .net then what would my superiors be saying - well why don't we look at alternatives for the databases - say SQL Serevr or Oracle. Good questions - I may just take them up on that. At least it'd be easier to get a new job.
Come on Progress guys are you just giving up on it and letting everyone go the .net front-end !!
Can you tell I'm a little peeved. Maybe I should have had a brew and counted to 10 before writing this.
I need a lie down now.