Mach-II, Transfer ORM, ColdSpring...wish me luck :)

Time for me to get out of my procedural programming techniques and jump into the 21st century. Time to get on the OO bandwagon.

For a project that I'm currently working on, it's going to be a trial by fire to absorb the contents of the blog title and be proficient...quickly!!

Kinda wish I was learning Model-Glue, but eh, either Mach-II or Model-Glue will turn my world upside down from the way I program sites now.

Scared, excited and up for the challenge!!!

Yahoo! Mail Beta -- frustratingly.....

sloooooooow....

Is Yahoo's mail beta slow due to the fact that it's trying too much to be like a desktop app or is it a ding on the weight/performance issues with ExtJS or both?

I just know that it's nice eyecandy and it functions well when it's fully loaded...but you have to wait and wait (even on a full T1 pipe at my office).

I'm going back to the original quick version.  I don't need that kinda eye candy.  I'll leave that up to Outlook.


Powered by ScribeFire.

Autocomplete + InPlaceEditor + Proto/Scriptaculous...finally!!

I blogged a while back about trying to mash up Spry/Prototype/Scriptaculous to do an inplace-edit and an autocomplete. Unfortunately, I lost a bit of momentum using Spry for this purpose because we're not using Spry in the office.

I picked up the ball to use just Prototype/Scriptaculous for our needs. What I found out was that there was a bit of a disconnect with Scriptaculous' Ajax.Autocompleter and Ajax.InPlaceEditor (to complete what I needed done).

What I needed: The ability to Add a Tag to a profile with InPlaceEditor but, I didn't want to have multiple versions of the same tag. (Ex. Dog, Dogs, Doggie) I needed to give the person who's inputting a new tag the ability to see tags that are similar to what he/she is currently typing.

Scriptaculous' Ajax.InPlaceEditor builds a form with an input or a textarea on the fly when you click on a link. Awesome! The only issue is that the

<input> or <textarea>
code doesn't include an ID for the html element created. The disconnect is that Autocomplete needs to target an INPUT's ID name.

With this knowledge, I had to make a change to Scriptaculous' library: contols.js. I am using the latest 1.8.0 version, so here is where I made my change at around line 551:


createEditField: function() {
...
fld.id = this.options.formId + '_input';
...
}
After making this change, viewing the generated javascript (god I love the web developer add-on for Firefox), I can see my form's dynamically generated input field, now has an ID. YAY!!!

Now I can continue with the Ajax.Autocompleter to target the INPUT field. But wait...There's a hangup :(

The generated form and the autocomplete execute almost simultaneously and there's an error. My Ajax.Autocompleter is complaining that the INPUT field that I am targetting doesn't exist? Huh? Doesn't exist? OH YEAH!! Need to do this in sequence :) My fix was to put a short setTimeOut function to execute the autocomplete library AFTER the INPUT field has been generated.

PHEW!! What a pain that was. But, hey, I learned alot with this little exercise. I'm almost certain that someone out there has done this before and probably did it better than me. If so, please point me in that direction :)

Here's the demo: Ajax.Autocompleter + Ajax.InPlaceEditor
(Try: Chris or phil or Boot or Hal)

Spry + Autocomplete + InPlaceEditing...anyone?

I have been trying to use Spry's autocomplete with Prototype Ajax.InPlaceEdit function but can't seem to see how to integrate the 2.

I have successfully added Prototypes Ajax.InplaceEdit with ACTB javascript (see if I can get a link up later to this sample).

If anyone has done this or knows how to combine InPlaceEditing with Autocompleting (spry and prototype), please reply :)

I'm surprised at 2 things. 1) Spry hasn't added InPlaceEditing (along with drag/drop) 2)Combining the 2 to begin with and having a demo up somewhere. I'm sure I'm not the only one who needs this combo.

In the meantime, I'll be plugging away at this and see if I can frankenstein the 2.

Back to BlogCFC

After toying around with MangoBlog by ASFusion, I've decided to go back to the tried and true BlogCFC. My last time using Ray Camden's blog engine was 5.0. Now that I'm on 5.9, I can see that there's many more options added than what I remember.

I think the only thing missing from BlogCFC is a Rich Text Editor like TinyMCE or FCKEditor. I know that FCKEditor is built into Coldfusion 8.0, so maybe the next iteration of BlogCFC will incorporate this feature (of course that'll probably push everyone to upgrade from previous versions of CF).

I'm going to have to spruce up the look and feel of the default BlogCFC engine with a new skin. I'll take advantage of my downtime (read: sick from a cold) to make this look prettier :)

Calendar

NAVIGATION

Recent Entries

Recent Comments

RSS

Search

Subscribe

Tags