Another one. Blah.
-
Recent Posts
Recent Comments
- Brian on Test
- Brian on Quick Update
- Asa Julian on Quick Update
- Srikant Raghavachari on At Long Last… 1.0!
- Mats on At Long Last… 1.0!
Archives
Categories
Meta
The Extensible blog’s RSS feed seems to be having some issues, so this is a test post. Apologies for the interruption.
So that it’s not a total loss, here’s a cute kitten:

Extensible is growing, and we’re looking for developers interested in getting in on the ground floor of something cool. We’ll have lots of opportunities for product development, project work, training, you name it. Since we are still early on in building the company, you’ll be able to step in and make a huge impact on our direction, culture and success.
Extensible was founded by Brian Moeskau, original cofounder of Ext JS (now Sencha, a 100+ person, VC-funded company). Our first product has been shipping successfully for over a year now and we’re aggressively looking to expand our business into new areas. We’re located in Austin, Texas and looking to have an impact on the local technology scene. Through Extensible’s products and open source initiatives you could have the opportunity to write code used by hundreds of companies around the world.
If this post sounds interesting to you or you know someone who might be a fit, please let us know! We don’t have a formal application process — just send over your resume or LinkedIn page and let us know a little bit about yourself and we’ll go from there.
I’m pleased to announce the latest maintenance release for each branch of Extensible:
One notable “feature” that was added recently in both 1.0.2 and 1.5.1 is a new file in the root of the project called Extensible-config.js. One common annoyance in the past has been how best to distribute the Extensible examples for ease of setup and use by end developers. Especially under Ext 4.0+, which introduced dynamic loading via Ext.Loader, this became quite a challenge since dynamic loading is ideal for Extensible development, but terrible performance-wise for public release. How best to maintain the needed JS and CSS includes for both Ext and Extensible, across all examples and for both development and release?
The answer now is Extensible-config.js, which writes the JS and CSS includes into the examples dynamically at runtime based on the configuration options specified in that file. Now with a simple config setting you can switch the deployment mode between “release” and “debug” (or “dynamic” under 1.5.1 to use Ext.Loader), or change the root paths for Ext and/or Extensible to easily facilitate testing against different versions. The examples should now work well out of the box (no more local editing of paths or .htaccess files required!) but take a look at the source comments in Extensible-config.js if you’d like to find out more.
While shopping for gifts for my daughter before Christmas this home office play set from Playmobil caught my eye:
Initially I just thought it was funny because it looked like a “Harry Potter at age 35″ set where he’s long graduated from Hogwarts and is now a disaffected office drone, plugging away at his TPS reports. But on closer inspection, I noticed something quite interesting on Harry’s computer screen:
Looks uncannily similar to some other software I’ve seen before…
It makes me happy to see Extensible products being put to good use in the real world!
Have an example of Calendar Pro being used in your own software? Please share!
Well, OK — New Year was a couple of weeks ago. Still, I thought it might be a great time to usher in 2012 with a little status update about what’s going on in Extensible land and what the immediate plans are.
For the past few weeks I’ve been fixing bugs, including a few pretty important ones, and preparing for the next maintenance releases of both the Ext 3.x and Ext 4.x branches of the calendar. Most importantly, as of today Calendar Pro is fully Ext 4.1-compatible, at least as of the most current beta version (things could still change, but I’m hopeful that any remaining issues that might come up will be minor). Although Ext 4.1 is a minor point release, it’s actually a huge revamp of the rendering and layout systems under the hood, so some hiccups were to be expected. These have been addressed and the calendar is back in full working form.
I have a few additional issues to iron out and some build process improvements to make, but I expect to be able to put out the new releases within the next week or so.
I’ve also been working on recurrence support, off and on, for a while now. Most recently I’ve been porting (well, rewriting) the existing recurrence editor widget to work under Ext 4, the only component from Extensible 1.0.x that had not yet been touched in the upgrade to Ext 4. That effort has been progressing nicely and I should have the new and improved widget done within the next few days.
I still have work to do on the event editing side to support recurrence fully, and I’ve been working on a separate blog post series that will soon lay out Extensible’s recurrence support in full detail. No ETA yet, but finishing recurrence and making it available is the highest priority feature right now.
I have lots of feature ideas on the whiteboard right now, but nothing much set in stone yet for releases beyond 1.6. The current most popular request after recurrence is Outlook-style split day view support, which is planned. A mobile / Sencha Touch version of the calendar has been a common request lately, what do you think? What other ideas do you have for next features?
Just a quick note that Extensible will be taking a few days off starting tomorrow, Thursday, December 22 through Monday, December 26 to spend some quality time with family and enjoy the holidays. The forums of course are always open, but please be aware that there will likely be a delay in answering questions or responding to support inquiries over the next few days.
I hope everyone has a safe and relaxing holiday weekend, and I’ll see you next week!
At long last, the beta is over and the final release is here. Extensible 1.5 provides full compatibility with Ext JS 4, and includes a ton of fixes since the original beta was released.
A few notable issues that were fixed in this release:
There are many other fixes as well – for the complete list check out the release notes. If you are still using the beta, please upgrade as soon as possible!
Here are the upcoming next steps we have planned:
Now that we’re caught back up with the latest Sencha release we can again start adding new features and continuing to make Calendar Pro the best JavaScript calendar available. We have no shortage of ideas for 1.7 and beyond, but we also love to hear from our community regarding what’s most important, so please tell us.
Now that Ext 4 is officially out (already at 4.0.2 as of this writing) I’ve been working for the past several weeks on updating Extensible to support it. The bad news is that since Ext 4 is nowhere close to backwards-compatible, Extensible must now be branched into two separate, actively-maintained code bases to support both Ext 3.x and 4.x. The good news is that this is finally (mostly) done.
The Ext 4 compatible version of Extensible is 1.5.x, and this is now the master branch in Github. I briefly considered releasing this version as 2.0, but decided not to primarily for two reasons:
Extensible 2.0 will be a major new feature release, and may also be a paid upgrade when it comes out (it’s not even started at this time). Because of that I felt it appropriate to keep the entire current Extensible line, both for Ext 3 and Ext 4, at the same major version number.
The first beta build of 1.5.0 is now available, or you can fork the master branch and build it yourself from source. There are a couple of known issues, so you might want to check the release notes as well. Please provide feedback and bug reports in the forums.
For existing Ext 3.x users who plan to stick with 3.x for a while, the Extensible 1.x branch will also be actively maintained, and regular maintenance releases will still be made. The official 1.0.1 bug fix release is available now (see the release notes for what’s changed). It is a fully-compatible upgrade from 1.0.0 and is recommended for all Ext 3.x users.
Some new features will still be made in both branches (including recurrence support, which was already planned for 1.1 before Ext 4 even came out). Moving forward, most new features will start going only into the Extensible 1.5.x branch and/or 2.0 once it gets started. Extensible 1.x will be fully supported for at least as long as Ext 3.x is supported by Sencha (which will be a while yet), but just as with Ext JS itself, major new features will typically appear only in the newest versions.
It’s been a while since my last update and I thought a few people might be interested in what’s going on with Extensible lately. Originally I had planned to put out a 1.1 version by now. After Extensible 1.0 I ended up focusing quite a lot of time writing the Ext JS 3→4 migration pack for Sencha for the past couple of months. Last week I was in Croatia presenting several sessions at the Sourc{ conference.
Now that Ext 4 is out and the conference is over, I’m refocusing on Extensible and plan to get 1.1 out as soon as possible. I’ve already started adding recurrence support and hope to have something committed for testing very soon.
I have also started updating the calendar for Ext 4 support, which will reside in a separate branch so that Ext 3 will still be fully supported as well. This will not be part of the 1.1 release plan, but should also be released pretty soon thereafter.
Finally, I will have more exciting Extensible product news in the coming weeks, but I don’t want to spoil the surprise just yet…