February 25, 2018
Should I Open Source Captivate Customizations?
Comments
(4)
February 25, 2018
Should I Open Source Captivate Customizations?
Guide 14 posts
Followers: 8 people
(4)

Hello Community,

In my previous blog I mentioned how I am using Captivate from a web developer’s point of view.  As I move more in this direction, focusing on mobile and measuring learning with Google Analytics, the tools are getting more complicated and exciting.

For example:

  • I am successfully getting PhoneGap plugins to work when you “publish for devices” to PhoneGap Build.
  • I am working on getting Firebase Authentication to function so a user can log in with Google, Facebook etc., so we can store custom variables on Google Firestore and retrieve them across multiple devices.
  • I will be offering these Captivate generated Apps via the app stores for download to mobile devices.
  • Updates to content will be automatic, because I am hosting mobile friendly web pages on Google Cloud Platform.  The are wrapped in Captivate with web objects.

Here are my questions:  If I publish all these customizations on Github with an open source license, would you as community members be interested in contributing to the project?  Can you help me maintain the github repo? Do you see any drawbacks to sharing this information?  Would you be interested in collaborating?

Thanks,

Brian

 

4 Comments
2018-02-23 05:38:36
2018-02-23 05:38:36

Hi Brian,

What you are doing sounds fascinating. I would definitely be interested in collaborating. Look forward to talking to you more about it.

-Steve Lewis

Like
(3)
>
slewis6337
's comment
2018-02-24 01:50:05
2018-02-24 01:50:05
>
slewis6337
's comment

Thanks for the reply Steve. Let’s talk soon. I still need weigh the pros and cons related to sharing everything. Looking forward to discussing it.

Brian

Like
>
b.rembrandt
's comment
2018-02-24 20:19:44
2018-02-24 20:19:44
>
b.rembrandt
's comment

Hi Brian,

Until you wrote about it in your blog I never thought about using Captivate for mobile web development. In linking mobile Captivate projects don’t you have the problem on IOS of the Captivate Splash screen appearing as you jump between mobile projects which makes the website not look as seamless? I know there is code you can add to the index.html file where you can get rid of the Splash screen but on IOS this will mess up the audio in the Captivate project. Just curious if you found a better solution without messing up the audio. In my dream scenario maybe the splash screen can be viewed for 1 second and then a JavaScript command can make the project continue on it’s own? If you don’t use audio then of course you won’t have a problem.

What do you think Brian?

-Steve

Like
>
slewis6337
's comment
2018-02-24 20:25:20
2018-02-24 20:25:20
>
slewis6337
's comment

Hey Steve,

I did add the code that people are talking about here to autoplay the project but didn’t have any audio issues. That was a while ago, so I should probably test that again and try to recreate the audio issue, but yes, that player button needs to not show up on IOS.

Like
Add Comment