Tag Archives: Adobe

brackets… another extension… annotation

To get into extending and adding functionality for Brackets is impressively easy…

David Deraedt has undertaken the feat of implementing an Annotation Extension which will provide developers with shortcuts to adding comments to their Brackets files…

Here is how it looks when I run it on my machine…

Obviously, the comment inserted is very simple, however remember this is very very early work and if you take a look at the code for generating this, you will appreciate the simplicity of the Brackets Extensibility Model and see that the entire extension is a mere 133 lines of JavaScript code at this point (including comments).

Check out the extension here…

…or have a look at other extension initiatives here…

…and please don’t forget, if you dont see what you like or need, its simple to just do it yourself using HTML, CSS and JavaScript combined with the elegant Extensibility API’s of Brackets.

Tagged , ,

BRACKETS… Your First Extension

…at the core of Brackets, you find an unparalleled open ness and tremendously awesome technology stack !

On top of the awesomeness of the technology stack and in the middle of some tremendously cool features build into Brackets by the team, you find a very simple extensibility model which allows anyone with knowledge of the basic Web Technologies, to write their own custom extensions in Brackets itself and using the same technologies we are using for the system we are making with Brackets…

Basically, every developers wet dream come true…

To get you started, the team behind Brackets has made a Quick-Start tutorial for getting started writing you own extension… it’s naturally a Hello World extension.

It will take you less than 5 mins to go through every step in the tutorial (including downloading the only 34 MB Brackets binary) and tweaking Mr. Hello World to say your name and make another or two small tweaks…

You can find the tutorial here…

The source code for the tutorial are made available, and can be found here…

Now, obviously popping up an Alert in response to a MenuClick is poor UI, so don’t make that mistake; but instead take a look at the Extension UI Guidelines:

If you’re working on anything big, its recommended you post to the brackets-dev Google group or the #brackets IRC channel on freenode early on so you can get feedback (there may be others working on similar ideas!).

For more detail on Brackets internals, see Brackets Development How Tos.
If you’re interested in contributing to the core Brackets codebase, see How to Hack on Brackets.

Tagged , , ,

Using semantic HTML, why you should…

Terry Ryan posted a nice article serving as an introduction to semantic HTML…

Check it out….

Tagged ,

The Brackets Team… using Trello

In my optics (and obviously when wearing my coders goggles) Brackets is the most exciting news to come out of San Jose this year… not only is the team targeting to build an entirely new code IDE for web projects, but they have decided to do it in a new way… a way that may prove both to be more challenging as a traditional product development approach as well as more rewarding as members of the community starts joining the development effort by adding both core features as well as extensions (an extension API is on its way) even from the very beginning of its lifetime…

Anyways, what I wanted to share was that the Brackets team is using Trello as their SCRUM board.. being a happy Trello user myself, this is off course both interesting and exciting…


The Brackets Team obviously practices Scrum. They have decided to work iteratively and produce stable builds every 2.5 weeks (12 coding days to be exact). A rather unusual number, however it works for the Adobe Brackets team… Development started in January 2012 so it’s still in the very early stages of the project.

The project goes under the parole: Code Free ! So I suggest you do exactly that, join the project, contribute a feature or two, learn a lot and then take this approach and apply to your development efforts in your own circles, being commercial or not, the approach is clever and when executed correctly, can empower to teams and the extended teams like no other approach…

Tagged , ,

Introducing Adobe Brackets… a new HTML/CSS/JavaScript Code IDE

Brackets… a new HTML/CSS/JavaScript Code IDE

…by putting this into the eco-system, Adobe has just shaken the bag once again… sparking off their ideas and possibilities on ways to optimize the development stack for Web Applications and Experiences… this is most recent newcomer…


Among the most interesting aspects to this new IDE project is that…

  1. It’s Adobe Systems Inc.
  2. It’s 100% Open Source
  3. It’s being developed in entirely the open, a new approach by Adobe and means everyone is invited to join the team (and release party)
  4. Its written entirely in HTML, CSS and JavaScript itself…

