Forum > iPhone/iPad
Options for iOS/Android
mse:
--- Quote from: airpas on March 19, 2016, 12:06:22 pm ---msegui/ide is good as a lightweight rad with a nice set of components, but has some drak sides : the project file is not backword compatible (if u have a project made with the version 3 , then it probably wont work with the new 4.2 ) ,
--- End quote ---
If stored properties of MSEgui components change I add code which automatically converts old *.mfm's while loading. Please load all forms in the new MSEide, RightClick-'Touch all forms' in one of the forms, 'File'-'Save all', that will write updated *.mfm files to disk.
If the conversion code is expensive I remove it after some MSEgui versions. If one loads an incompatible form afterwards the *.mfm file will be opened in source editor for manual fix-up. Often it is enough to delete the problematic rows.
IIRC the last time I removed conversion code was before MSEide+MSEgui version 3.0.
--- Quote --- another thing is the source code , its not commanted at all , that means the author does not reckon for contribution :/ .
--- End quote ---
That is not true! What is not obvious by reading the code *is* documented. The fact that I still can work with MSEgui code written in 1999 proves it. ;-)
--- Quote ---and the most important thing , the documentation .
--- End quote ---
The problem with the documentation is that it is scattered to many different places. None of the MSEide+MSEgui users was able to take over the task to coordinate the documentation process. Recently Michael Ebner made a new attempt:
http://wiki.freepascal.org/Reference:_MSEgui/TFace
http://wiki.freepascal.org/Reference:_MSEgui/TFont
http://wiki.freepascal.org/Reference:_MSEgui/TFrame
http://wiki.freepascal.org/Reference:_MSEgui/TLabel
http://wiki.freepascal.org/Reference:_MSEgui/TMseComponent
http://wiki.freepascal.org/Reference:_MSEgui/TSimpleWidget
http://wiki.freepascal.org/Reference:_MSEgui/TWidget
Maybe you can help?
If you have questions simply ask:
https://www.mail-archive.com/mseide-msegui-talk%40lists.sourceforge.net/
https://sourceforge.net/p/mseide-msegui/mailman
Blade:
--- Quote from: Leledumbo on March 18, 2016, 08:46:32 pm ---The only working (and I recommend) path for Android is to use LazAndroidModuleWizard. I never code for iOS, but the same author who produces component set used by LazAndroidModuleWizard also creates the equal component set for iOS. The author of LazAndroidModuleWizard recently creates LazArduinoModuleWizard, if you can convince him (probably providing him iOS device) he might be willing to create LaziOSModuleWizard.
--- End quote ---
I find this quite interesting. Sad that a LaziOSModuleWizard never came about, or at least not yet. I wonder if the author who produced the iOS component set is still active or willing. Appears he did an update in 2018, https://blog.naver.com/simonsayz/221209784815
Michael Collier:
Hi Phil
What you say intrigues me..
But the link seems broken for item (3) https://dl.dropboxusercontent.com/u/28343282/MacXPlatform/PascalDynLibs.html
Do you have another link available please?
--- Quote from: Phil on March 18, 2016, 05:49:22 pm ---Jim,
I really only see 3 realistic approaches for using Free Pascal in iOS development. They assume that the iOS headers have been parsed using Ryan's parser and that UI design uses iOS native controls and conventions.
(1) Write UI code in Objective Pascal without a designer. Virtually any IDE or text editor can be used. Write scripts for doing all the stuff that Xcode does for you automatically when building the .app bundle.
(2) Take a "hybrid" approach with Xcode, where the project has "dummy" ObjC files that are used only for UI design using the Xcode designer; corresponding Pascal units are what get compiled into the executable. I used to have templates for creating this kind of project in Xcode, but they were too much work to maintain (and very little interest from developers), so they're abandoned. Instead, just create the project with a script using an existing boilerplate project:
https://dl.dropboxusercontent.com/u/28343282/ObjP/ProjectXC.html
(3) Use Xcode per normal and write UI in Swift; all other code (ie, bulk of app) goes into a Pascal dynamic library. This allows normal use of Xcode UI designer and all other Xcode features that make life easier for the developer. Library code can then be shared with Pascal apps on other platforms.
A variety of examples that use the same Pascal library are here:
https://dl.dropboxusercontent.com/u/28343282/MacXPlatform/PascalDynLibs.html
Thanks.
-Phil
--- End quote ---
trev:
You are replying to a post from 2016 - six years ago. Phil has not logged on since 2018. You are unlikely to receive an answer.
Michael Collier:
oops, thank you.. I must have been thinking of Blades reply from a few months ago when I posted, thanks for letting me know :)
Navigation
[0] Message Index
[*] Previous page