[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] Some questions of EASE
|
Well not really. This would not be much different from simply creating
an instance of the module class you want to use.
The only things wrappers would do is handle optional parameters. I guess
that is very little improvement over simple class loading.
The initial reason to come up with loadModule() was to support users
with little programming background that do not have knowledge of OO
design patterns.
Also the prominent placement of modules and functions in the modules
explorer helps those users to get going. However simple class loading is
possible and can be used by more experienced programmers.
cheers
Christian
On 05/12/2016 11:45 AM, Jonah Graham wrote:
I have another perspective coming from the Python background and not
being all that familiar with Javascript.
I am personally not a fan of loadModule() putting lots and lots of
symbols in my namespace. I would love to see the option of
loadModule() returning an object that had all the module methods on
it, perhaps with optional arguments that specified which methods (or
all) to add to my namespace? Then loadModule() becomes synonymous with
Python's import statement.
Does that fit in with how Javascript is used?
Jonah
