 | Out of Date Content on this page is out of date and has been replaced by Future Ideas |
Refactor Projects
Weather Widget
The Weather Widget takes a zipcode and returns weather related data (e.g., temp, city, state, current conditions, humidity). There are two main problems with the weather widget which need correction via a refactor:
- The weather widget uses a yahoo api to request weather data and then parses the returned xml source for the data attributes it wants. The problem is that when yahoo changes their schema (as they have at least once) our weather widget may break (as it has already). We need to change the weather widget to fetch yahoo's schema and to use it to query for what we want in returned source.
- The weather widget does not allow for a direct input trigger (i.e. it has no trigger that says send this specific cargo (temp, for example) whenever you receive a zip code cargo and, as a result, the author must grab the zipcode data from wherever it is in the fluency application (probably a text field) and build a pipe from it to the weather widget each and every time he/she wants to fetch a new piece of weather data from the weather widget. The point is that once zip code data has been "shipped" to the weaterh widget once, it shouldn't have to "re-shipped" to it each time a different piece of data is requested from an output trigger.
watch a demo explaining item 2 above
Improve the way Fluency provides pipe and widget details in the editor
When you hover over a widget or a pipe in selection mode (in the editor), a blue box appears that gives very basic information about the item hovered over.
This refactor should occur in 2 phases:
- Add a "Get Details" context sensitive menu item to the right click menu that will display the blue box when a widget or pipe is right clicked (remove the on hover trigger that displays this information)
- Change the format of the information displayed to be more useful and elegant. It is not very "pretty" (but is somewhat functional) at present.
watch a demo explaining this project
Fix the View menu in the Fluency Editor
Presently the "View" menu has items/preferences that can be "toggled" on or off. Example menu items include: Display Grid, Prompt for Paths, DefaultPluginName, ListboxLinkage, Property Editor
The only items that consistenly work as expected are the first two (Display Grid, Prompt for Paths) because they were added explicitly as menu items in FluencyEditorFrame.initializeViewMenu(). The other items are being loaded automatically because they are plugins. The one entilted DefaultPluginName is most likely a mistake and should not be added OR it is not a mistake and it has not been given a proper name.
The refactor project involves understanding why the plugin menu items are not properly toggling the views of the plugins as expected and to clean up the code related to how this is handled.