Jump to content

Brandon D

Members
  • Posts

    4,314
  • Joined

  • Last visited

  • Days Won

    24

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Brandon D

  1. I agree they could be positioned elsewhere. Up top with the undo button would be nice. Pretty much anywhere above the textarea as, in the current position, if you want to expand it multiple times you have to keep moving your mouse for each click.

    @Tony Having it there would clash with browsers that natively support resizing of textareas. Altho, it would be nice if IPB didn't show those buttons if the browser is known to support that function natively.


  2. @Brandon D - each app can alter the search display, yes, which is why I said it could be skinned. However, to go back to a IPB 2.3 style display we'd need to make the results tabular (in a table), and each search app can only alter the "row". Because it's wrapped as a list presently, and not a table, it's a bit more challenging to make it look exactly like it did in 2.3.



    Ah, I see. So, to get tabular data you'd have to put a table within each list element (lol), or change the wrapping list to a table and make the necessary changes in each app's "row". The latter obviously being the ideal solution, but one I wouldn't wish upon anyone having to make this change late in IPB3 ;)

  3. We had to create a more generic interface since more types of content now show up in the search. This means it's much less "forum-specific" now, which I assume is where your dislike stems from mainly.



    :blink: Each app can alter the way it's search results look in /extensions/searchDisplay.php. So couldn't search results from the forums be made to look more "forum-specific" and not affect the other apps?

    I didn't like View New Content at first but it's grown on me. I like the simplicity of it.
  4. It's a bit worrisome tbh :P

    As far as I can remember I never came across any out of memory errors on this site back when it was 2.3.6 - but ever since 3.0 was added I've seen quite a few myself and 10-15 instances reported by others, each time there was always a "reason" why it happened. May not be directly caused by IPB3 (I think IPS moved servers with the IPB3 upgrade?), but it certainly doesn't help it's image - especially to newcomers.

    [edit] And no I'm not talking about just tonight with the RC2 upgrade ;)

  5. I never actually wrote components or directly modified IPB2 but I find getting what you want done in IPB3 to be simple and pain free (and, tbh, actually quite fun/interesting). I'm porting over bfarber's Links System for IPB3 and I've already managed to get the ACP ported along with several improvements to it. I like how they made it easy to integrate your app with several of the forum's core functions like searching, item marking, editing members/groups in the ACP, etc. without editing a single file. Of course, it helps that in IPB3 pretty much everything is now an application, even the stock functionality like core, members & forums, so 3rd party app developers benefit from whatever IPS does to make integrating their own apps easier :P

  6. Yes. Please.

    The mobile skin is so annoying to use and due to a (reported) bug I can't stay in the full skin longer than a few page loads... not to mention if the mobile skin actually provided information (i.e., the original mobile skin you had) I'd love to use it more than the full skin.

  7. Topic pagination also removed from topic index as well...

    So much functionality has been removed in hopes of improving the mobile experience that it's significantly impeded it, IMO. It's just a glorified RSS feed minus the RSS part :P

  8. I know it'd still be a performance hit, hence why I said it would be in my last reply :P

    I'm just too lazy to switch tabs to see if there's new content or I'll forget to switch tabs entirely, sue me :P

  9. I wonder if you could do an AJAX request after the screen has been printed for those counts, and then fade em in once the screen has them? That way the active tab's content is available before any further queries are run. It wouldn't be quite as useful and it'd still be a performance hit overall, but it's at least something.

  10. On the view new content page, I'd rather not flip through each application tab to see if there's new content. Could you add a count of new content within each application on the tabs? So I know, for example, that blog has two new entries while reading the Forum's new content? :)

×
×
  • Create New...