Re: Proposal for contributing code from GraniteDS

The URL is: http://granitedataservices.com/blog/2011/12/05/graniteds-data-management-tutorial/ Run the commands in the intro and then go to the section entitled "Step 5: Validation" Franck. 2012/11/28 Om >

Re: Proposal for contributing code from GraniteDS

The url you gave does not seem to be working. I tried this: http://granitedataservices.com/blog/2011/12/05/graniteds-data-management-tutorial/(Part 5: Validation) and this: http://granitedataservices.com/blog/2011/12/05/graniteds-data-management-tutorial/(Part%205:%20Validation) No luck. Can you

Re: Proposal for contributing code from GraniteDS

Om, Did you find time to play with the tutorial? Franck. 2012/11/14 Franck Wolff > Om, > > That tutorial can certainly help: > http://granitedataservices.com/blog/2011/12/05/graniteds-data-management-tutorial/(Part > 5: Validation) > > Run these commands: > > git clone git://github.com/wdrai/

Re: Proposal for contributing code from GraniteDS

On 11/28/12 11:35 AM, "Franck Wolff" wrote: > Alex, > > Sorry for the delay, I have been very busy last week with the new GraniteDS > release, among other things. > > My answers below: > > 2012/11/14 Alex Harui > >>> >>> Good point. All classes from the org.granite.math package were wri

Re: Proposal for contributing code from GraniteDS

Alex, Sorry for the delay, I have been very busy last week with the new GraniteDS release, among other things. My answers below: 2012/11/14 Alex Harui > > > > On 11/14/12 2:57 PM, "Franck Wolff" wrote: > > > Alex, > > > > My answers below: > > > > 2012/11/14 Alex Harui > > > >> OK, I skimmed

Re: Proposal for contributing code from GraniteDS

On 11/14/12 2:57 PM, "Franck Wolff" wrote: > Alex, > > My answers below: > > 2012/11/14 Alex Harui > >> OK, I skimmed through the files. Code-wise, it looks very nice, so thank >> you for being willing to donate this work. >> >> One thing that was bugging me as I was looking at the code

Re: Proposal for contributing code from GraniteDS

Alex, My answers below: 2012/11/14 Alex Harui > OK, I skimmed through the files. Code-wise, it looks very nice, so thank > you for being willing to donate this work. > > One thing that was bugging me as I was looking at the code is this: Did you > look at the Java code for the Java equivalents

Re: Proposal for contributing code from GraniteDS

OK, I skimmed through the files. Code-wise, it looks very nice, so thank you for being willing to donate this work. One thing that was bugging me as I was looking at the code is this: Did you look at the Java code for the Java equivalents when writing your code, are any portions of your code "sub

Re: Proposal for contributing code from GraniteDS

I agree: we are the copyright owners, there is no external contribution in that part of our code and we can freely choose the license (LGPL, Apache, commercial, etc.) You could certainly ask some legal guy at the ASF over this potential issue, but I'm pretty sure we have the right to change the li

Re: Proposal for contributing code from GraniteDS

Hi, Only issue I see is the current license which I believe is not compatible with Apache. Given you own the software and can licence it how you see fit I don't see this being an issue. Thanks, Justin

Re: Proposal for contributing code from GraniteDS

Thanks ;) 2012/11/14 Alex Harui > > > > On 11/14/12 9:46 AM, "Franck Wolff" wrote: > > > I would suggest that you make a quick review of the code on Github while > > I'm reading some ASF documents about committers. If we are both ok (you > > with the code, me with my obligations), then we can s

Re: Proposal for contributing code from GraniteDS

Om, That tutorial can certainly help: http://granitedataservices.com/blog/2011/12/05/graniteds-data-management-tutorial/(Part 5: Validation) Run these commands: git clone git://github.com/wdrai/wineshop-admin.git cd wineshop-admin mvn clean install cd webapp mvn jetty:run-war Then look at those

Re: Proposal for contributing code from GraniteDS

Franck, The level of detail on this document [1] is really good. Would it be too much to ask for a very simple working prototype with 'View Source' so that we get a better idea for the evaluation? I am guessing you would want to do something similar when the code gets committed and shipped. Tha

Re: Proposal for contributing code from GraniteDS

On 11/14/12 9:46 AM, "Franck Wolff" wrote: > I would suggest that you make a quick review of the code on Github while > I'm reading some ASF documents about committers. If we are both ok (you > with the code, me with my obligations), then we can start the all process. > > I can find some time

Re: Proposal for contributing code from GraniteDS

I would suggest that you make a quick review of the code on Github while I'm reading some ASF documents about committers. If we are both ok (you with the code, me with my obligations), then we can start the all process. I can find some time before the end of this week and review the documents. Can

Re: Proposal for contributing code from GraniteDS

Almost. It will be more like this (1 & 2 & 3 run in parallel): 1. You fill out and sign all legal documents 2. Some of us will review the code (assuming the Github links are the actual files you plan to donate). If it looks ok, we will start the committer approval process for you. Takes a minim

Re: Proposal for contributing code from GraniteDS

I do have the required authority to sign those documents. To summarize: 1. I fill out and sign all legal documents. 2. We wait for a confirmation from the Apache foundation (is it required? how long does it takes?) 3. You give me a read-write access to the SVN repository. 4. I commit our code som

Re: Proposal for contributing code from GraniteDS

