Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Responsive osCommerce - Bootstrap


Recommended Posts

  • Replies 2.2k
  • Created
  • Last Reply

Coming from the client-end having "certified" devs would be extremely useful.  You spend enough time combing through the code in modules and you learn who codes well and who doesn't, but that takes a LOT of trial and error and at least a workable knowledge of LAMP stack.

 

Certified Developers would be clearly noted in the add-ons page.

 

Certified Developers would have more details about project contracting, availability, specialties.

Two forks diverged in a git, and I— I took the fork traveled by burt, And that has made all the difference.

Link to comment
Share on other sites

Sure it is.

It already is in place.

Those are all written by Harold. It's easy to be certified when you are the one doing the certifying. :)

 

If this were to become reality, then the practice of having open addons, where anyone can upload, would have to stop. Or only the uploads uploaded by the certified programmer would be marked as certified. That would probably cause updates to slow or be stopped.

 

This idea,or something similar has been proposed before. If it could be made to work, it would be great. But the question of who will certify the addons has always been a problem. To that end, I hereby put my vote in for Gary. :P

Support Links:

For Hire: Contact me for anything you need help with for your shop: upgrading, hosting, repairs, code written, etc.

Get the latest versions of my addons

Recommended SEO Addons

Link to comment
Share on other sites

I'm pretty sure there are other Certified addons that are not Haralds - I don't know how they got certified or who did the certification.

 

It's certainly not something I'd want to take on (looking at all addons individually).

Link to comment
Share on other sites

If this were to become reality, then the practice of having open addons, where anyone can upload, would have to stop. Or only the uploads uploaded by the certified programmer would be marked as certified. That would probably cause updates to slow or be stopped.

 

Totally agree if you look at some of the 'think out of the box' addons would they ever have been created if only CERTIFIED uploaders were writing them?

Surely if they are that good then they are not going to be sitting there coding addons for free that they will never use themselves, I would say a large majority of addons only exist because the developer of the addon needed that feature for themselves and wrote it and then shared it (even though it may not be the best coded addon and as someone above said they then download it tweak/fix it and uploaded a revised version).

 

