Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Thank you.

hope this works out.
If there is anything I can do, please ask.

Kureem


On 5 September 2013 16:55, Christian Grobmeier  wrote:

> Perfect!
>
> I will now ask on the Struts list if there are some people interested
>
> Thanks!
>
> Am 05.09.13 14:42, schrieb Kureem Rossaye:
> > Done!
> > Kureem
> > Am 05.09.13 07:09, schrieb Kureem Rossaye:
> >> Thank you very much,
> >> I have not included the proposal to the Incubator wiki yet.
> >> How can I do that?
> > Create an account here:
> > http://wiki.apache.org/incubator/
> >
> > Then mail your username to this list, askinf for access. You'll be
> > granted then.
> >
> > Then you can add your proposal here:
> > http://wiki.apache.org/incubator/ProjectProposals
> >
> > I assume you know this link already:
> > http://incubator.apache.org/guides/proposal.html
> >
> > Please try to make the proposal look similar to the others on the wiki.
> >
> > Cheers!
> >
> >
> > On 5 September 2013 12:47, Christian Grobmeier 
> wrote:
> >
> >> Am 05.09.13 07:09, schrieb Kureem Rossaye:
> >>> Thank you very much,
> >>> I have not included the proposal to the Incubator wiki yet.
> >>> How can I do that?
> >> Create an account here:
> >> http://wiki.apache.org/incubator/
> >>
> >> Then mail your username to this list, askinf for access. You'll be
> >> granted then.
> >>
> >> Then you can add your proposal here:
> >> http://wiki.apache.org/incubator/ProjectProposals
> >>
> >> I assume you know this link already:
> >> http://incubator.apache.org/guides/proposal.html
> >>
> >> Please try to make the proposal look similar to the others on the wiki.
> >>
> >> Cheers!
> >>
> >> Christian
> >>> Thanks
> >>> Kureem
> >>>
> >>>
> >>> On 5 September 2013 00:09, Christian Grobmeier 
> >> wrote:
>  Nice!
> 
>  Have you included your proposal to the Incubator wiki?
>  I would like to forward it to the Struts team, some might be
> interested.
> 
>  I have no time to actually code, but I might help with incubation
>  (mentoring or championing). Before deciding on that, I would like to
>  hear if there is interest of others here.
> 
>  Am 04.09.13 15:04, schrieb Kureem Rossaye:
> > "*once could use Castafiore
> > in conjunction with Struts. In other terms, Castafiore could be used
> as
> > a Struts plugin which then calls Struts Actions and replaces Tiles,
> JSP
> > whatever. Is that correct?*"
> >
> > Correct!
> > Actually I myself did not get the idea that it could be used like
> that.
>  Yes
> > it can be used like that.
> > Actually, a castafiore application (which can be a simple table) can
> be
> > included on a page using a simple javascript or a jsp tag. So why
> not a
> > struts plugin.
> > Actually I have tried it as an echo2 framework component. It works
> just
> > nice.
> >
> >
> > Thanks for your interest
> >
> > Ragards,
> > Kureem
> >
> >
> > On 4 September 2013 15:32, Christian Grobmeier 
>  wrote:
> >> Kureem,
> >>
> >> this sounds nice. As far as I understood it, once could use
> Castafiore
> >> in conjunction with Struts. In other terms, Castafiore could be used
> >> as
> >> a Struts plugin which then calls Struts Actions and replaces Tiles,
> >> JSP
> >> whatever. Is that correct?
> >>
> >> Cheers
> >>
> >>
> >>
> >> Am 04.09.13 10:01, schrieb Kureem Rossaye:
> >>> Hi,
> >>> Indeed, I have read the incubation proposal guide. The only thing I
>  could
> >>> not figure out is how to recruit a champion.
> >>> However, after re-reading the guide, I missed something. I should
> >> have
> >>> prefixed the subject of the mail with [PROPOSAL]. So I am resending
> >> the
> >>> proposal with the proper subject.
> >>>
> >>>
> >> **
> >>> PROPOSAL
> >>> Abstract
> >>>
> >>> Castafiore framework is a web frameworks, fully component oriented,
>  ajax
> >>> based, one page appplication. Although the framework can be viewed
> >> as a
> >>> classical component oriented web framework like GWT, it has been
>  designed
> >>> and implemented with a particular goal in mind. It is to be able to
>  make
> >>> existing javascript libraries "java-able". Meaning that the
> framework
> >>> allows to easily take a javascript library like e.g jquery ui and
> use
>  the
> >>> components and features via java. The integration of the javascript
> >>> libraries need to be easy and natural.
> >>>
> >>> Actually companies like ext js and smartgwt have made their
> >> components
> >>> "java-able" using GWT. I wish to provide an alternative to gwt that
> >> is
> >> much
> >>> easier, fast, lightweight, and much more productive.
> >>> Proposal
> >>>
> >>> Castafiore framework has been designed and implemented with the
>  follo

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Christian Grobmeier]

Perfect!

I will now ask on the Struts list if there are some people interested

Thanks!

Am 05.09.13 14:42, schrieb Kureem Rossaye:
> Done!
> Kureem
> Am 05.09.13 07:09, schrieb Kureem Rossaye:
>> Thank you very much,
>> I have not included the proposal to the Incubator wiki yet.
>> How can I do that?
> Create an account here:
> http://wiki.apache.org/incubator/
>
> Then mail your username to this list, askinf for access. You'll be
> granted then.
>
> Then you can add your proposal here:
> http://wiki.apache.org/incubator/ProjectProposals
>
> I assume you know this link already:
> http://incubator.apache.org/guides/proposal.html
>
> Please try to make the proposal look similar to the others on the wiki.
>
> Cheers!
>
>
> On 5 September 2013 12:47, Christian Grobmeier  wrote:
>
>> Am 05.09.13 07:09, schrieb Kureem Rossaye:
>>> Thank you very much,
>>> I have not included the proposal to the Incubator wiki yet.
>>> How can I do that?
>> Create an account here:
>> http://wiki.apache.org/incubator/
>>
>> Then mail your username to this list, askinf for access. You'll be
>> granted then.
>>
>> Then you can add your proposal here:
>> http://wiki.apache.org/incubator/ProjectProposals
>>
>> I assume you know this link already:
>> http://incubator.apache.org/guides/proposal.html
>>
>> Please try to make the proposal look similar to the others on the wiki.
>>
>> Cheers!
>>
>> Christian
>>> Thanks
>>> Kureem
>>>
>>>
>>> On 5 September 2013 00:09, Christian Grobmeier 
>> wrote:
 Nice!

 Have you included your proposal to the Incubator wiki?
 I would like to forward it to the Struts team, some might be interested.

 I have no time to actually code, but I might help with incubation
 (mentoring or championing). Before deciding on that, I would like to
 hear if there is interest of others here.

 Am 04.09.13 15:04, schrieb Kureem Rossaye:
> "*once could use Castafiore
> in conjunction with Struts. In other terms, Castafiore could be used as
> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> whatever. Is that correct?*"
>
> Correct!
> Actually I myself did not get the idea that it could be used like that.
 Yes