Yes, the ICLA is for you personally to make changes to code. You will need this to be allowed to modify the files once they land in Apache SVN. The CCLA says that your corporation understands that you are doing this work and is ok with Apache having license to use your changes. And since the co

Re: Proposal for contributing code from GraniteDS

The copyright owner is GraniteDS. There is no need to retain any software revision history and there is no opened bug about this part of our code currently (or very very few, I didn't check). Do I still need to fill out [1] if the code is fully owned by GraniteDS? 2012/11/13 Alex Harui > > > >

Re: Proposal for contributing code from GraniteDS

On 11/13/12 11:17 AM, "Franck Wolff" wrote: > That's a 86 AS source files and 4 xml files piece of code (dont' ask me the > number of lines). I don't know if it's a "lot of code" or no... > > There is no copyright issue about this code (we are the owners and there is > no external contributio

Re: Proposal for contributing code from GraniteDS

That's a 86 AS source files and 4 xml files piece of code (dont' ask me the number of lines). I don't know if it's a "lot of code" or no... There is no copyright issue about this code (we are the owners and there is no external contribution) and there is no dependencies on code outside of the Flex

Re: Proposal for contributing code from GraniteDS

On 11/13/12 9:49 AM, "Franck Wolff" wrote: > Om, > > Yes we are. > > I think the best would be to commit our sources in the > trunk/frameworks/projects/experimental/src/ directory, changing our package > names to: > > org.apache.flex.math (BigDecimal implementation) > org.apache.flex.reflec

Re: Proposal for contributing code from GraniteDS

Om, Yes we are. I think the best would be to commit our sources in the trunk/frameworks/projects/experimental/src/ directory, changing our package names to: org.apache.flex.math (BigDecimal implementation) org.apache.flex.reflect (Reflection API) org.apache.flex.validation (Bean Validation imple

Re: Proposal for contributing code from GraniteDS

Franck, Sorry it a while for me to respond. I am assuming you are still interested in contributing the validation framework to Apache Flex. Please let me know how you would like to proceed. I have some free cycles and I can help committing it to the codebase. Thanks, Om On Wed, Oct 3, 2012 at

Re: Proposal for contributing code from GraniteDS

The goal is of course to give the validation framework with the less possible dependencies. Refactoring is an option but it should be minimal in order to preserve the current stability of our code (which is very good so far). We don't want to contribute an untested, deeply modified and potentially

Re: Proposal for contributing code from GraniteDS

Hi Franck, IMHO the only problem I see is that user could end with dependent frameworks that could be removed if some refactor is applyed, in this case with reflect classes from granite and other microframework like swiz, parsley or other. Maybe reflect classes could be cut to the minimun in orde

Re: Proposal for contributing code from GraniteDS

Hi Carlos, math & reflect (I forgot about this one) are mandatory. util & collections can certainly be refactored in order to lower dependencies. I need to check about that but, basically, we are ready to contribute all required code. Thanks for your feedback, Franck. 2012/10/3 Carlos Rovira >

Re: Proposal for contributing code from GraniteDS

Hi Franck, I was looking at the validation source in graniteds and I see that dependencies are a bit more complex. From what I see those are the packages needed: * math * reflect * util * collections maybe some other class could be needed... Maybe some refactor could be done to avoid overhead o

Re: Proposal for contributing code from GraniteDS

Thanks for the detailed responses, Franck. I think this could work and would make a great addition to Flex. PPMC folks, any objections? Or should we take a formal vote on this? What should be the next steps? Thanks, Om On Wed, Sep 26, 2012 at 3:07 AM, Franck Wolff wrote: > Om, > > 2012/9/25

Re: Proposal for contributing code from GraniteDS

Om, 2012/9/25 Om > Franck, > > My initial reaction after reading the documentation is that this would be a > great addition to the Flex framework. > > If you don't mind, maybe you could address these concerns I have? > > 1. Can we make sure that this approach does not tie Flex to specific > ser

Re: Proposal for contributing code from GraniteDS

On Tue, Sep 25, 2012 at 1:30 PM, Om wrote: > Can we make sure that this approach does not tie Flex to specific > server side solution (Java in this case)? > This is my exact concern. Great list Om. There is already such a huge group of companies that think if they don't use LCDS or Java/BlazeDS

Re: Proposal for contributing code from GraniteDS

Franck, My initial reaction after reading the documentation is that this would be a great addition to the Flex framework. If you don't mind, maybe you could address these concerns I have? 1. Can we make sure that this approach does not tie Flex to specific server side solution (Java in this cas

Re: Proposal for contributing code from GraniteDS

Hi Carlos, 2012/9/24 Carlos Rovira > Hi Franck, > > I think it would be great. I was in the way to make some > implementation some time ago since flex view validation is problematic > when you try to use MVC but I never get to far. In flex the problem is > that validation and view controls are d

Re: Proposal for contributing code from GraniteDS

Hi Franck, I think it would be great. I was in the way to make some implementation some time ago since flex view validation is problematic when you try to use MVC but I never get to far. In flex the problem is that validation and view controls are dependent and it would be great to have bean valid

Proposal for contributing code from GraniteDS

Hi All, We, at Granite Data Services , are considering contributing part of our Flex client code to this Apache project. Our first thought is to contribute our Bean Validation (aka JSR-303) implementation in ActionScript3: this framework gives an easy and powerful way to