It is a Great Idea Wilbert, nice your work. Merry Christmas.
Printable View
It is a Great Idea Wilbert, nice your work. Merry Christmas.
What amazing things we will be able to do with this new version! It's exciting to know that a large percentage of our users are heading for any and all information they can get about AS3 in anticipation of what is right around the corner for them. Your time spent doing so will not be wasted. As Wilberts component example clearly demonstrates, you will be able to customize things in ways you never dreamed of before.Quote:
Originally Posted by w.brants
Remus is going to blow you all away with his Necro3D package. Guys like Gerbick, ghol, Bret, Stoke and many others are already scoping the earth for compatible AS3 libraries, classes and packages. Wilbert , our quintessential component engineer, offers up goodies almost weekly and makes it look easy. Last but not least, Lucky Monkey couldn't have found a more dedicated man than Bob Hartzell. He's humble, unbelievably talented and what he is doing right now is nothing short of amazing in the time frame he has done it in.
Amen!
Chris, could you recommend a good AS3 book please? I just strated to catch up with as1 and as3 is already here.
Thanks!
Lets see...some solid ones are:
ActionScript 3.0 Cookbook
By Joey Lott, Darron Schall, Keith Peters
I own the actual book but would recommend the compiled html Ebook version instead. Reason being it's easier to copy paste snippets and the actual hard copy had tons of typos.
Actionscript 3.0 Bible
By Rojer Braunstein, Mims H Wright, Joshua J. Noble
I've always bought the bibles and always will. Nuff said :)
Learning Actionscript 3.0
by Rich Shupe and Zevon Rosser
While not as comprehensive as the previous two, it has some good stuff. Especially chapters on design patterns. Worth a read for sure.
I preferred Flex instead of CS3 for AS3 when Koolmoves didn't support it yet. As such I have quite a few Flex programming books which also cover a lot of AS3 but Flex books have a lot of code examples and snippets that make heavy use of E4X which we don't support yet so the three I mention above are better suited for straight up AS3 which is perfect for Koolmoves 7 with little to no code modifications needed.
WOW!!!
Great! Thank you so much!!!
Hello everybody,
Merry Christmas and a Prosperous and Happy New Year for all. :)
During these years I had to "assemble" a script to update the content of my web site with xHTML/CSS/PHP/MySQL/FCKeditor with a File Manager and a "big help of my friends," in order to select the images inside the images' directories and subdirectories and insert them inside the content of a text area field of the database, with text, using the FCKeditor and then, to update the site.Quote:
Originally Posted by Chris_Seahorn
As you can understand, a powerful WYSIWYG Editor component integrated with a File Manager/Upload component is vital in any web project, no matter if it is small or big, Flash or no Flash.
And as you can guess I spent years to grasp the surface of KM5, so components, easy to combine and integrate into my projects are a blessing to me.
I doubt I can put my hand on ASx, neither I have the time, so I need professional and fast results, for this reason I love KoolMoves and components.
In my humble opinion a TextArea WYSIWYG Editor integrated with a powerful File Manager/Uploader component will be the diamond that will generate a lot of prestige and purchases of KM7 among non programmers designers.
Best regards
joejac
^ Don't worry, you will be able to load and update your files on-line. As you know I have been doing this for years now thanks to components built by Chris and Wilbert.
In my experience, they are very useful to YOU rather than your clients, because you can easily edit their sites for them, rather than letting them do it. - After all you're the expert, and what's more you can charge for updates!
Thanks a lot for your reply Laurie.
Where I can get those components? The links are very welcomed.
Best regards
joejac
The current one will be obsolete soon, so if you can hang on till v7 is released I will upgrade it
http://examples.adobe.com/flex2/inpr.../explorer.html
Be it an online based one or a desktop based one (download) this type of thing is useful for everything from showing off what KM7 can do (if built with KM) to marketing (people get to play with the knobs big time before purchase).
It's gonna exist someday...one way or another :)
It's possible to create a sort of tree list with the current list component.
It took a while to figure out but here's an example.
http://www.waterlijn.info/km/as3/TreeList.html
I like where you guys are going with this.
I plan on saying something once I stop drooling all over my keyboard :)
As usual Wilbert...that is just too cool!
Quote:
Originally Posted by w.brants
Thanks Chris :)Quote:
Originally Posted by Chris_Seahorn
I converted it into a component now.
Here's an example of how it can be used.Internally the items are stored in array form; the XML syntax is only used to set the data.Code:var treeData:XML =
<data>
<account name='Mail account 1'>
<folder label='Inbox'/>
<folder label='Personal Folder'>
<folder label='KoolMoves' />
<folder label='KoolExchange' />
<folder label='AS3 related' />
</folder>
<folder label='Sent Items' />
<folder label='Trash' />
</account>
<account name='Mail account 2'>
<folder label='Inbox'/>
<folder label='Personal Folder'>
<folder label='Saved Mail' />
</folder>
<folder label='Sent Items' />
<folder label='Trash' />
</account>
</data>;
function treeLabel(item:Object):String {
// item._name contains the node name
return item._name == 'account' ? item.name : item.label;
}
var tree:Tree = new Tree();
ScriptedSkin.applyTo(tree);
tree.setSize(320, 280);
tree.move(10,10);
addChild(tree);
tree.setDataXML(treeData, false, 0, treeLabel);
tree.expand('label','Mail account 1');
The setDataXML function accepts both a XML object or an URLRequest object.
As you can see, labelling based on field data is possible but works a bit different as you might expect since it doesn't use XML functionality.
Somewhat similar functionality has been added to the List componentCode:var listData:XML =
<data>
<item label='Mail account 1' value ='account 1' />
<item label='Mail account 2' value ='account 2' />
<item label='Mail account 3' value ='account 3' />
</data>;
var list:List = new List();
ScriptedSkin.applyTo(list);
list.setSize(140, 100);
list.move(10,10);
addChild(list);
list.setDataXML(listData);
I built a few Flex forum systems and used all kinds of different methods of handling display of threads. A few versions used a tree component which was visually really a perfect fit. As such I have quite a few mysql driven, PHP based backends that create inline XML already in place for me to use to play with your Tree my friend :)
You are brilliant. It took about three minutes to setup this Koolmoves component to tap a MySQL/PHPtoXML backend structured for use with a Flex 3 tree. What a wonderful job you've done.
http://krazyaboutpizza.co.uk/index.php?page=245
Three minutes is fast Chris :)
I'm glad you like it. You can change the icons it uses if you wish but you might already have noticed that.
I sure did notice. I can also pretty much visually decide the icon used based on incoming data (just like it's Flex counterpart) making it a very useful component (to me at least) indeed.Quote:
Originally Posted by w.brants
I suppose i'd be pushing my luck to ask when you will be surprising me with an Accordian...or HBox/VBox or HDividedBox/VDividedBox....or TileList....or Grid....or Datagrid...or etc et al :) :) ;)
I only ask because you are single handedly making any future need for Flex almost a moot issue here :)
Spoke too soon on the icons. I would prefer a four slice image to add a different icon for parents without children.
Folder closed (has children)
Folder closed (has no children)
Folder open
Item
http://krazyaboutpizza.co.uk/index.php?page=245
As it stands now, if a parent folder is empty it uses the same icon as Item. Not a big deal but maybe better explained visually (this example posted earlier is updated with your icon code in action using the three slice 13x39 image) so you can see what I mean. Empty parent folders are not items...they are folders. To me, Item icons should only be for items and should only be visible if the item in question is contained in a parent folder (which is open).When users start bringing on their own icons I think the fourth icon would be beneficial. It's not as obvious when viewed using simple plus signs and minus signs but when you start to plug in images (and users can really use any images they like) it really stands out IMO. Any thoughts?
BTW...I would have simply referred to your earlier posted example Wilbert but it has no empty parents.