incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik de Bruin <e...@ixsoftware.nl>
Subject Re: Apache Flex website codebase
Date Sun, 16 Sep 2012 22:06:57 GMT
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 are pretty lame. I'm sure we
can do much better, especially if we're willing to stretch the CMS to
it's limits. But we'll have to make changes to your design to allow
for limitations of the CMS.

The only way I see this working is that you work on a reference design
(in Github or something) and that I and the other committers work in
the CMS to match that design as closely as possible. If you could host
a working copy of the reference design somewhere where we all can
review it, and we work in the "again" area as if it were a whiteboard,
everyone can keep an eye on each others work.

Also, I dislike jQuery with a vengeance. I don't think that a design
that looks as awesome as what you're working on need any animations or
fancy stuff like that. I think it's better to stick to plain HTML, CSS
and JavaScript, and keep things as simple as possible, so we make it
easy for others to contribute and keep the site up to date (although
effective templating will certainly help in that regard as well).

Also, what kind of browser support are you aiming at? Top of the line,
fully updated HTML5 compatible browsers on Win7, or are you trying to
get some backwards compatibility, say all the way back to XP with IE6
- 7, FF 3.6 on the Mac, Linux variations?

EdB



On Sun, Sep 16, 2012 at 11:39 PM, Ashish Desai - Zootar
<ashish.desai@zootar.com> wrote:
> 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 the code well, we can make changes quickly for you.
> 5. All the JQuery related animation work will be done on it in the coming weeks and contributed
to GitHub.
>
> Let me know if this sounds reasonable.
>
> Ashish Desai
> Zootar LLP
> ashish.desai@zootar.com
>
>
>
> On Sep 16, 2012, at 5:31 PM, Erik de Bruin <erik@ixsoftware.nl> wrote:
>
>> 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 you were planning for the site (as compared to the upload in
>> the JIRA ticket) will need to be made as patches for the SVN repo. You
>> can find the repo for the site here:
>>
>> https://svn.apache.org/repos/asf/incubator/flex/site/trunk/
>>
>> I'll be starting work on the new look and feel in a kind of a
>> whiteboard: unlinked anywhere, available only via direct URL. You can
>> find it in the repo in "content/flex/again/", the direct URL will be:
>>
>> http://flex.staging.apache.org/flex/again/
>>
>> 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.
>>
>> EdB
>>
>>
>>
>> On Sun, Sep 16, 2012 at 11:23 PM, Ashish Desai - Zootar
>> <ashish.desai@zootar.com> wrote:
>>> 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 development has been done by my developers, and will continue to to work on
it till we come up with a final flawless product, GitHub is the only way we can contribute
(as I am not  a committer yet & and not sure when I will be).
>>>
>>> But for a collaborative effort, a source control becomes much necessary. Hope
this clears the confusion. Please continue integrating with CMS while we polish the website
to standards.
>>>
>>> Ashish Desai
>>> Zootar LLP
>>> ashish.desai@zootar.com
>>>
>>>
>>>
>>> On Sep 16, 2012, at 5:16 PM, Erik de Bruin <erik@ixsoftware.nl> wrote:
>>>
>>>> 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 16, 2012 at 11:13 PM, Ashish Desai - Zootar
>>>> <ashish.desai@zootar.com> wrote:
>>>>> 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.desai@zootar.com
>>>>>
>>>>>
>>>>>
>>>>> On Sep 16, 2012, at 5:09 PM, Erik de Bruin <erik@ixsoftware.nl>
wrote:
>>>>>
>>>>>> 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 <bigosmallm@gmail.com>
wrote:
>>>>>>> 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 - Zootar <
>>>>>>> ashish.desai@zootar.com> wrote:
>>>>>>>
>>>>>>>> Om,
>>>>>>>> Here is my git hub user id, can you please grant access to
the repository?
>>>>>>>> user: asdesai
>>>>>>>>
>>>>>>>> Ashish Desai
>>>>>>>> Zootar LLP
>>>>>>>> ashish.desai@zootar.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Aug 2, 2012, at 4:10 PM, Ashish Desai <ashish.desai@zootar.com>
wrote:
>>>>>>>>
>>>>>>>>> Thanks om this helps. I will give you my user details
soon.
>>>>>>>>>
>>>>>>>>> Om <bigosmallm@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Ashish,
>>>>>>>>>>
>>>>>>>>>> I have created a new repo here:
>>>>>>>>>> https://github.com/bigosmallm/ApacheFlexWebsite
>>>>>>>>>>
>>>>>>>>>> You will need to create an account on github.com
and give me your
>>>>>>>> userid so
>>>>>>>>>> I can add you as a collaborator to this Repo.   Anyone
else interested
>>>>>>>> in
>>>>>>>>>> helping out, please do the same and I can add you
as collaborators.
>>>>>>>>>>
>>>>>>>>>> Alternatively, individuals can 'fork' this into their
own github repos
>>>>>>>> and
>>>>>>>>>> send 'Pull requests' when it is time to merge it.
 A ton of help and