Brackets seek to differentiate itself from other IDE’s by being envisioned with the following key parameters…

  • Tools shouldn’t get in your way. Instead of cluttering up your coding environment with lots of panels and icons, the Quick Edit UI in Brackets puts context-specific code and tools inline.
  • Brackets is in sync with your browser. With Live Development, Brackets works directly with your browser to push code edits instantly, set breakpoints, and jump back and forth between your real source code and the browser view.
  • Do it yourself. Because Brackets is open source, and built with HTML, CSS and JavaScript.

You can already now download a very early binary and start playing with it, or you can download the source code and compile for yourself.

It’s important to note that…

Brackets isn’t ready for general use yet. It’s still very early in development, is missing a lot of basic editor features, and probably has bugs. That said, we’ve actually been using Brackets to develop Brackets for awhile now, so what’s there is reasonably stable.

Although Brackets is built in HTML/CSS/JS, it currently runs as a desktop application in a thin native shell, so that it can access your local files. (If you just try to open the index.html file in a browser, it won’t work yet.) The native shell for Brackets lives in a separate repo, adobe/brackets-app, which includes this repo as a submodule.

The project is hosted at GitHub and offers you to both download binaries for MAC and Windows as well as the entire source code…

Check it out…

Brackets will be one of the first to take the place in the Code section among Tools and Services on Adobe’s page dedicate for HTML development… so that would be the place to check for public announcements along with Adobe Labs…

Tagged , , ,

Introducing Adobe & HTML

With so many exciting things happening at all levels of the web “stack”, Adobe wanted to create a single place where everything they are working on can be shared with the community to improve what is possible on the web and simplify how wen professionals work with HTML, CSS, SVG and JavaScript. It is here that you can find up-to-date information about all of the different HTML projects Adobe is working on, discover which events that will be worth attending, and find out how you can join Adobe in making the web better.

You can read the introductory statement…

…or you can head directly over to the new site… more resources will be added in the near future making this a very promising portal to learn about Adobe’s HTML initiatives…

One I personally find particularly interesting is the statement under Tools & Services…

We think there’s a need for a different type of code editor – we’re working on something and will have more to share soon.

UPDATE on May 3rd 2012: Check out this announcement on the emergence of “Adobe Brackets”

However, check it out… its all good stuff and could potentially make your life as a web professional easier and more fun…


Newest Headlines from the Adobe Developer Connection Newsstand…

The following rather insomnious introduction to my post is relevant considering the current development in the industry, because from where I am sitting, we can either ignore the significance of the events, we can consider the recent changes a rogue wave after which everything will stabilize and become it old self again or we can start considering if its the turning of a era in the software industry…

Rogue waves – also known as freak waves, monster waves, killer waves, and extreme waves. These are relatively large and spontaneous ocean surface waves that occur in deep water, usually far out at sea, and are a threat even to large ships and ocean liners.

Anecdotal evidence from mariners’ testimonies and damages inflicted on ships have long suggested rogue waves occurred; however, their scientific measurement was only positively confirmed following measurements of the “Draupner wave”, a rogue wave at the Draupner platform, in the North Sea on January 1, 1995. During this event, minor damage was inflicted on the platform, confirming that the reading was valid.
In modern oceanography, rogue waves are defined not as the biggest possible waves at sea; but instead as extreme sized waves for a given sea state.

– WIKIPEDIA, Dec. 8. 2011

Now this brings me to the recent announcements from Adobe on their latest postings on the Adobe Developer Connection… check it out…


Getting started with PhoneGap

PhoneGap: Developing for iOS

PhoneGap: Developing for Android

Introducing Adobe Flex 4.6 SDK

What’s new in Flash Builder 4.6

Flex mobile performance checklist

Web and mobile reference applications with Flex 4.5 SDK and Flash Builder 4.5 (updated)

Adobe AIR with captive runtime support for desktop

Adobe AIR with captive runtime support for mobile

Dynamically adapt the layout of tablet and mobile apps

Adapt UIs for multiple mobile platforms

Hello World: Build a mobile app in five minutes (updated)

My top 10 ADEP publishing features by Anirudh Verma


Thanks to Adobe PowerWoman Rachel Luxemburg for the heads up on these great resources for developers using Adobe Technologies…



