Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC02D9691 for ; Sat, 24 Mar 2012 16:12:35 +0000 (UTC) Received: (qmail 11074 invoked by uid 500); 24 Mar 2012 16:12:35 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 11021 invoked by uid 500); 24 Mar 2012 16:12:35 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 11012 invoked by uid 99); 24 Mar 2012 16:12:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Mar 2012 16:12:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Mar 2012 16:12:28 +0000 Received: by bkcjg15 with SMTP id jg15so3499988bkc.6 for ; Sat, 24 Mar 2012 09:11:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=9wIVwcyDWHWqke+k9lmS4M12FD8dsFukQSy5DxlPzZ4=; b=lQeQ78qNmp2kah7/qMkcl83iruac6xVIWiQvYpjncpZCCOwDsReNFzC8HeIws3SyNX jP9N38RMqzNhnp2tX+R5T+i/ySgDWSdrwlwBAfqigvNvLeU1Watz+UhrIRVf/F2fYKNJ 0T2pVW3pxBzDNbhoSkGWblz4X5A4R+kXw+KAgEDg2G9A4ffZixQqeh20QsnurTpi+Xi7 UDsB/8RBICbi48X+p01n7dG1k5GjU7+ursoL0d4pALWeIrF3WfGMxwvW5UL0ES8Xn2u4 cq5JgxV78oM/euyzWqMJHsTIGxGTNcXC0FXM+vm2YuIQ5V6dz2sR91Dil37th+9SRhd5 L+sQ== MIME-Version: 1.0 Received: by 10.204.154.202 with SMTP id p10mr5967731bkw.79.1332605511322; Sat, 24 Mar 2012 09:11:51 -0700 (PDT) Received: by 10.205.47.67 with HTTP; Sat, 24 Mar 2012 09:11:51 -0700 (PDT) X-Originating-IP: [173.10.39.57] In-Reply-To: <04be01cd09d2$6df46dd0$49dd4970$@tinylion.co.uk> References: <04be01cd09d2$6df46dd0$49dd4970$@tinylion.co.uk> Date: Sat, 24 Mar 2012 12:11:51 -0400 Message-ID: Subject: Re: Halo x Spark From: Nicholas Kwiatkowski To: flex-dev@incubator.apache.org, info@tinylion.co.uk Content-Type: multipart/alternative; boundary=0015175d07bc20cc7204bbff6614 X-Gm-Message-State: ALoCoQlsJJTTiJXwRdB7+fbSdEqs6+Jnz/mOD1b5UPhQA1kYemNYxye3KbqgiDP2jUnLGVnDYlyp X-Virus-Checked: Checked by ClamAV on apache.org --0015175d07bc20cc7204bbff6614 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable True. But the point I was trying to make was not about the power (which, it is extremely powerful), but that it is powerful, even at the introductory level. Making an Alert Box look like the iOS Alert Box in Halo is damn near impossible without resorting to raster images -- which don't scale, and add a LOT of weight to the framework. -Nick On Sat, Mar 24, 2012 at 11:26 AM, tinylion development wrote: > That=92s just the thing > > The example you=92ve shown isn't really a very > different look than the standard one. Just > different images in basically the same component. > > With spark skin you can make a component radically > different in ways that would be impossible in > halo. > > Try for example in halo, taking the stand list > component and just with skinning turn it into a > faux 3D rotating circle of selectable shapes or > images, each different and with different roll > over and selection images and then take that same > code and with some small changes make the circle a > horizontal fading line. > > Ok, I know there may not be a good UX reason for > this. But the way you make a component look in > spark is limitless. Where as in halo it's just a > different cover over basically the exact same > thing > > Sorry if this was not put very well, but the > payoff in using spark is huge. > > Glenn > tinylion > > > -----Original Message----- > From: Williams Farias > [mailto:will.farias@gmail.com] > Sent: 24 March 2012 04:22 > To: flex-dev@incubator.apache.org > Subject: Re: Halo x Spark > > Ok, so please show me a great example with Spark > skinning, with really custom components... and of > course, with source code... like that: > http://fleksray.org/skins/scribble/Scribble.html > > If you see the source code, you=B4ll se the > simplicity, its ridiculous, just CSS and images. > > Its not about what the technology can do... its > about who will use it and whith what ammount of > work? Man, developers usually dont do design... > they only code the things... acess databases and > so on. Spark components dont have so much > impressive skinning examples, in my point of view, > because of > that: designers where excluded from skinning > components! So, if only hardcode developders can > do it... what meters if it=B4s the best whay? if > nobody will use it... I what just to see an > exemple, with source code with a great custom > skin... > > If you have, please show me. > > > 2012/3/23 superabe superabe > > > I disagree. I think Spark skinning was the best > thing to happen to Flex. > > It makes it possible to do some insanely custom > skins that I would > > have shuddered to think about attempting to do > with Halo > > > > Yes it makes it harder to simply style based > skinning initially, but > > if you use that a lot, its possible to build > that style support in in > > your core component class, once and then reuse. > > It's a tradeoff that I am completely happy to > make. > > > > One important piece to skinning in Spark is to > understand the Catalyst > > workflow. > > I realize the product itself is discontinued, > but even at the state > > its in, it great for taking assets from > designers and generating FXG > > graphics or even mxml skin code, that you can > then use in your Flex app. > > > > superabe > > > > On Fri, Mar 23, 2012 at 8:25 PM, Richard Oren > wrote: > > > > > I am not sure what you were trying to do... > but with a little bit of > > > research you should have been able to still > use Flex 4 for your project. > > > There is a learning curve to get behind the > concept so I have felt > > > your pain before but if you stick with it it > does get somewhat > > > easier. I have had to resort back to OLD > school ways and Draw a lot > > > of graphical stuff > > for > > > Mobile Development with the Drawing API, but > for desktop stuff you > > > should be able to go with MXML. > > > > > > > > > > > > http://blog.flexexamples.com/2009/11/04/setting-a- > custom-horizontal-sc > > roll-bar-skin-on-a-spark-list-control-in-flex-4/ > > > > > > Hang in there! You can Do it! :) > > > > > > On Fri, Mar 23, 2012 at 3:44 PM, Cortlandt > Winters > > > > > >wrote: > > > > > > > Hi Will, > > > > > > > > I do have a prediction. And it's not a dire > one. > > > > > > > > It's true what you say, but though this is > an area that the flex > > > > components most need some TLC in, I'm > confident that it's the one > > > > area > > > that > > > > it's most likely to get it. > > > > > > > > As for predictions, I predict that Adobe > will do what it said it > > > > will > > do > > > > and it will leave Flex "5?" in a pretty > stable state. It will take > > > > some time for folk to get familiar with the > apache process and the > > > > framework > > > and > > > > to determine how to deal with scrolling on > mobile apps that have a > > whole > > > > new level of performance requirement, but > that there are going to > > > > be > > > plenty > > > > of opportunities to make both web based apps > easy to skin and > > > > mobile > > ones > > > > performant. > > > > > > > > The toughest part about taking flex and > making it open source is > > > > that > > > most > > > > flex users are not component developers, > they are end user app > > > developers, > > > > but as far as folk that are comfortable with > styling and skinning > > > > there should be a lot of easily available > expertise to create a good system. > > > > > > > > > > > > On Fri, Mar 23, 2012 at 6:16 PM, Williams > Farias < > > will.farias@gmail.com > > > > >wrote: > > > > > > > > > Greatings everyone, > > > > > > > > > > I=B4d like to know why does Spark skining is > so dificult to get a > > simple > > > > > result. > > > > > > > > > > I=B4m building now a web application and I > need just to skin the > > > ScrollBar. > > > > > Ok, in Flex3 i just open my Flash CS5, > create a new Symbol and > > "Export > > > > for > > > > > actionscript". Then i just add 4 new lines > in my CSS style code, > > > > > and > > > its > > > > > done. I have now a simple and 2 minuts > made scrollbar. > > > > > > > > > > But in Spark component... ohhh, what a > brutal work i=B4d had to take... > > > > > create a new Style... and put everything > on the code... ohhh > > > > > man, > > > thats a > > > > > really waste of time with hundreds of > codes lines and without a > > design > > > > > interface to see how it looks like... in > my opinion its too much > > > > > work > > > for > > > > > such a little result! > > > > > > > > > > Just because of that scrollbar man, i had > to decide to use Flex > > > > > 3 > > > insted > > > > of > > > > > 4!!! A simple and mediocre scrollbar > skin! > > > > > > > > > > I was wondering: how can the most simple > thing to do in Flex > > > > > could be transformed in a bunch of lines > and hard work as that > > > > > scrolllBar > > skin? > > > > > > > > > > If i could propose something to chance in > the next releases of > > > > > Flex, > > > is a > > > > > mix of Halo and Spark Skins. I think that > Flex3 skinning is much > > > > > more simple and intelligent to do. > > > > > > > > > > Antoher thing that frightened me was to > read that Adobe will not > > update > > > > > more the Design View of Flash Builder! > Does Apacge group have > > > > > any prediction about this? > > > > > > > > > > Thanks! > > > > > > > > > > Williams Farias > > > > > > > > > > > > > > > > --0015175d07bc20cc7204bbff6614--