>>>>>>>>>> tutorials on using github can be accessed here:
>>>>>>>> https://help.github.com/
>>>>>>>>>>
>>>>>>>>>> Please keep in mind that Apache nor Apache Flex has
any control over
>>>>>>>> what
>>>>>>>>>> is contributed to this Github repo.  Nor does it
come under the Apache
>>>>>>>>>> license.  I am setting this up only as a convenience
for non-committers
>>>>>>>> to
>>>>>>>>>> work together on a common codebase.  When everything
is finalized, the
>>>>>>>> code
>>>>>>>>>> will be 'committed' into the official Apache Flex
SVN repo at which
>>>>>>>> point
>>>>>>>>>> the Github repo will be retired.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Om
>>>>>>>>>>
>>>>>>>>>> On Thu, Aug 2, 2012 at 8:35 AM, Ashish Desai - Zootar
<
>>>>>>>>>> ashish.desai@zootar.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Om,
>>>>>>>>>>> Could you setup the github project for the new
website and also give me
>>>>>>>>>>> some pointers on how to integrate with CMS? I
think we can do the work
>>>>>>>> of
>>>>>>>>>>> integrating with CMS for Nick.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Ashish Desai
>>>>>>>>>>> Zootar LLP
>>>>>>>>>>> ashish.desai@zootar.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Jul 5, 2012, at 4:22 PM, Om <bigosmallm@gmail.com>
wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Not a problem, Ashish.  As I said, no pressure
:-)
>>>>>>>>>>>>
>>>>>>>>>>>> I will set up a public github project and
send the instructions soon.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Om
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Jul 5, 2012 at 12:55 PM, Desai, Ashish
S <
>>>>>>>>>>>> ashish.s.desai@jpmorgan.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Om,
>>>>>>>>>>>>> Give my team few days to build and join
as many dots possible and
>>>>>>>> put a
>>>>>>>>>>>>> version that everyone can work upon.
Does that sound reasonable?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Meanwhile, sure we can create a github
project.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Ashish
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com]
On Behalf Of Om
>>>>>>>>>>>>> Sent: Thursday, July 05, 2012 3:52 PM
>>>>>>>>>>>>> To: flex-dev@incubator.apache.org
>>>>>>>>>>>>> Subject: Apache Flex website codebase
>>>>>>>>>>>>>
>>>>>>>>>>>>> Ashish/Nick/Tomasz,
>>>>>>>>>>>>>
>>>>>>>>>>>>> No pressure, but if you start putting
up the code on GitHub, the
>>>>>>>>>>>>> collaboration could be made easier. 
I can help set up the github
>>>>>>>>>>> project
>>>>>>>>>>>>> if you'd like.  Please let me know.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Om
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jul 5, 2012 at 12:45 PM, Nick
Kwiatkowski (JIRA) <
>>>>>>>>>>> jira@apache.org
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> [
>>>>>>>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/FLEX-33134?page=com.atlassian.ji
>>>>>>>>>>>>>>
>>>>>>>> ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1340
>>>>>>>>>>>>>> 7423#comment-13407423]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Nick Kwiatkowski commented on FLEX-33134:
>>>>>>>>>>>>>> -----------------------------------------
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Om, my thoughts as well.  Additionally,
I will have to see how I can
>>>>>>>>>>>>>> break the CMS to best accomplish
one long page.  It /can/ be done, I
>>>>>>>>>>>>>> think, but the question is do we
want to that direction.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I printed out the PSD on my plotter
and have it on my whiteboard as
>>>>>>>>>>>>>> separate pages.  I like it, and I
think it could be easily scaled
>>>>>>>> for
>>>>>>>>>>>>>> mobile too... I think...
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> New Apache Flex website
>>>>>>>>>>>>>>> -----------------------
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>            Key: FLEX-33134
>>>>>>>>>>>>>>>            URL:
>>>>>>>> https://issues.apache.org/jira/browse/FLEX-33134
>>>>>>>>>>>>>>>        Project: Apache Flex
>>>>>>>>>>>>>>>     Issue Type: Task
>>>>>>>>>>>>>>>       Reporter: Tomasz Maciag
>>>>>>>>>>>>>>>       Assignee: Nick Kwiatkowski
>>>>>>>>>>>>>>>    Attachments: apache_flex_website_psd.zip.001,
>>>>>>>>>>>>>> apache_flex_website_psd.zip.002,
apache_flex_website_psd.zip.003
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> This message is automatically generated
by JIRA.
>>>>>>>>>>>>>> If you think it was sent incorrectly,
please contact your JIRA
>>>>>>>>>>>>>> administrators:
>>>>>>>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/secure/ContactAdministrators!default.js
>>>>>>>>>>>>>> pa For more information on JIRA,
see:
>>>>>>>>>>>>>> http://www.atlassian.com/software/jira
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> This email is confidential and subject
to important disclaimers and
>>>>>>>>>>>>> conditions including on offers for the
purchase or sale of
>>>>>>>>>>>>> securities, accuracy and completeness
of information, viruses,
>>>>>>>>>>>>> confidentiality, legal privilege, and
legal entity disclaimers,
>>>>>>>>>>>>> available at http://www.jpmorgan.com/pages/disclosures/email.
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ix Multimedia Software
>>>>>>
>>>>>> Jan Luykenstraat 27
>>>>>> 3521 VB Utrecht
>>>>>>
>>>>>> T. 06-51952295
>>>>>> I. www.ixsoftware.nl
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ix Multimedia Software
>>>>
>>>> Jan Luykenstraat 27
>>>> 3521 VB Utrecht
>>>>
>>>> T. 06-51952295
>>>> I. www.ixsoftware.nl
>>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Mime
View raw message