Jump to content

Community

Marcher Technologies

+Clients
  • Posts

    17,657
  • Joined

  • Days Won

    98

 Content Type 

Profiles

Downloads

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Store

Entry Comments posted by Marcher Technologies

  1. Maybe just me, but I have a really difficult time discounting developers' and IT managers' reviews of this service. I would tend to recommend holding braintree at arms distance, and certainly not as the sole payment gateway on any site. It's not a matter of PEBKAC for all, reading through those reviews. They have pulled some quite apparently less than ethical moves since being acquired by Paypal.

  2. On 9/30/2017 at 6:40 AM, steve00 said:

    You look around you (walking, on bus, plane, train ... in fact anywhere) and tell me what they cannot live without and it will be their phone whether it is for music, gaming, talking to friends etc .... they could not live without it for a week ... they would be pulling their hair out.

    No matter where you look ... someone is using their phone

    Would really love mobile operators to close their transmitters for a few days all at same time and see how they get on

    Not everyone falls into that pit. A phone is literally a phone to me, even a smartphone sees no apps installed, is small, and is not allowed to notify me of anything short of an actual call(which are not common, I'm not free with my number). When I leave the house, I unplug, I don't need the annoyance of it all, I can get it at home quite enough. I didn't even have anything but a landline until 6 months ago. Just pointing out many can indeed live without it and refuse to be attached to it.

    (To answer the question, clearly I'd be quite screwed without internet at home. ;) )

  3.  

    I don't fully understand that part.

    Can I set up a new site on 4.0 as a master and still use my old site on 3.4.x  as a slave? Or do all sites need to run 4.0?

    Think of it in terms of say the twitter API. This would truly be considered v2 of the ipsconnect 'specification', as such it's not going to be compatible with the first iteration, nor should it be due to the limitations adhering to that would impose.

    At least, that's my understanding.

  4. Can third-party applications add theme settings that would exist in every theme to control display options for our default templates?

    I would very much enjoy moving global settings that really are design decisions into theme settings in my own applications if possible.

  5. Looking good but I have a question: is there any way to display more than a title and the buttons for the row? For example I'd like to add a column with a on/off image to enable/disable the field without clicking edit and changing the value from the form. A shortcut basically, but it could be anything else.

    Similar to this,  let's suppose we have a tree of content pages....  it would be nice that the developer could add columns of data to be displayed like tables have the option to(in example case, last edit and size in kb, but could again be anything).

  6.  

    You can control the presentation of your settings pages using normal controllers (probably in conjunction with the form helper class).

    Hook settings? Where do we display configurations for hooks? Manually? Where are these displayed and how if no central settings panel exists?

    If I get this right, we have more control for apps but require more code for hooks? Not to mention without any standard for getting to settings globally, you know as well as I do configuration for the user becomes a nightmare as developers litter the landscape with their own settings display for x mod at x url. This is seriously NOT going to be easy on the user, you went from some fair consistency to completely free-form url and display-wise. Every app/hook is going to now have a learning curve for finding 'settings'?

    You went from an effortless thing to do settings to mancode to display them? Not being accusatory, just not understanding why you add more boilerplate here in something currently so dead simple to implement. I really don't want to end up with it being like WordPress, where you have to code the settings display before you can even use them. It adds much bulk to the code-base. Where hooks are concerned, this single item, needing a setting, is a kiss of death for it staying a hook with it like this.

    The way you present it, why should I as the developer even bother with 'settings'? Why not use rows from my own table/cache? Functionally, it is now the same amount of code?

    Worse, it takes MORE code for an app to display it's 'settings' page? This was a 6-liner. Again, why would the dev even bother with 'settings' at all if we have to manually display and save them?

  7. The "Type" field controls the code that will be placed in the file created for the section - the options are:

    • "Blank" - which will create the class with no other logic, so the section will be blank.
    • "Table" which will create a class with a boilerplate for displaying a table.
    • "Node Controller" - which will create a boilerplate for displaying a tree of containers such as IP.Board forums, IP.Downloads categories, IP.Nexus groups, etc. We've not posted how this class works, but a future blog entry will give more details.

    No matter which type you select, the system will automatically generate a file, with a basic class structure already filled in, including ACP restrictions checks, etc.

     

    Will these 'types' be extensible like the extensions(as in could I as the developer add a base 'template' for a section file to reduce rehashing it time and again)?

  8.  

     

    IPS4 no longer has AJAX modules.

     

    Since everything in 4.0 has a fallback if JavaScript is disabled, a lot of the AJAX and non-AJAX calls both go to the same controller with a call to IPSRequest::i()->isAjax() to differentiate the output to show. For things which are distinctively AJAX (like quick search in tables) we're just putting those actions in the normal controllers or creating AJAX controllers within a normal module.

    What about the only point OF ajax modules?

    I do not want the user 'active' somewhere they are not just because these were removed?

  9. If not, just ask him to make a converter tool that you can buy. :whistle:

    Shame on you. :tongue:

     

     
    Would be nice if Google+ synched the same way.

     

    Hopefully we will also be able to convert over users from Marcher's excellent mod.

    I think everyone misses that it is email-based :tongue:

    There is nothing one could do to require a conversion script trying to.

  10. Hey. There's one more thing regarding the new login handlers that I'd like to know.

     

    Will I be able to write my own handler as a replacement of the default one, so that my users wouldn't be required to provide their email addresses upon registration? 

    They need not provide it(see google registration, the service may provide it for them instead), but we still need it, and so do they, for functional purposes.

    That said, even now in 3.x you can write a custom login handler and not use(disable) the internal.

  11. in case there is any importance for the columns to appear in a certain order.

    If one's application code explicitly depends on a specific order of database columns in a table, one is definitively doing it dead wrong.

    Very, very nice Mark... I spy admin/front modules centralized there and version management outside the hard xml. :D

    Curious as ungodly about 'extensions' now.:P

  12. complex forms do not stand a chance of creation with such a tool, a dynamic form, or even a multi-step form, would immediately outgrow the bounds of such a tool.

    and seriously, HOW is that programming? You just showed me a video of a dude pressing auto-add buttons in a Content-like manner.

    Regardless, such could not be a part of the core of a web application, and is an over-glorified form WYSIWYG.

    WYSIWYG editors only open up accessibility for the laymen, but bind the hands of the more advanced developers.

    Such a tool could be created easily, but should not be forced down the dev's throat or bloating the core framework.

  13. This should have a builder tool to do all this.. something like the forms builder in Visual Studio.  

     

    Create a "blank" form and drag controls onto the form.  The programmer edits the control attributes in a properties window and the tool generates all the code for you.   The form gets stored as XML so it can be later edited.

    >.>... uhh.... No, just no? That's not programming by any means, and to call the user using such a tool a programmer is a stretch generally.

    Very nice Mark. :D I especially appreciate the validation callback... going to use that a LOT I can tell ;)

  14. complex where clauses.... how does that work syntax-wise?

    IPSDb::i()->buildAndFetch( array( 'select' => '*', 'from' => 'table', 'where' => array( 'foo=? AND bar=?', (string) $foo, (int) $bar ) ) );
    

    Or:

    IPSDb::i()->buildAndFetch( array( 'select' => '*', 'from' => 'table', 'where' => array( 'foo=? AND bar=?', array( (string) $foo, (int) $bar ) ) ) );
    

    ?

  15. IPS is the actual namespace name.

     

    If you were working with more than one installation, you'd just use different DB connections - after all, their source files will be the same.

    IPSDb::i( 1 )->...
    IPSDb::i( 2 )->...
    

    avoiding direct database calls where the framework handles it is what I am talking about....

    IPSMember::load( 1 )->isInGroup( 4 );
    

    is(?) going to differ if each one is using the default database connection.... no? Confused.

  16. I assume IPS is an alias... taking the instance of working with 2 or more IP.Suites, is that alias going to be of conflict, or is it possible to run more than one suite in the code via use ... as statements?

    use IPS as IPSOne;
    use forumsIPS as IPSTwo;
    
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy