Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add HTML editor #27

Open
ron064 opened this issue Feb 16, 2014 · 6 comments
Open

Add HTML editor #27

ron064 opened this issue Feb 16, 2014 · 6 comments

Comments

@ron064
Copy link

ron064 commented Feb 16, 2014

Many projects need HTML config file, so I think it should be included in the project (and imported/exported to GitHub when possible.)
It can be base for many improvements like auto-generation of config files(maybe with JS and C part as well), hosting the config file on Pebble server, or embed it into the JS file.
I'm guess there should be some good open source editor that is in similar enough environment to be easier to integrate.

@Katharine
Copy link
Contributor

The ordering on this issue is wrong – first a destination needs to be decided, then we can have an editor.

@ron064
Copy link
Author

ron064 commented Feb 16, 2014

Most Pebble projects on GitHub have html file, even if a user wants to import a project, update some things and test it, the html editor part is missing.
Default destination can be hosting on some pebble server. the traffic of config files is too low to bother anyone.

@unwiredben
Copy link

I'm personally fine using GitHub's editor for those files works fine. I like having CloudPebble just focused on the parts that go directly on the watch/phone. As long as it doesn't touch my "gh-pages" branch or the files in the root/other folders, I'm happy.

@ron064
Copy link
Author

ron064 commented Oct 17, 2015

The support for HTML keep popping out:
#215, #35
Now that Slate is the official pebble config method, I'd expect that CloudPebble will support it properly.
For example the video made for Slate shows as if a Linux development environment is required to develop config page, and this is exactly the opposite of what cloudPebble is suppose to be helpful with.
Adding automatic hosting for slate files made in CloudPebble is also very logical.

Personally I prefer full support for HTML files including the import/export, But if slate is the way to go, it is totally acceptable, It is even possible to add wizard that add slate fields by type.

@Katharine
Copy link
Contributor

Slate is not officially supported.

@ron064
Copy link
Author

ron064 commented Oct 18, 2015

Well Slate is part of pebble official documentation:
http://developer.getpebble.com/guides/pebble-apps/pebblekit-js/app-configuration/#building-beautiful-configuration-pages

The fact is that making configuration page for pebble application is very complicated task that require knowledge in several fields. The increased complexity reduces the quality of configuration pages that many independent developers can make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants