The mechanics of converting a solution to modules

Classic Servoy
1

I’ve just finished reading through the Servoy_module_development PDF, various posts on modules and looking at the new 2.2 beta. Fantastic new feature. You guys are fabulous!

If it’s there, then I missed a discussion on the mechanics of converting an existing solution to modules, what are the does and don’ts. Implied in some of the posts it seems to require exporting, deleting forms, methods, relationships (value lists?), not sure, then doing similar on the export and then importing.

Sounds both dangerous and a mountain of work. Would appreciate some commentary from those who have attempted the transition and existing solution to modules.

Kind regards,

2

ditto for Morleys request

at the moment we are in 2 minds

should we convert our main solution which we have spent over a year to put together.

or should we start from scratch and avoid all the renaming of forms, relationships etc which sounds like a lot of work.

the latest releases beta versions look fantastic and it looks like there are also many more efficient ways of doing things than in earlier versions of servoy BUT its not always obvious how to make the most of new enhancemets…

it would be great if the CRM or a new solution could be updated with each new beta release or full verions showing the most efficient and effective way of using the latest enhancements.

many thanks

3

We’re building a new CRM example solution that is based in modules. Hopefully that will help.

BOB’S PERSONAL OPINION: Unless you’re going to use portions of your main solution in other solutions - then don’t bother making them modules.

Modules are great for things you’re going to use over and over again (user management, value list management, etc).

Hope this helps.

4

bcusick:
BOB’S PERSONAL OPINION: Unless you’re going to use portions of your main solution in other solutions - then don’t bother making them modules.

Modules are great for things you’re going to use over and over again (user management, value list management, etc).

I suspect modules would also be very useful if multiple individuals work on separate segments of code simultaneously.

Before we embark on retrofitting an existing solution into modules and making a mess of existing code, I’d like to see a list of do’s and don’ts.

Has anyone already done it? What worked, what didn’t, what were the surprises?

5

We plan to make most of our main solution available in modules and also use modules so that more than one developer can work on it at one time.

ours is a big solution with hundreds of forms so we’ve got a big job to do which ever way we do it. im wondering if the improvements in servoy over the last year have resulted in many more efficient / effective ways of doing things than existed 12 months ago. So over and above the need to rename everything to the recommended module format are there other reasons that we might be better off starting from scratch.

Bob, the new crm that is being put together, do you know if it will use all the latest servoy enhancements besides modules.. is it being built from scratch or is the old crm being adapted to work with modules?

many thanks

it would nice to be to use the crm as a reference knowing that the methods used are the most simple to get the job done. for example when i first looked at the custom navigation bar in the crm i was amazed by the complexity of code and number of methods required to make this work. are there more simple ways of producing that type navigation bar in the latest versions of servoy?

6

The CRM is being re-built from scratch. We have a new Unified Data Model (UDM) that we will also release as the recommended schema for contact management stuff - so people can build inter-operable modules.

Regarding the amount of code for the menu bar: in general - the “easier” it looks, the harder it is to program. I haven’t looked at that code in a long time, but I know that there were lots of changing of buttons, updating of HTML, etc. The best way to see if something will work better - is to.. ummm… work on it. :D

7

many thanks Bob.. the new CRM sounds like it will answer a lot of questions. :D

without holding you to it (honest) any idea of ETA for the new CRM

we have been trying a lot of new things with servoy an not just sitting around waiting for someone else to do the work but being new to this kind of tool and not filmaker im aware that what ever solutions im coming up with are probably not as simple / elegant as someone who really knows what they are doing with servoy so rather than contiually reinvent the wheel its nice to know theres somewhere we can look to make sure we are on track with the way we using developer thanks again for developing the module system:D

8

ETA: When it’s done. :D

Seriously, I’m working my A** off on it. It will have some really interesting features: a “list mangaement” module to handle value lists (with hard coded values); a single data-driven find module that will work across all files and be able to store finds (even finds with multiple fieds and requests), etc. etc.

I’m still working out some technical issues on how to approach certain things (both module-wise as well as trying to determine the most flexible, data-driven way to handle common tasks).

I’ll be sure to post a “preview” of it when it’s closer.

Ta for your kind comments.