Merge lp://staging/~auroraeosrose/coapp-engine/devel into lp://staging/coapp-engine
Status: | Merged |
---|---|
Approved by: | Garrett Serack |
Approved revision: | 22 |
Merged at revision: | 10 |
Proposed branch: | lp://staging/~auroraeosrose/coapp-engine/devel |
Merge into: | lp://staging/coapp-engine |
Diff against target: |
2484 lines (+2156/-133) (has conflicts) 33 files modified
.bzrignore (+8/-1) CoAppApi.h (+0/-41) Readme.txt (+6/-1) TODO.txt (+13/-0) coapp-engine.sln (+52/-0) coapp-engine.vcxproj.filters (+0/-39) dllmain.cpp (+0/-17) libcoapp.vcxproj (+191/-0) libcoapp.vcxproj.filters (+57/-0) libcoapp/doc/manual.xml (+14/-0) libcoapp/include/libcoapp.h (+414/-0) libcoapp/include/libcoapp_format.h (+70/-0) libcoapp/include/libcoapp_transport.h (+75/-0) libcoapp/src/libcoapp.c (+72/-0) libcoapp/src/libcoapp_download.c (+57/-0) libcoapp/src/libcoapp_format.c (+39/-0) libcoapp/src/libcoapp_internal.h (+34/-0) libcoapp/src/libcoapp_metadata.c (+70/-0) libcoapp/src/libcoapp_package.c (+138/-0) libcoapp/src/libcoapp_plugin.c (+122/-0) libcoapp/src/libcoapp_repo.c (+135/-0) libcoapp/src/libcoapp_transport.c (+39/-0) libcoapp/src/libcoapp_transport_http.c (+29/-0) libcoapp/test/package.c (+90/-0) libcoapp/test/repo.c (+55/-0) libcoapp/test/test.c (+41/-0) libcoapp/test/test.h (+46/-0) props.bat (+19/-0) stdafx.cpp (+0/-8) stdafx.h (+0/-15) targetver.h (+0/-11) test-package.vcxproj (+135/-0) test-repo.vcxproj (+135/-0) Contents conflict in RepositoryDirectory.c Contents conflict in coapp-engine.vcxproj |
To merge this branch: | bzr merge lp://staging/~auroraeosrose/coapp-engine/devel |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Garrett Serack | Approve | ||
Review via email:
|
Commit message
Initial layout and API rough draft for libcoapp
Description of the change
Rough API spec for the engine - includes most APIS (still might be missing some) for the main engine although all the parameters are not yet filled in or finalized. Has general structure for layout, docs, and testing.
Currently is using javadoc style notations in docblocks in comments for processing via doxygen. If Garretts testing with doxygen, C files, and C# style xml notation the docblocks will later be used with xml tags instead of @ style notation.
The APIs for transport and package formats are not yet completed, since those will be driven by the needs of the engine. The main point was to get a general layout in place for locations, formats, commenting, and API design.
Looks good to me.