I edited some sample code in the web ide and I do not see a way to read/edit my program and the included *.h file.
I installed the desktop ide thinking that would get me a local copy to customize but can’t get to my program.
I am logged in and can see my device in the console but I do not see how to access the program.
I like the Photon but am having trouble with navigating the ide. Any documents better than the I need produced by particle would be helpfully.
Unfortunately, there currently is no way to access your Web IDE project from anywhere other than the Web IDE. If you want to edit the files/project locally, you’ll have to copy them over I’m afraid. That said, once you’ve done that, you’re free to use any sort of versioning system you like, be it github or dropbox for example.
You can edit .h and .cpp files in the Web IDE, but you’ll manually have to copy them into your project by using the little ‘+’ icon in the top right corner of the screen.
I’m aware that either of these is less than ideal, and it’s something I’ve been mentioning to Particle for a bit. It’s definitely on the backlog, but making the user project accessible from an API is a bit of a bigger project than you’d think on first glance (I miscalculated that one as well). With that in mind, some more pressing issues and/or more useful project have been prioritized. Let’s hope they’ll be able to work this out in the future though. For now, it’ll have to be a copy&paste though.
Thank you. Now I can stop banging my head on the desk.
The ide file system is my only complaint so far. I was hopping for something more like Arduino.
I need to see what is in [ #include “DS18.h”] this file is in the example I modded and it would be helpfull to see what is in it.
That’s doable in the Web IDE as well, though you can only look, and not change it, without copying the files over manually.
Ok, that helps a lot. Looks like there are several layers to the one file that showed on the first page. This is making it harder to see what is going on.
Not sure what layers you’re referring to. The library consist of a
.cpp, and two example files. That’s all there is to see for that given library.
Also, if you click at the GitHub icon just below the library name (DS18B20) you’ll find the GitHub repo the library is based on.
You can copy the library from there or in Desktop IDE you have an option to do that via the Library Manager too.
In the example I used the program had one #.h included and after opening that I see two more files.
If only we could see said example, then we wouldn’t have to guess as to what you could possible be seeing
The ino file is, ds18x20.ino, it includes ,onewire 2.0.1
The onewire file includes, ds18.h and .cpp and onewire.h and cop.
It is hard to follow what is going on due to all the compatibility included.
I might be better off going back to some Arduino sketch that uses the onewire library instead
Still a bit vague to see exactly what you’re seeing. If you could send us a share-link, we get the exact same setup as you’ve got.
I absolutely hate this ide.
So I opened the included library and now don’t see how to get back to the nodded program on my device.
The hate is real.
I’m using my phone so I hope I copied it correctly.
The reason I wanted to see the included file info was to try and understand why the output I am getting is not what I expected.
I get , light level, light level, temp(sensor1), light level, temp(sensor2), light level, light level, temp(sensor1), ect
All your code should be in the “code” tab.
Though the IDE definitely isn’t perfect, hating it goes a bit far if you ask me. It’s quite capable of doing most, if not all task that one could require it to do.
There’s always the desktop IDE for more flexibility. Heck, you could use any editor you like, and compile your files using the CLI. Plenty of options.
You are correct, I meant to say frustrated.
I see, you chose to go for a library that doesn’t expose its sources the way it’s meant to be.
With a library that does, you have some more options see what’s going on.
That’s also one of the reasons why @Moors7 has refered you to the
DS18B20 library that does try to adhere to the rules of contributing libraries as close as possible.
If you might ask, why do we have (at least) four libraries for one type of sensor with most of them not making things easy for the user, then I’m absolutely with your, but Particle can’t prevent people from contributing libraries or force them to keep up maintaining them properly.