ok a couple of questions
1) what is this graphical exported proedures? what graphics have to do with the export process?
2) Who can not execute his own methods any where he wants and what kind of help to do you offer to him what are the problems addressed?
3) Errm since when is the role of the library to control the focus of anything? Again what is the exact problem addressed?
4) if a function is exported why any application would not be able to use it be it main secondary or even a sub process that requires an other application to work.
5) erm now you lost me what is java-native and what it has to do with FPC or lazarus?
The rest did not bother to look, if the points given do not make sense then the solution presented is irrelevant for my development.
First of all, thanks to give attention to this tip.
The idea is to use fpc and his library-feature to be accessible to foreign languages (and to Pascal too, of course).
And mainly Java... (fpc can create Java-native libraries)
1) what is this graphical exported proedures? what graphics have to do with the export process?
That library is able to produce graphical result ("graphical exported methods"), like a graphical program does.
2) Who can not execute his own methods any where he wants and what kind of help to do you offer to him what are the problems addressed?
Hum, sorry, this one i do not understand...
3) Errm since when is the role of the library to control the focus of anything? Again what is the exact problem addressed?
Since now
=> Because the library has a graphical-main procedure, for example a form with some buttons, it is important that the library can keep control, to respond to button.click.
4) if a function is exported why any application would not be able to use it be it main secondary or even a sub process that requires an other application to work.
Aaargh, same as 2)
5) erm now you lost me what is java-native and what it has to do with FPC or lazarus?
It is the goal => You create a "hyper simple" Java-application, with only few methods.
That Java application will load your "graphical exported native Java library", run main-graphical-proc (in fact a fpcGUI application inside a thread) and Java application can still interface (if needed) with the main-graphical-proc (via other exported methods), even if Java application is also graphical (using native Java widget, for example).
[EDIT] If your main program does not need to have focus after running main-graphic-proc, the code is even simpler.
Recent
