I am trying to create a form that requires quite a large amount of components but I do not want to create them all manually. Is there a way to create these components using a Form's Pre-activation script or some other script?
As of install4j 7, form components have to be configured statically in the IDE, there is no way to create them at runtime.
You can develop your own form component with the API that exiibits dynamic behavior, see the samples/customCode project for an example on how to get started.
Related
For a Web Service framework I am currently working on I'd like to add the possibility to test the generic Json services based on their metadata. It should be possible to dynamically build a view to let users test available Web Services. Is there a provision or some supported way to generate views dynamically in Play? if not and supposing that I simply make a template and generate it on the fly, how can this view be injected into the application at runtime?
I will be happy to see documentation/examples/pointers that could help develop such solution ...
I am assuming that you want to create a scala.html and use it on somewhere by taking the html created, is that?
If you create a scala template myView.scala.html then on MyController you can call views.html.myView.render().body(); Then you would have the html created by the template.
Template Documentation
or "How to decouple UI from business logic in Delphi?"
Each target platform has its own set of native firemonkey controls (Windows=VCL, MacOS=TMS mCL, Android=D.P.F, iOS=TMS iCL and D.P.F). The new FireUI (multi-device form designer) is a great solution for styled components, but not for native components because it still requires the same component on the master pane to support all platforms. As you cannot mix them on the same form, it completely breaks the whole idea with Delphi.
A lot of developers would say that Delphi is the broken approach, see "Why FireMonkey is so fundamentally wrong in every aspect". However, the premise for this question is NOT to argue against Delphi, but to get the best results out of what it does offer.
The conclusion is then that for each form in your application you have to make a separate form for each target platform. This leads to these questions:
Challenge 1: How to include different form files in your project depending on your target platform?
Solution 1: include all of them, i.e. MainForm_IOS.pas, MainForm_Android.pas, MainForm_Win, MainForm_OSX.pas, and then use compiler directives inside the files, so only the content of one of the files is active. Disadvantage: a large application can have many forms (we have around 40), so we are talking about a large number of included files.
Solution 2: Do not include them in the project, but instead just place them in seperate folders. Then you can add the matching folder to the search path for each target platform. Disadvantage: They will not show up in the Project Manager, so it will slow down the workflow every time you need to find a file.
Solution 3: Create a project for each target platform. Disadvantage: Every time you add new units or change common project settings you have to (remember to) apply it to all projects.
Update: As suggested in the Malcom Groves video, placing all the business logic in a package will remove the disadvantage from Solution 3. So I consider solution 3 as the best approach.
Challenge 2: How to connect the different device forms to the (same) business logic?
Possible solution: Create a "Helper" class that contains all the code you would normally have in the form unit.
Update: This "Helper class" is actually what the MVVM calls a ViewModel. What I need seem to be a MVVM framework that can support the databinding. I have made another question about that.
Any input and suggestions about best practice are welcome.
For challenge 1:
You can conditionally link in your FireMonkey form resources depending on the compile target:
{$R *.Windows.fmx MSWINDOWS}
{$R *.Macintosh.fmx _MACOS}
etc.
This is excatly what the XE7 Multiview designer does, but I see nothing against using this mechanism to link whole form files conditionally in to your executable. Of course you might also want to ifdef the corresponding units in your project file.
For challenge 2: Just use some form of Model View Controler logic. So your platform dependant forms will talk to a platform independant controler.
I am working on some Oracle APEX Plugin development and wonder whether the following requirement is possible.
I basically would like to be able, via a plugin, create a form with say six page items, where two of those page items might be LOVs, another two are page items are text fields, where users have to enter values and the remaining two are display items only.
Based on this form requirement, I want to be able to upload/install this plugin within other Oracle Application Express apps/schemas, so when installed within other apps, this plugin is rendered within a region and the data is stored within a table in that schema, but using the form described above.
Can this be achieved building a plugin in Oracle APEX, and if so, how?
Create a stock application with the pages and regions that need to be replicated, export that, and import it into the other workspaces that need it. Then, when developing an application, copy the regions and/or pages as necessary from that stock application.
I want to use BIRT in an RCP application. I'll need to allow the user to enter parameter values and it's a requirement that the parameter entry UI must be customizable by users without compilation.
Is the only way to build a custom parameter JSP page and show it in an embedded browser? Or are there other ways to do this?
Besides the custom jsp, you can build your own SWT-UI that asks in your RCP for parameter values. You have to
parse the rptdesign file by BIRTS API to examine the parameter-types
prompt for example your custom dialog and
afterwards opening an embedded browser with the entered parameters (the parameters are appended to the URL of the ReportViewer), see also http://www.eclipse.org/birt/phoenix/deploy/viewerUsage.php#parameters
I had a doubt that can we have Checkbox in Dropdown in Oracle Forms?
There isn't a native control within Oracle Forms that allows a check box within a List Of Values (LOV)
However you may be able to use Plugable Java Components (PJC) to build a more appropriate control.
Here is a page that I have found very useful for help with PJC's