Reorganizing the frameworks for 2.0

[Dave Porter]

For SproutCore 2.0, I would love to see the opportunity taken to reorganize code between the frameworks. I'd like to see fewer frameworks with clearer lines between them and separated based on actual use cases.

Also, what about namespacing, or otherwise separating out content by framework? Maybe only for the non-core frameworks. But for example I'm thinking about LearnDot's great WYSIWYG editor, which includes like a dozen views. If that were brought into SproutCore proper as a non-core framework, how would they be grouped?

- SC.WYSIWYGEditorView (super ugly when you look down the list)

- SC.WYSIWYG.EditorView (sub-namespacing)

- WYSIWYG.EditorView (separate namespacing)

- SC.WGEditorView (the Cocoa two-letter-prefix trick)

So, frameworks and (actual or implied) namespaces. Thoughts?

[Topher Fangio]

I concur on the framework separation, but honestly, I can't say that I've actually had any experience (good or bad) regarding how the frameworks are currently named. I use the entire sproutcore framework, and don't really separate stuff.

For your other question, I very much prefer the last example (two-letter Cocoa prefix).

--

Topher Fangio

System Architect
Pharos Resources

office: 325.216.2908
mobile: 325.660.7141

--
You received this message because you are subscribed to the Google Groups "SproutCore Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sproutcore-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.