> > Could you give me an example? I'm not an expert on JCR, but I can't > > think of an operation that you can perform on a property, I thought > > you > > could only change its value. It's possible we could distinguish > > property operations which could be on this tab from node operations > > which would be on the "Operations" tab (maybe renaming it to "Node > > Operations" if needed). > > Well, this was a general UI idea. I think small icons or simple menus > are better than a separate tab for operations. Tabs should be used for > content, not for actions. >
Maybe, I don't disagree with you, but I'm also concerned with scaling and not trying to fit too much data on one view. For instance, if you have 500 properties, you shouldn't feel claustrophobic because there's too much other stuff on the same pane. Operations could potentially be handled by context menus on the nodes themselves, however, I'm not sure I really like context menus. Let me think about it a bit more and come up with a mock-up and we can go from there. I still have a lot to figure out and I'm sure my ideas will change. > > Yes, agreed. My idea here was to provide something along the lines > > of a > > CMS, something I'm ultimately interested in using sling for. > > Disclaimer: Sling comes from a CMS company ;-) > Yes, I realize that ;-) However, my needs are not for a full-blown, general-purpose CMS, just a way to do some niche content customization and templated pages. For instance, I'd looked at Magnolia before and it was overkill for what we need. I'd actually built something sort of like Sling last summer (not as robust, of course) on top of Jackrabbit using renderers decoupled from content (only supporting Velocity), etc., very similar idea with URI mapping to a path in the JCR to the content, just not quite as feature-full as sling or as broad in scope. Our company provides real-time monitoring and business performance views, and one of our claims to fame is the ability to customize views for the users needs (creating "dashboards" if you will). I am now looking to extend that functionality to the web, where we can intermingle with other sorts of web technologies, e.g. JSR-168 portals, non-standard portals (e.g. google, yahoo), BI tools, and other CMS systems (e.g. BEA ALUI). So I need a system that allows users to create pages from a palette of controls that we provide and a way to hook those pages and their widgets up to our real-time data. Then I'll need to build bridges to other systems (which is outside of the scope of Sling of course). What we need is a very niche sort of CMS capability for our base offering and not something I'd expect to find in a general-purpose CMS. Though it is possible that as users are exposed to this, we might find a need to build into a CMS that has more of the collaboration you'd expect from a general-purpose CMS. Anyway, I digress and I've rambled a bit ;-) Sling seems like a nice fit for what we need. > Alex > Cheers, Craig