A Saturday Night Status in the World of Flex

Upon a week of drama across the world of Flex, the past week proved to be business as usual… and thank heavens for that.

In case you have missed it, the Flex team at Adobe has amended their original statement regarding the future of Flex in the context of Adobe.

We are preparing two proposals for incubating Flex SDK and BlazeDS at the Apache Software Foundation.
In addition to contributing the core Flex SDK (including automation and advanced data visualization components), Adobe also plans to donate the following:

  • Complete, but yet-to-be-released, Spark components, including ViewStack, Accordion, DateField, DateChooser and an enhanced DataGrid.
  • BlazeDS, the server-based Java remoting and web messaging technology that enables developers to easily connect to back-end distributed data and push data in real-time to Flex applications.
  • Falcon, the next-generation MXML and ActionScript compiler that is currently under development (this will be contributed when complete in 2012)
  • Falcon JS, an experimental cross-compiler from MXML and ActionScript to HTML and JavaScript.
  • Flex testing tools, as used previously by Adobe, so as to ensure successful continued development of Flex with high quality

Adobe will also have a team of Flex SDK engineers contributing to those new Apache projects as their full-time responsibility. Adobe has in-development work already started, including additional Spark-based components.

You can read the entire post here:

Eventually, its a much more positive and inspirational variant of the post after the update compared to the original one, so thanks to Andrew and Deepa for taking the time to make the effort to apply the amendment.

In retrospect, I found the entire experience of having the bag shaken in which we have placed our faith to be motivational and a reminder to update my skillset. This last point is something we can all take away from this experience.

Upon talking with dozens of Flex developers over the past weeks, it became clear that some of us had forgotten to stay updated and expand our toolset, and regardless of what happens to Flex, this is an important reminder. A professional is only as good as his tools allow him to be and the quality of the output depends on both the skill of the professional as well as their ability to choose the right tool for the job.

We should use Flex when it makes sense and remember to stay tuned to what is going on in other areas or our industry for the moment when Flex may not be the optimal tool for the job.

Another reminder I have taken away from this experience is my old commitment to continuously contribute to at least one Open Source project at any given time… obviously I will be contributing to Flex once it hits the repositories… why don’t you join me ?

Tagged , ,

OpenSource AVM… Tamarind

Project Tamarind, once so promising and bespoken project… was co-owned by Adobe Systems and Mozilla Foundation, and has been discontinued for more than 3 years now…

However, the sad state of this cool OpenSource project is that it hasn’t been touched since March 2008…

The members from Adobe are mostly names I have never heard of so I sincerely wonder what have become of them (perhaps they are still engineering in the dungeons of San Jose), anyways check the names out for yourself…

If anyone knows the obituary belonging to Project Tamarind, please do share… it seems to have been a massive Adobe effort that apparently ended up in a fruitless archive of The Mozilla Foundation.

Anyways, you can check out the archived project home page here…

Tagged , ,

Brave new wwworld… day -1

Today is the last day of the old Flex and Flash era… its been a tremendously dramatic week due to the many far reaching announcements from Adobe.

It’s expected every year at the turn of the fiscal year, that announcements of lay offs are due and that organizational restructuring is due… however, this year was remarkable rough as Adobe really has been taking the organizational restructuring at heart and done it across the organization not leaving a single division untouched…

Tomorrow starts the new post-flash era where its back to the drawing board for many of us in terms of re-establishing the mature development track we were in with Flex, now based on web standards stack technologies…

We need the following in order to accomplish that to for the first couple of apps…

  1. IDE
  2. Micro Architecture Framework
  3. UI component set
  4. Data Service Tier
  5. Video and Audio Libraries
  6. Touch Libraries

…just to mention a few…

Its not going to be easy, however there is certainly something reinvigorating about this devastating situation… it may be a bit gloomy right now, but a lot of opportunities rest in the shadows…

We got on the Flex ship and enjoyed the ride, we learned a heck of a lot on the trip, now its time to re-saddle and make the best of the new brave flash- and flex-free wwworld…


Get every new post delivered to your Inbox.

Join 523 other followers