Skip to main content
Commonmark migration
Source Link

Design Conversation:

##Design Conversation: in reverse chronological order.

###part the Third: in which code poet waxes v1.

part the Third: in which code poet waxes v1.

###part the Second: in which code poet introduces vNext.

part the Second: in which code poet introduces vNext.

###part The First: in which code poet mixes good idea with short sightedness

part The First: in which code poet mixes good idea with short sightedness

###Our very own Growl Display

Our very own Growl Display

##Design Conversation: in reverse chronological order.

###part the Third: in which code poet waxes v1.

###part the Second: in which code poet introduces vNext.

###part The First: in which code poet mixes good idea with short sightedness

###Our very own Growl Display

Design Conversation:

in reverse chronological order.

part the Third: in which code poet waxes v1.

part the Second: in which code poet introduces vNext.

part The First: in which code poet mixes good idea with short sightedness

Our very own Growl Display

added 1261 characters in body
Source Link
Sky Sanders
  • 12.1k
  • 3
  • 32
  • 60

###part the Third: in which code poet waxes v1.

After the unexpected divine intervention of Brian, the developer of Growl for Windows, I was able to refactor the evolving custom pin-able update-able displays into much slimmer and much less complex code. The updates are now batched by the server, soapi-notify, and pushed to the notifications that are still registered for updates.

Thanks Brian.

For those that are not quite satisfied with the default displays provided with soapi-notify, the source for the default display is a great place to start writing your own. Be sure to share it here.

There are a few more things that I would like to incorporate into V1 before calling it soup.

  • the ability to monitor existing questions. keep an eye on questions as they evolve.
  • extended filtering support. either/or tags using the api methods is a bit limiting. I will use client side filtering to provide a more compelling filter experience.
  • proxy support - need to set up a proxy to test this.

These will be incorporated gradually over the next month or so. I need to finish some other projects and get a job. Anyone who wants to help out may submit patches and perhaps be added to the team.

Let me know what you think


###part the Second: in which code poet introduces vNext.

###part the Second: in which code poet introduces vNext.

###part the Third: in which code poet waxes v1.

After the unexpected divine intervention of Brian, the developer of Growl for Windows, I was able to refactor the evolving custom pin-able update-able displays into much slimmer and much less complex code. The updates are now batched by the server, soapi-notify, and pushed to the notifications that are still registered for updates.

Thanks Brian.

For those that are not quite satisfied with the default displays provided with soapi-notify, the source for the default display is a great place to start writing your own. Be sure to share it here.

There are a few more things that I would like to incorporate into V1 before calling it soup.

  • the ability to monitor existing questions. keep an eye on questions as they evolve.
  • extended filtering support. either/or tags using the api methods is a bit limiting. I will use client side filtering to provide a more compelling filter experience.
  • proxy support - need to set up a proxy to test this.

These will be incorporated gradually over the next month or so. I need to finish some other projects and get a job. Anyone who wants to help out may submit patches and perhaps be added to the team.

Let me know what you think


###part the Second: in which code poet introduces vNext.

added 2161 characters in body
Source Link
Sky Sanders
  • 12.1k
  • 3
  • 32
  • 60
Loading
Source Link
Sky Sanders
  • 12.1k
  • 3
  • 32
  • 60
Loading