take this facility away and as @@Jack_mcs says That would probably cause updates to slow or be stopped and I would add limited (would all the various shipping company modules from all over the world been there if the Certified developers were only in one or two countries.

Link to comment
Share on other sites

You mean certified to submit addons? if so i think that might be a bad idea as why write modules for OSC if you have to become certified you may as well write for one of the others and be paid for the addon.

 

I think there are a lot of opinions on what certified developers could mean. When I think about it, I don't feel as if it should be a requirement for submitting an addon, Anyone should still be able to write and submit an addon.

 

I think of it more in terms that if you are certified, then that is something you can use to show the public that you know what you are doing with osCommerce code and they can have confidence in dealing with you on a commercial basis.

 

A lot of things could define that certification, and if you/your dev company starts to do sloppy work, there could be a revocation of your certification.

 

It would also help to have that little badge in the addons as well. Rather than have to click on @@Jack_mcs username and see a list of his downloads after I first find one of his downloads so I can click the name, I can just "sort by certified" and there are all his addons in the list.

Follow the community build:

BS3 to osCommerce Responsive from the Get Go!

Check out the new construction:

Admin Gone to Total BS!

Link to comment
Share on other sites

I think there are a lot of opinions on what certified developers could mean. When I think about it, I don't feel as if it should be a requirement for submitting an addon, Anyone should still be able to write and submit an addon.

 

I think of it more in terms that if you are certified, then that is something you can use to show the public that you know what you are doing with osCommerce code and they can have confidence in dealing with you on a commercial basis.

 

A lot of things could define that certification, and if you/your dev company starts to do sloppy work, there could be a revocation of your certification.

 

It would also help to have that little badge in the addons as well. Rather than have to click on @@Jack_mcs username and see a list of his downloads after I first find one of his downloads so I can click the name, I can just "sort by certified" and there are all his addons in the list.

This is precisely how I saw it. No change to addons as they are already done, but certain people who produce quality work get a Certified badge.

Link to comment
Share on other sites

@@ShaGGy

 

In addition, we'll have a compatibility module available for those upgrading that will wrap removed functions (eg database) and constants (eg filenames, database names) to the new framework changes. This should allow v2.3 modules to continue to work with v2.4.

 

 

As mentioned, there will be compatibility. IMO - HPDL has been too generous in insuring addons have stayed compatible from version to version.

 

Without a compatibility layer the minimal changes I foresee needing to be done to make an old addon work:

 

MySQL queries  - They need to be changed to take advantage of the PDO driver. End result - faster & more secure.

HTML functions - rather than tep_draw_*  it would change to HTML:: or OSCOM:: - End result - can easily be overwritten, extended, or replaced by including your own class.

Defines  - No more more FILENAME_WHATEVER or TABLE_BLAH_BLAH_BLAH - End result, less processing by the program.

 

Other than those things, the older addons can still follow the same installation procedures as before. However, with the newer framework, we wont have to hack the core and as a result we will probably start seeing better addons. I think that alone will attract more users, both shop owners and dev's.

 

Ive worked on tons of osC sites through the years, I was inspired to become a web dev thanks to osC and a couple members on this forum, but I tell you - I'm also tired of hacking at core to do things. I try not too - I extend and bend where I can -  The new code base - beautiful - write a class, upload it, watch things change. BAM!

 

If an end user doesn't want to use the program because it changed, they can and will find another software. But if the software doesn't change, they still can and will find another software.

 

Really, osCommerce has been great through the years, your not going to find an ecommerce software with such a broad range of server compatibility and customization ready base. Look how many forks have branched off of osC. But now what are those forks doing? Nothing really, they have reached EOL - all the 500 addons they pulled straight from the contribution section has caught up with them. Now they are all outdated and osC is the only one that has advanced its code base so as not to get outdated, yet it also seems like osC is the one that has took the most crap. Can't win for loose they say.

 

Anyway, as all can see, there is going to be compatibility, there is all the effort of the community build rolled in, and there is new modern code. Compare the new code to other open source software out there - Ive been reading it for 2 weeks straight. Its well ahead of anything right now. PHP7 - no problem, 2 years from now - PHP10  - probably good to go there as well.

Follow the community build:

BS3 to osCommerce Responsive from the Get Go!

Check out the new construction:

Admin Gone to Total BS!

Link to comment
Share on other sites

Gradual...

 

Is that not "commit by commit" over the past 2.5 years?

 

You cannot get more gradual than that.

If a user doesn't want/like a certain commit...don't incorporate into the version you are hacking at...

 

The whole point is this;

 

instead of 5 years between releases...it's now 5 days or 5 hours or even 5 minutes.

Can't handle it? Use GOLD.

Link to comment
Share on other sites

@@kymation :thumbsup:

 

Yes that is, Ive played with it and got so far, but I think its more powerful than just what that example shows - reading through the latest classes I see where it has actions and execution. I would to see how it would handle a page, like contact us for example, I want to see how it would route the output after the submit form action is initiated.

 

Kind of like was started here:

https://github.com/haraldpdl/oscommerce2/tree/24-checkout/includes/apps/info

Follow the community build:

BS3 to osCommerce Responsive from the Get Go!

Check out the new construction:

Admin Gone to Total BS!

Link to comment
Share on other sites

@@GLWalker  I haven't gotten that far into it either. I did add a tab to the admin/orders page, using the hooks provided by the Paypal App, but I just used that to inject an action handler into the top of the page. It appears that there are better ways to do that with the hooks class. Sorry I can't be more help.

 

Regards

Jim

See my profile for a list of my addons and ways to get support.

Link to comment
Share on other sites

Is it possible we can get an example page using the hooks/apps? Preferably something like the contact_us. I would like to see how the actions would be constructed in this method.

 

I see code for an execute action but can quite figure out how to trigger it.

Documentation will be provided when the release is made. Until then, check out the OSC\OM\MessageStack class used in the Admin. It sets a few watches with anonymous functions, for example when Session->StartAfter->execute is called (in OSC\OM\SessionAbstract::start()).

 

"execute" is the default function that is executed on call - it's defined in the MessageStack class due to a custom function being defined with an anonymous function.

 

Apps will be able to define their watches in their main meta json file. The same could be done with:

 

{
  "modules": {
    "Hooks": {
      "Admin/Session": {
        "StartAfter": "Module\\Hooks\\Admin\\SomeClass"
      }
    }
  }
}
When Session->StartAfter is called, it will execute OSC\Apps\VENDOR\APPNAME\Module\Hooks\Admin\SomeClass::execute(). Passing parameters along will come in the next update.

 

It's also possible to add a module file in includes/Module/Hooks however this method will more than likely be removed (or kept for the core only) so add-ons must then be developed as an App.

:heart:, osCommerce

Link to comment
Share on other sites

I would slow down on major overhaul and introduce a number of gradual changes that head towards the end goal so as users can upgrade and adapt to the changes.

Stay on v2.3.x then, it lives by that rule. v2.3.x will continue to work after v2.4.x is production ready. No one is forcing you to upgrade as soon as that release is pushed out.

 

v2.3.x will receive an end of life once v2.4.x is production ready, with a really long term for security updates. This will be announced when v2.4.x is production ready.

 

v2.4 is progress!

 

v3.0 will hit you hard in the face :P It's more javascripty because of modern user interface design principles. People with javascript disabled should surf the web on a WAP device and complain about life in some WAP optimized forum out there.

:heart:, osCommerce

Link to comment
Share on other sites

I always knew  you guys were full of BS ;) ;) ;)