> it can be used like that.
> Actually, a castafiore application (which can be a simple table) can be
> included on a page using a simple javascript or a jsp tag. So why not a
> struts plugin.
> Actually I have tried it as an echo2 framework component. It works just
> nice.
>
>
> Thanks for your interest
>
> Ragards,
> Kureem
>
>
> On 4 September 2013 15:32, Christian Grobmeier 
 wrote:
>> Kureem,
>>
>> this sounds nice. As far as I understood it, once could use Castafiore
>> in conjunction with Struts. In other terms, Castafiore could be used
>> as
>> a Struts plugin which then calls Struts Actions and replaces Tiles,
>> JSP
>> whatever. Is that correct?
>>
>> Cheers
>>
>>
>>
>> Am 04.09.13 10:01, schrieb Kureem Rossaye:
>>> Hi,
>>> Indeed, I have read the incubation proposal guide. The only thing I
 could
>>> not figure out is how to recruit a champion.
>>> However, after re-reading the guide, I missed something. I should
>> have
>>> prefixed the subject of the mail with [PROPOSAL]. So I am resending
>> the
>>> proposal with the proper subject.
>>>
>>>
>> **
>>> PROPOSAL
>>> Abstract
>>>
>>> Castafiore framework is a web frameworks, fully component oriented,
 ajax
>>> based, one page appplication. Although the framework can be viewed
>> as a
>>> classical component oriented web framework like GWT, it has been
 designed
>>> and implemented with a particular goal in mind. It is to be able to
 make
>>> existing javascript libraries "java-able". Meaning that the framework
>>> allows to easily take a javascript library like e.g jquery ui and use
 the
>>> components and features via java. The integration of the javascript
>>> libraries need to be easy and natural.
>>>
>>> Actually companies like ext js and smartgwt have made their
>> components
>>> "java-able" using GWT. I wish to provide an alternative to gwt that
>> is
>> much
>>> easier, fast, lightweight, and much more productive.
>>> Proposal
>>>
>>> Castafiore framework has been designed and implemented with the
 following
>>> goals in mind
>>>
>>>1.
>>>
>>>Fully object oriented
>>>2.
>>>
>>>Simple API that is very close to html itself
>>>We wanted an API that is closer to html markup and javascripts
>> event
>>>model. I believe that this would help web developers easily
 visualize
>> the
>>>rendering when reading source code.
>>>3.
>>>
>>>Write a full application 

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Done!
Kureem
Am 05.09.13 07:09, schrieb Kureem Rossaye:
> Thank you very much,
> I have not included the proposal to the Incubator wiki yet.
> How can I do that?
Create an account here:
http://wiki.apache.org/incubator/

Then mail your username to this list, askinf for access. You'll be
granted then.

Then you can add your proposal here:
http://wiki.apache.org/incubator/ProjectProposals

I assume you know this link already:
http://incubator.apache.org/guides/proposal.html

Please try to make the proposal look similar to the others on the wiki.

Cheers!


On 5 September 2013 12:47, Christian Grobmeier  wrote:

> Am 05.09.13 07:09, schrieb Kureem Rossaye:
> > Thank you very much,
> > I have not included the proposal to the Incubator wiki yet.
> > How can I do that?
> Create an account here:
> http://wiki.apache.org/incubator/
>
> Then mail your username to this list, askinf for access. You'll be
> granted then.
>
> Then you can add your proposal here:
> http://wiki.apache.org/incubator/ProjectProposals
>
> I assume you know this link already:
> http://incubator.apache.org/guides/proposal.html
>
> Please try to make the proposal look similar to the others on the wiki.
>
> Cheers!
>
> Christian
> > Thanks
> > Kureem
> >
> >
> > On 5 September 2013 00:09, Christian Grobmeier 
> wrote:
> >
> >> Nice!
> >>
> >> Have you included your proposal to the Incubator wiki?
> >> I would like to forward it to the Struts team, some might be interested.
> >>
> >> I have no time to actually code, but I might help with incubation
> >> (mentoring or championing). Before deciding on that, I would like to
> >> hear if there is interest of others here.
> >>
> >> Am 04.09.13 15:04, schrieb Kureem Rossaye:
> >>> "*once could use Castafiore
> >>> in conjunction with Struts. In other terms, Castafiore could be used as
> >>> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> >>> whatever. Is that correct?*"
> >>>
> >>> Correct!
> >>> Actually I myself did not get the idea that it could be used like that.
> >> Yes
> >>> it can be used like that.
> >>> Actually, a castafiore application (which can be a simple table) can be
> >>> included on a page using a simple javascript or a jsp tag. So why not a
> >>> struts plugin.
> >>> Actually I have tried it as an echo2 framework component. It works just
> >>> nice.
> >>>
> >>>
> >>> Thanks for your interest
> >>>
> >>> Ragards,
> >>> Kureem
> >>>
> >>>
> >>> On 4 September 2013 15:32, Christian Grobmeier 
> >> wrote:
>  Kureem,
> 
>  this sounds nice. As far as I understood it, once could use Castafiore
>  in conjunction with Struts. In other terms, Castafiore could be used
> as
>  a Struts plugin which then calls Struts Actions and replaces Tiles,
> JSP
>  whatever. Is that correct?
> 
>  Cheers
> 
> 
> 
>  Am 04.09.13 10:01, schrieb Kureem Rossaye:
> > Hi,
> > Indeed, I have read the incubation proposal guide. The only thing I
> >> could
> > not figure out is how to recruit a champion.
> > However, after re-reading the guide, I missed something. I should
> have
> > prefixed the subject of the mail with [PROPOSAL]. So I am resending
> the
> > proposal with the proper subject.
> >
> >
> **
> > PROPOSAL
> > Abstract
> >
> > Castafiore framework is a web frameworks, fully component oriented,
> >> ajax
> > based, one page appplication. Although the framework can be viewed
> as a
> > classical component oriented web framework like GWT, it has been
> >> designed
> > and implemented with a particular goal in mind. It is to be able to
> >> make
> > existing javascript libraries "java-able". Meaning that the framework
> > allows to easily take a javascript library like e.g jquery ui and use
> >> the
> > components and features via java. The integration of the javascript
> > libraries need to be easy and natural.
> >
> > Actually companies like ext js and smartgwt have made their
> components
> > "java-able" using GWT. I wish to provide an alternative to gwt that
> is
>  much
> > easier, fast, lightweight, and much more productive.
> > Proposal
> >
> > Castafiore framework has been designed and implemented with the
> >> following
> > goals in mind
> >
> >1.
> >
> >Fully object oriented
> >2.
> >
> >Simple API that is very close to html itself
> >We wanted an API that is closer to html markup and javascripts
> event
> >model. I believe that this would help web developers easily
> >> visualize
>  the
> >rendering when reading source code.
> >3.
> >
> >Write a full application with only java
> >4.
> >
> >No need for compiler to convert to javascript like gwt.Javascript
> is
> >rendered at runtime.
> >5.
> >
> >The same API

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Christian Grobmeier]

