Tagged: Status Update Toggle Comment Threads | Keyboard Shortcuts

  • Dan Larkin 2:00 am on July 29, 2009 Permalink
    Tags: , Status Update   

    Paged comments are proving to be much mo… 

    Paged comments are proving to be much more difficult than they would seem, due to the original code’s convolution. Still trying to figure out how to adapt it to use MPTT without breaking compatibility (at least too much), and if any of the possible solutions offer enough performance gain to be worth it.

     
  • Daryl Koopersmith 10:03 pm on July 24, 2009 Permalink
    Tags: , Status Update   

    Hey everyone, This week has seen some m… 

    Hey everyone,

    This week has seen some major progress: I’ve considerably extended the framework’s capabilities, and have completely overhauled the editor’s backend. Customized files are now formatted to be easily readable, and the backend has been separated into three main components: the plugin page, theme customization, and theme install/upgrade. The editor’s theme installer/upgrader is working properly, so installing both the editor and the framework is now unnecessary.

    For the coming week, I’m going to focus on improving the editor’s UI / workflow, including integrating the save/load frontend. In addition, I’ll continue to expand the framework—I’ll be working on page defaults and adding missing features, such as context-sensitive headers and dynamic classes.

    Fun stuff. Hope everyone’s projects are going well.

     
  • Justin Shreve 4:50 pm on July 22, 2009 Permalink
    Tags: , Status Update   

    Hello, Right now I am working on some o… 

    Hello,

    Right now I am working on some of the documentation aspects of the project. I am working on the README right now to include the installation directions, description, uninstall etc. I am then going to try to write some developer documentation for adding new plugins.

    In addition, once the README is written I am going to have Andy post about my plugin to try to get some testing going on.

     
  • Dan Larkin 7:19 am on July 22, 2009 Permalink
    Tags: , Status Update   

    Sorry for the late update. This week wa… 

    Sorry for the late update. This week wasn’t all that productive in terms of writing code. I wrote some of the code for adapting MPTT for comments (or rather the other way around), but ran into a snag for paged comments. Since they’re handled differently than categories and pages, and especially since the WP code handling them is much messier, things get a bit tricky. Most of the week has been spent in planning (and checking with Ryan to see if my plans will break stuff that they shouldn’t).

     
  • mike 3:59 pm on July 20, 2009 Permalink
    Tags: , Status Update   

    Hello, Firstly thanks to my mentor, the… 

    Hello,

    Firstly thanks to my mentor, the administrator of WordPress.
    Secondly, about Buildpress,

    I have just embedded the Custom Header Option in Builder UI. It isn`t any Custom Header script, but a custom one, integrated to the Builder itself, showing a live preview of your crop 🙂

    Lil tweaks left, also we will be cleaning up code to WP standards.

    Lets hope we can release an alpha version of the complete system in the coming week 🙂

    Cheers Guys

     
  • Daryl Koopersmith 1:09 pm on July 18, 2009 Permalink
    Tags: , Status Update   

    Hey everyone, This week I began to rewo… 

    Hey everyone,

    This week I began to rework the UI, and added support for named blocks. Beau and I mapped out the features/improvements I’ll add to the editor by the end of the SoC, and spoke at length about different approaches for creating the core of the framework. For the coming week, I’ll be focusing primarily on properly implementing save/load, and building out the framework core.

    Happy coding!

     
  • Justin Shreve 4:01 pm on July 16, 2009 Permalink
    Tags: , Status Update   

    Here is my late update (late night last … 

    Here is my late update (late night last night)… I just got through with freshman orientation, registering for classes, etc. Yay computer science major!

    No updates really (sorry). The plugin was looked over by Andy and approved for mass distribution. So.. I just need to get it submitted to the plugins directory now and wait for some bug reports :).

     
  • Dan Larkin 9:33 pm on July 14, 2009 Permalink
    Tags: , Status Update   

    Well, a week later and I’ve got a new pa… 

    Well, a week later and I’ve got a new patch. This one includes both some fixes and updates to my previous work on categories as well as a (hopefully) fully-functioning page implementation. This one works from SVN rev. 11716. Once again, it has only undergone testing on my development system and on a near-default WordPress installation, so don’t trust any important data to it. Please to try it out on a test WordPress installation and let me know if anything is broken.

    I hope to get comments finished up within the next week or so as well. From there on out it should just be testing, performance tweaking, and potentially bug-squashing.

     
    • diegocaro 11:21 pm on July 25, 2009 Permalink

      Great work Dan!, For now, i’m reviewing how to maximize acceleration and fixing some bugs at insert nodes (by name). Can I take the code for get_lft (it is in your patch)?.

      Bye bye.

  • Daryl Koopersmith 5:01 am on July 11, 2009 Permalink
    Tags: , Status Update   

    A Prototype 

    Hey everyone,

    The past week has seen a huge amount of progress—there is now a working prototype. Beau and I have settled on the name Elastic, and things are moving forward at a steady pace.

    Elastic is separated into two major components: the editor, and the framework. If you decide to download the prototype, the rest of this post should help you see the context behind what you’re using.

    The Editor:

    The editor is currently the more mature of the two pieces. At this point, its purpose is to allow you to rapidly lay out the structure of your theme.

    Key: (implemented/not implemented).

    • Grid-based: The editor currently runs on a customized grid system based off of the Blueprint CSS framework. Grids are fixed-width only, but I plan on allowing fluid and potentially grid-less layouts in the future.
    • Types of Elements: Choose which elements will be your sidebar, content, etc. Currently, types are indicated by background color: header (dark blue), sidebar (gray), content (light blue), footer (dark gray). Eventually, headers and footers will be limited to one per page.
    • Not-quite WYSIWYG: The editor is not-quite WYSIWYG. Since content in WordPress can have an arbitrary height, the layout you draw is optimized to stretch vertically. Elements are grouped into columns wherever possible to prevent an extra-tall element from disrupting your layout. The one downside to this is that sometimes you want to group elements that are next to each other. At this point, there is no way to manually group elements. However, Beau and I have recently decided to tweak the grouping algorithm, so this should become much less of an issue in future releases.
    • Saving/loading themes: Currently, the editor will only modify and load themes in the “/themes/elastic/” directory. Users will eventually be able to save new themes and load any Elastic-editor based theme.
    • Named sidebars: At this point, the editor does not support user-named sidebars, and will name your sidebars for you. This is somewhat frustrating, but will be improved in the near future.
    • Whitespace between elements: Currently, the editor does not render whitespace between elements properly. In the future, users will be able to place elements in the layout with gaps between them and have those gaps preserved in the final layout.
    • The UI: It’s a work in progress. I’ll soon be removing all of the jQuery UI dialog boxes in favor of a more flexible system that requires fewer clicks. Element types and names will become much clearer. The core functions—dragging, resizing, and adding elements—will likely remain the same. However, I do plan on letting the user resize an element on the same click that it is added to the canvas.

    The Framework:

    The framework is still taking its baby steps. It is currently very basic, and only renders index.php. It’s heavily inspired by Thematic, Sandbox, and Carrington, but will hopefully be its own animal. The framework is being designed to be used with or without the editor—it will hopefully be useful as a standalone product.

    • Object Oriented: Since the editor requires a framework that can create elements in any configuration, I’m taking an object oriented approach to building the framework. The object based layout is defined in layout.php, which is currently not very reader friendly. Don’t get too comfy with the OO classes though—I’m in the process of rewriting the classes to provide tighter integration with javascript and more legible generated files.
    • structure.css: This is output from the editor that defines the structure of the layout.
    • style.css: This is predominantly styles from Thematic (for the time being). When the time comes, everything will be properly enqueued and a bit cleaner.

    If you have any questions or suggestions, let me know. Happy coding!

    —Daryl

     
    • DD32 10:25 am on July 11, 2009 Permalink

      I think you’ve forgotten to update the plugin.. “Description: A theme editor for the Elastic framework. Please note that the Elastic framework MUST BE INSTALLED in themes/elastic-editor/ for the plugin to work properly.” – dont you mean them

      Other than getting the editor included in the theme directory.. Sounds great and i’m going to go run off and play with it.

      What browsers are you currently testing it under? (And which is the primary dev. browser?)

      • DD32 10:26 am on July 11, 2009 Permalink

        Eugh, Ok that comment got mashed a bit. “Dont you mean it needs to be in /themes/elastic/ :)”

        • Daryl Koopersmith 7:14 pm on July 11, 2009 Permalink

          You’re right—the framework should be in themes/elastic/ and the editor should be in plugins/elastic_editor/.

          Once I have loading/saving up and running, you won’t be forced to include the theme, so that’ll clear up.

          For now I’ve been primarily developing in FF and also testing in safari. The framework will use a css reset and is based on blueprint’s grid system so it should hypothetically be cross-browser, but I’ll run it through the browser gauntlet at some point anyway.

  • Justin Shreve 3:16 am on July 9, 2009 Permalink
    Tags: , Status Update   

    Hello I was on a vacation from Monday t… 

    Hello

    I was on a vacation from Monday till today. Before that though Andy tested out the plugin(s) for me and reported issues to fix and suggestions.

    I went through and secured some of my code, changed how the plugins were loaded so they would work correctly, and added some alerts (if the plugin needs additional configuration or if you need to enable a search plugin for the api to use still). Minor fixes but the plugin(s) did get improved.

    I updated the source on http://wpsearch.serenelabs.com/ which can be downloaded here:

    http://code.google.com/p/wpsearchapi/downloads/list

    I believe we are releasing it on wp-plugins soon too.

    Also, I filled out the survey so I should be set for the mid-term :).

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel