This will be a CCK field soon!

When flash node was first written (back on Drupal 4.7) the CCK system wasn't so well established, so flash node became a content type in its own right. This was also part of making it a very easy solution for the end user - simply install flash node and off you go.

However, more people are now doing more things with Drupal, and there have been a few enquiries about making a CCK version of flash node.

This is on the development plan, but at the moment I am working up support for Views with flash node.

Once that's done then CCK content is probably next since the core of flash node is pretty stable, and there are really many further features to add (and hopefully not too many bugs left...)

I strongly encourage and support your work. CCK support is final major need for Flash node. Not because I just want to use it. CCK actually is guarantee that Flash Node will not become obsolete. So many great modules died because they lack flexibility and so many cck/views alternatives are in use, recommended and developed because they are customizable. Keep it up!

How I see Flash Node CCK support? Well, FN already have configuration page. Display settings would go to CCK field managemnent screens to configure these for each node. Otherwise its all the same.

Work on flash node for CCK (Drupal 6) has started!

It might be a while as I have never written modules for CCK before. Current plan is to use the FileField module to handle the upload process, and then to have a "Flash node CCK" module that picks up the upload and renders it as flash.

I actually have that working locally as a very rough prototype, but none of the features for sizing etc are done, but I guess it proves the principle.

At present the work flow is create a File Field, then add a Flash CCK field. You give the Flash CCK field the name of the file field you want to render, and that's it. How does that sound? I started trying to integrate the whole lot so you just add Flash CCK and it produces the file field for you, but at the moment it is making the code too complicated for me to get my head round!

Will upload to HEAD when I get on-line properly.

Just installed ImageField just to see (again) how it works. Yes, i think you can learn a lot from ImageField. Standing by for testing.

I started with ImageField, but having never written for CCK before the integration bit was making my head hurt! So that's why the prototype is currently to work with FileField to at least get everything else working. I am then assuming that simply substituting the FileField code with the appropriate ImageField integration will become "clear"...

The good news is that currently the Flash node CCK prototype accepts an upload, and you can now define the height and width, and the auto-detection of height/width is up and running.

So at a very basic level it is much like the early versions of flash node were!

I can see how this is going to be quite neat, since you can now combine flash content with any arbitrary set of other fields, so it makes things pretty flexible.

I just wish I could get my head round the concepts of fields and widgets properly!!

Minor note: Don't forget Lightbox2 module - it plays fine with ImageField images and vice versa. If flashnode could do the same, it would be great. Lightbox2 module already comes with possibility to display flash video and even html code in it, so its just a matter of linking them together. This way you would give Drupal something that took 5 years for youtube ;)

LOL - I'm glad there is someone enthusiastic about FN for CCK (FN4CCK?) I'll get the core module working, then start adding the extra features ;-)

Drupal is a hobby activity for me, so one challenge at a time is plenty!

I think if you need answers, you could join party on CCK here: http://groups.drupal.org/content-construction-kit-cck. This group is active and with lots of members who develop for CCK.

I am sure you already know CCK for Developers page http://drupal.org/node/101742. Info seems not so fresh there to me.

FN for CCK (FN4CCK?)

I think you can drop N from FN after this :D since all nodes will be Flash Nodes. F4CCKFNFN will be new name!

F4CCKFNFN = flash for content construction kit formerly known as flash node.

F4CCKFNFN

Jeepers! How about just "Flashfield".

"FlashField" it is.

Coming on nicely. Still haven't integrated the file upload field neatly yet as I am focussing on the basic generation of flash, but when you activate FlashField you now get a form with all the flash node options on it, including substitution text and flash vars. All the parameters seem to be saving and passing to flash node as expected.

At present FlashField is dependent on flash node to provide the rendering, but I'm thinking of separating it out so people using FlashField don't need to install flash node too?

That then suggests that FlashField is a project in its own right since there is no dependence and people using the CCK version won't want flash node itself?

I'm thinking of making each setting optional on a node basis as to which settings fields are presented? Maybe over-riding for an admin user?

I'm not connected to CVS at the moment, but will upload when I next get a chance.

In the meantime, do any of those interested in "FlashField" have any thoughts on the questions above, or about ideas for "FlashField" in general?

At present FlashField is dependent on flash node ..., but I'm thinking of separating it out ...

I agree fully. But I think you will still need some kind of support or API module that controls Flash sitewise and feeds defaults to CCK module and other areas.

Examples of settings changes from FlashNode to FlashField:

- Default display setting -> goes to "Display fields" tab on Content Type edit page.
- Weight of Flash content -> No need for that since it can be done on "Edit Content Type" page.
- Max/min displayed height/width, Scale factors -> These would go to "Display fields" tab on Content Type edit page, but...

... in "Display fields" tab you have drop down menus with options how to display content in Teaser and Full node view. You cannot set anything there, just choose, so there are 2 ways to go - easy way is to use same FN settings to define teaser/full view settings and feed them to "Display fields" tab drop down menus as "Teaser view" and "Full view" (already you get bonus - you may use bigger movies in teasers and small in full nodes, if you want to).

Harder* way would be to let users to create presets for those drop down menus (as in ImageCache, that works with ImageField). So user can create different presets - f. ex. Preview, Full size, Double size, Still frame, Some other preset. CCK would use these presets in "Display fields" tab drop down menus. User then could choose for teasers Still frame preset and for full node full size and Double size for viewing inside Lightbox2.

* Not necessarily the best ways, since i cannot think of a situation I would use it. For most users easy way would be good enough.

I have taken the plunge and created FlashField as a new project!

It now has its own project page and I just made the first commit of code to CVS. The code is full of debug messages, but it should actually work.

It's rough around the edges and there is no doubt some way to go, but it's a start.

I'm going to set this thread to fixed now. Any FlashField issues should be posted to its own issue queue and not here.

Wicked, thank-you so much for your hard work, really amping to use this:)

For anyone still tracking this thread, FlashField is developing quite nicely and is up and running with pretty much all the flash node features now CCK'd!

It's still only available from CVS as the code is still changing a little too regularly to justify any sort of release, but it's good enough for a "first look".

Like flash node you can run FlashField in stand alone mode, and just render SWFs, or if you have SWF Tools you can render mp3 and flv files.

If anyone tries it out and finds bugs/issues post them on the FlashField queue please!

Im waiting to test. Currently files from http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/flashfield/ cannot be installed as module. I see something in others, but module has no name and description is "This version is incompatible with the 6.5 version of Drupal core".

Should I manually change something? Drupal 6.5 here.

Did you get all the files from CVS? Sounds like the flashfield.info file is missing?