Am 05.09.13 07:09, schrieb Kureem Rossaye:
> Thank you very much,
> I have not included the proposal to the Incubator wiki yet.
> How can I do that?
Create an account here:
http://wiki.apache.org/incubator/

Then mail your username to this list, askinf for access. You'll be
granted then.

Then you can add your proposal here:
http://wiki.apache.org/incubator/ProjectProposals

I assume you know this link already:
http://incubator.apache.org/guides/proposal.html

Please try to make the proposal look similar to the others on the wiki.

Cheers!

Christian
> Thanks
> Kureem
>
>
> On 5 September 2013 00:09, Christian Grobmeier  wrote:
>
>> Nice!
>>
>> Have you included your proposal to the Incubator wiki?
>> I would like to forward it to the Struts team, some might be interested.
>>
>> I have no time to actually code, but I might help with incubation
>> (mentoring or championing). Before deciding on that, I would like to
>> hear if there is interest of others here.
>>
>> Am 04.09.13 15:04, schrieb Kureem Rossaye:
>>> "*once could use Castafiore
>>> in conjunction with Struts. In other terms, Castafiore could be used as
>>> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
>>> whatever. Is that correct?*"
>>>
>>> Correct!
>>> Actually I myself did not get the idea that it could be used like that.
>> Yes
>>> it can be used like that.
>>> Actually, a castafiore application (which can be a simple table) can be
>>> included on a page using a simple javascript or a jsp tag. So why not a
>>> struts plugin.
>>> Actually I have tried it as an echo2 framework component. It works just
>>> nice.
>>>
>>>
>>> Thanks for your interest
>>>
>>> Ragards,
>>> Kureem
>>>
>>>
>>> On 4 September 2013 15:32, Christian Grobmeier 
>> wrote:
 Kureem,

 this sounds nice. As far as I understood it, once could use Castafiore
 in conjunction with Struts. In other terms, Castafiore could be used as
 a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
 whatever. Is that correct?

 Cheers



 Am 04.09.13 10:01, schrieb Kureem Rossaye:
> Hi,
> Indeed, I have read the incubation proposal guide. The only thing I
>> could
> not figure out is how to recruit a champion.
> However, after re-reading the guide, I missed something. I should have
> prefixed the subject of the mail with [PROPOSAL]. So I am resending the
> proposal with the proper subject.
>
> **
> PROPOSAL
> Abstract
>
> Castafiore framework is a web frameworks, fully component oriented,
>> ajax
> based, one page appplication. Although the framework can be viewed as a
> classical component oriented web framework like GWT, it has been
>> designed
> and implemented with a particular goal in mind. It is to be able to
>> make
> existing javascript libraries "java-able". Meaning that the framework
> allows to easily take a javascript library like e.g jquery ui and use
>> the
> components and features via java. The integration of the javascript
> libraries need to be easy and natural.
>
> Actually companies like ext js and smartgwt have made their components
> "java-able" using GWT. I wish to provide an alternative to gwt that is
 much
> easier, fast, lightweight, and much more productive.
> Proposal
>
> Castafiore framework has been designed and implemented with the
>> following
> goals in mind
>
>1.
>
>Fully object oriented
>2.
>
>Simple API that is very close to html itself
>We wanted an API that is closer to html markup and javascripts event
>model. I believe that this would help web developers easily
>> visualize
 the
>rendering when reading source code.
>3.
>
>Write a full application with only java
>4.
>
>No need for compiler to convert to javascript like gwt.Javascript is
>rendered at runtime.
>5.
>
>The same API can be used to make an software that is server centric
 and
>or client centric. Meaning that the user can make part of his
 application
>server centric and part of his application client centric. He can of
 course
>choose to make the whole application client centric or server
>> centric
>depending on the requirement. All of this using the same API.
>6.
>
>Low memory footprint
>7.
>
>Easy packaging of application. Everything can be packaged in a
>> single
>jar. This includes images, css or javascript as well
>8.
>
>Same API used to create custom components. No need to external set
>> of
>API or specific programming technique to create custom components.
 Creating
>a custom components should be done only the same way as writing an
>applicatio

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Thank you very much,
I have not included the proposal to the Incubator wiki yet.
How can I do that?

Thanks
Kureem


On 5 September 2013 00:09, Christian Grobmeier  wrote:

> Nice!
>
> Have you included your proposal to the Incubator wiki?
> I would like to forward it to the Struts team, some might be interested.
>
> I have no time to actually code, but I might help with incubation
> (mentoring or championing). Before deciding on that, I would like to
> hear if there is interest of others here.
>
> Am 04.09.13 15:04, schrieb Kureem Rossaye:
> > "*once could use Castafiore
> > in conjunction with Struts. In other terms, Castafiore could be used as
> > a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> > whatever. Is that correct?*"
> >
> > Correct!
> > Actually I myself did not get the idea that it could be used like that.
> Yes
> > it can be used like that.
> > Actually, a castafiore application (which can be a simple table) can be
> > included on a page using a simple javascript or a jsp tag. So why not a
> > struts plugin.
> > Actually I have tried it as an echo2 framework component. It works just
> > nice.
> >
> >
> > Thanks for your interest
> >
> > Ragards,
> > Kureem
> >
> >
> > On 4 September 2013 15:32, Christian Grobmeier 
> wrote:
> >
> >> Kureem,
> >>
> >> this sounds nice. As far as I understood it, once could use Castafiore
> >> in conjunction with Struts. In other terms, Castafiore could be used as
> >> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> >> whatever. Is that correct?
> >>
> >> Cheers
> >>
> >>
> >>
> >> Am 04.09.13 10:01, schrieb Kureem Rossaye:
> >>> Hi,
> >>> Indeed, I have read the incubation proposal guide. The only thing I
> could
> >>> not figure out is how to recruit a champion.
> >>> However, after re-reading the guide, I missed something. I should have
> >>> prefixed the subject of the mail with [PROPOSAL]. So I am resending the
> >>> proposal with the proper subject.
> >>>
> >>> **
> >>> PROPOSAL
> >>> Abstract
> >>>
> >>> Castafiore framework is a web frameworks, fully component oriented,
> ajax
> >>> based, one page appplication. Although the framework can be viewed as a
> >>> classical component oriented web framework like GWT, it has been
> designed
> >>> and implemented with a particular goal in mind. It is to be able to
> make
> >>> existing javascript libraries "java-able". Meaning that the framework
> >>> allows to easily take a javascript library like e.g jquery ui and use
> the
> >>> components and features via java. The integration of the javascript
> >>> libraries need to be easy and natural.
> >>>
> >>> Actually companies like ext js and smartgwt have made their components
> >>> "java-able" using GWT. I wish to provide an alternative to gwt that is
> >> much
> >>> easier, fast, lightweight, and much more productive.
> >>> Proposal
> >>>
> >>> Castafiore framework has been designed and implemented with the
> following
> >>> goals in mind
> >>>
> >>>1.
> >>>
> >>>Fully object oriented
> >>>2.
> >>>
> >>>Simple API that is very close to html itself
> >>>We wanted an API that is closer to html markup and javascripts event
> >>>model. I believe that this would help web developers easily
> visualize
> >> the
> >>>rendering when reading source code.
> >>>3.
> >>>
> >>>Write a full application with only java
> >>>4.
> >>>
> >>>No need for compiler to convert to javascript like gwt.Javascript is
> >>>rendered at runtime.
> >>>5.
> >>>
> >>>The same API can be used to make an software that is server centric
> >> and
> >>>or client centric. Meaning that the user can make part of his
> >> application
> >>>server centric and part of his application client centric. He can of
> >> course
> >>>choose to make the whole application client centric or server
> centric
> >>>depending on the requirement. All of this using the same API.
> >>>6.
> >>>
> >>>Low memory footprint
> >>>7.
> >>>
> >>>Easy packaging of application. Everything can be packaged in a
> single
> >>>jar. This includes images, css or javascript as well
> >>>8.
> >>>
> >>>Same API used to create custom components. No need to external set
> of
> >>>API or specific programming technique to create custom components.
> >> Creating
> >>>a custom components should be done only the same way as writing an
> >>>application.
> >>>9.
> >>>
> >>>No need for javascript to create custom components.
> >>>10.
> >>>
> >>>Although there is no need for javascript to create an application,
> it
> >>>should be easy to integrate external javascript libraries and use
> >> them in
> >>>java codes itself. This should be done is a natural way just like we
> >> would
> >>>do in an HTML page. This should be like this so that javascript
> >> library
> >>>authors with some java skills

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Christian Grobmeier]

