Child objects within modules #532
Replies: 3 comments
-
Posted at 2016-02-17 by @gfwilliams I'd put them both in one module:
In fact, in a lot of cases you don't actually need access to the If you're doing this, please can you make your API the same as the existing filesystem - specifically the existing ... IMO it'd be ideal if someone could just compile all the existing FAT filesystem code into the ESP8266 port, and then it could even work with external SD cards if needed. While not perfect for flash memory, I'm sure it'd be good enough. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-02-17 by Wilberforce Thanks Gordon. I'm intending to have a decent looking ui that is self contained, so that you can connect to the esp8266 as an access point, and then select a wifi ssid, and enter a password to join the network. From there the front end (bootstrap etc) can be delivered via cdn. I like the idea of having a self contained web server, and with the large flash size on the esp8266, local resources can be stored. I'll post code once I've got it more refined. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2016-02-17 by @gfwilliams That'd be great to see when you get it done! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2016-02-16 by Wilberforce
I wondering the best way to handle this, and the best way to set modules up for child and parent relationships.
Do we have a single module that contains both the FileSystem and File objects?
I want file to have a reference to it's parent, and have it's own methods.
Should this be set up as two modules, where Filesystem is a list of File objects?
I've not seen any modules that contain two or related classes.
Beta Was this translation helpful? Give feedback.
All reactions