Hi there Folks
I've been digging around Vaadin source code and the way the move to support
compilation for HTML/CSS/JS with Java written only.
Their way of generating source code is pretty similar of what we have in
SystemManager(https://vaadin.com/api/com/vaadin/ui/AbstractComponent.html) and
UI
On 9/16/12 10:44 PM, "Om" wrote:
> Agreed. Will fix it.
>
> Do I need to make a new RC for just this change?
>
> Om
Yes because the signatures will change. I'd wait until sometime Monday in
case someone comes up with something else.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://
Fixed in SVN.
Om
On Sun, Sep 16, 2012 at 10:44 PM, Om wrote:
> Agreed. Will fix it.
>
> Do I need to make a new RC for just this change?
>
> Om
>
>
> On Sun, Sep 16, 2012 at 10:38 PM, Alex Harui wrote:
>
>>
>>
>>
>> On 9/16/12 10:29 PM, "Om" wrote:
>>
>> > On Sun, Sep 16, 2012 at 10:26 PM, A
Agreed. Will fix it.
Do I need to make a new RC for just this change?
Om
On Sun, Sep 16, 2012 at 10:38 PM, Alex Harui wrote:
>
>
>
> On 9/16/12 10:29 PM, "Om" wrote:
>
> > On Sun, Sep 16, 2012 at 10:26 PM, Alex Harui wrote:
> >
> >> +0.95. The word "agrement" is in the licensing screen.
>
On 9/16/12 10:29 PM, "Om" wrote:
> On Sun, Sep 16, 2012 at 10:26 PM, Alex Harui wrote:
>
>> +0.95. The word "agrement" is in the licensing screen.
>>
>>
> I think we can fix this in a dot release? I dont want to delay this release
> because of a typo which appears in a secondary window.
I
On Sun, Sep 16, 2012 at 10:26 PM, Alex Harui wrote:
> +0.95. The word "agrement" is in the licensing screen.
>
>
I think we can fix this in a dot release? I dont want to delay this release
because of a typo which appears in a secondary window.
Thanks,
Om
> On 9/13/12 5:33 PM, "Om" wrote:
>
>
+0.95. The word "agrement" is in the licensing screen.
On 9/13/12 5:33 PM, "Om" wrote:
> We are back again with RC4!
>
> This is the first official release of the InstallApacheFlex AIR
> application. The official Apache distribution is the source kit which can
> contains only source.
>
> Th
Sounds like a plan. Let me know your findings. I will also go through the CMS
link you have shared to understand how we can design the site to fit snugly
with CMS.
Lets start page by page. Let's see how much re-design it takes to get the
index.html redrafted to work with CMS. We can then make t
Ashish,
> Please see my comments inline. A also very easy route would be somebody
> voting me in as a committer. Don't like to ask it out, but I think I have
> dedicated considerable time and my resources to the cause.
I sympathise and agree. Not very long ago I was in exactly your
position. Pa
HI,
> So, you're free to work in Git, or whereever, but we need to figure
> out how we're going to get the changes you make to me (or any other
> committer) and how you are going to implement the changes I need to
> make it work in the CMS on your end.
There is a GIt mirror of the site here:
git:
Please see my comments inline. A also very easy route would be somebody voting
me in as a committer. Don't like to ask it out, but I think I have dedicated
considerable time and my resources to the cause.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 6:06 PM, Erik de Bru
I'm not seeing how that would work. For the code to work in the CMS,
we need to create one or more templates. The content will then have to
be adopted to work in those templates. For a reference and examples,
please see:
http://www.apache.org/dev/cmsref
Now, the example sites shown on that page
Understood, so let's follow this procedure:
1. We will push all our changes to GitHub.
2. We will notify this list about our activity on GitHub repo.
3. You guys can then pick up those files, have a review and let us know what
needs to change for your CMS integration.
4. Since my guys understand t
Ashish,
I'm not sure we understand each other. In order to integrate with the
CMS, I'll have to make substantial changes to the code you submitted
in the JIRA ticket. This means that I'll be effectively be working on
a branch of your code. This branch can only work IN THE CMS. So future
changes yo
I was not able to upload to the repository Om created. Not sure why, but i
created a new repository and will upload the code over there soon.
https://github.com/asdesai/ApacheFlexWebsite.git
The only way for multiple persons to work on this is to use source control.
Since majority of the develop
I'm looking at the code right now, thanks for the upload. And with
modifications I'm sure I can get a pretty close approximation working
in the CMS.
I was confused by all the talk about Git and Github. Maybe I missed
something. What are you trying to achieve using those tools?
EdB
On Sun, Sep
I am confused:-(. What issue are we trying to address here? Committing the code
or integrating the code with CMS?
Once again, the code is already uploaded to the JIRA ticket.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 5:09 PM, Erik de Bruin wrote:
> Hi,
>
> Since
Hi,
Since this project will be heavily dependant on the custom Apache.org
CMS, I don't see how we can collaborate other then using the site's
SVN repo and patches on JIRA tickets (for the non-committers). Please
correct me if I'm wrong.
EdB
On Sun, Sep 16, 2012 at 9:35 PM, Om wrote:
> Done.
>
The code is already attached to the JIRA ticket. I will take some time to get
it checked in into GitHub. Could we use the full codebase attached to the JIRA
ticket meanwhile?
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 3:35 PM, Om wrote:
> Done.
>
> But, since Nick
Done.
But, since Nick and Erik (both committers) are involved, we can probably
get the first version committed and you could continue contributing as
patches. That way anyone else who wants to contribute can do so as well
off of SVN.
Thanks,
Om
On Sun, Sep 16, 2012 at 11:28 AM, Ashish Desai - Z
Om,
Here is my git hub user id, can you please grant access to the repository?
user: asdesai
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Aug 2, 2012, at 4:10 PM, Ashish Desai wrote:
> Thanks om this helps. I will give you my user details soon.
>
> Om wrote:
>
>> Ashish,
>>
>> I hav
Attached the files to the ticket. Please verify. Let us know if you need
anything else for the integration.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 2:19 PM, Ashish Desai - Zootar
wrote:
> There is a JIRA ticket already. Details are below:
>> New Apache Flex webs
There is a JIRA ticket already. Details are below:
> New Apache Flex website
> ---
>
>Key: FLEX-33134
>URL: https://issues.apache.org/jira/browse/FLEX-33134
>Project: Apache Flex
> Issue Type: Task
> Reporter: Tomasz
Yes, I can probably do that.
A JIRA ticket is a great idea, we can also use that to track progress
and discuss specifics (general discussion and ideas or decisions
should be on this list).
EdB
On Sun, Sep 16, 2012 at 8:12 PM, Ashish Desai - Zootar
wrote:
> Great! Would you be able to use the
Great! Would you be able to use the html site code that we have created and
start integrating that with CMS? I can upload it to the JIRA ticket for the
time being.
Ashish Desai
Zootar LLP
ashish.de...@zootar.com
On Sep 16, 2012, at 2:03 PM, Erik de Bruin wrote:
> Hi,
>
>> Erik, could you
Hi,
> Erik, could you work on exploring how to integrate content management on the
> site? We have an initial codebase that
> will be uploaded tomorrow. While we complete that integration we will try to
> finish the rest of the design and issues.
Sure I can. I've added a new 'path' to 'lib/path
26 matches
Mail list logo
