Hi Dilan, On Wed, Dec 4, 2013 at 1:12 AM, Chathura Dilan <[email protected]> wrote:
> Hi Ruchira, > > I think it is good to publish and article about 'Best practices to > follow when using Caramel' and the design patterns which we can use with > Caramel. Since it is more generic, there is no proper way we can follow how > to use it. > Being open for a framework is good; but being too open cause developers to > do lot of work. but when it come to a product, we should have to lock down > it in someway, our own way using any design patterns we want, may be the > front controller or anything. Caramel need to support it. > > If we take a product like 'Generic Store' which is best use of Caramel (of > course it should be), there are some questions I have to ask. > > First thing is we cannot distinguish between what are the things which > handle by Caramel and what are not. Still I have no idea overriding an > asset is handle by Caramel or not in ES. Even from the Caramel blog > http://wso2.github.io/caramel/ I cannot get any idea .Normally developers > expect many thing from a framework to handle automatically without writing > hundred lines of codes. > caramel address a few, but bit important stuff that we faced during Jaggery based app developments. If you see that it lacks something, then that's where you need to contribute back and improve as I mentioned in my earlier reply. Because of the work load we had, we didn't have enough time to properly document caramel. But we had provided you a better sample at https://github.com/ruchiraw/wso2-samples-store. If you have ever followed what we have mentioned in the README, then it should have helped you a lot to understand caramel internals. > > There are too many configurations, it's good to use proper conventions > (such as naming files) and it would be very helpful for developers and > designers. > Without breaking many things in to partials (such as text of a button), it > is better to decide what really need to go in to partials. > If caramel was used to write a just a webapp, then things will be totally different. Generic store is a GENERIC store and it is not just a webapp. Generic store has been written in a way that every asset type gets its own sanbox like envirenment to control their parts. That's why we always asked you to use whatever the extension points that have been provided. Also we always got you feedbacks whenever you found any difficulties with its generic nature. But if someone did't adhere to the extension mechanism and had edited here and there in the store code base, then it's up to him to handle everything that he faces. That's why they will have to do a huge effort when they switch from one store milestone to the other. Again, as I have mentioned so many times in offline discussions generic store is not a good place to learn about caramel. That's why we have written above mentioned sample store app and had pointed you. Regarding your above partial example, there is only one place where the text of a button has separated into a partial. To be precise, it's is the 'Download' or the 'Bookmark' text. Since that is a generic store and that button text needs to be overridden by different asset types, we had to do so. If you had a better suggestion it would be better if you had given us the feedback as we had many discussions. > If you can publish and article on 'Best practices to follow when using > Caramel' to address above it would be very helpful. > > > > -- > Regards, > > Chatura Dilan Perera > *(Senior Software Engineer - WSO2 Mobile)* > www.dilan.me > -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* *email: [email protected] <[email protected]>, blog: ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, mobile: +94 77 5493444*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
