I think a written tutorial with good screenshots is a must. It's also easier to update the text over the years if something changes.
But the video is definitely a plus and a good guide. The video should be something like this: Compiling and Contributing to Apache Flex with IntelliJ by Nicholas Kwiatkowski http://www.youtube.com/watch?v=5COE3hYqCJk This is for IntelliJ 11.1, but not working with the latest IntelliJ version (and maybe because of the change of the source code location git/svn). I think there are a lot of developers out there who want to help, but don't know how. Like me, I have created some issues in the JIRA, but I have no idea how to compile / patch the SDK. I would really like to help and fix bugs in the SDK, but I don't know how. I am waiting for the tutorial. This would be very good for the project, if everybody knows how to compile / patch the SDK. So everybody can fix the bugs you have found yourself. Maybe more people, who are just Flex developers / user, contribute to this project. Thanks! Marcus Fritze Am 29.07.2013 um 11:18 schrieb "Sugan Naicker" <su...@dev-x.co.za>: > Great idea Jude! Simple and effective. > > Rgs, > > Sugan > > -----Original Message----- > From: jude [mailto:flexcapaci...@gmail.com] > Sent: 29 July 2013 05:41 AM > To: dev@flex.apache.org > Subject: Re: [REQUEST] A tutorial on how to fix bugs for the Flex SDK > > I have a suggestion on this tutorial writing thing. If anyone of you that > have this environment setup can record and upload a raw unedited video I can > edit it or rerecord it and republish it. What I'm thinking is that you could > log out and then log back in as guest, then go through recording the entire > process of setting up the environment and testing as a fresh new user. > > I use Camtasia on Mac to do screen recordings like this but there are many > others out there. It may be turn out to be a really long video; that's > alright. The reason is that it may be easier to show people how to set it up > than work on typing everything up. A video demonstration doesn't require any > writing per se. We can also capture small details that sometimes get left > out of tutorials and then make sure these details get into the tutorials. > This does *not* have to be edited at all. > > > On Fri, Jul 26, 2013 at 2:53 PM, Alex Harui <aha...@adobe.com> wrote: > >> Hmm. The source path is really >> "/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spa >> rk/sr c" (with "/src")? And you aren't using RSLs? >> What does a link report say for which Label.as it used? >> >> On 7/26/13 11:57 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >> >>> It was :-( >>> >>> EdB >>> >>> >>> >>> On Fri, Jul 26, 2013 at 4:10 PM, Alex Harui <aha...@adobe.com> wrote: >>>> >>>> >>>> On 7/26/13 2:41 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: >>>> >>>>> Ok, this is what I tried: >>>>> >>>>> I created a new project in FB. It uses the 4.10 SDK in the FB/sdks >>>>> folder. In "project properties/Flex Build Path" on the "Source path" >>>>> tab I added the folder >>>>> "/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/ >>>>> spark >>>>> ", >>>>> thinking this will allow me to work on the classic Spark components. >>>>> >>>>> In my project, I add a Label in MXML. I cmd click on 'Label' to get >>>>> me into the Label source. >>>> Check which Label.as it opened up. It may not be the one from git. >>>> >>>>> I place a trace statement in the constructor. I save, clean the >>>>> project (just to be sure) and launch the project in debug mode... >>>>> No trace statement shows up :-( When I try to put a breakpoint in >>>>> the source, it complains there is no code on that line. >>>>> >>>>> What am I doing wrong? >>>>> >>>>> EdB >>>>> >>>>> >>>>> >>>>> On Fri, Jul 26, 2013 at 1:38 AM, Alex Harui <aha...@adobe.com> wrote: >>>>>> >>>>>> >>>>>> On 7/25/13 3:37 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>>> but also means you don't have to build the SWCs before testing >>>>>>>> your changes. >>>>>>> >>>>>>> Perhaps I missing the point but if you make a change you will >>>>>>> have to recompile that project, you just don't have to recompile >>>>>>> the entire SDK. >>>>>> You are correct, but in my workflow, I don't even have to stop to >>>>>> compile a single project. >>>>>> >>>>>> For this resource module RTE I just worked on, I changed the >>>>>> files, compiled the test case without running any ant scripts, >>>>>> and repeated until it all worked. Then I go run a full build and >>>>>> start up mustella. >>>>>> >>>>>> -Alex >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >> >> >
