Parse / Angular web app - how to protect source - angularjs

I am developing an web app using Parse.com and AngularJS, ie in a two tier architecture.
My question is, how would I protect the source? Wouldn't anyone could completely copied my static files and clone the site?
Thanks guys

That is basically what you have to deal with when leveraging client-side javascript. You can certainly use an obfuscating minifier for your final downloadable file to make trying to reverse engineer it a little more difficult, but still there is no getting around the fact that you have a working open source file out there.

Related

Gulp unbuild from salesforce org

I am actually developping an application in a salesforce environment using MavensMate and Sublime Text 3, built with Gulp, in AngularJS from Yeoman.
I managed to connect my built application to salesforce thanks to CodeScience gulp angular tutorial on youtube, and can now develop my application locally, test it, build it, and finally send it to our org.
Right now i'm asking myself a question:
How can another person unbuild the metadata and static resources that I have built with Gulp after retrieving them using MavensMate ?
Isn't there any way to do it just so that we can work on different stuff on the project at the same time ?
That would be truely awesome, I haven't found a way to do it yet but will keep this post updated if I do.
Thanks for any help you might be able to provide.
I am the Director of Engineering at CodeScience. I'm glad you've had success with the Yeoman generator for our local SFDC UI stack. We use it a great deal internally to rapidly build SPAs in Salesforce. If I understand your question correctly, you are asking how to share code from a single or multiple SPAs (single page apps) with another developer. A better solution than sharing code through the static resource would be to use a version control solution like Git and a repository host like GitHub. We all work of our own branches (managed by push/pull requests) and branching in general works very well with our local build stack for rapid prototyping. Let me know if I, our or team can help you any further.
the answer is not to unbuild the static resource, but to distribute the source code to the other developers so they can build a new minified resource.

AngularJS with Durandal?

Is it possible to run AngularJS in a Durandal project? We are using Durandal now but want to move to AngularJS while still keep the site operational. Is it even a good idea to attempt this?
Any suggestion would be greatly appreciated.
You could run them side-by-side, but then you would just have two separate SPAs hosted on the same site. The doesn't seem like a good upgrade strategy to me. I think you would be better off to fully develop the new version and then replace the site altogether.
I would also advise that you wait for the release of AngularJS 2.0 (if possible). Rob Eisenberg has announced that he is currently working with the AngularJS team to provide core changes and plugins that will make Angular 2.0 more familiar to developers with Durandal experience, as well as to provide a migration path from Durandal to Angular 2.0.
The other answer isn't exactly correct. I have an example that proves it wrong.
Durandal is a module loader that can load any view / view model pair. If you choose to load an angular application and leave out the router portion it works just fine. It really isn't that difficult to get it set up.
Wrap your Angular.js application initialization code in an AMD module (view model) with a matching view and it just works.

Multiple apps with a shared db, what should I use to make it?

I am pretty new to programming and have so far only learnt HTML, CSS and a little bit of javascript and Jquery. What I would like to do is make a website which has a variety of apps (both web and mobile). All of these apps would need to share a DB with the website, not only for login but also various forms of data each app deals with.
A friend suggested to me that I should be using AngularJS with Firebase and just make one big app with all the apps and website included in that, but I would rather a more flexible option so the app doesn't become huge. So I would rather have a website which links to each app but also has access to the data.
So I have a few questions regarding this:
1 - What languages would I best to use to make this?
2 - If I went with angular and firebase for each app would I be able to use a language like php or rails to also tap into that db?
3 - What would be the easiest way to achieve this?
Thanks,
Marty
Yes , I'm making a big app like you and I've searched a lot and the easiest way is to use angular and php
although u can do better than this.
For example for your backend , you can use NODE.js , but its a matter of your knowledge and timing and how much energy you want to spare and consume.(But if you use php the right way , its very lightwaight/simple/fully supported/well known/free)
Angular is very wasy to learn and fast to use , and also PHP , because both od them have been tested and fully supported with lots of communities(thats very important)
for learning Angular Go to egghead.com , you can find lots of interesting angular video learning for free , And also you can simply search the youtube

Using Backbone or similar framework with Silverstripe

I am replicating an existing application in Silverstripe (PHP framework). The application has a lot of jQuery already and while its organised well at the moment it could get out of control as I grow it past its current point.
Having spent most of my development experience in PHP/MySQL, I have little experience in js front-end frameworks and would not likely use a framework to manage data manipulation with the server from the get go. Really I'm just looking for a suitable solution to organise and manage the js in the short term and something I can eventually evolve (with more experience under my belt) to a point I can manage all frontend logic with.
Is backbone the way to go? Any other advice?
I've been using SilverStripe framework with EmberJS and EmberData with great success. Ember connects to SilverStripe with a RESTful API module
But you can very well use any JS framework and mkae your own SS controller of find other SS modules to help http://addons.silverstripe.org/

JSPs for a simple Project Reporting Web App?

I'm about to start developing a simple reporting tool for tasks in international projects. In a nutshell: using the tool, a project is created, defining team members, tasks, and work packages. Team members will be asked to periodically submit reports on the work they've done (related to tasks and/or work packages). These reports will be stored and accessed trough the tool.
I'll use Google App Engine (client requirement) and its datastore (using JDO). But I want to ask you for advice on the frontend part: JSP looks pretty messy for non Java developers... any other idea???
Thanks!!!
Seems like at the moment it's either java or python. However, you may want to look at Grails. GSPs might looks a little less 'messy'. I'm suggesting Grails based on your description of the project, that I suspect will turn out anything but simple later on. You might end up being glad for the mix of constraints and flexibility that Grails will afford.
JSP doesn't need to be any messier than other similar HTML presentation frameworks, it really comes down to implementation. That being said, it is old Java technology which means it's not being kept up to date, and finding a good single source of documentation is difficult.
If you don't want to use JSP, there are other frameworks you can use, you just need to make sure they're compatible with Google App Engine.
The new kid on the block is the Play framework, and that's a Java MVC framework similar to Ruby on Rails. You can find a tutorial here: http://viralpatel.net/blogs/first-play-framework-gae-siena-application-tutorial-example/
If you're going to use Spring, check out this question: Alternatives to JSP for Spring MVC view layer
For a front end developer, if the code is separated correctly, you won't have to know anything about Java since there shouldn't be any Java mixed in with the HTML. If that's your only worry, then I would just go with JSP to keep things simple unless the team has experience with another technology.

Resources