Once we fill enough content we will figure out how to put into the Apache.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-github-repo-tp63786p63890.html
Sent
Ah, I see that Apache org on Github has disabled wiki pages. Sorry for the
noise :-(
Thanks,
Om
On Mon, Aug 14, 2017 at 11:17 AM, piotrz wrote:
> Om,
>
> What do you mean by check in those doc to flexjs source ? Do you mean
> create
> in our FlexJS repo [1] similar wiki tab as it is currently
Om,
What do you mean by check in those doc to flexjs source ? Do you mean create
in our FlexJS repo [1] similar wiki tab as it is currently on Olaf's github
?
[1] https://github.com/apache/flex-asjs
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context
I think Github is a better way to crowd-source documentation than asking
folks to write to a Wiki page.
It enables anyone to start working on documentation and then send a PR.
That said, Olaf, since you are already a committer, you can simply check in
the docs into the flex-asjs git repo and conti
Note that we can and have given out Apache Flex wiki edit access to
non-committers.
If the plan is to move this content to Apache someday, it is prudent to
make sure contributors have agreed to that before contributing. Having
this work contributed directly to the Apache Flex wiki implies that
ag
Let's just focus on content for now... there's still a way to go ;-)
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-github-repo-tp63786p63864.html
Sent from the Apache Flex Development mailing list archive a
Maybe that's the right way. Move everything from the scratch to Github WIKI
in Apache repo. I will be definitely working on getting as much as I can
filled.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.c
I’m not sure if it’s enough or not. I think you should explicitly make the wiki
Apache to be totally sure.
> On Aug 13, 2017, at 11:02 PM, Olaf Krueger wrote:
>
> OmPrakash Muppirala wrote
>> That said, if you plan to migrate it to the Apache Flex project at a
>> future
>> point, it will be eas
OmPrakash Muppirala wrote
> That said, if you plan to migrate it to the Apache Flex project at a
> future
> point, it will be easier if you add an Apache V2 license to your repo
> right
> away.
That was the first thing that I've done after creating the repo [1]
But cause you mention it I just wond
Olaf,
I think you should do what you feel comfortable given that you are putting
most of the work 😊
That said, if you plan to migrate it to the Apache Flex project at a future
point, it will be easier if you add an Apache V2 license to your repo right
away.
Thanks,
Om
On Aug 13, 2017 12:17 PM,
>By GitHub pages you mean as part of Apache ?
No. Github pages use Jekyll as static site generator under the hood and
Jekyll supports Markdown to generate the pages.
So the migration should not so much effort.
At the end, each particular article is represented by its particular file
then which cou
By github pages you mean as part of Apache ? I'm not enough familiar with
some of the stuff on github.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-
Ups, overlooked this Post...
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-github-repo-tp63786p63846.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
The history you mentioned is of the Home file.
Take a look at this [1] to see the moonshine history.
Maybe we should move it all sooner to a docs dir and publish it via github
pages. We probably have better control of all the content then.
HTH,
Olaf
[1] https://github.com/ok-at-github/flexjs
Something is wrong after vacation with me :) I see revisions now. :) Sorry
for the span :) I will continue filling of wiki.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-wi
Olaf,
NVM I figure out how it is working. Another stranger things is that I've
edited Moonshine IDE page, but I don't seen in the revision my changes [1].
Maybe I should be added as contributor ?
[1] https://github.com/ok-at-github/flexjs-docs/wiki/Home/_history
Thanks,
Piotr
-
Apache Fle
Olaf,
I think I get lost a bit. I've tried edit Moonshine sub page. I clicked on
it and click Edit, but it's appear as an separate page. [1][2]
Why it happened ?
[1] https://github.com/ok-at-github/flexjs-docs/wiki/Moonshine-IDE
[2] https://github.com/ok-at-github/flexjs-docs/wiki/Moonshine
Tha
One suggestion:
I think you should explicitly set a permissive license to any content on the
wiki so we can repurpose it however we like without worrying about licensing
afterwards.
> On Aug 9, 2017, at 2:13 PM, Olaf Krueger wrote:
>
> Hi guys,
> it seems to me that since Adobe announced the
I meant the “copied JS”, but yes.
> On Aug 11, 2017, at 11:23 PM, Olaf Krueger wrote:
>
> Forget about this:
>
>> The advantage of MXML is that we can declare both JS code and the CSS in
> the same file.
>
> I think you mean AS instead of JS?!
>
> Thanks,
> Olaf
>
>
>
> --
> View this mess
>Go for it! :-)
Done! [1]
Looking forward to following the steps by myself.
If I'll be successful I'll add a working FlexJS example to the wiki.
Olaf
[1]
https://github.com/ok-at-github/flexjs-docs/wiki/Adapting-HTML-CSS-JS-project
--
View this message in context:
http://apache-flex-develop
Forget about this:
>The advantage of MXML is that we can declare both JS code and the CSS in
the same file.
I think you mean AS instead of JS?!
Thanks,
Olaf
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Docs-Started-with-some-docs-using-a-github
Go for it! :-)
> On Aug 11, 2017, at 3:26 PM, Olaf Krueger wrote:
>
> This is an awesome tutorial, thanks Harbs!
> Hope I'll have some time to follow these steps by myself.
>
> However, if I'll get your permission I will definitely help to put in on the
> github wiki.
>
> Maybe we're also able
This is an awesome tutorial, thanks Harbs!
Hope I'll have some time to follow these steps by myself.
However, if I'll get your permission I will definitely help to put in on the
github wiki.
Maybe we're also able to build a working example including a live demo...
Thanks,
Olaf
--
View this m
Let’s just focus on getting documentation written for now. It can always be
re-organized later.
I just wrote what I think is a useful tutorial on using random HTML/CSS/JS.
This should probably be included somehow…
https://docs.google.com/document/d/1pW599xo-Icys-xXEeNi6tbTcH-iMepbTR6WcviLy7i8/e
Olaf,
I have in my head that we should some day create such website using FlexJS,
but it would require some longer time.
Focusing on your documentation idea is the better one for now. I hope when
it will be full we could automatically somehow generate some website and
push to Apache everything. :
Nicholas Kwiatkowski-2 wrote
> The current site is actually managed by a static-site generator using
> markdown.
What do you think about creating a site that is dedicated to FlexJS?
@Piotr
I've started to put some docs together for the mdl:badge bead. [1]
It's not complete and only a first shot.
Getting a sub-domain isn't a big deal. We just have to request it from
Apache Infra. I doubt that getting a domain name hosted elsewhere with the
"apache" name it will fly, though.
The current site is actually managed by a static-site generator using
markdown. I've jerry-rigged it so that if yo
Hi Piotr,
>As for the examples maybe it's worth to put them into FlexJS Tour where
Peter start initial work [1].
Is this FlexJS Tour already hosted anywhere as a live demo?
>Anyone know whether we could take from Apache some new domain or how to put
it as subpage of our website?
Would be great
Hi Olaf,
Great idea!!
As for the examples maybe it's worth to put them into FlexJS Tour where
Peter start initial work [1]. I will refresh it once I get back from
vacation. Anyone know whether we could take from Apache some new domain or
how to put it as subpage of our website?
I will start slo
Great input from all of you, thanks!
Unfortunately, I'm pretty sure that I don't know most of the FlexJS stuff
myself so expect some traffic here on the list related to all the topics
next time.
I'd like to create a demo (source code and live demo) for each particular
topic and I think it makes se
Data Binding needs special coverage because it requires some getting used to.
I’m not sure what the status of formatters and validators are. I think pretty
weak at the moment.
We’re using the MDL dialog.
Another good topic is the fact that there’s a big difference between the
behavior of “visi
please add few pages on following topics. These are commonly used in
enterprise applications.
FlexJS Data Binding
Formatters - Date Formatter , Number Formatter etc
Validators - StringValidator, DateValidator etc
Popupwindow or Dialog in FlexJS
File Browse, Upload and Download
HTTPService
T
I recommend including a review of basic MXML language features in the
getting started material. Things like binding, states, and even just how to
add children to containers, listen to events, and things like that. It's
good for people completely new to Flex/FlexJS, but I think it's also
important f
+1.
Here’s some topics that we need:
1. Different Layout beads and what they do.
2. What beads can be applied to which components
3. List of components and differences between them (i.e. Container vs Group)
There’s probably much more, but these come immediately to mind.
> On Aug 9, 2017, at 2:1
34 matches
Mail list logo
