Forge - Separate the "Component" from the "Demo"

By Justin James on 3 Aug

The Demos in Forge projects take up a TON of SUs/AOs. But if you delete the demos after installing, the next time you upgrade the component you get the demo code again.

Solution: have the component author upload a demo (OAP, OML, or OSP) separately from the component itself (OAP, OML, OSP, or XIF). Then allow the Forge user a choice of "Download Component Only" or "Download Component + Demo".

To make this better, add a "Project" that is similar to an OSP, but can contain Applications as well. That way, the Demo can be a separate Application from the Component, and they can be delivered together in one download. A level above "Application" has been requested a few times already.

J.Ja

Must have

J.7 Aug

Agreed.


I would like to keep the "external" components untocuhed, so you can upgared far more easily (instead of force installs etc)

so, yes, demo-stuff should be somewhere else

With this discussion (link) about having a separate Demo component for the SortRecordList component, it would be very helpful if OutSystems would implement the functionality to have in the a component:

1) one download for the component itself,

2) and a second download only for a demo on how to use the component.

Cheers,

Tiago Bernardo



Merged from 'In the Forge, for a Component, allow for a separate download only for a Demo of the component' (idea created on 2017-08-25 15:23:28 by Tiago Bernardo), on 2017-08-26 13:37:18 by Justin James
J.26 Aug

I agree, not sure how it should be implemented correctly, but we really need components as is and some demo-site




Merged from 'In the Forge, for a Component, allow for a separate download only for a Demo of the component' (idea created on 2017-08-25 15:23:28 by Tiago Bernardo), on 2017-08-26 13:37:18 by Justin James