Nice!

Have you included your proposal to the Incubator wiki?
I would like to forward it to the Struts team, some might be interested.

I have no time to actually code, but I might help with incubation
(mentoring or championing). Before deciding on that, I would like to
hear if there is interest of others here.

Am 04.09.13 15:04, schrieb Kureem Rossaye:
> "*once could use Castafiore
> in conjunction with Struts. In other terms, Castafiore could be used as
> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> whatever. Is that correct?*"
>
> Correct!
> Actually I myself did not get the idea that it could be used like that. Yes
> it can be used like that.
> Actually, a castafiore application (which can be a simple table) can be
> included on a page using a simple javascript or a jsp tag. So why not a
> struts plugin.
> Actually I have tried it as an echo2 framework component. It works just
> nice.
>
>
> Thanks for your interest
>
> Ragards,
> Kureem
>
>
> On 4 September 2013 15:32, Christian Grobmeier  wrote:
>
>> Kureem,
>>
>> this sounds nice. As far as I understood it, once could use Castafiore
>> in conjunction with Struts. In other terms, Castafiore could be used as
>> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
>> whatever. Is that correct?
>>
>> Cheers
>>
>>
>>
>> Am 04.09.13 10:01, schrieb Kureem Rossaye:
>>> Hi,
>>> Indeed, I have read the incubation proposal guide. The only thing I could
>>> not figure out is how to recruit a champion.
>>> However, after re-reading the guide, I missed something. I should have
>>> prefixed the subject of the mail with [PROPOSAL]. So I am resending the
>>> proposal with the proper subject.
>>>
>>> **
>>> PROPOSAL
>>> Abstract
>>>
>>> Castafiore framework is a web frameworks, fully component oriented, ajax
>>> based, one page appplication. Although the framework can be viewed as a
>>> classical component oriented web framework like GWT, it has been designed
>>> and implemented with a particular goal in mind. It is to be able to make
>>> existing javascript libraries "java-able". Meaning that the framework
>>> allows to easily take a javascript library like e.g jquery ui and use the
>>> components and features via java. The integration of the javascript
>>> libraries need to be easy and natural.
>>>
>>> Actually companies like ext js and smartgwt have made their components
>>> "java-able" using GWT. I wish to provide an alternative to gwt that is
>> much
>>> easier, fast, lightweight, and much more productive.
>>> Proposal
>>>
>>> Castafiore framework has been designed and implemented with the following
>>> goals in mind
>>>
>>>1.
>>>
>>>Fully object oriented
>>>2.
>>>
>>>Simple API that is very close to html itself
>>>We wanted an API that is closer to html markup and javascripts event
>>>model. I believe that this would help web developers easily visualize
>> the
>>>rendering when reading source code.
>>>3.
>>>
>>>Write a full application with only java
>>>4.
>>>
>>>No need for compiler to convert to javascript like gwt.Javascript is
>>>rendered at runtime.
>>>5.
>>>
>>>The same API can be used to make an software that is server centric
>> and
>>>or client centric. Meaning that the user can make part of his
>> application
>>>server centric and part of his application client centric. He can of
>> course
>>>choose to make the whole application client centric or server centric
>>>depending on the requirement. All of this using the same API.
>>>6.
>>>
>>>Low memory footprint
>>>7.
>>>
>>>Easy packaging of application. Everything can be packaged in a single
>>>jar. This includes images, css or javascript as well
>>>8.
>>>
>>>Same API used to create custom components. No need to external set of
>>>API or specific programming technique to create custom components.
>> Creating
>>>a custom components should be done only the same way as writing an
>>>application.
>>>9.
>>>
>>>No need for javascript to create custom components.
>>>10.
>>>
>>>Although there is no need for javascript to create an application, it
>>>should be easy to integrate external javascript libraries and use
>> them in
>>>java codes itself. This should be done is a natural way just like we
>> would
>>>do in an HTML page. This should be like this so that javascript
>> library
>>>authors with some java skills find it natural and easy to provide a
>>>castafiore component together with the library. e.g. The author of
>> flexgrid
>>>should should find it easy to create a castafiore component thus
>> making his
>>>library usable directly in java.
>>>
>>>  *Actually, I wanted to create a java web framework for javascript
>>> programmers. They should find it easy and fun to integrate and distribute
>>> their js libraries as a castafiore component

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

"*once could use Castafiore
in conjunction with Struts. In other terms, Castafiore could be used as
a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
whatever. Is that correct?*"

Correct!
Actually I myself did not get the idea that it could be used like that. Yes
it can be used like that.
Actually, a castafiore application (which can be a simple table) can be
included on a page using a simple javascript or a jsp tag. So why not a
struts plugin.
Actually I have tried it as an echo2 framework component. It works just
nice.


Thanks for your interest

Ragards,
Kureem


On 4 September 2013 15:32, Christian Grobmeier  wrote:

