Justin, I hear you about the style initialization.
I am coming from making some pretty large commercial components and of the most support questions it's about defaulting styles. I have come to the conclusion, until Adobe finds a better way, for component defaults, this is the best way of simplifying the process for the end user. Theme SWCs are to confusing for them, and including a default css sheet that they have to paste in all the time makes no sense either. As long as you are not adding huge sized skins, this really has no impact on what gets linked in. If you do find yourself needing comprehensive default skins, I advise just making a css sheet for skins and default all the other styles. This way, nothing of file size importance is getting linked in that the end user cannot get rid of. I'm just trying to help, I wish I had people steer me in the right direction so I didn't waste as much time as I have on this stuff. :) On 5/2/07, JWOpitz <[EMAIL PROTECTED]> wrote:
Hi Bjorn, Thanks for the feedback. The initial reason why I extended Canvas over the ListBase classes was my unfamiliarity with the mechanics of those classes. Also, since I was using the Flex Store as my model, that was what they had used too. Basically ignorance to be more precise. Keep in mind this class was originally started in Dec of 2006. After doing some recent research, I was thinking about doing just that: extending the TileBase or ListBase classes. But delving deeper into the mechanisms for those classes, I decided against it as there is yet another level of complexity in tying into and manipulating things at the level I want to in the ListContent property of the ListBase. I haven't completely ruled it out just yet, just haven't had time to really play with the idea. Do you have any suggestions on that particular approach? Thanks, Justin --- In [email protected] <flexcomponents%40yahoogroups.com>, Bjorn Schultheiss <[EMAIL PROTECTED]> wrote: > > Thanks Justin, > > Very generous of you. > Just a question, how come you decided to extend Canvas over one of > the List classes (ListBase, TileBase, etc) ? > > > > regards, > > Bjorn > > > On 01/05/2007, at 11:34 PM, jwopitz wrote: > > > The source is now up there. You can use SVN to get the latest from > > the repository:http://jwopitz-lib.googlecode.com/svn/trunk/ > > > > This is the link to view it in your browser: http://jwopitz- > > lib.googlecode.com/svn/ > > > > > > On 5/1/07, Bjorn Schultheiss < [EMAIL PROTECTED]> wrote: > > Hey jwoptiz, > > > > Is it possible to get the source for this component. > > I've noticed the swc on google code, but i'm more after the source > > as files. > > > > I plan to use it on an existing project and extend it further, with > > functionality such as drag and drop support. > > > > > > > >> http://www.geocitie s.com/jwopitz/portfolio/ tileCanvas/ > >> TileCanvasTest. swf > >> > >> Any comments, constructive criticism, etc. are appreciated. It is > >> still a work in progress. > >> > >> I need to work on a few things: > >> - better drag/drop functionality > >> - data accommodations from other components > >> > >> Once I get my code base straightened out, I will post the source > >> as well. > >> > >> Thanks, > >> jwopitz > >> > >> [EMAIL PROTECTED] com > >> > > > > > > > > > > > > > > -- > > justin w. opitz > > 617.771.6639 > > jwopitz(at)gmail.com > > > > >
-- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
