Add a `fuse.core` namespace
Reported by Kit Goncharov | March 3rd, 2011 @ 04:20 PM
FuseJS currently has two namespaces: fuse.dom for
DOM-related methods, and fuse.ajax for Ajax
operations. With this in mind, would it be worthwhile to move the
language extensions into a separate fuse.core
namespace? It would certainly help with the organization, although
my concern is that it will make the framework too Java-esque.
Comments and changes to this ticket
-
Joe Gornick March 6th, 2011 @ 10:38 PM
- State changed from “new” to “discuss”
- Tag cleared.
-
John-David Dalton March 14th, 2011 @ 01:13 AM
I want to avoid a
fuse.langorfuse.corefor things likefuse.Array. Is that what you meant? -
John-David Dalton March 14th, 2011 @ 01:26 AM
- State changed from “discuss” to “resolved”
-
Kit Goncharov March 14th, 2011 @ 09:35 PM
Yes, that's what I was suggesting. I agree, though, it's probably too verbose...
-
Kit Goncharov March 15th, 2011 @ 08:48 AM
- State changed from “resolved” to “invalid”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
JavaScript frameworks share similar features and functionality such as DOM manipulation, event registration, and CSS selector engines. FuseJS attempts to incorporate the strengths of these frameworks into one stable, efficient, and optimized core JavaScript framework.
Joe Gornick
John-David Dalton
Kit Goncharov