> Kureem,
>
> this sounds nice. As far as I understood it, once could use Castafiore
> in conjunction with Struts. In other terms, Castafiore could be used as
> a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
> whatever. Is that correct?
>
> Cheers
>
>
>
> Am 04.09.13 10:01, schrieb Kureem Rossaye:
> > Hi,
> > Indeed, I have read the incubation proposal guide. The only thing I could
> > not figure out is how to recruit a champion.
> > However, after re-reading the guide, I missed something. I should have
> > prefixed the subject of the mail with [PROPOSAL]. So I am resending the
> > proposal with the proper subject.
> >
> > **
> > PROPOSAL
> > Abstract
> >
> > Castafiore framework is a web frameworks, fully component oriented, ajax
> > based, one page appplication. Although the framework can be viewed as a
> > classical component oriented web framework like GWT, it has been designed
> > and implemented with a particular goal in mind. It is to be able to make
> > existing javascript libraries "java-able". Meaning that the framework
> > allows to easily take a javascript library like e.g jquery ui and use the
> > components and features via java. The integration of the javascript
> > libraries need to be easy and natural.
> >
> > Actually companies like ext js and smartgwt have made their components
> > "java-able" using GWT. I wish to provide an alternative to gwt that is
> much
> > easier, fast, lightweight, and much more productive.
> > Proposal
> >
> > Castafiore framework has been designed and implemented with the following
> > goals in mind
> >
> >1.
> >
> >Fully object oriented
> >2.
> >
> >Simple API that is very close to html itself
> >We wanted an API that is closer to html markup and javascripts event
> >model. I believe that this would help web developers easily visualize
> the
> >rendering when reading source code.
> >3.
> >
> >Write a full application with only java
> >4.
> >
> >No need for compiler to convert to javascript like gwt.Javascript is
> >rendered at runtime.
> >5.
> >
> >The same API can be used to make an software that is server centric
> and
> >or client centric. Meaning that the user can make part of his
> application
> >server centric and part of his application client centric. He can of
> course
> >choose to make the whole application client centric or server centric
> >depending on the requirement. All of this using the same API.
> >6.
> >
> >Low memory footprint
> >7.
> >
> >Easy packaging of application. Everything can be packaged in a single
> >jar. This includes images, css or javascript as well
> >8.
> >
> >Same API used to create custom components. No need to external set of
> >API or specific programming technique to create custom components.
> Creating
> >a custom components should be done only the same way as writing an
> >application.
> >9.
> >
> >No need for javascript to create custom components.
> >10.
> >
> >Although there is no need for javascript to create an application, it
> >should be easy to integrate external javascript libraries and use
> them in
> >java codes itself. This should be done is a natural way just like we
> would
> >do in an HTML page. This should be like this so that javascript
> library
> >authors with some java skills find it natural and easy to provide a
> >castafiore component together with the library. e.g. The author of
> flexgrid
> >should should find it easy to create a castafiore component thus
> making his
> >library usable directly in java.
> >
> >  *Actually, I wanted to create a java web framework for javascript
> > programmers. They should find it easy and fun to integrate and distribute
> > their js libraries as a castafiore component. They will be able to
> > distribute their libraries as a single jar. This is very convenient for
> > java developers to just download the jar, include in classpath, and using
> > the library, components and feature right away in their web application
> in
> > pure java. Furthermore the castafiore framework itself is very
> lightweight
> > with just 2 libraries and 1 web.xml entry. Even if the java developer is
> >

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Bertrand Delacretaz]

On Wed, Sep 4, 2013 at 1:23 PM, Kureem Rossaye  wrote:
> ...when you I should build a small community somewhere else before
> coming here, the small community can be of around how many contributors?...

There's no set size. For me, three contributors, along with other
items that demonstrate the existence of at least an embryo of a
community (blog posts, conference talks etc.) are a good starting
point, but the collective appreciation of the Incubator PMC is
subjective. We're basically trying to accept projects that show
potential, and there are many ways to show that.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Christian Grobmeier]

Kureem,

this sounds nice. As far as I understood it, once could use Castafiore
in conjunction with Struts. In other terms, Castafiore could be used as
a Struts plugin which then calls Struts Actions and replaces Tiles, JSP
whatever. Is that correct?

Cheers



Am 04.09.13 10:01, schrieb Kureem Rossaye:
> Hi,
> Indeed, I have read the incubation proposal guide. The only thing I could
> not figure out is how to recruit a champion.
> However, after re-reading the guide, I missed something. I should have
> prefixed the subject of the mail with [PROPOSAL]. So I am resending the
> proposal with the proper subject.
>
> **
> PROPOSAL
> Abstract
>
> Castafiore framework is a web frameworks, fully component oriented, ajax
> based, one page appplication. Although the framework can be viewed as a
> classical component oriented web framework like GWT, it has been designed
> and implemented with a particular goal in mind. It is to be able to make
> existing javascript libraries "java-able". Meaning that the framework
> allows to easily take a javascript library like e.g jquery ui and use the
> components and features via java. The integration of the javascript
> libraries need to be easy and natural.
>
> Actually companies like ext js and smartgwt have made their components
> "java-able" using GWT. I wish to provide an alternative to gwt that is much
> easier, fast, lightweight, and much more productive.
> Proposal
>
> Castafiore framework has been designed and implemented with the following
> goals in mind
>
>1.
>
>Fully object oriented
>2.
>
>Simple API that is very close to html itself
>We wanted an API that is closer to html markup and javascripts event
>model. I believe that this would help web developers easily visualize the
>rendering when reading source code.
>3.
>
>Write a full application with only java
>4.
>
>No need for compiler to convert to javascript like gwt.Javascript is
>rendered at runtime.
>5.
>
>The same API can be used to make an software that is server centric and
>or client centric. Meaning that the user can make part of his application
>server centric and part of his application client centric. He can of course
>choose to make the whole application client centric or server centric
>depending on the requirement. All of this using the same API.
>6.
>
>Low memory footprint
>7.
>
>Easy packaging of application. Everything can be packaged in a single
>jar. This includes images, css or javascript as well
>8.
>
>Same API used to create custom components. No need to external set of
>API or specific programming technique to create custom components. Creating
>a custom components should be done only the same way as writing an
>application.
>9.
>
>No need for javascript to create custom components.
>10.
>
>Although there is no need for javascript to create an application, it
>should be easy to integrate external javascript libraries and use them in
>java codes itself. This should be done is a natural way just like we would
>do in an HTML page. This should be like this so that javascript library
>authors with some java skills find it natural and easy to provide a
>castafiore component together with the library. e.g. The author of flexgrid
>should should find it easy to create a castafiore component thus making his
>library usable directly in java.
>
>  *Actually, I wanted to create a java web framework for javascript
> programmers. They should find it easy and fun to integrate and distribute
> their js libraries as a castafiore component. They will be able to
> distribute their libraries as a single jar. This is very convenient for
> java developers to just download the jar, include in classpath, and using
> the library, components and feature right away in their web application in
> pure java. Furthermore the castafiore framework itself is very lightweight
> with just 2 libraries and 1 web.xml entry. Even if the java developer is
> not using castafiore in his project, he should find it easy to just drop
> the 2 libraries + web.xml entry in classpath and start using it right away.
> Very practical.*
>
>1.
>
>Load external resources like css and javascript lazily and efficiently
>only when needed.
>2.
>
>Loading of external resources can be done eagerly if the API user wish
>so.
>3.
>
>The framework does not own the whole page. Meaning that an application
>created with the framework can be used in an already created page. This
>allows API developer to use the framework only for very specific purposes
>like for example a dynamic table, while at the same time using other web
>framework like struts for the other sections of the application.
>4.
>
>Although a whole application can be created using pure java, the
>framework should be

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Hi,
By the way, when you I should build a small community somewhere else before
coming here, the small community can be of around how many contributors?



