0
0
mirror of https://github.com/Doodle3D/doodle3d-firmware.git synced 2024-09-16 16:50:07 +02:00

Add project outline; minor changes.

Wouter R 2013-04-25 11:47:10 +02:00
parent 659b066020
commit 42d5f9c585
3 changed files with 39 additions and 7 deletions

21
Home.md

@ -2,14 +2,21 @@
This contains notes previously kept in several local files. Keeping notes here is more maintainable and integrates nicely with the issue tracker as well as the repository.
## Notes so far
## Milestones
[Building OpenWRT](BuildOpenwrt)
A number of milestones have been created in the issue tracker. Bitbucket sorts them alphanumerically (kind of) so internal milestones are prefixed with '0_', release versions with higher numbers and anything else without any prefix. 'IP' stands for 'Internal Progress'.
[analyzing uhttpd crashes](UhttpdCrash)
- (0_IP_1) First development milestone, implementation of basic supporting functionality.
- (0_IP_2) Second development milestone, same as 0_IP_1 but in a larger scope.
- (0_IP_n) Nth development milestone, at some point one has to be defined at which all core functionality is present and working reasonably well.
- (1.0) First release version.
- (Later) Indeterminate, but nonetheless wirthwhile implementing at some point.
[outline for self-update functionality](SelfUpdater)
## Pages on this wiki
[partial original wiki content](OriginalContent)
[Miscelanneous notes](MiscNotes)
[Building OpenWRT](BuildOpenwrt)
[analyzing uhttpd crashes](UhttpdCrash)
[outline for self-update functionality](SelfUpdater)
[partial original wiki content](OriginalContent)
[Miscelanneous notes](MiscNotes)
[An outline of the project structure](ProjectOutline)

23
ProjectOutline.md Normal file

@ -0,0 +1,23 @@
# Outline of the Wifibox project
Consider this a sketch, including some ideas which might never end up in the final application.
* Printer driver interface
Perhaps using the idea of printer/protocol/firmware families can reduce code duplication
* _for each printer_: implementation of the interface (leaving room for elaborate code, e.g. an S3G implementation)
* Web interface
* Doodle3D interface
... (suggestions: drawing+shaping interface, management of previous drawings, sharing with other users, etc.)
* gcode/s3g/... upload interface as well as manual command execution
* Printing interface (track progress etc.)
* Called from Doodle3D interface, direct file upload and manual command execution
* Administration interface (wifi config, printer settings, miscellaneous like for instance usbip)
* Interface to fetch and upload models from/to services like thingiverse
* Automatic wifi setup
* Self-update mechanism
* Anything else...?
## Init script logic
When the device boots, the init script tries to find any known network. If one is found, it will connect to it, otherwise it switches to AP mode.
IT might be necessary to create a lockfile to prevent accidental reruns (when could this happen?). In this case a mechanism would also be needed to remove the file on shutdown and detect a stale lockfile (e.g. after unclean reboot).

@ -22,6 +22,8 @@ From [here](http://stackoverflow.com/questions/5115613/core-dump-file-analysis).
- list (display code)
- print v
Note that remote debugging is also supported: http://wiki.openwrt.org/doc/devel/gdb.
## Further notes
- The connected issue: <<issue 3>>