Is it possible to use Brackets to edit CSS locally and live preview it in online server? - brackets

This is something I used to do when working with (MacRabbit) Espresso app. Writing local CSS and seeing how changes work in the online website in real-time (Espresso calls it "Overrides"). It was especially useful when working with WordPress.
Is it possible to do it (or something similar) in Brackets?

Related

Electron - How to save information?

I've recently learned about Electron, and given I have a rather well amount of knowledge of HTML, CSS, and Javascript, I decided to take a look at it. When I normally make web applications I use MySQL for storing user data mostly through PHP. I noticed Electron doesn't support PHP files like a normal browser does, so I'm curious as to what the best method for saving user data actually is. I read Electron allows for interaction of files like a real application does unlike web apps, but I feel like there's another way. Is there any "standard" when it comes to stuff like this?
As I mentioned in the comment, you could use a NoSQL solution (or as Paulo Galdo Sandoval mentioned, the HTML5 storage methods)
I googled and found these resources:
https://medium.com/#ccnokes/how-to-store-user-data-in-electron-3ba6bf66bc1e#.c45jm3tas
https://github.com/jviotti/electron-json-storage

Is there a way to overwrite an html file dynamically in a phone gap project?

So, my cohorts and I have been doing some development with Phonegap +jQueryMobile for an application we've been planning to rollout. We switched off doing this natively for iOS and Android, since its mostly html anyway, and phone gap seemed like a great way to do this without having to write a whole bunch of platform specific code (although we're more or less newbs when it comes to this type of development.)
Previously, all the html, javascript, etc, was going to be housed in the app itself. For the most part, this seemed to work for us, and we advanced our design/testing/etc accordingly. However, things have changed in our approach. For each of our customers (once they go through a log-in/authentication) has a 'starting' html file (essentially 'their' index.html) that is specific to said customer. This was different from before where everyone had the same files.
Now I've played around with storing certain scripts on the web server to try and off-set opening the html running on the server, but it's not really that useful when trying to integrate some of the functionality like the camera or some of the other plugins we're trying to use. It's essentially a form-based application, so this is the ONLY file that will change from customer to customer. Also, this will not be something that changes frequently. For the most part, it will be setup for a customer ONCE AND ONLY ONCE, and it truly is unlikely to change.
Is there a way to more or less pull down this html file from a web server to replace the one that is stored internally in the app, and then load that version? Would doing something like that (if its even possible) violate Apple's or Google's App guidelines? Or is what I'm describing not even possible in the framework?
The only other thing I can think of would be to change the stored 'index.html' file to not load any of the form itself, but rather make ajax (or equivalent) calls to do so, but I've been told by our developer working the web design side of things that it would be a huge pain.
Any insight/knowledge would be appreciated.
If you really need to do this (I don't quite understand why), I think your best bet is to go the AJAX route. At least Apple does not look kindly on applications that update themselves without going through the App Store submission process.
You can do the same index.html for all and a script config.js that be the responsible of load/unload resources/html of each user at app start.
All you need to do then is save that config JSON values in localstorage and go.

Extend Rails app with standard content pages

I developed an App with Rails 3.2
We realized that we may end up having many 'standard' content pages, mainly text documenting the application itself. Nothing the application users will be playing with.
Is there an extension (plugin, gem) I could use to add page to my app like we would normally do on a standard CMS?
I want to be able to delegate the addition/nodfication of content to the admin rather than coding it in HTML.
We had a similar problem with our knowledge base, and chose to use nanoc for it.
This gives us something similar to developer.github.com in term of end-user. And the code is written in markdown (developer.github.com is open source).
This way, all our documentation is written in markdown in static files.
Support people can write them without having to know about programming. With the GitHub Mac App, they can very easily push and pull from a repository.

client side search engine

I would like to get some suggestions on my current headache. I have been researching on search engine for client side browser. I am building custom glossary project. The idea of the search engine will be used for searching terms, keywords, or definitions.
Here are my requirements for this project
no server side support. Total client side
only for intranet
build for browser that is not HTML5
thousands of terms
Any suggestions or ideas on how to build the client-side only search engine?
Thanks in advance
Barring a full desktop app, I don't see how you can do this without a server. Distribute the HTML files as a .ZIP file and browse them locally? If yes, you probably need to make a honking big page with the whole database inside it (as Javascript data structures) and search that way. Shouldn't be too hard with regexes etcetera, but I doubt whether you'll end up with a fun user experience...
Really curious why a simple server-side solution won't work :-)

Web page looking bad after uploading on server

I'd create a web page with jquery and css3 and is looking good on my computer but after upload on server is awful in IE. In any other browser everything is good.
Any suggestion why is that?
This sounds like your css is not "compatible" to IE. Every brother is interpreting css a little bit different.

Resources