On 4 September 2013 12:26, Kureem Rossaye  wrote:

> Hi,
>
> Thank you,
> I have taken note
>
> Kureem
>
>
> On 4 September 2013 12:11, Bertrand Delacretaz wrote:
>
>>  [image: Boxbe]  This message is
>> eligible for Automatic Cleanup! (bdelacre...@apache.org) Add cleanup 
>> rule|
>>  More
>> info
>>
>> H,
>>
>> On Wed, Sep 4, 2013 at 10:01 AM, Kureem Rossaye  wrote:
>> > ...I should have
>> > prefixed the subject of the mail with [PROPOSAL]...
>>
>> That's correct but looking at your proposal IMO the main problem is
>> that it's a one-man show so far.
>>
>> As you already indicated, to start incubation you'll need a champion
>> and mentors - posting your proposal here might help finding those,
>> let's wait a bit to see if it's the case.
>>
>> Projects that come here with no community are usually told to first
>> start building at least a small community elsewhere and come back here
>> once they have demonstrated interest from more than just one author.
>>
>> Just posting your proposal here might prompt others to sign up as
>> initial committers, in which case your proposal might be accepted. If
>> too few people show interest, you'll need to try and build a community
>> elsewhere first.
>>
>> For now, let's wait to see if there's interest.
>>
>> -Bertrand
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>>
>
>
> --
> Kureem Rossaye
> Managing Director
>
> ArchNet ltd
> R. Tagore Avenue, Mesnil
> Mauritius
> Mobile :+230 7159028 / Tel :+230 6867326
> Skype : arkureem
> http://www.archnetltd.com
>
>


-- 
Kureem Rossaye
Managing Director

ArchNet ltd
R. Tagore Avenue, Mesnil
Mauritius
Mobile :+230 7159028 / Tel :+230 6867326
Skype : arkureem
http://www.archnetltd.com

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Hi,

Thank you,
I have taken note

Kureem


On 4 September 2013 12:11, Bertrand Delacretaz wrote:

>  [image: Boxbe]  This message is eligible
> for Automatic Cleanup! (bdelacre...@apache.org) Add cleanup 
> rule|
>  More
> info
>
> H,
>
> On Wed, Sep 4, 2013 at 10:01 AM, Kureem Rossaye  wrote:
> > ...I should have
> > prefixed the subject of the mail with [PROPOSAL]...
>
> That's correct but looking at your proposal IMO the main problem is
> that it's a one-man show so far.
>
> As you already indicated, to start incubation you'll need a champion
> and mentors - posting your proposal here might help finding those,
> let's wait a bit to see if it's the case.
>
> Projects that come here with no community are usually told to first
> start building at least a small community elsewhere and come back here
> once they have demonstrated interest from more than just one author.
>
> Just posting your proposal here might prompt others to sign up as
> initial committers, in which case your proposal might be accepted. If
> too few people show interest, you'll need to try and build a community
> elsewhere first.
>
> For now, let's wait to see if there's interest.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>


-- 
Kureem Rossaye
Managing Director

ArchNet ltd
R. Tagore Avenue, Mesnil
Mauritius
Mobile :+230 7159028 / Tel :+230 6867326
Skype : arkureem
http://www.archnetltd.com

Re: [PROPOSAL] Castafiore framework proposal to incubator

[Bertrand Delacretaz]

H,

On Wed, Sep 4, 2013 at 10:01 AM, Kureem Rossaye  wrote:
> ...I should have
> prefixed the subject of the mail with [PROPOSAL]...

That's correct but looking at your proposal IMO the main problem is
that it's a one-man show so far.

As you already indicated, to start incubation you'll need a champion
and mentors - posting your proposal here might help finding those,
let's wait a bit to see if it's the case.

Projects that come here with no community are usually told to first
start building at least a small community elsewhere and come back here
once they have demonstrated interest from more than just one author.

Just posting your proposal here might prompt others to sign up as
initial committers, in which case your proposal might be accepted. If
too few people show interest, you'll need to try and build a community
elsewhere first.

For now, let's wait to see if there's interest.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[PROPOSAL] Castafiore framework proposal to incubator

[Kureem Rossaye]

Hi,
Indeed, I have read the incubation proposal guide. The only thing I could
not figure out is how to recruit a champion.
However, after re-reading the guide, I missed something. I should have
prefixed the subject of the mail with [PROPOSAL]. So I am resending the
proposal with the proper subject.

**
PROPOSAL
Abstract

Castafiore framework is a web frameworks, fully component oriented, ajax
based, one page appplication. Although the framework can be viewed as a
classical component oriented web framework like GWT, it has been designed
and implemented with a particular goal in mind. It is to be able to make
existing javascript libraries "java-able". Meaning that the framework
allows to easily take a javascript library like e.g jquery ui and use the
components and features via java. The integration of the javascript
libraries need to be easy and natural.

Actually companies like ext js and smartgwt have made their components
"java-able" using GWT. I wish to provide an alternative to gwt that is much
easier, fast, lightweight, and much more productive.
Proposal

Castafiore framework has been designed and implemented with the following
goals in mind

   1.

   Fully object oriented
   2.

   Simple API that is very close to html itself
   We wanted an API that is closer to html markup and javascripts event
   model. I believe that this would help web developers easily visualize the
   rendering when reading source code.
   3.

   Write a full application with only java
   4.

   No need for compiler to convert to javascript like gwt.Javascript is
   rendered at runtime.
   5.

   The same API can be used to make an software that is server centric and
   or client centric. Meaning that the user can make part of his application
   server centric and part of his application client centric. He can of course
   choose to make the whole application client centric or server centric
   depending on the requirement. All of this using the same API.
   6.

   Low memory footprint
   7.

   Easy packaging of application. Everything can be packaged in a single
   jar. This includes images, css or javascript as well
   8.

   Same API used to create custom components. No need to external set of
   API or specific programming technique to create custom components. Creating
   a custom components should be done only the same way as writing an
   application.
   9.

   No need for javascript to create custom components.
   10.

   Although there is no need for javascript to create an application, it
   should be easy to integrate external javascript libraries and use them in
   java codes itself. This should be done is a natural way just like we would
   do in an HTML page. This should be like this so that javascript library
   authors with some java skills find it natural and easy to provide a
   castafiore component together with the library. e.g. The author of flexgrid
   should should find it easy to create a castafiore component thus making his
   library usable directly in java.

 *Actually, I wanted to create a java web framework for javascript
