Create InfoWindow on the fly!

170 views
Skip to first unread message

redhuan d. oon

unread,
Mar 23, 2016, 6:48:13 PM3/23/16
to iDempiere
Now with just a single line of Table list, you can create a new InfoWindow on the fly! http://red1.org/adempiere/viewtopic.php?f=45&t=1821&p=8764#p8764

Collect the Aladdin Magic Plugin org.my.erp..jar at http://sourceforge.net/projects/red1/files/ModuleCreator and save hours and days of meddling with the AD and repetitive script and code.

(Besides that you can still create new Master-Detail, translated with GenerateModel and ModelFactory, all on the fly.)

redhuan d. oon

unread,
Mar 23, 2016, 6:59:15 PM3/23/16
to iDempiere
By the way, who wants PrintFormat (master-detail) on the fly?
And for InfoWindows, there is no report generator, where selected items can be output right away as in normal window. Who wants that on the fly?
And wouldn't that be nice, if InfoWindow can automatically allow data entry? <-- that will be hard to code according to Hiep LQ here with me in Bangkok, but who cares, I will build that wall, i mean door! :)

Antoni Ten Monrós

unread,
Mar 30, 2016, 4:13:14 AM3/30/16
to iDempiere
Redhuan, your Aladdin Magic Plugin looks better and better every version!

This sort of tooling is really appreciated.

I guess I'm mostly looking at what I need, but then again, isn't Open Source about scratching one's itches and then seeing if others can profit from it? Can I suggest some added functionality?

- I would love to have the data you input into the plugin to make do it's magic (in New Window and Model Generator) packed out to a separate 2Pack so it's backed up outside of the database (meaning that I can replace the database with a clean one and quickly import my work). What I currently do is 2Pack the PackOut data. 
- I would love to have Event Hander and CallOut Factory (plus corresponding IColumnCallOut implementing class) stubs added. After Model Factory, those are the most used components for me.

I understand that this is a tool for devs, in a relatively "beta" status, and that devs should know to go look at your forum for detailed instructions (there's a link to your forum in the readme after all), but it's so "magical" that it at least confused me at first. Adding coma separated lists instead of going to a master/detail UI is so different compared to what's usual in *dempiere that users are in for a shock if they already knew their way around *dempiere and just want to save themselves from writing boilerplate code. Maybe a set of instructions that goes step by step would really help here, as otherwise the UI is a little cryptic

redhuan d. oon

unread,
Mar 30, 2016, 4:23:08 AM3/30/16
to iDempiere

As i explained in my forum and wikis, the stubs you talked about are already there as described from its base sample version http://wiki.idempiere.org/en/Plugin:_Sample_Plugin.
Indeed, the idea is to place stubs so that saves developer time from guesswork and fiddling around, and just hit the ground running.
I also explained that its 2Pack ready. Take a look at Pack Out window. :)

redhuan d. oon

unread,
Mar 30, 2016, 4:49:37 AM3/30/16
to iDempiere
BTW, please vote for Trump, i mean me, at my wikis, at the bottom. Also at http://wiki.idempiere.org/en/Plugin:_Aladdin_Magic_Plugin when you checked the GenerateModelFactory it will also do the eventhandler javas and xmls. For GenerateModel it will do the X and I and M classes. Just refresh your source and see the magic.
Then drag your new windows into the New Menu, or the ready Pack Out window and hit the export 2pack button. Then take the ModuleCreator.zip and rename to 2Pack.zip and put under your MANIFEST folder and then Export Wizard, and you got it all so easy. :)

Antoni Ten Monrós

unread,
Mar 30, 2016, 5:16:28 AM3/30/16
to iDempiere
On Wednesday, 30 March 2016 15:23:08 UTC+7, redhuan d. oon wrote:


As i explained in my forum and wikis, the stubs you talked about are already there as described from its base sample version http://wiki.idempiere.org/en/Plugin:_Sample_Plugin
Indeed, the idea is to place stubs so that saves developer time from guesswork and fiddling around, and just hit the ground running.

I know that your sample plugin contains the stubs. I use it to avoid making so much boilerplate code. I want to generate them from this plugin for the tables I create ;)
 
I also explained that its 2Pack ready. Take a look at Pack Out window. :)

Again, the problem is that this plugin is so magical and does so much behind it's back, that  it surprises me a lot. It's good that it is ready to packout it's own data. 

On Wednesday, March 30, 2016 at 10:49:37 AM UTC+2, redhuan d. oon wrote:
BTW, please vote for Trump, i mean me, at my wikis, at the bottom. Also at http://wiki.idempiere.org/en/Plugin:_Aladdin_Magic_Plugin when you checked the GenerateModelFactory it will also do the eventhandler javas and xmls. For GenerateModel it will do the X and I and M classes. Just refresh your source and see the magic.
Then drag your new windows into the New Menu, or the ready Pack Out window and hit the export 2pack button. Then take the ModuleCreator.zip and rename to 2Pack.zip and put under your MANIFEST folder and then Export Wizard, and you got it all so easy. :)

I saw that later. I was confused by the fact that the class is called <tablename>DocEvent.java and the component definition is <tablename>DocEvent.xml. I thus expected it to work on the on complete events instead of on generic events.

Possible bug, you must have created the directory structure or it will throw file not found exceptions. This means you must have the OSGI-INF, META-INF, src/org/my/model, src/org/idempiere/component directories created before saving the model designer entry. I expected it to create the dirs as needed.

Feature request: do not hardcode the packages, let me input my chosen packages for the models and the components

Antoni Ten Monrós

unread,
Mar 30, 2016, 5:40:08 AM3/30/16
to iDempiere
Also, another "feature request" that I assume is already part of the plugin but that I'm still not knowledgeable enough to use: create detail tabs to existing windows. For example, let's assume that I want to create a subtab to the sales order tab in the sales order window. This tab will serve to "extend" the order without touching core data structures (for example, adding a FOB field that will be used in shipments). Again, I'm not talking about making a detail window for the master represented by my new tab, (I think I know how to do that already).

redhuan d. oon

unread,
Mar 30, 2016, 10:24:55 AM3/30/16
to iDempiere
Package and folder layout can be directed by the location name (in future release). I have to think about the InfoWindow next, which has no printout generator, unlike the standard windows. So i like to make a new tab to choose InfoWindow and then GeneratePrint which will put a print process in the Info Window that will print only the selected lines.
After that i am thinking of making a JasperReport on the fly for the master-detail.
Reply all
Reply to author
Forward
0 new messages