I have been experimenting with the new 2.2b feature of being able to include modules within solutions. This feature is amazing and it seems to be working very well.
One question. When a solution is assigned to be a module, is there a way to make it so the module will not appear in the solutions list?
on the client, it wil NOT appear as a solution. On developer it must appear otherwise you can’t edit the module.
modules sound great and im just reading the docs before giving them a go.
1 question which you might have thought of…
If you have a big existing solution with lots of functionality you’d like to keep and share through modules. Is there a way to set an exisiting solution up as a module without having to build it again from scratch?
1 challenge i see from the docs would be the old solution would not have a good naming convention to be used as a module so it might be better to start from scratch… ?? which is still ok and probably better than trying to take a short cut that will take longer
any thoughts
Yes, this is my problem too!
The only way to do this now is: export and import as..
than delete all the stuff you don’t need from there.
Still a lot of work.
thanks
does export/import as work ok for you if you importing back into the same repository in the same database?
i read in one of the chats on servoy talk that people had a few problems importing so i did not want to risk it as all our solutions are in one repository.. how about you?
Don’t use that at the moment.
Work alone on one repository.
I would like to add one thing to this and share my experiences with that technique:
I did the same, exported and imported as and started to delete things. This is where I have one feature request: would it be possible to multiple select and delete forms and relations? I found myself sitting there quite a while to delete tons of relations that were not needed.
But now for to the dangerous part, that might need a fix also:
I cleaned up the copy of my original solution a bit and tried to make it a module in my original solution. When I reloaded my solution, I got an error message saying that the solution could not be loaded. There was no specific error given and no entry in the log. And now? Now, I was lost. I was unable to access the solution settings to remove the module and did not know what I had to fix. For the time beeing, I can only recommend to everyone: BACKUP before you attach a module.
Would it be possible to have an option to remove a module if the solution loading fails? In that case, you can at least enter your solution.
The whole process of makeing modules of big solution leads me to a feature request I made here: Multiple developers; One solution - Classic Servoy - Servoy Community, which would be very handy for many occasions:
- when exporting a solution you get a dialog similar to the method editor’s form tree.
- the tree shows you what is “inside” that form (elements, methods and data).
- you can then check which forms or parts of that form (elements, methods and data) you want to be exported
- for the data part, a query editor would be very helpful, too. I enter a query for the data exported. Then you can even go on record level…
This would solve lots of potential problems:
- you can export the data you want (for example some of my data is solution relevant; I would like to be able to update that on a customer’s solution without touching the other data)
- you export only those forms and/or methods, that you really want to be updated, everything else is untouched (for example a customer’s own form)
The idea is simply to export only parts of a solution as a solution. Is something like this possible?
Thanks
Patrick
patrick:
The idea is simply to export only parts of a solution as a solution. Is something like this possible?Thanks
Patrick
I vote for this one too!
Yes, I vote for that also!
that will be pretty hard..
Because what does it touch? What globals what kind of relations what is all related through tabpanels ect ect.
Let us discuss this further, because I think this could really be a milestone…
I see the problem regarding global variables and methods. Maybe we can think of a way to deal with those… Relations are already somehow form-bound already, aren’t they? What other problems do you see?
jcompagner:
that will be pretty hard..
Because what does it touch? What globals what kind of relations what is all related through tabpanels ect ect.
Johan, we don’t expect that everyting will work right again, when we export and import.
If you only could do it with forms and there methods, THAT would allready be a huge timesaver!
but then i would do it the other way around…
Import form from solution
(so not export … but only import)
jcompagner:
but then i would do it the other way around…
Import form from solution
(so not export … but only import)
If you could not only select forms from a list but also global variables/-methods then you have all you/we need.
Ofcourse dependancies like used image media should be taking into consideration when importing.
Import form from solution
This sounds like a great enhancement! This would make development a whole lot easier. For me it’d be good enough at first if just all elements, their properties and the methods were kept in place. If this would also work inside the same solution then we could skip some earlier requested “duplicate form” enhancements.