Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need help and guidance on planning and laying out framework for a project #97

Closed
sdinesh86 opened this issue Feb 24, 2016 · 4 comments
Closed

Comments

@sdinesh86
Copy link

I played around with mantra spec, and tried a sample app to get the hang or everything now I am planning on starting a small project for personal use and needed some help.

I would like to build something similar to CMS + IOT app, with themeing and customizability. I planned out a quick structure for the same but I am stuck or confused at some points

My goal is to build a simple IOT app for personal use, with a admin panel it should be extensible ( Plugin system ) and themes would be added point.

after taking clues from other CMS frameworks, my current plan is to implement the core functionality as core module which would have services which can be consumed, then I can extend that by writing modules which consume these services.
Example : Navigation module would have methods which would be exposed and can be consumed bu other modules in order to add menu item on navigation menu

honestly I might be expecting too much or would be wrong here, is it really possible with mantra spec and if yes can someone help me with this.

I have already created a sample app, which I am playing around right now and trying to get the most basic stuff in ( Page with Navigation Menu ), if anyone help me i could share this so people can share their expertise and guide me on this.

Thanks

@adamdawkins
Copy link

I don't think you're expecting too much, however I think Mantra's in an
early phase and we're all still trying to figure out what works well "in
the wild". Your approach sounds sensible, why not press on with it and see
how it goes with having different modules for plugins, etc.

If you then find some pain points (or successes), they'd be very helpful
for us all to hear about!
On Wed, 24 Feb 2016 at 19:49, Dinesh Salunke [email protected]
wrote:

I played around with mantra spec, and tried a sample app to get the hang
or everything now I am planning on starting a small project for personal
use and needed some help.

I would like to build something similar to CMS + IOT app, with themeing
and customizability. I planned out a quick structure for the same but I am
stuck or confused at some points

My goal is to build a simple IOT app for personal use, with a admin panel
it should be extensible ( Plugin system ) and themes would be added point.

after taking clues from other CMS frameworks, my current plan is to
implement the core functionality as core module which would have services
which can be consumed, then I can extend that by writing modules which
consume these services.
Example : Navigation module would have methods which would be exposed and
can be consumed bu other modules in order to add menu item on navigation
menu

honestly I might be expecting too much or would be wrong here, is it
really possible with mantra spec and if yes can someone help me with this.

I have already created a sample app, which I am playing around right now
and trying to get the most basic stuff in ( Page with Navigation Menu ), if
anyone help me i could share this so people can share their expertise and
guide me on this.

Thanks


Reply to this email directly or view it on GitHub
#97.

@sdinesh86
Copy link
Author

I am already on it, but due to lack of experience I am but confused and lost on how to structure and write this whole thing.
I went through the Telescope code and I am planning on going through the same route lets see.

My current hurdle is, how to let user override the defaults ui and behaviors using themes and plugins.
So I was planning on using the class based structure, but in one of the comment's from @arunoda I read its not preferred way. So now looking for other methdos.

@arunoda
Copy link
Collaborator

arunoda commented Feb 25, 2016

@sdinesh86 There is no restrictions on the class based React components. If needed you should use them. Stateless components are simple to write, but not always needed.

But, components should not have any methods. All the logic should be done via actions and mutating states.

@sdinesh86
Copy link
Author

@arunoda in the #57 you mentioned about Telescope style for the mantra-dialogue, Is mantra-dialogue also going to implement similar functionalities ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants