-
Notifications
You must be signed in to change notification settings - Fork 6
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
Suggest to load the extendscripter modules #6
Comments
Great work. I was wondering why you created another org on npm and here on Github too?
That gets confusing IMHO. Shouldn't we get all under one roof? |
My thinking was that Extendscripters holds all the sub-modules (and possibly share the same global.myApp variable) that make up complete apps/projects in ExtendScript. Clearly we would need to make this clear in the docs but can also rename if you like. What about myApp? |
I don't get it? Do you want to create a boilerplate? |
A mixture between a utility file (remember those) but then hosted seperared on NPM and an API/Framework (like IdExtenso) targeting other apps as well. The separation of the utility file is an important detail as that is what makes the framework work load well using require. Said that I will proberbly reference a boilerplate but this could be extentscriptr after we have the —nopoly flag. I hope this will start feeding different boilerplates. Maybe I am over explaining it? And just a bunch of utility functions/classes is good enough? Either way, it is a concept I am playing with. If it actually works I am not sure about (yet). But the seperate utility classes and functions would definitely be useful to developers even if the bigger picture fails. |
Hey guys, I added the extendscripter modules to NPM which breaks this collection into bite-size pieces.
I suggest adding these as a dependency here? Making it nice and DRY.
And then once this is successful do the es5 as well.
What are your thoughts?
Of course, it would be good to write some test etc first before we do anything but would love to get your feedback!
The text was updated successfully, but these errors were encountered: