@warren pls take a look and kindly leave some suggestions if possible! :)

@warren I saw that you mention you are in vacation...Can you pls take a look at mine when you free? Been posted for a while...

Hi, I was traveling for work, and got back yesterday (and took a day of rest :-P) but am reading through all of these now. Thanks!

@warren Yeah... I saw everybody is seeking u lol... Appreciated a lot have time checking our proposals!

Hi, the finite state machine idea is interesting. How would that look in an image-sequencer implementation? Can you illustrate this with some example code, imagining that you've integrated the finite state machine concept, to show me how image-sequencer would work with that model?

Could you also link to anything you've already done on the image-sequencer project, even comments and issues, just so I can see how you've started to look through the code? Thank you.

Vue.js also seems really interesting, thanks for suggesting it! Would it be (i'd prefer) an optional UI implementation for the project, alongside direct commandline (nodejs) use and (for example) a flow-based visual UI? Is there any way you could provide a kind of diagram of how the UI might be architected, a bit like the diagram here: https://publiclab.org/notes/mridulnagpal/03-01-2017/map-of-projects and/or a mockup of how it might look?

Thanks for your proposal and apologies for my slowness in replying!

@warren Since the deadline is almost approaching and I'm quite busy this week...:( I don't think I can have time to write down any codes within deadline... While I'll draw an UI graph to give more detail about how VUEJS and state-machine works. I'll also include my old project link later for showing my experience with VueJS and State-machine(That one is actually a private one but I might can dig them out for a while...) Thank you for advice!

Vue.js is great!

Sorry to interrupt, but isn't Image Sequencer supposed to handle the Image Processing? The front end which was written was a demo (a demonstration of Image Sequencer's functioning).

So is it okay to prioritise the UI Creation over the actual Image Sequencer Library, which is under construction rather than the modules themselves and Image Sequencer's core functioning, especially when we are more interested in the Node.js implementation?

@ccpandhare Well, I'm afraid I don't agree with what you say. Based on the description and after I read whole code base, there is a lot of logic and design needs contained on UI part of the whole application. Based on my point of view, this application is a early stage application and still need improvement of building a better structure. I'm saying that I'm gonna rebuild whole web application structure not only the UI part. I think what I can bring useful contribution is what I'm writing above and it does covers requirement of the topic, also shade a light for flexible and manageable for future development. :)

@warren Can u double check my revised proposals.

Hi, I guess I still think a diagram of sorts would help explain exactly what functions and states would be encapsulated in each component, and perhaps would help me understand the distinctions you're making -- I'm especially interested in which parts manage the "state" of the system and which are required for running. Notice we are trying to make:

1. the system runnable without a gui (in nodejs)
2. the modules as simple as possible so they can be written in a short and standard way by anyone
3. the whole system usable as a library in​multiple applications

So another thing to talk about is what specifically Vue.js and the state machine library would make possible that is am improvement (beyond just optimization) and what possible drawbacks they might have.

Thanks for your extra work to articulate your proposal, it's much appreciated.

@warren Hi, sry I'm a little busy recently... Let me re-state my very immature and personal thoughts with this updated diagram.(I also rewrite some of my proposal) The target of my proposals is to make this project a mature and "complete" projects that not only providing a excellent web application instead of a incomplete demo but also provide all modules API-ify -- At least I think that's most complete open source project do for their Phase 1. For current stage of this project, we don't have much modules, we don't have a complete demo, not to say we have any "multiply applications". We just say at least we providing so many modules that can make people use? Like a NPM library? people nowadays rare trust any start up NPM libraries, and making server side module API-ify usually is not in early stage of startup projects do. Even your aim for this project is indeed just want to building some libraries contributing to NPM community and making a lot people building their applications leverage your modules... I will still say I think rearrange whole structure and give a perfectly demo is more important. (Make modules API-ify is so easy to done, but make them competitive is hard)

Thank you for the diagram and for sharing your thoughts -- much appreciated!