2
 Followers
6
 Likes

Immeadiate CSS deployer

1CP
On our radar

Hi all,

When you are project face that you develop look and feel your application and part of the is styling things with CSS.  

Using 1-Click Publish is enough still too slow when you want to see your changes on action fast. If you are not able to see that fast, then it disturbs your concentration. 

It would be nice if the OS would provide short cut CSS deployments for Web Designer's to update CSS on OS server directly from Service Studio without 1. Click deployment.




Created on 26 Nov 2018
Comments (7)

Changed the category to 1CP


Hi,

It would indeed be nice if OutSystems can create something for this. Same for JavaScript development.

A work-around I often use is saving the files to local disk and then use the auto-responder feature of Fiddler to return my local version of the file to the browser. That way you can developer script and css quickly without the need of publising often.

It does mean you work outside of Service Studio of course.

I like to create JavaScript else where as that has logic. I have JavaScript project that created with nodejs / npm / gulp / mocha / browserfy to develop my JavaScript logic. I just created another idea so the integrations would be easier. At JS is also important to test the logic if it get's complex. 

https://www.outsystems.com/ideas/5960/possibility-import-javascript-files-from-remote-repository

Changed the status to
On our radar


Hi Sampsa,

Thank you for your idea.

We are always looking for ways to improve the 1CP process so that we can accelerate the development  team even more. I will mark this idea as under our radar to see further comment and evaluate it for future improvements.

Best regards

Merged this idea with 'Faster way to test UI changes' (created on 03 Oct 2018 20:13:28 by Munjal Subodh)

Publishing a module takes too long (especially if you have to do merge with other people's code) just to test simple UI changes. 

A probable solution would be to do branching (at least to avoid the merging part).

Maybe a better solution might be for the system to detect what changes were made and only publish those changes. For example if only CSS changes were made, we could just update the CSS instead of doing the full publish. 



This comment was:
- originally posted on idea 'Faster way to test UI changes' (created on 03 Oct 2018 by Munjal Subodh)
- merged to idea 'Immeadiate CSS deployer' on 11 Jun 2019 19:03:52 by Tiago Leão

Changed the category to 1CP




This comment was:
- originally posted on idea 'Faster way to test UI changes' (created on 03 Oct 2018 by Munjal Subodh)
- merged to idea 'Immeadiate CSS deployer' on 11 Jun 2019 19:03:52 by Tiago Leão
views
398
Followers
2