I’m trying to figure out how to code Google App scripts from a mobile device and I’ve narrowed in on some solutions, but have not quite found one that works.
The first step is to find a way to code app scripts from an online editor. I already do online coding through the iOS app Juno, which has an editor for Jupyter notebooks stored in the cloud on CoCalc.
Unfortunately, Jupyter notebooks do not natively code App scripts Java-like programming. So, i’d have to figure out how to deploy scripts from a python environment.
Google does have documentation on deploying app scripts with python, but require Clasp and other installs, which I’ve yet to figure out how to install in a Jupyter notebook.
I wish I could set up a cloud doc to share here, but I don’t have even the beginning elements of attempt yet. So, I hope this question is enough for someone to give me direction.
Thanks so much.
Related
I am deploying a code over sandbox from eclipse, I'm new to salesforce development.
what is the diff between building workspace and uploading cartridges in eclipse.
I appreciate all the help that i can get, thanks in advance
There are no "cartidges" in Salesforce documentation. Are you sure you're developing salesforce code? Maybe you're working on some Java integration? Or maybe you mean packages? zip files with package.xml and source code?
And Eclipse development model is outdated now, all the cool kids moved on to sfdx + visual studio code. What you're doing still works (it uses "metadata api") but you're consciously using old tools, depriving yourself from newer, faster toys. You can read more about metadata api style of deployments in https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_intro.htm
Now... If you ask about "why do I bother with doing deployments if in sandbox I can just edit the class/trigger directly and save"... well - you can't in production. You can't just go and edit code straight on production, even in the setup the button simply isn't there. It has to be a deployable package, it has to run unit tests during deploy (they need to pass, the code coverage has to be at least 75%). So you make a package when you're really ready to go to prod
I have a problem installing and running npwd script for fivem which is built on react.
I have searched on google but I haven't understood yet. I really want someone who can tutor me this part with screenshots or video.
I am rather new to several of the technologies involved here but here is the scenario:
I have a Windows PC at home, a PC laptop and an iPad Pro. I have a React project that I am working on and would like to be able to do so from anywhere. I dont have any kind of VPN solution available, and a usb stick is mostly out for the iPad, so I was wanting to use Google Drive (or as a last resort iCloud) to store the project. Also I do not wish to use github for a number of reasons.
Can anyone outline the best way to work on a React project (With NodeJS) in a cloud based storage and further how to run / deploy it from the iPad station? Thank you!
I Think you have to use a git repository (github, gitlab or bitbucket works great), and all your machines should have the tools pre-installed (node, code editor).
If you want to code without any tool, I recommend https://codesandbox.io, it works great with small/medium projects. One of it's downside is that your projects will be public on the internet.
This morning, I tried to get a coop student up and running on an older version of the Google App Engine for Eclipse plugin.
The following website and all related links appear to have been wiped off the face of the earth:
https://developers.google.com/eclipse/
Is this just down at the moment?
Is it possible to get older versions of the plugin?
While it is correct that the Google Plugin for Eclipse has been removed from Google's documentation, it is still available.
To install it, in Eclipse Neon, click "Install new Software" and add in this URL.
http://dl.google.com/eclipse/plugin/4.6
Next, click through the dialogues to allow the installation, and restart Eclipse.
While Google has chosen to stop supporting this, I personally feel that the new Cloud Tools for Eclipse plugin is just not ready. Also, in the early days, JDO was what many people were using on top of the data layer, and since GAE has been around for 10+ years, many of us have a lot of infrastructure built on top of this that is costly to change. While it's still possible, in theory, to run the DataNucleus enhancer manually, it's a huge pain that requires in-depth knowledge of the inner workings of GAE and DataNucleus and knowledge of which dependencies go together. It may have been well-documented in the past, but today it is not.
But be warned, one of our engineers recently lost the ability to deploy the project to Google App Engine using the GPE and was forced to use the gcloud tool, which doesn't seem to have sensible defaults, like deploying to a non-default version and instead will deploy straight to default, well, by default. So we're writing a script around that command that will pass in --no-promote so it doesn't immediately start migrating traffic... Visit the gcloud reference for app deploy for more details. Good luck!
For more information on the install process, please see How to install Google Plugin for Eclipse on mkyong.com.
GPE is indeed gone. It was not up to date and many parts of it no longer functioned. Over the coming year, even more core functionality was going to break. We wouldn't be doing anyone any favors by letting them invest their time in a broken tool. This is doubly true for new users such as your students. There are some old GPE snapshots floating around here and there, but those don't really work with GCP in 2018.
That official documentation is most likely gone for good, the plugin was deprecated in favour of the Google Cloud Tools for Eclipse. From Migrating from the Google Plugin for Eclipse:
The Google Plugin for Eclipse is deprecated and will not be supported
beyond Eclipse 4.6 (Neon). It will be removed in early 2018.
This document describes how to migrate a project that uses the Google
Plugin for Eclipse to the supported tooling.
You can check the snapshots of the docs on the Wayback Machine, and maybe still find the matching code repositories, if they haven't been removed as well.
But it's probably a good idea to switch to the supported tools sooner than later, especially since they're just getting started.
Related: Migrating GAE project to Java 8 - get XML validation error after adding runtime property to appengine-web.xml
Does Google still support SL4A for Android.
I have created an apk file for SL4A which is A6 using the old source code, could anyone kindly let me know if the source code for SL4A is available for the latest Android version(A16>).
Google never actually supported SL4A. The original developer, Damon Kohler, worked at Google, but SL4A was his own project.
I got the impression that Google weren't thrilled about SL4A on Android, for security, stability and performance reasons, but had no problem with Kohler working on it independently. I'm reading between the lines here though, so could be wrong.
The latest version of SL4A should work on more recent Android versions; you just wont have support for new Android API features.
There was at least one other lead maintainer after Kohler, but development was intermittent for a long time, and ground to a complete halt years ago. I know that they struggled to find Java developers that cared about Python on Android.
The SL4A Google Group still exists. You may still find some support there.