I'm now at the stage where I want to start coding "create domain" and "connect to domain" and similar messages between the app and the client, but I know you have your own architecture/design with domain views and so on, and I don't really see how it all fits together. These last 6 years I have been working in a more "agile" environment where you write what you need right now rather than over-designing in anticipation of future development. The code you have written so far is just one class referencing another with the code that actually does anything at the far end of the chain from the class that is requesting stuff to be done. It's very much not what I would have done, and so i just don't understand what it is meant to do.
As a result I very much feel I cannot progress any more without your direct involvement.
What I propose is that you first of all code review all the code I have written (the stuff in "client" is not even really started, so please ignore that for the time being) and then start fleshing it out by including it in the MIV Console you have already written. Any messages you find you need, implement them, or maybe just post what you need and I'll implement it for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I am behind you code-wise and ahead design wise ;)
And correct, I have only had time to write framing code. It does nothing yet.
I will review your code with the goal that we merge our efforts together and start coding in the same source and build environment!
I hoped to have gotten there this weekend but spent most of the time struggling with compiler configurations, ifdeff-ing code and organizing the repository. Can't imagine why we have 2013 but putting together software still is down to itsy-bitsy configuration problems and web-search for fixes as you go?
My goal is an environment where you install the build tools, check out the code and perform a make. And the contents of the directory structure makes it happen!
/Kjell-Olov
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My make files in my directory structure very much already do what you are trying to do. Go to "projects/jx" and type "make" and "make test".
As an extra feature, I made it pick up the source code automatically. At work we have a "src.mk" system to list files to build, but I really don't see why the makefile cannot automatically find the source files. So that's what I made it do and it really works well.
I am currently writing some code to use libgcrypt, to replace the code I lost earlier. It's a bit noddy, but I'm writing it so it can be expanded later into a proper key manager. The server will use it to manage node public keys and its own private and public keys. The applications will use it to manage the user's private and public keys. And somewhere in between it will be used to manage other users' public keys.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm now at the stage where I want to start coding "create domain" and "connect to domain" and similar messages between the app and the client, but I know you have your own architecture/design with domain views and so on, and I don't really see how it all fits together. These last 6 years I have been working in a more "agile" environment where you write what you need right now rather than over-designing in anticipation of future development. The code you have written so far is just one class referencing another with the code that actually does anything at the far end of the chain from the class that is requesting stuff to be done. It's very much not what I would have done, and so i just don't understand what it is meant to do.
As a result I very much feel I cannot progress any more without your direct involvement.
What I propose is that you first of all code review all the code I have written (the stuff in "client" is not even really started, so please ignore that for the time being) and then start fleshing it out by including it in the MIV Console you have already written. Any messages you find you need, implement them, or maybe just post what you need and I'll implement it for you.
Yes, I am behind you code-wise and ahead design wise ;)
And correct, I have only had time to write framing code. It does nothing yet.
I will review your code with the goal that we merge our efforts together and start coding in the same source and build environment!
I hoped to have gotten there this weekend but spent most of the time struggling with compiler configurations, ifdeff-ing code and organizing the repository. Can't imagine why we have 2013 but putting together software still is down to itsy-bitsy configuration problems and web-search for fixes as you go?
My goal is an environment where you install the build tools, check out the code and perform a make. And the contents of the directory structure makes it happen!
/Kjell-Olov
My make files in my directory structure very much already do what you are trying to do. Go to "projects/jx" and type "make" and "make test".
As an extra feature, I made it pick up the source code automatically. At work we have a "src.mk" system to list files to build, but I really don't see why the makefile cannot automatically find the source files. So that's what I made it do and it really works well.
I am currently writing some code to use libgcrypt, to replace the code I lost earlier. It's a bit noddy, but I'm writing it so it can be expanded later into a proper key manager. The server will use it to manage node public keys and its own private and public keys. The applications will use it to manage the user's private and public keys. And somewhere in between it will be used to manage other users' public keys.