Yeah, I had some discomfort with that initially, but got used to calling it "BS". It probably should have been "R" (for responsive), but that's water under the bridge.

 

99% of what we (this awesome community) have done over the past 2.5 years is IN !

We should all be very proud of this.

Seriously, that's GREAT! I would have hated to see so much dedicated effort thrown out (I hope Harald was able to keep much of his work in, too). It will be a relief not to have to tell newcomers to forget about the official version and to use some informal "community supported" version from GitHub instead. Now osC can speak with one voice.

 

osC has traditionally been "released when it's ready, not on a fixed schedule". While of laudable intent, that is a problem in that current and potential users have no idea how long it's going to be until a product refresh... weeks, months, years? osC gets the reputation of not being maintained and enhanced, and that's a severe image problem. If The Powers That Be (Harald, et al.) don't want to commit to a schedule, could something else be done to enhance communications with the community and with the ecommerce world at large? Perhaps a rolling (continuously updated) Road Map included with the official download: "This is what is in the pipeline, this is the near-term stuff we're finishing up (and should be in the next release), and the next release is probably early 4Q 2017 if all goes smoothly." That sort of thing.

 

Link to comment
Share on other sites

v3.0 will hit you hard in the face :P It's more javascripty because of modern user interface design principles. People with javascript disabled should surf the web on a WAP device and complain about life in some WAP optimized forum out there.

Palin = 2.3.x

Cleese = 3

 

Link to comment
Share on other sites

@GLWalker

There 2 examples :

One to execute a function, one to display something

Also if a hook exist you can extend with another hook. Advantage no intervention in the code and in orignal hook but for not the best solution (depends of the situation)

 

 

Hook with call  (not display)

$OSCOM_Hooks->call('Orders', 'ActionDeleteConfirm');




<?php

  namespace OSC\OM\Module\Hooks\Admin\Orders;

  use OSC\OM\OSCOM;
  use OSC\Sites\Admin\OrderAdmin;

  class ActionDeleteConfirm {

    public function __construct() {

      if (OSCOM::getSite() != 'Admin') {
        OSCOM::redirect('index.php');
      }

      $this->restock = $_POST['restock'];
      $this->oID = (int)$_GET['oID'];
    }

    private function redirect() {
      OSCOM::redirect('admin/orders.php', osc_get_all_get_params(array('oID', 'action')), 'AUTO');
    }

    public function execute() {
      OrderAdmin::removeOrder($this->oID, $this->restock);
      $this->redirect();
    }
  }

Hook with with display (very simple)


Registry::get('Hooks')->call('AllShop', 'FirstTime');


<?php
  namespace OSC\OM\Module\Hooks\Shop\AllShop;

  class FirstTime {
    public function execute() {
        echo TEXT_INSTALL;
        echo '   <div class="text-md-center;"><br /><a href="http://www.mysite.org/" target="_blank"><img src="images/logo.png" border="0" height="100" width="100" alt="Site"><br />Go to Site</a></div>';
        echo '   <div class="text-md-center" style="font-size: 10px;padding-top:10px;">blabla <a href="http://www.mysite.com" target="_blank">mysite</a>.</div>';

    }
  }


Regards
-----------------------------------------
Loïc

Contact me by skype for business
Contact me @gyakutsuki for an answer on the forum

 

Link to comment
Share on other sites

i have just recently spent a few days of getting a store in sync with edge

 

then a mail ticks in from a programmer i have hired for a job creating a a addon that can calculate avg. delivery times so we have an idea on how long it takes to delivery

 

 

this programmer says that 2.4 will be the end of life for the responsive version.... is he right? or would responsive live on and take bits from 2.4?

Link to comment
Share on other sites

  • burt locked this topic
  • burt unlocked and locked this topic

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...