Access Sugar Modules in 'Standalone' Manner

[blambert]

I am installing SugarCRM for use as the CRM portion of a reimplimentation of our corporate intranet. My (and my employer's) desire is to allow our users to customize their "workspaces" on this intranet, in order to allow them to arrange it to best suit their needs.

Although it's possible to write a standalone SOAP application to do this, I'd rather not have to take time away from my (or our developers') time spent on paying work in order to reimpliment work that the Sugar team has already done.

Using action=popup in the URL gets the *look* of it right, except that I then cannot actually use the module I'm trying to access. I'm not at all familiar with Sugar's internals, so I don't know how easy or difficult it would be to write a wrapper for this (I'm assuming that action=popup fails to profide a full metadata environment which the modules need, and that that would be where the fix would lie).

Of course, if I'm missing something important, and this is already available, I would love to be corrected.

[eggsurplus]

What we're planning on doing is just providing the direct link to the page they'd like to go to then it would just open Sugar to that area. We see our internal dashboard as just a starting point (a toolbox of sorts) while the actual work being done stays in all of the different systems.

[blambert]

I'm not sure what "open sugar to that area" exactly means; will it open that and only that module's interface? Or will it have the links/navigation bar/header as well? If so, that's exactly what I'm trying to avoid.

[eggsurplus]

Links headers etc.

What's the intended purpose of avoiding that?

[blambert]

The purpose in avoiding that is to allow users to manage their own "workspace" layout, and not have it dictated to them.

What I'm looking for is basically the "action=popup" appearance, but with the content being functional (which it apparently is not when you use that) so that it can be placed into an iframe element on a page.

[eggsurplus]

You could get this to work by creating your own MVC. Take a look in include/MVC for how it renders the page now. You'll then create your own so that it renders only the main page.