(Pie in the Sky alert - manage expectations may never happen!!!)
note: this is only for very advanced users/developers... as you will need to respect quite alot of 'unwritten rules' to do with parameters etc ... almost certainly you would need to know the Axoloti code base reasonably well
I was thinking last night, about some new objects that Id like to create,
but I realised quite quickly there were quite alot of parameters, and the current way to display parameters would just make the thing unbearable to use.
Now.. we already know we want to have more customisation options, and also presentation options. Which would be cool, and for many users very useful and enough.
BUT it will still have a fundamental limitation, that it will be limited by UI types defined in the axoloti java UI.
so i was wondering how about allowing objects to use custom java classes?
i.e. not only do you ship an axo, but also as jar which contains a java class that has custom java code.
Initially I thought about just for displaying the object, but later realised it could potentially also have custom generating code... (assuming we can get the 'right interface')
It seems not too tricky to actually implement:
objects have a class reference, and a jar reference, when the object is created the relevant class its loaded.
if its doesn't have a class reference the current implementation is used.
Note: Id considered a custom class loader and embedding the class into the axo file, but this could make the axo file pretty unwieldy
it will mean ensuring the entry points for display etc, are well defined (if its not already true) , but thats no bad thing
of course, there could be issues with versioning etc... but given the small number of users using this, i think its manageable.
What do you think? is custom java code a really bad direction?