Otto wrote:Hello Mark,
nothing would change for you as an application developer. Everything would remain the same for you here. Only the source code of xBrowse would change.
For example, if you look at the source code, everything is in one file. I think it should be structured more simply. At the moment, there are over 16,000 lines of code in a single sequence. For instance, I think the methods should be placed in separate classes:
METHOD SetDolphin( oMysql, lAddCols, lAutoOrder, aFldNames )
METHOD SetMySql( oMysql, lAddCols, lAutoOrder, aFldNames ) // TMySql object
METHOD SetColFromMySQL( cnCol, cHeader ) // used internally from MySQL
METHOD SetPostGre( oQry, lAddCols, lAutoOrder, aFldNames )
METHOD SetPostGreCol( nCol, oQry )
We are exactly at the point you mentioned. Are the FW users interested? I think the xBrowse source code is currently so complex that only very few can contribute to it. Even though many of us have ideas for improvements.
However, this suggestion has nothing to do with the web. You're mixing things up here.
Best regards,
Otto
We should go back many years, xbrowse did not exist and there were the classes Wbrowse (listbox by ceccarelli) and later Sbrowse (by Mercado), the real Xbrowse was used but it was part of an OZLIB package sold separately with other classes included.
Then after the split between the two partners of fivetech, Linares decided to include xbrowse in the fw.
I remember that xbrowse was smoother and was exclusively for the dbf format.
Later Mr. Nageswarao Gunupudi
adapted some new functions for Sql, Dolphin and MySql, maybe they should have made child object classes and not put everything in the xbrowse class.
Currently the source lines of the xbrowse class are 19341 and I realize that they are a bit too many, I saw that compiling a simple program with the addition of the xbrowse.prg file the compiler takes a little longer but it is still satisfactory
perhaps as I already said we could think of subclasses and merge the functions into other files but then I think it is too dispersive both for us and for those who are or will be working on it in the future
Maybe for an xbrowse for the web you could already think about making a subclass but I will not delve into this topic because I do not deal with the web as I have already repeated to you many times if I have to write a program for the web I use other programming languages that I have been using for many years now and doing it with fivewin remains very difficult for me, the policy has changed before you could write a source and space it in many operating systems, with the advent of fwh of the web the structure of the source code changes radically I was hoping for an equal source and to link only a library but unfortunately it is not like that and I do not have time to waste time in a new language that I do not know where it will take me.
Since from 1991/1992 ( fw for clipper Rel. 14.4 - Momos)
I use : FiveWin for Harbour November 2023 - January 2024 - Harbour 3.2.0dev (harbour_bcc770_32_20240309) - Bcc7.70 - xMate ver. 1.15.3 - PellesC - mail: silvio[dot]falconi[at]gmail[dot]com