search

CORE-POS / IS4C

Cooperative Operational Retail Environment
http://www.core-pos.com
GNU General Public License v2.0
63 stars 44 forks source link

Proposal: backend, documentation, fannie & license move up ../ out of pos #13

Closed blynch-newpi closed 13 years ago

blynch-newpi commented 13 years ago

This would help start the march to defining the 'pos' as a critical function area, the backend/fannie as critical function areas and then putting the documentation at the root of the IS4C.

This also brings up some naming conventions and organization. Proposal: IS4C is the working name of the overall project, pos refers to the critical files and functions needed to run the lane.

cgapperi commented 13 years ago

Are you suggesting that 'Fannie' come up to the POS level, as well? I like that idea.

blynch-newpi commented 13 years ago

Yes exactly. so the 'pos' folder only have those files, functions, etc. vital to running the lane. While 'fannie' comes out to the 'root' at the same level as 'pos'. Then, I foresee us starting to work on some of Andy's wishlist items, organizing all the files within the pos folder into categories either by function or whatever is decided for that framework.

gohanman commented 13 years ago

This sounds good to me. I especially like the idea of documentation going up to the top level.

gohanman commented 13 years ago

I made this change, partially so I could hit "Comment & Close" on purpose instead of by accident.

I realize that pos/is4c-nf is currently an unnecessary extra directory level. I'd like to keep it because I'm toying with the idea of multiple front ends managed from a single back end (specifically, on my side pos/is4c-web is a very, very alpha ecommerce site that understands IS4C's product/pricing table format and produces dtransaction-style sales records). Alternate front ends may well be beyond the scope of our project, but the extra directory level makes my life a little easier.