programmers. They should find it easy and fun to integrate and distribute
their js libraries as a castafiore component. They will be able to
distribute their libraries as a single jar. This is very convenient for
java developers to just download the jar, include in classpath, and using
the library, components and feature right away in their web application in
pure java. Furthermore the castafiore framework itself is very lightweight
with just 2 libraries and 1 web.xml entry. Even if the java developer is
not using castafiore in his project, he should find it easy to just drop
the 2 libraries + web.xml entry in classpath and start using it right away.
Very practical.*

   1.

   Load external resources like css and javascript lazily and efficiently
   only when needed.
   2.

   Loading of external resources can be done eagerly if the API user wish
   so.
   3.

   The framework does not own the whole page. Meaning that an application
   created with the framework can be used in an already created page. This
   allows API developer to use the framework only for very specific purposes
   like for example a dynamic table, while at the same time using other web
   framework like struts for the other sections of the application.
   4.

   Although a whole application can be created using pure java, the
   framework should be able to integrate templates.
   5.

   By default, there should be 100% separation of logic and presentation.
   Meaning that the API user should be able to take an html template, and
   dynamise it without needing to add any modification in the template.
   6.

   On the other hand, if an API user is more script centric, he is able to
   write groovy template, jstl templates or any other template engine.
   7.

   The API user should be able to easily use any template engine he wishes
   easily 

Re: Castafiore framework proposal to incubator

[Andy Van Den Heuvel]

I think Kureem already knows the incubation process.
He is looking for a java champion. Since he already has a first draft of
his proposal, I asked him to copy it
so people interessed could have an idea what the project is about.

Sorry if my communication caused any inconvenience


On Wed, Sep 4, 2013 at 8:50 AM, David Crossley  wrote:

> Kureem Rossaye wrote:
> >  Hello community,
> >
> > please find below a proposal I wish to submit to the ASF. I am new here
> and
> > was told that I could paste the proposal here. So here we are.
>
> That was misleading to simply say that. There is quite a process
> which will all be beneficial.
>
> > Awaiting reply, recommendation and feedback and will be pleased to answer
> > any questions.
>
> Please review the Incubator website. There are instructions
> about the process for Proposals.
> http://incubator.apache.org/
> In the top-left see the link to the "Proposal Guide".
>
> -David
>
> > Thanks in advance
> >
> >
> > Kind regards,
> >
> > Kureem Rossaye
> > Abstract
> >
> > Castafiore framework is a web frameworks, fully component oriented, ajax
> > based, one page appplication. Although the framework can be viewed as a
> > classical component oriented web framework like GWT, it has been designed
> > and implemented with a particular goal in mind. It is to be able to make
> > existing javascript libraries "java-able". Meaning that the framework
> > allows to easily take a javascript library like e.g jquery ui and use the
> > components and features via java. The integration of the javascript
> > libraries need to be easy and natural.
> >
> > Actually companies like ext js and smartgwt have made their components
> > "java-able" using GWT. I wish to provide an alternative to gwt that is
> much
> > easier, fast, lightweight, and much more productive.
> > Proposal
> >
> > Castafiore framework has been designed and implemented with the following
> > goals in mind
> >
> >1.
> >
> >Fully object oriented
> >2.
> >
> >Simple API that is very close to html itself
> >We wanted an API that is closer to html markup and javascripts event
> >model. I believe that this would help web developers easily visualize
> the
> >rendering when reading source code.
> >3.
> >
> >Write a full application with only java
> >4.
> >
> >No need for compiler to convert to javascript like gwt.Javascript is
> >rendered at runtime.
> >5.
> >
> >The same API can be used to make an software that is server centric
> and
> >or client centric. Meaning that the user can make part of his
> application
> >server centric and part of his application client centric. He can of
> course
> >choose to make the whole application client centric or server centric
> >depending on the requirement. All of this using the same API.
> >6.
> >
> >Low memory footprint
> >7.
> >
> >Easy packaging of application. Everything can be packaged in a single
> >jar. This includes images, css or javascript as well
> >8.
> >
> >Same API used to create custom components. No need to external set of
> >API or specific programming technique to create custom components.
> Creating
> >a custom components should be done only the same way as writing an
> >application.
> >9.
> >
> >No need for javascript to create custom components.
> >10.
> >
> >Although there is no need for javascript to create an application, it
> >should be easy to integrate external javascript libraries and use
> them in
> >java codes itself. This should be done is a natural way just like we
> would
> >do in an HTML page. This should be like this so that javascript
> library
> >authors with some java skills find it natural and easy to provide a
> >castafiore component together with the library. e.g. The author of
> flexgrid
> >should should find it easy to create a castafiore component thus
> making his
> >library usable directly in java.
> >
> >  *Actually, I wanted to create a java web framework for javascript
> > programmers. They should find it easy and fun to integrate and distribute
> > their js libraries as a castafiore component. They will be able to
> > distribute their libraries as a single jar. This is very convenient for
> > java developers to just download the jar, include in classpath, and using
> > the library, components and feature right away in their web application
> in
> > pure java. Furthermore the castafiore framework itself is very
> lightweight
> > with just 2 libraries and 1 web.xml entry. Even if the java developer is
> > not using castafiore in his project, he should find it easy to just drop
> > the 2 libraries + web.xml entry in classpath and start using it right
> away.
> > Very practical.*
> >
> >1.
> >
> >Load external resources like css and javascript lazily and efficiently
> >only when needed.
> >2.
> >
> >Loading of external resources can be done eagerly if the API use

Re: Castafiore framework proposal to incubator

[David Crossley]

Kureem Rossaye wrote:
>  Hello community,
> 
> please find below a proposal I wish to submit to the ASF. I am new here and
> was told that I could paste the proposal here. So here we are.

That was misleading to simply say that. There is quite a process
which will all be beneficial.

> Awaiting reply, recommendation and feedback and will be pleased to answer
> any questions.

Please review the Incubator website. There are instructions
about the process for Proposals.
http://incubator.apache.org/
In the top-left see the link to the "Proposal Guide".

-David

