dcporter
commented
11 years ago Agreed on all points. A few preliminary answers (I know, here rather than in a guide):
- SC.Page is badly named, and has nothing to do with metaphorical web pages. Its sole purpose is to hold pane and view classes (or designed instances – basically views that you've
extended ordesigned but NOTcreateed), and lazily instantiate them for you the first time yougetthem. It's a fantastic thing for performance, and is absolutely a best practice, but it's ... yeah, there are no "pages" involved with SC.Page. - SC.Pane is just a view class that doesn't require a parentView – it lives at the top of its view tree. The main pane that fills the whole screen and contains the main piece (or a main piece) of your application is appropriately called
SC.MainPane. You can only have one MainPane active at a time, and adding one will remove another. My appplications tend to have one main MainPane, and probably a MainPane that's used as the splash-screen during app launch, but if your app has multiple sections (multiple pages, if you will) then having multiple MainPanes is appropriate. Other pane classes are used for things like tool pallets (think photoshop's drag-around toolset windows that hover over top of your workspace), and pop-up modal dialogues, includingSC.AlertPane, SC's convenience dialogue box class. - Routes, and especially routing statecharts, are one of our great underdocumented features (and we have many!). I've used them but am definitely not an expert; would love to hear here from anyone that is!
So since making guides is easier now, we should definitely work on putting all this into a couple of guides. We should have guides for everything (with some organization of course). Thanks for the questions and ideas!
MFKoelmans
The sproutcore framework provides classes like
SC.PaneandSC.Pagewhich probably work great, but how to swap those, and when to use which, is not clear to me.SC.routescould be integrated into the guide on pages and panes as well, I've only seen a third party tutorial about this, using SC 1.4.2, which is, AFAIK outdated.