Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: > SOAP Tracer is one. I think there is a BPEL editor UI as well. > > Azeez > > > +1 for add "EditArea" to edit report template xml(report design ) files > for customizable reports. > Thanks ajithn ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
Yeah. We have to use the pretty printed XML.[1] The main concern here is that, it slows down drastically when we use a XML text of 2k+ lines. (Some of our xml configuration are very likely to go beyond that limit e.g. Synapse config, wsdls) [1]http://dl.dropbox.com/u/5494230/editarea/editarea_test.html On Sun, Jul 25, 2010 at 7:51 PM, Chanaka Jayasena wrote: > They are talking about auto indenting new lines. This is when you edit an > already pretty printed xml, and press "Enter" to go to a new line, the new > line will be auto indented. > > Chanaka > > > On Sun, Jul 25, 2010 at 7:10 PM, Afkham Azeez wrote: > >> >> http://www.cdolivet.com/index.php?page=editArea&sess=f0823c62280f9db7ce47ca8acd7aeb21 >> >> >> It says EditArea is capable of auto indenting >> >> Azeez >> >> >> On Sun, Jul 25, 2010 at 6:50 PM, Chanaka Jayasena wrote: >> >>> EditArea is not capable of pretty printing. But it can simply integrate >>> to do real time syntax highlighting. >>> >>> All the editors I worked with are using this EditArea plugin. I think >>> some folks are still using CodePress. If so they also have to convert them >>> selves to EditArea, since CodePress is still not supporting Chrome browser. >>> >>> >>> On Sun, Jul 25, 2010 at 6:35 PM, Waruna Ranasinghe wrote: >>> On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: > SOAP Tracer is one. I think there is a BPEL editor UI as well. We don't have a BPEL editor UI, but we show BPEL definition as an XML. Therefore, we only need XML syntax hi-lighting and pretty printing. I'm not sure whether we can use EditArea in this case. If possible +1 to integrate it. Thanks, Waruna > > Azeez > > > On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka > wrote: > >> Hi Chanaka, >> >> On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena >> wrote: >> >>> Data Services wizard is using the same editor (EditArea). >> >> >> Are there any components that use a different XML editor? If so can we >> switch to EditArea and be done with the old editor once and for all? >> >> Thanks, >> Hiranya >> >> >>> >>> >>> On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe < >>> sume...@wso2.com> wrote: >>> I think Data services wizard done by Chanaka uses a different xml highlighter. AFAIR esb also uses the same. /sumedha On 7/25/10, Afkham Azeez wrote: > We still have another syntax highlighter which was used earlier and still in > use by at least the SOAP Message Tracer. EditArea seems to be much better > than that one. We need to be careful when using multiple libraries for the > same functionality. I took a look at the license of EditArea, it is LGPL and > is OK to use but the authors notice needs to be published. Have we done > that? > > Azeez > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri wrote: > >> Hi folks, >> >> We had a major requirement in ESB to have real-time syntax highlighting >> for ESB source views(it was a raw text editor at that time :)) for Iridium >> release. So, at that point of time, Carbon UI framework does not have such >> highlighter to suit that requirement. I think, Chanaka dig a round for a >> good solution and he found Editarea[1] and I added it to Carbon UI[2] and >> used in in all ESB XML source view. >> >> However, now it is not just used in ESB but also in most of the other XML >> views in management console (Policy Editor etc.). >> I agree with Azeez that these changes were not properly communicated to >> the >> list :(. Anyway, if we are currently using multiple XML editors in our >> platform (or in most cases, not using any rich editor at all ), we should >> unify it to one editor (may be EditArea or something else). >> >> regards, >> Kasun >> >> [1] >> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >> [2] >> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >> >> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >>> wrote: >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > Hi Kasun, > I accidentally came across this
Re: [Carbon-dev] Javascript XML syntax highlighting
They are talking about auto indenting new lines. This is when you edit an already pretty printed xml, and press "Enter" to go to a new line, the new line will be auto indented. Chanaka On Sun, Jul 25, 2010 at 7:10 PM, Afkham Azeez wrote: > > http://www.cdolivet.com/index.php?page=editArea&sess=f0823c62280f9db7ce47ca8acd7aeb21 > > > It says EditArea is capable of auto indenting > > Azeez > > > On Sun, Jul 25, 2010 at 6:50 PM, Chanaka Jayasena wrote: > >> EditArea is not capable of pretty printing. But it can simply integrate to >> do real time syntax highlighting. >> >> All the editors I worked with are using this EditArea plugin. I think some >> folks are still using CodePress. If so they also have to convert them selves >> to EditArea, since CodePress is still not supporting Chrome browser. >> >> >> On Sun, Jul 25, 2010 at 6:35 PM, Waruna Ranasinghe wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: >>> SOAP Tracer is one. I think there is a BPEL editor UI as well. >>> >>> We don't have a BPEL editor UI, but we show BPEL definition as an XML. >>> Therefore, we only need XML syntax hi-lighting and pretty printing. >>> I'm not sure whether we can use EditArea in this case. If possible +1 to >>> integrate it. >>> >>> >>> Thanks, >>> Waruna >>> >>> Azeez On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka wrote: > Hi Chanaka, > > On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: > >> Data Services wizard is using the same editor (EditArea). > > > Are there any components that use a different XML editor? If so can we > switch to EditArea and be done with the old editor once and for all? > > Thanks, > Hiranya > > >> >> >> On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe > > wrote: >> >>> I think Data services wizard done by Chanaka uses a different xml >>> highlighter. AFAIR esb also uses the same. >>> /sumedha >>> >>> On 7/25/10, Afkham Azeez wrote: >>> > We still have another syntax highlighter which was used earlier and >>> still in >>> > use by at least the SOAP Message Tracer. EditArea seems to be much >>> better >>> > than that one. We need to be careful when using multiple libraries >>> for the >>> > same functionality. I took a look at the license of EditArea, it is >>> LGPL and >>> > is OK to use but the authors notice needs to be published. Have we >>> done >>> > that? >>> > >>> > Azeez >>> > >>> > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri >>> wrote: >>> > >>> >> Hi folks, >>> >> >>> >> We had a major requirement in ESB to have real-time syntax >>> highlighting >>> >> for ESB source views(it was a raw text editor at that time :)) for >>> Iridium >>> >> release. So, at that point of time, Carbon UI framework does not >>> have such >>> >> highlighter to suit that requirement. I think, Chanaka dig a round >>> for a >>> >> good solution and he found Editarea[1] and I added it to Carbon >>> UI[2] and >>> >> used in in all ESB XML source view. >>> >> >>> >> However, now it is not just used in ESB but also in most of the >>> other XML >>> >> views in management console (Policy Editor etc.). >>> >> I agree with Azeez that these changes were not properly >>> communicated to >>> >> the >>> >> list :(. Anyway, if we are currently using multiple XML editors in >>> our >>> >> platform (or in most cases, not using any rich editor at all ), we >>> should >>> >> unify it to one editor (may be EditArea or something else). >>> >> >>> >> regards, >>> >> Kasun >>> >> >>> >> [1] >>> >> >>> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >>> >> [2] >>> >> >>> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >>> >> >>> >> >>> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez >>> wrote: >>> >> >>> >>> >>> >>> >>> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >>> >>> wrote: >>> >>> >>> >>> >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez >>> wrote: >>> >>> > Hi Kasun, >>> > I accidentally came across this post, >>> > >>> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html >>> , >>> > in your blog. We already use JavaScript libraries that do XML >>> syntax >>> > highlighting. Also, in Carbon, we need to use the same >>> libraries across >>> > all >>> > components. So for instance, when it comes to graph generation >>> or XML >>> > syntax >>> > highlighting etc. we need to stick to a single agreed upon >>> library set. >>> >
Re: [Carbon-dev] Javascript XML syntax highlighting
http://www.cdolivet.com/index.php?page=editArea&sess=f0823c62280f9db7ce47ca8acd7aeb21 It says EditArea is capable of auto indenting Azeez On Sun, Jul 25, 2010 at 6:50 PM, Chanaka Jayasena wrote: > EditArea is not capable of pretty printing. But it can simply integrate to > do real time syntax highlighting. > > All the editors I worked with are using this EditArea plugin. I think some > folks are still using CodePress. If so they also have to convert them selves > to EditArea, since CodePress is still not supporting Chrome browser. > > > On Sun, Jul 25, 2010 at 6:35 PM, Waruna Ranasinghe wrote: > >> >> >> On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: >> >>> SOAP Tracer is one. I think there is a BPEL editor UI as well. >> >> We don't have a BPEL editor UI, but we show BPEL definition as an XML. >> Therefore, we only need XML syntax hi-lighting and pretty printing. >> I'm not sure whether we can use EditArea in this case. If possible +1 to >> integrate it. >> >> >> Thanks, >> Waruna >> >> >>> >>> Azeez >>> >>> >>> On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka >>> wrote: >>> Hi Chanaka, On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: > Data Services wizard is using the same editor (EditArea). Are there any components that use a different XML editor? If so can we switch to EditArea and be done with the old editor once and for all? Thanks, Hiranya > > > On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe > wrote: > >> I think Data services wizard done by Chanaka uses a different xml >> highlighter. AFAIR esb also uses the same. >> /sumedha >> >> On 7/25/10, Afkham Azeez wrote: >> > We still have another syntax highlighter which was used earlier and >> still in >> > use by at least the SOAP Message Tracer. EditArea seems to be much >> better >> > than that one. We need to be careful when using multiple libraries >> for the >> > same functionality. I took a look at the license of EditArea, it is >> LGPL and >> > is OK to use but the authors notice needs to be published. Have we >> done >> > that? >> > >> > Azeez >> > >> > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri >> wrote: >> > >> >> Hi folks, >> >> >> >> We had a major requirement in ESB to have real-time syntax >> highlighting >> >> for ESB source views(it was a raw text editor at that time :)) for >> Iridium >> >> release. So, at that point of time, Carbon UI framework does not >> have such >> >> highlighter to suit that requirement. I think, Chanaka dig a round >> for a >> >> good solution and he found Editarea[1] and I added it to Carbon >> UI[2] and >> >> used in in all ESB XML source view. >> >> >> >> However, now it is not just used in ESB but also in most of the >> other XML >> >> views in management console (Policy Editor etc.). >> >> I agree with Azeez that these changes were not properly >> communicated to >> >> the >> >> list :(. Anyway, if we are currently using multiple XML editors in >> our >> >> platform (or in most cases, not using any rich editor at all ), we >> should >> >> unify it to one editor (may be EditArea or something else). >> >> >> >> regards, >> >> Kasun >> >> >> >> [1] >> >> >> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >> >> [2] >> >> >> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >> >> >> >> >> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez >> wrote: >> >> >> >>> >> >>> >> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >> >>> wrote: >> >>> >> >> >> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez >> wrote: >> >> > Hi Kasun, >> > I accidentally came across this post, >> > >> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html >> , >> > in your blog. We already use JavaScript libraries that do XML >> syntax >> > highlighting. Also, in Carbon, we need to use the same libraries >> across >> > all >> > components. So for instance, when it comes to graph generation >> or XML >> > syntax >> > highlighting etc. we need to stick to a single agreed upon >> library set. >> > When >> > you start using a new library, please let others know about it >> (perhaps >> > I >> > missed that mail). >> > >> >> So does this mean that we are using multiple XML editors in the >> platform >> now? If so we need to converge into one. May be Chanaka can shed >> some >> light >> on the matter. IIR
Re: [Carbon-dev] Javascript XML syntax highlighting
EditArea is not capable of pretty printing. But it can simply integrate to do real time syntax highlighting. All the editors I worked with are using this EditArea plugin. I think some folks are still using CodePress. If so they also have to convert them selves to EditArea, since CodePress is still not supporting Chrome browser. On Sun, Jul 25, 2010 at 6:35 PM, Waruna Ranasinghe wrote: > > > On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: > >> SOAP Tracer is one. I think there is a BPEL editor UI as well. > > We don't have a BPEL editor UI, but we show BPEL definition as an XML. > Therefore, we only need XML syntax hi-lighting and pretty printing. > I'm not sure whether we can use EditArea in this case. If possible +1 to > integrate it. > > > Thanks, > Waruna > > >> >> Azeez >> >> >> On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka wrote: >> >>> Hi Chanaka, >>> >>> On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: >>> Data Services wizard is using the same editor (EditArea). >>> >>> >>> Are there any components that use a different XML editor? If so can we >>> switch to EditArea and be done with the old editor once and for all? >>> >>> Thanks, >>> Hiranya >>> >>> On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe wrote: > I think Data services wizard done by Chanaka uses a different xml > highlighter. AFAIR esb also uses the same. > /sumedha > > On 7/25/10, Afkham Azeez wrote: > > We still have another syntax highlighter which was used earlier and > still in > > use by at least the SOAP Message Tracer. EditArea seems to be much > better > > than that one. We need to be careful when using multiple libraries > for the > > same functionality. I took a look at the license of EditArea, it is > LGPL and > > is OK to use but the authors notice needs to be published. Have we > done > > that? > > > > Azeez > > > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri > wrote: > > > >> Hi folks, > >> > >> We had a major requirement in ESB to have real-time syntax > highlighting > >> for ESB source views(it was a raw text editor at that time :)) for > Iridium > >> release. So, at that point of time, Carbon UI framework does not > have such > >> highlighter to suit that requirement. I think, Chanaka dig a round > for a > >> good solution and he found Editarea[1] and I added it to Carbon > UI[2] and > >> used in in all ESB XML source view. > >> > >> However, now it is not just used in ESB but also in most of the > other XML > >> views in management console (Policy Editor etc.). > >> I agree with Azeez that these changes were not properly communicated > to > >> the > >> list :(. Anyway, if we are currently using multiple XML editors in > our > >> platform (or in most cases, not using any rich editor at all ), we > should > >> unify it to one editor (may be EditArea or something else). > >> > >> regards, > >> Kasun > >> > >> [1] > >> > http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 > >> [2] > >> > https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea > >> > >> > >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez > wrote: > >> > >>> > >>> > >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka > >>> wrote: > >>> > > > On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez > wrote: > > > Hi Kasun, > > I accidentally came across this post, > > > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html > , > > in your blog. We already use JavaScript libraries that do XML > syntax > > highlighting. Also, in Carbon, we need to use the same libraries > across > > all > > components. So for instance, when it comes to graph generation or > XML > > syntax > > highlighting etc. we need to stick to a single agreed upon > library set. > > When > > you start using a new library, please let others know about it > (perhaps > > I > > missed that mail). > > > > So does this mean that we are using multiple XML editors in the > platform > now? If so we need to converge into one. May be Chanaka can shed > some > light > on the matter. IIRC he did the initial work required to integrate > EditArea > into Carbon. > > >>> > >>> > >>> Yes! That was my point. See my earlier reply. AFAIC, there was no > mail to > >>> carbon-dev about using this library. When you make major platform > level > >>> decisions like that, you need to inform the list! >>
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 6:35 PM, Waruna Ranasinghe wrote: > > > On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: > >> SOAP Tracer is one. I think there is a BPEL editor UI as well. > > We don't have a BPEL editor UI, but we show BPEL definition as an XML. > Therefore, we only need XML syntax hi-lighting and pretty printing. > I'm not sure whether we can use EditArea in this case. If possible +1 to > integrate it. > Yes, you can use EditArea for syntax highlighting. (However, for pretty printing you need to use the XML Pretty printer in carbon.utils) > > > Thanks, > Waruna > > >> >> Azeez >> >> >> On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka wrote: >> >>> Hi Chanaka, >>> >>> On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: >>> Data Services wizard is using the same editor (EditArea). >>> >>> >>> Are there any components that use a different XML editor? If so can we >>> switch to EditArea and be done with the old editor once and for all? >>> >>> Thanks, >>> Hiranya >>> >>> On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe wrote: > I think Data services wizard done by Chanaka uses a different xml > highlighter. AFAIR esb also uses the same. > /sumedha > > On 7/25/10, Afkham Azeez wrote: > > We still have another syntax highlighter which was used earlier and > still in > > use by at least the SOAP Message Tracer. EditArea seems to be much > better > > than that one. We need to be careful when using multiple libraries > for the > > same functionality. I took a look at the license of EditArea, it is > LGPL and > > is OK to use but the authors notice needs to be published. Have we > done > > that? > > > > Azeez > > > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri > wrote: > > > >> Hi folks, > >> > >> We had a major requirement in ESB to have real-time syntax > highlighting > >> for ESB source views(it was a raw text editor at that time :)) for > Iridium > >> release. So, at that point of time, Carbon UI framework does not > have such > >> highlighter to suit that requirement. I think, Chanaka dig a round > for a > >> good solution and he found Editarea[1] and I added it to Carbon > UI[2] and > >> used in in all ESB XML source view. > >> > >> However, now it is not just used in ESB but also in most of the > other XML > >> views in management console (Policy Editor etc.). > >> I agree with Azeez that these changes were not properly communicated > to > >> the > >> list :(. Anyway, if we are currently using multiple XML editors in > our > >> platform (or in most cases, not using any rich editor at all ), we > should > >> unify it to one editor (may be EditArea or something else). > >> > >> regards, > >> Kasun > >> > >> [1] > >> > http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 > >> [2] > >> > https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea > >> > >> > >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez > wrote: > >> > >>> > >>> > >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka > >>> wrote: > >>> > > > On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez > wrote: > > > Hi Kasun, > > I accidentally came across this post, > > > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html > , > > in your blog. We already use JavaScript libraries that do XML > syntax > > highlighting. Also, in Carbon, we need to use the same libraries > across > > all > > components. So for instance, when it comes to graph generation or > XML > > syntax > > highlighting etc. we need to stick to a single agreed upon > library set. > > When > > you start using a new library, please let others know about it > (perhaps > > I > > missed that mail). > > > > So does this mean that we are using multiple XML editors in the > platform > now? If so we need to converge into one. May be Chanaka can shed > some > light > on the matter. IIRC he did the initial work required to integrate > EditArea > into Carbon. > > >>> > >>> > >>> Yes! That was my point. See my earlier reply. AFAIC, there was no > mail to > >>> carbon-dev about using this library. When you make major platform > level > >>> decisions like that, you need to inform the list! > >>> > >>> > Thanks, > Hiranya > > > > If this library is good enough, make it part of the Carbon UI > > framework, > > and
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 6:14 PM, Afkham Azeez wrote: > SOAP Tracer is one. I think there is a BPEL editor UI as well. We don't have a BPEL editor UI, but we show BPEL definition as an XML. Therefore, we only need XML syntax hi-lighting and pretty printing. I'm not sure whether we can use EditArea in this case. If possible +1 to integrate it. Thanks, Waruna > > Azeez > > > On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka wrote: > >> Hi Chanaka, >> >> On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: >> >>> Data Services wizard is using the same editor (EditArea). >> >> >> Are there any components that use a different XML editor? If so can we >> switch to EditArea and be done with the old editor once and for all? >> >> Thanks, >> Hiranya >> >> >>> >>> >>> On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe wrote: >>> I think Data services wizard done by Chanaka uses a different xml highlighter. AFAIR esb also uses the same. /sumedha On 7/25/10, Afkham Azeez wrote: > We still have another syntax highlighter which was used earlier and still in > use by at least the SOAP Message Tracer. EditArea seems to be much better > than that one. We need to be careful when using multiple libraries for the > same functionality. I took a look at the license of EditArea, it is LGPL and > is OK to use but the authors notice needs to be published. Have we done > that? > > Azeez > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri wrote: > >> Hi folks, >> >> We had a major requirement in ESB to have real-time syntax highlighting >> for ESB source views(it was a raw text editor at that time :)) for Iridium >> release. So, at that point of time, Carbon UI framework does not have such >> highlighter to suit that requirement. I think, Chanaka dig a round for a >> good solution and he found Editarea[1] and I added it to Carbon UI[2] and >> used in in all ESB XML source view. >> >> However, now it is not just used in ESB but also in most of the other XML >> views in management console (Policy Editor etc.). >> I agree with Azeez that these changes were not properly communicated to >> the >> list :(. Anyway, if we are currently using multiple XML editors in our >> platform (or in most cases, not using any rich editor at all ), we should >> unify it to one editor (may be EditArea or something else). >> >> regards, >> Kasun >> >> [1] >> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >> [2] >> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >> >> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >>> wrote: >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > Hi Kasun, > I accidentally came across this post, > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html , > in your blog. We already use JavaScript libraries that do XML syntax > highlighting. Also, in Carbon, we need to use the same libraries across > all > components. So for instance, when it comes to graph generation or XML > syntax > highlighting etc. we need to stick to a single agreed upon library set. > When > you start using a new library, please let others know about it (perhaps > I > missed that mail). > So does this mean that we are using multiple XML editors in the platform now? If so we need to converge into one. May be Chanaka can shed some light on the matter. IIRC he did the initial work required to integrate EditArea into Carbon. >>> >>> >>> Yes! That was my point. See my earlier reply. AFAIC, there was no mail to >>> carbon-dev about using this library. When you make major platform level >>> decisions like that, you need to inform the list! >>> >>> Thanks, Hiranya > If this library is good enough, make it part of the Carbon UI > framework, > and make sure that all components that do syntax highlighting use the > same > library. We can start by updating the SOAP Tracer syntax highlighting > bit. > > Others please note: you need to inform everybody when you decide to use > a library which implements a cross-cutting concern. One of the greatest
Re: [Carbon-dev] Javascript XML syntax highlighting
SOAP Tracer is one. I think there is a BPEL editor UI as well. Azeez On Sun, Jul 25, 2010 at 5:09 PM, Hiranya Jayathilaka wrote: > Hi Chanaka, > > On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: > >> Data Services wizard is using the same editor (EditArea). > > > Are there any components that use a different XML editor? If so can we > switch to EditArea and be done with the old editor once and for all? > > Thanks, > Hiranya > > >> >> >> On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe wrote: >> >>> I think Data services wizard done by Chanaka uses a different xml >>> highlighter. AFAIR esb also uses the same. >>> /sumedha >>> >>> On 7/25/10, Afkham Azeez wrote: >>> > We still have another syntax highlighter which was used earlier and >>> still in >>> > use by at least the SOAP Message Tracer. EditArea seems to be much >>> better >>> > than that one. We need to be careful when using multiple libraries for >>> the >>> > same functionality. I took a look at the license of EditArea, it is >>> LGPL and >>> > is OK to use but the authors notice needs to be published. Have we done >>> > that? >>> > >>> > Azeez >>> > >>> > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri >>> wrote: >>> > >>> >> Hi folks, >>> >> >>> >> We had a major requirement in ESB to have real-time syntax >>> highlighting >>> >> for ESB source views(it was a raw text editor at that time :)) for >>> Iridium >>> >> release. So, at that point of time, Carbon UI framework does not have >>> such >>> >> highlighter to suit that requirement. I think, Chanaka dig a round for >>> a >>> >> good solution and he found Editarea[1] and I added it to Carbon UI[2] >>> and >>> >> used in in all ESB XML source view. >>> >> >>> >> However, now it is not just used in ESB but also in most of the other >>> XML >>> >> views in management console (Policy Editor etc.). >>> >> I agree with Azeez that these changes were not properly communicated >>> to >>> >> the >>> >> list :(. Anyway, if we are currently using multiple XML editors in our >>> >> platform (or in most cases, not using any rich editor at all ), we >>> should >>> >> unify it to one editor (may be EditArea or something else). >>> >> >>> >> regards, >>> >> Kasun >>> >> >>> >> [1] >>> >> >>> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >>> >> [2] >>> >> >>> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >>> >> >>> >> >>> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez >>> wrote: >>> >> >>> >>> >>> >>> >>> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >>> >>> wrote: >>> >>> >>> >>> >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez >>> wrote: >>> >>> > Hi Kasun, >>> > I accidentally came across this post, >>> > >>> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html >>> , >>> > in your blog. We already use JavaScript libraries that do XML >>> syntax >>> > highlighting. Also, in Carbon, we need to use the same libraries >>> across >>> > all >>> > components. So for instance, when it comes to graph generation or >>> XML >>> > syntax >>> > highlighting etc. we need to stick to a single agreed upon library >>> set. >>> > When >>> > you start using a new library, please let others know about it >>> (perhaps >>> > I >>> > missed that mail). >>> > >>> >>> So does this mean that we are using multiple XML editors in the >>> platform >>> now? If so we need to converge into one. May be Chanaka can shed >>> some >>> light >>> on the matter. IIRC he did the initial work required to integrate >>> EditArea >>> into Carbon. >>> >>> >>> >>> >>> >>> >>> Yes! That was my point. See my earlier reply. AFAIC, there was no >>> mail to >>> >>> carbon-dev about using this library. When you make major platform >>> level >>> >>> decisions like that, you need to inform the list! >>> >>> >>> >>> >>> Thanks, >>> Hiranya >>> >>> >>> > If this library is good enough, make it part of the Carbon UI >>> > framework, >>> > and make sure that all components that do syntax highlighting use >>> the >>> > same >>> > library. We can start by updating the SOAP Tracer syntax >>> highlighting >>> > bit. >>> > >>> > Others please note: you need to inform everybody when you decide to >>> use >>> > a library which implements a cross-cutting concern. One of the >>> greatest >>> > aspects about the Carbon platform is consistency. >>> > >>> > Thanks >>> > -- >>> > Afkham Azeez >>> > Senior Software Architect & Senior Manager; WSO2, Inc.; >>> > http://wso2.com, >>> > Lean . Enterprise . Middleware >>> > Member; Apache Software Foundation; http://www.apache.org/ >>> > email: az...@wso2.com cell: +94 77 3320919 >>> > blog: http://blog.afkham.org >>> > twitter: http://twitter.com/afkham_aze
Re: [Carbon-dev] Javascript XML syntax highlighting
Hi Chanaka, On Sun, Jul 25, 2010 at 4:24 PM, Chanaka Jayasena wrote: > Data Services wizard is using the same editor (EditArea). Are there any components that use a different XML editor? If so can we switch to EditArea and be done with the old editor once and for all? Thanks, Hiranya > > > On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe wrote: > >> I think Data services wizard done by Chanaka uses a different xml >> highlighter. AFAIR esb also uses the same. >> /sumedha >> >> On 7/25/10, Afkham Azeez wrote: >> > We still have another syntax highlighter which was used earlier and >> still in >> > use by at least the SOAP Message Tracer. EditArea seems to be much >> better >> > than that one. We need to be careful when using multiple libraries for >> the >> > same functionality. I took a look at the license of EditArea, it is LGPL >> and >> > is OK to use but the authors notice needs to be published. Have we done >> > that? >> > >> > Azeez >> > >> > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri >> wrote: >> > >> >> Hi folks, >> >> >> >> We had a major requirement in ESB to have real-time syntax >> highlighting >> >> for ESB source views(it was a raw text editor at that time :)) for >> Iridium >> >> release. So, at that point of time, Carbon UI framework does not have >> such >> >> highlighter to suit that requirement. I think, Chanaka dig a round for >> a >> >> good solution and he found Editarea[1] and I added it to Carbon UI[2] >> and >> >> used in in all ESB XML source view. >> >> >> >> However, now it is not just used in ESB but also in most of the other >> XML >> >> views in management console (Policy Editor etc.). >> >> I agree with Azeez that these changes were not properly communicated to >> >> the >> >> list :(. Anyway, if we are currently using multiple XML editors in our >> >> platform (or in most cases, not using any rich editor at all ), we >> should >> >> unify it to one editor (may be EditArea or something else). >> >> >> >> regards, >> >> Kasun >> >> >> >> [1] >> >> >> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >> >> [2] >> >> >> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >> >> >> >> >> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: >> >> >> >>> >> >>> >> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >> >>> wrote: >> >>> >> >> >> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez >> wrote: >> >> > Hi Kasun, >> > I accidentally came across this post, >> > >> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html >> , >> > in your blog. We already use JavaScript libraries that do XML syntax >> > highlighting. Also, in Carbon, we need to use the same libraries >> across >> > all >> > components. So for instance, when it comes to graph generation or >> XML >> > syntax >> > highlighting etc. we need to stick to a single agreed upon library >> set. >> > When >> > you start using a new library, please let others know about it >> (perhaps >> > I >> > missed that mail). >> > >> >> So does this mean that we are using multiple XML editors in the >> platform >> now? If so we need to converge into one. May be Chanaka can shed some >> light >> on the matter. IIRC he did the initial work required to integrate >> EditArea >> into Carbon. >> >> >>> >> >>> >> >>> Yes! That was my point. See my earlier reply. AFAIC, there was no mail >> to >> >>> carbon-dev about using this library. When you make major platform >> level >> >>> decisions like that, you need to inform the list! >> >>> >> >>> >> Thanks, >> Hiranya >> >> >> > If this library is good enough, make it part of the Carbon UI >> > framework, >> > and make sure that all components that do syntax highlighting use >> the >> > same >> > library. We can start by updating the SOAP Tracer syntax >> highlighting >> > bit. >> > >> > Others please note: you need to inform everybody when you decide to >> use >> > a library which implements a cross-cutting concern. One of the >> greatest >> > aspects about the Carbon platform is consistency. >> > >> > Thanks >> > -- >> > Afkham Azeez >> > Senior Software Architect & Senior Manager; WSO2, Inc.; >> > http://wso2.com, >> > Lean . Enterprise . Middleware >> > Member; Apache Software Foundation; http://www.apache.org/ >> > email: az...@wso2.com cell: +94 77 3320919 >> > blog: http://blog.afkham.org >> > twitter: http://twitter.com/afkham_azeez >> > linked-in: http://lk.linkedin.com/in/afkhamazeez >> > >> > ___ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> >> >> -- >> >>
Re: [Carbon-dev] Javascript XML syntax highlighting
Data Services wizard is using the same editor (EditArea). On Sun, Jul 25, 2010 at 3:22 PM, Sumedha Rubasinghe wrote: > I think Data services wizard done by Chanaka uses a different xml > highlighter. AFAIR esb also uses the same. > /sumedha > > On 7/25/10, Afkham Azeez wrote: > > We still have another syntax highlighter which was used earlier and still > in > > use by at least the SOAP Message Tracer. EditArea seems to be much better > > than that one. We need to be careful when using multiple libraries for > the > > same functionality. I took a look at the license of EditArea, it is LGPL > and > > is OK to use but the authors notice needs to be published. Have we done > > that? > > > > Azeez > > > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri > wrote: > > > >> Hi folks, > >> > >> We had a major requirement in ESB to have real-time syntax highlighting > >> for ESB source views(it was a raw text editor at that time :)) for > Iridium > >> release. So, at that point of time, Carbon UI framework does not have > such > >> highlighter to suit that requirement. I think, Chanaka dig a round for a > >> good solution and he found Editarea[1] and I added it to Carbon UI[2] > and > >> used in in all ESB XML source view. > >> > >> However, now it is not just used in ESB but also in most of the other > XML > >> views in management console (Policy Editor etc.). > >> I agree with Azeez that these changes were not properly communicated to > >> the > >> list :(. Anyway, if we are currently using multiple XML editors in our > >> platform (or in most cases, not using any rich editor at all ), we > should > >> unify it to one editor (may be EditArea or something else). > >> > >> regards, > >> Kasun > >> > >> [1] > >> > http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 > >> [2] > >> > https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea > >> > >> > >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: > >> > >>> > >>> > >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka > >>> wrote: > >>> > > > On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > > > Hi Kasun, > > I accidentally came across this post, > > > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html > , > > in your blog. We already use JavaScript libraries that do XML syntax > > highlighting. Also, in Carbon, we need to use the same libraries > across > > all > > components. So for instance, when it comes to graph generation or XML > > syntax > > highlighting etc. we need to stick to a single agreed upon library > set. > > When > > you start using a new library, please let others know about it > (perhaps > > I > > missed that mail). > > > > So does this mean that we are using multiple XML editors in the > platform > now? If so we need to converge into one. May be Chanaka can shed some > light > on the matter. IIRC he did the initial work required to integrate > EditArea > into Carbon. > > >>> > >>> > >>> Yes! That was my point. See my earlier reply. AFAIC, there was no mail > to > >>> carbon-dev about using this library. When you make major platform level > >>> decisions like that, you need to inform the list! > >>> > >>> > Thanks, > Hiranya > > > > If this library is good enough, make it part of the Carbon UI > > framework, > > and make sure that all components that do syntax highlighting use the > > same > > library. We can start by updating the SOAP Tracer syntax highlighting > > bit. > > > > Others please note: you need to inform everybody when you decide to > use > > a library which implements a cross-cutting concern. One of the > greatest > > aspects about the Carbon platform is consistency. > > > > Thanks > > -- > > Afkham Azeez > > Senior Software Architect & Senior Manager; WSO2, Inc.; > > http://wso2.com, > > Lean . Enterprise . Middleware > > Member; Apache Software Foundation; http://www.apache.org/ > > email: az...@wso2.com cell: +94 77 3320919 > > blog: http://blog.afkham.org > > twitter: http://twitter.com/afkham_azeez > > linked-in: http://lk.linkedin.com/in/afkhamazeez > > > > ___ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > >>
Re: [Carbon-dev] Javascript XML syntax highlighting
I think Data services wizard done by Chanaka uses a different xml highlighter. AFAIR esb also uses the same. /sumedha On 7/25/10, Afkham Azeez wrote: > We still have another syntax highlighter which was used earlier and still in > use by at least the SOAP Message Tracer. EditArea seems to be much better > than that one. We need to be careful when using multiple libraries for the > same functionality. I took a look at the license of EditArea, it is LGPL and > is OK to use but the authors notice needs to be published. Have we done > that? > > Azeez > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri wrote: > >> Hi folks, >> >> We had a major requirement in ESB to have real-time syntax highlighting >> for ESB source views(it was a raw text editor at that time :)) for Iridium >> release. So, at that point of time, Carbon UI framework does not have such >> highlighter to suit that requirement. I think, Chanaka dig a round for a >> good solution and he found Editarea[1] and I added it to Carbon UI[2] and >> used in in all ESB XML source view. >> >> However, now it is not just used in ESB but also in most of the other XML >> views in management console (Policy Editor etc.). >> I agree with Azeez that these changes were not properly communicated to >> the >> list :(. Anyway, if we are currently using multiple XML editors in our >> platform (or in most cases, not using any rich editor at all ), we should >> unify it to one editor (may be EditArea or something else). >> >> regards, >> Kasun >> >> [1] >> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >> [2] >> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >> >> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >>> wrote: >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > Hi Kasun, > I accidentally came across this post, > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, > in your blog. We already use JavaScript libraries that do XML syntax > highlighting. Also, in Carbon, we need to use the same libraries across > all > components. So for instance, when it comes to graph generation or XML > syntax > highlighting etc. we need to stick to a single agreed upon library set. > When > you start using a new library, please let others know about it (perhaps > I > missed that mail). > So does this mean that we are using multiple XML editors in the platform now? If so we need to converge into one. May be Chanaka can shed some light on the matter. IIRC he did the initial work required to integrate EditArea into Carbon. >>> >>> >>> Yes! That was my point. See my earlier reply. AFAIC, there was no mail to >>> carbon-dev about using this library. When you make major platform level >>> decisions like that, you need to inform the list! >>> >>> Thanks, Hiranya > If this library is good enough, make it part of the Carbon UI > framework, > and make sure that all components that do syntax highlighting use the > same > library. We can start by updating the SOAP Tracer syntax highlighting > bit. > > Others please note: you need to inform everybody when you decide to use > a library which implements a cross-cutting concern. One of the greatest > aspects about the Carbon platform is consistency. > > Thanks > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; > http://wso2.com, > Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> -- >>> Afkham Azeez >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >>> Lean . Enterprise . Middleware >>> Member; Apache Software Foundation; http://www.apache.org/ >>> email: az...@wso2.com cell: +94 77 3320919 >>> blog: http://blog.afkham.org >>> twitter: http://twitter.com/afkham_azeez >>> linked-in: http://lk.linkedin.com/in/afkhamazeez >>> >>> ___
Re: [Carbon-dev] Javascript XML syntax highlighting
I think it has released under Apache license too[1]. "EditArea is released under "LGPL", "Apache" and "BSD" licenses, which mean that you can use EditArea if you follow at least one of thoses licenses." [1] http://www.cdolivet.com/editarea/editarea/docs/license.html On Sun, Jul 25, 2010 at 1:37 PM, Afkham Azeez wrote: > We still have another syntax highlighter which was used earlier and still > in use by at least the SOAP Message Tracer. EditArea seems to be much better > than that one. We need to be careful when using multiple libraries for the > same functionality. I took a look at the license of EditArea, it is LGPL and > is OK to use but the authors notice needs to be published. Have we done > that? > > Azeez > > On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri wrote: > >> Hi folks, >> >> We had a major requirement in ESB to have real-time syntax highlighting >> for ESB source views(it was a raw text editor at that time :)) for Iridium >> release. So, at that point of time, Carbon UI framework does not have such >> highlighter to suit that requirement. I think, Chanaka dig a round for a >> good solution and he found Editarea[1] and I added it to Carbon UI[2] and >> used in in all ESB XML source view. >> >> However, now it is not just used in ESB but also in most of the other XML >> views in management console (Policy Editor etc.). >> I agree with Azeez that these changes were not properly communicated to >> the list :(. Anyway, if we are currently using multiple XML editors in our >> platform (or in most cases, not using any rich editor at all ), we should >> unify it to one editor (may be EditArea or something else). >> >> regards, >> Kasun >> >> [1] >> http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 >> [2] >> https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea >> >> >> On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >>> wrote: >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > Hi Kasun, > I accidentally came across this post, > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, > in your blog. We already use JavaScript libraries that do XML syntax > highlighting. Also, in Carbon, we need to use the same libraries across > all > components. So for instance, when it comes to graph generation or XML > syntax > highlighting etc. we need to stick to a single agreed upon library set. > When > you start using a new library, please let others know about it (perhaps I > missed that mail). > So does this mean that we are using multiple XML editors in the platform now? If so we need to converge into one. May be Chanaka can shed some light on the matter. IIRC he did the initial work required to integrate EditArea into Carbon. >>> >>> >>> Yes! That was my point. See my earlier reply. AFAIC, there was no mail to >>> carbon-dev about using this library. When you make major platform level >>> decisions like that, you need to inform the list! >>> >>> Thanks, Hiranya > If this library is good enough, make it part of the Carbon UI > framework, and make sure that all components that do syntax highlighting > use > the same library. We can start by updating the SOAP Tracer > syntax highlighting bit. > > Others please note: you need to inform everybody when you decide to use > a library which implements a cross-cutting concern. One of the greatest > aspects about the Carbon platform is consistency. > > Thanks > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; > http://wso2.com, Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> -- >>> Afkham Azeez >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >>> Lean . Enterprise . Middleware >>> Member; Apache Software Foundation; http://www.apache.org/ >>> email: az...@wso2.com cell: +94 77 3320919 >>> blog: http://blog.a
Re: [Carbon-dev] Javascript XML syntax highlighting
We still have another syntax highlighter which was used earlier and still in use by at least the SOAP Message Tracer. EditArea seems to be much better than that one. We need to be careful when using multiple libraries for the same functionality. I took a look at the license of EditArea, it is LGPL and is OK to use but the authors notice needs to be published. Have we done that? Azeez On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri wrote: > Hi folks, > > We had a major requirement in ESB to have real-time syntax highlighting > for ESB source views(it was a raw text editor at that time :)) for Iridium > release. So, at that point of time, Carbon UI framework does not have such > highlighter to suit that requirement. I think, Chanaka dig a round for a > good solution and he found Editarea[1] and I added it to Carbon UI[2] and > used in in all ESB XML source view. > > However, now it is not just used in ESB but also in most of the other XML > views in management console (Policy Editor etc.). > I agree with Azeez that these changes were not properly communicated to the > list :(. Anyway, if we are currently using multiple XML editors in our > platform (or in most cases, not using any rich editor at all ), we should > unify it to one editor (may be EditArea or something else). > > regards, > Kasun > > [1] > http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 > [2] > https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea > > > On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: > >> >> >> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >> wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: >>> Hi Kasun, I accidentally came across this post, http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, in your blog. We already use JavaScript libraries that do XML syntax highlighting. Also, in Carbon, we need to use the same libraries across all components. So for instance, when it comes to graph generation or XML syntax highlighting etc. we need to stick to a single agreed upon library set. When you start using a new library, please let others know about it (perhaps I missed that mail). >>> >>> So does this mean that we are using multiple XML editors in the platform >>> now? If so we need to converge into one. May be Chanaka can shed some light >>> on the matter. IIRC he did the initial work required to integrate EditArea >>> into Carbon. >>> >> >> >> Yes! That was my point. See my earlier reply. AFAIC, there was no mail to >> carbon-dev about using this library. When you make major platform level >> decisions like that, you need to inform the list! >> >> >>> Thanks, >>> Hiranya >>> >>> If this library is good enough, make it part of the Carbon UI framework, and make sure that all components that do syntax highlighting use the same library. We can start by updating the SOAP Tracer syntax highlighting bit. Others please note: you need to inform everybody when you decide to use a library which implements a cross-cutting concern. One of the greatest aspects about the Carbon platform is consistency. Thanks -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Senior Software Engineer; >>> WSO2 Inc.; http://wso2.org >>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: az...@wso2.com cell: +94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Kasun Indrasiri > Senior Software Engineer > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 71 536 4128 > Blog : http://kasunpanorama.blogspot.com/ > > __
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 12:17 PM, Kasun Indrasiri wrote: > Hi folks, > > We had a major requirement in ESB to have real-time syntax highlighting > for ESB source views(it was a raw text editor at that time :)) for Iridium > release. So, at that point of time, Carbon UI framework does not have such > highlighter to suit that requirement. I think, Chanaka dig a round for a > good solution and he found Editarea[1] and I added it to Carbon UI[2] and > used in in all ESB XML source view. > > However, now it is not just used in ESB but also in most of the other XML > views in management console (Policy Editor etc.). > I agree with Azeez that these changes were not properly communicated to the > list :(. Anyway, if we are currently using multiple XML editors in our > platform (or in most cases, not using any rich editor at all ), we should > unify it to one editor (may be EditArea or something else). > I believe that the older editors used did have noticeable limitations. So, may be we need to switch to EditArea. Chanaka please shed some light. Also, we cannot afford to keep changing editors, per release. Therefore, we might need to come up with a capability criteria that we expect from a XML editor, and maintain some document that lists it. If we need some new capability that the current editor does not support, we then can find a new editor. Thanks, Senaka. > > regards, > Kasun > > [1] > http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 > [2] > https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea > > > On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: > >> >> >> On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka >> wrote: >> >>> >>> >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: >>> Hi Kasun, I accidentally came across this post, http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, in your blog. We already use JavaScript libraries that do XML syntax highlighting. Also, in Carbon, we need to use the same libraries across all components. So for instance, when it comes to graph generation or XML syntax highlighting etc. we need to stick to a single agreed upon library set. When you start using a new library, please let others know about it (perhaps I missed that mail). >>> >>> So does this mean that we are using multiple XML editors in the platform >>> now? If so we need to converge into one. May be Chanaka can shed some light >>> on the matter. IIRC he did the initial work required to integrate EditArea >>> into Carbon. >>> >> >> >> Yes! That was my point. See my earlier reply. AFAIC, there was no mail to >> carbon-dev about using this library. When you make major platform level >> decisions like that, you need to inform the list! >> >> >>> Thanks, >>> Hiranya >>> >>> If this library is good enough, make it part of the Carbon UI framework, and make sure that all components that do syntax highlighting use the same library. We can start by updating the SOAP Tracer syntax highlighting bit. Others please note: you need to inform everybody when you decide to use a library which implements a cross-cutting concern. One of the greatest aspects about the Carbon platform is consistency. Thanks -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Senior Software Engineer; >>> WSO2 Inc.; http://wso2.org >>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>> Blog: http://techfeast-hiranya.blogspot.com >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: az...@wso2.com cell: +94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Kasun Indrasiri > Senior Software Engineer > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > c
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 11:15 AM, Afkham Azeez wrote: > Then the old JavaScript libraries should have been scrapped, and all the > components that use those should have been updated. It seems the UI > framework is gathering a lot of garbage that never gets thrown out. I too agree. Another aspect is the duplication of code. For example, try "locate ns-editor | grep carbon-trunk | grep -v .svn | grep -v target" on a Linux machine. You see three different locations with the same code. We need to refactor the UI and get rid of these garbage code, and also reduce duplication, which will improve maintainability. > Azeez > > > On Sun, Jul 25, 2010 at 11:07 AM, Hiranya Jayathilaka wrote: > >> >> >> On Sun, Jul 25, 2010 at 1:35 AM, Afkham Azeez wrote: >> >>> Going through the commit logs & JIRAs, I found that at some point in >>> time, somebody has decided to switch to EditArea XML editor/syntax >>> highlighter. >> >> >> H This isn't exactly news. One of the UI improvements we did for >> the Iridium release was integrating this new XML editor into our UI system. >> As a result almost all the XML editor UIs were updated. And I think it was >> done in multiple products, not just in the ESB. The necessary libraries etc >> come from the Carbon core so it is available across the entire platform. >> > Yes. Even the UIs of G-Reg have been updated to use this editor. Thanks, Senaka. > >> Thanks, >> Hiranya >> >> >> >>> Please inform everybody else when you make such a cross cutting decision, >>> and make sure that all relevant code which are affected by that concern get >>> updated. >>> >>> Azeez >>> >>> >>> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: >>> Hi Kasun, I accidentally came across this post, http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, in your blog. We already use JavaScript libraries that do XML syntax highlighting. Also, in Carbon, we need to use the same libraries across all components. So for instance, when it comes to graph generation or XML syntax highlighting etc. we need to stick to a single agreed upon library set. When you start using a new library, please let others know about it (perhaps I missed that mail). If this library is good enough, make it part of the Carbon UI framework, and make sure that all components that do syntax highlighting use the same library. We can start by updating the SOAP Tracer syntax highlighting bit. Others please note: you need to inform everybody when you decide to use a library which implements a cross-cutting concern. One of the greatest aspects about the Carbon platform is consistency. Thanks -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez >>> >>> >>> >>> -- >>> Afkham Azeez >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >>> Lean . Enterprise . Middleware >>> Member; Apache Software Foundation; http://www.apache.org/ >>> email: az...@wso2.com cell: +94 77 3320919 >>> blog: http://blog.afkham.org >>> twitter: http://twitter.com/afkham_azeez >>> linked-in: http://lk.linkedin.com/in/afkhamazeez >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Senaka Fernando Associate Technical Lead WSO2 Inc. E-mail: senaka AT wso2.com; Mobile: +94 77 322 1818 http://www.wso2.com/ - "Lean . Enterprise . Middleware" ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
Hi folks, We had a major requirement in ESB to have real-time syntax highlighting for ESB source views(it was a raw text editor at that time :)) for Iridium release. So, at that point of time, Carbon UI framework does not have such highlighter to suit that requirement. I think, Chanaka dig a round for a good solution and he found Editarea[1] and I added it to Carbon UI[2] and used in in all ESB XML source view. However, now it is not just used in ESB but also in most of the other XML views in management console (Policy Editor etc.). I agree with Azeez that these changes were not properly communicated to the list :(. Anyway, if we are currently using multiple XML editors in our platform (or in most cases, not using any rich editor at all ), we should unify it to one editor (may be EditArea or something else). regards, Kasun [1] http://www.cdolivet.com/index.php?page=editArea&sess=af96897233104c82227a66378ea17ef7 [2] https://svn.wso2.org/repos/wso2/trunk/carbon/core/org.wso2.carbon.ui/src/main/resources/web/editarea On Sun, Jul 25, 2010 at 11:17 AM, Afkham Azeez wrote: > > > On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka wrote: > >> >> >> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: >> >>> Hi Kasun, >>> I accidentally came across this post, >>> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, >>> in your blog. We already use JavaScript libraries that do XML syntax >>> highlighting. Also, in Carbon, we need to use the same libraries across all >>> components. So for instance, when it comes to graph generation or XML syntax >>> highlighting etc. we need to stick to a single agreed upon library set. When >>> you start using a new library, please let others know about it (perhaps I >>> missed that mail). >>> >> >> So does this mean that we are using multiple XML editors in the platform >> now? If so we need to converge into one. May be Chanaka can shed some light >> on the matter. IIRC he did the initial work required to integrate EditArea >> into Carbon. >> > > > Yes! That was my point. See my earlier reply. AFAIC, there was no mail to > carbon-dev about using this library. When you make major platform level > decisions like that, you need to inform the list! > > >> Thanks, >> Hiranya >> >> >>> If this library is good enough, make it part of the Carbon UI framework, >>> and make sure that all components that do syntax highlighting use the same >>> library. We can start by updating the SOAP Tracer syntax highlighting bit. >>> >>> Others please note: you need to inform everybody when you decide to use a >>> library which implements a cross-cutting concern. One of the greatest >>> aspects about the Carbon platform is consistency. >>> >>> Thanks >>> -- >>> Afkham Azeez >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >>> Lean . Enterprise . Middleware >>> Member; Apache Software Foundation; http://www.apache.org/ >>> email: az...@wso2.com cell: +94 77 3320919 >>> blog: http://blog.afkham.org >>> twitter: http://twitter.com/afkham_azeez >>> linked-in: http://lk.linkedin.com/in/afkhamazeez >>> >>> ___ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Kasun Indrasiri Senior Software Engineer WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 11:15 AM, Hiranya Jayathilaka wrote: > > > On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > >> Hi Kasun, >> I accidentally came across this post, >> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, >> in your blog. We already use JavaScript libraries that do XML syntax >> highlighting. Also, in Carbon, we need to use the same libraries across all >> components. So for instance, when it comes to graph generation or XML syntax >> highlighting etc. we need to stick to a single agreed upon library set. When >> you start using a new library, please let others know about it (perhaps I >> missed that mail). >> > > So does this mean that we are using multiple XML editors in the platform > now? If so we need to converge into one. May be Chanaka can shed some light > on the matter. IIRC he did the initial work required to integrate EditArea > into Carbon. > Yes! That was my point. See my earlier reply. AFAIC, there was no mail to carbon-dev about using this library. When you make major platform level decisions like that, you need to inform the list! > Thanks, > Hiranya > > >> If this library is good enough, make it part of the Carbon UI framework, >> and make sure that all components that do syntax highlighting use the same >> library. We can start by updating the SOAP Tracer syntax highlighting bit. >> >> Others please note: you need to inform everybody when you decide to use a >> library which implements a cross-cutting concern. One of the greatest >> aspects about the Carbon platform is consistency. >> >> Thanks >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: az...@wso2.com cell: +94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
Then the old JavaScript libraries should have been scrapped, and all the components that use those should have been updated. It seems the UI framework is gathering a lot of garbage that never gets thrown out. Azeez On Sun, Jul 25, 2010 at 11:07 AM, Hiranya Jayathilaka wrote: > > > On Sun, Jul 25, 2010 at 1:35 AM, Afkham Azeez wrote: > >> Going through the commit logs & JIRAs, I found that at some point in time, >> somebody has decided to switch to EditArea XML editor/syntax highlighter. > > > H This isn't exactly news. One of the UI improvements we did for > the Iridium release was integrating this new XML editor into our UI system. > As a result almost all the XML editor UIs were updated. And I think it was > done in multiple products, not just in the ESB. The necessary libraries etc > come from the Carbon core so it is available across the entire platform. > > Thanks, > Hiranya > > > >> Please inform everybody else when you make such a cross cutting decision, >> and make sure that all relevant code which are affected by that concern get >> updated. >> >> Azeez >> >> >> On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: >> >>> Hi Kasun, >>> I accidentally came across this post, >>> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, >>> in your blog. We already use JavaScript libraries that do XML syntax >>> highlighting. Also, in Carbon, we need to use the same libraries across all >>> components. So for instance, when it comes to graph generation or XML syntax >>> highlighting etc. we need to stick to a single agreed upon library set. When >>> you start using a new library, please let others know about it (perhaps I >>> missed that mail). If this library is good enough, make it part of the >>> Carbon UI framework, and make sure that all components that do syntax >>> highlighting use the same library. We can start by updating the SOAP Tracer >>> syntax highlighting bit. >>> >>> Others please note: you need to inform everybody when you decide to use a >>> library which implements a cross-cutting concern. One of the greatest >>> aspects about the Carbon platform is consistency. >>> >>> Thanks >>> -- >>> Afkham Azeez >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >>> Lean . Enterprise . Middleware >>> Member; Apache Software Foundation; http://www.apache.org/ >>> email: az...@wso2.com cell: +94 77 3320919 >>> blog: http://blog.afkham.org >>> twitter: http://twitter.com/afkham_azeez >>> linked-in: http://lk.linkedin.com/in/afkhamazeez >>> >> >> >> >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: az...@wso2.com cell: +94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > Hi Kasun, > I accidentally came across this post, > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, > in your blog. We already use JavaScript libraries that do XML syntax > highlighting. Also, in Carbon, we need to use the same libraries across all > components. So for instance, when it comes to graph generation or XML syntax > highlighting etc. we need to stick to a single agreed upon library set. When > you start using a new library, please let others know about it (perhaps I > missed that mail). > So does this mean that we are using multiple XML editors in the platform now? If so we need to converge into one. May be Chanaka can shed some light on the matter. IIRC he did the initial work required to integrate EditArea into Carbon. Thanks, Hiranya > If this library is good enough, make it part of the Carbon UI framework, > and make sure that all components that do syntax highlighting use the same > library. We can start by updating the SOAP Tracer syntax highlighting bit. > > Others please note: you need to inform everybody when you decide to use a > library which implements a cross-cutting concern. One of the greatest > aspects about the Carbon platform is consistency. > > Thanks > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
On Sun, Jul 25, 2010 at 1:35 AM, Afkham Azeez wrote: > Going through the commit logs & JIRAs, I found that at some point in time, > somebody has decided to switch to EditArea XML editor/syntax highlighter. H This isn't exactly news. One of the UI improvements we did for the Iridium release was integrating this new XML editor into our UI system. As a result almost all the XML editor UIs were updated. And I think it was done in multiple products, not just in the ESB. The necessary libraries etc come from the Carbon core so it is available across the entire platform. Thanks, Hiranya > Please inform everybody else when you make such a cross cutting decision, > and make sure that all relevant code which are affected by that concern get > updated. > > Azeez > > > On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > >> Hi Kasun, >> I accidentally came across this post, >> http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, >> in your blog. We already use JavaScript libraries that do XML syntax >> highlighting. Also, in Carbon, we need to use the same libraries across all >> components. So for instance, when it comes to graph generation or XML syntax >> highlighting etc. we need to stick to a single agreed upon library set. When >> you start using a new library, please let others know about it (perhaps I >> missed that mail). If this library is good enough, make it part of the >> Carbon UI framework, and make sure that all components that do syntax >> highlighting use the same library. We can start by updating the SOAP Tracer >> syntax highlighting bit. >> >> Others please note: you need to inform everybody when you decide to use a >> library which implements a cross-cutting concern. One of the greatest >> aspects about the Carbon platform is consistency. >> >> Thanks >> -- >> Afkham Azeez >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> Lean . Enterprise . Middleware >> Member; Apache Software Foundation; http://www.apache.org/ >> email: az...@wso2.com cell: +94 77 3320919 >> blog: http://blog.afkham.org >> twitter: http://twitter.com/afkham_azeez >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> > > > > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Senior Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Javascript XML syntax highlighting
Going through the commit logs & JIRAs, I found that at some point in time, somebody has decided to switch to EditArea XML editor/syntax highlighter. Please inform everybody else when you make such a cross cutting decision, and make sure that all relevant code which are affected by that concern get updated. Azeez On Sun, Jul 25, 2010 at 1:29 AM, Afkham Azeez wrote: > Hi Kasun, > I accidentally came across this post, > http://kasunpanorama.blogspot.com/2010/03/real-time-xml-syntax-highlighter-in.html, > in your blog. We already use JavaScript libraries that do XML syntax > highlighting. Also, in Carbon, we need to use the same libraries across all > components. So for instance, when it comes to graph generation or XML syntax > highlighting etc. we need to stick to a single agreed upon library set. When > you start using a new library, please let others know about it (perhaps I > missed that mail). If this library is good enough, make it part of the > Carbon UI framework, and make sure that all components that do syntax > highlighting use the same library. We can start by updating the SOAP Tracer > syntax highlighting bit. > > Others please note: you need to inform everybody when you decide to use a > library which implements a cross-cutting concern. One of the greatest > aspects about the Carbon platform is consistency. > > Thanks > -- > Afkham Azeez > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, > Lean . Enterprise . Middleware > Member; Apache Software Foundation; http://www.apache.org/ > email: az...@wso2.com cell: +94 77 3320919 > blog: http://blog.afkham.org > twitter: http://twitter.com/afkham_azeez > linked-in: http://lk.linkedin.com/in/afkhamazeez > -- Afkham Azeez Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, Lean . Enterprise . Middleware Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