> Thanks in advance
> 
> 
> Kind regards,
> 
> Kureem Rossaye
> Abstract
> 
> Castafiore framework is a web frameworks, fully component oriented, ajax
> based, one page appplication. Although the framework can be viewed as a
> classical component oriented web framework like GWT, it has been designed
> and implemented with a particular goal in mind. It is to be able to make
> existing javascript libraries "java-able". Meaning that the framework
> allows to easily take a javascript library like e.g jquery ui and use the
> components and features via java. The integration of the javascript
> libraries need to be easy and natural.
> 
> Actually companies like ext js and smartgwt have made their components
> "java-able" using GWT. I wish to provide an alternative to gwt that is much
> easier, fast, lightweight, and much more productive.
> Proposal
> 
> Castafiore framework has been designed and implemented with the following
> goals in mind
> 
>1.
> 
>Fully object oriented
>2.
> 
>Simple API that is very close to html itself
>We wanted an API that is closer to html markup and javascripts event
>model. I believe that this would help web developers easily visualize the
>rendering when reading source code.
>3.
> 
>Write a full application with only java
>4.
> 
>No need for compiler to convert to javascript like gwt.Javascript is
>rendered at runtime.
>5.
> 
>The same API can be used to make an software that is server centric and
>or client centric. Meaning that the user can make part of his application
>server centric and part of his application client centric. He can of course
>choose to make the whole application client centric or server centric
>depending on the requirement. All of this using the same API.
>6.
> 
>Low memory footprint
>7.
> 
>Easy packaging of application. Everything can be packaged in a single
>jar. This includes images, css or javascript as well
>8.
> 
>Same API used to create custom components. No need to external set of
>API or specific programming technique to create custom components. Creating
>a custom components should be done only the same way as writing an
>application.
>9.
> 
>No need for javascript to create custom components.
>10.
> 
>Although there is no need for javascript to create an application, it
>should be easy to integrate external javascript libraries and use them in
>java codes itself. This should be done is a natural way just like we would
>do in an HTML page. This should be like this so that javascript library
>authors with some java skills find it natural and easy to provide a
>castafiore component together with the library. e.g. The author of flexgrid
>should should find it easy to create a castafiore component thus making his
>library usable directly in java.
> 
>  *Actually, I wanted to create a java web framework for javascript
> programmers. They should find it easy and fun to integrate and distribute
> their js libraries as a castafiore component. They will be able to
> distribute their libraries as a single jar. This is very convenient for
> java developers to just download the jar, include in classpath, and using
> the library, components and feature right away in their web application in
> pure java. Furthermore the castafiore framework itself is very lightweight
> with just 2 libraries and 1 web.xml entry. Even if the java developer is
> not using castafiore in his project, he should find it easy to just drop
> the 2 libraries + web.xml entry in classpath and start using it right away.
> Very practical.*
> 
>1.
> 
>Load external resources like css and javascript lazily and efficiently
>only when needed.
>2.
> 
>Loading of external resources can be done eagerly if the API user wish
>so.
>3.
> 
>The framework does not own the whole page. Meaning that an application
>created with the framework can be used in an already created page. This
>allows API developer to use the framework only for very specific purposes
>like for example a dynamic table, while at the same time using other web
>framework like struts for the other sections of the application.
>4.
> 
>Although a whole application can be created using pure java, the
>framework should be able to integrate templates.
>5.
> 
>By default,

Re: Castafiore framework proposal to incubator

[Kureem Rossaye]

Thank you ;-)


On 3 September 2013 16:54, Bertrand Delacretaz wrote:

>  [image: Boxbe]  This message is eligible
> for Automatic Cleanup! (bdelacre...@apache.org) Add cleanup 
> rule|
>  More
> info
>
> On Tue, Sep 3, 2013 at 2:51 PM, Kureem Rossaye  wrote:
> > ...Castafiore framework is a web frameworks...
>
> Love the name - could start a theme, next podling is called Bianca,
> then Nightingale ;-)
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>


-- 
Kureem Rossaye
Managing Director

ArchNet ltd
R. Tagore Avenue, Mesnil
Mauritius
Mobile :+230 7159028 / Tel :+230 6867326
Skype : arkureem
http://www.archnetltd.com

Re: Castafiore framework proposal to incubator

[Bertrand Delacretaz]

On Tue, Sep 3, 2013 at 2:51 PM, Kureem Rossaye  wrote:
> ...Castafiore framework is a web frameworks...

Love the name - could start a theme, next podling is called Bianca,
then Nightingale ;-)

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Castafiore framework proposal to incubator

[Kureem Rossaye]

 Hello community,

please find below a proposal I wish to submit to the ASF. I am new here and
was told that I could paste the proposal here. So here we are.

Awaiting reply, recommendation and feedback and will be pleased to answer
any questions.

Thanks in advance


Kind regards,

Kureem Rossaye
Abstract

Castafiore framework is a web frameworks, fully component oriented, ajax
based, one page appplication. Although the framework can be viewed as a
classical component oriented web framework like GWT, it has been designed
and implemented with a particular goal in mind. It is to be able to make
existing javascript libraries "java-able". Meaning that the framework
allows to easily take a javascript library like e.g jquery ui and use the
components and features via java. The integration of the javascript
libraries need to be easy and natural.

Actually companies like ext js and smartgwt have made their components
"java-able" using GWT. I wish to provide an alternative to gwt that is much
easier, fast, lightweight, and much more productive.
Proposal

Castafiore framework has been designed and implemented with the following
goals in mind

   1.

   Fully object oriented
   2.

   Simple API that is very close to html itself
   We wanted an API that is closer to html markup and javascripts event
   model. I believe that this would help web developers easily visualize the
   rendering when reading source code.
   3.

   Write a full application with only java
   4.

   No need for compiler to convert to javascript like gwt.Javascript is
   rendered at runtime.
   5.

   The same API can be used to make an software that is server centric and
   or client centric. Meaning that the user can make part of his application
   server centric and part of his application client centric. He can of course
   choose to make the whole application client centric or server centric
   depending on the requirement. All of this using the same API.
   6.

   Low memory footprint
   7.

   Easy packaging of application. Everything can be packaged in a single
   jar. This includes images, css or javascript as well
   8.

   Same API used to create custom components. No need to external set of
   API or specific programming technique to create custom components. Creating
   a custom components should be done only the same way as writing an
   application.
   9.

   No need for javascript to create custom components.
   10.

   Although there is no need for javascript to create an application, it
   should be easy to integrate external javascript libraries and use them in
   java codes itself. This should be done is a natural way just like we would
   do in an HTML page. This should be like this so that javascript library
   authors with some java skills find it natural and easy to provide a
   castafiore component together with the library. e.g. The author of flexgrid
   should should find it easy to create a castafiore component thus making his
   library usable directly in java.

 *Actually, I wanted to create a java web framework for javascript
programmers. They should find it easy and fun to integrate and distribute
their js libraries as a castafiore component. They will be able to
distribute their libraries as a single jar. This is very convenient for
java developers to just download the jar, include in classpath, and using
the library, components and feature right away in their web application in
pure java. Furthermore the castafiore framework itself is very lightweight
with just 2 libraries and 1 web.xml entry. Even if the java developer is
not using castafiore in his project, he should find it easy to just drop
the 2 libraries + web.xml entry in classpath and start using it right away.
Very practical.*

   1.

   Load external resources like css and javascript lazily and efficiently
   only when needed.
   2.

   Loading of external resources can be done eagerly if the API user wish
   so.
   3.

   The framework does not own the whole page. Meaning that an application
   created with the framework can be used in an already created page. This
   allows API developer to use the framework only for very specific purposes
   like for example a dynamic table, while at the same time using other web
   framework like struts for the other sections of the application.
   4.

   Although a whole application can be created using pure java, the
   framework should be able to integrate templates.
   5.

   By default, there should be 100% separation of logic and presentation.
   Meaning that the API user should be able to take an html template, and
   dynamise it without needing to add any modification in the template.
   6.

   On the other hand, if an API user is more script centric, he is able to
   write groovy template, jstl templates or any other template engine.
   7.

   The API user should be able to easily use any template engine he wishes
   easily and naturally.
   8.

   Event model is in 3 phase. Client-> server->back to clien