cfwindow -> Bootstrap Modal article

[cutterbl]

This is the cfwindow to Bootstrap Modal article, demo, and supporting files. I can definitely see multiple articles per tag, showing how to do this in different libraries (Bootstrap, jQueryUI, ExtJS, etc).

[cfjedimaster]

As an FYI, we do not want multiple articles per tag. We want to focus on one solution. Each article will end though with a list of alternatives.

[cutterbl]

OK, so that's how I've structured this one. Do you want this? Or would you rather I write a JQUI solution to go along with your tooltip example?

[cutterbl]

Ok, just saw the merge.

[cfjedimaster]

Sorry if I wasnt clear. I'm ok on multiple solution providers, just not multiple solutions. Ie, I'm cool with framework X being used to demo a replacement for cfX and framework Y for some other tag. I just want each INDIVIDUAL solution to focus on one framework.

On Tue, Jan 28, 2014 at 10:06 AM, cutterbl notifications@github.com wrote:

Ok, just saw the merge.

Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/ColdFusion-UI-the-Right-Way/pull/5#issuecomment-33492703 .

Raymond Camden, Web Developer for Adobe

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

[cutterbl]

I'm with ya. Thanks for the clarification.

[chopki]

Would it not be a more usable/simple guide if it were to focus on one library/framework for the main articles? Note that a large part of the audience this is aimed at is people using these tags because the dont know how to do it in JS themselves - you dont want to confuse the matter further.

[cfjedimaster]

Well, imo, I think we gain more benefit from showing different frameworks. I don't want to fall into the jQuery trap of, "Oh, I'm doing AJAX, therefore I must use jQuery."

On Tue, Jan 28, 2014 at 10:25 AM, chopki notifications@github.com wrote:

Would it not be a more usable/simple guide if it were to focus on one library/framework for the main articles? Note that a large part of the audience this is aimed at is people using these tags because the dont know how to do it in JS themselves - you dont want to confuse the matter further.

Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/ColdFusion-UI-the-Right-Way/pull/5#issuecomment-33494847 .

Raymond Camden, Web Developer for Adobe

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

[chopki]

Yes that's true and it makes sense to not push people into a "one library to rule them all" mindset.

I guess I am unclear as to whether the goal is supposed to be a drag and drop solution people can put into their projects to cure CF front end tags or whether its more of a 'Hey look you can do it without them' learning experience.

[cfjedimaster]

Oh god no - definitely NOT a drag and drop solution! That type of thinking is what leads to stuff like cfpod, etc. No, the idea more is to introduce people to UI libraries done client side and how easy they can be to use.

On Tue, Jan 28, 2014 at 10:57 AM, chopki notifications@github.com wrote:

Yes that's true and it makes sense to not push people into a "one library to rule them all" mindset.

I guess I am unclear as to whether the goal is supposed to be a drag and drop solution people can put into their projects to cure CF front end tags or whether its more of a 'Hey look you can do it without them' learning experience.

Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/ColdFusion-UI-the-Right-Way/pull/5#issuecomment-33498345 .

Raymond Camden, Web Developer for Adobe

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

[adamcameron]

I definitely agree with you here Ray: we don't want to be writing people's code for them, we simply want to demystify the whole notion that it's easier to implement this functionality with CFML tags than it is with "native" mark-up and JS.

That said, I'm not so clear on why we'd only definitely want ONE solution per topic? Could we not present one MAIN solution per topic, but also be able to have "alternative solutions" too? Are you thinking it would just be a bit of information overload?

Cheers for staying on top of the activity here, btw... still trying to enhance my Git skills, and find some time to write some code!

[cfjedimaster]

I think it would be overload.

However - here is an idea.

I meant for the list of shit at the end to be a list of alternative engines, ie "this framework can also do it". But we could ALSO include blog entries to more specific things as well.

So as an example. Imagine I'm doing cfgrid and I use jqgrid as the main solution. In my list of alternatives I'd mention the Ext Grid. The intent was to just link to the Ext Grid itself. But we could also include links to more specific blog entries ("CF and Ext Grid", "CF and Ext Grid part 2") by random folks.

So maybe the section becomes:

Alternative and Other Articles

On Tue, Jan 28, 2014 at 3:58 PM, Adam notifications@github.com wrote:

I definitely agree with you here Ray: we don't want to be writing people's code for them, we simply want to demystify the whole notion that it's easier to implement this functionality with CFML tags than it is with "native" mark-up and JS.

That said, I'm not so clear on why we'd only definitely want ONE solution per topic? Could we not present one MAIN solution per topic, but also be able to have "alternative solutions" too? Are you thinking it would just be a bit of information overload?

Cheers for staying on top of the activity here, btw... still trying to enhance my Git skills, and find some time to write some code!

Reply to this email directly or view it on GitHubhttps://github.com/cfjedimaster/ColdFusion-UI-the-Right-Way/pull/5#issuecomment-33531581 .

Raymond Camden, Web Developer for Adobe

Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: cfjedimaster

[adamcameron]

Yeah good! I like that.

Good thinking mate.

[cutterbl]

Speaking of, I have plenty of material for jqGrid, ExtJS (though older) and DataTables