@Brian - "but there's a lot of fragmented development and not a lot of investment going back in." --- yes, this is what I sense. I'm not even aware of the Brix community unlike Wicket which is more active. If you see the Brix architecture page i put some comments but Looks pretty dead which is pretty de-motivating.
"I would challenge you to create needs in the core by demonstrating those needs" --- No, I dont think the core needs to be changed as such, Simple is better & should remain preserved. However we can upgrade the Wicket dependencies from time to time? :) ?! I ALSO like the idea it does NOT have a custom workflow etc built into core, coz I'm a fan of Drools work flow & Rules Engines to allocate business logic and workflows; Apache Camel & Spring Integration. "If you are worried about people having access to your assets" --- No sir, the more the merrier. I'd love to get into it once i'm sure to commit time & effort. >From a "using for commercial web sites" perspective, issue is from a UI perspective the Admin module has a poor finish compared to Alfresco and say Hippo; its not just the CSS but the general layout sucks. ...I cant sell a website & present that to the customer without significant effort. Something I can look to contribute on. thank you. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Java-in-CMS-arena-wicket-to-lead-the-way-tp2541542p2543378.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
